Hope this helps if you have the Winblows2k installation disk.
When you boot the installation media, you can press R to use the Emergency
Repair process. You will then press M for a Manual Repair or F for a Fast
Repair.
During a Manual Repair, you can select/deselect the following:
[X] Inspect startup environment
[X] Verify Windows 2000 system files
[X] Inspect Boot Sector
Continue <perform selected tasks>
Inspect Startup Environment checks the ARC path against the Setup.log file
on the ERD or %SystemRoot%\Repair folder. The Setup.log files contains:
[Paths]
TargetDirectory = "\WINNT"
TargetDevice = "\Device\Harddisk1\Partition1"
SystemPartitionDirectory = "\"
SystemPartition = "\Device\Harddisk1\Partition1"
With this data, the ARC path can be corrected or a missing boot.ini can be
created.
Verify Windows 2000 System Files checks all the Windows 2000 files on the
System/Boot partition against the Setup.log CRC value for each file. If the
file is missing or corrupt, you are prompted to replace it.
NOTE: The optional NTbootdd.sys is not checked.
Inspect Boot Sector repairs the active system partition boot sector and
reinstalls the boot loader. If a non-Windows 2000 boot sector is found on a
FAT or FAT32 system partition, the Bootsect.dos file is created and a C:\ =
"Microsoft Windows" is added to boot.ini.
NOTE: There is no registry repair option with Manual.
The Fast Repair option does all of the Manual Repair options and checks the
SAM, SECURITY, SYSTEM, and SOFTWARE registry hives for corruption.
If a hive is missing or corrupt, it is replaced from the %SystemRoot%\Repair
folder.
If a hive is replaced, your system has some updated hives and some original
hives. You must do one of the following:
1. Restore the System State
2. Use the Recovery Console to replace the hive with a more recent copy, as
from %SystemRoot%\Repair\Backup (if you checked Backup the Registry while
creating a recent ERD).
Both repair options will check the file system integrity on the boot and
system partition. If a correction is made, you will need to restart and
choose Repair again.
Neither option checks %SystemRoot%\System32\Config.nt or
%SystemRoot%\System32\Autoexec.nt.
Michael Perry.
R&D. Dep. Netafim Magal.
<<<<Linux -- the Ultimate Windows Service Pack>>>>
The three most dangerous things are a programmer with a soldering iron, a
manager who codes, and a user who gets ideas.
> -----Original Message-----
> From: Gary [SMTP:[EMAIL PROTECTED]]
> Sent: Mon, June 12, 2000 02:39
> To: Lance
> Subject: Re[2]: [newbie] this is an emergency (lilo, mbr,
> windows...)LanceREAD NOW
>
> Hi Lance,
>
> On Sunday, June 11, 2000, 2:40:51 PM, you hammered out in part about
> "[newbie] this is an emergency (lilo, mbr, windows...)LanceREAD NOW":
>
> L> I followed someone's advice on Linuxnewbie.org last night and went
> L> into the Win2k recovery console (**I DO NOT have the Win2k rescue
> L> floppy discs!!**), I ran the fixmbr and fixboot commands as
> L> suggested, and it said it rewrote the mbr ok (to C:). I then
> L> restarted and it said NTLDR not found (which I guess is the Win2k
> L> bootloader)
>
> At this point, Lance, do you know anybody close to you who is running
> W2K and then they could go into programs/accessories/system
> tools/backup and *make* a rescue disk for you. This might work okay.
>
> --
>
> Best regards,
> Gary
>
> Today's thought: Estimated amount of glucose used by an adult human
> brain each day, expressed in M&Ms: 250
>
> PGP Public Key: mailto:[EMAIL PROTECTED]?subject=SendPGPKey
>
>
