Pe2usb: Installing Bartpe To Usb Flash Disk Options

[Bart Lagerweij]

Hi all,

I've been playing around with the new setup loader that comes with server 2003 sp1 (release candidate) and this opens the door to load BartPE on USB sticks through a ramdisk loader (not to be confused as the ramdrive "b:" you have in BartPE). So I've created a simple script that helps you to install it.

Please check instructions below (piece from pe2usb.txt)

CODE

...
Installation of PE2USB:
You should copy the files pe2usb.cmd and pe2usb.bin to your <pebuilder>
directory.

For successful installing BartPE to a USB flash disk you need:

1) A USB flash disk with a capacity of 256MB or more
2) Server 2003 SP1 (or a release candidate). You can download this from
  http://www.microsoft.com/downloads/details.aspx?familyid=02734CEA-7A4B-4D95-B220-8E1708C3ED46
  This file is large, about 350MB!!!
 Unpack the files from the service pack (this is not installing) with:
 sr1sp.exe -x, lets assume you extract it to c:\server2003sp1
 Create the folder <pebuilder>\srsp1
 Copy the file c:\server2003sp1\i386\setupldr.bin to the <pebuilder>\srsp1 folder
 Expand the file c:\server2003sp1\i386\ramdisk.sy_ to the <pebuilder>\srsp1 folder
 expand -r c:\server2003sp1\i386\ramdisk.sy_ <pebuilder>\srsp1
 You can now remove the c:\server2003sp1 folder, not needed anymore...
3) Build BartPE using pebuilder as normal, you must set the output folder to
  "BartPE", you do not need to generate an ISO image for now.
4) Run "pe2usb -f <drive:>" to format and install the files to your UFD.
  Formatting is only needed the first time, so next time you can run
  "pe2usb <drive:>" (without -f) to update the BartPE files.

For successful booting BartPE from a USB flash disk you need:
1) A PC that is capable of booting from a USB flash disk with 256MB memory
  or more.
...

Download: http://www.nu2.nu/pebuilder/files/pe2usb101.zip

Regards,
Bart.

[fafot]

@Bart, that looks great!
Thank you

[this-is-me]

Why must the server 2003 ramdisk driver be enabled?

[norseman]

Why can't those two files included with the zip file?
350MB can be a bit much for some users to download for just 2 files..

[Bart Lagerweij]

@this-is-me

The 2003 setupldr with ramdisk option prevent windows from crashing or a 0x7b stop error (inaccessible boot device).

This happens when windows is loading the USB devices drivers and the USB driver "resets" the USB bus. When we are riding from the ramdisk loader, we are not dependant any USB vendor windows driver from resettings the USB bus. We can now boot successful from "most" usb capable of booting hardware.

Regards,
Bart.

[Bart Lagerweij]

@norseman

This is the only "legal" way todo it.
Who knows, people from ms are members of this forum and we don't know...
I don't want to get in trouble with microsoft.

The 100% legal way is the only way for me...

Regards,
Bart.

[Bigtime5000]

Hi Bart,

I have tried the new way and successfully created the files using your new script.
But still all I seem to get is a message saying insert bootable media. The pc is a new has a new motherboard and has usb boot enabled, it detects the usb dongle then does nothing.

Any idea`s

[foxiness]

The file management utility has a really slow load time with this method. Is there a way to fix this?

[Sillosyben]

I was not able to get this to work with my hardware. Has anyone had luck with bootable USB drives and ASUS mother boards? I tried a combination of settings in the BIOS but nothing would boot. I did verify the .iso on the USB stick worked using VPC.

Hardware:
ASUS P4P800-VM (mini ATX) motherboard, 1 Gig RAM
Sandisk Cruiser Mini 256 MB

Thanks in advance...

[Bart Lagerweij]

@Sillosyben

Asus is bad in booting USB when all BIOS settings are left "default"...

Try changing the USB emulation.
Go in the BIOS setup and change:
Advanced-> USB Mass Storage Device Configuration -> Emulation Type=Harddisk
Boot-> Hard Disk Drives-> 1st Drive= [USB Flash Device]
Boot-> Boot Device Priority-> 1st Boot Device=[USB Flash Device]
(stupid AMI bios!)

@foxiness

Assuming you mean the A43 file manager, I did not try that, maybe you can try Total Commander I use that all the time and works great!

@Bigtime5000

Check the BIOS settings, the BIOS should "tread" the UFD as if it is a harddisk.
Also recheck the boot-order.

Some BIOSes like hp/compaq have a F8 or F9 key that can be presses to select the boot device...

Regards,
Bart.

[this-is-me]

Can this be configured to work if the iso is on another drive? I am looking to have all the windows files on the USB Stick or the iso with the windows files on there, while originally booting from cd.

[bigdaddy]

Using a Kingston 1GB, I still get: Missing operating system.

I followed the instructions to the letter. I tried it on a IBM T41p laptop and a new Gateway desktop.

I have the following files on the USB disk:

BartPe.iso
ntdetect.com
ntldr
winnt.sif

The contents of the winnt.sif file are:

[SetupData]
BootDevice = "ramdisk(0)"
BootPath = "\I386\SYSTEM32\"
OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=bartpe.iso"


Any ideas?

[kyspace]

Can I execute these steps in win2000?
Or only for winxp?

Thanks for your doing!

[Bart Lagerweij]

@bigdaddy

Missing operating system

This message comes from the MBR.
(see http://www.ata-atapi.com/hiwmbr.htm)

This message means that the LBR (bootsector of your USB volume) does not have a valid (55aah) signature, or that the partition table or MBR is wrong/corrupt.
If you run "mkbt -i -x <usb-drive:>" does it give "ok" for the signature?
Does is also give "bartpe" as the OEM ID?

@this-is-me

Think not...

@kyspace

You should be able to run pe2usb on w2k also, but I did not test it...

Regards,
Bart.

[bigdaddy]

Bart,

This is what I got when I tried your command:

D:\Download\MKBT20\mkbt20>mkbt -i -x n:
* Expert mode (-x)
Opening "p♥2" (for read) failed (tried 5 times).
Error code 0x7b: The filename, directory name, or volume label syntax is incorrect.

I guess that explains why it doesn't work.

I'll try the entire sequence again tomorrow. I must be doing something wrong.

Thanks,

Charlie

[Sillosyben]

I tested this on as much hardware as I could get my hands on today and I was unsuccessful in getting my USB stick to boot. I played around with the various BIOS settings on the Compaq and Dell hardware. Unless I systematically managed to use all incompatible hardware, I'm under the impression the Sandisk Cruiser Mini product is the issue. In all cases except the Compaq DL360 G3, I recieved no errors. It would simply hang at a black screen.

* Dell Precision 450 & 470
* Dell Latitude D600 Laptop
* Compaq DL360 G3 (602 - Diskette Boot Record Error)
* Compaq DL360 G4 (attempting to boot from USB DriveKey (C:)) Hangs
* Compaq 6400R w/PCI USB Card (I wasn't expecting this to work)

I tried with with two different USB sticks and built with XP/SP2 and 2K3. I tried the "mkbt -i -x" command from the above post and it shows a successful signature. Any ideas? I'm not sure if it matters but creating the .iso to the USB stick took upwards of 45 minutes. Can someone recommend a known good brand USB product?

[jaclaz]

@Sillosyben

My two cents:
1) in my (little) experience, the problem can be on BOTH sides, i.e. motherboard and stick, but most of the time is on the motherbosrd side or in an improperly formatted stick.
Here is a list I found about keys that work on the XBOX (if they work there they will work on PC's, whilst those reported as "not working" might work as well):

1 Devices that do work

3System USB Flash Disk USB Drive 32 MB (1998 blocks)
Aigo 128MB USB Memory Stick (7997 blocks)
Apacer 256Mb USB Key (Paradigit)
AVB 64 MB USB 1.1 Mobile Drive (4030 blocks, ID 0ea0:6803)
Belkin 32MB USB Memory Stick
Captiva USB BAR 128 MB (7989 blocks)
Commodore Floppy -on- stick 128MB (7989 blocks)
COMSOL 16MB
COMSOL 128MB
Creative Labs Nomad Muvo MP3 Player 128MB (7997 blocks)
Dolphin  PowerCAM 2.0 Megapixel Digital Camera FASTUSB-1015
Digital Research MP3 player 32MB (~5092 blocks)
Digitrex DSC-1300 camera, in Mass Storage mode (8MB)
EasyDisk 32MB (2014 Blocks)
EasyDisk 128MB (7997 Blocks)
Freecom USB Stick 32 MB (1998 blocks)
Fujitsu Siemens 64MB Menustick
Fujitsu Siemens SB-512 MemoryBird USB-2.0 (512MB, how do I get MechInstaller onto it? - sajb)
Gateway 16MB USB Flash Drive (998 blocks), Windows sees it as "USB NAND FLASH DISK",  VID:0c45 PID:1060
Gateway 32MB USB Flash Drive (1998 blocks), Windows sees it as "MFG FLASH DRIVER", Vendor=0c45 ProdID=1060
Hama 6-in-1 USB Card Reader (Model-Nr.: 46958) with Lexar Media 16MB CompactFlash (992 blocks)
HP Photosmart 315 with 8 MB SanDisk CF Card
HP Photosmart C618 Digital Camera
IBM 32 MB USB Memory Key (1998 blocks)
KBGear JamP3 Player (9998 blocks)
KingMax USB2.0 Flash Drive 512MB - KS/PD2-512M (31994 blocks)
Kingston DataTraveler  32 MB (1998 blocks) & 256 MB (15740 blocks)
Lexar JumpDrive Secure 128 MB (7869 blocks)
Lexar JumpDrive Secure 256 MB (15740 blocks)
Lexar JumpDrive Sport 64 MB
Linksys Instant USB Disk 64 MB (Model USBM64M) (3998 blocks)
Logic3 16MB USB (991 blocks)
Medion USB 128 MB (7997 blocks)
Memorex 64 MB (4030 blocks) & 128 MB
Memorex ThumbDrive 256MB (16116 blocks)
Memory in Black USB memory pens from 32 to 512 MB, both the PQI-based and Opti-based models
Micro Advantage 64MB (4008 blocks)
Minolta DiMAGE F300 with 64MB SD-Card
M-Systems DiskOnKey 8MB (486 blocks)
Nikon Coolpix (test with 1x 16 MB and 2x 128 MB CF/SD cards)
Nikon Coolpix 995 w/128MB SanDisk CompactFlash
Ocean 8 MB (490 blocks)
Olympus D-510 Zoom Digital Camera with 64 MB SmartMedia (3990 blocks)
Olympus D-550 Digital Camera with 128 MB SmartMedia (7997 blocks)
Olympus D-380 Digital Camera with 64 MB SmartMedia (MechInstaller - Open 8-32MB image and write to 64MB)
Oti 32 MB
Paradigit 128 MB USB2.0 memory stick  (aka Apacer memory stick) (7837 blocks)
PNY 64 MB (3998 blocks)
PQI "Travelling Disk" translucent USB sticks, 64 and 128MB at least
  (all 0ea0:6803; some models (09a6:8001) say "damaged", though)
Prolific USB Flash Disk 256 MB (15996 blocks)
SanDisk Cruzer Mini USB Flash Drive 128MB (USB 2.0)  Works Great for mechassault install
SanDisk Cruzer Mini USB 128MB - Had to use 8MB-32MB image
Sandisk Mini Cruzer 256Mb USB 2.0 (15k+ blocks - tossed my notes on this)
Samsung 64Mb USB disk (4030 blocks)
Sony 64MB MicroVault (USB 2.0) - 3998 blocks - for MechInstaller, open 8-32MB .img, write to 64MB stick. Has security features, see JetFlash below (?)
Soyo CigarPro2 (USB 2.0, 128MB--the green plastic one) - shows up as "Prolific USB Flash Disk" on WinXP (7997 blocks)
Sweex 128 MB
Transcend JetFlash 64 MB - se below
Transcend JetFlash 128 MB - Depending on model, there are 6 JetFlash types, see link 
    http://www.transcendusa.com/Products/ModLi...eldNo=2&CatNo=4 and info in the paragraph above.
TwinMos MobileDisk III 64 MB (3998 Blocks)
Twinmos Mobile Disk USB 1.1 Pocket Pen Drive 64B (seller p/n XPD64) (Manuf p/n FMD064S) 
                                        (0ea0:6803,Manuf="USB",Prod="Solid state disk")
Typhoon USB Memory Adapter 32 MB (USB 1.1, Art. Nr. 83049, 2014 blocks, for MechInstaller, open
                                  "MechInstaller-1.0-FATX-8MB-to-32MB.img", write to 32MB stick)
Universal Smart Drive 64MB - used 8mb-32mb image
USB UltraDrive 32 MB (1998 blocks)
Zyon Systems 64MB popdrive - commonly handed out to trade show patrons:) - must be plugged in before xbox is powered on, otherwise nothing.

2 Devices that don't work

AIPTEK PenDisk 64MB
Apacer HandyDrive 64 MB (0d7d:0100, not detected)
Atech Pro-9 Card Reader with 8 CF or memory stick (not detected)
Belkin Media Reader USB2 8-in-1 (F5U248) with at least 4 different SM/CF media, from 32 to 128 MB (not detected)
Ben MP3 and Pen Drive 64MB
Casio Qv3000 Camera with with 8 meg casio CF-8x card (makes the screen flash over and over..)
Creative MuVo 128MB
Creative MuVo 64MB
Creative NOMAD MuVo NX 128meg (Xbox said "damaged" but then formatted it with 7005 blocks. but not recognised on reconnect)
Dazzle Memory Stick Reader (04e6:0314, screen flashes and "damaged" shows up when media removed from reader)
DataFab KESD-USBA Reader with Toshiba 16MB SD Memory Card (Memory screen flashes indefinitely)
Dell branded Lexar 16MB
Dell branded Lexar 64MB
DeLock UISDMC1S, 6x Card Reader with 2 slots + ExtreMEmory 256 MB CF-Card ("damaged")
DeLock UISDMC1S, 6x Card Reader with 2 slots +  Apacer 64 MB CF-Card ("damaged")
DeLock UISDMC1S, 6x Card Reader with 2 slots +  SanDisk 48 MB CF-Card ("damaged")
DeLock UISDMC1S, 6x Card Reader with 2 slots +  32 MB SmartMedia Card ("damaged")
DeLock UISDMC1S, 6x Card Reader with 2 slots +  64 MB SmartMedia Card ("damaged")
Disgo 512MB PRO USB2 (M-Systems DIS20512R) 0x08EC:0x0012, relative of DriveKey, bootable but "damaged"
Disgo 64MB (Damaged, even when low-level formatted)
DiskOnKey 16MB (says "damaged")
DiskOnKey 64MB (says "damaged")
Frontier Labs NexII with 8 meg Casio CF-8x card ("damaged")
FujiFilm FinePix 6800Z Camera (tested with 16 MB and 128 MB SmartMedia cards)
FUJIFILM 128MB USB 2.0 DRIVE (PLUG & PLAY) (says i may have a corrupt memory card)
HP Photosmart 620 with 256MB SanDisk SD memory card (camera says connected to pc, but xbox does not recognize)
HP Photosmart P-1000 with Hitachi 8MB CompactFlash Card
Hama 6-in-1 USB Card Reader (Model-Nr.: 46958) with PQI 128MB CompactFlash
Hama 6-in-1 USB Card Reader (Model-Nr.: 46958) with SanDisk 128MB SecureDigital
Hama 6-in-1 USB Card Reader (Model-Nr.: 46958) with HAMA SmartMedia 32MB
Hama 6-in-1 USB Card Reader (Model-Nr.: 46958) with Sony MSA-128A 128MB
Hama 6-in-1 USB Card Reader (Model-Nr.: 46958) with SanDisk 128MB CompactFlash (says "damaged")
Hama 6-in-1 USB Card Reader (Model-Nr.: 46958) with Canon 8MB CompactFlash (says "damaged")
Imation FlashGo! (IMN-USB-FG1) with at least 4 different SM/CF media, from 32 to 128 MB ("damaged")
Iomega PocketZIP 40 USB (says "damaged")
Iomega ZIP 250 USB (says "damaged" on all media)
Jump Shot 8MB (says "damaged")
KingMax usb 64 (says "damaged")
Kodak EasyShare CX6230 Camera -- neither internal memory nor 256 MB Sandisk SD card -- no apparent recognition by XBOX
Lexar JumpDrive 64MB USB memory stick
Lexar JumpDrive 128MB
Lexar JumpDrive Trio with 128mb Secure Digital card (says "damaged")
LG Flatron USB Drive 64 MB from haansecure (Korea) (says "damaged")
Memorex USB -> CF Card Reader, causes the memory page in the Dash to flicker repeatedly, tried with multiple CF (32, 64, 128)
Mercury Cyberpix - all models (says "damaged")
NAPA P22 WMA mp3 player
No-name (Lexar Chipset + Samsung Memory) 128 Meg USB 2.0 (not detected)
Nikon Coolpix 775 (with 8Mb Nikon card or 32MB Sandisk card) -- no apparent recognition by XBOX
Nikon Coolpix 5400 w/32mb sd card.  (shows moving rectangle on camera display and never connects)
Olympus USB SmartMedia Reader-Writer with at least one card of unknown size
Packard Bell AudioKey 32MB
PNY Attache 64MB (says "damaged")
PQI "Travelling Disk" translucent USB sticks, 64 MB (some work, some (09a6:8001) say "damaged")
QDI U2Disk 64MB
SanDisk Cruzer with SD 256MB card.
SanDisk ImageMate combination CompactFlash/SmartMedia to USB adapter
Softick Card Export II (SD drive emulation for the Palm OS - Uses USB mass storage driver) (Xbox breifly recognizes the card 1 time out of 10 - will format in FatX, but will not read savegames - Screen flashes)
Sony Cyber-shot DSC-P31 with Memory Stick (054c:0010, Camera recognizes USB connection but XBox screen flashes)
Sony Cyber-shot DSC-P32 with Memory Stick
Sony Cyber-shot DSC-p71 (makes the screen flash over and over..)
Sony DCR TRV18E Digital Camcorder with Memory Stick
Sony DCR TRV-25 Digital Camcorder with Memo
Sony Micro Vault 256 MB USB 2.0
Topcom Pocket Memory II 256 MB
Transcend JetFlash 2A 128MB (TS128MJF2A, 0c76:0005, see link above) just makes the memory screen flash forever.

2) Please have a look at this thread:
http://www.911cd.net/forums/index.php?showtopic=7632
and particularly to this post of mine:
http://www.911cd.net/forums/index.php?show...pic=7632&st=62#

3) It is a good idea to test the stick+motherboard combo with a "normal" dos boot utility, I found several of them:

sp27213 HP Windows Format Utility for USB Drive Key or DiskOnKey
sp27214 DOS-based Format Utility for HP Drive Key or DiskOnKey USB Device
sp27608 Windows-based Format Utility for HP Drive Key or DiskOnKey USB Device
(substitutes 27213)

Just make a google search for sp27xxx where x is the number and you will find the hp page for download.


Dell has a utility to make their keys bootable. R69131.EXE
ftp://ftp.dell.com/rmsd/R69131.exe

There is another one from hp called
cp004916
that includes syslinux.

And yet another one apparently from Smart Modular, known to be Lexar compatible, called
usb_memory_boot_setup.exe

(just google for the filename)

jaclaz

[cokeman]

Works Great with a Transcend JetFlash 1GB

But an idea' PE builder 3.2, With USB Flash Builder

and perhaps an other idea, a Small ISO file, and all the software as files on the USB stick, so that you only have an 32-64MB ISO, and the programs as normal files on the device, will that work? (This in PEbuilder 3.5?)

- Dahl

[webmedic]

yes it is true that not all usb drives are created equal. Many of them are of really cheap quality and barely run under windows even. There was a big stink about this also when mandrake came out with mandrake move bootable linux on a cd that would allow you to save your personal files to a usb stick. They foud out really quick that most usb drives are not of a very good quality.

It also doesn't help that allot of users are trying to use dell systems specificly as they are known to have issues with allot of things. For instance some hardware (not just dell) dont work with regular drivers and such. You have to use specific drivers for that hardware. The only times you see this are when the hardware has issue and they have to hack the drivers to get them to work.

I use sandisk here and cant say I ever have an issue. I'll try to build a bootable barts with it in a bit and report back.

[bigdaddy]

Just a follow up, when I run mkbt -i -x N:

This is what I get:

C:\pebuilder313\plugin\peinst>mkbt -i -x n:
* Inspect mode (-i)
* Expert mode (-x)
Checking Boot sector information
Boot sector type is "FAT"
Signature=55AAh, OK
Jump instruction=EB, OK
Jump offset=3C, OK
OEM ID="MSDOS5.0"
Bytes per sector=512, OK
Sectors per Cluster=32
Reserved sectors=2
Number of FATs=2, OK
Root entries=512
Media Descriptor=F8h
Sectors per FAT=251
Sectors per Track=63
Number of Heads=255
Hidden Sectors=63
Large Sectors=2052544 (0.98GB)
Physical Drive Number=00
Reserved=00h
Extended Boot Signature=29h, OK
Volume Serial Number=F2692384h
Volume Label="BartPE "
System ID="FAT16 "
Boot sector looks OK!

Obviously, the OEM ID should not be MSDOS5.0, but I have followed the instructions exactly and have no idea of what to do next.