H
Harry Simpson
I'm using the PocketPC Installer Professional app for deploying our app.
Works great but we've decided we have to move the Profile.cpf out of the
installation itself to keep the installation the same for all clients while
be able to provide the variable Profile.cpf to clients separately.
So this installer app allows the developer to shell out to one application
at the end of the install app. My thought was to write another small
bootstrap app that I'd call from here to programmatically add a WiFi Profile
and set it's various properties programmatically - is this possible?
(Motorola MC70 - Windows Mobile 5)
The other idea I had was to call WCELOAD with the name of the Custom.cpf but
I cannot find wceload.exe on the device anywhere to list in the program
path. I know it's there since it auto invokes on physical tap of any CPF or
CAB file.
Basically I need to be able to have a variable file like Custom.Cpf which
will set up a particular WiFi profile with that clients particular AP essid
and passphrase etc. This has to be bootstrapped before the device can
communicate with the AP to start with.
TIA
Harry
Works great but we've decided we have to move the Profile.cpf out of the
installation itself to keep the installation the same for all clients while
be able to provide the variable Profile.cpf to clients separately.
So this installer app allows the developer to shell out to one application
at the end of the install app. My thought was to write another small
bootstrap app that I'd call from here to programmatically add a WiFi Profile
and set it's various properties programmatically - is this possible?
(Motorola MC70 - Windows Mobile 5)
The other idea I had was to call WCELOAD with the name of the Custom.cpf but
I cannot find wceload.exe on the device anywhere to list in the program
path. I know it's there since it auto invokes on physical tap of any CPF or
CAB file.
Basically I need to be able to have a variable file like Custom.Cpf which
will set up a particular WiFi profile with that clients particular AP essid
and passphrase etc. This has to be bootstrapped before the device can
communicate with the AP to start with.
TIA
Harry