Guide for MultiBoot USB-stick with boot.ini Menu

In this Guide is described How to Make a MultiBoot USB-stick, where boot options
as MS-DOS, FREEDOS 1.0, GRUB4DOS, BartPE, TXT-mode Setup Windows XP, WinPE 2.0 and SYSLINUX
can be used directly from boot.ini Menu. In this way a powerful Admin's Swiss Army Knife is obtained.

The USB_MultiBoot.cmd Batch Program can now be used for making such MultiBoot USB-Drive,
instead of the Manual Procedure as described below. The Attachment gives USB_MultiBoot.zip file.
The USB_MultiBoot.cmd program can be used for making
MultiBoot USB-Drive for Install of Windows XP with Extra Boot Options for System Recovery with Ghost.

All Editable Configuration Files for making a MultiBoot USB-stick are given in the MULTI_CONTENT folder.
The content of MULTI_CONTENT folder is copied to USB-Drive by the USB_MultiBoot.cmd program.
Adapt the configuration files and the content of the MULTI_CONTENT folder to your personal needs.

Where USB-stick is mentioned in the description, USB-Harddisk with 2 GB FAT Partition can be used as well.
Use USB-sticks with High Read/Write Speed and FAT Format for Direct Booting with MS-DOS from USB.
e.g. Buffalo FireStix RUF2-R2G-S (Corsair Flash Voyager sticks are too slow for FAT Format)

Direct Booting with MS-DOS from FAT Format USB-stick with boot.ini Menu is prepared as follows:
You only have to add from Win98 MS-DOS BootFloppy the files IO.SYS and MSDOS.SYS to
the MULTI_CONTENT Folder and file COMMAND.COM to the folder DOS of the MULTI_CONTENT Folder.
These Hidden System Files are only visible in Windows Explorer after adjusting Tools > Folder Options

Run USB_MultiBoot.cmd and choose FAT Format with PeToUSB (max 2GB stick) and
Select Multi_boot.ini as boot.ini (option B ) and MULTI_CONTENT as Source (option 2) in the Main Menu.
The supplied config.sys of the MULTI_CONTENT folder regulates that for MS-DOS
the COMMAND.COM is found in the DOS folder so that confusion with FREEDOS is prevented.

Direct Booting with FREEDOS from USB was Removed since there were too few cases successful.

More INFO on Install XP from USB: http://www.msfn.org/board/install-XP-USB-t...6.html&st=6

HP USB Disk Storage Format Tool V2.0.6 - NTFS Format
Install of XP from USB in 16 minutes - Corsair Flash Voyager 4 GB USB-stick

Supports also USB-Drives having FAT32 or NTFS Format, thus overcoming the 2 GB limit of FAT Format.
NTFS Format allows larger DriveSize and is very useful for Install of XP from USB-Harddisk.
Besides NTFS Format is handy for Install of Vista from USB via GRUB4DOS chainload of bootmgr
FAT32 is extremely slow in Windows XP FileCopy during TXT Mode,
whereas NTFS Format of USB-Drive makes everything go faster than with FAT Format.

Multi-Partitioning an USB-stick is possible when dummydisk of Anton Bassov
is Installed in your computer http://www.codeproject.com/KB/system/sovie...ct_hooking.aspx
More Info See below.

================================================================================

A. Boot Test - Making Bootable USB-stick or USB-Harddisk with boot.ini Menu and NTLDR Bootsector
First Test if your PC is Booting from USB-stick:

1. Use 2 GB USB-stick with High Read/Write Speed (e.g. Apacer HT203 OR Buffalo FireStix RUF2-R2G-S are OK)

2. Format USB-stick with PeToUSB.exe http://gocoding.com/page.php?al=petousb
to Make Bootable USB-stick with FAT FileSystem, FAT = Faster
such that USB-stick has NTLDR Logical Drive Bootsector(mostly sector 0x3F=63)
and is seen by BIOS as Harddisk (MBR is at sector 0).
Use PeToUSB.exe with Settings: Enable Disk Format with LBA FAT16X

3. Copy XP BootFiles ntldr, NTDETECT.COM, Bootfont.bin and boot.ini from your XP C-drive to USB-stick
For this purpose in Windows Explorer Extra>Folder Options, Set Hidden and System Files to be Visible.

4. Change in boot.ini on stick rdisk(0) in rdisk(1) and add a second entry
so that on Booting from USB-stick you will be able to see the boot.ini Menu.
Before you Edit boot.ini, Remove first via Right-click and Properties the Read Only property.

boot.ini

5. Reboot your PC with USB-stick plugged in and Enter BIOS Setup by pressing [Delete] or F2
and change Boot settings more permanent so that Harddisk is used as first Boot device type
and USB-Drive is seen as first Harddisk. Save BIOS Settings with F10.

6. Test if your PC is Booting from USB-stick with boot.ini Menu. If you can see the Menu, it is OK
If USB-stick is not bootable:
Check BIOS bootsequence settings or use different USB-stick / computer combination,
OR Instead of PeToUSB use HP USB Disk Storage Format Tool Version 2.0.6 and use FAT filesystem
http://download.chip.eu/en/USB-Disk-Storag...0.6_176935.html

If you did prepare your USB-stick with USB_MultiBoot.cmd so that it can be used for Install of Windows XP,
than you had already a stick with boot.ini Menu and the required bootfiles, and you don't need to do steps 1-4

Instead of an USB-stick one can also make a Bootable USB-Harddisk using the steps 2-6 given above.

FOR USB-Harddisk make 1900 MB partition at beginning of the USB-Harddisk using e.g. Partition Magic.
Use FAT Format and Set Active OR use PeToUSB to Format such partition.
Without Set Active you will get DISK BOOT FAILURE.

================================================================================

***** WARNINGS *****
Be very careful with writing of bootsectors with HDHacker, bootsect.exe or mkbt.exe
Be always aware you make your changes on the right drive. Otherwise loss of DATA may be the result.
It is advisable to first remove all other removable drives, like USB Backup Harddisks and Memory Cards,
so that they cannot be involved by mistake in the writing process.

Do NOT use HP Tool for USB-Harddisks having more than 1 Partition
WARNING - HP Tool Formats whole Disk - Second Partition is Lost

Using PeToUSB.exe is SAFE, it can only Format partitions with size less than 2 GB
without destroying the existing partition table, so that Data partitions are still accessible.

Use of USB_MultiBoot.cmd and everything in this Guide is COMPLETELY at your own risk.

================================================================================

B. Adding New Boot Options - e.g. Booting the USB-stick via boot.ini directly into MS-DOS

This requires making a Bootsector File for each specific Boot Option and Adding a rule to boot.ini
mkbt.exe of Bart Lagerweij is very handy to make such Bootsector Files.
See: http://www.nu2.nu/mkbt/
mkbt.exe is so handy because it can change the Bootcode in the Bootsector,
while keeping the BIOS Parameter Block and the Extended Parameter Block unchanged.
This means the Drive geometry and File System (FAT) is maintained !
For this purpose the 7 f16*.bin files are supplied in folder makebt\BS_F16 as Source Code Bootsector Files.

1. Use procedure of Part A to make Bootable USB-stick with boot.ini Menu and NTLDR Bootsector
Make a proper Selection of your PeToUSB Settings to make a USB-Drive with FAT Format.
PeToUSB Settings To Format USB-Drive : Enable Disk Format with LBA FAT16X
When USB_MultiBoot.cmd is applied on existing USB-Drive with XP Install Files,
then Format is not needed and should be DeSelected.

Copy XP BootFiles ntldr, NTDETECT.COM, Bootfont.bin from your XP C-drive to USB-stick
Copy XP BootFile Multi_boot.ini from b_ini Folder to your USB-stick and Rename as boot.ini

2. Use mkbt.exe to Save the USB-stick Logical Drive bootsector as file NTBOOT.bs in folder btsec on your USB-stick.
Next use mkbt to Install MS-DOS Bootcode from bootsector file f16msdos.bin into USB-Drive Bootsector
Then Save modified USB-Drive Bootsector as Bootsector File MSBOOT.bs
And finish by Resetting USB-Drive Bootsector to the original NTLDR Bootsector using file NTBOOT.bs

Usage : mkbt [switches] <source> <target>
switches: -c = Copy mode(copy bootsector to Bootsector File, -x = Expert mode

For this purpose Open a Command Window (cmd) at the USB_MultiBoot\makebt Folder and type:

where R: is your USB-stick drive

3. boot.ini on stick was changed by adding the following rule:

C:\btsec\MSBOOT.bs="3. MS-DOS 7.10"

From Win98 MS-DOS BootFloppy Copy the files IO.SYS and MSDOS.SYS and COMMAND.COM to your USB-stick.
These Hidden System Files are only visible in Windows Explorer after adjusting Tools > Folder Options

4. In a similar way we can make the Bootsector File for FREEDOS 1.0 KERNEL.SYS
When both MS-DOS and FREEDOS are added it is necessary to place the COMMAND.COM in a folder
and to use in CONFIG.SYS and FDCONFIG.SYS SHELL commands like shell=\dos\command.com /e:1024 /p
and 12345?!SHELL=\FREEDOS\COMMAND.COM /E:2048 /F /MSG /P
Download FREEDOS 1.0 bootfloppy image fdboot.img from http://www.freedos.org/

5. TXT-mode Setup Windows XP, BartPE and WinPE 2.0 require a bootcode which is the same as
present in the NTLDR Bootsector, except that the file to which the bootsector refers is different,
being XPSTP, PELDR and BOOTMGR respectively instead of NTLDR.
SETUPLDR.BIN of XP was renamed to XPSTP because of NTFS Format 5-letter limit of MakeBS3.cmd
The program MakeBS3.cmd made by jaclaz is very handy to make
Bootsector Files XPSTP.bs for TXT-mode Setup Windows XP and PELDR.bs for BartPE or UBCD4Win,
where only the NTLDR loader filename was changed into e.g. XPSTP and PELDR respectively using:

where R: is your USB-stick drive

Such Bootsector Files are given in makebt folder as files f16xpstp.bin and f16peldr.bin
of which the BootCode can be used also by mkbt.exe to make XPSTP.bs and PELDR.bs
similarly as the procedure for making MSBOOT.bs

6. For Windows PE 2.0 a Bootsector File is required which refers to BOOTMGR instead of NTLDR.
The same Bootsector file can also be used to Install Windows Vista by launching Vista Setup.
Open CMD Window and use BootSect.exe to change the bootsector for use with bootmgr

where R: is your USB-stick drive.

Such BOOTMGR Bootsector File is given in makebt folder as file f16btmgr.bin with correct Error Messages,
which can be used by mkbt.exe to make BOOTMGR.bs similarly as the procedure for making MSBOOT.bs,
so that BootSect.exe which is more difficult to obtain, is no longer needed.

WinPE is a Console with rather limited use.
A lot of simple programs which run from BartPE, do not run from WinPE.
Windows PE 2.0 is included in the Windows Automated Installation Kit WAIK (see below for Download)
- Follow the instructions in the WAIK guide to create PE 2.0 files.
- Copy the contents of the "ISO" folder created in the proceding step to the root of your USB stick.


7. SYSLINUX Menu Support from boot.ini Menu requires to make Bootsector file SLBOOT.bs according to:
- Download syslinux from http://syslinux.zytor.com/download.php
- Use syslinux.exe from win32 folder in a Command Window as given below
- Copy the Bootsector with mkbt.exe as file SLBOOT.bs in btsec folder on USB-stick
- Reset USB-Drive to NTLDR Bootsector using mkbt.exe and the original Bootsector File NTBOOT.bs

where R: is your USB-stick drive.

8. GRUB4DOS Menu Support is added to boot.ini Menu as follows:
Download grub4dos-0.4.4.zip from http://sites.google.com/site/grubdos/ or http://download.gna.org/grub4dos/
Copy grldr and grub.exe to the Root directory of the USB-stick and make Custom file menu.lst
Launching of GRUB4DOS Menu via grldr is obtained by simply adding to boot.ini the rule:
C:\grldr="Start GRUB4DOS Menu - DOS FLOPPY IMAGES + Linux - Start Vista"

The boot.ini file in the Root Directory of the USB-Drive making all Boot Options available is given by:

boot.ini

Not all options are available on all USB-Drive Devices. So you can edit boot.ini to your needs.
Booting from MS-DOS is not available on 4 GB Apacer HT203, whereas 1 and 2 GB sticks are OK.
A lot of FREEDOS Bootsectors don't work and even the supplied FREEDOS Bootcode
only works on some USB-sticks and not on USB-Harddisk.

TinyHexer or HDHacker are useful to View in detail and to Save the USB-stick Logical Drive bootsector.
The Logical Drive bootsector is usually located 63 sectors from the beginning (MBR=sector 0) of the USB-disk.
HDHacker see http://dimio.altervista.org/eng/
TinyHexer 1.8 see http://www.chip.de/downloads/c1_downloads_13014623.html
HDHacker can also be used to Load Bootsector Files and to Write as Bootsector on USB-stick Logical Drive.

BootSect.exe can be obtained from the very large VISTA WAIK download (almost 1 GB).
The Windows Automated Installation Kit with the program bootsect.exe is available as download from Microsoft:
http://www.microsoft.com/downloads/details...;displaylang=en

================================================================================

C. Bootsector Files - Extra Info

The booting mechanism of NTLDR with boot.ini Menu and the use of Bootsector Files in boot.ini
has been excellently explained by jaclaz and is reproduced below:
http://www.911cd.net/forums//index.php?sho...=16980&st=8

1) The BOOTSECTOR (i.e. first sector of the Active Primary Partition)
contains CODE that boots (under NT/2K/XP/2003) the NTLDR
2) The NTLDR has the capacity to boot (through the selection in BOOT.INI and using NTDETECT.COM)
only the windows NT/2K/XP/2003 System partition, (i.e. \Winnt or \Windows) through an arcpath sintax,
(i.e. something like multi(0)disk(0)rdisk(0)partition(1)\WINNT)
3) To keep compatibility with elder MS operating systems,
the NTLDR has also the option to load ANOTHER bootsector;
this bootsector MUST have the same geometry (dynamic data) of the main one, but can have different CODE,
i.e. can load something different like the DOS files IO.SYS MSDOS.SYS COMMAND.COM
or another OS, or even another bootloader
4) BartPE normally boots by using a copy of SETUPLDR.BIN renamed as NTLDR or PELDR.
5) SETUPLDR.BIN behaves differently from NTLDR:
a.) It DOES NOT use the BOOT.INI settings file
b.) Searches for needed files in the \I386 directory
(this is fixed, hardcoded INSIDE SETUPLDR.BIN, needs hexediting to be changed)
or in the \minint one if on hard disk
c.) Reads the textsetup.SIF, or WINNT.SIF (or any other .sif file)

The way to have a BartPE selection in boot.ini is to have an alternate BOOTSECTOR, peboot.bin,
that loads PELDR (i.e. a renamed SETUPLDR.BIN) INSTEAD of NTLDR.

So the booting goes like this:
1) REAL BOOTSECTOR loads NTLDR
2) NTLDR loads BOOT.INI
3) If the line invoking the ALTERNATE bootsector peboot.bin is chosen, peboot.bin loads PELDR

You cannot load anything else but an ARCPATH or a BOOTSECTOR from NTLDR/BOOT.INI!

Using GRLDR or GRUB.EXE makes it possible to load DIRECTLY (i.e. chainload) NTLDR or SETUPLDR.BIN
without need for renaming the latter to NTLDR or PELDR.

Note Added: Bootsector File peboot.bin is equal to our PELDR.bs Bootsector file.

================================================================================

D. GRUB4DOS Menu Support - Extra Info

GRUB4DOS is added to boot.ini Menu as follows:
Download grub4dos-0.4.4.zip from http://sites.google.com/site/grubdos/ or http://download.gna.org/grub4dos/
Copy grldr to the Root directory of the USB-stick and make Custom file menu.lst
Launching of GRUB4DOS Menu via grldr is obtained by simply adding to boot.ini the rule:
C:\grldr="Start GRUB4DOS Menu - DOS Boot Floppy Images + Linux"

Use WinImage http://www.winimage.com/ to Inject Files and to Save a DOS Boot Floppy Image.

Download ready-to-run DOS Boot Floppy Images fdubcd.img and msubcd.img
made by Erwin Veermans See http://www.veder.com/nwdsk/
These images are based on the Modular Boot Disk of Bart Lagerweij See http://www.nu2.nu/bootdisk/modboot/
and were made for Ultimate Boot CD http://www.ultimatebootcd.com/
BootDisk.com has also a lot of Info and bootdisks available, See http://www.bootdisk.com/

Use the grub4dos tutorial to make menu.lst and add menu.lst to USB-stick
http://grub4dos.sourceforge.net/wiki/index.php/Main_Page
http://www.gnu.org/software/grub/manual/grub.html
http://grub4dos.sourceforge.net/wiki/index...ub4dos_tutorial

GRUB4DOS via boot.ini is in any FileSystem very powerful, especially using chainload of BootLoaders.

Use Disk emulation with Direct mapping in menu.lst:

menu.lst

Besides DOS Floppy Images, it is interesting to add to menu.lst of grub4dos also
Puppy Linux (NTFS Read/Write support) and DSL Linux (Knoppix with NTFS Read only support) ,
as described by diddy
http://www.911cd.net/forums//index.php?showtopic=18846

Download the latest Puppy Linux ISO file - Tested using "puppy-2.12-seamonkey.iso"
http://puppylinux.org/user/news.php

Download the latest DSL Embedded .ZIP file - Tested using "dsl-3.3-embedded.zip"
http://damnsmalllinux.org/

================================================================================

E. TXT-mode Setup of Windows XP - Software Install Extra Info

TXT-mode and GUI-mode Setup Windows XP
The procedure for Install of Windows XP from bootable USB-stick using a LocalSource was developed by
ilko_t , jaclaz , cdob and porear and is described by ilko_t in MSFN Forum:
http://www.msfn.org/board/index.php?showto...1384&st=199
The automatic making of a bootable USB-stick for Install of Windows XP can be realised
with the USB_MultiBoot.cmd batch command program.

The TXT-mode Setup of Windows XP includes the possibility to use the Recovery Console.
The Recovery Console is of very limited use as compared to
BartPE having Mini XP Desktop with very powerful Program Menu.
Nevertheless it is worthwhile to mention the Recovery Console within the scope of this subject.

Further Improvements of MultiBoot USB-stick:
1. Using Windows XP Source with Updates and DriverPacks Integrated:
using RyanVM Integrator http://integrator.siginetsoftware.com/index.php?download
with Update Packs and Addons http://www.ryanvm.net/forum/index.php?sid=...490d2bd5184b68a
and for DriverPacks using DP Base http://driverpacks.net/DriverPacks/overview.php
and for Unattended Install http://unattended.msfn.org/unattended.xp/

$OEM$\CMDLINES.TXT can be used for making UserAccounts and install of Registry Tweaks at T-12
On first logon the Extracted BTS DriverPacks are deleted, which normally takes a long time,
because SystemRestore copies them to System Volume Information folder.
The Disable_SystemRestore.reg Registry Tweak prevents this action, so that first logon is much faster.

Personally I am using only the 5 smallest BTS DriverPacks with Mass Storage text mode enabled.
So I do not integrate the 5 large Sound and Graphics DriverPacks, but use these Packs manually
when Updating Drivers. The extraction and deletion of these 5 large DriverPacks is taking a lot of time.
Mass Storage DriverPack with text mode enabled offers a lot of Extra SCSI, SATA and RAID Drivers
for the $WIN_NT$.~BT Windows XP Bootfolder so that F6 for Extra Driver Floppies is no longer needed.

2. Booting from DOS, with Ghost for System Backup and System Restore
http://www.911cd.net/forums//index.php?sho...=19621&st=7
3. Adding WPI for Automatic Install of Additional Programs http://wpiw.net/
4. Unattended Install of Office 2003 with Updates Integrated http://www.siginetsoftware.com/forum/
5. Adding WinTools running direct from USB-stick using nu2menu http://www.dirk-loss.de/win-tools.htm
Such WinTools are small programs which can run from WinTools Menu without the need of Install.
Double-click on GO_WINTOOLS_MENU.BAT on USB-drive provides WinTools Menu from GO button.
It also is possible to run the WinTools from any drive,
by copying the wintools folder and GO_WINTOOLS_MENU.BAT to the root of a harddisk drive.
Support for extra Portable Utilities is possible by editing nu2menu.xml file in MULTI_CONTENT\wintools\Nu2Menu folder.
An additional interesting list of Portable WinTools which can be added to WinTools Menu by editing nu2menu.xml file,
is found here http://users.pandora.be/Robvdb/USBMemStick.htm

================================================================================

F. BartPE or UBCD4Win - Extra Info

BartPE of Bart Lagerweij is a MINI XP with very powerful Program Menu,
and can simply be added to boot.ini Menu http://www.nu2.nu/pebuilder/
UBCD4Win is based on BartPE and can be used as well http://www.ubcd4win.com/index.htm
USB_MultiBoot.cmd Program has a build in routine for Adding BartPE or UBCD4Win to your USB-drive.

For a MultiBoot USB-stick combining BartPE ( minint folder ) and the LocalSource of Windows XP Setup (see below),
I found the following solution to make BartPE boot from the minint folder, instead of launching Windows XP setup.
Hexedit peldr using TinyHexer. Change in peldr the first occurrence of txtsetup.sif in notsetup.sif
Now BartPE will boot from minint folder and will not use WinXP txtsetup.sif from root directory.
http://www.msfn.org/board/index.php?showto...1384&st=224

Thanks to jaclaz for his helpful advice to use gsar.exe for Hexediting of peldr in USB_MultiBoot.cmd program.
Download gsar from http://gnuwin32.sourceforge.net/packages/gsar.htm

Usage: gsar [options] -s[search string] -r[replace string] [infile] [outfile]


gsar Option -o
Search and replace of multiple files, overwrite the input file(s).
For each input file, gsar creates a tempfile which contains the replacements and
copies the tempfile to the original input file name.
If no matches were found, the input file stays the same. The tempfile is removed.

================================================================================

G. SYSLINUX Menu Support - Extra Info

Install of SYSLINUX is drive specific and it is not possible to Reinstall SYSLINUX by simple filecopy.
File ldlinux.sys made in USB Root directory uses the Custom made files syslinux.cfg and menu.txt
Bootsector Files are only recognised by SYSLINUX as such when they have the extension .bs

syslinux.cfg


menu.txt

It is worthwhile to note that also direct booting with MS-DOS from SYSLINUX Menu is possible in this way.

SYSLINUX Menu requires a Drive Specific Install and is in general booting Faster than GRUB4DOS Menu,
but boot.ini Menu is the most versatile BootMenu from which all other Boot Options are available !
Windows XP can be launched from any partition of any harddisk using the boot.ini Menu.
Windows Vista can be launched from any partition of any harddisk using the menu.lst Menu of GRUB4DOS.

================================================================================

Previous Version:
Number of downloads:
275 + 284 + 6500 + 3896 + 1200 (3) + 2720 (4) + 10023 (5) + 3707 (6) + 1250 (7) + 8033 (8) + 8112 (9)

Edit 8 jan 2008: Added PeToUSB.exe
Changed GO_WINTOOLS_MENU.BAT and Added nu2menu.exe in MULTI_CONTENT\wintools\Nu2Menu folder
Double-click on GO_WINTOOLS_MENU.BAT provides WinTools Menu from GO button.
Added FREEDOS + DOSDEV drivers, grldr and grub.exe, VC, some tools

EDIT 5 feb 2008:
Removed %_mypath% in Making BootSector Files causing program crash when USB_MultiBoot2 folder was deep nested in Documents and Settings which results in a path with spaces.
Added /r option in xcopy of $WIN_NT$.~LS Folder from usb_xpbt Folder to USB-Drive ,
needed in some cases where presetup.cmd was Read Only.

EDIT 14 feb 2008: Attachment Updated to USB_MultiBoot3.zip

Edit 20 feb 2008: New Release USB_MultiBoot4.zip
Possible DOSNET.INF Parsing Error (biosinfo.inf not found etc.) was removed.

Edit 28 feb 2008: New Release USB_MultiBoot5.zip
ren_fold.cmd was changed such that $OEM$\$1 and $OEM$\$$ folders are copied
as usual to systemdrive (usually C:\) and systemroot (usually C:\WINDOWS) respectively.
Format Menu was added allowing to use HP USB Format Tool
for making USB-sticks (greater than 2 GB) with NTFS Format allowing Install of XP in 16 minutes.
USB_MultiBoot5.cmd has now Option for Adding BartPE instead of using PeToUSB.
Possible source of Error in SOURCE Pathes is Detected e.g. when XPSOURCE path contains SPACES.

Edit 14 mar 2008: New Release USB_MultiBoot6.zip
DOSNET.INF Parsing Routine was simplified, necessary when adding Drivers with nLight
For BartPE I386\WinSxS Folder is used as a marker instead of using as Tagfile winbom.ini
winnt.sif file is tested for the needed presence of MsDosInitiated="1" and floppyless="1"
Log filename was Changed to usb_log.txt

Batch Program INSTALL_DRIVERS.CMD was Added to Folder INSTALL_DRIVERS:
Supports Post XP Setup Install of Drivers with Device Manager by
Unpacking DriverPacks or OEM Source Folder to Selected Target Drive
And by Setting DevicePath to Selected Target Driver Folder

Edit 28 mar 2008: New Release USB_MultiBoot7.zip
Support for XP x64 using AMD64 Folder was added
MULTI_CONTENT was optimised for FAT Format and Direct Booting with MS-DOS from boot.ini Menu
X_CONTENT was optimised for NTFS Format and Supports Booting from DOS Floppy Images via GRUB4DOS Menu
ntfs_menu_lst.txt was removed because X_CONTENT is now dedicated for NTFS Format
For Link in Program Intro removed &st=6 causing Message st is unknown command
Options B and W) have been changed for Vista which is not able to use VBS FileSelector

Edit 04 apr 2008: New Release USB_MultiBoot_8.zip
Support for XP x64 changed txtsetup.sif entries 55 instead of 100
OEM or nLite winnt.sif File is detected in XPSOURCE and Auto Changed for Install of XP from USB.
In that case All Setup Parameters come from XPSOURCE and therefore Empty $OEM$_X Folder is Selected.
$OEM$ Folder is made User Selectable from Main Menu.
Making of BootSector Files was rewritten and internal organisation was changed and improved.
SETUPLDR.BIN of XP was renamed to XPSTP for ALL Formats to avoid confusion,
because of the 5-letter limit of MakeBS3.cmd for NTFS Format.
Direct Booting with FREEDOS from USB was Removed since there were too few cases successful.
The MULTI_CONTENT Folder is recognised from usbmulti TagFile
for making MS-DOS Windows PE 2.0 and SYSLINUX BootSector Files for MultiBoot Support.

Edit 08 May 2008: New Release USB_MultiBoot_9.zip

- Display and Edit of the 8 required parameters for Unattended Setup is build in
where the Selected winnt.sif file is first savely copied to the Current_winnt.sif file.
The Current_winnt.sif File is adjusted for Install from USB and then
copied by USB_MultiBoot.cmd to $WIN_NT$.~BT folder on USB-Drive.
The file useraccounts.cmd with UserName is made in the Currently Selected $OEM$ Folder.

- For each XP Source the Program Supports now to launch Unattended or Attended Setup.
Therefore a second SetupLoader XATSP for Attended Setup is made ,
where winnt.sif is Patched as winat.sif using gsar.exe
So the extra Setup Option does not take extra space from the USB-stick.

- Multiple XP Install from USB is now Supported (max 9 sources)
http://www.msfn.org/board/SOLVED-Install-M...SB-t114543.html
Run USB_MultiBoot.cmd again using New XP Source and Empty XX_CONTENT Source Folder

- Windows XP Recovery Console from USB is now supported and launched via GRUB4DOS Menu

- Multiple PE (BartPE and UBCD4Win) from USB is supported using Multi_Partition USB-Drives.
INSTALL_DUMMY.cmd was made for dummydisk, which you will find in the makebt Folder.
When dummy.sys is Installed in your OS,
then you can make Multiple Partition USB-sticks with NTFS format,
allowing to combine BartPE and UBCD4WIN or different Vista Versions x86 and x64
http://www.msfn.org/board/Multiple-PE-from....html&st=11
http://www.911cd.net/forums//index.php?sho...20089&st=24
Run USB_MultiBoot.cmd again using New BartPE Source and
using Empty XX_CONTENT Source Folder and No Copy of XP Source.

- Install of Vista from USB is now supported and launched via GRUB4DOS Menu
http://www.msfn.org/board/vista-t114092.html&st=6
http://www.msfn.org/board/Install-Vista-fr...6.html&st=2
For Vista Install from USB, Remove on first Restart your USB-stick.

- Improvement of the Main Menu and the boot.ini Menu's

- GRUB4DOS grldr and grub.exe Updated to grub4dos-0.4.3-2008-05-02


Edit 06 June 2008: New Release USB_MultiBoot_10.zip

- For the Option Edit UserData for XP Setup we have:

A. Unattended Install - UserName = YourName
in winnt.sif file - unattendswitch="Yes" - UserName is used Automatically
useraccounts.cmd with UserName is created in $OEM$ Folder copied to USB-drive

B. Semi-Unattended Install - UserName = None
in winnt.sif file - unattendswitch="No" - UserNames are given Manually at Windows Welcome Screens
useraccounts.cmd is Renamed to Inactive txt file in $OEM$ Folder copied to USB-drive

C. Undefined Install - UserName = Unknown
No Changes are made in winnt.sif file or $OEM$ folder

In all cases Selecting Cancel keeps given Settings for winnt.sif file and $OEM$ folder Unchanged

For Install of XP from USB the program has to remove the [Unattended] Section from the winnt.sif file,
so that unattendswitch="Yes" Setting made by nLite in the [Unattended] Section is lost.
Consequently XP Setup will present in this case Windows Welcome Screens for Creating UserNames.

Selecting Unattended Install in the Editor instead of Cancel will enable to skip the Welcome Screens
by automatic adding the unattendswitch="Yes" Setting to the [Data] Section of the Current_winnt.sif file.
The UserName given at Edit Screen 8 will not be used in the case of XPSOURCE made by nLite.

- In preparing the USB-drive, the file useraccounts.cmd with UserName is made now in the $OEM$ Folder
located in the temporary folder usb_xpbt, so that the original $OEM$ Folder remains unchanged.
The XP Setup Type and the given User Name are Displayed in the Main menu
and in the Status Report Screen just before Copy to your USB-drive is Selected.

- The winat.sif file for Attended Install is now derived from your Current_winnt.sif file
which is more logical than using the preconfigured Attended_winnt.sif file.
In the Attended Install all Setup Parameters are given Manually during the GUI Mode of Setup Windows XP.
Attended Install is always available as Extra Option in the boot.ini Menu.

- Computation of Estimated XP Folder Size to prevent overflow
includes now $WIN_NT$.~BT + cmpnents + I386 + AMD64 + $OEM$ + OEM Folders instead of previously I386 only

- REMOVE_DUMMY.cmd was made to remove dummydisk from the Registry, which you will find in the makebt Folder.
After removal of dummydisk all USB-sticks are seen again as Removable Devices.

- GRUB4DOS grldr and grub.exe Updated to grub4dos-0.4.3-2008-05-07

EDIT 30 Sept 2012 - Update of USB_MultiBoot_10.zip for compatibility with Windows 7 (solved USB-drive Not Valid)
Number of downloads previous version = 4768503

Thank you for spending the time to gather this information into a useable solution.

NICE JOB.

Does this mean that this whole approach is only available to VISTA users?

The Windows Automated Installation Kit with the program bootsect.exe is for everybody available as download from Microsoft:
http://www.microsoft.com/downloads/details...;displaylang=en

The WAIK is a rather large download for getting the small file bootsect.exe.
Another solution can be reformating the USB-stick, which is in most cases acceptable.
When the USB-stick is first formated with the HP Utility without using DOS System files,
one can use HDHacker to Save the USB-stick Logical Drive NTLDR Bootsector as file NTBOOT.dat
which can be used later in step 4. to Reset the NTLDR Bootsector, instead of using bootsect.exe

The Guide for making a MultiBoot USB-stick with boot.ini Menu was improved and updated.

All Editable Configuration Files for making a MultiBoot USB-stick are given in post #1 as Attachment file usb_cfg2.zip

Great job

***** NEW PROGRAM USB_MultiBoot.cmd *****

The USB_MultiBoot.cmd Batch Program can now be used for making a MultiBoot USB-Drive,
instead of the Manual Procedure as described in the Updated Guide of Post Nr. 1

The Attachment of Post Nr. 1 gives USB_MultiBoot.zip file.
The USB_MultiBoot.cmd program can be used after or before usb_prep8.cmd program for making
MultiBoot USB-Drive for Install of Windows XP , thus providing Extra Boot Options for System Recovery with Ghost.

All Editable Configuration Files for making a MultiBoot USB-stick are given in the usb_cfg folder.
The content of usb_cfg folder is copied to USB-Drive by the USB_MultiBoot.cmd program.
Adapt the configuration files and the content of the usb_cfg folder to your personal needs.

In USB_MultiBoot.cmd I needed a simple and quiet way to find out which Drives have FAT Format.
That resulted in the program DriveList where all available Drives are specified for their FileSystem and Drive Type.

The Attachment gives DriveList.zip file.

Regards,

wimb

Edit 18 dec 2007: Added PeToUSB.exe to USB_MultiBoot.zip
Changed GO_TOOLS_MENU.BAT and Added nu2menu.exe in usb_cfg\tools\Nu2Menu folder
Double-click on GO_TOOLS_MENU.BAT provides WinTools Menu from GO button.
Added FREEDOS + DOSDEV drivers, grldr and grub.exe, VC

Edit 12 feb 2008 - Attachment Update - DriveList_XV.zip is now XP and Vista Compatible.

There is a complete New Program Available: USB_MultiBoot2.cmd

I have integrated usb_prep8.cmd in MultiBoot2.cmd Batch Program, which:
- Prepares MultiBoot USB-Drive provided with Windows XP Setup LocalSource
- Supports Booting: MS-DOS FREEDOS BartPE WinPE 2.0 and Setup Windows XP
- Supports GRUB4DOS with DOS FLOPPY IMAGES + Linux and Supports SYSLINUX Menu
- Supports Portable WinTools which run direct from GO-Menu button

Changes:
- Virtual Drive as used in usb_prep8.cmd is no longer needed.
Instead in MultiBoot2 Folder a Temporary Folder usb_xpbt is made with all Custom made Files,
and where the XP BootFolder $WIN_NT$.~BT is created by parsing DOSNET.INF from XP Source.
The XP Source is copied direct to the $WIN_NT$.~LS Folder on the USB-Drive
and not to the Temporary Folder usb_xpbt,
but it is not needed to copy XP Source and to Support Setup Windows XP.

- Install of BartPE by PeToUSB is supported, where a 2-byte hexedit of peldr enables its use
in combination with coexisting XP Setup files, thus resolving possible conflict.

- New is the USB Content Source Folder U_CONTENT,
which can contain additional DOS, Linux and Win PE 2.0 files,
but one might also select the complete Content of an earlier made USB-stick,
Or one may select an empty folder with only usbflash TAGFILE (needed).
The Bootsector Files, Install of Syslinux, peldr and migrate.inf are Renewed to make the MultiBoot USB-Drive.

- New is also the wintools folder with Portable win32 WinTools.
Double-click on GO_WINTOOLS_MENU.BAT on USB-drive provides WinTools Menu from GO button.

The Attachment of Post Nr. 1 gives latest USB_MultiBoot.zip file.


Regards,

wimb

EDIT 20 feb 2008: Changed Download Info

**** NEW PROGRAM ****

**** BootSector Backup Utility - MBR_Backup.cmd ****

When working in USB_MultiBoot2.cmd with BootSector Files,
I thought it would be nice to have a program,
which can make a Backup of the BootSectors of my Harddisk.

For this purpose I have Created the Program - MBR_Backup.cmd -

It makes a Backup of all Bootsectors of all Local Harddisks (Fixed + Removable).

Learn More about it Using the Links in MBR_bookmark.htm in Folder Help_Info.
Use TinyHexer.exe to Study and Compare BootSectors in Detail.

***** Using These Programs is COMPLETELY At Your Own Risk *****

The Backup Folder MBR_Date_ComputerName Contains for each Harddisk :

BootSector Files for:
- Master Boot Record - MBR - Sector 0 of Harddisk containing Partition Table
- Extended Partition Boot Record - EPBR - Beginning of Extended Partition
- Extended Boot Records - EBR - Beginning of Logical Partitions within Extended Partition
- Logical Drive BootSectors - 16 Sectors for NTFS and 1 Sector for FAT32 FAT

- And Partition Info File = MBR_Date_ComputerName.txt

The FileName of the BootSector Files contains HD number and Sector Position,
which information is very useful for later Restore using TinyHexer.exe

Hopefully Restore of BootSectors will NOT be needed,
but when e.g. the daisychain of EBR's for reaching your Data Partition is broken,
it will be nice to have such a Backup of BootSectors Available.

Using MBR_Backup.cmd for making BootSector Files is very fast and convenient
as compared to doing this Manually for all Bootsectors of all your Harddisks !

Regards,

wimb

MBR_Backup is Suitable for the 32-bits versions of Windows XP and Vista,
but requires for Vista to turn User Account Control OFF

EDIT: 02 May 2009 - Previous Downloads 8500
Update Attachment MBR_Backup.zip
Removed Error due to forward slash in DATE

***** NEW PROGRAM *****

***** USB_MultiBoot_10.cmd - Install XP from USB *****

Unpack USB_MultiBoot_10.zip to your Harddisk in a simple Path without SPACES.

Major Changes and Support:

- Basic Use Involves only Selecting XP Source Folder and USB-Drive Target
to make USB-Stick which can be used for Install of XP on Mobile PC like e.g. ASUS Eee subnotebook

- USB_MultiBoot.cmd is Vista Compatible, but requires User Account Control OFF.
The bootmgr BootSector made by PeToUSB is Detected and
Converted to NTLDR Bootsector ( No need anymore to use BootSect.exe separately )
XP as OS is Preferred for Speed of FileCopy to USB ( 10 min instead of 30 minutes for Vista OS )

- Advanced Users can make USB-MultiBoot SuperStick or Harddisk,
when selecting Multi_boot.ini and MULTI_CONTENT Source offering a large variety of
handy computer tools available via boot.ini GRUB4DOS or SYSLINUX Menu

- Siginet's RyanVM Integrator or nLite can be used to Integrate Windows UpdatePacks in the XP-Source.
http://integrator.siginetsoftware.com/index.php?download and http://www.nliteos.com/
The Complete XP-Source is Copied to XP LocalSource Folder $WIN_NT$.~LS on USB-Drive
Take care that your XPSOURCE Folder is located on your Harddisk in a simple Path without SPACES.

- Supports the use of BTS DriverPacks located in OEM Folder on USB-Drive - http://driverpacks.net/DriverPacks/
For Install of XP on a modern system with SATA Drives it is needed to use DPsBase.exe
for Integrating in your XPSOURCE BTS DriverPack Massstorage with TXT Mode Enabled.
In that case a lot of Extra RAID SCSI and SATA Drivers (about 120 extra) are Integrated which appear in the
XP Setup BootFolder $WIN_NT$.~BT on USB-Drive and can prevent a lot of XP Install Boot Problems.
First use RyanVM Integrator and than use DPsBase to Improve your XP-Source.
The program supplies a Customised presetup.cmd and changes the winnt.sif file for use of DriverPacks.

- For USB-Harddisk use Menu Option 0) to Change USB-stick in USB-Harddisk.
Because that makes that rdummy.sys is used and this is essential for using USB-Harddisk.
rdummy.sys makes Fixed USB-Harddisk seen in XP Setup as Removable Device.

- boot.ini and winnt.sif Files and $OEM$Folder are User Selectable,
Handy for Windows 2003 and Non Standard Installs and for making MultiBoot USB-Drive
Use the supplied winnt.sif file, which is copied to file Current_winnt.sif in Folder w_sif
For Unattended Install use the build in Edit UserData Setup to give ProductKey and TimeZone.
Use for Preparing USB-Drive Only winnt.sif file without an [Unattended] Section and with MsDosInitiated="1"
The Current_winnt.sif File is adjusted for this and copied by USB_MultiBoot.cmd to $WIN_NT$.~BT folder on USB-Drive.

- OEM or nLite winnt.sif File is detected in XPSOURCE and Auto Changed for Install of XP from USB.
In that case All Setup Parameters come from XPSOURCE and therefore Empty $OEM$_X Folder is Selected.
For UNATTENDED XP Install use the build in Edit UserData Setup to Change the 8 required parameters.
Give ProductKey and TimeZone used in Current_winnt.sif Copy of your winnt.sif

- Change $OEM$ folder to your needs, which is copied to $WIN_NT$.~LS folder on USB-Drive
CMDLINES.TXT is used for making UserAccounts and install of Registry Tweaks at T-12
Info see: http://unattended.msfn.org/unattended.xp/
ren_fold.cmd was changed such that $OEM$\$1 and $OEM$\$$ folders are copied
as usual to systemdrive (usually C:\) and systemroot (usually C:\WINDOWS) respectively.
For anything else you want to copy from USB-Drive, you can add similar lines to ren_fold.cmd,
which is executed at T-9 by the Section SetupParams of winnt.sif file
Or Use CMDLINES.TXT and useraccounts.cmd in the $OEM$ Folder for Extra Copy Commands.

- Supports also USB-Drives having FAT32 or NTFS Format, thus overcoming the 2 GB limit of FAT Format.
NTFS Format allows larger DriveSize and is very useful for Install of XP from USB-Harddisk.
Besides NTFS Format is handy for Install of Vista from USB via GRUB4DOS chainload of bootmgr
FAT32 is extremely slow in Windows XP FileCopy during TXT Mode (has anyone an idea why ?),
whereas NTFS Format of USB-Drive makes everything go faster than with FAT Format.

In the Format Menu one can Select:
P) PeToUSB - FAT Format - Max 2 GB
Install of XP from USB in 30 minutes - Buffalo FireStix 2 GB
FAT Format Supports Direct Booting with MS-DOS using MULTI_CONTENT
Do NOT Select here FileCopy of BartPE

H) HP USB Disk Storage Format Tool V2.0.6 - NTFS Format - use X_CONTENT
Install of XP from USB in 16 minutes - Corsair Flash Voyager 4 GB USB-stick

N) No Format - Use USB-Harddisk with FAT or NTFS Format by Windows XP

Use MULTI_CONTENT Folder only with FAT Format USB-Drive
for Support of Direct Booting with MS-DOS from boot.ini Menu
Use X_CONTENT Source Folder for making NTFS or FAT Format USB-Drive
with Support of Booting from DOS Floppy Images via GRUB4DOS Menu

HP Format Tool Enables to make large USB-sticks with NTFS Format which are very useful,
but is missing the option of PeToUSB to Install BartPE on USB-Drive.
The program was changed such that BartPE http://www.nu2.nu/pebuilder/
or UBCD4Win http://www.ubcd4win.com/index.htm can be added now for all Format Options to USB-Drive
by Selecting BartPE Source Folder in the Main Menu. Remove with Cancel.
So don't use PeToUSB for Install of BartPE anymore, but only use PeToUSB to make FAT Format USB-Drive.
Using Cancel in BartPE Source Folder Selection, Disables the Install of BartPE on USB-Drive.
FileCopy to USB-Drive begins with USB Content Source Folder, followed by the XP Setup Source Folder
and finally the BartPE Source Folder is copied when a valid path was given with option 5)

- FAT32 and NTFS do not support Direct Booting into MS-DOS FREEDOS and Windows PE 2.0
Unsupported Boot Options are automatcally removed from the Menu's.
GRUB4DOS via boot.ini is in any FileSystem very powerful, especially using chainload of BootLoaders.
But GRUB4DOS also allows to Boot from MS-DOS or FREEDOS Floppy Images and to Boot from Linux.
http://grub4dos.jot.com/WikiHome
http://grub4dos.sourceforge.net/wiki/index...ub4dos_tutorial

- BootSector Files are made with dsfo / dsfi from the once with mkbt.exe copied BootSector,
instead of Install, Copy and Reset of BootSectors using mkbt.exe for making each BootSector File.
MakeBS3.cmd of jaclaz is used for making NTFS BootSector Files,
where SETUPLDR.BIN was Renamed to XPSTP according to the 5-letter limit requirement.

- Windows XP Recovery Console from USB is supported and by launching it via GRUB4DOS Menu
Booting Direct with XP Recovery Console has conflict by unwanted launching XP Setup.
The program CMDCONS_Folder.cmd can be used separately,
which makes Recovery Console folder cmdcons by parsing DOSNET.INF File.

- Overflow Control has been added by measuring DiskSize, FreeSize, XP-Source and
Multi_Content Source Folders using ASP Drive Object and Visual Basic Scripting.
SEE: http://www.w3schools.com/asp/asp_ref_drive.asp
http://www.robvanderwoude.com/index.html

- Excluding LANG and WIN98X Folders from Copy to USB can be Selected,
which reduces the XP-Source on USB-Drive by 135 MB
Reduction of the XP WINDOWS Folder can be achieved with nLite
but do NOT select Operating System Options-->Manual Install and Upgrade for removal.

XPSOURCE Space Saving Tips see: http://unattended.msfn.org/unattended.xp/view/web/57/
You can Safely Remove the XPSOURCE folders:
WIN9XMIG, WIN9XUPG and WINNTUPG - This will free up 37.6 MB
LANG - 99 MB and cmpnents - 22.6 MB ( Needed for MCE / Tablet PC only )

- The Folder usb_cfg_extra provides scripts for BartPE Menu http://www.nu2.nu/pebuilder/
For the Automatic Install of Programs after Install of XP from USB
we can use a script for the very handy Windows Post-Install Wizard (WPI) http://wpiw.net/

- In WPI script there is the option to run SFC /purgecache which deletes the dll cache and
which is a very simple way to reduce the WINDOWS Folder Size by 360 MB
The Result is a XP WINDOWS Folder Size on Harddisk of only 785 MB inclusive all Updates.

- Supports Portable WinTools which run direct from GO-Menu button in a VISTA or XP environment
http://www.dirk-loss.de/win-tools.htm
http://users.pandora.be/Robvdb/USBMemStick.htm

- Direct Booting with MS-DOS from USB-stick with boot.ini Menu is prepared as follows:
You only have to add from Win98 MS-DOS BootFloppy the files IO.SYS and MSDOS.SYS to
the MULTI_CONTENT Folder and file COMMAND.COM to the folder DOS of the MULTI_CONTENT Folder.
These Hidden System Files are only visible in Windows Explorer after adjusting Tools > Folder Options

Run USB_MultiBoot.cmd and choose FAT Format with PeToUSB (max 2GB stick) and
Select Multi_boot.ini as boot.ini (option B ) and MULTI_CONTENT as Source (option 2) in the Main Menu.
The supplied config.sys of the MULTI_CONTENT folder regulates that for MS-DOS
the COMMAND.COM is found in the DOS folder so that confusion with FREEDOS is prevented.

- Direct Booting with FREEDOS from USB was Removed since there were too few cases successful.

- More Help with Bookmarks is available in the Help_Info Folder in USB_MultiBoot_10.zip

- Use of MultiBoot_10.cmd and everything in this Guide is COMPLETELY at your own risk.

Edit 28 feb 2008: New Release USB_MultiBoot5.zip
ren_fold.cmd was changed such that $OEM$\$1 and $OEM$\$$ folders are copied
as usual to systemdrive (usually C:\) and systemroot (usually C:\WINDOWS) respectively.
Format Menu was added allowing to use HP USB Format Tool
for making USB-sticks (greater than 2 GB) with NTFS Format allowing Install of XP in 16 minutes.
USB_MultiBoot5.cmd has now Option for Adding BartPE instead of using PeToUSB.
Possible source of Error in SOURCE Pathes is Detected e.g. when XPSOURCE path contains SPACES.

Edit 14 mar 2008: New Release USB_MultiBoot6.zip
DOSNET.INF Parsing Routine was simplified, necessary when adding Drivers with nLite
For BartPE I386\WinSxS Folder is used as a marker instead of using as Tagfile winbom.ini
winnt.sif file is tested for the needed presence of MsDosInitiated="1" and floppyless="1"

Edit 28 mar 2008: New Release USB_MultiBoot7.zip
Support for XP x64 using AMD64 Folder was added
MULTI_CONTENT was optimised for FAT Format and Direct Booting with MS-DOS from boot.ini Menu
X_CONTENT was optimised for NTFS Format and Supports Booting from DOS Floppy Images via GRUB4DOS Menu
ntfs_menu_lst.txt was removed because X_CONTENT is now dedicated for NTFS Format
For Link in Program Intro removed &st=6 causing Message st is unknown command
Options B and W) have been changed for Vista which is not able to use VBS FileSelector

Edit 04 apr 2008: New Release USB_MultiBoot_8.zip
Support for XP x64 changed txtsetup.sif entries 55 instead of 100
OEM or nLite winnt.sif File is detected in XPSOURCE and Auto Changed for Install of XP from USB.
In that case All Setup Parameters come from XPSOURCE and therefore Empty $OEM$_X Folder is Selected.
$OEM$ Folder is made User Selectable from Main Menu.
Making of BootSector Files was rewritten and internal organisation was changed and improved.
SETUPLDR.BIN of XP was renamed to XPSTP for ALL Formats to avoid confusion,
because of the 5-letter limit of MakeBS3.cmd for NTFS Format.
Direct Booting with FREEDOS from USB was Removed since there were too few cases successful.
The MULTI_CONTENT Folder is recognised from usbmulti TagFile
for making MS-DOS Windows PE 2.0 and SYSLINUX BootSector Files for MultiBoot Support.


Edit 08 May 2008: New Release USB_MultiBoot_9.zip

- Display and Edit of the 8 required parameters for Unattended Setup is build in
where the Selected winnt.sif file is first savely copied to the Current_winnt.sif file.
The Current_winnt.sif File is adjusted for Install from USB and then
copied by USB_MultiBoot.cmd to $WIN_NT$.~BT folder on USB-Drive.
The file useraccounts.cmd with UserName is made in the Currently Selected $OEM$ Folder.

- For each XP Source the Program Supports now to launch Unattended or Attended Setup.
Therefore a second SetupLoader XATSP for Attended Setup is made ,
where winnt.sif is Patched as winat.sif using gsar.exe
So the extra Setup Option does not take extra space from the USB-stick.

- Multiple XP Install from USB is now Supported (max 9 sources)
http://www.msfn.org/board/SOLVED-Install-M...SB-t114543.html
Run USB_MultiBoot.cmd again using New XP Source and Empty XX_CONTENT Source Folder

- Windows XP Recovery Console from USB is now supported and launched via GRUB4DOS Menu

- Multiple PE (BartPE and UBCD4Win) from USB is supported using Multi_Partition USB-Drives.
INSTALL_DUMMY.cmd was made for dummydisk, which you will find in the makebt Folder.
When dummy.sys is Installed in your OS,
then you can make Multiple Partition USB-sticks with NTFS format,
allowing to combine BartPE and UBCD4WIN or different Vista Versions x86 and x64
http://www.msfn.org/board/Multiple-PE-from....html&st=11
http://www.911cd.net/forums//index.php?sho...20089&st=24
Run USB_MultiBoot.cmd again using New BartPE Source and
using Empty XX_CONTENT Source Folder and No Copy of XP Source.

- Install of Vista from USB is now supported and launched via GRUB4DOS Menu
http://www.msfn.org/board/vista-t114092.html&st=6
http://www.msfn.org/board/Install-Vista-fr...6.html&st=2
For Vista Install from USB, Remove on first Restart your USB-stick.

- Improvement of the Main Menu and the boot.ini Menu's

- GRUB4DOS grldr and grub.exe Updated to grub4dos-0.4.3-2008-05-02


Edit 06 June 2008: New Release USB_MultiBoot_10.zip

- For the Option Edit UserData for XP Setup we have:

A. Unattended Install - UserName = YourName
in winnt.sif file - unattendswitch="Yes" - UserName is used Automatically
useraccounts.cmd with UserName is created in $OEM$ Folder copied to USB-drive

B. Semi-Unattended Install - UserName = None
in winnt.sif file - unattendswitch="No" - UserNames are given Manually at Windows Welcome Screens
useraccounts.cmd is Renamed to Inactive txt file in $OEM$ Folder copied to USB-drive

C. Undefined Install - UserName = Unknown
No Changes are made in winnt.sif file or $OEM$ folder

In all cases Selecting Cancel keeps given Settings for winnt.sif file and $OEM$ folder Unchanged

For Install of XP from USB the program has to remove the [Unattended] Section from the winnt.sif file,
so that unattendswitch="Yes" Setting made by nLite in the [Unattended] Section is lost.
Consequently XP Setup will present in this case Windows Welcome Screens for Creating UserNames.

Selecting Unattended Install in the Editor instead of Cancel will enable to skip the Welcome Screens
by automatic adding the unattendswitch="Yes" Setting to the [Data] Section of the Current_winnt.sif file.
The UserName given at Edit Screen 8 will not be used in the case of XPSOURCE made by nLite.

- In preparing the USB-drive, the file useraccounts.cmd with UserName is made now in the $OEM$ Folder
located in the temporary folder usb_xpbt, so that the original $OEM$ Folder remains unchanged.
The XP Setup Type and the given User Name are Displayed in the Main menu
and in the Status Report Screen just before Copy to your USB-drive is Selected.

- The winat.sif file for Attended Install is now derived from your Current_winnt.sif file
which is more logical than using the preconfigured Attended_winnt.sif file.
In the Attended Install all Setup Parameters are given Manually during the GUI Mode of Setup Windows XP.
Attended Install is always available as Extra Option in the boot.ini Menu.

- Computation of Estimated XP Folder Size to prevent overflow
includes now $WIN_NT$.~BT + cmpnents + I386 + AMD64 + $OEM$ + OEM Folders instead of previously I386 only

- REMOVE_DUMMY.cmd was made to remove dummydisk from the Registry, which you will find in the makebt Folder.
After removal of dummydisk all USB-sticks are seen again as Removable Devices.

- GRUB4DOS grldr and grub.exe Updated to grub4dos-0.4.3-2008-05-07


Download Direct from CD Forum: USB_MultiBoot_10.zip

More Info See Guide with ScreenShots

Regards,

wimb

ScreenShots of USB_MultiBoot.cmd are given in next post.

wimb

Screenshots From USB_MultiBoot_10.cmd

=============1. Introduction =============
Click to view attachment

============ 2. Format Menu =============
Click to view attachment

============= 3. PeToUSB ========================== 4. HP Format Tool ============
Click to view attachment=====Click to view attachment

=============5. Main Menu ==============
Click to view attachment

============= 6. Select XP Source ===========
Click to view attachment

====== 7. winnt.sif from XP Source ? ======
Click to view attachment

====== 8. Edit UserData in winnt.sif ======
Click to view attachment

====== 9. UserData in Current_winnt.sif ======
Click to view attachment

========== 10. USB-Drive Target ==========
Click to view attachment

=========== 11. Main Menu Selected ========
Click to view attachment

============= 12. Status =============
Click to view attachment

============ 13. Copy Select ===========
Click to view attachment

====== 14. Ready - Choice BootDrive Letter ====
Click to view attachment

=============15. END - HELP ===========
Click to view attachment

========== 16. Windows Explorer ==========
Click to view attachment

@wimb_2

Thank you verry much for this great guide
Because of using this guide,I understand a (litle) bit more of bootsectors and the use of the program Mkbt.exe.

Using your guide and program,I'm able to start BartPE,ReatogoPe and programs like them,from the boot.ini instead of Grub4Dos,witch I always wanted.

I'm experimenting a lot with BartPe and ReatogoPE,booting from USB sticks,and your program is a great help for install en reïnstall,after changes,on my USB sticks and saves a lot of time


Greetz wanderer.

@wimb_2

Thank you very much for this excellent guide that I bookmarked carefully. There are lot of useful and valuable information that I re-discover each time. Combined with grub4dos power, this is a guide that all boot lovers should read.

Is there a way to use the multiboot like described here, of cource, not using cdshell?
I edited the files like described there but when i try to install XP in TXT mode, I receive an error message: "File \$WIN_NT$.~BT\biosinfo.inf could not be loaded. The error code is 14".
I already tried to edit the files XPSTP, SETUPLOADER.BIN and TXTSETUP.SIF, but no success
I want to know, if possible, which files point to $WIN_NT$.~BT folder and then to edit those files.

@wimb_2
You did a very great work, keep on going
Thank you very much.

Have a look at this thread:
http://www.msfn.org/board/SOLVED-Install-M...SB-t114543.html

TY ilko, it`s usefull to me


Is there a way using [Unattended] Section with USB_MultiBoot_8.cmd?

If you use that section, Setup will not ask you where to install windows to, on which disk/partition, and will attempt to install on the USB stick. Only if there is no available space, then you will have an option to change destination drive. That's risky.
The limitation comes from Microsoft and their way of installing from hard drives, using winnt(32).exe and $win_nt$.~bt and ~ls folders.

Read here for details:
http://www.msfn.org/board/Issues-with-Setu...424#entry734424

You can find workarounds of using [unattended] section. What exactly do you have in there?

ilko

Is there a way starting windows installation like flyakite does in his guide?
That would be perfect!

Which part are you referring? The menus? You could use ntldr/boot.ini or grub4dos, matter of your personal choice. This was covered in the link, given above.
The contents? This has been answered already in the same link.

Sorry for not being so precise...
I wanted to ask if there is a way to chainload those .DAT files, like cdshell does: "if $lastKey == key[3]; then chain /PRO3.DAT", or something similar.

TY ilko for fast replys.

The principles- Windows Setup determines the type of the installation media- for CD/DVD use I368, for hard disk type- use $win_nt$.~bt for boot portion and Text mode Setup itself and ~ls for the source.
$win_nt$.~bt and ~ls are hardcoded in setupldr.bin and setupdd.sys. Hex editing that gives you another possible boot and source. "SetupSourcePath=..." in txtsetup.sif is ignored when installing from HD media.
This must be launched from Setupldr.bin. Have a different versions of the latter, hexedited in order to start the different sources.
Setupldr.bin can be chainloaded directly from grub4dos GRLDR, or from a bootsector, loaded by NTLDR. Having a few bootsectors, calling setupXP1.bin, setup2k31.bin and so on gives you the ability to launch the different setupldr.bin's from NTLDR.

Whether you'd like to use NTLDR and different bootsectors or grub4dos/GRLDR is your choice.

Or are you asking for an option to start Setup 1 or 2 by pressing 1 or 2, instead of navigating to Setup 1 and 2 with the arrow keys? Is that your question? You may use syslinux in this case. I am still puzzled what exactly you want.

All I want is a fully unattended xp installation from usb/hdd.
Thank You!

@Malin
USB_MultiBoot_8.cmd supports making USB-stick for fully unattended xp installation from USB.
Use the default Settings and Use the supplied winnt.sif file, which is copied to $WIN_NT$.~BT folder on USB-Drive.
For Unattended Install give your key in productkey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX" and remove leading ;

In supplied $OEM$_UserXP Folder you can in useraccounts.cmd Change UserXP for Your Login Name.

Multi-Partitioning the USB-stick using cfadisk.sys or dummydisk.sys was studied

as follow up on reply of jaclaz in http://www.911cd.net/forums//index.php?sho...21362&st=16

I used cfadisk.sys as described by diddy in http://www.911cd.net/forums//index.php?showtopic=18846
so that the USB-stick was indeed seen as Fixed Local Disk and patitioning is possible.

Here is the procedure from diddy for using cfadisk.sys slightly modified by me:

Download Hitachi Microdrive Filter (cfadisk.sys) from http://xpefiles.com/cs/files/folders/hardware/entry616.aspx

Open cfadisk.inf and edit the [cfadisk_device] section
by adding an entry with Hardware-id for your USB-stick and removing the others (DiskIBM)

The Hardware-id for your stick is found from
Device Manager > Diskdrives (USB-stick) > Properties > Details > 1st entry
For my 1GB Corsair test USB-stick I get: USBSTOR\DiskCorsair_Flash_Voyager___1.00


Open Device manager and check for your USB drive in "Disk Drives".
Right click on the entry for your drive and select option to update driver.

* Don't use windows update
* Install from a list or specific location
* Don't search. I will choose the driver to install
* Have disk
* Browse to location of edited cfadisk.inf

Update and restart windows

If the driver installed successfully your USB stick should now be mounted as a Local Disk not Removable Disk

==============================================================================

Then I tried to use dummydisk.sys of Anton Bassov
http://www.codeproject.com/KB/system/sovie...ct_hooking.aspx

as described by Dietmar, but was not successful, as found also by diddy.
http://www.911cd.net/forums//index.php?sho...181&st=1957

On booting XP from Harddisk, the system was in trouble and changed to ControlSet002
but dummy.sys belongs to ControlSet001 so that did not work.

The Current ControlSet being used is found in the HKEY_LOCAL_MACHINE\SYSTEM\Select registry key.

I decided to remove the [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\dummy\Enum]
from the proposed Registry Tweak.
The point is that the Enum Registry key is produced later by the Windows XP System
and must not be introduced with the Tweak.

After using Ghost for Restore of my XP System, I did install dummy.sys again and got success.

The USB-stick was seen as Fixed Local Harddisk and Partitioning is possible and NTFS Format can be used.

So here is the adapted procedure of Dietmar and diddy which worked for me:

* Downloaded the driver dummydisk.sys
* Renamed dummydisk.sys to dummy.sys and copied it to C:\WINDOWS\system32\drivers Folder
* Imported the following file to registry:



After Reboot your USB device is shown at once as Local harddisk.
Also, every new connected USB stick is shown as Local harddisk and Partitioning is possible.
The fact that dummy.sys is NOT USB-stick Specific, makes it more easy to use than cfadisk.sys

When dummy.sys is Installed, then a with Killdisk Erased USB-stick
will be initiated by Windows Disk Manager giving it a MBR.
New Multiple Patitions with NTFS Format can be made.
Setting Active the first partition is needed for booting from the stick.

==============================================================================

Without dummydisk.sys the stick is seen as Removable Device and Disk Manager will NOT intitiate the MBR code,
but we can use mbrbatch.cmd for Creating and Writing XP-MBR code on the previously Erased USB-stick.

First mbrbatch.cmd is used from CMD Window to CREATE File my_xp.mbr in mbrbatch directory.
When the USB-stick is Physical Drive 2 we can WRITE file my_xp.mbr to Drive 2 by:


Change the Drive Number 2 for your USB-stick Drive Number seen in XP Disk Manager.

After Disconnecting and Reconnecting the device, Open Windows XP Disk Manager.
Now it is possible to Create New Partition on USB-stick with Windows Disk Manager.

Allow NTFS Format for Removable Drives by:
Change USB-stick Drive Properties in "optimize for performance"

Open Windows Explorer allows now to Format USB-stick with NTFS FileSystem.

In this way the USB-stick gets a Harddisk like structure wth MBR and a single NTFS Partition
similar to what can be made with HP USB Format Tool.

MBRBATCH of jaclaz is a great tool for this purpose. http://www.boot-land.net/forums/?showtopic=3191

More Interesting Info on USB-sticks Properties See: http://www.uwe-sieber.de/usbstick_e.html

==============================================================================

USB_MultiBoot_8.cmd can be used for realising multiple PE from USB-Drive having two Partitions.
Simply by running the program twice.

First BartPE plus XP Setup Folders are Installed on First Partition as usual.
Then UBCD4Win is Installed on Second Partition, using Empty XX_Content Source Folder and No Copy of XP Source.

In GRUB4DOS menu.lst on First Partition one has to make adjustment for launching UBCD4Win


This works, no problem with manual hexediting and no conflict of PROGRAMS folders

USB_MultiBoot_8.cmd does all the work

Man... long time since i was active on these forums. Exelent work from you wimb !!
I finally got around to use someusb sticks again and my old bartpe usb bootstick was outdated
the
I managed to get about almost everything to work by trial and errors and alotta searching trough these and
other forums;)

I use the NTFS method by the way (formatted stick as NTFS)

First :
DSL i cant get it to work no way ! i have tried 5 different distros, different GRUB4DOS commands etc etc.
Puppy works fine. I manage to get the DSL to initialize but after it scans for usb devices it just says "cant find KNOPPIX file system"

Is it others in here who has problems with DSL ? would be nice to know other users experiences. I have
really tryed everything i possible can imagine.

If someone has sucsessfully managed to get DSL running with a NTFS formatted stick, GRUB4DOS please
post you menu.lst entry for it and what DSL distro you used. also if you have used modified GZ files or other linux files.

Is it possible to add ubcd and ubcd4win to this multiboot usb? If it is, could anybody tell me how or where to start?


Regards

You joking, right?

Post #25 (two posts above yours) tells you specifically about a way for UBCD4win, but the batch comprises it, just re-start from the beginning of the thread and read it, then download the file and read the info within it.

jaclaz

Thanks, very usefull info. Alot of it, but usefull none the less. I tried reading the whole thread in one go, but as expected, it was to much for one being half asleep at the moment. I was looking to try something like this with a USB stick. I have a 2 Gig stick and was going to try the USB NTFS method mentioned to Install XP automated Style. Im guessing I can use the USB_MultiBoot_8.cmd and following youre screenshots post. Im guessing those screenshots are for me. lol!

Yes
The Program is quite simple in use as compared to reading and understanding all the details in the Guide

I found it useful to combine all the background knowledge and references in one Guide,
but I realise that it is not simple to read it in one take.

For Latest Release of USB_MultiBoot.zip:

See Post #10 http://www.911cd.net/forums//index.php?sho...=20089&st=9

wimb

I have a question. I would like to use GAG which I am used to and like, to add UBCD4Win, Bartpe, UBCd, etc. to my USB HDD. Is this method able to work with GAG? What should I try to start with to enable me to multiboot a part of my USB HDD? Stay with this thread or read others also?

Thanks, Plain

Okay. I finally read enough to figure out how to get started. If I get stuck I `ll be back.

Hi all,

Dear wimb_2,
There seems to be a CRC error in "USB_MultiBoot_9.zip" with the file "USB_MultiBoot_9\MULTI_CONTENT\grub.exe"
Do you have another download location?

Because of the CRC error I tried something myself. Used the HP utility with latest version to format my USB stick as NTFS.
Then copied the XP BootFiles ntldr, NTDETECT.COM and boot.ini from my Windows XP Pro SP3 English installation root to the root of the USB stick.
There was no Bootfont.bin present so could not copy that one. Rebooted my computer with the USB stick but it does not load. Now I have used this same USB stick before to boot from only then it was with DOS. But so I know it is bootable. What am I doing wrong?

I want to be able to use my USB stick to boot AeroStudio (which is like cdshell or bcdw) and from there boot images, winpe, etc.
I need it partitioned as NTFS so I can use the whole 4 GB of space. The speed increase is also a nice plus.

Can anyone help on how to achieve this?

There are some similar reports.

The cause can be usually tracked down to "UNKNOWN REASON" , but usually it can be resolved using these two things:
1) Write binary 00's to first, say, 100 sectors of the stick, using a hex/disk editor or a dd-like program
2) making sure that the HP utility has made the partition actually bootable (Active)

For 1) if you do not have a hex/disk editor handy and you do not want to "dirt your hands" with dsfo/dsfi or similar command line dd-like utilities, you may want to try this one (just found - never tested):
http://www.sdean12.org
http://www.sdean12.org/Download.htm
http://www.sdean12.org/zipped2/USBFlashTools100.zip

For 2) you should get beeblebrox:
http://students.cs.byu.edu/~codyb/
and verify that the partition on the USB stick is Active (must have 80 in the Boot field)

However some motherboards have been reported to be simply not capable of booting a NTFS formatted stick (BIOS limit), and some other workaround must be found.

jaclaz

Do not use the latest version of HP USB format tool (2.1.8?), as far as I remember it was not setting the partition active, use 2.0.6 instead, or set it active manually.
For the GRUB.EXE- why don't you just download the latest version and replace grldr/grub.exe?

http://grub4dos.jot.com/WikiHome

Thank you very much for replying. I checked with beeblebrox and indeed the stick's ntfs partition was not bootable (80) so I set it. rebooted and now it doesn't skip the stick but it just hangs on it with a blinking cursor. nothing else. Tried the USB_MultiBoot_9 script and same result after trying to boot off the stick.

And ilko. I just tried it since I will not be using GRUB but AeroStudio. It's sort of a vista looking bootloader which you can design on yourself on how it looks. Very cool. Check http://www.boot-land.net/forums/?showforum=72

Anything else I can try? In stead of using a CD/DVD I would very much like to use my USB stick since it is faster and has much more capacity. And don't forget much smaller in size so you can easily always have it with you.

Retry after having 00ed out initial sectors.

Try again with FAT16 first. (I know you want a bigger sized partition, but bear with me)

Copy to it NTLDR, NTDETECT.COM and BOOT.INI

Confirm that it boots.

Open the stick in Disk Manager.

Delete FAT16 partition.

Create new bigger NTFS partition.

Copy to it NTLDR, NTDETECT.COM and BOOT.INI

If you have problems, install the Hitachi Microdrive Filter cfadisk.sys or dummydisk.sys:
http://www.911cd.net/forums//index.php?sho...20089&st=24

If it still does not boot, it may be a problem of your motherboard BIOS, there are reports that using the grub4dos grldr.mbr MBR (+grldr) works better, and you may also use FAT32 which is strongly suggested INSTEAD of NTFS on Flash based devices.

jaclaz

New Release USB_MultiBoot_10.zip available,

See Post #10 http://www.911cd.net/forums//index.php?sho...=20089&st=9

Download Direct from CD Forum: USB_MultiBoot_10.zip


wimb

I'm new here, and trying out these tools for my Eee 701. When I downloaded it, my virus scanner detected a Rootkit trojan in dummy.sys. I just want to be re-assured that this is indeed a safe file.
I didn't see any disclaimers yet regarding virus checkers, so I though I would mention it. And the last thing I'd want is an infected rootkit installed on my SSD flash drive.

Thanks in advance,
----Z.

It's not unusual for an AV to find fault with a PE plugin. Some are designed to circumvent PC security to resolve and fix problems.

When an av flags a file you want to keep try running the file through another av, several online scanners are available. If the file is flagged by all of them then you will have to decide whether to ignore the warnings or to discard the plugin.

I can assure you that USB_MultiBoot_10.zip does not contain a Rootkit trojan.
What Virus Scanner did you use ?
It must have been a false positive warning that you have received.

According to

• Avast 4.8 Free Home Edition http://www.avast.com/eng/download-avast-home.html
• BitDefender Online Scanner http://www.bitdefender.com/scan8/ie.html

USB_MultiBoot_10.zip is Save.

There is now an easy-to-read Tutorial on Install of XP from USB available at BootLand Forum.
Together with the ScreenShots of USB_MultiBoot_10.cmd and the List of FAQs this will be a handy source of information.

Links on Install of XP from USB using USB_MultiBoot_10.cmd

• Download Program - USB_MultiBoot_10.zip - and Mirror - USB_MultiBoot_10.zip - (Thanks to Siginet)
• Tutorial on Install of XP from USB at BootLand Forum - Tutorial
• ScreenShots of USB_MultiBoot.cmd - ScreenShots
• List of FAQs at MSFN Forum - FAQs
• Install XP from USB at MSFN Forum - Install XP from USB
• Install XP from USB - Support and Changes USB_MultiBoot.cmd - Support and Changes
• Guide for MultiBoot USB-stick with boot.ini Menu - Guide
• More Help with Bookmarks is available in the Help_Info Folder in USB_MultiBoot.zip

There is an Alternative Download from BootLand Forum: USB_MultiBoot_10.zip

Regards,

wimb

The scanner I have is AVG Free.
I was nearly certain the file was not malicious because of the need for it and its purpose for these tools.
Since I hadn't tried any of the previous versions, I err'ed on the side of caution that maybe it might have been specific to version 10.
But I now have some assurance from those who have used it including yourself.
Thanks much,
-----Z.

Not a bad side to be on.

Why does this instructions is so long ? It is too long for me. I prefer instruction by pictures.

ScreenShots of USB_MultiBoot_10.cmd - ScreenShots

Tutorial on Install of XP from USB at BootLand Forum - Tutorial

Dear wimb_2

Install XP from USB-stick is working fine,so thank you for that.

Is it possible to use the "repair" option as with the CD install,also from USB-stick?

"To repair the selected Windows XP installation,press R."



Thanks in advance,wanderer.

Hi wanderer,

USB-sticks prepared with USB_MultiBoot_10.cmd can be used for Repair Install.
Therefore a rule in boot.ini on Harddisk was made by Install XP from USB.
If not present you have to add this rule to your Harddisk C:\boot.ini file prior to booting from stick.



There is also a NEW technique available:

*** Install XP from USB AFTER Booting with PE from HDD or USB ***

USB_XP_Setup.cmd can be used for Repair Install as well and is described at Boot Land Forum:
http://www.boot-land.net/forums/?showtopic=5306

XP Setup Source Folder must always be on USB-stick or on partition 1 of ANY Harddisk.

This way of Install of XP from USB can also be used without BIOS Support.
Booting for XP Setup occurs all the time as normal from the C-Install Drive.
Thus the USB-stick does not need to be bootable
and it is not needed that the motherboard supports booting from USB.

Cheers,

wimb

Hi wimb_2


Until now I used USB_MultiBoot_5.cmd,so I tried nr. 10.

I Have now the XP source and Winbuilder on the USB-stick with this boot.ini/


Setup goes direct to added screen,still no option to select a Windows partition to repair.

Greetz