21 replies
by mjd420nova
by zlitocook
by secor941
by shpl
by ic-it
Replace your motherboard battery, reboot to BIOS and reset to defaults.
Check your settings (in BIOS) insure any BIOS virus protection is turned of and that PNP OS = No.
Reinstall XP. Do not use the fdisk /mbr option on an XP installation. If needed use the Recovery Console Fixmbr command. You may also need to run fixboot and bootcfg /rebuild.
edited to add: should you still feel a need to upgrade (flash) the BIOS; identify the motherboard/manufacturer and go to their site for the file and instructions.
I have the same problem. This is just my theory, but I'm thinking the HD isn't spinning up properly. By making the system check the CD Rom before going to the HD, its giving the HD time to stablize.
I've replace my power supply with a better one, and still have the problem. I've even put the HD on its own power rail, but it is still buggy.
I'm guessing impending failure.
That's what I get for buying recertified drives.
If it's an old drive, it may just be that the MBR sector is corrupted or physically damaged.
Try running the recovery console from the Windows CD and using FIXBOOT command to attempt to rewrite the MBR. If this doesn't work, I'm guessing what I said above is true.
by tkman28
I had this exact problem.
I surfed the web and tried all kinds of things.
I tried new cables, the hard drive in a different machine as a slave, I ran disk tests, I reinstalled twice, I checked for viruses, tested the power supply,...etc.
I submitted a question to the Western Digital folks to see if they had an answer. Nothing.
I was about to buy a new hard drive but decided to talk to the tech guy first.
Thanks to my local PC store tech guy he suggested I check the jumpers on the drive.
I have always set the Jumpers to Master when there is only one drive in the system.
With Western Digital this causes weird failure.
I totally removed the jumper and the system started beautifully. I then set the jumper to cable select and had the drive attached to the last connector and this worked beautifully as well.
Thus before trying all the other stuff look at the hard drive and the pins beside the data cable. There should be some indication as to what pins are for Master, slave, and cable select. Either remove all jumpers or go with cable select.
Hope this works for you.
by xd40er
TKMan - if you do nothing else this week, stop and the liquor store and pick up an expensive bottle of Tequila for your local tech guy.
I was at my wits end with my computer and came across this - tell you boy he is the man.
Exact same problem, exact same drive.
Eternally Grateful - OldManTod
by george
by yaronkle3
I had the same problem with the "DISK BOOT FAILURE" and the need for the XP boot disk.
The BIOS boot sequence was HD1 instead of HD0.
It should never have booted in the first place since there was no HD1.
Found out the problem after I reset BIOS settings.
by tyfuslijer
YES!
This is what worked for me aswell. I've got me a brand new system, but that darn disk boot failure almost ruined my day.
I also had the wrong hard disk set for booting, changed it in the BIOS and all works fine (for now ;) )
by wjnevon
by firthy
How I fixed it ...
I had to move my HD off the IDE 1 port on the motherboard to the IDE 2 port.
I disconnected the cdrom from IDE 2 so I only had my HD on IDE 2 and no cdrom connected.
Re-booted and it booted up without giving me the Disk boot failure msg.
I then connected the cdrom to the IDE 1 connector.
It all works fine like that, so basically just swapped the HD and cdrom over to opposite IDE ports.
Hope this helps someone in the future...
by bob
by crsohan
Yeah , the ubiquitous "Disk Error, Insert System Disk" :-(
I googled etc. & tried various remedies.
Things started off with a WinXP mesg to chkdsk after I installed the megaupload toolbar - which is apparently a spyware gateway.
1. Uninstalled the meagupload add-ins, chkdsk'd - some stuff got fixed- then the "Disk Error, Insert System Disk" came on.
2. Reinstalled WinXP Pro from scratch, still didn't fix.
3. Reformatted partition & reinstalled OS, still no dice.
4. Split partition into two : now they got D:, E: drive letters :-(
5. Tried reformatting & installing onto D:, no dice
6. Tried reformatting & installing onto E:, no dice
7. bootcfg /list indicated everything was ok, but tried fixmbr, then fixboot w/o success
8. Set up dual boot with linux (Fedora Core) on another partition, notwthings are interesting! Fedora comes up fine from another partition on the same drive. With Fedora, I can mount & see the contents of the NTFS partition (now E:) where I installed WinXP, but obviously, the bootup process has a problem. I tried booting WinXP from the dual boot, but that didn't work either - it just hung there trying to load WinXP after
rootnoverify (hd0,5)
chainloader +1
Any pointers, anyone - help mucho appreciated!
by c4kays
Took the HD and floppy cage out of the case to change the HD, booted the PC with the same drive, (just to make sure)
No more disk failure.
Put the unit back in the case, back to failure.
Moved the HD up, physically, to a higher slot in the cage and no more failures.
by tmelloch
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending