• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Disk error in XP install

haut

Member
I just got a new motherboard and reformatted my hdd so that I could set up my OS's (win xp and mandrake 9.1). I started with windows because it seems to take over the boot loader if I do linux first. I booted to the CD and after formatting my partition and copying files, setup restarted and instead of continuing setup I got a disk error. I'm not sure what causes this, but installing mandrake on its own worked flawlessly. Could it be the ide controller in my new motherboard? Its an Asus a7v8x. I've tried this multiple times and am sure its not a fluke, has anyone seen this before and/or know how to fix it? I got it at newegg so I'm sure if its defective I can RMA, but I'd really like to make sure its defective before I go through something like that. Why would linux work and windows not? I'm using LILO as my bootloader in linux and my partitioning scheme is as follows: 4gb for windows first (tried fat32 and ntfs), 5gb for linux next (reiserfs), and ~20 gb for a common drive between the two (fat32). I haven't touched the common drive but see no reason to. Thanks all!!!!
-Ryan
 
It would be helpful if you post the error message or more detailed description of the "disk error".
 
Disk error
Press any key to restart

Thats the whole error. I can't continue Windows setup. There is a folder called Windows on the drive that I ran Windows Setup. Has anyone seen this before? Thanks again.
--Ryan
 
that error usually means your BIOS can't find a bootable partition, or the wrong partition is marked active in the MBR.

Check your BIOS boot order settings and if on IDE ensure your drive is master, not slave.
 
Make sure LBA is enabled in the BIOS. Most motherboards' BIOS will have it at Auto but I've seen some that have problems when set at Auto (had to manually enable LBA).
 
Back
Top