andrewb


Group: Members
Posts: 316
Joined: July 2005 |
 |
Posted: Aug. 10 2007,01:36 |
 |
I had problems with a TP-link card with the atheros chipset. I ended up using ndiswrapper to get wpa to work. You should try this. Instructions are the post referred to by ^thehatsrule^ above. Note that if you are running on a slowish machine it is worth saving the /etc/ndiswrapper directory to backup once the 'ndiswrapper -i' command has been used, then this step can be missed out in furture (all it does is set up the windows drivers so ndiswrapper can use them - it can be a lengthy process where there are a lot of cards serviced by one driver).
|