Roger Binns
2006-04-03 05:03:36 UTC
I just posted something to bitpim-user about this and updated
the help page:
http://www.bitpim.org/help/errors-datacomms.htm
What I was seeing with my VX4400 and Prolific pl2303 cable
was that reading files would abort with a CRC error. The
data that had arrived was a plausible block matching the
read block, terminated with ~ followed by some more gunk
terminated with ~ and then some more gunk. However the
checksums weren't correct. (I even wrote some code at
one point that split the data into ~ terminated sections
and looked for any that were valid). I also tried adding
delays in reading (eg 0.2 seconds every 5 blocks read).
Nothing helped - it would always fail between the first and
last wallpaper read, although the failure would sometimes
occur in the phonebook or index files.
Once I rebooted my machine into /onecpu mode, the reading
was 100% reliable repeatedly.
Roger
the help page:
http://www.bitpim.org/help/errors-datacomms.htm
What I was seeing with my VX4400 and Prolific pl2303 cable
was that reading files would abort with a CRC error. The
data that had arrived was a plausible block matching the
read block, terminated with ~ followed by some more gunk
terminated with ~ and then some more gunk. However the
checksums weren't correct. (I even wrote some code at
one point that split the data into ~ terminated sections
and looked for any that were valid). I also tried adding
delays in reading (eg 0.2 seconds every 5 blocks read).
Nothing helped - it would always fail between the first and
last wallpaper read, although the failure would sometimes
occur in the phonebook or index files.
Once I rebooted my machine into /onecpu mode, the reading
was 100% reliable repeatedly.
Roger