From: Christopher A. Lee on
Finally got it to work after...

I went from Vista home premium 32 bit to Win7 64 bit because that came
with the replacement laptop.

The DWA 160 USB dual band adapter wouldn't work at all on the new
system.

Installing from the CD went just so far and then said it couldn't
detect the adapter.

Downloaded the latest drivers.

Still couldn't detect it.

Turned off Windows automatically installing drivers.

Plugged in the adapter.

Browsed for the driver and pointed to the folder containing the
Vista-64 drivers for it.

Wouldn't install.

Tried again with the XP-64 bit drivers.

Success this time.

Remembered to turn automatic driver installation back on for the next
new device.

But should I really have had to do all this?

And would a less experienced user have known what to do and how to do
it?

There are three revisions of the DWA 160, two with Atheros drivers and
one with Ralink. Turns out there is only development and maintenance
on the Ralink, D-Link aren't maintaining the drivers for the Atheros
version any more.

There is no way to tell which revision from the box until you open it,
and the Atheros versions are still on store shelves.

More unethical behaviour from the manufacturers.


From: John Navas on
On Tue, 03 Aug 2010 11:01:23 -0700, in
<qhlg569ovk85m9gcvq9n6n8rokv6570nmc(a)4ax.com>, Christopher A. Lee
<calee(a)optonline.net> wrote:

>Finally got it to work after...
>
>I went from Vista home premium 32 bit to Win7 64 bit because that came
>with the replacement laptop.
>
>The DWA 160 USB dual band adapter wouldn't work at all on the new
>system.
>
>Installing from the CD went just so far and then said it couldn't
>detect the adapter.
>
>Downloaded the latest drivers.
>
>Still couldn't detect it.
>
>Turned off Windows automatically installing drivers.
>
>Plugged in the adapter.
>
>Browsed for the driver and pointed to the folder containing the
>Vista-64 drivers for it.
>
>Wouldn't install.
>
>Tried again with the XP-64 bit drivers.
>
>Success this time.
>
>Remembered to turn automatic driver installation back on for the next
>new device.
>
>But should I really have had to do all this?
>
>And would a less experienced user have known what to do and how to do
>it?
>
>There are three revisions of the DWA 160, two with Atheros drivers and
>one with Ralink. Turns out there is only development and maintenance
>on the Ralink, D-Link aren't maintaining the drivers for the Atheros
>version any more.
>
>There is no way to tell which revision from the box until you open it,
>and the Atheros versions are still on store shelves.
>
>More unethical behaviour from the manufacturers.

How is it unethical to not provide free support forever?
When you got the device drivers were provided,
and anything beyond that was gravy.
In other words, be grateful the XP drivers worked,
so you didn't have to buy a more current device.

--
John

"Assumption is the mother of all screw ups."
[Wethern´┐Żs Law of Suspended Judgement]
From: alexd on
Meanwhile, at the alt.internet.wireless Job Justification Hearings,
Christopher A. Lee chose the tried and tested strategy of:

> You take pot luck when you buy it whether it will install cleanly
> (Ralink) or not (Atheros).

I haven't had any problems with Atheros and Ralink devices in linux.

--
<http://ale.cx/> (AIM:troffasky) (UnSoEsNpEaTm(a)ale.cx)
17:35:36 up 17 days, 8:06, 6 users, load average: 0.10, 0.07, 0.22
Qua illic est accuso, illic est a vindicatum

From: Christopher A. Lee on
On Wed, 04 Aug 2010 17:36:22 +0100, alexd <troffasky(a)hotmail.com>
wrote:

>Meanwhile, at the alt.internet.wireless Job Justification Hearings,
>Christopher A. Lee chose the tried and tested strategy of:
>
>> You take pot luck when you buy it whether it will install cleanly
>> (Ralink) or not (Atheros).
>
>I haven't had any problems with Atheros and Ralink devices in linux.

Linux is different. You have to be a bit of a hacker and there is more
information available as well as help from people who've hacked it.

Heck, you can even go to the source code which is what I was used to
on the IBM mainframes before they went object code only.

My gripe is that I bought a dual-band adapter to go with Windows 7
because my Vista laptop was close to dying. The hinge had broken and
it was only a matter of time before the screen detached itself
completely. Windows 7 was already on all the new PCs in the stores and
I knew the replacement would have it.

My router was new. When the previous one died I got a dual band WNDR
3700 from Netgear even though I did not yet have dual band adapters.

When I bought a new laptop I reasonably expected the wireless adapter
I had just bought to work. After all both the Microsoft Win7
compatibility and D-Link web sites said it was supported.