Knight <(E-Mail Removed)> wrote:
> Jeff & D, it's a Gateway and yes Fn+ f2 starts and stops the
> wirelss adpater which DOES work. Windows XP by the way....
> The Buffalo adpater also works just fine!
> That's really rude dude!
Take the knowledge, and adjust your humor detector to something that
includes, or ignores, Jeff's level of side notes.
> If I uninstall the Buffalo adpater drivers then I get my internal to
> work but it seems like I can't turn on the internal as long as I have
> the Buffalo drivers on the machine.
The internal works. Turn off the internal, and the external works.
Plug in the external, enable the internal, and neither works.
Unplug the external and the internal still doesn't work, until... what?
What do you have to do to get the internal to work? Uninstall the buffalo
drivers? Not just remove the card and reboot? When you uninstall the
Buffalo drivers, does the internal card start working right away, or after
a reboot? Does it reinstall drivers for the internal card?
Same named driver, different rev, perhaps?
Does IPConfig ever show both NICs? What about device manager?
Do you know what card the internal is? I see an Intel 3945 listed for some
Gateways. start-run-msinfo32 network adapter might let you know.
The MAC address, Device ID, service name, or driver name might be clues.
Or the FCC-ID, on a label on the bottom of the laptop.
Jeff will probably ask for the FCC-ID of the Buffalo and the internal, just
so he can find out what they really are... retail package names aren't that
interesting. You could ignore him, but I don't ;-)
--
Clarence A Dold - Hidden Valley Lake, CA, USA GPS: 38.8,-122.5
|