roberts


Group: Members
Posts: 4983
Joined: Oct. 2003 |
 |
Posted: May 01 2006,20:04 |
 |
Sorry, not to be of much further help.
The dlink website shows that there are 3 revisions of this card. Each revision has different software requirements.
The half dozen or so devices that I have tested with the latest ndiswrapper have all worked pretty much the same.
After ndiswrapper -i your_driver's_inf and doing a modprobe ndiswrapper then the device appears. You can see the unconfigured device by typing iwconfig without any parameters.
If you don't see a unconfigured card at this step then remove the module and unload ndiswrapper and try another driver.
If you do see a device by only using iwconfig then you can proceed to configure the card with your settings, using manual commands or the GUI.
I have heard it reported that on some machines, the wireless cards may need extra boot options to get the card recognized, Irq conflicts or such. I know that can be difficult if you have such a machine.
|