Utility for creating FAT/FAT32/NTFS BartPE USB-Sticks/HDD's Options

[fuwi]

Bootable USB-Drive Utility for creating bootable FAT/FAT32/NTFS BartPE USB-Sticks and Harddrives

Download-Link : http://www.fuwi.ethz.ch/files/USB-Boot_Utilities.zip

Some screenshots here

Guide: Kickbooting a BartPE USB-Stick or Harddrive (created with the 'Bootable USB-Drive Utility') directly from the BartPE-CD:
http://www.911cd.net/forums//index.php?s=&...st&p=158496



June-23-2010: v1.8.6
Hardware Detection Tool (HDT) updated (latest pci.ids).
New memtest86+ version 4.10
Some other files updated.
'Create_WinPE_Kicker-CD.iso.cmd' now also works under 64-bit Windows versions.

May-11-2010: v1.8.4
some files updated.
bug fixed: Create a new bootable harddisk (HDD-Partition created under Windows 7) -> blinking cursor instead the bootmenu.

February-08-2010: v1.8.1
a small bug fixed, thanks ChinaDragon (http://www.911cd.net/forums//index.php?sho...st&p=161159)
Hardware Detection Tool (HDT) updated (latest pci.ids)

January-26-2010: v1.8.0
some internal functions enhanced (e.g. more configuration settings in the file 'BOOTABLE_USB-DRIVE.cmd').
bootscreens redesigned, see screenshots
script for changing the grub4dos-bootmanager configuration on a working USB-drive (switching grub4dos-start between MBR and Bootsector -> CHBOOT.cmd in \GRUB4DOS\CHBOOT\)
new utility in the "Others" menu: Hardware Detection Tool (HDT). This replace the "CPU Identification Utility" in the previous version.
new memtest86+ version 4.0

August-11-2009: today, there was a buggy version v1.7.2a for some hours on my server!
please replace it with the updated version v1.7.2b !

August-07-2009: v1.7.2
small bug fixed (no drive-icon if PE-dir = i386 on the USB-Drive).
some internal functions enhanced (e.g. more configuration settings in the file 'BOOTABLE_USB-DRIVE.cmd').
Infoscreen when selecting 'Kick-Boot BartPE (fast)' in the bootmenu of the USB-Drive but no valid kickboot-image is on that drive (e.g. after 'Update').

May-27-2009: v1.7.0
unfortunately, in version 1.6.9 from yesterday i have packed a wrong version of the PEBuilder-Plugin
the CD-nu2menu is now working in the new version v1.7.0

May-26-2009: v1.6.9
newer version of robocopy, the Daylight Saving Time switching problem is solved.
now Server 2003 can be used as PEBuilder-source (no need for patching the Server 2003-setupldr.bin, this is done by the Utility automatically).
optional starting the 'Boot-Kicker Image Creator' after each new creation or update of an USB-Drive
(set UpdKicker=1 or 0 in 'BOOTABLE_USB-DRIVE.cmd').

May-13-2009: v1.6.8
support for i386 folder on the USB-drive. Just rename the minint folder to i386 and make
an Update of the USB-drive, that's all. You don't have to patch the files setupldr.bin or
ntldr, this is done by the Utility automatically. Also the opposite way: rename the i386
folder to minint, then make an Update, that's it.
In the previous versions, there was only one script for customizing an USB-drive:
'customize.cmd' in the folder 'Custom', but this script is only called from the function
'Create a new bootable USB-Drive'. In the new version, there is an additional script 'custom-upd.cmd'
in the folder 'Custom'. This script is called from the function 'Update BartPE on a USB-Drive',
so you can make your special updates without re-creating the USB-drive.
Note: predefined (but commented out) in 'custom-upd.cmd' is an option to re-install grub4dos
back to the MBR (default it is in the bootsector). Activate this option if you have boot-problems
with non-standard bootsectors.

April-30-2009: v1.6.7
filesystem for USB-Sticks can be switched between FAT, FAT32, NTFS and no-reformat
Submenu 'Others' (menu2.lst) in Main-Menu (menu.lst).

April-23-2009: v1.6.6
option to bypass the internal formatter on creating new USB-Sticks: create a dummy file
'format.ok' on the already (correctly) partitioned and formatted stick, then select 'Create a new bootable….'
as usual. Only 1 file has changed (budu.cmd) -> update all occurrences of budu.cmd in your installation.

Mar-19-2009: v1.6.4
grldr starts now in bootsector instead from MBR (fix F9-bootmenu problem on HP DC 7x00).
users of the PEBuilder-plugin should also update the files & folders in the plugin 'files'-folder :
-> delete everything in 'files', copy all files & folders from 'USB-Boot_Utilities.zip' to 'files').

Mar-10-2009: v1.6.3
new version of grldr, bootscreens redesigned
(hiding the ‘F1 / F2’ - Linux stuff, see screenshots here).

Feb-27-2009: v1.6.2
new bootscreen for drives without BartPE.
added a MsgBox (relevant for the kick-booting feature after re-creating or updating an USB-drive).

Feb-23-2009: v1.6.1
now Vista/Windows 7 UAC compatible.
now a PEBuilder-plugin included:
- adds the utility to the nu2menu/ShellPE-menu (for creating/updating USB-drives in BartPE).
- adds a script ‘Bootable USB-Drive Utility.cmd’ to the CD-root (executable under XP/Vista/Win7,
the CD is automatically source for the PE-files (no need to edit ‘Config_SourcePath.cmd’).


Installing the Utilities:
Copy USB-Boot_Utilities.zip in your PEBuilder root-folder (where PEBuilder.exe is).
Unzip the archive to a new folder 'USB-Boot_Utilities' (same hierarchy level as 'plugin', 'drivers' etc).
Run 'Bootable_USB-Drive.cmd' in the 'USB-Boot_Utilitys'-folder.

if you get the message 'No valid BartPE files found!'
then you have to change the value of the variable 'SourcePath' in the file 'Config_SourcePath.cmd' change in accordance with your needs.

There is also a BartPE plugin included in USB-Boot_Utilities.zip:
- adds the utility to the nu2menu/ShellPE-menu on your BartPE-CD (for creating/updating USB-drives in BartPE).
- adds a script ‘Bootable USB-Drive Utility.cmd’ to the BartPE-CD root (executable under XP/Vista/Win7).
-> the CD is automatically source for the PE-files (no need to edit ‘Config_SourcePath.cmd’).

Setup/Update the plugin:
1. delete everything in the 'files' folder of the plugin
2. copy all files & folders from USB-Boot_Utilities.zip to the 'files' folder
3. delete the folder 'PEBuilder-Plugin' in the 'files' folder

USB-Harddisks:
Any existing primary partition on a USB-Harddisk (FAT,FAT32 or NTFS, must not be active)
can be used as the boot-volume. It's recommanded to use the first partition,
because only the first partition can be used for 'self Kick-Booting'.
(for Kick-Booting with the Kicker-CD, the partition number has no influence).
Partitions will not be reformatted, so existing files and folders are preserved.

Executing Create_WinPE_Kicker-CD.iso.cmd also expands the grub4dos-menu on the USB-drive
with a 'Kick-Boot BartPE'-entry (for faster booting). You have to run this script after each Update!

Note:
The first postings in this thread (up to Oct 10 2008) are related to my older tool "BartPE USB-Stick Utility"
which can create a special kind of FAT32 BartPE USB-Sticks (DOS7-boot, loading BartPE via grub4dos started in config.sys).
This utility is still available here, but it is recommanded, that you try first the new "Bootable USB-Drive Utility".

The postings for the actual 'Bootable USB-Drive Utility' are starting here

fuwi

This post has been edited by fuwi: Jun 23 2010, 10:12 AM

[jaclaz]

Good!

Hmmm, if I get it right it is a "wrapper" around the command line version of the HP USB utility, the interesting point for me is the use of gpatch.exe to write "80" at offset 64 or 36, that should mean that you have experienced that in some cases this value can be "81" or "82", but what is the reason for re-writing the bootsector with bootsect.exe?

jaclaz

This post has been edited by jaclaz: Jun 25 2008, 08:50 AM

[fuwi]

@jaclaz

my reply comes tomorrow, i have 30 degree celsius in my office, i go swimming now...

fuwi

[fuwi]

@jaclaz

1.
the interesting point for me is the use of gpatch.exe to write "80" at offset 64 or 36
...
2.
what is the reason for re-writing the bootsector with bootsect.exe?

1.
I found out, that when i wipe a USB-Stick (beginning with physical sector 1, writing '00', for example with roadkil's diskwipe)
and after that, i run the USB-Stick.cmd under XP without patching the bootsector (after formatting with hpusbf.exe), the 'Drive ID' is
0 instead 80h, and the Stick doesn't boot, see screenshot1

2.
The reason for re-writing the bootsector with bootsect.exe:
when i run the USB-Stick.cmd under Vista without re-writing the bootsector after formatting with hpusbf.exe, the Stick has a Vista-style
bootsector (BOOTMGR instead NTLDR, and the language is the lanuage of the Vista-OS), and the Stick doesn't boot, see screenshot2

After re-writing the bootsector with bootsect.exe, i have a valid NTLDR-style bootsector in english, see screenshot3

fuwi

This post has been edited by fuwi: Jun 26 2008, 04:20 AM

[ChinaDragon]

@fuwi

CODE

:: ----------------------------------------------------------------------------
:: if the folder with the BartPE USB-Stick Utility is located on the BartPE-CD:
:: set SourcePath=\

:: if the folder with the BartPE USB-Stick Utility is located in the PEBuilder:
set SourcePath=..\BartPE\

What is the mean for the SourcePath ? refer to the tools directory of "USB-Stick" or the PE output source (e.g. D:\PeBuilder\pebldr )

[ChinaDragon]

@fuwi

Personally, I change it to ..\PeBldr\, and finally I get a stick as below

CODE

Directory of F:\

04/13/2008 22:13 47,564 NTDETECT.COM
04/14/2008 00:02 260,288 ntldr
05/14/2008 09:23 167 winbom.ini
06/23/2008 16:44 0 WIN51IP
06/23/2008 16:44 0 WIN51IP.SP3
11/02/2004 15:05 46 autorun.inf
06/23/2008 16:42 <DIR> minint
06/23/2008 16:44 <DIR> shortcuts
06/23/2008 16:44 <DIR> PROGRAMS
6 File(s) 308,065 bytes
3 Dir(s) 1,322,803,200 bytes free

But it can't boot from the USB, it is sure work before by win98 format with grub4dos. ComPro way

Sorry for my bad English

This post has been edited by ChinaDragon: Jun 26 2008, 06:46 AM

[fuwi]

@ChinaDragon

which file system did you select? FAT or FAT32?

fuwi

[ChinaDragon]

@fuwi

Thank you for your attention, I choice the [n] with file system FAT32.

CODE

-------------------------------------------------------
[n] = Create a (n)ew bootable BartPE USB-Stick - FAT32
-------------------------------------------------------
[f] = Change (f)ilesystem for Option [n] (FAT or FAT32)
[x] = E(x)it

Enter your choice [n,f,x]: n

It has a BLACK screen with a flashing underscore at the top of left hand side only, the system halted

[fuwi]

@ChinaDragon

when you change the filesystem for Option [n] to FAT (key 'f' <enter>)
and re-create your Stick with Option 'n' -> does it boot?

fuwi

[ChinaDragon]

@fuwi

Work fine now with FAT file system, what going wrong for the FAT32 ?

Your work great, many thank

[fuwi]

@ChinaDragon

The most compatible format for a bootable flash device is FAT16. Only "some" boards bios can boot FAT32.

fuwi

[ChinaDragon]

@fuwi

Just do a test for the FAT32 format, for same USB stick and booting machine, I think the issue is not related to the bios. It can boot to Win98 DOS shell.

CODE

D:\PEBUILDER\USB-Stick>hpusbf.exe I: -FS:FAT32 -Q -Y -B:Win98se -D:minint\SYSTEM32 -S:D:\PEBUILDER\USB-Stick\Stick-Flag

HP USB Disk Storage Format Tool, Version 1.00.012 (11/13/2003)
Copyright © 2003 Hewlett-Packard Development Company, L.P.

The type of the current file system is FAT32.
QuickFormatting 1.92GB...
Initializing file system structures...
Format completed successfully.

System files transferred successfully.

Files transferred successfully.

The type of the new file system is FAT32.

Volume Serial Number is AC38-F653

   2,058,477,568 bytes total disk space.
   2,058,141,696 bytes available on disk.

           4,096 bytes in each allocation unit.
         502,558 total allocation units on disk.
         502,476 available allocation units on disk.

This post has been edited by ChinaDragon: Jun 26 2008, 10:57 AM

[jaclaz]

@ChinaDragon

The matter has not been solved yet.

Read these:
http://www.911cd.net/forums//index.php?sho...=20747&st=0
http://www.boot-land.net/forums/?showtopic=4756

There are reports by ktp that using the grldr.mbr+grldr from grub4dos to directly chainload the loader (thus by-passing the bootsector) works, so the problem MUST lie in something in the bootsector for FAT32, but what exactly I cannot say:
http://www.boot-land.net/forums/?showtopic=1339

jaclaz

[sanbarrow]

@ fuwi

I tested with Kingston 8 Gb DataTraveler
when using 2k3-sp2 as source I get the message "ntldr not found" when tyrying to boot a HP-notebook. I tried to replace the ntldr (255kb) with one from 2k3-sp1 to no avail.

anyway - thanks for your work

[ChinaDragon]

@ jaclaz , fuwi

Thank you for your information, I will wait for the solution.
Currently I'm playing with the FAT32 + Grub4dos then clainload the loader for launching my PE, very interesting.

[jaclaz]

@ jaclaz , fuwi

Thank you for your information, I will wait for the solution.
Currently I'm playing with the FAT32 + Grub4dos then clainload the loader for launching my PE, very interesting.

If you are into experimenting, try also this method:
http://www.boot-land.net/forums/?showtopic=5000

Not at all straightforward, but guaranteed to create a non-fractional cylinder/head partition table , if this is the problem, this method could solve it.

NOTE, as is it won't work on Vista, it needs 2K/XP files:

CODE

SET Sysfile=%SystemRoot%\System32\dmadmin.exe
REM SET Sysfile=%SystemRoot%\System32\spcmdcon.sys
REM SET Sysfile=%SystemRoot%\ServicePackFiles\I386\setupdd.sys

to get the MBR code and uses the "normal" FORMAT command, thus if used on Vista it will create a Vista bootsector.

jaclaz

This post has been edited by jaclaz: Jun 26 2008, 01:57 PM

[ChinaDragon]

@jaclaz

A bit of hard for me, it is very nice tutorial, I will study on it. thank a lot.

[fuwi]

@all

because of the problems with fat32-booting, i have changed my BartPE-USB Utility.

If you select FAT32 as filesystem, now a DOS7 Boot-Stick is created, and BartPE is started via grub4dos.
For FAT as filesystem -> nothing has changed.

Download the new version and test it please

(ChinaDragon, sanbarrow with the 8GB DataTraveler)

fuwi

This post has been edited by fuwi: Jun 30 2008, 09:31 AM

[Ed_P]

Don't you need a menu.lst file similar to:

CODE

color white/blue  black/light-gray
default 0
timeout 0
fallback 1

title Bart-PE
chainloader /MININT/SETUPLDR.BIN

title Return to DOS
chainloader /IO.SYS

Or a fallback to the hd's system?

[ChinaDragon]

@Ed_P

They embed the menu in the config.sys

CODE

device=\grub4dos\grub.exe --config-file="timeout 0;default 0;title Booting BartPE;find --set-root /ntldr;chainloader /ntldr"

@fuwi
Still can't boot with FAT32 file system
It has a BLACK screen with a flashing underscore at the top of left hand side only, the system halted.

I just back to use the ComPro way to make again, it work

This post has been edited by Ed_P: Jun 27 2008, 11:46 AM

Reason for edit: Changed Codebox tags to Code.