Winnt\sys32\config\systemCED Error

  • Thread starter Thread starter ColTom2
  • Start date Start date
ColTom2 wrote:

* Do you have any idea how I could identify the Adapter so I could
obtain an appropriate driver for it? Never had this problem before.........*
**
* Again without your help I would never have gotten her operating
system back up. Thanks again for all your professional help and if you
have any idea as to what I can do now please advise me accordingly.*
**
Click to expand...

Just a suggestion. You will need to remove the adaptor card from the PC.
Make sure you are grounded first before handling it, and do not touch
any of the chips on it or the connectors (where it connects in to the
PCI slot), ie handle card only at its edges if possible. There are a
series of numbers and letters imprinted on the card, which identify it.
You may even see a manufactures's name on the card or on the chips. Make
an accurate note of these serial numbers/letters. Then google for them.
You should come up with the actual manufacurer and model of the card.
Then go to their site and download the driver. Then replace the card
back in its slot.
 
Thank you for the follow up. I see you had to go the full nine yards to
get things back up, sometimes that's how it goes. In the end it's
probably for the best, she has a new stable installation.

Frank has given you an answer to the NIC identification problem, quite
often that is the easiest way to do it. Sometimes it can be quite
difficult to properly identify these devices, especially if they are
from a lesser known vendor. Sometimes for the sake of a $20 to $30
device I find that it's not worth the hassle and I just buy a new card.
Here is another way that you can try to identify the NIC card.

Have your friend go here: http://support.microsoft.com/kb/311272/ and
download DevCon. Have her put the 32 bit devcon version in her
\winnt\system32 folder.

Have her start a Command Prompt (Start > Run > cmd). At the command
prompt have her enter the following command:

devcon hwids =net >c:\nic.txt

Now have her find the file nic.txt at C:\ and tell her to email it to you.

In the file you should find something that looks like this:

PCI\VEN_10B7&DEV_9200&SUBSYS_00C71028&REV_78\4&BB7B4AE&0&60F0

Go here: http://www.pcidatabase.com/index.php

and search for the vendor. The vendor number is typically like so:


PCI\VEN_ 10B7 &DEV_9200&SUBSYS_00C71028&REV_78....
This is the # ^^^^

In this case you would search for vendor ID 10B7


To search for the device:

PCI\VEN_10B7&DEV_ 9200 &SUBSYS_00C71028&REV_78\....
This is the device ^^^^

Search for device 0x9200

The device search may yield results from different vendor, so it's
important to search on the vendor first. From there you can go to the
manufacturer's web site and find the proper drivers, that failing do a
search for the drivers on the net.

You can also get the information on the vendor and device by using the
msinfo32 tool ( Start > Run > msinfo32) and selecting the proper
"Components" branch. From there the information can be saved to a text
file.

Regards

John
 
Hi John and Frank:

I went back over this morning with some new Dell info and got the network adapter driver installed properly, so that cleared that up. I just had a lapse in memory about the Other Devices Network Adapter, as had I been thinking I should have known this was causing a conflict problem etc.

I removed a wireless card that she had installed and this of course resolved that problem and now everything is working fine with no conflicts and able to access to internet etc. She will now have to reinstall the wireless card and install the appropriate LinkSys driver and this will again allow her wireless to work.

John I did as you recommended and installed the W2K SP4 and also the Rollup 1 for it. She now has all the outstanding Windows Updates installed, so for all practical purposes she is back in business.

Also John, as I have stated before, I never would have gotten off the ground with Win2K system had it not been for you and many many thanks to you!

God's Blessings,

ColTom2


Thank you for the follow up. I see you had to go the full nine yards to
get things back up, sometimes that's how it goes. In the end it's
probably for the best, she has a new stable installation.

Frank has given you an answer to the NIC identification problem, quite
often that is the easiest way to do it. Sometimes it can be quite
difficult to properly identify these devices, especially if they are
from a lesser known vendor. Sometimes for the sake of a $20 to $30
device I find that it's not worth the hassle and I just buy a new card.
Here is another way that you can try to identify the NIC card.

Have your friend go here: http://support.microsoft.com/kb/311272/ and
download DevCon. Have her put the 32 bit devcon version in her
\winnt\system32 folder.

Have her start a Command Prompt (Start > Run > cmd). At the command
prompt have her enter the following command:

devcon hwids =net >c:\nic.txt

Now have her find the file nic.txt at C:\ and tell her to email it to you.

In the file you should find something that looks like this:

PCI\VEN_10B7&DEV_9200&SUBSYS_00C71028&REV_78\4&BB7B4AE&0&60F0

Go here: http://www.pcidatabase.com/index.php

and search for the vendor. The vendor number is typically like so:


PCI\VEN_ 10B7 &DEV_9200&SUBSYS_00C71028&REV_78....
This is the # ^^^^

In this case you would search for vendor ID 10B7


To search for the device:

PCI\VEN_10B7&DEV_ 9200 &SUBSYS_00C71028&REV_78\....
This is the device ^^^^

Search for device 0x9200

The device search may yield results from different vendor, so it's
important to search on the vendor first. From there you can go to the
manufacturer's web site and find the proper drivers, that failing do a
search for the drivers on the net.

You can also get the information on the vendor and device by using the
msinfo32 tool ( Start > Run > msinfo32) and selecting the proper
"Components" branch. From there the information can be saved to a text
file.

Regards

John
 
Back
Top