Netgear USB adapter is lost after reboot...

[jeradsyn]

I have found a problem that I have been attempting to resolve...

I am using a Netgear MA111 v1 USB adapter for connectivity, XP Pro/SP2. The management software and the wireless device are both working fine, until you reboot.

Once you reboot, the management software starts (I can see it in the task manager), but its icon and wireless indicator icon don't show up in the system tray. To get the connectivity back, I have to unplug and replug the USB adapter- it seems to wake up the whole process and restart the management console. I then have to reenter the SSID and the WEP Key to fully restore the connectivity.

Has anyone seen this before? I have checked the Netgear website but haven't found resolution. Hardware is cheap these days, but if there is an even cheaper out,... cheap is good!

Any assistance with this would be greatly appreciated.

jeradsyn.

[CCT]

http://kbserver.netgear.com/inquira/...15#__highlight

[NooNoo]

Jeradsyn does the XP wireless config exhibit the same symptoms?

[jeradsyn]

Thank you for the response, CCT and NooNoo; your assistance is much appreciated.

I used the fix to repair a bluescreen that was occurring during bootup. 0x19 bad_pool_header.

I will give the Windows manager a try, to see if it resolves the problem, and drop you a line.

[NooNoo]

Aah Bsods... do you have any others?

[jeradsyn]

just the one bsod... I have reconfigured the wireless to Windows-managed. Can't get my gf to give up the computer to reboot it! She's in the middle of a game of Mahjjong!

More to come...

jgd

[jeradsyn]

By switching from the NETGEAR manager, and allowing Windows Wireless manager run the show, it works- got to be the best solution to this problem.

Instead of throwing money at the problem, try throwing lots and lots of expert advice!!! Many thanks, NooNoo... and to you, CCT.

Happy holidays, to which ever you celebrate!

jeradsyn

[NooNoo]

OK, so go to Netgear and get the latest driver/software for your card. (Sometimes they manage to list it as firmware) and test that. If they both work now, you can put it down to a bad driver.