That's not a good error to have (as if there were any good errors to have :-\
). This error can mean a multitude of things but it is commonly associated
with a bad hard drive or a corrupt Windows install. The "boot.ini" file
could be bad too. It could be a bad cable or ribbon going from the drive to
the motherboard. As you can see, there are several places to start your
troubleshooting. The fact that you don't have your setup disk is bad. One
should always have that handy. I know some OEMs like Dell & HP don't always
ship the disk... You may have to borrow one from a friend.
You can use the setup disk to boot up and get into the Command Console.
This stripped-down version of an "OS" can do you some good! One of the
things it can help you with is just checking to see if the hard drive is good
or not. Running the Command Console will try to mount your Windows Install
to the working environment. If it can't even see the Windows Installation on
the hard drive, you may be looking to replace said hard drive. If it mounts
it, you may be able to run "chkdsk /r" (without the quotes) and it will
attempt to repair things on the hard drive. Oh, and if the Command Console
doesn't mount the Windows installation, you can try to go into the setup.
Now, don't be so quick to run the setup! Just go through the motions and
check to see if it see a drive to install on. If it does, see what size is
showing up. Ive seen systems where the setup disk saw the drive but had 0
out of 0 bytes available. This too could mean your hard drive is bad.
Check out the following link:
http://support.microsoft.com/kb/555302
Also, search the web for help. There's plenty of stuff to be found in
forums around the world. Google is your friend! You're not the first one to
have these issues.
10-26-07
1537 EDT