I rue the day I bought my D Link wireless networking equipment. Well, it's not all that bad, but it does sometimes cut out at the most annoying of times and come back again all of a sudden. I found a fix to this problem a few months ago when I was experimenting with different nLite builds for Windows XP. I think what I did was remove the Wireless Zero Configuration service (not disable mind, remove) but I can't remember and I have since made newer CDs with up to date hotfixes integrated.
What appeared to be the source of the problem was that the Dlink utility for managing the wireless connection to the router would not run while the wireless zero configuration was started. The Dlink utility would start with windows, and would appear in the task manager, but there would be no tray icon and it just seemed to be running in the background doing nothing, while windows managed the connection. This would be fine, except I get these intermittent disconnects from the router.
When I try to disable the service using services.msc so that it doesn't start WZC at startup, the D Link utility works and the icon appears and the connection is a lot better. But... after booting into windows, this takes an age to start up. Again, I know nothing about this, but it seems as though windows is having an issue because I turned off the service. This is why I think that the removal of the service is how I got everything sorted last time. Windows always used the Dlink app, rather than WZC and there was no huge lag time at boot before my PC got a connection.
Can anyone comment on this? Do those of you running wireless equipment have to turn off the Wireless Zero Configuration service too for the utility to work?
What appeared to be the source of the problem was that the Dlink utility for managing the wireless connection to the router would not run while the wireless zero configuration was started. The Dlink utility would start with windows, and would appear in the task manager, but there would be no tray icon and it just seemed to be running in the background doing nothing, while windows managed the connection. This would be fine, except I get these intermittent disconnects from the router.
When I try to disable the service using services.msc so that it doesn't start WZC at startup, the D Link utility works and the icon appears and the connection is a lot better. But... after booting into windows, this takes an age to start up. Again, I know nothing about this, but it seems as though windows is having an issue because I turned off the service. This is why I think that the removal of the service is how I got everything sorted last time. Windows always used the Dlink app, rather than WZC and there was no huge lag time at boot before my PC got a connection.
Can anyone comment on this? Do those of you running wireless equipment have to turn off the Wireless Zero Configuration service too for the utility to work?
