Data Communications Error

BitPim speaks two major protocols with your phone. One is the official vendor sync protocol which usually only covers most of the phonebook information and the other is to access the embedded filesystem in the phone.

For CDMA phones, the latter protocol has a checksum for each command and response transmitted and received. Some of the synchronization protocols also have the checksum such as the protocol used for CDMA LG phones.

If you encounter this error, then it means the data the phone thinks it sent is not the same as the data received by BitPim. BitPim detects the problem and immediately stops.

The usual cause is in your cabling and where you plugged it in. You should ensure your cable is plugged directly into a port on your computer, not going through a hub. Do not use cable extenders, gender changes or converters. If you still have problems, use a different host port. Try reseating your cable at the phone end. If none of these solve the problem, then the problem may be your cable.

Multi-processor machines: Sometimes this problem is caused by poor driver behaviour on multi-processor machines. Your machine is multi processor if you have hyper-threading turned on, or it is dual-core. You can also tell by running the Task Manager (press ctrl-alt-delete) and looking in the View menu. If there is a submenu labelled CPU History that lets you choose one graph or one graph per CPU then you have a multi-processor machine.

Editting your boot.ini could result in your machine not booting if you make mistakes. If you run bootcfg from a command prompt, it will list the current operating settings.

You can reboot your machine and tell Windows to only use one cpu even if there is more than one in your machine. To do so you will need to add a line to boot.ini and specify the /onecpu switch. Microsoft has a guide for editting boot.ini in KB289022. In general you should copy the first line in the [operating systems] section, add /onecpu on the end and edit the text between quotes to say it is the onecpu line. You may also want to increase the timeout (seconds) in the [boot loader] section. When you reboot, you'll have that many seconds to pick the onecpu line. You can tell if it worked by running Task Manager as detailed in the previous paragraph and looking for the View > CPU History sub-menu.

BitPim Online Help built 17 January 2010