Posted 08 March 2012 - 01:57 PM
You only wanted me to back up the registry ie net start afd was not running, correct?
Posted 08 March 2012 - 02:09 PM
If it still needs you to start it manually then you need to reset TCPIP. You want to back up the registry before you remove tcpip so that if it won't work you can back up to the last registry.
Posted 08 March 2012 - 03:39 PM
I am sorry but I do understand what you mean when you say "If afd is running on its own right after a reboot then you don't need to do anything more". Does this mean my computer is fixed? Even though the internet does not work w/o going into the command prompt. I heard back up your registry many times but to be honest I do not know what that does. Can you please explain this to me.
Thanks so much for your help.
Edited by Steven Gottlieb, 08 March 2012 - 03:39 PM.
Posted 08 March 2012 - 04:06 PM
Here is some additional information which might help you. I started the computer and no internet. I went to cp and typed in sc query afd and it said it was running. I left the computer running for a few minutes and observed that the 'two computers' in the lower right corner appeared and was 'acquiring network address' with sent/received packets both 0. I waited a few more minutes (no changes) and then typed in net start dhcp in cp and got internet.
I hope this helps. I see that you are having a hard time with this one.
Thanks for trying so hard!
Posted 08 March 2012 - 04:41 PM
(Reboot and when you see the maker's logo, hear a beep or it talks about F8, start tapping the F8 key slowly. Keep tapping until the Safe Mode Menu appears and choose Safe Mode with Networking. Login with your usual login.)
This keeps a lot of other stuff from running so things might boot faster. Can you get on line without the command line stuff?
If not then I think we need to go ahead and try the tcpip reset:
reinstall tcpip. Usually this works fine but I did have one case where it deleted OK but would not reinstall and we had to reload XP. That's why I now call for a registry backup before trying it.
Do you have the file:
IF so. Back up your registry:
Then see if you can follow the steps in the Hardcore method when nothing else is working section on
Posted 08 March 2012 - 04:57 PM
Same thing with safe.
The wife and I are going out for a bit so I'll look into backing up the registry in a few hours.
Posted 08 March 2012 - 08:52 PM
WOW, backing up the registry was very simple.
Now the hardcore method is a bit different. I'd truly appreciate it if you could help me understand step 1 and 2, please.
1. Locate the Nettcpip.inf file in %winroot%\inf, and then open the file in Notepad.
2. Locate the [MS_TCPIP.PrimaryInstall] section.
Posted 08 March 2012 - 09:40 PM
Bad news, I followed the instructions but still no internet. Any other ideas?
Posted 09 March 2012 - 12:04 AM
After we ran reset2.cmd and reset TCPIP I don't think we went back and tried to delete the Network Adapters again. Let's try that:
Right click on My Computer and select Manage then View , Show Hidden Devices then under Network Adapters try to right click and delete each one.
Are they still claiming they are needed to boot?
Posted 09 March 2012 - 06:46 PM
Same error as before-they are needed to boot.
eMachine model EL1352G
I have a wired connection to the internet
Edited by Steven Gottlieb, 09 March 2012 - 06:48 PM.
Posted 09 March 2012 - 07:59 PM
Windows keeps a Device Manager entry for every piece of hardware that's ever
been recognized by the system, regardless of whether it is currently present in the
machine or was even set up correctly in the first place. The "View Hidden Devices"
option in Device Manager won't show you these "residual" drivers.
You can force it to show you everything by going to My Computer Properties, the Advanced
tab, Environment Variables, and adding a new system variable with the name "DEVMGR_SHOW_NONPRESENT_DEVICES"
and a value of 1. Now opening Device Manager and choosing "Show Hidden Devices" really
will show you everything.
Standard practice at the factory is to use a single image and just move it from model
to model, letting it plug and play all the new hardware along the way.
This leaves you with an impressive list of hardware still in the Device Manager,
but no longer in the system. You also see this to a lesser degree when you restore
a system from an image you created for backup purposes. These "residual" drivers
can sometimes cause all kinds of weirdness and are best removed by right-clicking
on their entry in the Device Manager and choosing "uninstall"
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users