Guide for MultiBoot USB-stick with boot.ini Menu Options

[wimb_2]

**** 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

This post has been edited by wimb_2: May 2 2009, 04:53 AM

Attached File(s)

 MBR_Backup.zip ( 1.38MB ) Number of downloads: 2287

 

[wimb_2]

***** 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

This post has been edited by wimb_2: Jun 7 2008, 02:33 PM

[wimb_2]

ScreenShots of USB_MultiBoot.cmd are given in next post.

wimb

This post has been edited by wimb_2: Apr 3 2008, 04:29 AM

[wimb_2]

Screenshots From USB_MultiBoot_10.cmd

=============1. Introduction =============


============ 2. Format Menu =============


============= 3. PeToUSB ========================== 4. HP Format Tool ============

=====

=============5. Main Menu ==============


============= 6. Select XP Source ===========


====== 7. winnt.sif from XP Source ? ======



====== 8. Edit UserData in winnt.sif ======


====== 9. UserData in Current_winnt.sif ======


========== 10. USB-Drive Target ==========


=========== 11. Main Menu Selected ========



============= 12. Status =============


============ 13. Copy Select ===========


====== 14. Ready - Choice BootDrive Letter ====


=============15. END - HELP ===========


========== 16. Windows Explorer ==========


This post has been edited by wimb_2: Jun 6 2008, 01:26 AM

[wanderer]

@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.

[ktp]

@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.

[Malin]

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.

[ilko]

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

[Malin]

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

TY ilko, it`s usefull to me

Use for Preparing USB-Drive Only winnt.sif file without an [Unattended] Section and with MsDosInitiated="1"

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

[ilko]

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

This post has been edited by ilko: Apr 14 2008, 04:36 PM

[Malin]

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

[ilko]

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.

[Malin]

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.

[ilko]

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.

This post has been edited by ilko: Apr 14 2008, 05:34 PM

[Malin]

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

[wimb_2]

- 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 $WIN_NT$.~BT folder on USB-Drive.
For Unattended Install give your key in productkey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX" and remove leading ;
Use for Preparing USB-Drive Only winnt.sif file without an [Unattended] Section and with MsDosInitiated="1"

- 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.

- 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.

Download Direct from CD Forum: USB_MultiBoot_8.zip

@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.

This post has been edited by wimb_2: Apr 18 2008, 02:18 AM

[wimb_2]

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

CODE

[cfadisk_device]
%Microdrive_devdesc% = cfadisk_install,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:

CODE

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\dummy]
"Type"=dword:00000001
"Start"=dword:00000000
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,64,00,75,00,6d,00,6d,00,79,00,2e,\
00,73,00,79,00,73,00,00,00
"DisplayName"="USB-Massenspeichertreiber"
"Group"="System Reserved"
"Tag"=dword:00000001

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:

CODE

mbrbatch.cmd CREATE my_xp.mbr
mbrbatch.cmd WRITE my_xp.mbr 2

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

CODE

title UBCD4Win - Load PELDR From USB-HD 0 - Partition 1
root (hd0,1)
chainloader (hd0,1)/PELDR

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

USB_MultiBoot_8.cmd does all the work

This post has been edited by wimb_2: May 4 2008, 03:13 AM

[Czar]

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.

[rmi]

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

[jaclaz]

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