Now, isn't that interesting! The driver that the manufacturer recommends doesn't work for your situation. Even though your device is set up as raid, the raid driver doesn't work for you.

My advice to you would be that since you aren't using the device for it's raid capabilities you should change the bios settings to non-raid setting. Then the driverpack should work as the ultra.sys driver should be used rather than fasttrak.sys.

Now, isn't that interesting! The driver that the manufacturer recommends doesn't work for your situation. Even though your device is set up as raid, the raid driver doesn't work for you.

My advice to you would be that since you aren't using the device for it's raid capabilities you should change the bios settings to non-raid setting. Then the driverpack should work as the ultra.sys driver should be used rather than fasttrak.sys.

Regards,Galapo.

Maybe I'm confused or I have confused you. I have never used the raid configuration. That is why I separated out the ATA 133 ultra driver from the Gigabyte driver pack years ago because it is the only one I need. The XP ultra driver does not work, it requires the Gigabyte ultra driver.

Nevertheless, your device is recognised by the system as raid. Hence these non-raid HWIDs weren't recognised in your tests above: PCI\VEN_105A&DEV_5275&CC_0101, PCI\VEN_105A&DEV_5275&CC_0100 but instead this raid HWID was the one that got you access to your disks: PCI\VEN_105A&DEV_5275&CC_0104. That means that your device is configured by the system as raid, not as something else. It is that configuration which causes the DriverPacks mass storage pack to not work in your situation, as that situation is non-predicatable.

The XP ultra driver does not work, it requires the Gigabyte ultra driver.

Yes, I realise that. We've only ever been discussing the OEM drivers here as far as I was aware.

Nevertheless, your device is recognised by the system as raid. Hence these non-raid HWIDs weren't recognised in your tests above: PCI\VEN_105A&DEV_5275&CC_0101, PCI\VEN_105A&DEV_5275&CC_0100 but instead this raid HWID was the one that got you access to your disks: PCI\VEN_105A&DEV_5275&CC_0104. That means that your device is configured by the system as raid, not as something else. It is that configuration which causes the DriverPacks mass storage pack to not work in your situation, as that situation is non-predicatable.

Yes, I realise that. We've only ever been discussing the OEM drivers here as far as I was aware.

Regards,Galapo.

I just went into the bios. The controller has two options RAID and ATA. I have it set for ATA. But what you are saying is that the MB still reports it as a raid device which then causes the DriverPack to load the incorrect driver? I sure appreciate your sorting all that out for me. I have on numerous occasions regretted having ever put the system drive on that controller. This case is just one of the pains it has caused! (But never quite enough pain to go back and undo it!)

But what you are saying is that the MB still reports it as a raid device which then causes the DriverPack to load the incorrect driver?

Yes, that's what I'd have to suggest is happening. If in the bios you have set it to a non-raid setting, there seems no other explanation which explains the fact that the HWID used by the system for the device remains PCI\VEN_105A&DEV_5275&CC_0104. To me it seems that altering that bios setting is doing nothing.