• 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.

Harddrive boot delay problem

Z

zuze

Member
I have a WD 80GB 7200rpm harddrive. I had it a few months in my system which is a P4 2.53Ghz with Iwill P4GS i845G board. This drive was always secondary to my IBM 20GB drive, but I do have my win xp installed on it. I have started to experience a delay during a boot time. Before it starts reading off the disk after the post screen and device table there is a delay of like 20 seconds and then it goes to boot into winxp. I thought that setting the drive as a master would fix it but an awful thing happend. It wouldn't boot at all and make some awful noises and lock the sytem right after memory test. All settings were set right, and the same repeated when I had tha drive in the system alone by disconnecting all other drives including cdrom. I checked things many times. After trying for a long time, I reverted the drive back to the slave setting and BAH, it WORKED again with the same delay. But at least it worked. Can anyone explain that? To finish it off, the dirve is on the primary ide channel and programs on that drive start just tad slower than they used to.
 
Well, it works as a slave to the IBM drive because the bootloader is on the IBM drive. The BIOS reads the boot record from the primary, which then says "Start Windows from where it's installed, on the other drive." Taking the IBM drive off the primary master leaves you with no boot record.
If you want to go without the IBM drive, you could put the WD on primary master, boot from the Windows CD into rescue mode, and type "fixboot" to write a bootloader on the WD.
As for the delay in booting, the only thing that comes to mind is a setting in the BIOS where you can delay booting from the hard disk by x seconds, but you'd probably know if you changed that.
 
Bootloader is on the slave drive(ntldr). Plus the system is set to boot from hd1 not hd0. If the boot record wasn't there it would have never started up win xp. IBM drive boots immediately.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top