| | |
Ethernet Adapter problem?
![]() |
•
•
Join Date: May 2005
Posts: 7
Reputation:
Solved Threads: 0
Hey guys,
I'm having internet connection problems.
In network connections on a Win XP Home pc there is no listing for the Ethernet Adapter.
In device manager there is a listing for this adapter, but when you click on it you get this message.
"This device cannot find enough free resources that it can use." Code 12.
I ran the troubleshooter and when I went to IRQ's, to see if the adapter was listed twice, it was not listed at all.
Why would the ethernet adapter be listed in the device manager but not listed under IRQ's or any of the other resources?
This adapter is a Netgear adapter for a note book pc. Anybody have any suggestions as to how I can fix this so I can get my internet connection back?
Thank you,
john
I'm having internet connection problems.
In network connections on a Win XP Home pc there is no listing for the Ethernet Adapter.
In device manager there is a listing for this adapter, but when you click on it you get this message.
"This device cannot find enough free resources that it can use." Code 12.
I ran the troubleshooter and when I went to IRQ's, to see if the adapter was listed twice, it was not listed at all.
Why would the ethernet adapter be listed in the device manager but not listed under IRQ's or any of the other resources?
This adapter is a Netgear adapter for a note book pc. Anybody have any suggestions as to how I can fix this so I can get my internet connection back?
Thank you,
john
•
•
Join Date: Mar 2004
Posts: 1,620
Reputation:
Solved Threads: 51
Hello,
To my understanding, if the device driver failed to initialize properly, it should not necessairly consume any resources, such as using an IRQ or memory places.
My guess is that your driver is bad, and/or something upstream is bad, perhaps the PCMCIA drivers, or your chipset. I would remove the device driver, and check to make sure the subsystems are up to date too, and then re-install the network adapter.
Christian
To my understanding, if the device driver failed to initialize properly, it should not necessairly consume any resources, such as using an IRQ or memory places.
My guess is that your driver is bad, and/or something upstream is bad, perhaps the PCMCIA drivers, or your chipset. I would remove the device driver, and check to make sure the subsystems are up to date too, and then re-install the network adapter.
Christian
•
•
Join Date: May 2005
Posts: 7
Reputation:
Solved Threads: 0
kcOarf,
Thanks for that fast reply. You apparently mistook me for someone more knowledgeable.
Your reply went right over my head. But again, thanks.
This is what we did so far.
Went to the device manager and ran the "Hardware update wizard".
The wizard actually updated the driver and changed the name from, ADMtek AN985 to Netgear FA511.
Restarted and went back to device manager and the adapter still had the yellow exclamation point with the same message as before.
As to your reply, why would the device driver fail to initialize?
Also, could you please explain a little more about something upstream possibly being bad and the chipset.
Thanks a bunch,
John
Thanks for that fast reply. You apparently mistook me for someone more knowledgeable.
Your reply went right over my head. But again, thanks.
This is what we did so far.
Went to the device manager and ran the "Hardware update wizard".
The wizard actually updated the driver and changed the name from, ADMtek AN985 to Netgear FA511.
Restarted and went back to device manager and the adapter still had the yellow exclamation point with the same message as before.
As to your reply, why would the device driver fail to initialize?
Also, could you please explain a little more about something upstream possibly being bad and the chipset.
Thanks a bunch,
John
•
•
Join Date: Mar 2004
Posts: 1,620
Reputation:
Solved Threads: 51
Hello,
First, I need to disclaim that I have never run XP Home before, and my XP Pro / 2000 Pro ideas might not apply to XP Home.
A device driver would fail to initialize because the driver is calling upon hardware that doesn't exist, or is not configured properly. The device drivers are special pieces of code that expect certain components to be there in order to function.
Think of a computer that operates a traffic light. The computer turns the lights on -- red, yellow, green. The hardware is the lightbulb. The software is the program that turns on the light, and checks for power drain (a lit light draws power to make the shine, and gives off heat). If the lightbulb is missing, you don't have light, and there would not be a power drain. Software says there is a problem. Driver did not initialize properly.
Chipset drivers are a newer thing to motherboards, beyond what we call BIOS. Chipset drivers are used to configure special pieces of hardware and software on the motherboard. The chipset software controls things like the PCI bus, the floppy disk buss, memory management, maybe the parallel port, USB devices. You might need to go to motherboard manufacturer's website and download some software that will help your motherboard out.
What kind of network card do you have? Take a look at it. See if you can find the model number. Go to a website for the manufacture, and download the latest driver. Remove the one Windows thinks it is, and install the one you found that you know works with the card. Again, you might need to get the chipset going properly before the card itself (I have had to do this with some hot-off-the-press dells that we need to use WIndows 2000 with instead of XP. W2K has no idea what the components are in the new state-of-art boxes, and thus I needed to go and get the stuff to make it work).
Your system might have also come with a CD-ROM that has the materials all in one place.
WIthout knowing what you have here in front of me, it is hard for me to "drive" the repair. I hope you can find clues to help you along.
Christian
First, I need to disclaim that I have never run XP Home before, and my XP Pro / 2000 Pro ideas might not apply to XP Home.
A device driver would fail to initialize because the driver is calling upon hardware that doesn't exist, or is not configured properly. The device drivers are special pieces of code that expect certain components to be there in order to function.
Think of a computer that operates a traffic light. The computer turns the lights on -- red, yellow, green. The hardware is the lightbulb. The software is the program that turns on the light, and checks for power drain (a lit light draws power to make the shine, and gives off heat). If the lightbulb is missing, you don't have light, and there would not be a power drain. Software says there is a problem. Driver did not initialize properly.
Chipset drivers are a newer thing to motherboards, beyond what we call BIOS. Chipset drivers are used to configure special pieces of hardware and software on the motherboard. The chipset software controls things like the PCI bus, the floppy disk buss, memory management, maybe the parallel port, USB devices. You might need to go to motherboard manufacturer's website and download some software that will help your motherboard out.
What kind of network card do you have? Take a look at it. See if you can find the model number. Go to a website for the manufacture, and download the latest driver. Remove the one Windows thinks it is, and install the one you found that you know works with the card. Again, you might need to get the chipset going properly before the card itself (I have had to do this with some hot-off-the-press dells that we need to use WIndows 2000 with instead of XP. W2K has no idea what the components are in the new state-of-art boxes, and thus I needed to go and get the stuff to make it work).
Your system might have also come with a CD-ROM that has the materials all in one place.
WIthout knowing what you have here in front of me, it is hard for me to "drive" the repair. I hope you can find clues to help you along.
Christian
![]() |
Similar Threads
- Added an Ethernet Adapter Card (NIC), but no LAN! (PCI and Add-In Cards)
- Two PCI Ethernet Adapter(s) Problem on Win Fund. LPC (XPSP2) (PCI and Add-In Cards)
- driver adapter problem (PCI and Add-In Cards)
- HELP!!!!!!!! ATEN Usb to Ethernet Adapter (PCI and Add-In Cards)
Other Threads in the Windows NT / 2000 / XP Forum
- Previous Thread: Standby option has changed since BIOS upgrade
- Next Thread: Red Square., PICTURES not Showing Win XP
| Thread Tools | Search this Thread |
.net 3.5 3daccelertion 64bit 2010 activedirectory alaris android application arm auto black blue book bsod canonical cellphones chinese codeplex collaboration combofix computer computerfreezes crash deployments desktop desktops domain dotnetnuke drive error errors explorer fax folder fonts freeze gadgets hardware home intel killprocess laptop laptops latitude lcd linux load mac markshuttleworth memory microsoft minimalizes mobile monitor netbooks opensource operatingsystems options oracle osinstallationproblem outlook partition patch port product program proxy raid rds reformat remotedesktopconnection retail screen security server. slowperformance sp1 sp3 spyware studios ubuntu unreadable update upgrade usb verizon virtual virus vpn vulnerability wab webos weecam window windows windows7 windowsxp worm xp






