ilko_t

4- compare output of the 2 batch files, the newest one may give slightly different result, the older one is not necessarily the suitable one. 6- migrate.inf goes to $WIN_NT$~BT folder on the USB stick.

1) What's the exact model of this mini? 2) Can you test with another USB stick, say 1GB or bigger?

Try the option in BIOS too.

What program did you use to prepare the USB stick? 1) You may have to replace grldr file in root of USB stick with any of the latest versions in these packages: http://www.nufans.net/grub4dos/grub4dos-0.4.4.zip http://www.nufans.net/grub4dos/grub4dos-0.4.4-2009-10-16.zip Just take the grldr file in the root of archive and put it in the root of the USB stick. 2) Check in BIOS if you have option how USB storage devices are emulated as- floppy disk(FDD), hard disk (HDD), ZIP...Make it as HDD. 3) What program did you format the stick with?

I'll try to summarize: - you are using USB_multiboot10 - with USB flash stick 2GB you can get letter U: of it during setup on all machines - with USB flash stick > 2GB or SD card of any size it does NOT get U: during setup, on all machines Did I get it right?

Use the latest WinSetupFromUSB. Prepare the USB drive. Start it on the computer in question. Disable card reader in advance. During First part of setup delete all partitions and create new ones. Do NOT continue, use F3 to reboot instead. Start First part again. Drive letters should be fine. Continue with setup. Pay attention which partition you are installing into: Note Partition1 (hidden in this case) and Partition2. Say we installed Windows in C: (partition2). So for the second part, I'd be selecting "Start second part of setup from HD 0 partition 2". If you have customized Windows, using own folder name for Windows directory, make sure that directory name is used in boot.ini on the USB drive. multi(0)disk(0)rdisk(1)partition(1)\WINDOWS What USB disk are you installing from? Is it USB stick or USB hard disk?

To grub4dos boot menu? Just add this to menu.lst on the USB disk: title Boot from first internal disk map (hd0) (hd1) map (hd1) (hd0) map --hook chainloader (hd0)+1 rootnoverify (hd0)

Did you use RAM loaded setup in this case too, not USB_multiboot.cmd/WinSetupFromUSB?In RAM loaded setup there is no reference so far for preserving USB drive letter, I wonder how you made it appear as U in the case above?

Which one is a typo and which one is correct?Are contents of the previous migrate.inf similar, the one which did NOT work properly and gave you letter D during setup? Did you produce migrate_inf.txt on the laptop in question, with freshly installed Windows? We need to compare what prefix was used where you prepared the SD card, and the prefix used on the machine where Windows is being installed onto.

Did you run the script against your drive letter of the sd card? MkMigrateInf_c.cmd G: c:\migrate_inf.txtReplace G: with whatever letter the SD card is. Or http://sourceforge.net/projects/usbhistory/ usbhistory.exe > c:\usb_history.txt Please attach this file, it's quite interesting to dig deeper into this. Yes, replacing the one in ~BT folder.Clarification- migrate.inf is generated by older version of MkMigrateInf.cmd from your local registry, usb_multiboot does not have a 'generic' migrate.inf included.

Have a look: http://www.msfn.org/board/2-t137508.html http://www.msfn.org/board/2-t131770.html Try latest MkMigrateInf.cmd: http://www.msfn.org/board/index.php?act=at...st&id=27356 What is ParentIDprefix of this SD card on the computer you prepare it on, and on the computer you are installing from it?

1) What Windows version did you put on it? 2) Did you select/move the radio button FIXED/REMOVABLE usb disk type? It should be on FIXED for your case.

1) From \WinSetupFromUSB\Docs\HOW-TOs.txt: Program will detect existing Setup files and on the prompt will tell you what to press to add another source, patching the previous one. 2) At what stage it freezes? What's the last thing you see in the screen? 3) Yep, just add all those windows setups as per above and at some point UBCD4Win as well, order I think does not matter, could be even simultaneously with one of the windows sources. @mehboob Thanks, will add it as a mirror.

http://www.msfn.org/board/winsetupfromusb-...-1-t137731.html

A few notes: Using in winnt.sif [setupdata] SetupSourceDevice = \ArcName\multi(0)disk(0)rdisk(0)partition(1) results in broken DosPath in $winnt$.inf, which key is created and used as source path at start of GUI, thus source cannot be found. [Data] floppylessbootpath = "\Device\HardDisk1\partition1" ... ... sourcepath = "\arcname\multi(0)disk(0)rdisk(0)partition(1)\xp_pro\" MsDosInitiated = "0" floppyless = "1" dospath=GLOBALROOT\Device\Harddisk0\Partition1\XP_PRO\ Changing sourcepath to the value of floppylessbootpath (created by Text mode with the proper path where Setup was booted from), before start of GUI using fake setup, results in properly created dospath: floppylessbootpath = "\Device\HardDisk1\partition1" sourcepath = "\Device\HardDisk1\partition1\xp_pro\" dospath = U:\xp_pro\ Just tested this with full XP install till first desktop. Another note- as mentioned in KB article, having unattended section and oempreinstall=yes results in migrate.inf being ignored. During Text mode stick is U:, but at GUI is E: or whatever. http://support.microsoft.com/kb/234048

Nearly done:http://www.msfn.org/board/alternative-loca...p;view=findpost Just has to test a bit a code the changes.

Update- after playing a bit with WinObj found a few more allowed variants for SetupSourceDevice: Migrate.inf used. technet.microsoft.com/en-us/sysinternals/bb896657.aspx SetupSourceDevice = \GLOBAL??\U: SetupSourceDevice = \device\HarddiskVolume2 SetupSourceDevice = \GLOBAL??\STORAGE#REMOVABLEMEDIA#7&16F722A4&0&RM#{53f5630a-b6bf-11d0-94f2-00a0c91efb8b} The first two make sense since they are symlinks to a partition, but can't quite figure out why the third one worked too, since it should be pointing to a device Not yet quite useful, since all of them may vary depending of the number of the disks present or the ParentIDPrefix generated. These two, which I bet on, since there is no drive letter or ParentIDPrefix involved, unfotunately did NOT work: ;SetupSourceDevice = \GLOBAL??\USB#Vid_05dc&Pid_a640#AA04015900000158#{a5dcbf10-6530-11d2-901f-00c04fb951ed} ;SetupSourceDevice = \GLOBAL??\USBSTOR#DISK&VEN_LEXAR&PROD_JD_LIGHTNING_II&REV_1100#AA04015900000158&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} Other unsuccessful attempt: \GLOBAL??\PhysicalDrive1 Now the best part: SetupSourceDevice = \ArcName\multi(0)disk(0)rdisk(0)partition(1) DID work Now with this syntax allowed, knowing that when booted from the USB stick seen as HD we would always know that we can point Setup to it for source files and do not have to use msdosinitiated=1 and ~LS folder, thus no files would be deleted during Text mode and section Unattended should be allowed too.

Disconnect the second disc, with Windows 7 on it, and try again. Where do you want to install XP on? Were partitions on first disk created under Vista/7?

I am comparing menu.lst in \UBCD4Win3.50\plugin\!Critical\ubcd4winToUSB\grub4dos\ with ubcd4win.lst. Locations are the same, the difference is that folder images is Images in menu.lst, with capital "I". This may matter depending on grub4dos version.UBCD4Win 3.50 creates folder "images" inside BartPE folder. ubcd4win.lst has the proper syntax for newest grub4dos versions. I can't see a reason why ubcd4win.lst did not work, besides, no idea what exactly did not work. The reason I am bringing this up is to fix ubcd4win.lst if there is something incorrect in it.

Which program are you using?

What types of partitions you have on the first drive? Is there any valuable data on them? Is it the one you want to install Windows onto? Disconnect the other drive and try again. If it fails again please write what you see on the partitioning screen in Text mode. Mind you- XP Setup will replace bootsector on the first drive, which now most likely is Vista/7 type (loading bootmgr rather than ntldr) and if you format the active partition on the first drive you will have to rebuild Windows 7 BCD store as well, which should be also in the active partition of the first drive. To fix bootsector and rebuild BCD store: http://windows.microsoft.com/en-us/windows...ns-in-Windows-7 http://support.microsoft.com/kb/927392

As for the slow first part- did you use NTFS on the USB stick? Compare speeds: http://www.msfn.org/board/2-t125116.html As for the freezing second part- did you get past the grub4dos screens first/second part and when selected second part it froze? Did the moving "worm" appear at all?

What does "wouldn't load" mean exactly? How far did you go? Switching SATA mode to IDE is a workaround of integrating the proper SATA drivers. Default Windows does not support SATA. So you either use 3rd party drivers, or use IDE and Windows' ones. You can also switch to SATA after Windows has been installed: http://www.msfn.org/board/enable-ahci-inte...xp-t109450.html The generic XP 32 bit must have had SATA drivers integrated, or you were in IDE mode.

Glad you got it sorted Credits for the program are in this thread, several people are involved http://www.msfn.org/board/credits-and-thankyous-t111401.html BTW- did you have to use SP2/3 or just harddisk type and changing 100 to 1?

Use USB-Harddisk, change in txtsetup.sif binifix4.cmd and the other few around to from 100 to 1 as mentioned in the other topic. If no luck- slipstream SP2 at least, or even SP3 or use a source with SP2/3. http://www.google.com/search?hl=en&rlz...amp;btnG=Search