Thanks for the post. It saved my life.

@Jake – heh, maybe it’s just me then. Most cards I own require ndiswrapper to some degree. :(

@vacri: Just pointing out that the card seems to work better in ndiswrapper than XP, as Luke said.

@Luke: Actually, most of the cards in my house have drivers. Three computers have drivers included with Ubuntu that work out of the box (a Netgear PC Card, Atheros, and Linksis). Mine is a Broadcom that has to be downloaded via ethernet with the restricted device manager, but that’s no big deal. None of these cards were purchased for Linux compatibility either. :)

I might be wrong, but I think if you only install the driver (when prompted by the Add New Hardware wizard) you won’t encounter this issue. I think it happens when you install their wireless manager suite.

But yeah, it’s sad when a card works better with ndiswrapper than under winxp. It’s even sadder than the card requires nidiswrapper at all, but which one doesn’t these days.

Sigh… You can make 3 lists of Wifi cards: those which work natively under linux, those which work with ndiswrapper, and those which do not work at all. The first list is sadly the shortest one. :(

Wouldn’t it be more to Netgear’s credit if the WG111 didn’t need ndiswrapper?

Well, to Netgear’s credit, the WG111 works better in ndiswrapper than any other network card I’ve tried… in fact it’s on a commonly used machine around the house. No problems.

This “bug” is a total pain in the ass. I ran into the exact same thing when I did a clean install on my computer a few months ago.

What in hell?! That’s disgraceful.. shameful.. downright evil!

I’m referring of course to the “circa-1991” design :P

(The Netgear thing is even worse)

Apparently he is to busy writing registry hacks to actually update his circa 1991 website layout and design…

BURN!!

That seem’s ridiulous! Why would networking drivers even need to touch that file?