2k boot trouble

[yawningdog]

When I select NT (win 2000) from my grub loader, I'm getting the following error

disk i/o error: status = 00001000 NTDETECT failed

By some miraculous co-inky-dink, I have boot.ini, ntdetect.com, and ntldr files
saved on a floppy. Are these what I need to rescue my system? If so, how? PLease,
my wife is really angry over this.:mad:

[sea69]

The Boot.ini text file displayed by the Boot Loader menu during boot-up. It identifies the physical location of the operating system files. So, it must adhere to ARC Path conventions Some values in this file can be changed from GUI: Computer properties, Advanced tab, “Startup and Recovery” dialog.


The Ntldr which reads Boot.ini. It displays the “Starting Windows” progress bar at the bottom of the screen. It calls file Ntoskrnl.exe, the Windows 2000 OS kernel that manages all remaining boot functions. Note: Ntldr takes the place of file BOOTSECT.DOS which loads non-Windows 2000 OSs. Ntldr uses interrupt (INT) 13 BIOS calls to locate Ntoskrnl.exe and other files that it loads at startup.

NTDETECT.COM, which builds a (“Plug and Pray”) hardware list for Ntldr to add to the Registry.


NTBOOTDD.SYS, a device driver for SCSI disk controllers if BIOS SCSI is disabled.

Windows 2000 Debugging

Store your data on a different physical hard drive.
Copy the Windows 2000 Install CD onto a hard disk.
Create a new Emergency Repair Disk (ERD) after every time you apply a Windows Service Pack.
Backup data to a different media, before you install or upgrade a new application
Use a (RAID-1) mirror drive for redundancy on the boot partition.
Install Recovery Command Console [Q216417] so that it's an option presented from Boot.ini. Example:
X:\ENGLISH\WIN2000\PRO\I386\winnt32.exe /cmdcons
Stuck in boot-up Text screen
Boot-up from CD-ROM or diskette created from Windows installation CD's.
ntdetect.com
Press F6 and load third-party SCSI drivers
Responses to problems
Look at the ntldr.txt
If your system does not boot, at the black screen, press F8 and choose Last Known Good
If your system boots, boot up in Safe Mode to start the operating system with basic drivers and services
Safe Mode Advanced Options
Enable Boot Logging
Enable VGA mode
Directory Services Restore mode
Debugging mode
Uses for Safe Mode
Incompatible driver or setting for the video card
Corrupted Windows Explorer shell
Run msinfo32
In the Recovery Console
Almost all previous DOS commands are available.
FIXBOOT to restore a damaged boot sector.
FIXMBR to repair a Master Boot Record.
Or from a boot up disk: FDISK /MBR
Replace damaged system files, drivers, and registry hives from floppy or CD.
Remove Active Directory from Domain Controller
For security reasons, the Recovery Console allows reading from but NOT writing to diskettes. ......

or you could boot to "last known good"

hope some of this helps- and there's the recovery console....link in my signature!




;)