I'm amazed. How do these nutjobs do this? Here's the rundown: Dell D610 with Windows XP. Two NICs: Broadcom NetXtreme 57xx GBit Dell Wireless 1450 Dual-Band Mini-PCI Card
The Wireless Card itself is AWOL in the device manager... but it's PACKET SCHEDULER is reporting in as a 3COM 3C902. ...What?
Using a different hard drive of a same-model system, the Wireless tests good. Unfortunately, the user is adamant that we don't wipe and rewrite. Custom software and all. *shrug* So, my guess is, if we delete the old driver, we can install the new. But the packet scheduler doesn't want to die. Any ideas, y'all?
This conversation is currently closed to new comments.
is loading a piece of "firmware" into the card and thus preventing it from dying as well as representing its self as 3com (which it very well could be, since Dell farms all that out). Log in as an admin user, add/remove all software for the wireless card. Remove it from device manager. Reboot, install new driver. Any result? What happens if you just try to install the new driver over the old?
If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.
Need to remove incorrect Packet Scheduler device
Dell D610 with Windows XP.
Two NICs:
Broadcom NetXtreme 57xx GBit
Dell Wireless 1450 Dual-Band Mini-PCI Card
The Wireless Card itself is AWOL in the device manager... but it's PACKET SCHEDULER is reporting in as a 3COM 3C902.
...What?
Using a different hard drive of a same-model system, the Wireless tests good. Unfortunately, the user is adamant that we don't wipe and rewrite. Custom software and all. *shrug* So, my guess is, if we delete the old driver, we can install the new. But the packet scheduler doesn't want to die. Any ideas, y'all?