If you use grub4dos (with grldr.mbr installed to the MBR or with a bootsector invoking grldr) you do not actually need "NTLDR" (in the sense of a SETUPLDR.BIN renamed to NTLDR on ROOT of the drive), as you can chainload from grub4dos directly the /minint/setupldr.bin, typically:

If you use the multipartition approach, you will need of course to add cfadisk.sys or dummydisk.sys to the BartPE build (if you want to access from the booted environment partitions beyond first one), search on the board for the plugin by cdob.

jaclaz

@Patrick Cates


You can use my 'Bootable USB-Drive Utility' to install BartPE on your USB stick with the following workaround:
prepare your stick as a multipartition drive (e.g. with the Microdrive driver)
or format it with RMPARTUSB.exe http://www.boot-land.net/forums/index.php?...ost&id=8150 (thanks jaclaz for the link!)
i've made a test with RMPARTUSB.exe:
1. 'rmpartusb.exe list' to find the USB drive number, e.g. 2
2. 'rmpartusb.exe drive=2 xp fat32 volume=PE-STICK' (drive= number from step 1)
3. copy this batch to the stick - prepstick.cmd:

4. execute 'prepstick.cmd' on the stick
5. execute my 'Bootable USB-Drive Utility' and select 'Update'
say 'y' at the following prompt:
Drive found with such a BartPE-Installation (USB-Stick z:)
Update this USB-Stick? (y,n): y
say 'y' at the following prompt:
Siblo Bootmanager found on this USB-Drive...
Convert to the new style Bootmanager? (y/n): y
6.
after the 'Bootable USB-Drive Utility' has finished, you can delete 'prepstick.cmd' and the folder 'to_delete_(siblo)' on the stick

now you should be able to boot the stick, and start BartPE from the boot-menu

fuwi

For the record, jaclaz DID NOT post a direct link to an attachment .

He posted a link to a thread where user steve6375 posted his app.

The thread is here:
http://www.boot-land.net/forums/index.php?showtopic=7739

Latest version of the app is attached to this post:
http://www.boot-land.net/forums/index.php?...=7739&st=33

The app is FREEWARE for Personal use only:


jaclaz

@jaclaz



sorry...
copy/pasted the wrong link from my notes

fuwi

NO prob.

To add to info about FAt32 32Gb format limit:
http://www.online-tech-tips.com/computer-t...rive-to-fat-32/

jaclaz

@all

New version of my USB-Boot Utilities available (v1.6.6)

New: option to bypass the internal formatter on creating new USB-Sticks:
create a dummy file 'format.ok' on the already (correctly) partitioned and formatted stick,
then select 'Create a new bootable….' as usual:


With the new version of the USB-Boot Utilities, this workaround http://www.911cd.net/forums//index.php?sho...st&p=155995 is no longer necessary.

Now you can use your preferred tool to partition & format the USB-Stick, e.g. gparted in Parted Magic http://www.911cd.net/forums//index.php?s=&...st&p=155586

Only 1 file has changed (budu.cmd) -> update all occurrences of budu.cmd in your installation.

-> Download link for the new version in the first post

fuwi

And steve6375 posted a new version, 1.9, here:
http://www.boot-land.net/forums/index.php?...=7739&st=54

And wimb has made his own version (derived loosely from MBRBATCH/MKIMG) and included it in his do-everything-tool:
http://www.boot-land.net/forums/index.php?...5306&st=196

(friendly ) competition is a great thing

Maybe we will soon be able to finally put the "HP" (read Datasystems ) utility at rest after several years of good (but also bad ) service.

jaclaz

Hi,

I have recently used the FreeDos option and have discovered that the keyboard mappings, particularly for symbols (e.g. /?!@#~ etc.) do not work properly - you get weird characters instead of the character on the keyboard.

I have tested on a couple of computers with identical results.

Is this a known issue?

VW

I don't know if it is a known issue.

But once a OS is loaded, it's the OS own keyboard drivers (or lack of them) that comes into play.

Does FreeDOS booted through ANY other mean behave the same?

In other words, what makes you think that this is related to the booting and not to the way you need to modify/integrate the FreeDOS files?

What is the keyboard layout of the keyboard you are using on those PC's?

What are EXACTLY the keys that are wrongly mapped?

jaclaz

@VeeDub


To change the keyboard mapping for the FreeDos option, you must edit the AUTOEXEC.BAT file in the root of the stick:

Currently the swiss-german (SG) mapping is active, because i am swiss-german.
Change it for your country.

fuwi

@fuwi

This was the issue.

I would suggest that this ought to be a question that is asked at setup, and the appropriate default chosen. This is a potential trap for the un-wary, and I wasted sometime trying to figure out what was going on with the keyboard.

Thanks

VW

@all

New version of my USB-Boot Utilities available (v1.6.7)

Now the filesystem for USB-Sticks can be switched between FAT, FAT32, NTFS and no reformat (no reformat: the stick must be correctly
partitioned and formatted with an other utility, e.g. RMPrepUSB.exe http://www.boot-land.net/forums/index.php?showtopic=7739)

To prevent the Main-Bootmenu from overloading, i have implemented a submenu 'Others' (menu2.lst).
From the submenu 'Others' you can go 'Back to Mainmenu' (back and forth).
If you create a new USB-Drive, FreeDOS (if drive is FAT or FAT32) and the Hitachi Drive Fitness Test are installed in 'Others' (menu2.lst).
In menu2.lst, you can insert your personal menu-items.

-> Download link for the new version in the first post

fuwi

Here are my experiences and suggestions

I'm dl last v1.6.7 and expanded in USB_Boot folder (same hierarchy level as 'plugin').
Before beginning, I looked the post and in cmd files. Starting 'main' BOOTABLE_USB-DRIVE.cmd or budu.cmd produce exit without error message.
I found that the initial set of variables does not work for some stupid reason, so I hardcoded. Note, this is my situation, adjust it to your situation:

First in Config_SourcePath.cmd (as already suggested):
set SourcePath="D:\Reatogo-235\ReatogoPE"

then in budu.cmd (main problem):
:: set WorkDrv=%~d0
set WorkDrv=D:
:: set WorkDir=%~dp0
set WorkDir=D:\Reatogo-235\USB_Boot\

After this intervention utility is started normally. As you can see I use Reatogo (BartPE + Xpe). Destination is usb stick Verbatim Store 'n' Go 2Gb.
Somewhere is recommended, and the selected FAT. Routine has made all properly unless XPE / Reatogo specifics.
I am manually copied from Xpe/Reatogo Destination Folder:
SFX folder - Xpe profiles
and missing files from root:
autorun.inf - Reatogo use it to start reatogoMenu.exe, different from the utility
Panther.ico - my customized, original is reatogoBlue.ico
reatogoMenu.exe
reatogoMenu.ini

Tested on Thinkpad R51 and everything is ok. Manually copying is not the problem, but the proposal of utility update for Xpe / Reatogo users.

fuwi

I would try adding to the batches two lines at the beginning:


http://www.robvanderwoude.com/parameters.php

First one should be the "stupid reason".
Second one should make no harm.

jaclaz

USB-Boot_Utilities

I am still testing the use of this tool
It does work, but, I do have a couple problems.

One that I am not sure is related to this tool with booting img files like memtest on some systems

The second that is directly related to this tool is,,,

The update feature doesn't always work.
Every second try, or even just right after creating the stick, the update refuses to copy files over to the stick
The tool just hangs at "Processing folder 'minint'..." , with no activity on the stick.
This happens on multiple PC's.

I have to copy my custom files and folders, recreate the stick, then copy my custom stuff back to it.
If I just try to update minint folder by deleteing the minint and programs folders and copying over the i386 and rename minint
My bartpe fails to load properly and services fail and doesn't boot.

It may depend on the size of the stick.
And on the amount of files (size of the build).
And if there are non-standard named files.
There are known problems when "base" files are recorded past a given address on the disk, they may be beyond reach of the initial loader(s).
Check this same thread, starting from here:
http://www.911cd.net/forums//index.php?sho...21702&st=44

You may want to adapt the batch to your build.

jaclaz

In the script I use to update my writable installs of BartPE I found that I needed to remove the Hidden attribute from the Config's log files else the system files didn't get updated.


The running of BartPE resets them to Hidden every time.

hth

@Ed_P


strange...

tried to reproduce:
1. create new stick: DEFAULT & DEFAULT.LOG, SAM & SAM.LOG, SECURITY & SECURITY.LOG, SOFTWARE & SOFTWARE.LOG -> all are from 29.04.09, none is hidden
2. booting the stick: SAM.LOG & SECURITY.LOG are now 04.05.09 and hidden, all other files as in step 1.
3. updating the stick: DEFAULT & DEFAULT.LOG, SAM & SAM.LOG, SECURITY & SECURITY.LOG, SOFTWARE & SOFTWARE.LOG -> all are again from 29.04.09, none is hidden (same as in step 1.)

maybe i have something misunderstood, what to you mean with

fuwi

@Nikky


I've made a test scenario:
On my D: drive, i've created a folder 'Reatogo-235'. In 'Reatogo-235', i created 2 folders -> 'ReatogoPE' and 'USB_Boot'.
I've copied my Bootable USB-Drive Utility to 'USB_Boot' and my PEBuilder-Output to 'ReatogoPE'
I've changed the SourcePath to 'D:\Reatogo-235\USB_Boot\'.
I've not changed 'WorkDrv' and 'WorkDir' in budu.cmd (leave unchanged %~d0 resp. %~dp0).

Then i've created a new stick, and tested the 'Update'-function -> everything works fine!

Second:

FAT32 works also...
Instead of manually copying your Xpe/Reatogo specific files and folders, you can do that automatically in 'customize.cmd'.
In 'customize.cmd' you can use all the environment-vars from budu.cmd (like %DrvLetter%, %SourcePath% etc).
Because 'customize.cmd' runs at the end of the 'Bootable USB-Drive Utility', a file already copied by the 'Create'-function
can be replaced with a custom version of the file (e.g. autorun.inf).
Remember: 'customize.cmd' is running on 'creating' a new bootable drive, not on 'updating' an existing drive.
And don't forget to save your individual folder 'Custom' before you replace the entire 'Bootable USB-Drive Utility' with a newer version from my homepage

BTW: perhaps it would be a good idea to implement in the next version a 'custom-upd.cmd' batch (called by the 'Update'-function) for updating user specific files and folders?

fuwi

@Tepid



To debug:
- make a copy of budu.cmd (e.g. budu.cmd.org).
- open budu.cmd with notepad, search for ":UPD2" (without the quotes)
- after ":UPD2" insert "echo on" (without the quotes)
- make a stick-update, wait until no activity on the stick and verify (and post here) the last few verbose lines in the cmd-window.

fuwi

The update portion of my script for minint is simply an XCOPY command. Without the fix for the hidden files it would error out and not copy any files remaining to be updated in the minint folder. I should have shown you more of that portion of my script.



Hopefully this clears up what I meant.

@Ed_P


You use your own script for Update, right? (because this code is not from my Utility).
I use robocopy /mir for updating, this mirrors exactly the source in the destination, no problems with attributes

This is the corresponding part in my script (budu.cmd):

fuwi

@fuwi

Having a boot problem with a USB-Stick created by the utility not starting on a Gigabyte M61PM-S2. Previously USB would boot using a HP formatted stick and GRUB4DOS

Boot.ini

As I would prefer to use your utility for all my USB sticks, any suggestions on how to troubleshoot?

Thanks

VW

@VeeDub


I don't have a machine with such a mainboard, so it's difficult for me to give you suggestions for troubleshooting
What happens at booting ?
Gigabyte M61PM-S2 rev. 1.0 or rev. 2.0 ?
Do you have the most recent BIOS ? (version F9C from 2008/03/10)
http://www.gigabyte.com.tw/Search/Search_L...SearchType=BIOS

fuwi

@fuwi
At booting - it just sits and waits - or if other media alternatives are configured in the BIOS, the alternative media is attempted.

I'm not sure whether it is Rev 1.0 or 2.0, the machine is at a remote location. I won't be able to check for a few days.

The BIOS version is F8, but as it has booted in the past while it's not the latest I would have thought it is current enough. I am going to build a stick using an alternative method, and if that works, then I'll pass on the details for reference. At the end of the day if occassionally I have to use a different approach for older computers it's not the end of the world.

Thanks

VW

@all

New version of my 'Bootable USB-Drive Utility' available (v1.6.8)
-> Info's & download link for the new version in the first post

fuwi

@VeeDub

Maybe the Gigabyte M61PM-S2 mainboard has USB-Boot problems with USB-drives with non-standard bootsectors.
You can try the new version of my USB-Boot Utilities (v1.6.8). With this version, you can re-install grub4dos back to the MBR
(default it is in the bootsector). Read Info's in the first post.

fuwi

@all

I've noticed that there is a problem using my Bootable USB-Drive Utility with a PEBuilder project using Win 2003 Server SP1 or SP2 as source.
If you create a Boot-Kicker CD, or if you change (rename) the 'minint' to 'i386', the you get the error 'NTLDR is corrupt' and BartPE doesn't boot.

Solution:
Create a plugin W2k3_SETUPLDR_Fix (reference: http://ubcd4win.com/forum/index.php?showto...t=#entry61450):

Copy the setupldr.bin file from the i386 folder of your Server 2003 CD into the files folder of the plugin.

Then:
1. open setupldr.bin in the plugins files folder with your favorite hex editor
2. goto hex address: 0x2060
3. change "74 03" to "EB 1A"
4. save it
(reference: http://www.msfn.org/board/index.php?showtopic=58410)

Rebuild your PEBilder project, make an Update of the USB-drive with the Bootable USB-Drive Utility and the USB-Drive should now boot without errors.

Note: this patched Server 2003 setupldr.bin can also used in PEBuilder projects using XP as source.

fuwi

Don't you use gsar.exe already?

Post #69 http://www.msfn.org/board/index.php?s=&...st&p=580692
This works at all lanuages 2003 SP1 and SP2.

IF need be you can run this at all XP, x46:xda:x74:x03 is not available.
Setupldr.bin is not changed.

You may call this gsar command always.

There is another robocopy.exe version, part of Robocopy GUI. This version runs at XP.
http://technet.microsoft.com/en-us/magazine/cc160891.aspx

@cdob

Thanks for pointing me to the newer version of robocopy. I've obtained it and i will test it (especially the /dst parameter).
In the next version of my Utility, i will detect and patch a Windows Server 2003 setupldr.bin automatically - using the enhanced search string "46 da 74 03" - as you suggest in your post http://www.msfn.org/board/index.php?showto...mp;#entry580692

fuwi

Hello!

I'm new on this board.
In fact, I've solved my problem while waiting my authorization to write in the forum.

With this marvelous tool, I've managed to format in FAT32 my 8GB "CORSAIR Flash Voyager" and make it bootable
It's very useful ! You did a nice work guys !

My aim was to put WinPE and the recovery Ghost image of my ASUS Eee 1000H (delivered on DVD in the Asus package) to an USB stick (so no need to buy an external DVD player... I prefer to put money in an USB stick ! ).
First, I did that using the russian release of PEtoUSB 3.0.0.8 ( http://eaz.nm.ru/download/PeToUSB_3.0.0.8.zip ) that allows you NTFS format, very useful for keys > 4GB. The initial PEtoUSB 3.0.0.7 is limited to FAT16, 2GB (sometimes, for some sticks, it can handle 4GB with 64KB! clusters according to some witnesses).
If you're afraid by using code from russian site, you can check it at http://www.virustotal.com : it seems clean !
...but you'll find 7 alerts for USB-Boot_Utilities.zip !!!
Hey Fuwi ! They are all false positive alerts, aren't they ?
You should write to these naysayers to tell them you're not a cracker although a piece of code in your package handles MBR !

I was satisfied till I read NTFS was not a good idea for USB sticks because of many I/O on the stick with this format.

Q1- Do you have valuable web links that explain that in detail ?
If the NTFS stick stays in a drawer and is only used in case of emergency, it's a minor problem, isn't it ?
The problem occurs if you use your stick very often with other data. It can shorten the life of the stick, if I've well understood.
The good point is that the start up of WinPE is quicker than in FAT32 format that can be important if you have to restore Ghost image on thousands of netbooks !

So I've successfully tested a FAT32 solution with your tool.
I answered "no" to BartPE installation cause I use WinPE. I extracted and copied the WinPE .ISO from Asus DVD to my stick and made the changes manually:

- rename directory "i386" to "minint" (no quote !)
- copy NTDETECT.COM from "minint" to root directory of the stick
- edit \minint\system32\winpshl.ini
- replace X:\EPCRecover.exe with X:\ghost32.exe to directly start Ghost recovery tool
- save your changes
- edit \menu.lst and add to the menu entries


- save your changes

And now reboot your PC, in BIOS select USB stick to boot and enjoy !


Yet I've a few questions :

Q2- Is it possible to hide GRUB4DOS menu (I just need to "chainload") ? The menu is nice and can be very useful but in my case, I just need WinPE and Ghost to start.

*edit*
I answer to myself: in fact, the answer is in the question !
You just have to put only this line in menu.lst :



Q3- In fact, I don't understand very well why we have to use a "chainload" to boot a FAT32 USB key and not for a NTFS one. Is it a kind of bug with MicroSoft MBR ? What is actually the problem ? Any links to clarify that ?

Q4- Could it be possible to develop a PEtoUSB release, or similar tool, that handles FAT32 format without "chainload" ?
(I've asked to the official PEtoUSB site but had no answer. Obviously, no new development expected)

Sorry for this very long 1st post.

Best regards,


Steve.

Steve,
simply READ this thread. from the beginning.
The problems about the "standard" bootsector for FAT32 being "picky" has been talked about at length.

About wear due to the NTFS filesystem, it has become a lesser problem for TWO reasons:
1) prices going down
2) newer sticks with internal wear leveling algorithms

In any case, if you use the stick as a bootable system, disabling partially the semi-journaling features of NTFS is advised, by disabling the lat access timestamp:
http://www.pctools.com/guides/registry/detail/50/
http://www.uwe-sieber.de/usbstick_e.html

You do NOT need this:


Simply change your menu.lst from:

to:


But since you actually boot from the stick, it is already ROOT, so all you need is:


About menu.lst, you may try to change the "embedded" one in grldr, see here:
http://diddy.boot-land.net/grub4dos/files/embedded.htm

jaclaz

@fuwi

In the meantime I built a USB stick using PeToUSB which does boot on the Gigabyte system.

This is not a system that I have physical access to on a regular basis, but at some stage I will try a USB stick with the later version and see whether it also works.

Thanks

VW

Hi Jaclaz !

I've tested your trick :
- in menu.lst : chainloader /minint/setupldr.bin => ok ! chainloader can access any file in any directory
- but NTDETECT.COM must be under the root directory of the stick, else I get a "NTDETECT failed" message on boot and it stops

So, only one step saved (in fact 2: copy and rename)... but it's better than nothing, thanks !

Regards,

Steve.

You are right.

My bad.

I'm so used to "multi-boot" thingies that I forgot that "one" NTDETECT.COM has to be in ROOT.

I seem to remember that manipulating SETUPLDR.BIN and/or TXTSETUP.SIF (or both) it is possible to have everything within the subdirectory, but cannot seem to find right now a "complete" reference.
These may be however of your interest:
http://www.911cd.net/forums//index.php?showtopic=17504
http://www.msfn.org/board/index.php?showtopic=130828
http://www.msfn.org/board/index.php?showtopic=119742

jaclaz

I've modified my initial post to explain the simplest way to boot WinPE with Ghost on a FAT32 stick, taking into account Jaclaz's comments.

Steve

@all

New version of my 'Bootable USB-Drive Utility' available (v1.6.9)
-> Info's & download link for the new version in the first post

fuwi

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

fuwi

@fuwi

Is it possible to add a new hot key (like "S") that used to switch the Grub4dos either install on bootsector or MBR ?

I searched the topic and didn't see anything. Is there anyway to utilize the fast speed of the kicker-cd iso on a usb drive, but convert the whole process to work on a BartPE boot CD?

NOT what you asked, but maybe you can try sorting the source appropriately.

See here:
http://www.911cd.net/forums//index.php?sho...21702&st=63
up to post #71

jaclaz

Just to try and keep things as together as possible, dencorso has posted here:
http://www.boot-land.net/forums/index.php?...=8528&st=21
a pre-compiled version of the tool discussed previously, here:
http://www.911cd.net/forums//index.php?sho...1702&st=129
the one to patch FAT32 bootsectors with the 4 NOP's to avoid CHS problems.

jaclaz

@jaclaz

Since vers. 1.6.4 (March 09) my Bootable USB-Drive Utility starts the grldr from the bootsector instead from the MBR, see post #148
so i have not a MSWIN4.1 nor a MSDOS5.0 resp. a NTFS bootsector -> i have a GRLDR bootsector.

Here an example of such a GRLDR bootsector:


As you can see, there is no byte sequence 0x0F 0x82 0x4A 0x00 or 0x0F 0x82 0x3A 0x00, so i don't know, how i can kill the CHS access.
On the other hand, i have no feedback received for problems with booting from the GRLDR bootsector.

fuwi

Most probably the GRLDR bootsector is ALREADY "good" .

My post wasn't aimed specifically to your utility, but since we talked here:
http://www.911cd.net/forums//index.php?sho...1702&st=129
of this problem, I thought appropriate to add the info here.

On the other hand, knowing how to patch a "standard" bootsector is a kind of info that could be useful even to users of your utility that want to "tweak" the result, just like the "HP patch" for the "standard" 2K/XP MBR:
http://www.boot-land.net/forums/index.php?...=2246&st=15

You know my usual critical approach/rantings to otherwise very nice and useful tool like yours : the actual lack of documentation on exactly WHAT the "nice tool" does and WHY it does it, that may provoke hiding knowledge...:
http://www.msfn.org/board/index.php?showtopic=133309

jaclaz

tl;dr

just take the purple pill

@all

New version of my 'Bootable USB-Drive Utility' available (v1.7.2)
-> Info's & download link for the new version in the first post

fuwi

9Aug2009
Greetings.
I discovered your AWESOME utility yesterday. THANKS.
I would like to submit for your consideration
adding a menu item to launch Parted Magic (PM) ...
PM files on a USB stick are all under one folder in the root.
It seems to me that maybe one could copy the PM-USB folder
to the USB stick after using your utility to put BartPE on the stick
(or maybe you could integrate adding PM to your utility ...) .
I hope maybe this seems like a good idea & not too much work ...
Thanks again.
Regards,
AEN
Æ

You can run the .iso allright:
http://www.911cd.net/forums//index.php?sho...1702&st=189

jaclaz

13August2009
Greetings.
Thanks for the reply.

1)
I'm not having any success ... yet.
For the time being I only have access to PM3.7 & PM4.3 isos and PM43usb.
I have tried Fuwi's original 9Apr09 menu mod &
subsequent 14Apr09 menu mod.
I have the PM4.3 iso in a pmagic directory off the root.

On the screen now (& for the last half hour) is»
(hd0,0)
Filesystem type is iso9660, using whole disk
[Linux-bzimage, setup=0x2e00, size=0x3d23b0]
[Linux-initrd @ 0x39fb3000, 0x65545 bytes]
Probing EDD (edd=off to disable) ... _

It's not clear to me if this method should only work with PM4.0 or not?
I would also like to ask/know if it matters
if one names the iso pmagic-4.3.iso or pm43.iso?
and makes the menu command
find --set-root /pmagic/pm43.iso
map --mem /pmagic/pm43.iso (hd32)?
I've tried both. Neither work for me.

2)
It is also not clear to me what the point/use of the KickerCD.iso is.
I copied it off the USB stick and PM still loads/run fine.
What was/is the resolution of the following post/question?

I've not found any post/reply directly to the point.

Any helpful replies/insights appreciated.
Thank you.
Regards,
AEN
Æ

@AEN

Which version of my Bootable USB-Drive Utility are you using?

-> just tried out to setup Parted Magic 4.4 on a USB-Stick (created with the latest version of my Bootable USB-Drive Utility) -> works like a charme!

Steps:
- go to http://sourceforge.net/projects/partedmagic/files/
- download pmagic-usb-4.4.zip
- unzip pmagic-usb-4.4.zip and copy the complete folder 'pmagic' to the root of the USB-Stick
- add this to the menu.lst (or better to menu2.lst, if your stick is created with a newer version of my Bootable USB-Drive Utility -> strongly recommended ):

ISO-boot works also:
- download pmagic-4.4.iso.zip from the link above
- unzip and copy pmagic-4.4.iso to the 'pmagic'-folder on the USB-Stick
- add this to the menu.lst (or menu2.lst):



The WinPE_Kicker-CD.iso has nothing to do with Parted Magic, it speeds up the loading of BartPE, if you choose 'Kick-Boot BartPE (fast)' in the bootmenu.
Further, you can create a bootable CD with WinPE_Kicker-CD.iso. Together with the USB-Stick, you can boot BartPE (only BartPE, not Parted Magic nor the
other tools on the Stick) on systems, on which USB-Booting is not supported (the Kicker-CD is booted first, after a short time, the remaining boot process is
passed to the USB-Stick, and the CD can be ejected).
Note: after every Update of the Stick you have to execute the Create_WinPE_Kicker-CD.iso.cmd to create a new WinPE_Kicker-CD.iso (and burn a new CD)
else you can have curious effects in BartPE!
And: the Boot-CD works only together with that USB-Stick, on which the WinPE_Kicker-CD.iso was created! With an other Stick you get a bluescreen!


No!
This technique works only with a disk-image for the first part, and a real harddrive for the remaining part of the boot process.
The disk-image and the real harddrive (the USB-Stick in this case) must have the same signature, so it can not work with a CD,
a CD has not a disk-signatur.


BTW: all what i said for USB-Sticks is also true for USB-Harddrives, they work similar.

fuwi