jaclaz

Pfff, now I see. You want to find the way Xp generates the value 7&16f722a4&0&RM in your example , and find a way to generate it under Windows 7. What does Windows 7 has in here?: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\DeviceClasses\{53f5630a-b6bf-11d0-94f2-00a0c91efb8b} HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\DeviceClasses\{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\STORAGE\RemovableMedia jaclaz

Well, if you thought that booting Linux on another key formatted with FAT is enough proof that ANOTHER key formatted as FAT32 or NTFS and witha Windows XP MBR and bootsector will boot, by now you should have been convinced by the evidence. You may want to read FAQ #10 here: http://home.graffiti.net/jaclaz:graffiti.n...SB/USBfaqs.html I don't understand the question. I gave you a link to FOUR different and LATEST approaches to increase the bootability of a stick, try first one: http://www.911cd.net/forums//index.php?showtopic=21702 http://www.fuwi.ethz.ch/files/USB-Boot_Utilities.zip if it doesn't work, try second one, etc, etc. As ilko_t suggested, zeroing out first few sectors is a guarantee that the tools "start from scratch" avoiding the (unprobable but possible) "influence" of previous "wrong" data on the stick. jaclaz

From the given site: Here: http://www.ftdichip.com/Drivers/VCP.htm Zip: http://www.ftdichip.com/Drivers/CDM/CDM%20...20Certified.zip Installer: http://www.ftdichip.com/Drivers/CDM/CDM%202.04.16.exe No problem at all, it will create a "fake" COM port (just like the USB to RS-232 converter talked about in the thread). jaclaz

@teryx510 The problem can be easily solved by using grub4dos or a similar bootmanager, see here: http://www.msfn.org/board/index.php?showtopic=86373 More updated data here: http://www.msfn.org/board/index.php?showtopic=133418 and of course here: http://www.boot-land.net/forums/index.php?showforum=66 @Wrex bootfix.bin is NOT called by ANYTHING if not by the no-emulation bootsector on CD/DVD. You should read this: http://www.msfn.org/board/index.php?showtopic=133418 jaclaz

ilko, maybe I am still missing something, but do you have any reason/experience/documentation supporting the idea that a migrate.inf file is read at all during Windoows 7 setup? jaclaz

Use THIS guide/page: http://www.msfn.org/board/index.php?showtopic=133387&hl= http://www.mapleleafmountain.com/seagatebrick.html as reference. However, original images were re-posted on this same thread by member pichi, here: http://www.msfn.org/board/index.php?showto...807&st=1243 jaclaz

Well, no. (I mean yes ) As long as the image is SMALLER than 512 Mb AND you have at least 1 GB of memory, it is possible to use a RAMDISK approach using the known Server 2003 SP1 or R2 files. (and of course you need a license for Server 2003, or for ERD 2005, that includes those files) OR, regardless of the .iso size, Diskless Angel is a working, Commercial solution, though noone has published anything about actually using it during setup. jaclaz

Sure , just out of curiosity how much you still have in your pocket of the US$ 30.00 you took for "entertainment expenses"? And what happens if you forget your stick in (which was the OP problem question)? jaclaz

What you were told. Try using the given apps. I'll quote myself, with bolding and underlining what you might have missed: A test with another key (and another "family" of OS ), does not prove in any way that the 8Gb key is booting on your PC. (which obviously is what is completely failing to happen, most probably due to a "wrong" partitioning/formatting of the stick or to some "peculiarity" of the motherboard) jaclaz

OK, then I simply don't get it. This (the windows 7 contents of HKLM\SYSTEM\MountedDevices--> DosDevices) : _??_USBSTOR#Disk&Ven_LEXAR&Prod_JD_LIGHTNING_II&Rev_1100#AA04015900000158&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} Seems to me similar to the contents of the key HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\DeviceClasses\{53f56307-b6bf-11d0-94f2-00a0c91efb8b}\ on my XP: ##?#USBSTOR#Disk&Ven_USB&Prod_DISK_2.0&Rev_1219#O29OXXJDI4BOBM6F&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} Another one: ##?#USBSTOR#Disk&Ven_OTi&Prod_Flash_Disk&Rev_2.00#130B5F43D7479CD7&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} See below: _??_USBSTOR#Disk&Ven_LEXAR&Prod_JD_LIGHTNING_II&Rev_1100#AA04015900000158&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} ##?#USBSTOR#Disk&Ven_USB&Prod_DISK_2.0&Rev_1219#O29OXXJDI4BOBM6F&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} ##?#USBSTOR#Disk&Ven_OTi&Prod_Flash_Disk&Rev_2.00#130B5F43D7479CD7&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} What was the question? Was it not how to create the contents of the DOSDEVICES key on a non-Windows 7 system? Can you expand on it? jaclaz

The "scheme" in the Windows 7 snippet you posted is remarkably similar to contents of key: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\DeviceClasses\{53f56307-b6bf-11d0-94f2-00a0c91efb8b} in my XP (example): HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\DeviceClasses\{53f56307-b6bf-11d0-94f2-00a0c91efb8b}\##?#USBSTOR#Disk&Ven_USB&Prod_DISK_2.0&Rev_1219#O29OXXJDI4BOBM6F&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} jaclaz

There are several threads already opened, related to this. See here: http://www.msfn.org/board/index.php?showtopic=84411 http://www.msfn.org/board/index.php?showtopic=108515 http://www.msfn.org/board/index.php?showtopic=110914 http://www.msfn.org/board/index.php?showtopic=128727 http://www.msfn.org/board/index.php?showtopic=130645 http://www.msfn.org/board/index.php?showtopic=131620 http://www.msfn.org/board/index.php?showto...1620&st=105 jaclaz

BOTH the symptoms you report are NOT due to WinsetupfromUSB, but rather to the way the USB stick was partitioned/formatted. Probably you have a somehow "peculiar" motherboard. Try the apps listed in this post: http://www.msfn.org/board/index.php?showto...87993&st=17 Make sure that you can boot something from that USB stick, fuwi's batch should be a good enough test. jaclaz

As ANYTHING in life, doing it can be right, OVERdoing it is always wrong. jaclaz

Well, NO. AFTER having solved the bootsector problem, he couldn't get it working by copying and pasting the engine.de settings, while the attached files made it working. In the same thread, OP had problems with SP3: http://www.msfn.org/board/index.php?showto...19963&st=30 It is very probable that you are using a somehow modified SOURCE. Use a "pure" XP SP2 one. About FiLeNaMe BeInG CaSe SeNsItive, of course it is important on CD-ROM, but on it it should be UPPER CASE. , on FAT16/FAT32/NTFS I can assure you that it is normally as well UPPER CASE. What are you using to create the .iso? With WHICH options? At WHICH speed and with which app/settings are you burning the CD? Have you tested the .iso in a VM such as VirtualBOX or even better (but slower) Qemu? To re-cap: Forget (momentarily) about USB. Do to your "clean" SP2 Source the modifications needed along the ngine.de Tutorial. Use the patched (SP2) NTDETECT.COM Double and Triple check everything. Create a .iso. Test the .iso by performing a "normal" install in a VM. Only if the above works smoothly try burning the CD and perform the actual USB install. Additionally: Use ONLY a "pure" text editor such as NOTEPAD to modify .sif/.inf/.reg files. Be very, very careful when copying/cutting/pasting on .sif/.inf/.reg files, they are rather "sensitive", you may introduce by mistake an unprintable character like a TAB, a LF or whatever that may "break" them. jaclaz

Hey peeps . When replying to a thread, please do check DATE of last post. I sincerely hope that in 6 months stiffy420 found a way to solve the problem And besides jeff1971lee was reporting a solution, NOT a request. jaclaz

Besides the "easy" approach through the "reversed Dummy disk" Filter Driver, one could use a migrate.inf file to assign a drive letter to the USB hard disk, though this limits some Unattended settings. There may be also another (complex, UNtested and really NOT advised) possible way, along the lines of the "no more CATCH 22" trick for Recovery Console: http://www.911cd.net/forums//index.php?sho...20983&st=25 i.e. pre-creating a "fake" previous install, which will probably consist of just a couple of directories and a very stripped down HKLM/SYSTEM hive including Mounteddevices and possibly some other keys/sub-hives jaclaz

You may have better luck with the patcher: http://www.911cd.net/forums//index.php?sho...=19235&st=2 http://www.911cd.net/forums//index.php?sho...181&st=1986 jaclaz P.S.: Forget the above. This is the first report I ever saw about a Windows filesystem/app being CaSe SensItIvE. Are you sure of your last edited post? Have you tried the files I gave you a link previously?

There may be some problems with copy/paste the files from the engine.de Tutorial. Check this: http://www.msfn.org/board/index.php?showtopic=119963 http://www.msfn.org/board/index.php?showto...19963&st=23 jaclaz

...not partitioned and with a MBR. jaclaz

Do a loopback test, see here: http://www.msfn.org/board/index.php?showto...8807&st=384 http://www.msfn.org/board/index.php?showto...807&st=1194 jaclaz

You are very welcome. We try to deliver solutions. FYI (since you are not afraid to "dirty your hands" ) a seemingly unrelated, but interesting thread/approach: http://www.boot-land.net/forums/index.php?showtopic=7138 jaclaz

Good. Since you use grldr in such a "vertical" way, you can even rename it to something specific, like WinPEx86. jaclaz

You need a migrate.inf file. Search for "mkmigrateinf.cmd", "mkmigrateinf2.cmd" "mkmigrateinf_b.cmd" jaclaz

Since you use timeout 0, you may want to edit the "embedded" menu in grldr and get rid of menu.lst, too. For the record you do NOT need a "boot" command in a menu.lst entry. "boot" is implied (and executed) when another "title" line is found or end of file is reached jaclaz