Smart and powerful OCR tools

WiFi-Manager – FAQ

- I have some problem with WiFi-Manager.

Firstly, check the log file "WIFIMAN-LOG.txt" for errors, for most cases you can find the reason there. Use sample projects for testing, they have additional code for checking status of Windows WiFi service. You can use sample projects as start point for your application, or you can use them to learn how to use WiFi-Manager. If you cannot find answer to your question and want to contact us for technical support then please launch "Delphi Advanced Sample", reproduce the problem and send us "WIFIMAN-LOG.txt" log file from its directory. (..\program files\[Advanced ]WiFi-Manager\samples\delphi advanced sample\) with the detailed description of the problem.

- I cannot connect to Access Point.

Firstly, make sure you have created correct profile for this network, you won't be able to connect if Access Point (AP) has different type of authentication or encryption, or different key/passphrase. Try to narrow the problem by setting AP to use "Open system" authentication and "None" encryption, if you can connect to such AP then probably you typed key or passphrase incorrectly, for WEP keys make sure you type keys in the correct form: 5 or 13 characters if you type key in ASCII form, 10 or 26 characters if you type key in HEX form. For WPA-PSK and WPA-PSK2 passphrase must be in ASCII form and cannot be shorter thant 8 characters.

- My application does not work if I start it on different PC.

Your application needs WiFi-Manager installed, except if you have purchased sources codes (in this case you can link WiFi-Manager statically with your EXE file). Please read   WiFi-Manager documentation for details how to install WiFi-Manager.

- How can I enable/disable Windows WiFi service manually?

Open "Control Panel", double-click "Administrative Tools" icon, double-click "Services" icon, a new window with the list of services will appear. For Windows XP SP2 find "Wireless Zero Configuration" service, for Windows Vista find "WLAN AutoConfig" service. Right click it, select "Properties" command in the context menu, a new window with the service properties will appear. To start the service select "Startup type = Automatic" and press "Start" button, to start the service press "Stop" button and select "Startup type = Disabled".

- Does WiFi-Manager need Windows WiFi service?

WiFi-Manager always manages wireless networks with help of Windows WiFi service, therefore this service must be started. You can check Windows WiFi service status with "GetWIFIServiceStatus" function and set new status with "SetWIFIServiceStatus" function, note you must have enough privileges to call "SetWIFIServiceStatus" function.

- Does Advanced WiFi-Manager need Windows WiFi service?

Advanced WiFi-Manager can also communicate with WiFi adapter drivers directly, in this mode (NDIS calls mode) Windows WiFi service must be disabled because only one software can communicate with the WiFi adapter driver at once. By default Advanced WiFi-Manager detects if there is WiFi service for this version of Windows and for Windows XP SP2 and Windows Vista it works exactly as WiFi-Manager, for other Windows versions it uses NDIS calls mode. You can make it always use NDIS calls mode with "SetLibraryOption(OPT_MODE, OPT_MODE_NDIS)" function, it must be called before calling any other functions, see notes for OPT_MODE constant.

- I cannot create more than one profile with WiFi-Manager in Windows XP x64.

You can see this problem only if your application is x86 so you use x86 binaries of WiFi-Manager. We know about this issue, it is because there is no way to create more than one network profile via WZC API in WinXP x64 SP2. You try to create second network profile and it fails. Windows x64 SP2 has a lot of bugs in x86 version of WZC API, Microsoft knows about it but dropped that OS. Therefore there is no way to fix this problem, we spent a lot of time to find any workaround but with no success. The only way for this OS is to use Advanced WiFi-Manager in NDIS mode to avoid using WZC API. Or make your application 64bit, it will use x64 version of WiFi-Manager and WZC API and therefore it will work properly.

- I cannot use some functions in Windows x64.

You can see this problem only if your application is x86 so you use x86 binaries of WiFi-Manager. Windows x64 blocks some actions if they are called from x86 code. Therefore the following functions have some limitations in Windows x64 if your application is 32bit: SetAdapterIPInfo, SetAdapterDNS, SetAdapterMac, SetAdapterDefaultMac, EnableNetAdapter, DisableNetAdapter, RestartNetAdapter, SetNetAdapterIPInfo, SetNetAdapterDNS, SetNetAdapterMac, SetNetAdapterDefaultMac.
These functions will work from x86 code but they will require system reboot to apply changes because Windows x64 blocks attempts to disable or enable adapter from 32bit code to apply changes. The best solution is to use x64 version of WiFi-Manager in Windows x64.