Re: Winnt\sys32\config\systemCED Error
- From: "ColTom2" <nomailaddress@xxxxxxxx>
- Date: Thu, 12 Oct 2006 21:37:12 -0400
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> 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
- Follow-Ups:
- Re: Winnt\sys32\config\systemCED Error
- From: John John
- Re: Winnt\sys32\config\systemCED Error
- References:
- Winnt\sys32\config\systemCED Error
- From: ColTom2
- Re: Winnt\sys32\config\systemCED Error
- From: John John
- Re: Winnt\sys32\config\systemCED Error
- From: ColTom2
- Re: Winnt\sys32\config\systemCED Error
- From: John John
- Re: Winnt\sys32\config\systemCED Error
- From: ColTom2
- Re: Winnt\sys32\config\systemCED Error
- From: John John
- Re: Winnt\sys32\config\systemCED Error
- From: John John
- Re: Winnt\sys32\config\systemCED Error
- From: ColTom2
- Re: Winnt\sys32\config\systemCED Error
- From: John John
- Re: Winnt\sys32\config\systemCED Error
- From: ColTom2
- Re: Winnt\sys32\config\systemCED Error
- From: ColTom2
- Re: Winnt\sys32\config\systemCED Error
- From: John John
- Re: Winnt\sys32\config\systemCED Error
- From: ColTom2
- Re: Winnt\sys32\config\systemCED Error
- From: John John
- Winnt\sys32\config\systemCED Error
- Prev by Date: Re: \WINNT\SYSTEM32\CONFIG\SYSTEM file size problem - prevention?
- Next by Date: Re: Winnt\sys32\config\systemCED Error
- Previous by thread: Re: Winnt\sys32\config\systemCED Error
- Next by thread: Re: Winnt\sys32\config\systemCED Error
- Index(es):
Relevant Pages
|