Can I use a Win 2000 Emergency repair disk from a different comput

[Guest]

Hi folks
My system doesn't boot because of 'inconsistencies' on my FAT32 drive. PC
Doctor utility says the drive passes all tests.
I guess I'd like to 'repair' a presumed damaged Win 2000 installation then
rather than 'recover' the entire thing & losing everything done to date as a
result of reformatting. During the repair process I invoked, I was asked to
insert the emergency repair disk (which of course I never created when all
ran well).
My PC with the problem is an IBM. I have a Dell at work that runs Win 2000.
Can I create an emergency repair disk on the Dell & use it on the IBM or are
these specific to your vendor/model PC?
Drawbridge

 

[Dave Patrick]

No, ERD's are machine specific. The error is of a file system nature and
really doesn't have anything to do with the ERD. Your drive may be failing
and the drive now has some bad sectors.

You can run
chkdsk /r
from the recovery console command line. (/r implies /f and /p)

To start the Recovery Console, start the computer from the Windows 2000
Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
floppy disks and your computer cannot start from the Windows 2000 Setup CD,
use another Windows 2000-based computer to create the Setup floppy disks.
Press ENTER at the "Setup Notification" screen. Press R to repair a Windows
2000 installation, and then press C to use the Recovery Console. The
Recovery Console then prompts you for the administrator password. If you do
not have the correct password, Recovery Console does not allow access to the
computer. If an incorrect password is entered three times, the Recovery
Console quits and restarts the computer. Note If the registry is corrupted
or missing or no valid installations are found, the Recovery Console starts
in the root of the startup volume without requiring a password. You cannot
access any folders, but you can carry out commands such as chkdsk, fixboot,
and fixmbr for limited disk repairs. Once the password has been validated,
you have full access to the Recovery Console, but limited access to the hard
disk. You can only access the following folders on your computer:
%systemroot% and %windir%

You may want to attempt to backup your important data before running chkdsk
or doing anything else with it for that matter.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Hi folks
| My system doesn't boot because of 'inconsistencies' on my FAT32 drive. PC
| Doctor utility says the drive passes all tests.
| I guess I'd like to 'repair' a presumed damaged Win 2000 installation then
| rather than 'recover' the entire thing & losing everything done to date as
a
| result of reformatting. During the repair process I invoked, I was asked
to
| insert the emergency repair disk (which of course I never created when all
| ran well).
| My PC with the problem is an IBM. I have a Dell at work that runs Win
2000.
| Can I create an emergency repair disk on the Dell & use it on the IBM or
are
| these specific to your vendor/model PC?
| Drawbridge

 

[Guest]

Thank you for replying Dave. I would have tried the ERD from the foreign
platform w/out your advice & presumably caused more harm! I'm glad I asked
first. I did go home & try the chkdsk /r as suggested & got a reply
instructing me to type the full path to autochk.exe. I've since checked for
it's location on my machine at work & found it at C:\WINNT\system32
I'll try it again tonight supplying that path. Does it seem strange to you
autochk.exe didn't know to look there?

No, ERD's are machine specific. The error is of a file system nature and
really doesn't have anything to do with the ERD. Your drive may be failing
and the drive now has some bad sectors.

You can run
chkdsk /r
from the recovery console command line. (/r implies /f and /p)

To start the Recovery Console, start the computer from the Windows 2000
Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
floppy disks and your computer cannot start from the Windows 2000 Setup CD,
use another Windows 2000-based computer to create the Setup floppy disks.
Press ENTER at the "Setup Notification" screen. Press R to repair a Windows
2000 installation, and then press C to use the Recovery Console. The
Recovery Console then prompts you for the administrator password. If you do
not have the correct password, Recovery Console does not allow access to the
computer. If an incorrect password is entered three times, the Recovery
Console quits and restarts the computer. Note If the registry is corrupted
or missing or no valid installations are found, the Recovery Console starts
in the root of the startup volume without requiring a password. You cannot
access any folders, but you can carry out commands such as chkdsk, fixboot,
and fixmbr for limited disk repairs. Once the password has been validated,
you have full access to the Recovery Console, but limited access to the hard
disk. You can only access the following folders on your computer:
%systemroot% and %windir%

You may want to attempt to backup your important data before running chkdsk
or doing anything else with it for that matter.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Hi folks
| My system doesn't boot because of 'inconsistencies' on my FAT32 drive. PC
| Doctor utility says the drive passes all tests.
| I guess I'd like to 'repair' a presumed damaged Win 2000 installation then
| rather than 'recover' the entire thing & losing everything done to date as
a
| result of reformatting. During the repair process I invoked, I was asked
to
| insert the emergency repair disk (which of course I never created when all
| ran well).
| My PC with the problem is an IBM. I have a Dell at work that runs Win
2000.
| Can I create an emergency repair disk on the Dell & use it on the IBM or
are
| these specific to your vendor/model PC?
| Drawbridge

 

[Dave Patrick]

Yes that is odd, never heard that one before. Did the recovery console start
without issue? You may want to download a diagnostic utility from the drive
manufacturer's web site. Be sure to back your data before proceeding.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Thank you for replying Dave. I would have tried the ERD from the foreign
| platform w/out your advice & presumably caused more harm! I'm glad I asked
| first. I did go home & try the chkdsk /r as suggested & got a reply
| instructing me to type the full path to autochk.exe. I've since checked
for
| it's location on my machine at work & found it at C:\WINNT\system32
| I'll try it again tonight supplying that path. Does it seem strange to you
| autochk.exe didn't know to look there?

 

[Guest]

Hi Dave
A piece of information I never relayed that may help explain it is the
recovery console was started from "E:\WINNT" which is a partition on the
drive that contains the recovery software. A recovery CD was never provided
with the PC. The needed information was instead placed on a partition of the
same physical drive. Apparently that partition doesn't contain the
autochk.exe it was looking for.

 

[Dave Patrick]

I don't know what 'recovery software' you're talking about but in order to
start the recovery console; it needs to have been installed as a startup
option or you boot from the Windows 2000 install CD-Rom. There's no other
way.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Hi Dave
| A piece of information I never relayed that may help explain it is the
| recovery console was started from "E:\WINNT" which is a partition on the
| drive that contains the recovery software. A recovery CD was never
provided
| with the PC. The needed information was instead placed on a partition of
the
| same physical drive. Apparently that partition doesn't contain the
| autochk.exe it was looking for.