ilko_t

@300 Please look at this topic, it's about the very same problem and has a quick workaround and another sollution: http://www.msfn.org/board/index.php?showtopic=133164

You may be better off with Wimb's tool: http://www.msfn.org/board/index.php?showtopic=121446 The problem is x64, which using this method of install will delete some files during file copy phase in text mode, so you'd need to synchronize your x64 source with contents on USB stick after each setup. As for adding various Linux distros- look at this post for a generic solution: http://www.msfn.org/board/index.php?showto...st&p=845651 Or search on grub4dos forum: http://www.boot-land.net/forums/index.php?showforum=66 Latest Kubuntu may work in a similar way: http://www.boot-land.net/forums/index.php?...ost&p=64856

I am getting the same thing when trying XP for a Dell Optiplex 745, or a Dell GX280. Have we found a solution for this yet? The answer is just a couple of posts below the one you quoted, it's also in the FAQs thread: http://www.msfn.org/board/index.php?showtopic=116766 http://www.msfn.org/board/index.php?showto...st&p=786908

Assuming you put XP setup on it: 1. Format it using HP USB format tool, use the one which comes with WSFUSB. 2. Use grubinst_gui.exe to install grub4dos bootsector on it 3. Copy grldr and menu.lst first 4. Copy the rest of the files in root next 5. Copy ~BT folder 6. Copy ~LS folder last This will take longer than if you just run WSFUSB again and prepare the new stick with it. Or are both stick 100% similar? You may try to create an image and put it back on the other stick: http://www.roadkil.net/program.php?ProgramID=12 http://dubaron.com/diskimage/ http://www.boot-land.net/forums/index.php?showtopic=1299

Have a look here:http://www.msfn.org/board/index.php?showto...st&p=797585 http://www.msfn.org/board/index.php?showto...st&p=815048 And the "historical" thread, which covers all basics: http://www.msfn.org/board/index.php?showtopic=61384 I guess the first two links should be pretty close to a tutorial. Nope, there is something else wrong going on. This part is NOT just for testing boot or recovery options. Why it didn't boot and separate problem, you need to provide more details what you performed, what files system was used on the USB stick etc.Bootsector is something different, it's not copied from the DVD anyway. Please run the following command in CMD window, replacing G with the drive letter of the DVD drive: dir /a /s G: > c:\windows7.txt Put in a zip archive your WinSetupFromUSB.log, found in program's directory, all date-time-log.cab files, found in \backups\ directory and c:\windows7.txt. Upload the zip file here, or on datafilehost.com or similar hosting site. The option which does not work for you has been used on number of machines to prepare Vista and 7 for installation and never gave a glitch. Did you format the USB in FAT16 by any chance?

Wait a second, you need to put Windows 7 on the USB stick, right? Then use the appropriate field, I guess you are using the one for 2000/XP/2003, do NOT. Use the appropriate field and select the root of the DVD: Initially I thought you run the program on Windows 7, not that you need to put 7 on USB stick.

Are you selecting I386 folder itself? Do not, select its parent folder, which contains I386.

Here is a little set of files, which allow you to switch easily to ACHI or move Windows to Intel ICH controller. What it does: 1. Creates the needed entries in HKLM\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase for the following HardwareIDs: PCI\VEN_8086&DEV_24DF&CC_0104 PCI\VEN_8086&DEV_25B0&CC_0104 PCI\VEN_8086&DEV_2652&CC_0104 PCI\VEN_8086&DEV_2652&CC_0106 PCI\VEN_8086&DEV_2653&CC_0106 PCI\VEN_8086&DEV_2681&CC_0106 PCI\VEN_8086&DEV_2682&CC_0104 PCI\VEN_8086&DEV_27C1&CC_0106 PCI\VEN_8086&DEV_27C3&CC_0104 PCI\VEN_8086&DEV_27C5&CC_0106 PCI\VEN_8086&DEV_2821&CC_0106 PCI\VEN_8086&DEV_2829&CC_0106 PCI\VEN_8086&DEV_2922&CC_0106 PCI\VEN_8086&DEV_5029&CC_0106 PCI\VEN_8086&DEV_27C6&CC_0104 PCI\VEN_8086&DEV_2822&CC_0104 PCI\VEN_8086&DEV_2824&CC_0106 PCI\VEN_8086&DEV_282A&CC_0104 PCI\VEN_8086&DEV_2923&CC_0106 PCI\VEN_8086&DEV_2929&CC_0106 PCI\VEN_8086&DEV_3A02&CC_0106 PCI\VEN_8086&DEV_3A03&CC_0106 PCI\VEN_8086&DEV_3A22&CC_0106 PCI\VEN_8086&DEV_3A23&CC_0106This should cover ICH5 up to ICH10, including a couple of OEM specific HWIDs. 2. Creates the relevant services- iastor55, iastor70, iastor78 and iastor86 3. Copies iastor55.sys, iastor70.sys, iastor78.sys and iastor86.sys to \system32\drivers\ 4. Copies the relevant and modified inf and cat files to \windows\DR\ and adds this location to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath, preserving any existing values in this key, so Windows can find and use the appropriate driver from this folder upon new hardware detection. The driver versions and HWIDs are as per BTS mass storage DP 9.01 I1-I4. Thanks to BTS DriverPacks team for this great project. Intended for 32 bit XP only. Has been tested already on a few machines, having multiple iastor services seems to cause no harm. Not tested, but updating manually the driver with original one through Device manager or installing Intel matrix storage pack may not be not good idea as this will create another iastor service. Just in case- use F8 at Windows start and "Last known Good Configuration" if you get any issues after installing this. http://www.datafilehost.com/download-a548acb9.html

Thanks for the kind words 1) You should be safe to do so, just do it AFTER formatting the USB stick and praparing it with WSFUSB. The reason is that some BIOSes won't find the boot files if they are placed beyond certain boundary. 2) If you will be installing XP 32 bits SP2 or SP3 then there should be no files deleted. If it's XP x64, 2003 or 2000 then there is a quick workaround since you have 30 similar machines or all they have 1 internal hard disk and no card readers attached, just say if you need details. 3) You should be safe to move it elsewhere as well as you can initially install it elsewhere, preferably in path without spaces in it, although this should be already fixed but not thoroughly tested. 4) No, this would not grow your resulting Windows folder.

This has something to do with GrubInst.exe, which is external tool from grub4dos package. If you don't mind please post at grub4os support forum the information above, where its authors may help troubleshooting and release a fix if needed. http://www.boot-land.net/forums/index.php?showforum=66

Sorry, I have no experience with such large USB sticks, so can give ideas only. Did you try using NTFS rather than FAT32? It's preferred for speed as well. You may also try MulTiPartitionUSBstick folder and the relevant batch files within to install a filter driver, which will show USB stick to windows as USB hard disk, thus allowing partitioning and proper formatting from Disk Management, just like with ordinary hard disks. You need to set the first partition active. This would work on 32 bit Windows only, XP is tested, no idea about 2003/Vista/7.

Try this: http://www.msfn.org/board/index.php?showto...st&p=835001 Grubinst.exe is in \winsetupfromusb\files\grub4dos\ HD Hacker is in \winsetupfromusb\files\tools (hd1,0) in your case would be (hd2,0) if nothing is unchanged since the log files attached was produced. (hd0,0) is the first hard disk in the system/first partition, do NOT use it. You may use grubinst.exe -l (hd1) or grubinst.exe -l (hd2) to display partition information and compare sizes, then figure out what hdX is the USB one. There is a file in \winsetupfromusb\files\grub4dos\ calles grubinst_switches. Please post the output of grubinst.exe (hdN,0) and whether HD Hacker displays grldr string in the bootsector. If you need further clarification what exactly to do- please ask, do not try steps you are not sure what they does as some of them could be destructive if used on the wrong disk.

Nice catch, thanks.

Do you install on a SATA hard disks in both occasions? You mentioned that you have disconnected a SATA disk, where did you install to then? Try to slipstream BTS mass storage drivers in your source and rebuild the stick. Here is a similar thread: http://www.msfn.org/board/index.php?showtopic=128718

Many thanks to cdob and pipster for revealing the truth behind these mysterious cases, when migrate.inf was not taken into account. BTW- Pipster, I wish all the guys asking for support had your patience and returned in a similar manner the requested information, thanks.

What machine did you boot the USB stick on? How did you select to boot off the USB device- an option in BIOS or F12,Esc or similar key during POST?

Seems for some reason grub4dos bootsector was not installed. Did you have anything on the USB stick before using the program? Did you format the stick and then place whatever you put on it? To get you going quickly- open up boot.ini on the USB stick and add a line on the bottom: c:\grldr="Start Grub4Dos" Use this boot entry then continue as usual- first part then second part of setup. Please put in a zip archive and attach WinSetupFromUSB.log file from program's directory along with DATE-TIME-log.cab files found in folder BACKUPS, lets investigate why this happened.

Sorry, my bad, a lot of information after midnight...

Quite interesting, thanks for all the reports. So RemovableMedia#8 made the difference. In old windows it's 8, in the new install it's 7. Reading this and cdob's link reveals the bolded part is ParentIdPrefix. \??\STORAGE#RemovableMedia#8&141a0a73&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} Cdob raised the question: Search at microsoft.com shows no clues for the changing number, a lot to be read from Google results.Another interesting quite from the links above: So by detecting the latter we may know that migrate.inf drive lettering may not be applied and by putting in it multiple entries for RemovableMedia#7 , 8 (any others used for USB mass storage devices?) we might get around similar issues. @pipster Does the new PC have any card readers? As far as I remember you tried the USB stick on other computers, did any of them have USB card reader or any similar USB mass storage device- USB MP3 player, printer with card reader, phone connected via USB etc. etc. ? Do you have on the old computer an USB hub or PCI USB card? Where do you connect the USB stick to?

Happy the read everything is fixed now

You most likely do not have MBR. Try zeroing the first 100 sectors of the USB stick: http://www.boot-land.net/forums/index.php?...ost&p=32296 Unplug it using safely remove hardware icon, plug it back in and then format it with HP USB format tool included in WSFUSB. If you find the above complicated ot do not understand what to do, do not risk. This way below will take longer, but is much safer- download this: http://www.killdisk.com/downloads/killdisk2.zip Use KD_WIN.EXE, select the USB stick itself, NOT the drive letter below it. Use F10 to zero out all sectors. Unplug, replug the stick and try to format it with 2.0.6 version of HP utility. If stick is not displayed again in it use 2.1.8, but use Beeblebrox afterwards to ensure you have set active partition. Post again WinSetupFromUSB.log file, to attach it simply add it to a zip archive, or change extension to .txt.

What version did you use of HP format tool? The ones after 2.0.6 (included on WSFUSB) do NOT set active partition, thus the program will not show it as a valid device. WSFUSB shows only devices with MBR and active partition set as stated in the tooltips and readme.txt. Please attach WinSetupFromUSB.log file found in program's directory, it may reveal something interesting. Now get Beeblebrox and check if the first partition is set as active (80), you most likely have 00 in boot column. Set it 80 and save changes. Make sure you are working with the correct disk. Unplug the USB stick and replug it. Start WSFUSB, its the stick recognised now? Alternatively you can format it with other tools, check this post: http://www.msfn.org/board/index.php?showto...st&p=852405

What exactly happens when you boot on them? Freezes on black screen or blinking cursor? Boots the internal disk? What exactly? How large is the USB stick? What tool did you use to format it? In what file system? Do you copy anything to the USB stick, before launching USB_multiboot? Do not, do it afterward.

What tool did you use to format the USB stick? Use the included HP USB format tool if you did not, use NTFS for speed. Attach WinSetupFromUSB.log file found in program directory.

Thanks cdob, quite interesting, as usual. Reading http://www.uwe-sieber.de/usbtrouble_e.html it appears that if no serials are present upon change of USB port stick will be detected as a new one. This would explain why getting another USB stick helped the other user with the same problem- the second one had USB serial number. Maybe OP had bad luck with the second stick he tried, not having serial number as the first one Will be waiting for pipster's results from USBDeview, hopefully this will reveal the mystery.