The CD Forum > Pe2usb: Installing Bartpe To Usb Flash Disk

Full Version: Pe2usb: Installing Bartpe To Usb Flash Disk

The CD Forum > Bart's PE Builder > USB Booting

Pages: 1, 2, 3, 4, 5, 6, 7, 8, 9

Bart Lagerweij

Feb 9 2005, 09:18 AM

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

Feb 9 2005, 11:23 AM

@Bart, that looks great!
Thank you

this-is-me

Feb 9 2005, 12:56 PM

Why must the server 2003 ramdisk driver be enabled?

norseman

Feb 9 2005, 01:09 PM

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

Feb 9 2005, 01:14 PM

@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

Feb 9 2005, 01:17 PM

@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

Feb 9 2005, 12:47 PM

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

Feb 9 2005, 08:24 PM

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

Sillosyben

Feb 10 2005, 02:25 AM

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

Feb 10 2005, 03:55 AM

@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

Feb 10 2005, 01:32 PM

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

Feb 10 2005, 02:10 PM

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

Feb 10 2005, 02:30 PM

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

Thanks for your doing!

Bart Lagerweij

Feb 10 2005, 05:00 PM

@bigdaddy

QUOTE

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

Feb 10 2005, 06:38 PM

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

Feb 10 2005, 09:11 PM

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

Feb 11 2005, 05:53 AM

@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):

QUOTE

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:

QUOTE

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

Feb 11 2005, 06:42 AM

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

Feb 11 2005, 10:03 AM

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

Feb 11 2005, 10:33 AM

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.

khauyeung

Feb 11 2005, 02:31 PM

Bart, thanks for the pe2usb information with which I was able to make my MiniPE into the BartPE.iso and boot from the USB Flash Disk as RAMDISK X:. With similar approach using the setupldr.bin and ramdisk.sys of the SRSP1, I can also boot the ISO directly from the hard drive.

Loading up the RAMDISK for the whole ISO (from the USB flash) is pretty slow, but there is another BIG problem other than the loading speed: with the BartPE running in RAMDISK X:, the system was no longer able to set up our normal RAMDRIV B:. Without the RAMDRIV running, some programs cannot work properly.

Any idea to fix this RAMDISK and RAMDRIV conflict?

aec

Feb 11 2005, 04:02 PM

@khauyeung

QUOTE

...
the system was no longer able to set up our normal RAMDRIV B:.

Have a look at this thread Howto boot a Pebuilder iso from ram. This ramdrv issue has been discussed there. It seems to be a ramdrv-version related problem.

Regards

khauyeung

Feb 11 2005, 05:33 PM

QUOTE (aec @ Feb 11 2005, 04:02 PM)

Have a look at this thread Howto boot a Pebuilder iso from ram. This ramdrv issue has been discussed there. It seems to be a ramdrv-version related problem.

Regards

@ aec, thanks for pointing out the thread. Replacement of the QSoft Ramdisk Driver (RAMDRIV.SYS) to a later version 5.2.10.2 which comes with pebuilder v3.1.3 did fix the problem.

Jeff_Birt

Feb 11 2005, 09:05 PM

I tried this today and got a error after the ISO was loaded and the 'normal' set up screen starts. It could not find ntoskrnl, from the thread on booting to the ramdrive it seems one must use an XP w/sp2 cd as the source (I tried both XP/sp1 and W2K3 with no luck). Can one start with a XP/sp1 cd and slipstream sp2 (I think that is the correct term, don't fully understand yet)?

Thanks,

Jeff_Birt

fafot

Feb 11 2005, 11:44 PM

I have some silly problem that I cannot overcome: (my USB stick is Q: (Kingston - Data Traveler Elite 512Mb)

After creating the BartPE in the pebuilder\BartPE directory when I'm running the
pe2usb Q:
I get the error from mkisofs:

QUOTE

mkisofs: Uh oh, I cant find the boot image 'bootsect.bin' !

and the bootsect.bin is there:

CODE

Directory of N:\PEBuilder\BartPE

12/02/2005 14:40 <DIR> .
12/02/2005 14:40 <DIR> ..
02/11/2004 15:05 46 autorun.inf
12/02/2005 14:28 2,048 BOOTSECT.BIN
12/02/2005 14:25 <DIR> Documents and Settings
12/02/2005 14:25 <DIR> DOSUtil
12/02/2005 14:30 <DIR> I386
12/02/2005 14:26 <DIR> peshell
12/02/2005 14:27 <DIR> PROGRAMS
12/02/2005 14:25 0 WIN51IP
12/02/2005 14:25 0 WIN51IP.SP2
25/01/2005 18:36 221 WINBOM.INI

Here is my full run:

QUOTE

N:\PEBuilder>pe2usb Q:

BartPE USB Installer v1.0.1
Copyright © 2005 Bart Lagerweij. All rights reserved.
This program is free software. Use and/or distribute it under
the terms of the Nu2 License.

USB target drive set to "Q:"
Checking drive "Q:"
Checking files...
Checking bootsector from drive Q:
* Expert mode (-x)
* Inspect mode (-i)
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=16
Reserved sectors=6
Number of FATs=2, OK
Root entries=512
Media Descriptor=F8h
Sectors per FAT=249
Sectors per Track=63
Number of Heads=255
Hidden Sectors=11
Large Sectors=1019380 (0.49GB)
Physical Drive Number=00
Reserved=00h
Extended Boot Signature=29h, OK
Volume Serial Number=FCFA14A3h
Volume Label="BartPE "
System ID="FAT16 "
Boot sector looks OK!
Copying N:\PEBuilder\srsp1\ramdisk.sys to N:\PEBuilder\BartPE\i386\system32\driv
ers
1 file(s) copied.
Copying N:\PEBuilder\srsp1\setupldr.bin to Q:\ntldr
1 file(s) copied.
Copying N:\PEBuilder\BartPE\i386\ntdetect.com to Q:\
1 file(s) copied.
Building Q:\winnt.sif
Generating ISO image Q:\bartpe.iso
Warning: Creating ISO-9660:1999 (version 2) filesystem.
Warning: ISO-9660 filenames longer than 31 may cause buffer overflows in the OS.

mkisofs: Uh oh, I cant find the boot image 'bootsect.bin' !

Ready!

ISO image size is 0MB
*******************************************************************************
You should be able to boot this on systems with at least 64MB of memory!
*******************************************************************************

Done (program will be closed)
Press any key to continue . . .

Any ideas?
Tx

fafot

Feb 12 2005, 12:45 AM

I found the problem.

I was using the Cyrano custom_commands.cmd. In that script there is a uppercasing for bootsect.bin to BOOTSECT.BIN:

%PEUtilsPath%\filecase.exe /u /h /q "%OutDir%\BOOTSECT.BIN"

fafot

Feb 12 2005, 03:38 AM

Now after I created succesfully the iso on the stick I have that error when I booting:

Disk boot failure, insert system disk and press enter
and "boot sector looks OK" like in the post above.

Surely I setup the booting to boot USB stick in the Bios. (top in HDD boot priority). (Same stick boots with its own booting utility with other files formatted as FAT).

My PC: Shuttle SB65G2, Pentium 4 3.2Ghz

JonF

Feb 12 2005, 09:56 AM

QUOTE (bigdaddy @ Feb 10 2005, 06:38 PM)

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'm getting the same with with a Sandisk Cruzer mini 512 MB. I've tried very carefully twice, with no success. Here's the log of pe2usb:

CODE

BartPE USB Installer v1.0.1
Copyright (c) 2005 Bart Lagerweij. All rights reserved.
This program is free software. Use and/or distribute it under
the terms of the Nu2 License.

USB target drive set to "V:"
Checking drive "V:"
Checking files...

*******************************************************************************
Drive V: will be formatted!!! All data on drive will be erased!
*******************************************************************************

Type "YES" (uppercase) to continue:YES
Formating drive "V:"...
The type of the file system is FAT.
Verifying 488M
Initializing the File Allocation Table (FAT)...
Format complete.

512,180,224 bytes total disk space.
512,180,224 bytes available on disk.

8,192 bytes in each allocation unit.
62,522 allocation units available on disk.

16 bits in each FAT entry.

Volume Serial Number is 5403-0747
Installing bootsector from E:\Bart's_PE_Builder\pe2usb.bin on drive V:
* Expert mode (-x)
* Volume label set to "BartPE"
Reading source boot sector from "E:\Bart's_PE_Builder\pe2usb.bin"
Checking Boot sector information
Reading target boot sector from "\\.\V:"
Writing boot sector back to "\\.\V:"(try 0)
Checking bootsector from drive V:
* Expert mode (-x)
* Inspect mode (-i)
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=16
Reserved sectors=6
Number of FATs=2, OK
Root entries=512
Media Descriptor=F8h
Sectors per FAT=245
Sectors per Track=63
Number of Heads=255
Hidden Sectors=63
Large Sectors=1000881 (0.48GB)
Physical Drive Number=00
Reserved=00h
Extended Boot Signature=29h, OK
Volume Serial Number=54030747h
Volume Label="BartPE "
System ID="FAT16 "
Boot sector looks OK!
Copying E:\Bart's_PE_Builder\srsp1\ramdisk.sys to E:\Bart's_PE_Builder\BartPE\i
86\system32\drivers
1 file(s) copied.
Copying E:\Bart's_PE_Builder\srsp1\setupldr.bin to V:\ntldr
1 file(s) copied.
Copying E:\Bart's_PE_Builder\BartPE\i386\ntdetect.com to V:\
1 file(s) copied.
Building V:\winnt.sif
Generating ISO image V:\bartpe.iso
Warning: Creating ISO-9660:1999 (version 2) filesystem.
Warning: ISO-9660 filenames longer than 31 may cause buffer overflows in the OS

Size of boot image is 4 sectors -> No emulation
3.66% done, estimate finish Sat Feb 12 09:53:48 2005
7.31% done, estimate finish Sat Feb 12 09:54:29 2005
10.97% done, estimate finish Sat Feb 12 09:54:52 2005
14.62% done, estimate finish Sat Feb 12 09:54:36 2005
18.28% done, estimate finish Sat Feb 12 09:54:32 2005
21.94% done, estimate finish Sat Feb 12 09:54:24 2005
25.59% done, estimate finish Sat Feb 12 09:54:15 2005
29.25% done, estimate finish Sat Feb 12 09:54:12 2005
32.90% done, estimate finish Sat Feb 12 09:54:09 2005
36.56% done, estimate finish Sat Feb 12 09:54:02 2005
40.21% done, estimate finish Sat Feb 12 09:54:00 2005
43.87% done, estimate finish Sat Feb 12 09:53:55 2005
47.52% done, estimate finish Sat Feb 12 09:53:50 2005
51.18% done, estimate finish Sat Feb 12 09:53:48 2005
54.83% done, estimate finish Sat Feb 12 09:53:46 2005
58.49% done, estimate finish Sat Feb 12 09:53:43 2005
62.14% done, estimate finish Sat Feb 12 09:53:42 2005
65.79% done, estimate finish Sat Feb 12 09:53:42 2005
69.46% done, estimate finish Sat Feb 12 09:53:41 2005
73.11% done, estimate finish Sat Feb 12 09:53:38 2005
76.76% done, estimate finish Sat Feb 12 09:53:38 2005
80.42% done, estimate finish Sat Feb 12 09:53:34 2005
84.07% done, estimate finish Sat Feb 12 09:53:33 2005
87.72% done, estimate finish Sat Feb 12 09:53:29 2005
91.39% done, estimate finish Sat Feb 12 09:53:28 2005
95.04% done, estimate finish Sat Feb 12 09:53:28 2005
98.68% done, estimate finish Sat Feb 12 09:53:27 2005
Total translation table size: 2048
Total rockridge attributes bytes: 0
Total directory bytes: 199160
Path table size(bytes): 1736
136799 extents written (267 MB)

Ready!

ISO image size is 267MB
*******************************************************************************
You should be able to boot this on systems with at least 331MB of memory!
*******************************************************************************

Done (program will be closed)
Press any key to continue . . .

The_Doomer

Feb 12 2005, 02:56 PM

Here is a tool that can be of use to boot from Usb Flash disk. Have not tried it myself yet.

FlashBoot.

http://www.prime-expert.com/flashboot/screenshot.php
http://www.prime-expert.com/flashboot/features.php

Jeff_Birt

Feb 12 2005, 08:59 PM

OK, I slipstreamed XPpro (original, not sp1) with sp2, and repeated all the steps in Barts instructions. I now get just past the Setup screen to the Please Wait screen before it hangs. Since the ISO has already loaded at this point I don;t see how it can be a problem with the UFD (but will try another). Perhaps something is wroing with my build? Other than slipstreaming sp2 it's no options or additionl plugins, BartPE build. Should I have slipstreamed sp1 in before sp2?

Machine: Dell Latitiude D600
UFD: SanDisk Cruzer mini 512 mb

Added: I just tried slipstreaming sp1 then sp2, no change. Still hangs at the Please Wait screen. I'll try diffrent machines/UFD Monday at work

Thanks,

Jeff_Birt

webmedic

Feb 13 2005, 12:50 AM

dell?

Bart Lagerweij

Feb 13 2005, 04:38 AM

QUOTE (khauyeung @ Feb 11 2005, 08:31 PM)

Loading up the RAMDISK for the whole ISO (from the USB flash) is pretty slow, but there is another BIG problem other than the loading speed: with the BartPE running in RAMDISK X:, the system was no longer able to set up our normal RAMDRIV B:. Without the RAMDRIV running, some programs cannot work properly.

Any idea to fix this RAMDISK and RAMDRIV conflict?

Only thing that keeps ramdriv from loading is out of memory...
Try a smaller ramdriv or check if you have enought memory...

Regards,
Bart

Squale

Feb 13 2005, 05:27 PM

@ Bart,

Very good job.

All is ok (ASUS P4P800, 1 Go, USB stick PQI Cooldrive 1Go) ... no more BSOD (with error 7B) with ramdrive ... and it's very, very fast !

Regards
Squale.

fafot

Feb 14 2005, 01:21 AM

@Bart

Can you please give me a hint what I did wrong? My stick is brand new and extreemly fast 24Mb/15Mb R/W so I wonder what can cause that problem:

QUOTE

Now after I created succesfully the iso on the stick I have that error when I booting:

Disk boot failure, insert system disk and press enter
and "boot sector looks OK" like in the post above.

Surely I setup the booting to boot USB stick in the Bios. (top in HDD boot priority). (Same stick boots with its own booting utility with other files formatted as FAT).

My PC: Shuttle SB65G2, Pentium 4 3.2Ghz

Tx
fafot

Bart Lagerweij

Feb 14 2005, 02:44 AM

QUOTE (fafot @ Feb 14 2005, 07:21 AM)

@Bart

Can you please give me a hint what I did wrong? My stick is brand new and extreemly fast 24Mb/15Mb R/W so I wonder what can cause that problem:

QUOTE

Tx
fafot

What emulation does your bios use for your UFD?

Regards,
Bart.

InTheWayBoy

Feb 14 2005, 03:49 AM

Worked like a charm for me! I'm using a CompUSA brand 1GB USB 2.0 HD. Followed directions, using an SP2 source, and worked! VERY slow ramdisk load...my next quest is to slim her down some. Thanx!

fafot

Feb 14 2005, 03:50 AM

@Bart

I'm not sure what do you mean. I have English XP Pro SP2 and using XPE 1.02 with PEBuilder 3.1.3 on PC with 1Gb memory made from SP2. Here is my complete log:

QUOTE

BartPE USB Installer v1.0.1
Copyright © 2005 Bart Lagerweij. All rights reserved.
This program is free software. Use and/or distribute it under
the terms of the Nu2 License.

USB target drive set to "Q:"
Checking drive "Q:"
Checking files...
Checking bootsector from drive Q:
* Expert mode (-x)
* Inspect mode (-i)
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=16
Reserved sectors=6
Number of FATs=2, OK
Root entries=512
Media Descriptor=F8h
Sectors per FAT=249
Sectors per Track=63
Number of Heads=255
Hidden Sectors=11
Large Sectors=1019380 (0.49GB)
Physical Drive Number=00
Reserved=00h
Extended Boot Signature=29h, OK
Volume Serial Number=FCFA14A3h
Volume Label="BartPE "
System ID="FAT16 "
Boot sector looks OK!
Copying N:\PEBuilder\srsp1\ramdisk.sys to N:\PEBuilder\BartPE\i386\system32\driv
ers
1 file(s) copied.
Copying N:\PEBuilder\srsp1\setupldr.bin to Q:\ntldr
1 file(s) copied.
Copying N:\PEBuilder\BartPE\i386\ntdetect.com to Q:\
1 file(s) copied.
Building Q:\winnt.sif
Generating ISO image Q:\bartpe.iso
mkisofs: Warning: -rock has same effect as -rational-rock on this platform.
Warning: creating filesystem that does not conform to ISO-9660.
Warning: Creating ISO-9660:1999 (version 2) filesystem.
Warning: ISO-9660 filenames longer than 31 may cause buffer overflows in the OS.

Size of boot image is 4 sectors -> No emulation
2.02% done, estimate finish Sat Feb 12 17:35:43 2005
4.04% done, estimate finish Sat Feb 12 17:35:43 2005
6.06% done, estimate finish Sat Feb 12 17:35:27 2005
8.07% done, estimate finish Sat Feb 12 17:35:18 2005
10.09% done, estimate finish Sat Feb 12 17:35:23 2005
12.10% done, estimate finish Sat Feb 12 17:35:27 2005
14.12% done, estimate finish Sat Feb 12 17:35:22 2005
16.14% done, estimate finish Sat Feb 12 17:35:12 2005
18.16% done, estimate finish Sat Feb 12 17:35:16 2005
20.17% done, estimate finish Sat Feb 12 17:35:13 2005
22.19% done, estimate finish Sat Feb 12 17:35:12 2005
24.20% done, estimate finish Sat Feb 12 17:35:10 2005
26.23% done, estimate finish Sat Feb 12 17:35:09 2005
28.24% done, estimate finish Sat Feb 12 17:35:11 2005
30.26% done, estimate finish Sat Feb 12 17:35:10 2005
32.27% done, estimate finish Sat Feb 12 17:35:06 2005
34.29% done, estimate finish Sat Feb 12 17:35:08 2005
36.31% done, estimate finish Sat Feb 12 17:35:07 2005
38.33% done, estimate finish Sat Feb 12 17:35:07 2005
40.34% done, estimate finish Sat Feb 12 17:35:09 2005
42.36% done, estimate finish Sat Feb 12 17:35:08 2005
44.37% done, estimate finish Sat Feb 12 17:35:07 2005
46.39% done, estimate finish Sat Feb 12 17:35:07 2005
48.41% done, estimate finish Sat Feb 12 17:35:06 2005
50.43% done, estimate finish Sat Feb 12 17:35:06 2005
52.44% done, estimate finish Sat Feb 12 17:35:07 2005
54.46% done, estimate finish Sat Feb 12 17:35:08 2005
56.48% done, estimate finish Sat Feb 12 17:35:08 2005
58.49% done, estimate finish Sat Feb 12 17:35:09 2005
60.51% done, estimate finish Sat Feb 12 17:35:10 2005
62.53% done, estimate finish Sat Feb 12 17:35:10 2005
64.54% done, estimate finish Sat Feb 12 17:35:11 2005
66.56% done, estimate finish Sat Feb 12 17:35:10 2005
68.58% done, estimate finish Sat Feb 12 17:35:11 2005
70.60% done, estimate finish Sat Feb 12 17:35:12 2005
72.61% done, estimate finish Sat Feb 12 17:35:12 2005
74.63% done, estimate finish Sat Feb 12 17:35:12 2005
76.64% done, estimate finish Sat Feb 12 17:35:13 2005
78.66% done, estimate finish Sat Feb 12 17:35:14 2005
80.68% done, estimate finish Sat Feb 12 17:35:15 2005
82.69% done, estimate finish Sat Feb 12 17:35:15 2005
84.71% done, estimate finish Sat Feb 12 17:35:15 2005
86.73% done, estimate finish Sat Feb 12 17:35:16 2005
88.74% done, estimate finish Sat Feb 12 17:35:16 2005
90.76% done, estimate finish Sat Feb 12 17:35:16 2005
92.78% done, estimate finish Sat Feb 12 17:35:16 2005
94.80% done, estimate finish Sat Feb 12 17:35:16 2005
96.81% done, estimate finish Sat Feb 12 17:35:17 2005
98.83% done, estimate finish Sat Feb 12 17:35:16 2005
Total translation table size: 2048
Total rockridge attributes bytes: 393703
Total directory bytes: 832984
Path table size(bytes): 3282
247908 extents written (484 MB)

Ready!

ISO image size is 484MB
*******************************************************************************
You should be able to boot this on systems with at least 548MB of memory!
*******************************************************************************

Done (program will be closed)
Press any key to continue . . .

N:\PEBuilder>

Tx
fafot

Joshua

Feb 14 2005, 03:55 AM

@fafot
Bart want's to now what emulation your bios use for UFD.
Go in to your motherboard bios and have a look under options,
or look in motherboard maual for info.

Joshua

Bart Lagerweij

Feb 14 2005, 04:22 AM

@fafot

You should make your USB iso image smaller or else it will not boot on most systems out there...

Try to keep it below 200MB...

Regards,
Bart.

fafot

Feb 14 2005, 04:35 AM

@Bart
Tx, I know that it sghould be small, but I just testing it on the big system.
Regarding the - UFD - USB flash drive Emulation - I have no idea where its sits in the BIOS.

Joshua

Feb 14 2005, 04:46 AM

QUOTE (fafot @ Feb 14 2005, 09:35 AM)

Regarding the - UFD - I have no idea where its sits in the BIOS.

@fafot
What motherboard and bios version do you use?

Joshua

fafot

Feb 14 2005, 05:40 AM

Shuttle - SB65G2, Phoenix - Award Bios, the latest from Sep 2004.
I can boot USB stick - I actualy using my old stick 128Mb for more than a year for emergency programs like Ghost. The problem is only with the BartPE on the stick...

Squale

Feb 14 2005, 06:48 AM

@Bart,

Just for clarification, in pe2usb.cmd, you use :
format %_target% /fs:fat /u /v:usb /backup

But the switchs /u and /backup seem not to exist

???? (i.e Crosoft).

Do you agree with me ?

Squale.

Bart Lagerweij

Feb 14 2005, 07:33 AM

@Squale

Nope, I don't agree...

i.e. Bart:
format.com:

CODE

000007f0h: 32 33 32 4B 00 00 00 00 2F 66 3A 31 32 33 32 00; 232K..../f:1232.
00000800h: 2F 66 3A 31 32 30 30 4B 42 00 00 00 2F 66 3A 31; /f:1200KB.../f:1
00000810h: 32 30 30 4B 00 00 00 00 2F 66 3A 31 32 30 30 00; 200K..../f:1200.
00000820h: 2F 66 3A 37 32 30 4B 42 00 00 00 00 2F 66 3A 37; /f:720KB..../f:7
00000830h: 32 30 4B 00 2F 66 3A 37 32 30 00 00 2F 66 3A 36; 20K./f:720../f:6
00000840h: 34 30 4B 42 00 00 00 00 2F 66 3A 36 34 30 4B 00; 40KB..../f:640K.
00000850h: 2F 66 3A 36 34 30 00 00 2F 78 00 00 2F 79 00 00; /f:640../x../y..
00000860h: 2F 62 61 63 6B 75 70 00 2F 76 3A 2A 00 00 00 00; /backup./v:*....
00000870h: 2F 76 3A 22 22 00 00 00 2F 66 6F 72 63 65 00 00; /v:"".../force..
00000880h: 2F 63 00 00 2F 71 00 00 2F 75 00 00 2F 76 00 00; /c../q../u../v..
00000890h: 2A 00 00 00 25 73 25 57 00 00 00 00 46 4F 52 4D; *...%s%W....FORM
000008a0h: 41 54 00 00 25 64 25 64 00 00 00 00 25 64 00 00; AT..%d%d....%d..
000008b0h: 46 6F 72 6D 61 74 45 78 00 00 00 00 55 00 00 00; FormatEx....U...
000008c0h: 4E 54 46 53 00 00 00 00 46 41 54 33 32 00 00 00; NTFS....FAT32...
000008d0h: 46 41 54 00 52 41 57 00 48 50 46 53 00 00 00 00; FAT.RAW.HPFS....
000008e0h: FF FF FF FF 49 59 00 01 5D 59 00 01 4E 42 31 30; ÿÿÿÿIY..]Y..NB10

@fafot

check all screens from your bios setup. You should have the emulation type set to harddisk...

Regards,
Bart.

Squale

Feb 14 2005, 02:20 PM

QUOTE (Bart Lagerweij @ Feb 14 2005, 12:33 PM)

@Squale

Nope, I don't agree...

But you are a very malignant fox, and you do not hold any account of official microsoft information

Squale

fafot

Feb 14 2005, 06:56 PM

@Bart

Now I understand what do you mean - took me a while...

I already tried all of them:
USB-FDD
USB-ZIP
and another two. I don't have USB-HDD emulation but it is not needed because the only thing that matter is the "Hard Disk Boot Priority" order that setting the USB-Disk(0) to top one. It works correctly when I boot that stick with usual FAT - DOS formatting, but not with the BartPE Pe2usb.

fafot

jaclaz

Feb 15 2005, 04:20 AM

@fafot

From what I gathered there are two "formats" for USB sticks:
1) is called "superfloppy", and applies to "ZIP" and LS-120" disks, it is JUST a partition with NO MBR (Master Boot Record) and NO Partition Table.
2) is like a "normal" Hard Disk, so that it has the first (63?) sectors hidden and on the first one there is the MBR and Partition Table.

see here also:
http://www.marlow.dk/site.php/tech/usbkeys

jaclaz

fafot

Feb 15 2005, 07:41 AM

@Jaclaz
I understand but you see, this are my BIOS settings: Click on each link:

Advanced Bios Features
Hard Disk Boot Priority
First Boot Device

So, as I said the only thing that sets the boot order for USB Stick is the Hard Disk Boot Priority that is setting the stick as USB-HDD(0). It is working OK with the same USb formatted with dos but not with BartPE.
BTW - The First Boot Device has NO influence on the booting.

jaclaz

Feb 15 2005, 07:22 PM

@fafot

From the screens you posted it looks like your motherboard recognizes the stick correctly, so maybe there is some problem in the way it is "MBRed" / formatted under BartPE.

Please do confirm that your stick is formatted as a hard disk (i.e. it has an MBR)
BOTH when formatted under DOS (the setup that works)
AND when formatted under BartPe (the setup that does not)

You can "try" to use the MBRfix utility:
http://www.911cd.net/forums/index.php?show...topic=10606&hl=
http://www.911cd.net/forums/index.php?show...topic=10684&hl=
http://www.911cd.net/forums/index.php?show...topic=10768&hl=

to rebuild the MBR.

Or you could use it to dump contents of the MBR on the stick (BOTH versions) and post it here.

jaclaz

fafot

Feb 16 2005, 12:22 AM

@jaclaz

Success

After plying with my UFD for good few hours and trying 4 different format utilities I managed to make it work. Here are the findings:

0. I am using the Kingston Data Traveller Elite HS 2.0 (hardware ver. 5.02).
1. The only format utility that made it work was the HP USB format utility Ver. 2.0.6 using FAT file system. (I tried the Kingston utility, Dell, VIOSoft Recovery Manager and the HP).
2. After formatting with this utility I just used the pe2usb <USBdisk>.
3. Using Bart format made the UFD unbootable.
4. Here is the comparison between BART and HP MBRs:

5. The MBR-after-Bart:

The MBR-after-HPutility:

@Bart - can you please check what is causing that problem with your format utility so it will be more compatible?

@all
Thanks you for your help

My current test image size is 208Mb that includes the very basic Bart plugins with 32Mb ramdrv. What is puzzling me is the loading time that was very long: OVER 6 minutes on P4 3.2 GHz 1GB memory and the same with Athlon 2500+ 512Mb memory.

But... after it loaded it was lightning fast, just like running from HDD.

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.