Help - Search - Members - Calendar
Full Version: How To: Boot BartPE from a FAT32 formatted USB drive (Easy)
UBCD4Win Forums > Other Support > USB Booting Support
Pages: 1, 2
ComPro
BOOT BARTPE FROM A FAT32 FORMATTED DRIVE (Great for 8+ gigabyte drives)
---
Tools Required
  • HP USB Disk Storage Format Tool - http://downloads.pcworld.com/pub/new/utili...als/SP27608.exe
  • GoCoding.com's PEtoUSB.exe - http://gocoding.com/projects/petousb/V2TU0...USB_3.0.0.7.zip
  • Windows 98SE Bootable Floppy Disk - http://files.frashii.com/~bootdisk/newjersey/boot98se.exe
  • GRUB4DOS 0.4.3 - http://superb-east.dl.sourceforge.net/sour...b4dos-0.4.3.zip


Steps
  • Insert your USB key and your Windows 98 floppy

  • Open the HP USB Disk Storage Format Tool
    • Select your USB key
    • Set the file system to FAT32
    • Check "Create a DOS startup disk"
    • Tell it to use the DOS system files located at A:
    • Click "Start" and let it go.


  • Open PEtoUSB.exe
    • Check "Enable File Copy" and select Overwrite Always from the drop-down
    • Click "Start" and wait for the file copy to finish


  • Select all the files for GRUB4DOS and copy them to the root of the USB key.
    • Allow it to overwrite config.sys
    • Open config.sys and edit the second line to read:

      CODE
      device=grub.exe --config-file="color black/cyan yellow/cyan;timeout 0;default 0;title find and load NTLDR of Windows NT/2K/XP;find --set-root /ntldr;chainloader /ntldr"


      This will allow it to go straight to the NTLDR process.


  • Boot your USB key.


Interesting side effect - When you boot off of the USB key, you will see the Windows 98 splash screen, followed by the Windows XP boot process and splash screen.

This is confirmed working on an 8gb SanDisk Cruzer Micro. After trying various different things, I stumbled upon success with these steps. Hopefully my steps will help others out there trying to accomplish the same thing.

-ComPro
masterchi
awesome job !

Quick question, though i think i already have the answer from reading the instructions.........Does this boot directly into UBCD4Win or does it display a boot menu first whre you can choose MemTest and such like with the CD?

Nice work, Awesome Job !!
ComPro
The way I configured it, it boots straight into UBCD4WIN/BartPE. You can conceivably create a boot menu with other options using GRUB4WIN, but I haven't tried it.
masterchi
Cool. And easier method i've been using to boot right into UBCD4Win to a USB drive is this below, try it if you like but just another option:

QUOTE
1. download PEtoUSB (http://gocoding.com/page.php?al=petousb)
2. Create your UBCD4win load, no ISO is needed just the initial BARTPE folder with all the files
3.Open PEtoUSB and ensure Destination Drive is set to your Flash Drive and as USB Removeable
4.Check the box "Enable Disk Format" and for "Source Path to Built BARTPE.." just point it to the location of the BARTPE folder that UBCD4win created on your build. ALSO ENSURE YOU CHECK BOX "ENABLE FILE COPY" and have it set to overwrite always.
5.Once you click start it will format the drive and then copy the files it needs to boot from.
6.Now if you try to boot now it will work but then stop at a 0x07b BSOD before it loads Windows so ensure you replace all instances of NTDETECT.COM, SETUPLDR.BIN, and RAMDISK.SY_ that are found on the thumbdrive with the same files from a Server 2003 CD to stop the BSOD.

As an added help, your file structure on your thumbdrive will look like it does below
BCDW(folder)
CMDC(Folder)
Images(Folder)
MININT(folder)
Programs(Folder)
autorun.inf(file)
bootsect.bin(File)
ntdetect.com(File)
ntldr(file)
win51ip(file)
win51ip.sp2(file)
winbom.ini(file)
ComPro
QUOTE (masterchi @ Dec 1 2007, 04:14 PM) *
Cool. And easier method i've been using to boot right into UBCD4Win to a USB drive is this below, try it if you like but just another option:

QUOTE
1. download PEtoUSB (http://gocoding.com/page.php?al=petousb)
2. Create your UBCD4win load, no ISO is needed just the initial BARTPE folder with all the files
3.Open PEtoUSB and ensure Destination Drive is set to your Flash Drive and as USB Removeable
4.Check the box "Enable Disk Format" and for "Source Path to Built BARTPE.." just point it to the location of the BARTPE folder that UBCD4win created on your build. ALSO ENSURE YOU CHECK BOX "ENABLE FILE COPY" and have it set to overwrite always.
5.Once you click start it will format the drive and then copy the files it needs to boot from.
6.Now if you try to boot now it will work but then stop at a 0x07b BSOD before it loads Windows so ensure you replace all instances of NTDETECT.COM, SETUPLDR.BIN, and RAMDISK.SY_ that are found on the thumbdrive with the same files from a Server 2003 CD to stop the BSOD.

As an added help, your file structure on your thumbdrive will look like it does below
BCDW(folder)
CMDC(Folder)
Images(Folder)
MININT(folder)
Programs(Folder)
autorun.inf(file)
bootsect.bin(File)
ntdetect.com(File)
ntldr(file)
win51ip(file)
win51ip.sp2(file)
winbom.ini(file)



This will format the drive to FAT. It works, but not on bigger drives that do not support FAT. My method will make FAT32 drives work.
SteelTrepid
Thanks for the instructions, I have pinned this topic in our new USB area. I haven't had the chance to attempt your method yet but hope to soon.
ComPro
Thanks for pinning the topic. I appreciate it.
ablok
I believe you have to start the "Create ISO" option in the autobuilder so that the final menu is laid out correctly in the files in the UBCD4WIN\BartPE folder before starting the procedure above. I did not do this first because I didn't know about the resulting duplicate start menu entries issue at the time. Also I can't seem to get the Recovery Console working when I create it as a new option in the grub4dos menu. The default setupldr in the \CMDC folder points to \minint and I don't know if the ISO creation portion fixes this. I did edit \CMDC\setupldr.bin and changed three instances of minint to CMDC and then added six 0s to the end of the file for padding but that didn't work.

If you don't have a floppy drive in your computer, you can extract the .ima file from boot98SE.exe with Winrar. It will error out during the extraction but the file will come out ok. Then you can use 7-zip to extract the contents of the .ima file. The HP USB formatting program can call these files from anywhere you select and it doesn't have to be a floppy drive. I used this method and there config.sys is not created on the USB stick, so there is no existing config.sys file to overwrite when you get to the grub4dos step, which is fine.
moorzilca
Hi all !
Ubcd4win works fine !
I create combocd ubcd4win+ubcd4dos and i want run it from usb stick.
Is it possible to add some magic strings to config.sys and boot ubcd4dos by grub ?

If i use syslinux + fat format way i customize my syslinux.cfg adding
LABEL main
KERNEL menu.c32
APPEND /menus/main.cfg
All programs works fine such as mhdd, memtest, netbootdisk with ghost and etc.
But Partition Magic 8 2.88 floppy image did not work because it recognize my usb stick as hdd and try to fix some errors on stick.
If i fix theese errors on usb stick by Partition Magic I still allow to use any floppy images from ubcd4dos, but ubcd4win and Win Recovery Console won`t boot.
Alternatively if i don`t fix errors computer hangs on Partition Magic screen.

And last question: is it possible to setup WIndows XP Professional from usb stick not using winnt.exe way ?

It was tested on 4 pc`s , on 1 pc I flash new bios, after this all works fine on it.
spurster
ComPro's instructions work very well with my 8GB Corsair Flash Voyager. Excellent!

Now my Christmas will be complete if I get my wireless running with BartPE/XPE.
Spider
I tried this. Looks like it's booting, but after that got an error - can't find arcsas.sys. But it is in the driver folder. Any ideas?

Thanks
hilander999
QUOTE (Spider @ Jan 4 2008, 06:22 PM) *
I tried this. Looks like it's booting, but after that got an error - can't find arcsas.sys. But it is in the driver folder. Any ideas?
The driver folder?

Is the file on your usb device in the \I386\SYSTEM32\DRIVERS folder?
Is the error name EXACTLY the same as the file name? (Case is important.... ARCSAS.SYS is not arcsas.sys)
Spider
QUOTE (hilander999 @ Jan 4 2008, 06:42 PM) *
QUOTE (Spider @ Jan 4 2008, 06:22 PM) *
I tried this. Looks like it's booting, but after that got an error - can't find arcsas.sys. But it is in the driver folder. Any ideas?
The driver folder?

Is the file on your usb device in the \I386\SYSTEM32\DRIVERS folder?
Is the error name EXACTLY the same as the file name? (Case is important.... ARCSAS.SYS is not arcsas.sys)


Yes you are right it is \I386\SYSTEM32\DRIVERS. The name is in lowercase arcsas.sys in folder and in error message. I tried to delete any reference to it from txtsetup.sif. Next reboot give me this: file lsi_sas.sys can't be found sad.gif
Spider
Finally got it to work. First I use WinXP to build BartPe - failed to start. Then I tried Win2k3 x86 - Works.
Thanks for instructions biggrin.gif
ronbo76
QUOTE (ComPro @ Nov 30 2007, 09:43 PM) *
BOOT BARTPE FROM A FAT32 FORMATTED DRIVE (Great for 8+ gigabyte drives)
---
Tools Required
  • HP USB Disk Storage Format Tool - http://downloads.pcworld.com/pub/new/utili...als/SP27608.exe
  • GoCoding.com's PEtoUSB.exe - http://gocoding.com/projects/petousb/V2TU0...USB_3.0.0.7.zip
  • Windows 98SE Bootable Floppy Disk - http://files.frashii.com/~bootdisk/newjersey/boot98se.exe
  • GRUB4DOS 0.4.3 - http://superb-east.dl.sourceforge.net/sour...b4dos-0.4.3.zip


Steps
  • Insert your USB key and your Windows 98 floppy

  • Open the HP USB Disk Storage Format Tool
    • Select your USB key
    • Set the file system to FAT32
    • Check "Create a DOS startup disk"
    • Tell it to use the DOS system files located at A:
    • Click "Start" and let it go.


  • Open PEtoUSB.exe
    • Check "Enable File Copy" and select Overwrite Always from the drop-down
    • Click "Start" and wait for the file copy to finish


  • Select all the files for GRUB4DOS and copy them to the root of the USB key.
    • Allow it to overwrite config.sys
    • Open config.sys and edit the second line to read:

      CODE
      device=grub.exe --config-file="color black/cyan yellow/cyan;timeout 0;default 0;title find and load NTLDR of Windows NT/2K/XP;find --set-root /ntldr;chainloader /ntldr"


      This will allow it to go straight to the NTLDR process.


  • Boot your USB key.


Interesting side effect - When you boot off of the USB key, you will see the Windows 98 splash screen, followed by the Windows XP boot process and splash screen.

This is confirmed working on an 8gb SanDisk Cruzer Micro. After trying various different things, I stumbled upon success with these steps. Hopefully my steps will help others out there trying to accomplish the same thing.

-ComPro


I tried this method with some mixed results. As best I can, I will report what I have experienced. I am using a A-Data PD2 8gb USB flash drive (http://www.adata.com.tw/adata_en/product_show.php?ProductNo=AP02ZZZSV). I formatted it as per these instructions with the modifications to the config.sys file for grub.exe.

Let me state that I have formatted several different USB flash drives (from 1 to 2 gb) with UBCD4Win and the A-Data PD2 2gb boots perfectly which is why I bought the 8gb flash drive.

On a normal boot or restart, I see the Windows 98 and XP screens followed by the UBCD4Win bootmenu and a BSOD which halts my laptop.

Interestingly enough, one thing I have found is that when laptop boots down unexpectedly from running down my battery to being locked up a program, the A-data PD2 8gb formatted as per these instructions will boot into UBCD4Win menu.

Last night, I wanted to try use A-data's PD2 format download to partition the flash drive. I had a 1gb Memorex USB flash drive that boots into a Windows 98 environment in my F: drive and the A-data PD2 8gb in the G: drive. When I tried to boot using the F12 boot from USB option, my laptop initially looked at the F: and then G:. The G: boot took over as it began to boot into UBCD4Win. Waiting for the BSOD, I noticed that LED on the PD2 would stop and Memorex drive would light then the system looked back and forth between both drives for a while before the UBCD4Win finally booted successfully.

I rebooted my laptop and again it looked at the F: drive and then the G: (and back and forth as per the previous paragraph). Again, I saw the Windows 98, XP and UDCD4Win screens boot successfully.

To sum this all up, if I use the PD2 8gb by itself, I get a BSOD. If I use after an abnormal shutdown, I get a successful UBCD4Win boot. If I have my Windows 98 boot USB flash drive in the F: drive and the PD2 8gb in the G: drive, I get a successful UBCD4Win boot.

Unfortunately I do not have access to Server 2003 files as per another post. I wish I did! I wonder why I get the successful boots and if there is a way to incorporate back whatever is being seen on the Windows 98 USB flash drive that causes successful boots.

Thanks for the great project!
hilander999
QUOTE
Unfortunately I do not have access to Server 2003 files as per another post. I wish I did! I wonder why I get the successful boots and if there is a way to incorporate back whatever is being seen on the Windows 98 USB flash drive that causes successful boots.


http://technet.microsoft.com/en-us/windows...r/bb430831.aspx
mlist
I have problem with image larger than 2 GB and multiboot
I'll try to explain:
Some days ago finally I created an iso with the following distroes:
xp
knoppix
netbootdisk

I burned the created image on my DVD and all worked perfectly so I decided to create a bootable usb key (and it worked perfectly too!) following these simple steps:
a) used petousb enabling the options "format" (FAT) and "overwrite files"
cool.gifexecuted syslinux f: (where f is my pen drive)
c) added the necessaries entries for knoppix in syslinux.cfg
It worked perfectly!
PLEASE NOTE THAT I EXECUTED SYSLINUX BECAUSE, IF I HAVE CORRECTLY UNDERSTOOD, IT IS NECESSARY TO ENABLE MULTIBOOT OPTIONS. And I think to have correctly understood because my usb key works perfectly but....

Yesterday I decided to add clonezilla to my dvd and to my usb key both; moreover I added others tools (like kaspersky, avg etc...) but I saw that my image is grown and now it is about 2.2 GB
So...I created my dvd again and it still worked correcly but my usb key doesn't boot correctly although I followed yours instructions in this post.

Problem:
Reading this post I tried to re-create my new bootable usb key based on my new cd but it doesn't work and I can't understand the reason.
I'll show you all steps I executed and I hope someone will help me:
a) I used hp usb format tool with a win98 boot disk as suggested. Moreover I formatted FAT32!
cool.gifI used petousb (Without format option because usb was already formatted by hp tool)
c) I copied all files from grub4dos-0.4.3 folder to f: (my usb key)
d) I added the following lines to f:\config.sys
device=grub.exe --config-file="color black/cyan yellow/cyan;timeout 0;default 0;title find and load NTLDR of Windows NT/2K/XP;find --set-root /ntldr;chainloader /ntldr"
e) Before to add others menu options I decided to test it so I rebooted the pc and my usb key worked correctly. Xp booted as usual!
f) I tried to add others entries (as I already did with my previous usb key...when image was < 2GB) executing:
syslinux f:
g) I copied all files from bootmenufiles.zip in f: (as I already did for my previous key paying attention to copies extracted files in the root:)
Copy c:\temp\bootfiles\CMDC\SETUPLDR.BIN F:\
Copy c:\temp\bootfiles\syslinux f:
Copy c:\temp\bootfiles\rcldr f:
h) I deleted the following files from f:
BCDW
isolinux
images
Etc
BOOTSECT.BIN
Win51IP.SP2
Win51IP
i) I added knoppix entries as I alredy did for my previous key.
l) I added netbootdisk entries

The problem is that now knoppix and netbootdisk work correctly instead xp doesn't run and say:
disk error
press any key to restart

I suspect that something goes wrong executing syslinux but I think that in order to have multiboot (as I did when image was < of 2gb) it is necessary.. What am I wrong? I thought that the xp stopped working when I executed syslinux but I'm not sure about this and I already tried 4 times to re-create the usb key Without success.
To sum up the problem is that using an image larger than 2GB all distroes work correctly execpt xp!
Please note that my usb key is a TDK 8GB


Thanks!
mlist
Ok

I just made some other tests and I have the confirmation that the problem is related to the usb pen drive that is 8GB.
Using a 2GB key all work correctly in fact on my kingston 2gb I have:
a)xp
b)knoppix
c)netbootdisk

Using an usb key bigger than 2gb it doesn't work! I think the problem could be related to syslinux that doesn't work on keys formatted in FAT32...but I'm not sure about it.
I hope someone will help me otherwise...I think that an usb key with 2 distroes is enough... blush.gif

bye
hilander999
I'm not the Linux guru around here, but I do have a couple comments you may find interesting.

Textmode setup (the first pe boot phase) does not recognise anything over 2gb when reading the boot data.
When we create a CD/DVD with mkisofs, we use a -sort list to ensure all boot files are added to the media below the 2gb barrior.

This makes sense why a 2bg usb drive works and why a larger one may have trouble.

I do not know for sure, but you should be able to copy the files to the usb drive in a fashion that respects the boot order, possably copying these files first may correct the issue or there may even be a way to run some sort of defrager to take care of it afterwards.

Try adding your linux images to the usb drive after running a defrag tool that moves all data to the front of the drive first. This may or may not help.
ronbo76
QUOTE (hilander999 @ Jan 20 2008, 02:51 PM) *
QUOTE
Unfortunately I do not have access to Server 2003 files as per another post. I wish I did! I wonder why I get the successful boots and if there is a way to incorporate back whatever is being seen on the Windows 98 USB flash drive that causes successful boots.


http://technet.microsoft.com/en-us/windows...r/bb430831.aspx


I downloaded that link which produced an iso. The iso when written to a CD looks to be a trial software installation. I looked at all its directories exploring cab files etc. and could not find the necessary 2003 files. I am fairly hesitant to install a trial program as MS never installs well.
iguru42
I tried following the instructions but I get stuck here:

QUOTE (ComPro @ Nov 30 2007, 11:43 PM) *
[*]Open PEtoUSB.exe
  • Check "Enable File Copy" and select Overwrite Always from the drop-down
  • Click "Start" and wait for the file copy to finish


PEtoUSB.exe doesn't see my 80 GB HDD. The HP tool blew away my 1 GB partition and formatted the whole drive to 80 GB fat32. I don't see any way to tell the HP tool to not use the whole HDD.

Isn't PEtoUSB limited to 2 GB partitions?

How do I get PEtoUSB.exe to see my HDD?
tjm
ComPro - Your suggestion works great. I have tested this on a 2 16usb drives and they work like a champ. I can store my ghost images on the fat32 as well as boot. I also used DD to copy the image over to my usb 2.5" Hard drive. Thanks again for such an easy solution. Tjm
thousandbuckle
tim,

Can you send me PM with the exact steps or repost the exact steps you took to get your 16gb drives working? Especiall when it comes to the part of adding the GRUB4DOS files. This is where I end up going astray and not understanding for some reason. I am having some issues with the instructions from ComPro and would really like to get this working on my 8gb flash drive.
thousandbuckle
QUOTE (thousandbuckle @ Mar 10 2008, 08:33 PM) *
tim,

Can you send me PM with the exact steps or repost the exact steps you took to get your 16gb drives working? Especiall when it comes to the part of adding the GRUB4DOS files. This is where I end up going astray and not understanding for some reason. I am having some issues with the instructions from ComPro and would really like to get this working on my 8gb flash drive.


Never mind I finally got it. Stupid mistake on my part. I did not realize that the second line of the config.sys file to edit was on string in the posting by ComPro.

Funny thing though this same image on a 1GB stick loads alot faster than on the 8GB stick.

Ohh well just glad it is working. Sorry for the newbie mistake.

Appreciate all the postings in here.
thejack
@masterchi


QUOTE
1. download PEtoUSB (http://gocoding.com/page.php?al=petousb)
2. Create your UBCD4win load, no ISO is needed just the initial BARTPE folder with all the files
3.Open PEtoUSB and ensure Destination Drive is set to your Flash Drive and as USB Removeable
4.Check the box "Enable Disk Format" and for "Source Path to Built BARTPE.." just point it to the location of the BARTPE folder that UBCD4win created on your build. ALSO ENSURE YOU CHECK BOX "ENABLE FILE COPY" and have it set to overwrite always.
5.Once you click start it will format the drive and then copy the files it needs to boot from.
6.Now if you try to boot now it will work but then stop at a 0x07b BSOD before it loads Windows so ensure you replace all instances of NTDETECT.COM, SETUPLDR.BIN, and RAMDISK.SY_ that are found on the thumbdrive with the same files from a Server 2003 CD to stop the BSOD.

As an added help, your file structure on your thumbdrive will look like it does below
BCDW(folder)
CMDC(Folder)
Images(Folder)
MININT(folder)
Programs(Folder)
autorun.inf(file)
bootsect.bin(File)
ntdetect.com(File)
ntldr(file)
win51ip(file)
win51ip.sp2(file)
winbom.ini(file)



.
This method does not work : on 3 different usb pen, on 3 different personal computer thumbdown.gif
on start the text is "remove support"

I do not know no.gif
rdsok
QUOTE (thejack @ Mar 22 2008, 03:42 PM) *
This method does not work : on 3 different usb pen, on 3 different personal computer thumbdown.gif
on start the text is "remove support"

I do not know no.gif


Actually the method does work... the problem you are running into is that not all systems use the same methods for booting USB devices because there is no set standard. So instead of passing judgement, try any of the other methods that are mentioned on this forum or the 911CD forum.... just be warned about what I said about there not being a standard, you may need to work with several methods until you find one that does work or even not find any that does it for the systems you try it on...
thejack
QUOTE (ComPro @ Dec 1 2007, 05:43 AM) *
[*]Windows 98SE Bootable Floppy Disk - http://files.frashii.com/~bootdisk/newjersey/boot98se.exe


no is a valid link

example .. this http://www.giulianoartico.it/soft/util/boot98se.exe is valid?

and...
i have on notebook no floppy drive

@ablok

QUOTE
If you don't have a floppy drive in your computer, you can extract the .ima file from boot98SE.exe with Winrar. It will error out during the extraction but the file will come out ok. Then you can use 7-zip to extract the contents of the .ima file. The HP USB formatting program can call these files from anywhere you select and it doesn't have to be a floppy drive. I used this method and there config.sys is not created on the USB stick, so there is no existing config.sys file to overwrite when you get to the grub4dos step, which is fine.
[/url]


my file boot98SE.exe do not open to Winrar : the messages is "this is not archive"

How can I do?

I am beginners :
There is a more detailed guide?

thanks
thejack
QUOTE (rdsok @ Mar 22 2008, 09:56 PM) *
QUOTE (thejack @ Mar 22 2008, 03:42 PM) *
This method does not work : on 3 different usb pen, on 3 different personal computer thumbdown.gif
on start the text is "remove support"

I do not know no.gif


Actually the method does work... the problem you are running into is that not all systems use the same methods for booting USB devices because there is no set standard. So instead of passing judgement, try any of the other methods that are mentioned on this forum or the 911CD forum.... just be warned about what I said about there not being a standard, you may need to work with several methods until you find one that does work or even not find any that does it for the systems you try it on...


I also tried the method ok dummptyhummpty and it works : I ubcd4win with the problem that startup the "pre logon" program i stopped
i have on post : http://www.ubcd4win.com/forum/index.php?showtopic=9630&st=60
Hemo2
I thought I'd post a note of thanks for this thread. I appreciate very much others taking the time to work through these things and post things like this. I made a USB boot project using the instructions posted originally by dummptyhummpty and it worked great, but I ran into an issue of my custom boot floppy disks not working. I was attracted to this post due to it using FAT32 so I can use larger than 2GB devices, so I've been working on a USB boot device the past 4 days and have had success getting a multiboot menu to work for us. I'll post my results below, but wanted to say thanks again.

  • Used the HP formatting tool to format to FAT32. I have a DOS boot disk created under Windows 98 so I used that as my source. In fact, I just copied off the IO.SYS, MSDOS.SYS, COMMAND.COM files to a folder and used those to make the bootable disk. (I also copied HIMEM.SYS so I could use it in my CONFIG.SYS file.)
  • Built my Multiboot UBCD4Win project like normal. I had it create an .ISO too.
  • Downloaded and ran the PEtoUSB tool to copy my project to the USB thumbdrive.
  • Downloaded the grub4dos-0.4.3.zip file and extracted to a temp folder. I copied the GRUB.EXE, MENU.LST, and CONFIG.SYS files to my thumbdrive.
  • The config.sys from Grub4DOS has an entry already to start the grub.exe with command line parameters specified. I REM'd this line out and simply put DEVICE=GRUB.EXE and it boots up to use their default MENU.LST menu.
  • Since it worked, I began editing their menu.lst file to customize it for items we wanted. That's basically it. The hard part was figuring out the syntax and commands to use in the menu though.


Since the thumbdrive was created using a Win98 DOS bootdisk as the source, when you boot you see the Windows 98 splash screen initially. To get rid of this, you can edit the MSDOS.SYS file in a text editor. I added the below lines to remove the splash screen, stop creating a bootlog.txt file and to also hopefully ignore any improper shutdown notices upon bootup.

CODE
[Options]
BootGUI=0
BootMenu=0
BootWarn=0
DisableLog=1
Logo=0


I then ran into a problem where Grub4DOS seems to have some limitation on the number of menu entries you can put into the menu.lst file. I couldn't find any information on limitations with the Grub4DOS menus though. So all I can figure is there is a maximum limit on menu entries or maximum file size (or something) going on because the max menu entries I could get was about 22. I shuffled things around a bit and did get 23 one time, but I can't figure out what the limitation or issue is. So I quite fighting that and to get the items I wanted to include I had to dust off my old DOS experience and put a multiboot menu inside of CONFIG.SYS. Here is what I have done inside of CONFIG.SYS to break things out. Notice I reference a menu file for grub.exe to use in each section. This is how I got Grub to use different menus depending on the selection you make.

CODE
[MENU]
MENUITEM UBCD4WIN, Ultimate BootCD for Windows v3.12
MENUITEM STATESD, State of SD Boot Disks
MENUITEM HDDIAGS, Hard Disk Diags & Tools Boot Disks
MENUITEM OTHER, Other tech Boot Disks
MENUITEM GPARTED, GParted Partitioner
MENUDEFAULT UBCD4WIN, 30
MENUCOLOR 15,1

[UBCD4WIN]
DEVICE=HIMEM.SYS
DOS=HIGH
FILES=60
BUFFERS=30
device=grub.exe --config-file="color black/cyan yellow/cyan;timeout 0;default 0;title Ultimate BootCD for Windows v3.12;find --set-root /ntldr;chainloader /ntldr"

[STATESD]
DEVICE=HIMEM.SYS
DOS=HIGH
FILES=60
BUFFERS=30
device=grub.exe --config-file=/statesd.lst

[HDDIAGS]
DEVICE=HIMEM.SYS
DOS=HIGH
FILES=60
BUFFERS=30
device=grub.exe --config-file=/hddiags.lst

[OTHER]
DEVICE=HIMEM.SYS
DOS=HIGH
FILES=60
BUFFERS=30
device=grub.exe --config-file=/other.lst

[GPARTED]
DEVICE=HIMEM.SYS
DOS=HIGH
FILES=60
BUFFERS=30
device=grub.exe --config-file=/gparted.lst


I could have put the common commands inside a [COMMON] section of our CONFIG.SYS, but I couldn't remember when the common section gets executed upon DOS bootup and I wanted to ensure those commands got executed before the GRUB.EXE getting executed. This part wasn't rocket science, so I figure a messy config.sys that I know works is an acceptable solution.

For others to reference, I've listed below the contents of the menus I use and how I boot up the various items. My knowledge of this stuff is pretty shaky and I did a "lot" of internet searching for examples and information. Despite a lot of frustration and headaches, I managed to get things to work well enough for us and maybe others will find this useful.

The nice thing about this is that I used our corporate version of Ghost and made a ghost image of my thumbdrive. I then ghosted that image to my external 80GB USB hard drive and it now boots up fine just like the thumbdrive. Thus, I can hopefully include our various clone images we use to deploy to workstations all on the same boot device.

CODE
# This is the statesd.lst file. You can make changes to add or remove boot options.
# Items with a "#" are comments and are not executed.

color black/cyan yellow/cyan
timeout 30
default /default

title State of SD: PointSec Force Removal Utility
find --set-root /images/ps_recvr.img
map --mem /images/ps_recvr.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title State of SD: Intel CPU Identifier v3.7.6
find --set-root /images/cpu_id.img
map --mem /images/cpu_id.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title State of SD: Intel CPU Identifier (For Old CPU's)
find --set-root /images/frq_id.img
map --mem /images/frq_id.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title State of SD: DOS Universal Network Bootdisk v10b
find --set-root /images/uni10_cd.img
map --mem /images/uni10_cd.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title State of SD: DOS w/Ghost v11.0.1 (with limited USB support)
find --set-root /images/w98gst11.img
map --mem /images/w98gst11.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title State of SD: DOS Bootdisk with DOS Utilities
find --set-root /images/w98nonet.img
map --mem /images/w98nonet.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title State of SD: WipeDrive v3.0.0 (Drive eraser)
find --set-root /images/wipedrv.img
map --mem /images/wipedrv.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title State of SD: PCI Info v1.1 (Hardware info)
find --set-root /images/pciinfo.img
map --mem /images/pciinfo.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title State of SD: SpinRite v6.0 (Disk Recovery and Analysis)
find --set-root /images/spinrite.img
map --mem /images/spinrite.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title State of SD: Windows NT Repair
find --set-root /images/ntrepair.img
map --mem /images/ntrepair.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title GRUB4DOS Commandline
commandline

title Exit to DOS
quit

title Reboot computer
reboot

title Halt computer
halt


CODE
# This is the hddiags.lst file. You can make changes to add or remove boot options.
# Items with a "#" are comments and are not executed.

color black/cyan yellow/cyan
timeout 30
default /default

title HD Diags & Tools: Fujitsu Diagnostic Tool v7.00
find --set-root /images/fjdt.img
map --mem /images/fjdt.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title HD Diags & Tools: Gateway GWScan Diagnostic Tool v5.12
find --set-root /images/gwscan.img
map --mem /images/gwscan.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title HD Diags & Tools: Hitachi/IBM Drive Fitness Test v4.11
find --set-root /images/dft.img
map --mem /images/dft.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title HD Diags & Tools: Maxtor PowerMax v4.23
find --set-root /images/pwrmax.img
map --mem /images/pwrmax.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title HD Diags & Tools: Samsung SHDIAG v1.25
find --set-root /images/shdiag.img
map --mem /images/shdiag.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title HD Diags & Tools: Seagate SeaTools Desktop v3.02.04
find --set-root /images/stools.img
map --mem /images/stools.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title HD Diags & Tools: Seagate(Maxtor) SeaTools for DOS v2.07 (Replaces SeaTools Desktop & PowerMax)
find --set-root /images/seatools.img
map --mem /images/seatools.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title HD Diags & Tools: Western Digital Data Lifeguard Diagnostics v5.04f
find --set-root /images/wddlg.img
map --mem /images/wddlg.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title HD Diags & Tools: Magic BootDisk w/MHDD 4.6
find --set-root /images/mbd20.img
map --mem /images/mdb20.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title HD Diags & Tools: DOS Boot Disk w/ATTO Tech SCSI UL4S/UL4D
find --set-root /images/w98atto.img
map --mem /images/w98atto.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title GRUB4DOS Commandline
commandline

title Exit to DOS
quit

title Reboot computer
reboot

title Halt computer
halt


CODE
# This is the other.lst file. You can make changes to add or remove boot options.
# Items with a "#" are comments and are not executed.

color black/cyan yellow/cyan
timeout 30
default /default

title Memtest86+ v2.01 (Memory Diagnostic)
kernel /images/memtestp.bin

title Smart Boot Manager (Boot a CD/DVD when BIOS doesn't support CD boot)
kernel /syslinux/memdisk
initrd /images/sbootmgr.dsk

title Norton GoBack Removal Tool
find --set-root /images/goback.ima
map --mem /images/goback.ima (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title GRUB4DOS Commandline
commandline

title Exit to DOS
quit

title Reboot computer
reboot

title Halt computer
halt


CODE
# This is the gparted.lst file. You can make changes to add or remove boot options.
# Items with a "#" are comments and are not executed.

color black/cyan yellow/cyan
timeout 30
default /default

title GParted LiveCD 0.3.4-11 (Auto Configuration)
kernel /isolinux/gparted root=/dev/ram0 init=/linuxrc real_root=/dev/loop0 looptype=squashfs loop=/gparted.dat udev dokeymap scandelay=6 dodmraid nosound cdroot=/dev/sd
initrd /isolinux/gparted.igz

title GParted LiveCD 0.3.4-11 (Force VESA video configuration)
kernel /isolinux/gparted root=/dev/ram0 init=/linuxrc video=vesa real_root=/dev/loop0 looptype=squashfs loop=/gparted.dat udev dokeymap scandelay=6 dodmraid nosound cdroot=/dev/sd
initrd /isolinux/gparted.igz

title GParted LiveCD 0.3.4-11 (Force i740 video configuration)
kernel /isolinux/gparted root=/dev/ram0 init=/linuxrc video=i740 real_root=/dev/loop0 looptype=squashfs loop=/gparted.dat udev dokeymap scandelay=6 dodmraid nosound cdroot=/dev/sd
initrd /isolinux/gparted.igz

title GParted LiveCD 0.3.4-11 (Force i810 video configuration)
kernel /isolinux/gparted root=/dev/ram0 init=/linuxrc video=i810 real_root=/dev/loop0 looptype=squashfs loop=/gparted.dat udev dokeymap scandelay=6 dodmraid nosound cdroot=/dev/sd
initrd /isolinux/gparted.igz

title GParted LiveCD 0.3.4-11 (Auto Configuration and Frame Buffer)
kernel /isolinux/gparted root=/dev/ram0 init=/linuxrc real_root=/dev/loop0 vga=788 looptype=squashfs loop=/gparted.dat udev dokeymap scandelay=6 dodmraid nosound cdroot=/dev/sd
initrd /isolinux/gparted.igz

title GRUB4DOS Commandline
commandline

title Exit to DOS
quit

title Reboot computer
reboot

title Halt computer
halt


Regarding the GParted. I know nothing about linux booting, etc. and it initially complained about an invalid loop for gparted.dat. On my initial command line try, it had "cdroot". After I did a lot of searching and found an example somewhere, I tried using "cdroot=/dev/sd" and then it booted up. I apologize for my lack of knowledge on this and have no idea if what I did is appropriate, or for that matter, even accurate. But regardless, it started booting up after that. The GParted is part of my multiboot of the UBCD4Win project that I believe "pcuser" had created the plugin for. (Many thanks for that pcuser!)
teobromina
QUOTE (Hemo2 @ Apr 9 2008, 09:34 AM) *
The nice thing about this is that I used our corporate version of Ghost and made a ghost image of my thumbdrive. I then ghosted that image to my external 80GB USB hard drive and it now boots up fine just like the thumbdrive. Thus, I can hopefully include our various clone images we use to deploy to workstations all on the same boot device.

Inspired in your post, I have made a backup of a flash memory Kingston 4 Gb multiboot pendrive including UBCD4Win, Freedos, Parted Magic Live Linux, Mint Live Linux and Slax Live Linux with DriveImageXML ( http://www.runtime.org/driveimage_faq.htm ). Then I have restored the backup in a mini hard disk Iomega 8 Gb with identical results: It boots fine with all options. The backup took 12 minutes (about 2 Gb) and the restoration about 6 minutes. clapping.gif

*JT.
huangj
QUOTE (ComPro @ Dec 1 2007, 12:43 AM) *
BOOT BARTPE FROM A FAT32 FORMATTED DRIVE (Great for 8+ gigabyte drives)
---
Tools Required
  • HP USB Disk Storage Format Tool - http://downloads.pcworld.com/pub/new/utili...als/SP27608.exe
  • GoCoding.com's PEtoUSB.exe - http://gocoding.com/projects/petousb/V2TU0...USB_3.0.0.7.zip
  • Windows 98SE Bootable Floppy Disk - http://files.frashii.com/~bootdisk/newjersey/boot98se.exe
  • GRUB4DOS 0.4.3 - http://superb-east.dl.sourceforge.net/sour...b4dos-0.4.3.zip


Steps
...
-ComPro


Hi ComPro, am new here and am trying to get a USB thumb drive set up with UBCD4Win using your tips. I have gotten 2 generic 2GB sticks to work, but a third (Lexar 2GB) came out screwy. The "Start" menu gives me several repetitions of each mennu item. I have used the same configuration for all 3 sticks.
One point tho, I used the PEtoUSB app to format and load the sticks and nothing else.
Would you have any ideas as to why this has happened? I know that it is difficult to "see" the situation from just a briuef text description. I have made a screen cap while in PE but they are in pdf format and I do not know how to upload that.
Your advice would be appreciated.

James
wimb
You can use USB_MultiBoot_8.cmd for Install of BartPE or UBCD4Win on
Bootable USB-stick of any size and format using Windows XP or Vista OS.

Download USB_MultiBoot_8.zip - At CD Forum

More Info See:
Guide for MultiBoot USB-stick with boot.ini Menu

How to install XP from USB

ScreenShots

You can Select BartPE or UBCD4Win Source in the Main Menu, ScreenShot 5
You can use No Copy of XP Source at Copy Select ScreenShot 12

wimb
charlestek
I'm trying ComPro's method for Ubcd4Win 3.13. After the windows xp splash screen I get a blank blue desktop and cursor and an error: "PreLogon: File Not found" and the boot stops and crashes.
gva482
ComPro,

Thank you, I am finally able to boot my PC with my 16GB Corsair Flash Voyager. I only have one problem. Nearly all the menu items in the Start/Program menu show up multiple times. Some display correctly, but some are displayed as many as 18 times (Submenuse as well). They all work, but it takes forever to scroll through the entire list from top to bottom and I'd like to correct the problem if possible.

Could you think of anything I may have done to create such an issue, or would you have any suggestions for a fix.

Thanks again for your awesome contribution.
rdsok
QUOTE (gva482 @ Jun 3 2008, 11:49 AM) *
ComPro,

Thank you, I am finally able to boot my PC with my 16GB Corsair Flash Voyager. I only have one problem. Nearly all the menu items in the Start/Program menu show up multiple times. Some display correctly, but some are displayed as many as 18 times (Submenuse as well). They all work, but it takes forever to scroll through the entire list from top to bottom and I'd like to correct the problem if possible.

Could you think of anything I may have done to create such an issue, or would you have any suggestions for a fix.

Thanks again for your awesome contribution.


You must let the build create the ISO... this is the process that also sorts the menu and removes duplicate entries. If you did let it create the ISO, then that indicates that one of the XML menu items for a plugin that was added has an error that doesn't fit with the existing menu structure, you'd have to correct the XML or remove/disable the plugin that is causing it.
datarunner
QUOTE (gva482 @ Jun 3 2008, 05:49 PM) *
ComPro,

Thank you, I am finally able to boot my PC with my 16GB Corsair Flash Voyager. I only have one problem. Nearly all the menu items in the Start/Program menu show up multiple times. Some display correctly, but some are displayed as many as 18 times (Submenuse as well). They all work, but it takes forever to scroll through the entire list from top to bottom and I'd like to correct the problem if possible.

Could you think of anything I may have done to create such an issue, or would you have any suggestions for a fix.

Thanks again for your awesome contribution.


hi there

did u get a fix 4 this as i get the same?
Ramrunner
Hey there all, I'm visiting this again because of a new Corsair Survivor I've bought (I've previously never gotten this to work with RunDisks and A-Data drives). I also play with the WinBuilder PE project (based on Vista), which I'd never gotten to work either.

To my surprise after the WinBuilder - I ended up with a bootable Vista PE and a heap of tools on my new Corsair drive!

BUT - because of the bootloader used I don't think I can multi-boot with it (I need memtest), and their tools don't have Western Digital diagnostics on them either (which I use a lot).

So, I thought, with a known working drive I'd try here again.

Lo and behold!!!

I got all the way to the desktop before the dreaded "Prelogon - File not found" error.

At least it's booting right?

Unfortunately I do not have access to an XP machine, but reading all the posts I then built the PE under the Sun VM under XP Pro SP2.

This also starts booting, but when the Windows XP logo is supposed to come up, both machines I've tried it on reset.

I've also tried both building environments with a Server 2003 CD as source - no difference.

Is there any chance we can all get together and fix the Vista building problem?

Reason I ask is XP is now not supplied/sold any more officially really (yes I know if you look you can still find), so Vista is going to be our build environment in the very near future (any new PC bought after July now pretty much guaranteed has Vista on it).

Basically we HAVE to tackle why it's not working at some stage. We cannot simply say "build it on XP" any more.

Any guru's out there who helped make this possible and can explain how the boot process actually works? I'm happy to diagnose....

Regards,
Ed.
Astol
i followed ComPro's steps, but i keep getting a BSOD
CODE
STOP: 0x7B


how do i fix this?

i have an LG USB Drive, 1Gb
pcuser
QUOTE
STOP: 0x7B
how do i fix this?


Try THIS method. It will not only put UBCD4Win on your usb drive but will also make a small iso image that can be burned to cd and booted as a "kicker" to initiate usb booting on computers that can't boot from usb or have problems booting from usb.
Astol
thanks! i'll give it a go and let you know how it goes
Sparky2675
QUOTE (ComPro @ Nov 30 2007, 10:43 PM) *
BOOT BARTPE FROM A FAT32 FORMATTED DRIVE (Great for 8+ gigabyte drives)
---
Tools Required
  • HP USB Disk Storage Format Tool - http://downloads.pcworld.com/pub/new/utili...als/SP27608.exe
  • GoCoding.com's PEtoUSB.exe - http://gocoding.com/projects/petousb/V2TU0...USB_3.0.0.7.zip
  • Windows 98SE Bootable Floppy Disk - http://files.frashii.com/~bootdisk/newjersey/boot98se.exe
  • GRUB4DOS 0.4.3 - http://superb-east.dl.sourceforge.net/sour...b4dos-0.4.3.zip


Steps
  • Insert your USB key and your Windows 98 floppy

  • Open the HP USB Disk Storage Format Tool
    • Select your USB key
    • Set the file system to FAT32
    • Check "Create a DOS startup disk"
    • Tell it to use the DOS system files located at A:
    • Click "Start" and let it go.


  • Open PEtoUSB.exe
    • Check "Enable File Copy" and select Overwrite Always from the drop-down
    • Click "Start" and wait for the file copy to finish


  • Select all the files for GRUB4DOS and copy them to the root of the USB key.
    • Allow it to overwrite config.sys
    • Open config.sys and edit the second line to read:

      CODE
      device=grub.exe --config-file="color black/cyan yellow/cyan;timeout 0;default 0;title find and load NTLDR of Windows NT/2K/XP;find --set-root /ntldr;chainloader /ntldr"


      This will allow it to go straight to the NTLDR process.


  • Boot your USB key.


Interesting side effect - When you boot off of the USB key, you will see the Windows 98 splash screen, followed by the Windows XP boot process and splash screen.

This is confirmed working on an 8gb SanDisk Cruzer Micro. After trying various different things, I stumbled upon success with these steps. Hopefully my steps will help others out there trying to accomplish the same thing.

-ComPro

Sparky2675
OK, I am no where near an expert at this and I am strugling with it.

Followed the instructions to a T (or maybe it's an I, whatever) I got everything to load or build. My CD's work great, so I thought I would try the thumbdrive, and not so great.

I get it to begin to boot and it freezes at the 98 boot screen.

I modified the config.sys like it said but nothing is working.

Can someone please help!
pcuser
Try what I suggested in post #39
Sparky2675
QUOTE (pcuser @ Sep 17 2008, 11:08 AM) *
Try what I suggested in post #39



What did you post in 39 that will help me, sorry but I am not good with code, you will have to hold my hand on this one.

I looked at my MSDOS.SYS and it has on line in it, ( ;W98EBD ) Is that correct?

I friggin lost!
pcuser
http://www.ubcd4win.com/forum/index.php?showto...ost&p=63507

QUOTE
Try THIS method
Sparky2675
OK, I could do it that way, but what about what I have already built.

What is supposed to be in that MSDOS.SYS file?

Is that the problem?

Thanks in advance and for all you have done to help.

I am still going to try the THIS Method.
datarunner
hi all

tried this method and all seems ok. however i cannot get this method to work with AMI bios's. tried using both xp sp2 and w2k3 sp1 sources but still no joy on ami bios.

anyone else get this?

regards
ell
Well, I've tried this several times, each time I end up with just a blinking cursor on boot on a pent 4 desktop with xp . I made my pe files with xpsp2 and used my micro cruzer 2 gb flash drive. Formatted fat32. Heres a jpeg of my usb drive, anybody help me figure this out? I'm determined to get this to work!
grandgroove
Wow, this is my first post! It's good to start off with a happily working USB flash drive.

I followed the instructions and set up my UBCD4Win customized build to an Ativa 4GB so-small-you'll-likely-lose-it-often drive ($20 @ Office Depot - Click here for product description).

The first boot proved successful! I have the usual task of adding custom drivers for some of the items on here.

BTW, I'm using a Sony Vaio UX380N as my test PC. This thing is simply amazing, and I have some things to try and add that may be new to the forum. I'll definitely post on it.

Thanks again! I truly think this is one of the best projects I've worked on in a long time. I help friends and family with PC issues, and I pretty much carry around this flash drive and a couple others to do everything.

Until next time ... sayoonara!

spewk
Wow I am just about to smash my head into a brick wall over this crap....

I have a 2 GB jump drive, but the build is too big to fit on it .
I'd really like to understand what I'm screwing up on here.

I HAVE to get this stupid EeePc fixed.

Can anyone offer any tips on how to get all this crap onto a jump drive ?

I assume the iso has to be extracted to the jump drive for anything to work.

I'm really at the end of my freakin' rope here, so if anyone can help that would be great.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.