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.

It is a known issue of third-party trial protection system we use for trial versions of our products. We are working on the solution, right now you can use Visual Studio 2005 or use Windows XP if possible. Full versions of our products do not have this problem, it is related only to trial versions that you can download freely.

It is a known issue of third-party trial protection system we use for trial versions of our products. We are working on the solution, right now you can use Windows XP if possible. Full versions of our products do not have this problem, it is related only to trial versions that you can download freely.

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.

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 this page for details how to install WiFi-Manager.

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".

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.

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.

It is a known issue of third-party trial protection system we use for trial versions of our products. We are working on the solution, right now you can copy "regsvr32.exe" into some folder, rename it to any other name (for example "regwifi.exe") and execute it: "regwifi.exe wifiman.dll". Full versions of our products do not have this problem, it is related only to trial versions that you can download freely.