I have installed this network card on about 3 computers, and I have never had a problem.
The installation of this card into the PC is quite simple, just like installing any card. The antenae sticks out the back, could be problems if the back of your PC is often brushed against by animals. I have always wondered why they don't allow you to extend the ariel. as behind the PC can not be the most interferance free place.
Anyway as soonas its installed you install the software on the CD (Ignoreing windows finding new hardware, in fact to make it easier do the install off the CD before turning off and putting the card in)
The software installs quickly and asks to a few questions about the region your in, so the transmission frequency is right, etc.
As soon as it is set up you have the Netgear wireless software to do the connections. To be fair I have always hated these additional wireless managers as Windows Wireless manager is always used behi9nd the scenes, but whether its Netgear, Dell, Intel, etc they always have theirs loaded aswell which wastes more resources and half the time THEIR application crashing is what cuases your problem. So a lot of the time I turn off their management control software and just use windows it uses less memory than the 2 together and has all options available.
But still the software doe shave some nice graphical features for connecting and monitoring the network.
Overall this card is good, however with new MIMO technology I would be looking at the WPN models more than the WGT's, as well as some truely designated N range wireless adapters.
Overall though I have had no problems with these cards and I have found them very reliable. I have used Netgear equipment a lot and they have never caused me or my clients many problems, unlike some other brands. But it comes down to personal tastes, and making sure you have the right equipment to work togehter to get the most out of it.
I bought a NetGear wireless LAN based around the DG834GT router and WG311T adapter cards for my broadband service; I thought some of the problems I encountered were worth a mention.
The first four machines worked fine and I encountered no problems installing or getting them to work. However, on adding a fifth machine, I experienced problems that were frustrating to say the least and as it turned out, impossible to circumvent as NetGear - though denying everything - were only too aware that there was a major bug in their software.
Firstly, a quick pre-amble on where the wireless LAN market is with regard to the current major players. The wireless network adaptor market is currently a game of two chipsets; these being the Atheros© chipset as used by companies such as NetGear and D-Link, and the Broadcom© chipset as used by companies such as US Robotics and LinkSys.
The Atheros chipset is of US origin, being manufactured in China more than likely to save costs and has a host of problems and therefore critics. These problems are widely reported (see the NetGear forum).
In identifying the issue area, two main schools of thought seem to prevail; one the one hand, it is believed that there are issues of compatibility between the Atheros chips and the AMD CPU.
On the other hand, it is believed that the Atheros chips have compatibility issues with the VIA chipset used by a number of motherboard manufacturers.
Other threads are also in evidence, such as incompatibility of Atheros chips with certain ATi VGAs.
What happens is that the PC freezes completely, no mouse or keyboard input and the only get-out is to reboot the PC. This freeze seemed to manifest itself around boot-up or just after entry into Windows; very occasionally it would boot up normally but only until you tried to access the web, when it would freeze. There is - to date - no known work-around.
I can't speak for D-Link but NetGear are doing a fine job of not really saying anything about the problem, presumably in the hope that people will feel that there isn't really a problem. There will be NO fix for v1.0 adaptors and they're still doing the denial thing on the v2.0 stuff.
The good news is that if you've got an Intel-based system you're OK.
The Broadcom chipset - also of US origin - is an in-house design from US Robotics, so it's hardly surprising that they'd choose to use it in their own hardware. Fortunately for LinkSys, they had the good sense to use it too.
Someone really sat down and did their homework with this chipset; it's just as easy to install as any of the Atheros-based offerings and has the added advantage of working with everything, so if you've got an Intel-based system you're still OK and no matter what permutation of AMD-based system you have, you're also OK.
So, there is a well-documented and very major issue with Atheros-based networking adaptors with certain permutations of AMD-based systems; this could be as a result of the processor itself, the motherboards VIA chipset or the model of ATi graphics card that is reported to cause the problem.
The problem with the problem is that despite the prodigious quantities of guesses, opinions, technical theses and itemized reports of what happens when it happens, is that no-one is really any closer to knowing for sure what the specific cause is - no thanks in no small part to the rather unhelpful stance adopted by NetGear.
Consequently, you could well buy an Atheros-based wireless LAN for your AMD-based computer network and it could/might work, but when you know that buying a US Robotics or LinkSys offering will definitely work, it hardly seems worth the anxiety of trying it.
I eventually gave up on the fifth machine, returned no fewer than two NetGear WG311Ts and bought a US Robotics card - installed, straight in and working with the existing NetGear LAN.