Note for Mustang, K0lo, MudCrab, and Boot Disk Builders & further to this Acronis Forum thread: https://www.wilderssecurity.com/showthread.php?t=200480&highlight=atitlan Just as I was trying to figure out the DriverIntegrator script for use with VistaPE 11, I noticed MudCrab's exhange at the boot-land forum from February 18 re a Silicon Image 3132 driver: http://www.boot-land.net/forums/No-HDD-was-found-t3905.html The chip on my PCI eSATA card is a Silicon Image, the drivers for which are SI3212. Oddly enough the DriverIntegrator script ran 'normally' in my WinBuilder 074. The path to the actual driver files is the same as MudCrab's, excepting the different name of the last subfolder: C:\WinBuilder\Projects\VistaPE\DriverIntegrator\Drivers\Drivers\SiliconImage3112 In the event, the Boot Disk burned from the iso built with the 3112's 'Integrated' yields VistaPE recognition of the eSATA drive; hot-swapping, as in Vista; and about half the time for all ATI 11 VistaPE Plugin operations in comparison to a USB 2 connection. Absent the DriverIntegrator script, two earlier version 11 VistaPEs would not 'read & load' the eSATA drivers located in C:\Drivers. This seems to work for Network drivers from what I have read, but not for Mass Storage drivers — at least not my eSATA's. I imagine as VistaPE evolves, the 'your mileage may vary' experience of individual builds and special cases will diminish.