At 12:19 AM 8/30/2002 -0700, you wrote: >At 8:13 AM +0100 8/30/02, Steve Janaway wrote: >>I 'think' it's because the Treo runs PalmOS version 3.5 which does not >>include the INet library (which was introduced in version 4.0). I've run >>into problems like this when trying to use the Telephony library which >>was also introcued in PalmOS 4.0 and so isn't on the Treo. > >INetLib has been around since Palm OS 3.0. However, I 'think' that it's >not on all devices (the m1xx series seems to ring a bell). I don't know >about the Treo.
Actually, Palm OS 3.2 would be the one to introduce INetLib, on the Palm VII. INetLib was made to layer on top of ordinary NetLib for Palm OS 3.5, and it was made available for devices as part of the Palm Mobile Internet Kit. My understanding is that INetLib has been an optional component: a licensee can included it in the OS image along with Clipper if they want to support web clippings and INetLib-using applications, but it wasn't required. Palm itself has shipped devices lacking INetLib in the ROM, but available to be installed separately from the device driver CD. I think the Palm m125 is like this, IIRC. As with any optional component, you need to code defensively. Check to see if its there before you use it, and either disable features or provide workarounds if your needed capabilities aren't there. -- Ben Combee CodeWarrior for Palm OS Platform technical lead [EMAIL PROTECTED] -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
