Alter

You can find this list inside any of INFs. If sysprep requires some specific format of this list - tell me and I'll add this format generator.

I'm not sure if you can replace PCIIDE.SYS with UNIATA, since PCIIDE (and PCIIDEX) is used by other ATA drivers like port driver. It does common work for ATA controllers and leave controller-specific staff for vendor's drivers. To avoid conflicts I tried to disable both these drivers. UNIATA can be used instead of other drivers of onboard dual-channel IDE controllers in most cases. I know only about some problems with ICH4, but there was no possibility to debug driver with this controller. Another thing, that I was proposed is to add the following registry values: HKLM, "system\currentcontrolset\control\CriticalDeviceDatabase\pci#CC_0101", "Service", %REG_SZ%, "uniata" HKLM, "system\currentcontrolset\control\CriticalDeviceDatabase\primary_ide_channel", "Service", %REG_SZ%, "uniata" HKLM, "system\currentcontrolset\control\CriticalDeviceDatabase\secondary_ide_channel", "Service", %REG_SZ%, "uniata" this guarantees, that UNIATA shall be loaded by PNP manager, but I could not integrate these settings into INF file. What about 2 INFs for XP: I've made them because it doesn't matter for driver, how the controller is exposed to system in device manager. Because actually system requires storage devices to be representred as SCSI. There is some difference for PNP manager only. In some cases it likes MassStorage/SCSI INF, in other - IDE. I don't know why. I'd be thankful for any help on it.