Windows 7/8 or 7PE is needed to make Boot Manager Menu.
BOOT_USB - Make Bootable USB-Drives
Booting with Grub4dos Menu and using Boot Image files
Download - BOOT_USB - mirror
In Win7 OS Set User Account Control Off and Reboot
Run the SFX SelfExtractor BOOT_USB.exe and Extract to simple path.
In this way you will get on your Local Harddisk the folder BOOT_USB from which you can launch 2 Programs:
- BOOT_USB.exe - Make USB-Drives booting with Grub4dos Menu and using Boot Image files
- USB_Part_Flip.exe - Change which primary partition of USB-stick is visible in Windows
BOOT_USB2.png 35.9KB 315 downloads
Features of BOOT_USB.exe
- Format USB-stick e.g. NTFS with FAT32 2nd partition
- Make Grub4dos Menu on USB for booting Boot Image files (types IMG or ISO or VHD) e.g. Portable Windows XP and Windows 7
- Make BootManager Menu on USB-drives for booting Win7 VHD Boot Image files (requires Win7 or 7PE as OS)
- Copy Source folder e.g. BOOT_USBMULTI to USB Target Drive
- Copy Bootable USB-drives (from drive to drive) by using Exclude list makebtExclude_Copy_USB.txt
- Change MBR Bootcode of USB-disks - Select Grub4dos (preferred) Or Standard Windows XP MBR BootCode
- On NON USB-drives Make Grub4dos Menu for booting Boot Image files (types IMG or ISO)
- Add in BootManager Menu of Windows 7 - to Start Grub4dos Or to Start XP
Make Grub4dos Boot Menu on Harddisk or USB-drive for Boot Image files e.g.
- BartPE / UBCD4Win / LiveXP - IMG or ISO files booting from RAMDISK
- Parted Magic - Acronis - LiveXP_RAM - CD - ISO File - http://partedmagic.com/
- Superfloppy Image files e.g. boot 15 MB FreeDOS or 25 MB MS-DOS Superfloppy images
- XP Recovery Console Image RECONS.img booting from RAMDISK - http://www.911cd.net...showtopic=21883
- 7pe_x86_E.iso - Portable Windows 7 PE booting from RAMDISK - http://www.911cd.net...showtopic=23931
- XP-1.img - XP Image file booting as FILEDISK or RAMDISK using WinVBlock or FiraDisk driver
- Win7-1.vhd - Win7 VHD file booting with VHD HBA driver Or as FILEDISK and as RAMDISK using WinVBlock or FiraDisk driver
Boot Portable Windows XP Or Portable Windows 7 from Grub4dos Menu on USB-drive
Also part of IMG_XP package - More Info - http://www.911cd.net...showtopic=23553
IMG_XP_Create.exe - Use button NEW for direct Install of XP in Boot Image file by using WinVBlock driver
IMG_XP_Compact.exe and VHD_W7_Compact.exe can be used to make Portable Windows XP and Win7 VHD Image files
More info USB_Part_Flip.exe - http://www.911cd.net...showtopic=24392
Install of XP or Windows 7 from USB After Booting with 7 PE and
by using WinNTSetup2_x86.exe and Setup ISO file in Virtual drive
0. Use BOOT_USB.exe to prepare USB or HDD drive for booting with Grub4dos Menu and using 7 PE Boot Image file
- Info BOOT_USB - http://www.911cd.net...showtopic=24424
- Info Make_PE3 - http://www.911cd.net...showtopic=23931
1. Boot from USB or HDD with 7 PE loaded in RAMDISK - use Grub4dos Boot Menu and 7pe_x86_E.iso Boot Image file
2. Use R-mouse to Mount Windows Setup ISO in ImDisk virtual drive
- If needed first Install ImDisk driver by running imdiskinst.exe (also available in makebt folder)
3. Quick Format TargetDrive - use NTFS FileSystem
4. Run WinNTSetup2_x86.exe and prepare Target drive for Install of XP or Windows 7
Thanks to JFX - http://www.msfn.org/...-winntsetup-v2/
5. Reboot from Target Drive and Install XP or Windows 7
Instead of 7 PE you can use any other way of booting that allows you to Format and prepare your Target Drive.
You might decide e.g. to boot with Portable Windows XP IMG or with Windows 7 VHD from USB
In any case you can use WinNTSetup2_x86.exe to prepare your Target drive for Install of XP or Windows 7
See Tutorial file XP-W7-Setup.txt in IMG_XPHelp_Info folder
Info IMG_XP - http://www.911cd.net...showtopic=23553
Download - IMG_XP
The advantage is that you never boot from USB during XP Setup
and that makes everything much more reliable and you have full control of what you are doing.
Also using a single XP Setup ISO file mounted in ImDisk Virtual drive is much more reliable
than having a bunch of XP Setup files on USB.
Transfer of the ISO file to USB is much faster and easier to maintain.
Instead of USB-stick it is much better to use Portable 2.5 inch USB-harddisk e.g. Samsung S2
As easy to carry and connect, but much higher speed and more capacity.
How to prepare XP Setup Source ? - Prepare XP Setup ISO file with integrated UpdatePack and DriverPacks
Take care that your XPSOURCE Folder is located on your Harddisk in a simple Path without SPACES.
Copy the Content of your Windows XP Setup CD to your XPSOURCE Folder on Harddisk
First Integrate ServicePack SP3 in your XP-SP2 Source (don't use here nLite).
Download from - http://www.microsoft...i...ng=en&id=24
In Command Window use for English version and XPSOURCE folder on drive E:
Siginet's RyanVM Integrator 1.6 can then be used to Integrate Windows UpdatePacks in the XP-Source.
Download preferred version RVM Integrator 1.6.1 Beta 2.1 - http://www.mediafire.com/?ynajonymmnz
Windows XP UpdatePacks and Addons:
Work according to Section 2 in - http://www.911cd.net...showtopic=21883
For Install of XP on a modern system with SATA Drives it is needed to use DPsBase.exe
for Integrating in your XPSOURCE 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 Install-Drive and can prevent a lot of XP Install Boot Problems.
Use DPsBase.exe to Integrate DriverPacks Chipset + Processor + MassStorage + LAN + WLAN DriverPacks
which will then be located in OEM Folder in your XPSOURCE folder
Always first use RyanVM Integrator and then use DPsBase to Improve your XP-Source
DPsBase makes presetup.cmd in folder I386 and changes the I386winnt.sif file for use of DriverPacks
presetup.cmd in folder I386 will start decompression of DriverPacks located in OEM folder
at the beginning of GUI-mode of XP Setup, which does NOT take to much time for the 5 DriverPacks
You should select to Keep The Drivers for Chipset + Processor + MassStorage + LAN
Then WINDOWSDriverPacks is about 135 MB which is acceptable and provides a lot of extra driver support
which is useful to make XP Universal and adapt easily to very different hardware.
In that case the DevicePath is set accordingly in key
so that XP can automatically make use of these drivers for adjusting to New Hardware
When you don't use nLite, you can copy the supplied $OEM$ folder to your XP Source folder
Change $OEM$ folder to your needs for UserAccounts and Registry Tweaks and Adding Drivers
CMDLINES.TXT is used for making UserAccounts and install of Registry Tweaks at T-12
Info see: http://unattended.ms.../unattended.xp/
Use DriverForge.v4.5.4.exe to Install from C:Drivers at T-9 of GUI XP Setup (just for the last Reboot).
DriverForge.v4.5.4.exe was made by kickarse http://www.msfn.org/...howtopic=110783
At end of TXT-mode XP Setup the folder $OEM$$1Drivers is copied to C:Drivers
and $OEM$$1InstallDriverForge.v4.5.4.exe is copied to C:Install
For Auto Use of DriverForge at T-9 add uncompressed driver folders in $OEM$$1Drivers
and Uncomment two rules by removing ; in winnt.sif file copied from winnt_sif to your I386 folder
This is very useful for Install of your well known Audio and Video driver during GUI-mode of XP Setup.
[SetupParams] UserExecute = "%SystemDrive%INSTALLSetupPar.cmd"
PnP Drivers specified in winnt.sif can be added to $OEM$$1Drivers
TEXTMODE Drivers defined in winnt.sif and located in $OEM$TEXTMODE folder of the XP Source
can be used instead of using F6 floppy for MassStorage Drivers.
The content of the $OEM$TEXTMODE folder is copied to XP Setup BootFolder $WIN_NT$.~BT$OEM$
See cdob and allanf in http://www.boot-land...?...5306&st=180
Smart Driver Backup 2.12 of Jaque is very useful to Backup your drivers before install of XP
How to make XP Setup ISO File ?
- Use BBIE (see below) or Isobuster to Extract Boot Image bootsect.bin from Original bootable XP Setup CD
bbie will make image1.bin that you can copy as bootsect.bin to XP Setup source folder
- Reduce Size of XP Setup Source folder (if needed to fit on CD then remove folders LANG WIN9XMIG WIN9XUPG)
- Use ImgBurn and bootsect.bin to make Bootable CD
1. Remove 3 folders LANG WIN9XMIG WIN9XUPG - reduction in size = 135 MB
2. Run ImgBurn - Portable Tool in PStart Menu - IMG_XPMULTIPStartProgsImgBurn
- Select Write files/folders to disc
- Output - Select Image File
- Browse Source folder and Select your XP Setup Source folder
- Browse Destination file - Give Name e.g. XP-Setup.iso
- Labels ISO 9660 - Give Name e.g. XP-Setup
- Advanced Restrictions - ISO9660 - Select Level X and DOS CharSet with 4x Checkbox On (allow ...)
- Bootable Disc - Make Image bootable - Checkbox On - Browse Boot Image - Select bootsect.bin file
- Bootable Disc - Emulation Type = None
Load Segment = 07C0
Sectors to Load = 4
BBIE - Bart's Boot Image Extractor v1.0, © 2001, Bart Lagerweij
will make BOOT_USBmakebtimage1.bin that you can rename as bootsect.bin
Format Stick using BOOT_USB.exe
An AutoIt3 Routine was created to Format USB-sticks with a Harddisk like structure and NTFS/FAT32/FAT FileSystem.
- First 100 Sectors of USB-stick are erased quickly using dsfi.exe and file Erase_100.bin
- MBR BootCode is obtained from XP file dmadmin.exe just as in MBRBatch.cmd made by jaclaz
- Partition Table entry is constructed from the USB-stick CHS geometry as derived from MBRWiz.exe /list
- Partition is ending on Cylinder boundary to improve bootability as compared to HP Format Tool, which would give a CHS-LBA unbalanced partition.
- CHS Knockout Patches and Dummy Second Partition are user selectable options to improve USB-stick bootability
CHS Knockout Patches can be applied to XP-MBR BootCode (HP Patch)
and to FAT32 or NTFS BootSector to improve bootability as described by Clemens Fruhwirth and tested by cdob to be useful.
- Apply HP Patch to USB-stick XP-MBR Code for CHS Knock-out
Change at offset 0xCA 3 bytes - 0xB8 0x01 0x02 --> patched to 0xEB 0x1A 0x90
- Apply 4x NOP Patch to FAT32 and NTFS BootSector for CHS Knock-out
FAT32 boot sector ("MSDOS5.0" found at offset 0x03) :
Change at offset 0xE6 - 4 bytes - 0x0F 0x82 0x4A 0x00 --> patched to 0x90 0x90 0x90 0x90
NTFS boot sector ("NTFS" found at offset 0x03) :
Change at offset 0xD9 - 4 bytes - 0x0F 0x82 0x3A 0x00 --> patched to 0x90 0x90 0x90 0x90
USB-sticks with Dummy Second Partition of about 8 MB (using 1 Cyl in case of n/255/63 geometry)
can be generated to further improve bootability as described by online
The Format Stick routine was further improved for FAT and FAT32 FileSystem,
by patching after Format two important bytes which determine bootability of USB-stick.
- MBR - Reset FAT FileSystem byte = 0E (LBA) at offset 0x1C2 in MBR, after format it was 06 (CHS) and not bootable
- FAT BootSector - drive-id patch 0x80 at offset 0x24 , after format it was 00 and Not bootable
- MBR - Reset FAT32 FileSystem byte = 0C (LBA) at offset 0x1C2 in MBR, after format it was 0B (CHS) and Not bootable
- FAT32 Bootsector - drive-id patch 0x80 at offset 0x40 , after format it was 00 and Not bootable
FAT and FAT32 USB-stick are NOT bootable without patching these two critical bytes, and flashing cursor or Disk Error would be the result.
The problem is that Windows OS all the time tries to reset these bytes to NON-bootable value.
But this problem was overcome in the present procedure.