> err = ExgPut(socketPtr);
> if (!err) {
> err = ExgDBWrite(WriteDBData, socketPtr, NULL, dbID, cardNo);
> err = ExgDisconnect(socketPtr, err);
> }
>
> Sometimes the LCD display gets corrupted after the ExgPut() call.
After the ExgPut call or after the ExgDBWrite call? How do you know? Could
your callback function be writing to screen memory? What device are you
using? Which version of Palm OS are you using? Debug or release ROM?
If you can get your beaming code working in loopback mode (shortcut-dot-t),
you can run it in Poser on a debug ROM. I'm guessing either you or the OS is
writing using an invalid pointer. There's a good chance using Poser as I
described will discover who's doing this when it first happens. Of course,
the problem may go away when you run in loopback mode. This is likely if our
IrDA stack is to blame.
You could use the "ss" = "step spy" command in PalmDebugger to watch the
appropriate area of screen memory, but you couldn't stay connected to the
debugger while you're actually beaming. This isn't likely to be a problem
because it sounds like the spurious write is occurring before you call
ExgDisconnect. I don't think the serial port is needed until then.
Please post similar questions to comm-dev-forum in the future. Thanks!
--
Danny @ Palm
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
