> None of these solutions is very good when you're trying to beam something
> to the laptop. :)
A "Disable IrDA Polling" in Prefs could have solved that also, so you
could toggle between both behaviors.
> The IrDA stack won't come up fast enough to catch the first discover
> request, but it'll get the second one which it will then respond to. An
> IrLAP connection will then come up, and so on. In Palm OS 3.0 - 3.5, the
> progress dialog appears as soon as the IrDA stack starts up. In Palm OS
> 4.0, it doesn't appear until the Tiny TP connection is established - just
> before the OBEX connection is made.
Is this why IrDA in general on OS4 (and more specifically the m50x
devices) is 2-3x slower overall than previous OS versions and hardware?
/d
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
