Re: Winnt\sys32\config\systemCED Error



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

ColTom2 wrote:

*Hi John:*
** * Well you cannot believe what happened. I tried the repair procedures 2 or 3 times and never could get a good repair, as it always went back to that same original error. I did have to change the BIOS boot settings.*
** * Finally did the complete reinstall, although the instructions for it was not all that great. Felt real good at this point; however, when I tried to connect to the internet with Comcast (Broadband) I could not get it to connect. Opened Device Manager up and there were five items with the big yellow question mark. Checked these out and the reason was none had divers and she could not find a CD with appropriate drivers on it. Called Dell and got a tech to give me the specific drivers that I needed over the phone and downloaded them to my laptop and burned a CD for installation.*
** * All driver installations went well except for the last which was for Network Adapters (Ethernet etc). The tech said that the computer was shipped with a CNET adapter and I tried all CNET drivers, but none worked. Apparently she had someone work on the computer and they replaced the CNET adapter and I have no idea how to determine the adapter and corresponding drivers.*
** * The computer is completely restored back to full working order except for this, which was somewhat upsetting to say the least.*
** * 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.*
** *ColTom2*

"John John" <audetweld@xxxxxxxxxxx <mailto:audetweld@xxxxxxxxxxx>>
wrote in message news:%23si2f1m7GHA.3280@xxxxxxxxxxxxxxxxxxxxxxx
You're welcome and good luck. Just remember that unless the drive is
toast her data is almost surely all intact and recoverable. Keep your
cool, if things don't pan out you can salvage the data by other means
and reinstall Windows from scratch.

John

ColTom2 wrote:

> *Hi John:*
> **
> * Thanks and I will advise you tomorrow evening sometime as to how
> things went. Again I am most appreciative for all your timely
responses.*
> **
> *ColTom2*
>
> "John John" <audetweld@xxxxxxxxxxx
<mailto:audetweld@xxxxxxxxxxx> <mailto:audetweld@xxxxxxxxxxx>>
> wrote in message news:%230BtYnm7GHA.5020@xxxxxxxxxxxxxxxxxxxxxxx
> Chkdsk will run from the Recovery Console. You can still get
security
> updates for Windows 2000 by using Internet Explorer and going
to the
> Windows update site. Microsoft will issue security fixes and
updates
> for Windows 2000 until about mid 2010.
>
> John
>
> ColTom2 wrote:
>
> > *Hi John:*
> > **
> > * If the system does not want to boot, as mentioned in
your last
> > paragraph, then how can I run chkdsk /r at this time?*
> > **
> > * Also is Windows 2000 still supported by Microsoft with
Windows
> > Updates or has support for this system been discontinued?*
> > **
> > *Thanks,*
> > **
> > *ColTom2*
> >
> > "John John" <audetweld@xxxxxxxxxxx
<mailto:audetweld@xxxxxxxxxxx>
> <mailto:audetweld@xxxxxxxxxxx> <mailto:audetweld@xxxxxxxxxxx>>
> > wrote in message
news:e2FqXVm7GHA.3396@xxxxxxxxxxxxxxxxxxxxxxx
> > First thing to do is to boot the computer and see if
you can
> launch the
> > Recovery Console and access the Windows 2000
installation.
> Then see if
> > you can do the repairs without doing the chkdsk. If
you see
> that you
> > can copy, rename and delete the files then the chkdsk
should
> not be
> > necessary, don't do it unless you have to. When I
approach these
> > computer problems I always take the "if it ain't broke
don't
> fix it"
> > attitude, do the necessary minimum to get things back to
> normal. Once
> > the installation boots up properly then I think it
would be a
> good idea
> > to do a chkdsk.
> >
> > Keep in mind that while you are in the Recovery
Console your
> access to
> > files and folders will (most likely) be restricted and
> limited. By
> > default you won't have permissions to most of the
files and
> folders on
> > the drive, that is a security feature of the Console. You
> will have
> > access to the root of any drive, such as C:\ as well
as the
> Windows
> > folder (\winnt) and the system32 folder
(\winnt\system32).
> You can use
> > the cd and dir commands to move around and explore but
> keep the
> > above in mind. If you or your friend want to see if other
> files are
> > still there, like in her "My Documents" folder, you
won't be
> able to
> > see
> > them. What you see and what is while you are in the
Console
> can be a
> > bit misleading, don't jump to conclusions.
> >
> > If, on the other hand, you are sure that you are properly
> logged on to
> > the Windows installation and can't rename, copy
between folder or
> > delete
> > files and are getting error messages, or if the "fixed"
> installation
> > doesn't want to boot, chances are that there is
corruption on
> the disk
> > and you will have to do the chkdsk to try to overcome the
> problem.
> >
> > John
> >
.



Relevant Pages

  • Re: Windows XP PRO Boot up problem
    ... I have bought this used laptop yesterday. ... the person I have bought it from has wiped all the software and drivers, ... By the way the OS is Windows XP PRO. ... it's a XP installation CD, as long you know it to be bootable. ...
    (microsoft.public.windowsxp.general)
  • Re: What?
    ... According to EA Support the game should work under Windows XP. ... As a last resort use the -nosound switch to disable the game sound. ... You can also try running the installation for the game using ... Update the drivers for your sound and video cards. ...
    (microsoft.public.windowsxp.games)
  • Re: printing
    ... To install USB device with Virtual PC: ... Installation or reinstallation of the USB printer: ... bar menus then tools then Windows Update. ... 2-1 It is necessary to download the last drivers and to install them. ...
    (microsoft.public.mac.virtualpc)
  • Re: FC5 and ATi x1300 follow-up
    ... So I uninstalled the two packages mentioned above, and downloaded and installed ATi's own Linux drivers. ... but i thought it is unnessesary because installation is to easy;-) ... reboot to load the new kernel ... That's something I wish would work more or less as advertised, like they do under Windows... ...
    (linux.redhat)
  • Re: Can my NDIS driver be signed?
    ... Has this changed with Windows Vista? ... Vendor-signed drivers will not be required to pass the HCT/WHQL tests, ... vendor", by placing the vendor certificate somewhere to Cert Store (this can ...
    (microsoft.public.development.device.drivers)