Hi,
There really isn't a good answer for this. The "IR Enhancement Package"
was always intended as a stop-gap remedy with the New Serial Manager coming
in to save the day in the end.
The best I can recommend is that you isolate the API differences and to
check at launch time which API to use. The New Serial Manager is the API
that will be available in future revisions of the Palm OS(R) software, and
we're right now in the transition to the new way of the serial world.
Cheers,
Bruce Thompson
Senior Developer Support Engineer
Palm Computing, Inc.
>Date: Fri, 29 Oct 1999 11:31:15 -0400
>From: Michael McFarland <[EMAIL PROTECTED]>
>Subject: serious problem? how to handle IrComm across all Palm devices?
>To: "'Palm Development List'" <[EMAIL PROTECTED]>
>Mime-Version: 1.0
>Precedence: Bulk
>Reply-To: [EMAIL PROTECTED]
>
> Here's the situation as I see it. Someone please let me know if/where
>I'm wrong. Visors and Palm IIIe devices are being sold with OS 3.1 and
>can't be upgraded to a newer OS. Palm Vx devices come with OS 3.3. How do
>I write software that uses IrComm that will work on all Palm OS 3.0+
>devices? For OS3.0 and 3.1, I used the official Palm OS Infra-red update.
> I either had the user flip the switch in their preferences to redirect
>serial I/O to IrComm, or I made the change in software. From my
>experiments so far, it seems that the preferences switch and software
>library from the official IR update don't work in OS3.3. And I can't use
>the New Serial Manager functions in OS 3.1. So how is one expected to
>write IrComm applications now?
>
> Michael
>
