Windows XP Pro Instalation Problem

[paliopetho]

I have recently tried to install windows XP Pro on a brand new 60GB hardrive. I replace the hardrive and power up. The blue Windows Setup screen comes up, "F6 if you have SCSI", "Loading Setup Files", "Copying Setup Files", that finishes, "Reboot In 15 Seconds". On reboot Windows never starts, it does the whole process over again, "SCSI", Setup Files" I repartioned, reformated, setup files again, reboot, over and over again. Windows never starts. Could it be due to harddrive jumper settings? The hardrive shows no jumper settings for single master. Please Help.....Losing sleep, going mad.

[Rick]

If you have your boot order set to
floppy.cd-rom,hard drive
Then you should run the setup and at the point where it reboots.
Remove the cd from the drive and allow it to boot off the hard drive


Also
In a few rare cases I have found 2 copies of setting running
What I did to stop the never ending loop was press Ctrl-Alt-Del and end one of the setup's during the setup but before the system did the auto restart

[paliopetho]

After reboot, it says "No Emulation" and goes right back to the Windows Setup Screen. What is "No Emulation"?

[Paul Komski]

"No Emulation" relates to the way that CD's are made bootable - not that it is something I have researched very much - and seems to mostly crop up as an error when using slipstreamed (for non-attended) installation CDs. Is yours a normal WinXP CD?

Occasionally this problem can be related to BIOS settings or to bad IDE connection cables. I s'pose it's also possible that the ram/ramdisk is not being cleared during the reboot.

Try booting to a normal Win98/ME or other boot diskette and then navigate to the i386 folder on the CD. Then run winnt from inside the i386 folder. This should bypass the "Windows" SetUp sequences. If that doesnt do the trick then just copy the whole i386 folder to the HDD and then run winnt, as before. Since the CD now doesn't need to be used for the install it should hopefully set things up without any further problems.

[paliopetho]

Aparently it was the bios. I flashed the bios and it works great