Screwed up LAN bindings - (Difficult)

A

Atlas

1) My system is working
2) Suddenly, dunno why, when looking at the Local Area Connection Properties
data is incomplete, not showing the current adapter description, not showing
the protocols (I had Commview and vmware protocols binded apart from
TCP-IP), showing only the clients (file sharing & client for msnet.)
3) Recently added a FireWire adapter, showed in network adapters in the
device manager (see config below)
4) To see if it could help to show missing data, tried to swap PCI slots,
but XP couldn't setup properly drivers with error code 31 or 1 and driver
update wizard stating "couldn't fine the file specified" (see below
setupapi.log)
5) Unistalled Commview and Vmware to see if removing protocols and
rebuilding bindings could help, no result.
6) I've put the FireWire and the NIC adapter backi in their original PCI
slots, it works again
7) Again not showing correctly LAN/Adapter/Protocols properties

Any hint?

*********************************
My cfg:
- Mobo: ASUS CUSL2-C (ACPI Bios rev 1009,02/27/2001-I815-CUSL2-C-00, Bios
Award medallion 6.0, Award Bios ext.1.0A)
- Bios Settings: Legacy USB=Enabled, PNP OS=Yes
- CPU: P3-933 (No overclock)
- RAM: (1x256@133) + (1x128@133) = 392@133
- VGA: Creative TNT 2 Ultra Bios v. 2.05.2.11
- Audio: Creative SoundBlaster Live! 1024
- SCSI: Adaptec AHA2940UW Bios v. 1.21
- Mouse: Microsoft Intellimouse Optical USB, Logitech First Wheel Mouse USB
- Keyb: Logitech DeLuxe PS/2
- NIC: 3com 3C905CX-TX-M
- Mass Storage: Adaptec DuoConnect AUA-3121 (1394 + USB 2)
- Windows XP Pro + SP1 + Windows Updates to this date
- Norton Antivirus 2004 Pro
**********************************

setupapi.log:
r.
[2003/09/17 10:57:06 3496.2]
#-199 Executing "C:\2000\system32\rundll32.exe" with command line:
rundll32.exe newdev.dll,ClientSideInstall
\\.\pipe\PNP_Device_Install_Pipe_0.{BDBD5682-38B9-4CC1-A4F0-6F6FB10C3BBA}
#I060 Set selected driver.
#-019 Searching for hardware ID(s):
pci\ven_10b7&dev_9200&subsys_100010b7&rev_74,pci\ven_10b7&dev_9200&subsys_10
0010b7,pci\ven_10b7&dev_9200&cc_020000,pci\ven_10b7&dev_9200&cc_0200
#-018 Searching for compatible ID(s):
pci\ven_10b7&dev_9200&rev_74,pci\ven_10b7&dev_9200,pci\ven_10b7&cc_020000,pc
i\ven_10b7&cc_0200,pci\ven_10b7,pci\cc_020000,pci\cc_0200
#W383 "netel90b.PNF" migrate: PNF Language = 0409, Thread = 0410.
#I022 Found "PCI\VEN_10b7&DEV_9200&SUBSYS_100010B7" in
C:\2000\inf\netel90b.inf; Device: "3Com EtherLink XL 10/100 PCI For Complete
PC Management NIC (3C905C-TX)"; Driver: "3Com EtherLink XL 10/100 PCI For
Complete PC Management NIC (3C905C-TX)"; Provider: "Microsoft"; Mfg: "3Com";
Section name: "EL90BC.905CTX.NDI".
#I023 Actual install section: [EL90BC.905CTX.NDI]. Rank: 0x00000001.
Effective driver date: 07/01/2001.
#I022 Found "PCI\VEN_10b7&DEV_9200" in C:\2000\inf\netel90b.inf; Device:
"3Com 3C920 Integrated Fast Ethernet Controller (3C905C-TX Compatible)";
Driver: "3Com 3C920 Integrated Fast Ethernet Controller (3C905C-TX
Compatible)"; Provider: "Microsoft"; Mfg: "3Com"; Section name:
"EL90BC.905CTX.NDI".
#I023 Actual install section: [EL90BC.905CTX.NDI]. Rank: 0x00002001.
Effective driver date: 07/01/2001.
#W383 "oem4.PNF" migrate: PNF Language = 0409, Thread = 0410.
#I022 Found "PCI\VEN_10b7&DEV_9200&SUBSYS_100010B7" in C:\2000\inf\oem4.inf;
Device: "3Com EtherLink 10/100 PCI For Complete PC Management NIC
(3C905C-TX)"; Driver: "3Com EtherLink 10/100 PCI For Complete PC Management
NIC (3C905C-TX)"; Provider: "3Com"; Mfg: "3Com"; Section name:
"PCIEL905CTXM.ndi".
#I023 Actual install section: [PCIEL905CTXM.ndi.NT]. Rank: 0x00000001.
Effective driver date: 08/01/2000.
#I022 Found "PCI\VEN_10b7&DEV_9200" in C:\2000\inf\oem4.inf; Device: "3Com
3C920 Integrated Fast Ethernet Controller (3C905C-TX Compatible)"; Driver:
"3Com 3C920 Integrated Fast Ethernet Controller (3C905C-TX Compatible)";
Provider: "3Com"; Mfg: "3Com"; Section name: "PCIEL905CTXM.ndi".
#I023 Actual install section: [PCIEL905CTXM.ndi.NT]. Rank: 0x00002001.
Effective driver date: 08/01/2000.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [EL90BC.905CTX.NDI] in
"c:\2000\inf\netel90b.inf".
#I320 Class GUID of device remains: {4D36E972-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of
"PCI\VEN_10B7&DEV_9200&SUBSYS_100010B7&REV_74\4&2B96F39&0&48F0".
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#W383 "layout.PNF" migrate: PNF Language = 0409, Thread = 0410.
#-011 Installing section [EL90BC.905CTX.NDI] from
"c:\2000\inf\netel90b.inf".
#W383 "drvindex.PNF" migrate: PNF Language = 0409, Thread = 0410.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [EL90BC.905CTX.NDI.Interfaces] from
"c:\2000\inf\netel90b.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of
"PCI\VEN_10B7&DEV_9200&SUBSYS_100010B7&REV_74\4&2B96F39&0&48F0".
#I121 Device install of
"PCI\VEN_10B7&DEV_9200&SUBSYS_100010B7&REV_74\4&2B96F39&0&48F0" finished
successfully.
#E154 Class installer failed. Error 2: The system cannot find the file
specified.
 
A

Atlas

Anyone willing to measure up with it????

Atlas said:
1) My system is working
2) Suddenly, dunno why, when looking at the Local Area Connection Properties
data is incomplete, not showing the current adapter description, not showing
the protocols (I had Commview and vmware protocols binded apart from
TCP-IP), showing only the clients (file sharing & client for msnet.)
3) Recently added a FireWire adapter, showed in network adapters in the
device manager (see config below)
4) To see if it could help to show missing data, tried to swap PCI slots,
but XP couldn't setup properly drivers with error code 31 or 1 and driver
update wizard stating "couldn't fine the file specified" (see below
setupapi.log)
5) Unistalled Commview and Vmware to see if removing protocols and
rebuilding bindings could help, no result.
6) I've put the FireWire and the NIC adapter backi in their original PCI
slots, it works again
7) Again not showing correctly LAN/Adapter/Protocols properties

Any hint?

*********************************
My cfg:
- Mobo: ASUS CUSL2-C (ACPI Bios rev 1009,02/27/2001-I815-CUSL2-C-00, Bios
Award medallion 6.0, Award Bios ext.1.0A)
- Bios Settings: Legacy USB=Enabled, PNP OS=Yes
- CPU: P3-933 (No overclock)
- RAM: (1x256@133) + (1x128@133) = 392@133
- VGA: Creative TNT 2 Ultra Bios v. 2.05.2.11
- Audio: Creative SoundBlaster Live! 1024
- SCSI: Adaptec AHA2940UW Bios v. 1.21
- Mouse: Microsoft Intellimouse Optical USB, Logitech First Wheel Mouse USB
- Keyb: Logitech DeLuxe PS/2
- NIC: 3com 3C905CX-TX-M
- Mass Storage: Adaptec DuoConnect AUA-3121 (1394 + USB 2)
- Windows XP Pro + SP1 + Windows Updates to this date
- Norton Antivirus 2004 Pro
**********************************

setupapi.log:
r.
[2003/09/17 10:57:06 3496.2]
#-199 Executing "C:\2000\system32\rundll32.exe" with command line:
rundll32.exe newdev.dll,ClientSideInstall
\\.\pipe\PNP_Device_Install_Pipe_0.{BDBD5682-38B9-4CC1-A4F0-6F6FB10C3BBA}
#I060 Set selected driver.
#-019 Searching for hardware ID(s):
pci\ven_10b7&dev_9200&subsys_100010b7&rev_74,pci\ven_10b7&dev_9200&subsys_10
0010b7,pci\ven_10b7&dev_9200&cc_020000,pci\ven_10b7&dev_9200&cc_0200
#-018 Searching for compatible ID(s):
pci\ven_10b7&dev_9200&rev_74,pci\ven_10b7&dev_9200,pci\ven_10b7&cc_020000,pc
i\ven_10b7&cc_0200,pci\ven_10b7,pci\cc_020000,pci\cc_0200
#W383 "netel90b.PNF" migrate: PNF Language = 0409, Thread = 0410.
#I022 Found "PCI\VEN_10b7&DEV_9200&SUBSYS_100010B7" in
C:\2000\inf\netel90b.inf; Device: "3Com EtherLink XL 10/100 PCI For Complete
PC Management NIC (3C905C-TX)"; Driver: "3Com EtherLink XL 10/100 PCI For
Complete PC Management NIC (3C905C-TX)"; Provider: "Microsoft"; Mfg: "3Com";
Section name: "EL90BC.905CTX.NDI".
#I023 Actual install section: [EL90BC.905CTX.NDI]. Rank: 0x00000001.
Effective driver date: 07/01/2001.
#I022 Found "PCI\VEN_10b7&DEV_9200" in C:\2000\inf\netel90b.inf; Device:
"3Com 3C920 Integrated Fast Ethernet Controller (3C905C-TX Compatible)";
Driver: "3Com 3C920 Integrated Fast Ethernet Controller (3C905C-TX
Compatible)"; Provider: "Microsoft"; Mfg: "3Com"; Section name:
"EL90BC.905CTX.NDI".
#I023 Actual install section: [EL90BC.905CTX.NDI]. Rank: 0x00002001.
Effective driver date: 07/01/2001.
#W383 "oem4.PNF" migrate: PNF Language = 0409, Thread = 0410.
#I022 Found "PCI\VEN_10b7&DEV_9200&SUBSYS_100010B7" in C:\2000\inf\oem4.inf;
Device: "3Com EtherLink 10/100 PCI For Complete PC Management NIC
(3C905C-TX)"; Driver: "3Com EtherLink 10/100 PCI For Complete PC Management
NIC (3C905C-TX)"; Provider: "3Com"; Mfg: "3Com"; Section name:
"PCIEL905CTXM.ndi".
#I023 Actual install section: [PCIEL905CTXM.ndi.NT]. Rank: 0x00000001.
Effective driver date: 08/01/2000.
#I022 Found "PCI\VEN_10b7&DEV_9200" in C:\2000\inf\oem4.inf; Device: "3Com
3C920 Integrated Fast Ethernet Controller (3C905C-TX Compatible)"; Driver:
"3Com 3C920 Integrated Fast Ethernet Controller (3C905C-TX Compatible)";
Provider: "3Com"; Mfg: "3Com"; Section name: "PCIEL905CTXM.ndi".
#I023 Actual install section: [PCIEL905CTXM.ndi.NT]. Rank: 0x00002001.
Effective driver date: 08/01/2000.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [EL90BC.905CTX.NDI] in
"c:\2000\inf\netel90b.inf".
#I320 Class GUID of device remains: {4D36E972-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of
"PCI\VEN_10B7&DEV_9200&SUBSYS_100010B7&REV_74\4&2B96F39&0&48F0".
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#W383 "layout.PNF" migrate: PNF Language = 0409, Thread = 0410.
#-011 Installing section [EL90BC.905CTX.NDI] from
"c:\2000\inf\netel90b.inf".
#W383 "drvindex.PNF" migrate: PNF Language = 0409, Thread = 0410.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [EL90BC.905CTX.NDI.Interfaces] from
"c:\2000\inf\netel90b.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of
"PCI\VEN_10B7&DEV_9200&SUBSYS_100010B7&REV_74\4&2B96F39&0&48F0".
#I121 Device install of
"PCI\VEN_10B7&DEV_9200&SUBSYS_100010B7&REV_74\4&2B96F39&0&48F0" finished
successfully.
#E154 Class installer failed. Error 2: The system cannot find the file
specified.



-------------------------------------------------------------------------- --
 
Joined
Nov 1, 2006
Messages
1
Reaction score
0
Please Help

Hi
more than 3 years later I have exactly the same Problem.
Did someone find a solution.
I would greatly appreciate any help.
 
Joined
Dec 5, 2006
Messages
1
Reaction score
0
I m' discovering the same problem and of course I'm trying to resolve it !!!
I 'm now in a worse case than yourself because I have done the error of thinking that by deleting the card in the device manager maybe it will make windows rediscover them and maybe windows could put all that stuff back correctly... That was a Wrong idea because now I have even lost access to the network.

So I' m writing on this forum from another machine :-(

Some ideas :
1) You are not alone. We are 2 at least ;-)
I've got this mess after a VMware player which was correctly installed asked me for an update . The update then uninstalled the first VMplayer and then said when I was trying to use Virtual machine Bridge Device 'VMnet0' Not Running
After that (maybe like you) I uninstalled the VMPlayer trying to put the older one and ... it didn't work. At those times I felt in the mess you described above....

2) #E154 Class installer failed. Error 2: The system cannot find the file specified
or in french (French PC means french errors so this message is for frenchies lurking on the web ; [highlight]Bienvenue au club ;-)[/highlight]
#E154 L'installateur de classe a échoué. Erreur 2: Le fichier spécifié est introuvable

To understand a little better what we have in SetupAPI.log, I've found a very interesting file to read named SetupAPIlog.doc from http://download.microsoft.com/download/e/b/a/eba1050f-a31d-436b-9281-92cdfeae4b45/SetupAPILog.doc

This file explain what we see but not enough

The file not found is unknown so we could try to find what file is lacking by using filemon ( regmon maybe too) to see what happens. Those tools can be found freely from sysinternals which is now in the microsoft bag;-) here http://www.microsoft.com/technet/sysinternals/default.mspx

I can do a try by deleting the card in the device manager again and using filemon, but you probably can't because you will lose your network access

3) probably you will have to look at :
How to reset Internet Protocol (TCP/IP) in Windows
http://support.microsoft.com/kb/299357/en-us (for XP)
Note that There is a downloadable guide which automatize the job in the US version !!! but Microsoft is too lazy to produce it in other languages or version
http://support.microsoft.com/kb/317518/en-us (Windows 2003)

Maybe it's interesting to have a look also to :
How to troubleshoot TCP/IP connectivity with Windows
http://support.microsoft.com/kb/314067/en-us (Windows XP)
http://support.microsoft.com/kb/102908/en-us (Windows 2000 and even Windows NT)

and to :
How to determine and recover from Winsock2 corruption
http://support.microsoft.com/kb/811259/en-us

If anybody have already done the job / has THE Answer / own THE Solution , please HELP. Reformat+ reinstall solution is of course forbidden ;-)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top