anightin
04-14-2005, 10:16 AM
Hi,
I've written a WOL (wake on lan) app for my NZ90 and its WiFi card courtesy of cygwin and the PalmOS5 dev kit, but there seems to be an issue with Netlib and the use of UDP and broadcast addresses.
I've convinced myself of this by the use of WOL Monitor (thanks to www.depicus.com) in that if I UDP a specific IP address (x.y.z.a) say on port 7, this is sufficient to wake up my PC in standby.
If I shut down the PC it can only be woken by sending the UDP datagram packet to x.y.z.255 -- which is where the NZ90 just plain crashes with a Fatal error.
Running the exact same code on the PalmOS5 emulator (using the host PC UDP stack), works file and wakes up my PC from any sleeping state using the x.y.z.255 IP broadcast address.
Any clues as to how I would get round this one? I hear that the Palm Tungsten-C has a re-written Netlib to cope with broadcast addresses etc.
I am willing to let people try the app on different WiFi enabled PalmOS PDAs if they are interested.
Cheers
Andy
I've written a WOL (wake on lan) app for my NZ90 and its WiFi card courtesy of cygwin and the PalmOS5 dev kit, but there seems to be an issue with Netlib and the use of UDP and broadcast addresses.
I've convinced myself of this by the use of WOL Monitor (thanks to www.depicus.com) in that if I UDP a specific IP address (x.y.z.a) say on port 7, this is sufficient to wake up my PC in standby.
If I shut down the PC it can only be woken by sending the UDP datagram packet to x.y.z.255 -- which is where the NZ90 just plain crashes with a Fatal error.
Running the exact same code on the PalmOS5 emulator (using the host PC UDP stack), works file and wakes up my PC from any sleeping state using the x.y.z.255 IP broadcast address.
Any clues as to how I would get round this one? I hear that the Palm Tungsten-C has a re-written Netlib to cope with broadcast addresses etc.
I am willing to let people try the app on different WiFi enabled PalmOS PDAs if they are interested.
Cheers
Andy