I don't think you should be rebuilding next versions just yet. There's more to add when the time comes to get new package up and current is working and fixable for now.
Well, technically you don't wanna use Wait4UFD for USB 1.1/2.0 and only patch the Wait4UFD itself as this gives more control like your "UsbBootWatcher'-check patching on VHD_fix side. I do think you should separate and point me to the location what .reg is used to modify the 'Boot Bus Extender = 0' and to where by the current fixer because that list is identical idea as 'Mass Storage'-devices and I think everything patched to registry should be located same place as they are all mass storage devices.
"C\U\I"-Intel, no, I don't think I wanna support driverpacks idea it was bad from begin with. I can as well mount and direct edit the registry for myself for Intel USB 3.0 controller for XP. You are currently including 1 driver fopr these controllers already and some odd script companied with it. Following standard like DriverPacks for this kinda project is good, but when "we" are already fixing every damn driver in there and like I did even created whole damn scripted installs like txtsetup.oem files for each mass storage device, well.. Although, thinking usage of driverpacks 7-zip files. Because all you would need to do is for example include the .7z to the driver where the VHD is for example and extract .sys files only while doing that. This would give better end result than including driver packs.
Edited by genetix, 30 August 2013 - 09:25 AM.