Disk Boot Failure. Please Help Me!

[ArbY]

You probably have faulty RAM.
Run the memtest over night. I was getting the Blue Screen with XP installs as well. Cause? Faulty RAM.

 

[sweetpants]

You probably have faulty RAM.
Run the memtest over night. I was getting the Blue Screen with XP installs as well. Cause? Faulty RAM.

I am willing to bet that it is not memory causing this error. Usually, at least in my experience, memory is not the cause of no bootable partition to be found.

In Windows XP installations where a lot of data is having to be written and read from memory, yea I can definately see that happening (and see it on a daily basis)

 

[ches111]

Arby,

Hang on man....


He just got the bloody optical drive to recognize.... He is not even close to needing that yet...

Please stop suggesting that until such time as it is needed. He has what seem to be minor issues right now.

 

[LPS]

Rmn,

As far as I remeber, the Samsung run SATA2 do not need any caps on the back.

As question as before, have you a floppy drive so you can load the gigabyte preinstall ATA drive with F6 on XP install?

 

[sweetpants]

I'm not really sure why he needs to install third party raid controllers when he has one drive... anyone else want to point this ou for me?

 

[LPS]

Not the RAID controller. ATA IDE controller. I have seen a similar post elsewhere.

Gigabyte downloads have this very driver listed for F6 Preinstallation of XP

link - check it out!

 

[ches111]

LPS may be correct but it seems that there are NO jumpers on his drive at this time.

The model is a Spinpoint P series 2405C

Which needs jumpers in place to be ANYTHING...

In fact it needs two jumpers. Weird!

You would think all open would be equiv to CS but it is not..

The manual states that it needs to be jumped to be CS even.

 

[LPS]

Samsung FAQ about the jumper

Error Patch that look interesting

 

[rman3349]

ok everyone, thanks for all the help. Here's where I stand:

I stole jumpers from my fans (not desireable i know but i had to try) so i could set my drive as the master. It worked, and my BIOS correctly identifies it as such. However, I still got the blue screen.

to LPS: could elaborate for me slightly please

to ches111: thanks for all the help man, nice to know that people actually care about my problems (and are able to put up with my lack of experience)

 

[LPS]

Rman,

Can I ask 2 things;

1. which SATA port on the motherboard have you used for the hard drive?

2. Elaborate on what exactly.

 

[LPS]

Ches111,

I still belive you don't need the jumpers, otherwise they would have been supplied and Rman would not ahve to steal one.

 

[rman3349]

1.) I have tried all the SATA ports with the same result (actually only 3 but i think thats proof enough)

2.) Elobarate on what the implications of this Gigabyte driver are and how exactly one might download it without windows.

Thanks

 

[LPS]

Ok still a little confused on the master/slave issue.

I fyou do not have a floppy drive you can not use the driver any way.

If you do, you need to daownload the file on to a floppy disk.

Start the XP install and press F6 when XP asks.

The press F6 comes up acroos the bottom of the screen almost straight away. It actually says something about F6 to load raid drivers, but its the same spot.

Might be worth a try.

 

[rman3349]

thanks ill def try that

 

[LPS]

Also, now that you have jumpered the HDD, check that it hasn't affected the size in BIOS and XP create partition.


As a matter of interest, what happens if you Unpin the HDD and pin the DVDrom to slave?

 

[rman3349]

HOw can I get that friver installed. I have it on a floppy, what do I do.

 

[LPS]

OK, did you unzip it fiorst. As I recall it was a ZIP file download.

Then start the install of XP again, read the text that is displayed doen the bottom and press F6 when instructed to.

It will then ask for the floppy disk and you should be able to select the file.

Once it has it, it will continue the install.

 

[michaelahess]

If you have a floppy drive, use it and hit f6 when booting the xp cd, if not you have to slipstream the driver which is way beyond your abilities at this time.

If you had to jumper a sata drive that was NEW, something is wrong, unless it was to jumper from sata2 to sata1. Do you have any friends that have built pc's in the past, get some help maybe from them. You are getting too much wrong advice here to both messing around any more, unless you like wasting your time.

 

[LPS]

Which advise do feel is wrong?

Didn't offer the slipstream options as he is having enough trouble and he has already got as far as putting it on floppy, so I would assume that means he has one.

 

[michaelahess]

First off, jumpering a SATA drive for anything other than switching between sata1 and sata2. Second, having a master/slave setting for sata to begin with. Third, giving a dam about which sata port the hd or which ide port the dvd is plugged into (you can boot off slave or master on either ide connector and no, cable placement doesn't matter if you don't use CS.) And fourth, the blue screen during install is a RAM, CPU or bad disk or drive problem, it has nothing to do with which port the hd or dvd is plugged into.

I looked over the manual, it seems you need a driver disk for the intel ICH7R even if not using RAID, how thoughtfull of intel to suck so much. But the OP said he got a blue screen after a while in the install, which to me would mean the HD was seen by windows setup without the driver disk (please correct if wrong on that assumption.)

PDF of Driver requirments.

 

[LPS]

I agree with you about the jumper and I actually stated the same thing in my posts.

In the gigabyte board driver downloads there was also an ATA driver to use under F6.

I only threw in the what cables were where to try and understand myself why 1. his HDD was being allocated as a slave in his bios. 2. when doing as others suggested, jumpering the HDD, which apparently worked, to work out why it worked.

Would be nice to hear from Rman3349 again to see how it is going.

 

[michaelahess]

I understand, I was curious about #2 as well, I have a feeling there may be something funky about his board, I've never seen a SATA drive do that unless it was connected to and IDE port via an adapter. He shouldn't need the ATA driver but then again, it's an Intel chipset

 

[rman3349]

hi everyone. I have taken a few days off because I'm taking a summer class and I have and exam tomorrow. Hopefully, I'll have some time after that to try this again. In the meantime I really haven't had the time. Thanks for all the help. Check back tomorrow 😀

 

[CrAy-Z]

The driver disk for your sata controller is definately the way to go... just because windows can see and recognise your drive, this does not mean that the default windows drivers are best... I was attempting to install vista B2 the other day and while it recognised my disk drives and could see them i was getting all sorts of disk errors and blue screens.. funnily enough it turned out to be the drivers i was using.

Follow the good advice already given here about using a driver floppy during the XP installation.
Don't worry so much about dud ram unless you get this issue sorted and are still running into problems.

From my understanding of SATA, it should not matter if the system is showing your drive as a master or slave if it is your only drive, but from a 'neatness' point of view it is nice to have your first disk showing as master on the primary controller etc etc.

Good luck.

 

[rman3349]

ok, thanks for you patience everyone. Here's the update:

Windows begins ot load as before but then gives me the error message. So i downloaded the driver, unpacked it, opened the WINXP folder (I'm using XP Home) and found three files. I put them all onto a floppy and when setup began ot check for my hardware, I inserted it. I hit f6 a moment later and then waited for about 10 seconds and got this screen:

Setup was unable to load support for the mass storage device you specified. Currently, Setup will load support for the following mass storage device(s)

<none>

To specify additional SCSI adapters, CD-ROm drives, or special disk controllers for use with Windows, including those for which you have a device support disk from a mass storage device manufacturer, press S

If you do not have any device support dicks from a mas storage device manufacturer, or do not want to specify additional mass stoarage devices for use with Windows, press Enter


Well, there it is: More Shit. So i decided to press S just to see what happens. Here it is:

The file txtsetup.oem could not be found. Press and key to continue


Pressing any key returns me to the previous error screen.
WTF?!