Has anyone found a way to work around the delay problems? I found out the hard way about the problems with SrmReceiveCheck. When I narrowed it down, I did a search and found the bug to be documented here.
My problem is on a T3, my comm routine runs about half the speed of OS<5.0. I found the palm is taking 22-24 ms to respond to a two byte response. The response is sent within 5 ms of the request, but the Palm waits 22-24ms before it recognises that there is data in the buffer. I tried SrmReceiveCheck as well as SrmReceiveWindowOpen to check for data and it didn't make any difference. I was hoping the problem would dissapear when I used the SrmReceiveWindowOpen but of course it couldn't be that easy... >From previous threads is seems to be a delay in how the OMAP processor moves data around it's buffers.(?) Is this something that can even be fixed or is it tied to the hardware? I have to say, supporting all these new "better" Palms has become quite unprofitable and very time consuming. The original reason I chose Palm instead of PPC is because of Palm's simplicity...it made for a better platform for our product. Unfortunately that is no longer true. It seems I can't just write one program, it's got to be tweaked every time someone releases a new model... We are running out of compatible PDAs because of one OS or hardware bug or another. Thanks, Mike -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
