WinXP won't boot from SATA
reelbigfish
Boston, MA Member
Hey guys. I have an Abit IS7 and a Western Digital Raptor. I can get through the entire install of WinXP and it just won't boot. I have the Raptor on SATA 1. All that happens is that the screen stays black right after it says updating DMPI pool. If I install Win2k it will boot from the SATA, but it is extremely slow. With XP when it has to boot from the HDD during install it is quite quick. Then nothing. I have the latest BIOS and drivers. I have no idea why it won't boot. Help!
0
Comments
That may isolate a SATA problem.
~dodo
I take it that you installed the sata drivers during the install right? (the F6 thing) Or are the sata embedded on that board so that you dont have to install the drivers?
Also, check if Apic is enabled in bios. If it is, i suggest you disable it and do a reinstall or perhaps a repair.
Additionally, while I am somewhat reluctant to point you elsewhere for help, there are many and thorough NF7 posts in the Abit section on nForceHQ here
Even with the release bios, the drives should work, but you will get trouble during boot.
FYI, i´m not a damn bit better myself. Sorry for pointing it out. It´s an ugly thing to do.
On top of that, Fish has an IS7 which is as far from an Nforce you can go. (It´s an Intel board)
Fish, you haven´t touched the jumper on the drive i hope?
Assuming all IS7's use the same basic bios menus, there are two places where you can enable SATA.
The correct menu for your board (plain IS7, I believe...) is the "OnChip IDE Device" menu -> "OnChip Serial ATA"
The IS7-G has another SATA controller under "Onboard PCI Device" menu -> "Serial ATA controller"
I dont want to use my slow IDE (7200rpm) HardDrive, I want to use my SATA WD Raptor(10,000rpm) and salvage my old HD to another computer. This being said, I've already begun looking into the problem.
So far, this is what I've found from a different forum, so I hope it helps:
1. make sure "USB keyboard support" and "USB mouse support" are both set to "OS" and not "BIOS" - if either of these are set to "BIOS", it somehow causes the Via RAID BIOS to be disabled during boot, thus preventing the SATA HDD from being recognized as a bootable device
2. make sure "bootable add-in device" is set to "OnChip SATA RAID"
3. make sure "SATA RAID BIOS" is set to "enabled"
4. VERY IMPORTANT - use a normal internal floppy drive when loading Via RAID drivers during windows setup!!! (you may laugh, but I was using a USB FDD, and this seems to have been the main cause for my troubles, as it somehow corrupted the installation)
5. I doubt this last one matters, but set boot device order to: 1. floppy, 2. cdrom, 3. hard disk, and make sure "boot other device(s)" is enabled.
This Thread was posted for the Abit KV7, so I'm not sure the BIOSs are the same... also I encountered some confusion in the post. This person said, make sure keyboard and mouse are set to OS and not BIOS, while another person said it worked when set both to BIOS instead of OS. I'd try the former of the two first.
I don't actually know if this works or not, but just remember not to set up the SATA as a RAID. Also, here's a link to the page i got the info from:
http://www.techsupportforum.com/computer/topic/9974-1.html
The USB mouse/keyboard issues on the KV7 have been fixed with recently released bios v.15
Verifying DMI Pool Data.........
Boot from CD:
Boot from CD:
DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER
My Windows XP is of course on the SATA Raptor drive, also in SATA slot 1. Once I put the CD in the drive and restart, Windows XP boots fine....
hey dude,
follow these steps you'll be fine.
1. get a computer that boots to an os aready ie: win95/98/2000 etx.
2. get the mother board cd and locate the drivers.
3. get a floppy disk and format it.
4. find the scsi drivers and create a scsi driver disk this disk is not bootable.
5. remove your ide hdd and boot to the cd for installation.
6 press"f6" and wait till it asks for the scsi drivers then is stall both the controller and the drivers from the floppy (this WILL not work from cd)
7. take fdd out.
u should have no problems anymore.
cheers.
Hello, I have just come across a similar problem.
I am building a new PC, based upon a KV7 motherboard and a 160GB SATA harddrive.
I had not appreciated that the drive would not simply be a straightforward boot up device.
I have tried a number of the suggestions made earlier in this thread, but am stuck with either the DMI pool message, or if trying to install WinXP, a message of "textsetup.oem caused an unexpected error (512) at line 1742 in d:\xpclient\base\boot\setup\oemdisk.c" the message is followed by the inevitable "press any key". This is with an internal DVD and floppy drive installed.
Strangely, putting in a conventional IDE harddrive, with a working WinXP installation from another PC, instead, doesn't seem to help.
Is it me?. I have built a number of PCs from scratch, and never been as stumped now.
Anyone's help would be much appreciated.
By the way, I'm new on the forum, but it looks great.
Try disconnecting the Floppy Drive - you never know......
make shure the cd-rom is not scratched.
if the sata is a wd then sorry but you MUST have a working fdd with the sata scsi driver and controller.
you make this with the mobo cd and copy the files to a fdd (it will not read them from any other media)
from what your saying it sounds like a hardware/media issue.
however if the sata is a segate then as far as im aware it should boot without the drivers .
should fly i know this cus my hdd took literally under 30 seconds to format
my system mite be a little underspec to you but i like it. ;-)
3400 + 64
1 gig ddr2 667 ram (1 module)
ATI RADEON R9800XT/256MB DDR/DVI/TV-OUT/AGP8X
GA-K8VT800 (gigabyte)
120gb wd sata hdd
does what i want.
cheers
I dont want to use my slow IDE (7200rpm) HardDrive, I want to use my SATA WD Raptor(10,000rpm) and salvage my old HD to another computer. This being said, I've already begun looking into the problem.
Thank you, I have similar problem with P4P800-X and Seagate Barracuda 160 GB. I'm going to try your solving
make sure "USB keyboard support" and "USB mouse support" are both set to "bios" and not "OS"