We have functional AsMedia USB 3.0 !
Wow, was surprised myself and "man" I still don't know what it was.
1. Made and Copied XP.ISO (and winvblock.ima) to USB 2.0 :
- IntegrateDrv:
1a. Intel DMI 2.0 PCIx-PCI driver (microsoft driver copied from XP - I simply checked devmgmt for driver files and copied those with oem inf this also can be done by Intel Server board driver which all in all should be faster and more reliable)
[Unsure if this step is nessessary for AsMedia controller, BUT couldn't get it working on below only]
1b. USB 3.0 drivers (Generic HUB + USB Root HUB + correct XHCI Controller)
1c. Wait4UFD
- Loaned winvblock floppy .ima (thanks to sha0)
2. Every single thing on-board disabled (Z68 board so it has S ATA-2 and S ATA-3 controllers, JMicron IDE controller, all sort of BT's and NICs etc..)
- Disabled every last thing of the board(Everything from Bluetooth to SATA to NIC what ever I could disable) except 2 USB devices:
* AsMedia USB 3.0 (USB 3.0 Legacy Emulation: Enabled)
* Intel USB 2.0 (USB 2.0 Legacy Emulation: Enabled)
* EHCI hand-off disabled
* Both USB Media: USB-HDD / USB-Hard Disk: Forced
3. Booted to USB 2.0 8GB with G4D installed with options:
; <<<<<<<BOOT from USB drive>>>>>>
title Here We come BSOD.. TXT
find --set-root --ignore-floppies /XP.ISO
map --mem /XP.ISO (0xff)
map --mem /winvblock.ima (fd1)
map --mem /winvblock.ima (fd0)map (hd1) (hd0)
map (hd0) (hd1)
map --hookchainloader (0xff)
boot
title Here We come BSOD.. GUI
find --set-root --ignore-floppies /XP.ISO
map --mem /XP.ISO (0xff)
map --mem /winvblock.ima (fd1)
map --mem /winvblock.ima (fd0)map (hd1) (hd0)
map (hd0) (hd1)
map --hookroot (hd0,0)
chainloader /ntldrboot
title Here We come BSOD.. First Careful identical boot
map (hd1) (hd0)
map (hd0) (hd1)
map --hookroot (hd0,0)
chainloader +1
boot
; <<<<<<<BOOT from VHD at USB drive>>>>>>
title Here We come BSOD.. TXT
find --set-root --ignore-floppies /XP.ISO
map --mem /XP.ISO (0xff)
map --mem /winvblock.ima (fd1)
map --mem /winvblock.ima (fd0)find --set-root -ignore-floppies /XP-1.VHD && map /XP-1.vhd (hd0)
map (hd0) (hd1)
map --hookchainloader (0xff)
boot
title Here We come BSOD.. GUI
find --set-root --ignore-floppies /XP.ISO
map --mem /XP.ISO (0xff)
map --mem /winvblock.ima (fd1)
map --mem /winvblock.ima (fd0)find --set-root -ignore-floppies /XP-1.VHD && map /XP-1.vhd (hd0)
map (hd0) (hd1)
map --hookroot (hd0,0)
chainloader /ntldrboot
title Here We come BSOD.. First Careful identical boot
find --set-root -ignore-floppies /XP-1.VHD && map /XP-1.vhd (hd0)
map (hd0) (hd1)
map --hookroot (hd0,0)
chainloader +1
boot
ERROR NOTE: Because USB 3.0 is still recognized as removable for some odd reason Windows XP will notify you that 'pagefile.sys' cannot be used or missing at GUI mode setup. Ignore this as you won't be using pagefile anyway. However, paging file is still created and in case of my VHD testing it was created to USB you still want to disable it.
4. #:
* Removed USB 2.0
* Re-enabled everything disabled at stage 2 from BIOS back up. (Which seems now booting up just fine even with RAID/AHCI enabled.)
* Direct Booted to USB 3.0 Flash Drive
Few suggestions to original what to disable at first boot:
Further more of 'Wimb' IMG_XP I would advice disabling event viewer and all counters operations(HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control <- you will find every single thing in here, but more information on web if you search how to disable counters at web and I think there is even tools made for this) from system, hybernate files (if even created) and everything that could possibly write anything to flash, if you need an RW space for caching anything or writing. I would suggest that you mount ram drive for this purpose and automate the windows internal or 3rd party write-ups there you most likely only need really minor 64-256M ram drive for this purpose (for example read to ram and caching file search would be idea).
5. (general testing schenarios):
* Tested this setup against IMG_XP project by Wimb: Works clean up without registry modifications (unless IntegrateDrv adds some) while integrating drivers.
-VHD has to be at USB 3.0 while XP is installed. There is no way in hell you move it after install to USB 3.0 (I tested this quite a bit 'too much, rofl'). So, just beaware that install it while VHD at USB also for some reason I could not get this working while only 1 USB drive was used had to do exact above from USB 2.0.
@tal.alone
Sorry to hijack the topic for so many posts and that above novel.
Edited by genetix, 14 August 2013 - 06:17 PM.