Working on winsetupfromusb multiboot

[TanakL]

I imagine the OEM folder be supposed to be shifted to the root of our USB Sticks. These methods if most of them encompass XP Pro and XP Home on our sticks they are able to together utilize the OEM folder as an alternative of having their own OEM folders. This would save regarding 500 MB or so every time the DriverPacks would be replica. In Windows XP PowerPacker I do this. This might lessen the code in WinSetupFromUSB for the reason by means of the intention of it determine to not encompass to change presetup.cmd for the reason by means of the intention of it determine to previously locate the OEM folder at the root of the stick. The tribulations is not innovative. It might be completed this technique, additional than I would rather maintain them in separate folders, in case somebody uses dissimilar sets/versions or descriptions of DP for 2000, XP and 2003.If disk space is a tribulations they might be moved to root physically and setup.cmd adjusted, or in case of NTFS utilize hard links by means of the contained DFHL.exe. Necessitate additional feedback commencing utilizing BTS and USB setup by means of multiple sources.

[Emiliio]

In this you have to attach your USB drive to the system and launch WinSetupFromUSB. If you have encompassed not prepared your USB drive appropriately, you determine to observe the error "No USB disks become aware of or not appropriately formatted" in the USB Disk Selection field go back to part one and go subsequent to the instructions there. If you observe your USB disk in this field, then it has been appropriately organized. Choose the checkbox subsequently to Vista/7 setup/PE/Recovery ISO, and then enter E:\LonghornAIO\Distribution (or wherever you generated your running folder in the preceding) into the box. You determine to be warned if the source is too great to fit on your USB drive, and determine to not be capable to continue, so create certain your install.wim is diminutive sufficient to fit on the drive.

[Felisha]

The WinSetupFromUSB might come into view to crash when it is copying the wim files – do not be anxious, it determine to respond on one occasion the file relocate has finished. Subsequent to a small number of minutes (or longer, if you encompass a sluggish USB drive and a large install.wim) WinSetupFromUSB determine to report by means of the intention of the procedure is complete. You at present encompass a bootable USB drive commencing which you be able to install whatever versions or descriptions of Windows you incorporated into the install.wim. If by means of the intention of is the entire you desire to utilize the USB drive for, then you do not necessitate to proceed several further. If you desire to add Windows XP/2003 or several 3rd party utilities, read on. At present would be a superior time to make sure with the intention of the USB drive runs as intended insert it into a system by means of the intention of supports booting commencing USB and choose it as the boot device. You be supposed to observe the "Windows is loading files" message, and ultimately be taken to Windows Setup.

[Zavier]

In order to be capable to choose dissimilar alternative for boot, most of them necessitate to install a boot loader and Grub4DOS is one of the majority popular ones. For this you have to Download Grub4DOS and the Grub4DOS Toolbox, and eradicate them into a directory on your hard disk, E:\Tools for illustration. Create certain by means of the intention of you put together in the similar directory, otherwise the Grub4DOS Toolbox determine to be not capable to locate Grub4DOS. Attach your USB drive and commence the Grub4DOS Toolbox. Commencing the Tasks menu, choose Add Grub4DOS to bootmgr boot list of options (Vista/2008 above), then choose the bootmgr file on your USB drive.

[DanielV]

I figured with the intention of was your reasoning. I had to create a conclusion similar to with the intention of back when I wrote powerpacker. I determined to go the route of immediately putting them the entire on the root. I stature in most cases people determine to utilize the similar driverpacks for each OS. On the other hand I do not deal by means of Windows 2000 multiboot stuff to any further extent. I do imagine by means of the intention of the XP-2003 driverpacks are the similar although. And in most cases I imagine 2000 drivers would make use of the similar as well. On a USB stick the additional space you save by protecting duplicate files the superior. It's not much of a deal by means of multiboot cd/dvds for the reason by means of the intention of of iso optimization.

[Enriquee]

Perhaps you might do this, user works winsetupfromusb, and is adding a subsequent, third xp source, etc. If DriverPacks are originate, present to shift them to root for common utilize, or leave unaccompanied for separate make use of (in case of dissimilar packs). For the reason that I would in addition similar to a common pack in root, in view of the fact with the intention of I am utilizing the similar files. So, what revolutionize would I have encompassed to formulate to achieve by means of the intention of, immediately shift OEM to root, and edit i386/setup.cmd to point there. I previously had seen speedily the connection you make available, additional than when I saw by means of the intention of you pointed me the entire in excess of again to this. I am endeavoring to utilize WinSetupFromUSB to add UBCD4Win to my USB pen (8 GB).

[mesterio]

I have encompassed my UFD setup utilizing WinSetupFromUSB 0.1.1. I was capable to boot commencing UFD and acquire into the Windows XP SP2 Blue text based Setup display. On the other hand, XP Setup was not capable to observe my internal HD. I am on a laptop by means of one internal HD and 3 partitions. I desire to run the XP Setup non critical repair characteristic on internal HD separation. My nLite inaugurate contains the Intel SATA drivers and runs commencing CD. I have encompassed completed convinced I did not choose "Operating System Options-->Manual Install and upgrading for elimination" throughout the nLite setup. My XPSetup commencing UFD (when it was running) merely observes the single separation on the UFD.