NetStumbler.org Forums - View Single Post - Seamless Connectivity for a WinCE 4.2 .NET device

arsham11 · 07-17-2005

The OS is built specifically for us using the WinCE 4.2 .NET platform builder which based on Microsoft's comment and actually seen in the performance tests is capable of resuming the system in less than a second. The module used at this time is an integrated small footprint b sol. We can specify the Auth method for the best end user exp.

Now the problem is unlike other drivers, module's driver is un-loaded before the suspend and has to be initialized after resume. I am not looking for a wake-on-LAN solution, but a way to possibly have the module's state saved as part of the OS image before suspend. This way, the module will think it never went into suspend and will resume work without a need for re-association.

07-17-2005	#3 (permalink)
arsham11 <-121-> Join Date: Mar 2004 Location: California Posts: 29	The OS is built specifically for us using the WinCE 4.2 .NET platform builder which based on Microsoft's comment and actually seen in the performance tests is capable of resuming the system in less than a second. The module used at this time is an integrated small footprint b sol. We can specify the Auth method for the best end user exp. Now the problem is unlike other drivers, module's driver is un-loaded before the suspend and has to be initialized after resume. I am not looking for a wake-on-LAN solution, but a way to possibly have the module's state saved as part of the OS image before suspend. This way, the module will think it never went into suspend and will resume work without a need for re-association. __________________ <-arS-121-Ham-> Last edited by arsham11 : 07-17-2005 at 02:28 PM.