I can't help with the first problem.
The WiFi question can, in theory, be handled by P/Invoking (calling to
native code), the Windows Zero Config API. OpenNETCF has classes for doing
this. See the Smart Device Framework at
www.opennetcf.org. How applicable
this is will depend a lot on what authentication mechanisms are used by the
wireless network. In particular, EAP-based authentication requires a *lot*
of work to configure and there is *no* documentation on the APIs for doing
this; The Smart Device Framework wraps the APIs, but the meaning of the
fields of various structures is not specified anywhere.
Paul T.
<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Sorry my English.
>
> I have many PocketPC > 70 in different citys
> My application and config.ppc placed on SD card
> Users do not understand how to setup a handheld computer
> Users must connect by bluetooth and mobile phone to internet and send
> information to central office
> One user can have from 1 to 7 mobile operators with different
> connections setting (phone number,username,...)
>
> 1. I need from my application on startup create connections for all
> mobile operator (list in config.ppc)
> 2. Users click on Button "Connect" select current mobile operator
> and my application connect by selected connection
> 3. Application send information
> Problem in steps 1 and 2
>
> Users must connect in office by WiFi
> 1. Users click on Button "Connect WiFi" my application connect to
> AccessPoint (from config.ppc)
> 2. Application send information
> Problem in steps 1
>
> Can your help me?
>
Similar Threads
