MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically.

Recommended Posts

Ok for this one, I followed the instruction to update the VIA SATA RAID controller device in Device manager and browsed to the folder that only has uataxp.inf in it. It did not change the VIA device but instead put a flagged device into Other devices. I then installed the driver for that, and now under System there is a UATA Virtual Communication Device. That driver is in the root of the Release folder of the driver download. The instructions do not mention having to install this device.

This particular computer does have the IDE controller also, but the only thing connected to it is a DVD drive.

Now having rebooted with this UATA driver installed, it doesn't seem to make any difference. It still shows the inaccessible drive (now E) in My Computer, and the same "healthy" extent sized volume in Disk Management.

Share this post

Link to post

Share on other sites

Yes I had moved the INFs to different folders because it specifically says to use one vs the other depending on the controller. So I moved the H to a different folder so Windows could only pick the INF I wanted.

Quote

10. enter path to .INF file for new driver

If this is usual onboard IDE controller, use
C:\temp\uniata\Release_Dist\uata_xph.inf
If this is IDE RAID controller or additional PCI IDE controller, use
C:\temp\uniata\Release_Dist\uata_xp.inf

So since this is a "VIA SATA RAID" controller, I didn't want Windows to try to use the uata_xph.inf so I took it out of the folder.