ilko_t

@vatastala Please test this version: http://www.winsetupfromusb.com/download/winsetupfromusb-1-2-exe/

The output of bcdedit seems to differ when run on Windows with Italian localization and the function parsing BCD store fails. Other languages maybe affected too. I've tested on English and Bulgarian localizations so far. I will have a look what is happening. Meanwhile, if you need to get going quickly and do not need EFI support, use the 1.0 version which does not edit BCD store at all. Please post long text output as attachment or upload it to file sharing service.

The only limit for Windows OS is disk free space, you can put as many as you need. Can you post the log file when the error appeared? The last lost file in next to WinSetupFromUSB.exe, previous log files are in cab archives, data-time stamped, in the backups folder. Find the relevant one, or just put them all in a zip archive and upload it to www.datafilehost.com for example.

Program updated to 1.1, list of changes: (U)EFI support for Windows Vista x64 SP1 and later 64 bits Windows. USB disk must be formatted in FAT32 as per EFI specifications to boot under EFI. To prepare USB disk running the program under Windows XP or 2003, which do not include bcdedit.exe, an active internet connection must be present in order to download it Firadisk driver is now added to each XP 32 bits source, but disabled by default. A new option in DPMS and custom F6 floppy menus activates it. This should help loading SATA/AHCI/RAID drivers from virtual floppy on problematic machinesNT6 sources boot menus are now handled by BOOTMGRfixed recognition of Windows 8.1 sources which contain INSTALL.ESD instead of INSTALL.WIMadded check in boot menu for Linux sources to warn if PLoP is loaded. Linux sources would not work with PLoP loaded as it supports only read moderemoved the ZIP archive as it seems some users tend to launch the program directly from the Windows zip folder view, rather than extracting all files and folders. A self extracting SFX archive is added insteadupdated wimlib to 1.5.3various small bug fixesDownload: http://www.winsetupfromusb.com/downloads/

Look at FAQ #3 : http://www.winsetupfromusb.com/faq/ And by the way, it's indeed frequently asked and answered question.

Why is yours so different? At first glance you are missing firaedit.inf which also removes the firadisk service, the one which brings you up second disk, the CD with XP contents... There might be other issues because of the missing lines. What about this other txtsetup.oem file? Where is that attachment from? It's quite hard to follow you.

I think you should just use the latest version: www.winsetupfromusb.com/downloads/ Let me know if there are still issues.

It should not write to the debugme file itself, but copy all log files next to it. Did you place it next to the Win8 ISO file? It must be without an extension. Can you manually copy x:\windowds\winpresetup.log when you get the error? Shift+F10 will bring up command prompt, then copy it to the USB disk. It would really help if you copy the other log files as well to see what is happening: x:\windows\inf\setupapi.offline.log x:\windows\inf\setupapi.app.log x:\windows\system32\winpeshl.log x:\windows\setupact.log x:\windows\setuperr.log Just in case- you are using 1.0 version of the program, right?

It is supported both as host and target OS, even the very first versions should support it. What does make you think it is not, did I miss to put an info anywhere?

Put an empty file called debugme next to the Win8 ISO file and restart the setup, get to the point when the error is displayed and cancel/close setup windows one by one until it restarts. All log files from PE phase will be copied next to it. Put them all in a zip file and post it here. Did you happen to use an USB 3.0 port? Use 2.0 instead. Did you try Win8 on another computer? Is it vanilla source?

Mostly because of lessons learned with the source for 0.x.x- one program rip-off, and one attempt for something I can't even figure out what was. I have yet to see the source used for something meaningful or improvement, properly credited. On the other side, which I consider more important, should anyone ask, I'd be happy answering how and what the program exactly does, as it's always been, that's the knowledge we all gain and share on these boards, besides, the log file reveals every action and the resulted config and other files, including the ones in the package, are all properly commented with credits and links to the source, nothing is hidden. Secondly, because the code do need some cleaning, for which I currently don't have the spare time, nor the willingness to do it. The futures and bug fixes I'd like to implement are way higher priority.

I am glad it's useful. Why would you need the source code?

This is answer file for fully unattended setup, RC or Repair option won't be shown. I don't recall which option exactly triggers the behaviour, been a long time, but if you now just need RC or Repair options, remove temporarily everything bellow the data section, starting with the Unattended section and put it back when ready. If you want to have both- partially unattended and RC and Repair options- do a little search in this board, it should be mentioned many times, or experiment a bit which option exactly triggers. And please, read carefully

Can you post winnt.sif , in USB disk\winsetup\xpXXXX\i386\ ? Please remove all sensitive info in it first- passwords, serial numbers etc.

For anyone having the same issue as Marlu and moujack888 above, please read this post for details and fix until a new version is out.

I can't see anything wrong in the log file, nor can reproduce the problem. Any chance for remote desktop connection to your computer? I've sent you a PM with details. It shlould be in winnt.sif, in your case in F:\WINSETUP\XPpSP3\I386\WINNT.SIF : http://unattended.msfn.org/unattended.xp/view/web/82/ http://unattended.msfn.org/unattended.xp/view/web/19/

Glad you got it solved.

That's weird... I am testing on my side as well and it goes as it should. Sorry, my bad, ignore this for now. Try the corrected winsetup.lst in the zip file attached. Triple check the correct DPMS.ISO file is in \DPMS folder. Open it up with 7-zip and confirm there are FIRA and WINV folders in it. winsetup.zip

Did you extract DMPS.iso from the attached archive above and replace the original one in DPMS folder on the USB disk? Please make sure you do exact steps. There should have been two instances of the mentioned lines. There is no need at all to test single floppy option.

Lets try using Firadisk or WinVBlock as helper driver. Replace DPMS.iso in \DPMS folder on the USB disk with the one in the attached archive. Might need to make the new file contiguous using WinContig in \files\tools\RMPrepUsb\WinContig folder. Then modify in Notepad winsetup.lst in the USB root. Replace both instances of set FIRA=0with set FIRA=2Replace /dpms2.g4b 0 with /dpms2.g4b 2Put # sign in front of both of these lines or just delete the whole line, should be present twice in your menu: map (0) (1)so they look like #map (0) (1)Next try Setup using only the Double floppy option. DPMS.7z

Start again from USB, select Double floppies menu entry. When you return to the menu, press the key "c" to enter command prompt. Then type: ls (0)/(0 is zero, not the letter "o") and press enter. Make a note of the output and post it back. Or better off take a picture of the screen and post it. Then type: cat (0)/txtsetup.oemand press enter. Make a note of the output and post it back. Or better off take a picture of the screen and post it. It's irrelevant that you get past the partitioning screen. On picky machines this is expected behaviour- Setup would fail to maintain and use the contents of the virtual floppies created and ask for the files.

What version of the program did you use? Does that happen with both Single and Double floppy option? What is the Hardware ID and driver name detected? You can see it when you select either of the DPMS options, something like Mind you, on picky machines DPMS may not work, the safest bet always is to integrate BTS mass storage driver pack with Text Mode option selected, or simply switch the disk controller to IDE/Compatible mode in BIOS.

Most likely the disk controller is in AHCI/SATA mode which vanilla XP doesn't have drivers for. Look at FAQ #3: http://www.winsetupfromusb.com/faq/

Yes, spot on. Each for different purpose MULTIpartitionUSBstick - installs dummydisk driver, making all removable disks to appear as fixed(basic) disks, thus allowing multiple partitions and so on operations, which are not allowed on removable disks. ImDIsk- virtual disk driver, mount CD, hard disk etc. images as virtual drives, similar to DaemonTools for example, but free, open source and actively maintained I think Google will help you a lot about the rest. Ask here if in doubt. Most of the tools are there just for user convenience, a good toolbox. And please, be very careful, some of the tools could lead to data loss if used in a wrong way or on the wrong disk/volume. Ditto. MultiPartitionUSBstick, or since you asked, another alternative is DiskMod which should also get you around the pagefile errors. You may install XP in disk image and load it completely in ram. Wimb has made some nice tools and guides, look at his signature for more: http://www.911cd.net/forums//index.php?showtopic=23553 In addition- use decent USB stick, most of them are quite slow with reads/writes of small files. Here are some tests: http://usbflashspeed.com/ http://hardwarebg.com/forum/showthread.php/92033-USB-%D1%84%D0%BB%D0%B0%D1%88-%D0%BF%D0%B0%D0%BC%D0%B5%D1%82-%D0%A2%D0%B5%D1%81%D1%82%D0%BE%D0%B2%D0%B5-%D0%B7%D0%B0-%D0%BF%D1%80%D0%BE%D0%B8%D0%B7%D0%B2%D0%BE%D0%B4%D0%B8%D1%82%D0%B5%D0%BB%D0%BD%D0%BE%D1%81%D1%82 Windows won't make pagefile on USB disk, use DiskMod. Yes. It's an empty tag file, used to find the USB disk among all disks by the presence of this file on it, hence the name and size.

Can you put in a zip archive winsetupfromusb.log found in program directory and attach it to your next post? The last log is in next to WinSetupFromUSB.exe, previous logs are in the backup folder, date-time stamped.