ilko_t

1) You may have to wait longer for 700MB ISO, perhaps the real hardware was using USB 1.1 at boot. Alternatively try Plop: http://www.boot-land.net/forums/index.php?showtopic=8605 For loading in VirtualBox- same applies, no idea if PLOP could help. 3) Yes, critical for the GUI mode, which you have not reached yet.

@demontager 1) How large is the ISO file? 2) How much RAM you had in the real and the virtual machine? 3) Not related, but did you put original setup.exe as setuporg.exe in \setup\I386\ in XP_INST.IMA? Mount the image, use ImDisk for example, put setup.exe renamed to setuporg.exe in \setup\I386\ if using 32bit Windows and unmount the virtual disk. Make sure you are not monting it as read-only.

Hmm, my lengthy post disappeared... Anyway, You need to add another line, just below C:\btsec\XPSTP.bs.... multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Second part of XP Professional setup from hd 0 part 1" /FASTDETECTsince you are installing in partition 1 and you will be using it. This line, with partition 1, was present in boot.ini in post #3, you had to correct only disk(1) to disk(0). Where did it disappear? BTW- where do you get all thise boot.ini's from? You said you used WinSetupFromUSB, boot.ini posted is from usb_prepare.cmd or usb_multiboot.cmd, with wrong disk () values... How this mess is happening? @Wimb- there are no issues with drive letters, just wrong disk() values, which should be 0.

Just edit boot.ini on the USB stick changing all disk(1) to disk(0). How did it get changed in first place? What you posted is not default boot.ini...

That's weird. Do you have any USB card reader, mobile phone, iPod etc. connected to the computer being installed? Did the Text mode part work fine, no errors, missing files etc. ?

Are you using modified Windows, which may install in another directory, not Windows? Zip and attach winnt.sif in ~BT folder and txtsetup.sif from USB root. What Windows version are you installing?

Did you delete ALL partitions during Setup and create a new one? ?

What do you have in boot.ini on the USB stick? As I get it you have one partition only on the internal hard disk, where Windows is being installed to, right?

Don't delete anything. Setuporg.exe which has to be placed in XP_INST.IMA \setup\ : 1) In case BTS driver packs were used, or any other method using "fake setup" at start of GUI- just use I386\setupORG.exe, which should be the original MS setup.exe. 2) Original media/unmodified setup.exe- extract it from I386 (7zip or default MS expand.exe) and rename it to setuporg.exe. Don't worry about winnt.sif for now, that's optional.

The issues with those files not found is because there are duplicated entries about them in txtsetup.sif: ie4uinit.mui = 1,,,,,,,2,0,0,ie4uinit.exe.mui ie4uinit.mui = 1,,,,,,,1005,0,0,ie4uinit.exe.mui .... iedkcs32.mui = 1,,,,,,,2,0,0,iedkcs32.dll.mui iedkcs32.mui = 1,,,,,,,1005,0,0,iedkcs32.dll.mui ... mshta.mui = 1,,,,,,,2,0,0,mshta.exe.mui mshta.mui = 1,,,,,,,1005,0,0,mshta.exe.mui and so on. This way mshta.mui should be copied to \windows\system32 and renamed to mshta.exe.mui, as well as to \windows\system32\en-US\. Default behavior of setup when launched from HD-like media, having msdosinitiated=0 in WINNT.SIF is to delete files as they are extracted in order to preserve disk space, by default those files in ~LS and ~BT folders are considered temporary. This method of installing avoids that behavior by write-protecting USB via registry entry, read from migrate.inf during Text mode. Thus Setup attempts to delete files are unsuccessful. This registry entry works for XP SP2/3 x86 only. Apparently, when a file has been attempted to be deleted, it's marked as deleted, although it's still on the USB media, maybe write cache plays role here, cannot comment further. As the file is considered as deleted, next attempts to copy the same file will fail with error "file not found". Original MS media does not have duplicated entries in txtsetup.sif. No idea if those files should be present in both directories too. The media you have would fail with the same errors if Setup is started from Winnt32.exe, as this time those files will be deleted indeed and the error message will be "true". When the same source is used from a CD-like media, those errors don't happen, as the files are not deleted, or attempted to be. This would not happen if using this, as msdosinitiated=0 tells Setup not to delete files: http://www.msfn.org/board/index.php?showtopic=119742 Which method is what Wimb uses in his program. Hope that helps you understand the process and your issues.

That's another limitation, x64 versions and USB hard disk. I'd rather not to waste your and my time in something which won't work properly for your needs. Wimb's tool would suit much better: http://www.msfn.org/board/index.php?showtopic=121446 Although overall a bit more complicated to get used to, it does not have the limitations mentioned.

The attached txtsetup.sif is for Windows 2000. Open up all TXTSET00.sif, 01, 02 etc. you have in root and search for "strings"- in that section you will find out which file for which Windows version is. Attach the one for XP x86. Read this thread:http://www.msfn.org/board/index.php?showtopic=137508 Run the new MkMigrateInf_c.cmd: MkMigrateInf_c.cmd H: c:\migrate.infChange H: with the drive letter of your USB stick. Copy c:\migrate.inf to all ~BT directories on the USB stick, replacing the existing migrate.inf. Does that fix USB drive letter to U: ? There could be some issues if any of the slipstreamed install packages use hard coded paths, e.g. %CDROM%\PRO1\I386\, will try to sort them out once we fix the other issues. Was that on the same hardware?

This is not tested scenario, as you can guess there are many possible variations...How was the multi DVD created, what files were changed? What files are reported as missing? Stick with one version, let's troubleshoot it in a new topic, attach the corresponding txtsetup.sif. Check if files are present in your source and on the USB stick. As you were warned by the program, after first setup of any Windows different than XP SP2/3 some files will be deleted, so after setup you need to synchronize the USB stick with the source. Methods which do not have that limitation: http://www.msfn.org/board/2-t121446.html "Work in progress"- http://www.msfn.org/board/install-xp-ram-l...ge-t137714.html This should not be happening, USB stick should be U: and remain this.What drive letter did it get during Text mode? What letter at first logon?

Glad you got it solved

Search for shell32.dl_, is it in ~LS\I386 folder on the USB stick and in I386 on the CD? Nope, in case you have a proper source CD and properly working hardware, including USB stick.Do you have a chance to try with another USB stick? You can do many things in grub4dos prompt, but in regard to your issue none would be relevant.http://diddy.boot-land.net/grub4dos/Grub4dos.htm

BTS driver pack: http://forum.driverpacks.net/viewtopic.php?id=1449 Manual slipstreaming: http://unattended.msfn.org/unattended.xp/view/web/36/ Using nLite: http://maxeasyguide.blogspot.com/2008/04/p...llation-cd.html http://www.google.com/search?hl=en&rlz...mp;oq=&aqi= No idea what the option "Flash cache module" is for, so cannot advice.

You need either to integrate the appropriate mass storage (SATA) driver in your Windows source(manually or using nLite), use BTS mass storage driver pack, or change in BIOS SATA(AHCI) mode off, or to IDE, whatever the option is called.

What happens with boot.ini on internal hard disk in that case?

That's awesome cdob, thanks A few notes: Direct editing of $winnt$.inf in 64 bit versions would not work: http://blogs.sepago.de/nicholas/2008/03/13...on-windows-x64/ Maybe start another batch just for editing $winnt$.inf? start64.exe "%systemroot%\system32\cmd.exe" "/c %systemroot%\syswow64\editinf.cmd or with path whereever editinf.cmd lands when used from txtsetup.oem. Samo approach is used in WinSetupFromUSB to start binifix5.cmd, which edits $winnt$.inf. Another idea- could ImDisk be avoided and use boot.ini options to mount Firadisk emulated drive? http://www.boot-land.net/forums/index.php?...ost&p=77090 Is Firadisk added as a service with start 0 by Setup when used during text mode this way? There was a way if I recall correctly to include default options to boot.ini via txtsetup.sif or winnt.sif. Maybe txtsetup.oem could be used, or winnt.sif in the floppy image This way editing of $winnt$.inf may not be needed, if Firadisk creates the same device as if mounted by grub4dos.

That means grub4dos worked properly. I would try that first.

When used WinSetupFromUSB did you go first to "Windows XP/2000/2003 Setup- First and Second parts" entry, then from the new 2 options- First and Second parts you selected First part? If yes- did you try with unmodified source?

...Do you select every time Prepare Boot/RC files only? I see it marked on the screenshot posted as well as in the log file. You should NOT use it when preparing USB stick. This option is to be used: 1) If you want to place XP setup boot files ONLY in order to reach to the partition screen in Text mode and test of USB stick boots properly. USB stick has to be reformatted afterwards. 2) If you want to place Recovery Console only. If adding another, full XP Setup, you need to answer NO when it finds another Windows source on the stick in order to rename existing ~LS and ~BT folders and patch setup and startup files. Program will fail if FIXED button is selected along with Boot files/RC only option, this is corrected in the next, unpublished yet version. Lets go through this step by step. 1) Reformat the USB stick, use NTFS 2) Select Windows source 3) Move radio button to FIXED 4) Do NOT add or select anything else yet 5) Press GO 6) Zip and attach here USB_stick\~LS\I386\presetup.cmd, the new WinSetupFromUSB.log, USB_root\txtsetup.sif and USB_stick\~LS\I386\setup.ex_ I will check those files first then you can continue with another attempt for setup. Later on, if everything worked fine you can add UBCD4Win and Vista, it doesn't have to be done on one go.

Does that mean that when you start from USB you get nothing but black screen? Nothing means nothing, no boot menu, no cursor etc. What file system did you format the USB stick with? Did you try all possible- FAT16, FAT32, NTFS? What's USB stick capacity? Is it one of those emulating second drive- CD-ROM?

That's why I said hard disk, not USB stick There is something which was needed: There is FIXED/REMOVABLE radio button in WinSetupFromUSB program, did you play with it before?For some reason your USB stick is detected as fixed (hard disk) during Setup. sourcepath=\device\harddisk0\partition1\$win_nt$.~ls Another possibility is that the fake setup.exe is not launched, it starts presetup.cmd. Look in ~LS\I386 folder. Zip and attach with your next post setup.ex_ along with WinSetupFromUSB.log.