Re: XP Pro install stuck: repeats after first system restart



Thanks, John. I created a slipstream CD with SP2, but I'm still having the
same problem. After the first restart, if I let it boot from the hard drive
(which is what I'm supposed to do, right?), I get "Disk read error". And, as
before, if I boot from the CD the installation just starts over.

I'm using FAT32 because I'm dual booting with Ubuntu Linux, and Linux can't
write reliably to NTFS. I've not heard any clear statement of why NTFS is
better than FAT32. Is it more space-efficient? It doesn't seem to fragment
any less, and I've not heard of FAT32 being any less reliable, but I don't
really know. If NTFS really is better, then maybe I'll set up a small FAT32
extra partition that both XP and Linux can read and write from; then XP's
main partition can be NTFS.

"John John" wrote:

The problem is related to 48-bit LBA and disks larger than 137GB.
Because the XP cd that you are using doesn't have SP1 or later it cannot
properly use disks that are larger than 137GB. Slipstream your cd with
SP2 and you should have no problems. Alternatively, create smaller
partition on the disk for the XP installation and after you install SP2
you can create another partition in the unallocated disk space. Also,
why FAT32? Unless you have compelling reasons to use FAT32 you would be
better off using NTFS, esspecially on such a large disk.

John

Alfredo wrote:
I'm installing XP Pro from an original full retail CD, pre-SP1, on a new
computer (upgrading my old hardware). It goes fine until the first system
restart, after which everything repeats as if nothing had happened. Except,
after I choose a partition, the installer says there's another operating
system installed, which must be XP from the first time around. I'm
installing to a 200GB FAT32 partition, which is the first partition. The
hard drive is SATA running in IDE mode. If I try to boot from the hard drive
itself, I get a disk error. I assume the system should boot from the CD
after the restart and then notice that it's already written to the disk, but
for some reason this isn't happening.

Any help very much appreciated.

.



Relevant Pages

  • SUMMARY: Moving /usr From Under Root "/" To Its Own Partition
    ... One of the reasons for doing this is to end up with a smaller root ... Install the boot block and boot off the new drive. ... " In order for the root partition to be fscked and remounted ... D> temporarily on the existing disk. ...
    (SunManagers)
  • Re: laptop - new HD - no CD or floppy drive
    ... I put the laptop HD back in the PC and I could boot from it. ... If the primary partition has an incorrect boot sector. ... If the disk geometry is incorrect. ...
    (microsoft.public.windowsxp.hardware)
  • Re: laptop - new HD - no CD or floppy drive
    ... I put the laptop HD back in the PC and I could boot from it. ... If the primary partition has an incorrect boot sector. ... If the disk geometry is incorrect. ...
    (microsoft.public.windowsxp.hardware)
  • Re: Can I boot of an XP System disk, nested in a logical volume
    ... I'll boot of Partition Magic or some other kind of magic and fix it that-a-way. ... It's been a long time since I messed with partitions like this, but in the back of my head I have this fragment about boring registry hands-on editing, 'derived Disk ID's' and the 'Master Boot Sector' -- that's S as in 'Senile'. ... One reason for the drive letter change on cloned drives is to keep the parent drive hooked up the first time the clone is booted, being that the clone has the same Mount Manager database, and being that the Mount Manager *always* respects drive letter assignments, it will see the parent drive and its valid disk signature and assign the C: drive letter to the original C: drive, so there will be no C: letter available for the clone. ...
    (microsoft.public.windowsxp.basics)
  • Re: Fedora Core 2/Windows XP dual boot: selecting Linux doesnt work
    ... grub is installed on the /root partition, which is the first partition on hdc: hdc1, or in grub notation. ... Stage1 is the unpatched 512-byte file, that is patched and copied to the boot record during setup. ... This byte is initialized to 0xff in the stage1 file, but patched to 0x81 in your setup, to say "we are booting from disk." ...
    (comp.os.linux.setup)