Follow up on: How do I install an f6 disk driver after the fact?

[ToddAndMargo]

Thank you. This seems like the easiest way. It will be
pretty quick too (~25 min) on an i7 motherboard.
-T

Hi All,

This is a follow up on the above post.

The install was fresh, I really had nothing to
loose except another 1/2 hour to do a repair
install of XP. So I figured I could get brave.

Here is what I did.

1) opened up my motherboards manual and looked
at the specificationsto see what kind of controller
I have: ICH10R

2) Booted XP. Opened the device manager and looked
for the hard drive controller. I found two of them:
a four port and a two port (makes sense, have six
SATA ports on my motherboard).

3) I then proceeded to do a force upgrade of these two
controllers to the ICH10R drivers on the F6 disk (also
on my hard drive as well). Windows did whine about
me replacing the drivers with the wrong drivers.

4) shutdown and rebooted into BIOS. Told my BIOS that
my controller was now AHCI (was IDE).

5) successfully booted back into Windows. BSOD all gone!
Happy camping returned.

Try this only at your own risk! Hope this helps someone
else. Thanks to all who gave me tips on this!

-T

 

[Guest]

Todd,

Or you could have downloaded the drivers, extracted & right-clicked the
'inf' file & click install. You could then use them

Your F6 is just to load drivers such as SCSI, SATA... when you get a 'boot
device not found' error on Windows XP setup

The one thing you need to know is that forcing other drivers may have
decreased the spead of data I/O

 

[PA Bear [MS MVP]]

NEVER change the subject in a reply to your thread, please.

 

[Guest]

Todd,

Newsgroup nanny has spoken. We forgot he owns the newsgroups & Internet with
his 2 website memberships & Gmail address

--
SPAMCOP User

 

[ToddAndMargo]

Todd,

Or you could have downloaded the drivers, extracted & right-clicked the
'inf' file & click install. You could then use them

Tried that. Did not work. Still got BSOD after reboot when
changing BOIS to AHCI. Maybe it would have worked if Windows
had been able to boot past the BSOD and seen the AHCI controller
as "New Hardware"

-T