SCOUG-HELP Mailing List Archives
Return to [ 27 |
April |
2005 ]
>> Next Message >>
Content Type: text/plain
Hi Steven,
I don't know if you had a chance to look at the rmb USB Mgr. device readout stuff I sent
you, but there have been some new developments. While on my recent trip, I tried to get
the D-Link Airplus G120 wireless USB nic working under W2K, but could not -- despite two 20
min. sessions on the phone with their Tech Support. The last thing they told me was to d/l
a later driver than what was on the install CD, uninstall the old driver, and replace it
with the new. Actually, it is way more than a driver, as it includes a configuration /
monitoring / control utility that goes onto both the Win desktop and the systray. Well,
let me tell you, that is one persistent, pernicious little bugger. You can't remove it
with dynamite, even in "Safe" mode. Attempts to get rid of it just hang one process or
another, interminably. As such, it joins the Rogue's Gallery of indestructible Win items,
along with the ScanSoft suites and intractable remnants of Symantec AV. [Reason #146 why I
despise Windoze. This crap just doesn't happen on our turf.] I'm going to try to roll
back the Registry and kill all the D-Link files & folders from the other W2K boot
partition. Hopefully that will be sufficient, but I gather it may not be. Under the
circumstances, I'm very disinclined to give the later version driver a turn at bat, no
matter what else happens.
A couple days later, I had a chance to discuss this with a very experienced consultant (who
only does Win), and he told me that: 1) D-Link wireless NICs are pretty good at connecting
with a D-Link wireless router, but pretty lousy at connecting with anyone else's router.
The wireless router at this location was not a D-Link. & 2) A lot of D-Link installed
software works this way -- like a tick that attaches itself and just won't let go. For
that reason, he avoids their wireless gear, and advises his clients to do the same.
Why am I mentioning this here ? In case anyone is about to make a buying decision of this
type. I'm going to see what's up with Linksys, which the consultant recommended -- esp. in
regard to researching the chipsets. The main reason I bought this particular USB nic was
that it has a somewhat later version of the Prism chipset, which turned up on that list for
(*potential*) eCS wireless driver support. Before I toss the D-Link though, I had a
question for you. Let's say it's possible to follow a project like the one pursued by
Mark, for this device, and the end result is a viable driver. Our drivers, even for the
same device, in no way behave in this manner . . . where they're sucking up a lot of CPU
cycles and you just can't pry them loose . . . right ? Even if there could be an eCS
driver, there won't be any monitoring or control utility for eCS, and I probably won't be
able to use it on the Dark Side. I'm just wondering if this is even worth pursuing.
Jordan
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"postmaster@scoug.com".
=====================================================
>> Next Message >>
Return to [ 27 |
April |
2005 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
|
