This error message is returned both by the Palm OS Emulator, and by the Palm
Device.
It is caused when the CodeWarrior Debugger Plugin looks for a Windows
registry key used by the previous version of CodeWarrior. The error indicates
that the debugger has failed to connect to the emulator or device. There are
several possible reasons and workarounds:
� Constructors for Palm OS 1.2 and 1.5 both have a bug in which they use 100%
of CPU. If Constructor is running at the same time as the debug session, this
will prevent the debugger from connecting. The Constructor must be shut down
before debugging.
� As a consequence of previous debugging the application to debug is running
on the device or Palm OS� Emulator while trying to debug.
� An application segment is greater than 64K. To avoid it the application
should be reorganized in a a multi-segment structure, taking care or arrange the
files in the segments to guarantee that no segment exceeds 64K.
� If this message is returned while debugging to the device, it is possible
that the 'shortcut .. 2' is not recognized correctly by the device. The best
way to do this is to enter it in the Find window. A recognized entry will
disappear when the '2' is entered, with no up-arrow at the lower right of the
Find window.
� The HotSync� Manager is not running when debugging to the device. The
serial port on the device must be free. In some instances (e.g., an improper
termination of a debugging session or HotSync process) the serial port might not
be available. A soft-reset will free the serial port.
� If this message is returned using the Palm OS Emulator, the "Redirect
NetLib Calls to Host TCP/IP" in "Properties" and "Use TCP/IP Sockets"
preferences should be checked.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
