Quote:
|
Originally Posted by DeadOnTheHead
The install starts ok, but after windows copies files to the computer and it shuts down that first time to complete the installation. It starts the install process over. And this happens everytime. It's just in a loop.
|
Quote:
|
I have also repartioned and formated the drive using the xp disk and I am still getting the same thing
|
Quote:
|
Boot from CD/DVD or Hard drive or network. I have tried every option
|
The reboot isn’t the issue, the install loop is. The only way to resolve this issue is to set the drive up outside of windows, using a manufacturer’s utility. Here’s why:
Basically, when you boot to the install cd, windows loads all drivers into memory, scans the system, finds the drive and looks for the MBR and you are given options to setup the drive. Setup then writes a permanent boot.ini to control all subsequent boots, copies temporary setup files and writes a temporary line to boot.ini that directs the next boot to complete the setup routine. Setup then reboots as it is supposed to, reads boot.ini and is directed to complete the setup. Setup completes, temp files and the temporary line in boot.ini are erased and you should have a working xp install. In this instance, setup went south for whatever reason, and the temporary files and boot.ini line were not erased. As such, on every boot/reboot boot.ini tells setup to install files. The only way to stop the loop is to setup the drive using the manufacturer’s utility and get rid of boot.ini. Windows/windows setup can’t do it because boot.ini always takes control of the boot process before windows is started. It doesn’t matter if you boot from cd or hard drive. Setup reads the MBR, then looks at boot.ini and boot.ini tells windows for what to do next.
While a hardware issue, as Who and TU36 have indicated, could be causing the reboot, the original post indicates the original reboot was probably appropriate. And hardware would be a seperate issue. For purposes of my discussion only, reboot is totally irrelevant. Who and TU36 know that better than I. However, until you address the bad boot.ini, you’re never going to know. First fix the drive, then address hardware with WHO and Tumble
Hopefully, this is what your not hitting on. Similar situations are very common because people don't realize the significance of boot.ini, when it is written and that it totally controls the boot process
Post back and let us know what's up.
Bill