Hmmm, let's see if I can put down a "schematics" of your idea in the way I may be able to understand it:
The USB stick (modified with Manufacturer's Tool) has two parts, LUN1 (CD-ROM) and LUN2 (HD-Like device).
Th PC is booted from the LUN1 (CD-ROM), which contains:grldr
as no-emulation bootsectormenu.lstWHAT ELSE?
The LUN2 (HD-Like device) contains:\I386WHAT ELSE?
The point you seem to have not fully considered/understood is the way NTLDR or SETUPLDR.BIN actually boot.
Until you are in "real mode" (read Text Mode, including BOOT.INI choices or the blue screen SETUP) the information from BIOS (and the ones "faked" by grub4dos) are trusted.
As soon as you "switch" to "protected mode" (read black screen/loading progress bar) ANY info from BIOS (and from grub4dos) is ignored, it simply vanishes in thin air, a new scan of the hardware is performed and unless a given hardware is found AND an appropriate driver for it is loaded, the booting will be aborted, possibly with a 0x0000007b BSOD STOP ERROR.
The exception being that of a driver that is loaded "forcibly".
The only known one to be working is the RAMDISK.SYS driver used in conjunction with the SETUPLDR.BIN coming from SERVER 2003 SP1 or R2 (NOT "gold", NOT SP2).
There may be other possible ways, but it seems like the topic is not of much interest:http://www.boot-land...?showtopic=1507http://www.boot-land...?...c=5512&st=7http://www.boot-land...?...c=5512&st=9
Would you be "game" for this?
The "trick" of the "XP kansas City Shuffle" is simply that of loading through grub4dos mapping a smaller image that appears to the NT booting IDENTICAL to the actual partition on hard disk.
During "real mode" the mapped image is accessed, during "protected mode" the real partition is loaded.
This allows for two newish things:
1) booting from USB on computers with no or defective booting from USB support
2) speed up the booting on computers with USB-2.0-chips-but-only-USB-1.1-speed-support-while-booting, since only the files in the smallish mapped image is loaded with the USB BIOS routines whilst the large number of files on the partition are loaded through the native NT drivers, at USB 2.0 speed
In the particular case you posed, it could have the "advantage"
of having a "fixed" LUN1 booting (but still with the "USB_multiboot" tricks) a "variable" part on LUN2, in other words you would only need to run the Manufacturer's Tool once and setup the DISK SIGNATURE of the LUN2 once, after which you would be free - within limits - to change the contents of LUN2 with ordinary file tools.
Edited by jaclaz, 21 December 2008 - 10:11 AM.