|
Situation: BitPIM 0.7.29 running in Windows XP Pro
(SP2) with LG VX6000 connected via straight USB cable; phone is not an upgrade
from a prior handset, but had been "re-programmed" by Verizon to fix a problem
of jumping to non-Verizon towers and failing to return to Verizon towers even
when available, in spite of recent PRL update (it did improve this problem, but
didn't entirely solve it). Verizon service persons indicated the phonebook
and calendar had not been deleted so were not re-loaded, but I suspect
that may not be entirely true. Phone communicates satisfactorily with
BitPIM which is able to "Get" the wallpaper, calendar and ringers with no
problems. Have been able to successfully "Send" ring tones, but have not
yet tried to send wallpaper or calendar data from BitPIM to the
phone.
Problem: Attempts to "Get" the phonebook data
return the dreaded "unexpected exception" message indicating under
"IntegrityCheckFailed" that the phonebook data is inconsistent and there are
"multiple entries with the same serial number." Unlike some of the other
postings on this subject, BitPIM does not successfully "Get" ANY phonebook
entries, and after closing the "Exception" dialog box, the "Log" or "Protocol
Log" are both completely blank. In the "Exception" dialog box, under
"Frame getphonebook", the "dupecheck" line lists all but three of the 57 numbers
also listed above in the "pbook" line. This problem occurs repeadedly,
with no apparent variations.
Question: Is there any relatively easy way to
save my phonebook data (i.e. rather than laboriously writing down all the
entries or manually typing them into BitPIM) so that BitPIM can push this data
to the phone with corrected serial numbers? Even alot of "block-copying"
would be preferable to manually re-entering all the names, numbers, emails,
etc. I'm not a programmer, but am fairly savvy in computers and other
tech stuff.
Additional Thought: This problem seems to be a
frequent post to the user forum. Since those discussion threads indicate
that BitPIM already has the ability to correct the duplicate phonebook serial
numbers, it might not be too big a step to add the ability to "Get" the
phonebook data even though it might be corrupted by duplicate serials, warn the
user of the problem, then walk the user through deleting the phone's entries and
restoring the phone's phonebook (with corrected serials) from BitPIM.
Maybe in v0.7.30?
Help is GREATLY appreciated.
Dan West
|
