WZC - Windoze Zero Config

[.UK.]

WZC the XP system util for wireless network connections. Its shite.

Probably well known to all those who have worked with WZC on systems with real-time requirements - WZC adds enough traffic every 60 secs to cause a ping over 3000 or a time-out. This is because it is broadcasting probe requests (or something similar - not entirely sure).

The problem here lies with manufacturers who use WZC as their primary util. Many installation discs will not run the install program in XP, you need to locate the application yourself and run it in Win2k compatibility mode, then use "services.msc" to knock off WZC for good (its near bottom of list - disable it and put it on manual startup).

Its been pissing me off for a while.

[Qu|rk]

WZC the XP system util for wireless network connections. Its shite.

I would have to agree there, from the bit of toying done, it does respond much better to XP beta SP2 however. I will assume that you disabled the XP config utility before playing with it as well, if not unwanted bluescreens of death can occur. If you have not yet...

A) start button
B) control panel
C) administrative tools
D) services
E) scroll down to the windows zero configuration, right click on properties.
F) Change startup type to DISABLED
G) Click on STOP
H) Click on OK

Quirk-

[[Syntax]]

I havent hit a system where zero config turned on caused a problem. I know people turn it off to prevent connecting to networks on accident.

As for Software not installing on XP, Most Linksys cards dont require the software be installed on XP because of Zero config, On Windows 2000 the same card requires the software due to lack of ZeroCfg.

What brand cards were you installing? Where you trying to turn Zero Config off, and use the connection manager software the wireless card comes with? If your doing that, I can understand why the software had to be ran in 2000 Compatibility mode.

[.UK.]

I use a Linksys WMP54G and a BenQ AWL300, they both suffered the latency issues. The problem with WinXP is that WZC is by default enabled, and by default the installers won't do anything other than install drivers unless you disable WZC.

I didn't test prior to resolving the issue by disabling through services.msc, but I have a feeling that the installation of the utility is not dependant upon the status of WZC, rather whether the OS is WinXP

[Chris]

A) start button
B) control panel
C) administrative tools
D) services
E) scroll down to the windows zero configuration, right click on properties.
F) Change startup type to DISABLED
G) Click on STOP
H) Click on OK

Just as an FYI for those that are not as experienced and reading this. The actual service that .UK. and Qu|rk are referring to is Wireless Zero Configuration, not Windows Zero Configuration.

Just thought that should be cleared up.

[Qu|rk]

Yes, again you've found another of my posts where my logic and thinking wasn't all there - I'm going to stop posting while under the influence as to not confuse others.


Quirk-

[[Syntax]]

.UK. thats exactly what I said... that XP does not require the Wireless Configuration Utility be installed.. Because XP comes with Wireless Zero Config. The installer for Linksys Products, at least the PCI Card I installed into someones machine recently, will pop open, and then close instantly, before you have a chance to see anything.

The installer is OS dependant, and Linksys recommends you use the Zero Config when using XP.

That is why you had to run it in 2000 mode, to fool the program into thinking Zero Config was not present.. If it thinks your OS is 2000, its going to install the utility that comes with the card.

As for your latency, It could be related to that bluetooth bug I mentioned, try turning Bluetooth support off.. on your router..
if theres an option. The router they were using was a Linksys B router, and a PCI G card.

[.UK.]

I wasnt posting a question, it was an answer. But thanks anyway, and Bluetooth has nothing to do with it.