Screwed up boot sequence....

Seth

New Member
Boot sequence screws up :S

Hey, Recently i have purchased myself a new Hard drive. before that i ran a 250GB sata HDD as my primary drive with a 120GB IDE drive as a secondary. I have put my new 320 sata drive in as another secondary drive. Anyways, i got it and plugged it into my secondary sata port on my motherboard and booted her up. All worked fine. Formated it all good and it works fine. EXCEPT!

*Sometimes* when i turn my computer on, during the POST screen, it will freeze at the "detecting IDE drives" part...and just sit there for like 1-2 minutes just frozen. The light on the front of my computer indicates that HDD(s) are busy...constant. After it gets over the freeze it moves along to windows boot...sort of. Half way through fading the windows logo onto the screen it freezes. Like i can JUST see the windows loading thing very faintly. This time it freezes for good.

So what the heck is going on!?!?!

What makes it more confusing is that it only happens about 50% of the time when turning my comp on...is there something in the BIOS i have missed or what?

Thanks for any help you can give :)
 
Last edited:
Well i must be booting off the right drive as sometimes it boots fine. I'll check about the raid thing though...Any more ideas anybody? One of my friends said it could be something to do with the jumpers on the back of the HDD. Though another friend told me not to touch jumpers on SATA drives at SATA works it all out for itself...
 
There are no jumpers on my SATA drive...Anyway I would advise against changing the jumpers because your friends are right SATA should work out by itself being one channel per drive, how ever if it was IDE then you would change the jumpers.

Sounds to me like a power issue. But power isn't one of my most knowledgeable subjects.

Also didn't XP at first not have SATA drivers or something like that?(Just a thought, could be wrong)
 
Well it freezes before it gets to have to go anything to do with XP. Also as it boots half the time without issue i would have though that drivers cannot be it.

So could i be power issue? I would have thought that a power issue would occur constantly and not only half the time...but again power isn't my area of knowledge.
 
Back
Top