|""Reboot and Select proper Boot device or insert Boot Media in Selected Boot device and press any key"|
"I do have an errors in Event Viewer every time I boot cold or from Standby which I've never had before, which says "The driver detected a controller error on \Device\Harddisk0\D." Error ID: 11.
I either do a ctrl-alt-delete to restart again or sometimes have to shut the machine off and it starts up fine."
If those errors DO NOT happen every time you boot the computer, then they probably have nothing to do with a boot.ini problem.
These things are a lot more likely.....
Some bios Setups have a setting where you can specfiy how long the bios takes to detect hard drives. Sometimes you must increase the time from it's default seting in order for your hard drive Windows has been installed on to be reliably detected as bootable every time you boot the computer.
It's extremely unlikely there's anything wrong with your drive controllers, but there certainly can be something wrong with your drive's data connection. Windows can't tell the difference..
It is common to un-intentionally damage IDE data cables, especially while removing them - the 80 wire ones are more likely to be damaged. What usually happens is the cable is ripped at either edge and the wires there are either damaged or severed, often right at a connector or under it's cable clamp there, where it's hard to see - if a wire is severed but it's ends are touching, the connection is intermittent, rather than being reliable.
Another common thing is for the data cable to be separated from the connector contacts a bit after you have removed a cable - there should be no gap between the data cable and the connector - if there is press the cable against the connector to eliminate the gap.
80 wire data cables are also easily damaged at either edge if the cable is sharply creased at a fold in the cable.
Try another data cable if in doubt.
80 wire data cables must have the proper end connector connected to the mboard IDE header - usually that's blue, but in any case it's the one farther from the middle connector on a 3 connector data cable.
Check your SATA data cables. The connector on each end should "latch" into the socket on the drive and on the mboard, or on the drive controller card - it should not move when you merely brush your hand against it near the socket - if it does, mere vibration can cause a poor connection of it - use another SATA data cable that does "latch", or tape the connector in place.
(There is a slight projection or bump on one side of the outside of the connector that "latches" it into the socket - it's easily broken off or damaged)
The same thing applies for the SATA power connection.
Once you're SURE there's nothing wrong with your data cables....
Check your hard drive with the manufacturer's diagnostics.
See the latter part of response 1 in this:
If you don't have a floppy drive, you can get a CD image diagnostic utility from most hard drive manufacturer's web sites, but obviously you would need to make a burned CD, preferably a CD-R for best compatibility, on another computer if you need to.
Seagate's Seatools will test (almost) any brand of hard drive.
Do the long test.
The bootable Dos versions of SeaTools can be used even if Windows is not working properly.
If the hard drive itself tests okay, any data problems found can be fixed, one way or another.
"The MIcrosoft site says the boot.ini should look more like this:"
You were looking at boot.ini as it was used in Windows NT, not XP.
Most computers these days DO NOT have SCSI drives. However, Microsoft chose to use it's long time support of SCSI drive controllers to support SATA hard drive controllers in Windows, so they show up in Device Manager as SCSI devices.
How to Use and Edit Boot.ini in Windows XP
Also has info about bootcfg.
You can't change boot.ini using the msconfig utility, the first method shown, unless the attributes of boot.ini have been changed from the default Read only, but you can change the settings and Edit boot.ini using the second method shown.