D865PERL: network still works with "no adapter"

[Beemer Biker]

We have lost our "local area network" if we ever had it. Nothing shows up
in the network connections popup. Bringing up System - Network Adapters in
control panel shows no adapter present. If I click on "show hidden items"
then the Intel Pro/100 VE miniport shows up. This does not seem to the
built in ethernet not to function. It works perfectly, in fact it worked
for for about a year and we never knew we had a problem until XP Pro Service
pack 2 went in and the firewall got enabled. It blocked all access to the
computer and "shared files" on this system were no longer accessible. When
I went to the firewall panel and looked at exclusions, "local area network"
was not available. When I started backtracking I discovered the "Pro/100"
chipset was not listed under network adapters unless I enable "hidden
items".

I downloaded and re-installed...

latest bios from intel
latest chipset inf
latest network drivers
latest audio drivers

All driver upgrades say i am using the most current. I cannot get that
"Pro/100 VE" chipset to show up. If a force on in using "Add Hardware" it
shows up as local area connection #2 and has that yellow bang. Clearly,
something in the registery has gotten corrupted. I got into regedit and
poked around and found about 18 network devices including that 2nd non
working "Pro/100 VE". If I uninstall the one I forced in, the count goes
down to 17 so I know I am close to where the problem is. I do no know
enough about the registery and what those entries are. Anybody got any
suggestions?

FWIW, on a hunch I added a spare 3com ethernet adapter. It worked just
fine, but same problem...it does not show up as a network connection.

 

[Bob Bailin]

We have lost our "local area network" if we ever had it. Nothing shows up
in the network connections popup. Bringing up System - Network Adapters in
control panel shows no adapter present. If I click on "show hidden items"
then the Intel Pro/100 VE miniport shows up. This does not seem to the
built in ethernet not to function. It works perfectly, in fact it worked
for for about a year and we never knew we had a problem until XP Pro Service
pack 2 went in and the firewall got enabled. It blocked all access to the
computer and "shared files" on this system were no longer accessible. When
I went to the firewall panel and looked at exclusions, "local area network"
was not available. When I started backtracking I discovered the "Pro/100"
chipset was not listed under network adapters unless I enable "hidden
items".

I downloaded and re-installed...

latest bios from intel
latest chipset inf
latest network drivers
latest audio drivers

All driver upgrades say i am using the most current. I cannot get that
"Pro/100 VE" chipset to show up. If a force on in using "Add Hardware" it
shows up as local area connection #2 and has that yellow bang. Clearly,
something in the registery has gotten corrupted. I got into regedit and
poked around and found about 18 network devices including that 2nd non
working "Pro/100 VE". If I uninstall the one I forced in, the count goes
down to 17 so I know I am close to where the problem is. I do no know
enough about the registery and what those entries are. Anybody got any
suggestions?

FWIW, on a hunch I added a spare 3com ethernet adapter. It worked just
fine, but same problem...it does not show up as a network connection.

Amazingly enough, I ran into this same problem last week when I attempted
to remove an XP SP1 hotfix in Add/Remove Programs that was not
automatically removed when I had installed SP2 a couple of months ago.
I ignored the warning about the software that was installed after the patch
I was trying to remove, and in the process, hosed my networking connections
completely. In my case, the onboard Intel VE adapter still showed up in
Device Manager, but when I uninstalled in and redetected it, again
nothing appeared under Network Connections.

I didn't have a WinXP SP2 CD handy to attempt a repair installation, so
my next best guess was to remove SP2, after first removing all of the
patches I had applied since installing SP2. At some point, the proper
networking driver was restored and I had my network back again. In
this particular case, networking was restored after removing one of the
post-SP2 patches, so I probably didn't have to remove and reinstall
Service Pack 2, but did so anyways just to be sure nothing else was
mucked up.

Bob

 

[Beemer Biker]

Amazingly enough, I ran into this same problem last week when I attempted
to remove an XP SP1 hotfix in Add/Remove Programs that was not
automatically removed when I had installed SP2 a couple of months ago.
I ignored the warning about the software that was installed after the patch
I was trying to remove, and in the process, hosed my networking connections
completely. In my case, the onboard Intel VE adapter still showed up in
Device Manager, but when I uninstalled in and redetected it, again
nothing appeared under Network Connections.

I didn't have a WinXP SP2 CD handy to attempt a repair installation, so
my next best guess was to remove SP2, after first removing all of the
patches I had applied since installing SP2. At some point, the proper
networking driver was restored and I had my network back again. In
this particular case, networking was restored after removing one of the
post-SP2 patches, so I probably didn't have to remove and reinstall
Service Pack 2, but did so anyways just to be sure nothing else was
mucked up.

Bob

Uninstalled SP2, didnt make a difference. The adapters didnt show up in
device manager, no network connections were listed yet the network still
worked (but not for long). I decided to re-install XP and copied the two
wpa files to a floppy so I would not have to reactivate. I put in the
original XP cd, with service pack "0" and tried booting but forgot I had
replaced the original EIDE disk with a true SATA about a year ago and
service pack "0" does not support SATA. I then ran the original XP cd
directly as un upgrade app thinking that would work. It seem to go fine
until the reboot when I got 100's of "entry point GetIUMS not found in
msdart.dll" I had to click on every one of those error messages with the
mouse to finish the install. All further reboots failed and I had no other
computer with an SATA interface to get access to the hosed drive.

I went here http://www.nu2.nu/pebuilder/ and downloaded and built Bart's
slipstreamed XP repair disk using my original XP CD and that microsoft SP2
download. I was able to boot and replaced the msdart.dll with a newer one
but it was too late, the original "upgrade" would not resume and I was
forced to do a new install overwriting windows. It finally booted and I am
back in business althought I still had to re-activate. XP would not accept
those two wpa. files for some reason, but the internet activation worked
fine and I managed to locate the original office 2000 disks but I am still
looking for other crap that used to be there. This was a real learning
experience and I posted what I did in case somebody else runs into this
problem.