You can start the recovery console and from a command prompt issue the
command;
fixboot
to repair the bootsector.
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%
Also try creating a boot disk. For the floppy to successfully boot Windows
2000 the disk must contain the "NT" boot sector. Format a diskette (on a
Windows 2000 machine, not a DOS/Win9x, so the NT boot sector gets written to
the floppy), then copy ntldr, ntdetect.com, and boot.ini to it; and possibly
ntbootdd.sys. Edit the boot.ini to give it a correct ARC path for the
machine you wish to boot and fix it after the OS starts.
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
:
| When booting windows 2k pro I get an invalid boot
| diskette. Insert boot diskette in A:. I do not have a
| disk in the drive. When the system gets rebooted then
| that error does not occur.
|
| What is the corrective solution to this issue.
