Help - Search - Members - Calendar
Full Version: Bartpe and CDFS on USB stick
The CD Forum > Bart's PE Builder > USB Booting
Pages: 1, 2
knoks
QUOTE (fuwi @ Jan 26 2012, 04:31 PM) *
sorry, i have overwritten knoks original post... blush.gif

How could this happen? I had thought, only the original poster can edit his own post. confused1.gif

@jaclaz
I have a SMI based USB-Stick and use the tool: "SMI_UFDiskUtilities.exe" to create a CDFS-Partition on this stick. One can copy a BartPE .iso to the CDFS-Partition and boot this partition (but only if the BIOS can handle USB-Sticks). Therefore I seek for a method to boot the stick with a kicker-CD if the BIOS don't see USB-Sticks.

BartPE on a CDFS-Partition has the advantage that a Kaspersky-AV Plugin can update his virus database (on a FAT32 or NTFS partition this don't work). Furthermore i have the impression that the boot from a CDFS partition is faster than FAT32/NTFS.
Ed_P
QUOTE (knoks @ Jan 26 2012, 03:40 PM) *
How could this happen? I had thought, only the original poster can edit his own post. confused1.gif

Mods can also.

FWIW I have two U3 USB sticks which I boot BartPE from, and not from the U3 CD drive. One stick is formated NTFS, required for large files, and one FAT32, which boots everywhere, once the LBA format option was used.

QUOTE
BartPE on a CDFS-Partition has the advantage that a Kaspersky-AV Plugin can update his virus database (on a FAT32 or NTFS partition this don't work).

That makes no sense. How can a non-writable device be more conductive to updating than a writable device? hmm.gif

QUOTE
Furthermore i have the impression that the boot from a CDFS partition is faster than FAT32/NTFS.

How about if you boot a BartPE ISO from a FAT32 drive?
jaclaz
knoks,
this thingy (if it will EVER work) is not going to be a "matter of a few posts". ph34r.gif

If you are OK with it (just post so) I would move the issue to a new thread.

In the meantime, take some time checking these three threads (though seemingly "random" w00t.gif they do contain some ideas/info that may be of use):
http://www.911cd.net/forums//index.php?showtopic=19663
http://reboot.pro/9916/
http://reboot.pro/3765/

(besides the "main" XP Kansas City Shuffle one):
http://www.911cd.net/forums//index.php?showtopic=21242

The original method works because Hard Disk devices do have a "unique" signature in the MBR (and a checksum is performed) in the MBR, and the Windows NT booting mechanism relies on these to identify the boot device.

What you propose would be "new terrain to explore", but maybe, just maybe, it is possible to port the method to CD-ROM like devices. unsure.gif

An interesting thing to experiment would be to make a few tests with an El-Torito Hard Disk emulation image.
Useful info about that here:
http://reboot.pro/3890/
http://reboot.pro/3890/page__st__6
http://reboot.pro/3890/page__st__46

cheers.gif
jaclaz
knoks
@jaclaz
open a new thread is ok.

QUOTE (Ed_P @ Jan 27 2012, 03:43 AM) *
That makes no sense. How can a non-writable device be more conductive to updating than a writable device? hmm.gif

The updates are stored in RAM-Disk. It seems Kaspersky prevents update of the database in case of a trial version. But the CD based trial version can make updates. See Attachment.

I also made some benchmark tests with the different boot methods:

T1: Time to build the media (burn CD / copy files to Stick / extract .iso to CDFS).
T2: Time to boot the media until the XPE login password.
T3: Time from XPE login password until finish.

Time format is minutes:seconds
----------------------------------------
Media ......| T1 ..| T2 ..| T3 ..|T2+T3|
------------|------|------|------|-----|
DVD-RW..4X..| 5:37 | 4:53 | 3:57 | 8:50|
DVD-ROM 16X | 3:06 | 4:14 | 4:12 | 8:26|
FAT32-Stick |18:31 | 2:59 | 2:25 | 5:27|
NTFS-Stick .|15:00 | 1:33 | 1:59 | 3:32|
CDFS-Stick .| 2:38 | 0:55 | 1:13 | 2:08|
----------------------------------------

This data is based on a 1,56 GB BartPE .iso.
Using the CDFS-Format is the fastest in build and boot BartPE. Furthermore CDFS is always write protected, FBWF works and there are no problems with the file designation minint instead of i386.
The only problem ist that the CDFS-Stick will not boot if the BIOS don't see the stick.
jaclaz
My guess (mind you NOT what you asked for) is that the "normal" NTFS times can be shortened, see:
http://www.911cd.net/forums//index.php?sho...40&start=40
http://www.911cd.net/forums//index.php?sho...21702&st=63
http://www.911cd.net/forums//index.php?sho...21702&st=70
(or the times you mentioned are with already optimized builds? unsure.gif)

Also the 15 minutes to build the NTFS stick seems a bit too much, at first sight, JFYI:
http://www.msfn.org/board/topic/125116-fat...d-on-usb-stick/

This said, back to work.
The hard disk emulation mode for the CD-like device (that seems to me the most promising approach) won't probably fulfill your write protect issues dubbio.gif, but it is IMHO still worth a try.

If it doesn't work:
Boot (on a machine that allows it) that USB thingy "as is".
Export/save/whatever the whole HKLM\SYSTEM\MountedDevices

Remove info for all other devices BUT the CD-like USB stick LUN, and post it.
This is the other thread with Andy07 experience:
http://www.911cd.net/forums//index.php?showtopic=21682
(not actually SAME issue, but maybe containing some useful info).

cheers.gif
jaclaz
knoks
QUOTE (jaclaz @ Jan 27 2012, 08:36 PM) *
(or the times you mentioned are with already optimized builds? unsure.gif)

I use Fuwi's USB-Drive Utility without any changes.

QUOTE (jaclaz @ Jan 27 2012, 08:36 PM) *
The hard disk emulation mode for the CD-like device

I have no idea what a "hard disk emulation mode" is. But the Attachment contain the registry export from MountedDevices. The CDFS Partition of the stick has drive letter X:. The corresponding Volume ID is {dc9a4571-4b45-11e1-be7f-806d6172696f}. The NTFS partition of the stick has drive letter P:.

Maybe it would help me if i understand Fuwi's Kicker-CD. How redirects the the CD the boot process to the stick after the driver for the USB stick are loaded?
knoks
Some more informations how to build a cdfs stick:
http://blog.usboffice.kr/?p=146

To find out wich usb stick has the necessary Verdor-ID, look here:
http://flashboot.ru/index.php?name=iflash&pagenum=1

Here is another forum to discuss cdfs Stick solutions:
http://reboot.pro/15475/page__p__138146#entry138146
jaclaz
QUOTE (knoks @ Jan 30 2012, 05:25 PM) *
Maybe it would help me if i understand Fuwi's Kicker-CD. How redirects the the CD the boot process to the stick after the driver for the USB stick are loaded?

The main related thread is this one:
http://www.911cd.net/forums//index.php?showtopic=21242
the method is called either "XP Kansas City Shuffle" or "Fake Signature" method. (with these keywords you may be able to find morethreads/posts discussing it).

It essentially needs a Disk Signature to work, and since only a harddisk-like device has a signature, I thought that maybe it can work with a hard disk emulation CD (which does have a Disk Signature).

Right now the device has:
QUOTE
"\\DosDevices\\X:"=hex:5c,00,3f,00,3f,00,5c,00,55,00,53,00,42,00,53,00,54,00,\
4f,00,52,00,23,00,43,00,64,00,52,00,6f,00,6d,00,26,00,56,00,65,00,6e,00,5f,\
00,46,00,6c,00,61,00,73,00,68,00,26,00,50,00,72,00,6f,00,64,00,5f,00,44,00,\
72,00,69,00,76,00,65,00,5f,00,53,00,4d,00,5f,00,55,00,53,00,42,00,32,00,30,\
00,26,00,52,00,65,00,76,00,5f,00,31,00,31,00,30,00,30,00,23,00,41,00,41,00,\
30,00,34,00,30,00,31,00,32,00,37,00,30,00,30,00,30,00,31,00,30,00,33,00,32,\
00,34,00,26,00,30,00,23,00,7b,00,35,00,33,00,66,00,35,00,36,00,33,00,30,00,\
64,00,2d,00,62,00,36,00,62,00,66,00,2d,00,31,00,31,00,64,00,30,00,2d,00,39,\
00,34,00,66,00,32,00,2d,00,30,00,30,00,61,00,30,00,63,00,39,00,31,00,65,00,\
66,00,62,00,38,00,62,00,7d,00


Which "translates" to:
CODE
USBSTOR#CdRom&Ven_Flash&Prod_Drive_SM_USB20&Rev_1100#AA04012700010324&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}


Cannot say if it is possible to somehow make a "kicker" for this.

Most probably some info/ideas can be found in this (seemingly UNrelated) project:
http://reboot.pro/3890/
which does use hard disk emulation CD, but your mileage may vary. ph34r.gif

cheers.gif
jaclaz
cdob
QUOTE (knoks @ Jan 26 2012, 09:40 PM) *
Therefore I seek for a method to boot the stick with a kicker-CD if the BIOS don't see USB-Sticks.

The kicker feature works out of the box. That's default booting at a BartPE CD already.
Core boot load drivers at textmode. Next CD drives are initilized and BartPE is redetected.
By default the same CD drive kicks in. In addition this can be another (USB)(fake) CD drive.

Kicker-CD: create a BartPE valid at textmode only.

X:\temp\usb_bartpe
QUOTE
\grldr
\menu.lst
\pebuilder.iso
Use the equal pebuilder.iso as for fake CD drive.

menu.lst
CODE
default 0
timeout 0

# grub4dos-chenall
# http://code.google.com/p/grub4dos-chenall/downloads/list

title BartPE
set ISO=/pebuilder.iso
cat --length=0 %ISO% > nul || find --set-root --devices=hf %ISO%
map %ISO% (222)
map --hook
chainloader (222)/I386/SETUPLDR.BIN


CODE
mkisofs.exe -iso-level 4 -r -b grldr -hide boot.catalog -no-emul-boot -boot-load-size 4 -o bartpe_kick.iso X:/temp/usb_bartpe


Do not include a ISO file driver, like firadisk or firadisk.
This CD is valid at textmode: read BSOD 0x7b stand alone.
A addional USB BartPE CD is found by default, booting continues from CD drive.
Try the approach with a fake USB BartPE CD.
knoks
@cdob
I am not sure, i understood your suggestion. I tryed the following:
1. I create the folder "temp\usb_bartpe" within the addon folder and put in the recomended files: grldr, menu.lst and pebuilder.iso.
2. Start the PE-Builder to create a new iso image (no plugins or additional drivers are present).
3. Your mkisofs-code produces the following error message:
mkisofs: No such file or directory. Invalid node - X:/temp/usb_bartpe
This is because the the output from PE builder is .\BartPE.
4. Therefore i try the following mkisofs code:
mkisofs.exe -iso-level 4 -r -b grldr -hide boot.catalog -no-emul-boot -boot-load-size 4 -o bartpe_kick.iso F:\Bart-PE\Kicker-CD\BartPE
This produce a bootable BartPE cd which boots until a startnet.cmd error (missing file).

But i have a new idea:
What about a bootable DOS disk or cd which contains grub for dos. The missing usb drivers must be pressent and start within CONFIG.SYS.
cdob
QUOTE (knoks @ Feb 29 2012, 10:12 PM) *
1. I create the folder "temp\usb_bartpe" within the addon folder

Which addon folder do you use?

A full path X:\temp\usb_bartpe was recommeded as temporarily work space.
You may use another drive letter. c:\temp\usb_bartpe
Or use any folder you like.

QUOTE
2. Start the PE-Builder to create a new iso image (no plugins or additional drivers are present).

Do not run PEBuilder.

QUOTE
3. Your mkisofs-code produces the following error message:
Well, mkiosofs dosn't find given folder. The path dosn't exist.
If you choose a own full path, then adjust the command line. Set choosen folder.

QUOTE
But i have a new idea:
What about a bootable DOS disk or cd which contains grub for dos. The missing usb drivers must be pressent and start within CONFIG.SYS.
Why does DOS require USB drivers?
knoks
QUOTE (cdob @ Mar 1 2012, 09:41 AM) *
Which addon folder do you use?

I use a foulder named addon as custom foulder (see appendix).
QUOTE
Do not run PEBuilder.

What else should i do with X:\temp\usb_bartpe?
QUOTE
Why does DOS require USB drivers?

I think about a bootable DOS CD or Floppy. Because DOS don't know USB devices one need the appropriate USB-driver for DOS. After the bootable DOS medium see the USB devices one can use grub4dos to boot from that USB device.
cdob
QUOTE (knoks @ Mar 1 2012, 02:08 PM) *
What else should i do with X:\temp\usb_bartpe?
Copy listed files to this folder. Create a kicker ISO image from this files.

QUOTE
After the bootable DOS medium see the USB devices one can use grub4dos to boot from that USB device.
I doubt this approach.
knoks
I have download the newest grub4dos-0.4.6a and store the containing grldr together with your menu.lst and the pebuilder.iso into a folder C:\CDFS_Kicker.
Then i execute the following command:
mkisofs.exe -iso-level 4 -r -b grldr -hide boot.catalog -no-emul-boot -boot-load-size 4 -o bartpe_kick.iso C:\CDFS_Kicker
The .iso creation finished without errors. Burning pebuilder.iso to a DVD and boot from it produces the following error:
CODE
Booting BartPE
cat --length=0 %ISO% > nul || find --set-root --devices=hf %ISO%
Error 27: Unrecognized Command
Press any key to continue

I also tryed to create a kicker DVD with fuwi's _PeBootKickerCdCreator.cmd. I changed the mkisofs command within the script to the mkisofs command above. The _PeBootKickerCdCreator.cmd ask me for the driveletter of the PE stick. But the _PeBootKickerCdCreator.cmd don't accept a CDFS stick (only FAT32 and NTFS sticks are allowed).

Any Idea?
cdob
QUOTE (knoks @ Mar 2 2012, 07:35 PM) *
I have download the newest grub4dos-0.4.6a
Never ever write the latest or newest. Name the full version, this includes date.

QUOTE
Error 27: Unrecognized Command

Change timeout: timeout 10
Build a new DVD.
Boot to grub4dos, press c to command line. Enter line by line.

Which pebuilder.iso do you use?
Ed_P
QUOTE (knoks @ Mar 2 2012, 01:35 PM) *
But the _PeBootKickerCdCreator.cmd don't accept a CDFS stick (only FAT32 and NTFS sticks are allowed).

What's wrong with using the writable portion of the U3 USB stick? I have 2 U3 USB sticks which are bootable and load BartPE and various ISOs. And both still also run U3.
knoks
@cdob
Grub4dos do not know the "set" command. I changed your menu.lst:
CODE
default 0
timeout 10

# grub4dos-chenall
# http://code.google.com/p/grub4dos-chenall/downloads/list

title BartPE
cat --length=0 /pebuilder.iso > nul || find --set-root --devices=hf /pebuilder.iso
map /pebuilder.iso (222)
map --hook
chainloader (222)/I386/SETUPLDR.BIN

But now the "cat" command produce the follewing error:
ERROR 1: Filename must be either an absolute pathname ore blocklist
That is curios because /pebuilder.iso is a absolute pathname.

Furthermore i made a bootable floppy with the usb cdrom drivers for DOS. Now i can access the CDFS partition of the usb stick out of DOS. For USB DOS drivers look here:
http://www.bootdisk.com/usb.htm

But grub4dos do not see any CD-ROM device. I use the following config.sys:
CODE
DEVICE=DISPLAY.SYS CON=(EGA,,1)
device=usbaspi.sys
device=cdrom.sys /D:CD1
device=usbcd.sys /D:CD2
device=grub.exe

A "chainloader (cd0)" command produce the error message:
Error 23: Error while parsing number

A "cdrom --init" command respond with:
No CD-ROMs found.

If i start grub.exe manually after boot then i get the error mesage:
Failure restore ROM INT 0x09 vector. Unsupported DOS, devicedriver or TSR

@Ed_P
1. CDFS is faster
2. I need a 100% write protected solution, because of virus infection.
3. There is no problem with the folder minint insted of i386.
4. Some plugins work only within a CD.
cdob
QUOTE (knoks @ Mar 4 2012, 07:00 PM) *
Grub4dos do not know the "set" command.
A current grub4dos-chenall does support "set" command.
Which grub4dos version do you use? Name full version including date.

QUOTE
But now the "cat" command produce the follewing error:
ERROR 1: Filename must be either an absolute pathname ore blocklist
No idea.
Which hardware do you use?
Which BIOS do you use?
Which boot device do you use?

QUOTE
That is curios because /pebuilder.iso is a absolute pathname.
No, it's not a absolute pathname. Device is missing.
Try ()/pebuilder.iso

QUOTE
Furthermore i made a bootable floppy with the usb cdrom drivers for DOS.
But grub4dos do not see any CD-ROM device.

Grub4dos is a boot loader. And dosn't use OS drivers. No USB DOS drivers are used.
Ed_P
QUOTE (knoks @ Mar 4 2012, 01:00 PM) *
@Ed_P
1. CDFS is faster

I find that hard to believe. The chip set is the same for the whole USB drive. The U3 system partitions them to two different formats but they're the same chips thus the same speed.

QUOTE
4. Some plugins work only within a CD.

I have not encountered that situation in my systems.
knoks
@cdob
The pebuilder-kicker CD work now. Until the black screen with the progressbar the computer boots from CD/DVD. After that booting will continued from CDFS stick. Thank you! celebrate3.gif

I use the Grub4DOS version 0.4.6.a from 2012/2/27
Is it necessary to put the same pebuilder.iso on the kicker CD as extrakted to the CDFS partition on the USB stick? Because that iso is very big (3,6GB). Or is it possible to use a smaler pebuilder.iso (without any plugin) for the kicker CD.

@Ed_P
QUOTE (Ed_P @ Mar 4 2012, 10:50 PM) *
I find that hard to believe.

you are not dependent on it to believe, you can test it. I use a stick with a SMI controller chip. For this stick i have made benchmark tests (see post #4). Maybe this results vary for other sticks.
Ed_P
QUOTE (knoks @ Mar 5 2012, 02:38 PM) *
@Ed_P
QUOTE (Ed_P @ Mar 4 2012, 10:50 PM) *
I find that hard to believe.

you are not dependent on it to believe, you can test it. I use a stick with a SMI controller chip. For this stick i have made benchmark tests (see post #4). Maybe this results vary for other sticks.

OMG!! blush.gif So you did. And with dramatic speed differences. ohmy.gif I wonder how that can be. hmm.gif

Thanks for pointing out that prior post.
cdob
QUOTE (knoks @ Mar 5 2012, 08:38 PM) *
The pebuilder-kicker CD work now.
Congratulations. I'm curious: which part did you changed recently?

QUOTE
Is it necessary to put the same pebuilder.iso on the kicker CD as extrakted to the CDFS partition on the USB stick?
I doubt this. Core boot files are about 10mb to 20mb data.

QUOTE
Because that iso is very big (3,6GB).
Which big files do you add?
How do you build the ISO image? Post the mkisofs command line.

QUOTE
Or is it possible to use a smaler pebuilder.iso (without any plugin) for the kicker CD.

I wonder: is the same file system required? Are two different file systems possible at kicker ISO and fake USB CD drive?

Can you try:
Run pebuilder. Create a new big ISO image. Write this to fake USB drive.
Delete Programs directrory. Build another ISO image. Write this to a kicker CD/DVD.
Can you boot?
knoks
At time i have a problem with further tests. I sold my 4GB stick: "SuperTalent Pico C" and buy a new stick with 8GB (same model). But the SMI_UFDiskUtilitie dont work with the 8GB Stick. The 8GB stick has the same vendor and produkt id as the 4GB stick (VID=090C, PID= 1000). How can this be?
Does someone know a stick that work 100% with any of the MP-Tools from SMI, USBest or Phison?
jaclaz
QUOTE (knoks @ Mar 11 2012, 09:22 PM) *
At time i have a problem with further tests. I sold my 4GB stick: "SuperTalent Pico C" and buy a new stick with 8GB (same model). But the SMI_UFDiskUtilitie dont work with the 8GB Stick. The 8GB stick has the same vendor and produkt id as the 4GB stick (VID=090C, PID= 1000). How can this be?
Does someone know a stick that work 100% with any of the MP-Tools from SMI, USBest or Phison?

You are seemingly playing the game reversing it's Rules w00t.gif which are conventionally established as:
  1. You get a stick.
  2. You find the suitable tool for the stick you got.


The VID/PID is usually connected to the stick BRAND (in your case SuperTalent).
A same brand may use, EVEN on EXACTLY the SAME model, different chips from different manufacturers.
Some "low end" brands will leave VID&PID of the chip manufacturer, "bigger" ones will change them to their own.

Additionally a given utility may work with a given controller from a given manufacturer, but may not work with another (newer) model from the same manufacturer)

In other words VID&PID are sometimes a very good indicator, but sometimes they are meaningless.


What EXACTLY does Chipgenius report on that particular stick?

http://reboot.pro/4661/


If you check here:
http://flashboot.ru/index.php?name=iflash
you will find how there is at least a report of the supertalent pico C 4Gb having a SMI325 and of a pico C 8 Gb having the SMI321, and one having the SM325AC/SM321U.

So, it seems like they all use SMI chips, and possibly you need to update the Manufacturer tool, but you can never say for sure, for the reasons previously stated.

jaclaz
knoks
@jaclaz
I put the Chipgenius output in the Attachment. The first picture is from the 4GB stick, the second one from the 8GB stick. It seems the only difference is the Serial Number. The 8BG stick is also slower (sequential read 17MB/sec). The 4GB stick has had 30MB/sec.
According to this Blog: http://blog.usboffice.kr/?p=146 all sticks with a VID=090C should work with the SMI UFD utility. I use version 1.0.0.2 of the SMI UFD utility. please let me know If there is a newer version.
jaclaz
QUOTE (knoks @ Mar 12 2012, 02:17 PM) *
I use version 1.0.0.2 of the SMI UFD utility. please let me know If there is a newer version.

Sure, that is seemingly an oldish version.

Latest available is v2.03.49 or 1.17.47 (depending on the one you are using):
http://flashboot.ru/index.php?name=Files&a...p=cat&id=10

also, do not trust too much version numbering and/or "assume" that a later one is better than an earlier one, sometimes settings/info/docs can be found in older verisons....

Additionally to the above do check the links that Chipgenius outputs.

It's "strange" that it provides two different references:
http://bbs.mydigit.cn/read.php?tid=4345
http://dl.mydigit.net/special/up/smi.html

cheers.gif
jaclaz

cdob
Create a sorted BartPE: mkISO_BartPE_sort.cmd
Core boot files are sorted in front of media.File

Used external applications:
mkisofs.exe : http://cdrecord.berlios.de http://www.student.tugraz.at/thomas.plank/
dd.exe : http://www.chrysocome.net/dd
gsar.exe : http://home.online.no/~tjaberg
Add applications yourself.

Assumption: Required BartPE files are uppercased already.
Use PeBuilder at ISO output or
InfCacheBuild.exe with filecase.ini.


There are different approaches to use this feature:

1 From a real CD to fake USB CD drive

CODE
mkISO_BartPE_sort.cmd -core-iso C:\PEBuilder\OutDir


There are two files created: BartPE.iso and BartPE.iso.core.iso
Write BartPE.iso to fake USB CD drive.

Load BartPE.iso.core.iso with grub4dos.
Add BartPE.iso.core.iso to data partition at USB drive

Or add to a real CD. Use directory C:\temp\bartpe_cd_kick
QUOTE
\grldr
\menu.lst
\BartPE.iso.core.iso


CODE
title BartPE kicker ISO image to CD\nchainboot CD drive
#small ISO file load
set ISO=/BartPE.iso.core.iso
cat --length=0 %ISO% > nul || find --set-root --devices=hcf %ISO%
map --mem %ISO% (222)
map --hook
chainloader (222)/I386/SETUPLDR.BIN
boot


CODE
mkisofs.exe -iso-level 4 -r -b grldr -hide boot.catalog -no-emul-boot -boot-load-size 4 -o BartPE_kick.iso C:/temp/usb_bartpe

Write BartPE_kick.iso to a CD.



2 From a real CD to the same CD drive
Especiacl laptop drives require long access times. This delays reading files.
Textmode part is loaded to RAM first.
It's faster to read a block of data to RAM and read files from RAM disk.

Copy grldr and menu.lst to BartPE output directory: C:\PEBuilder\OutDir

menu.lst
CODE
color blue/green yellow/red white/magenta white/magenta
timeout 10
default 0

#BartPE CD - fast textmode boot

# grub4dos-chenall
# http://code.google.com/p/grub4dos-chenall/downloads/list

title BartPE Chain CD \nchainboot itself
#ISO image created by mkISO_BartPE_sort.cmd
#RAM load about 10-20mb data
#() CD current boot device
command ()/RAMBOOT.LST
echo CD sectors %CDsec%
map --mem ()+%CDsec% (222)
map --hook
root (222)
chainloader /I386/SETUPLDR.BIN

title plain BartPE
chainloader /I386/SETUPLDR.BIN


CODE
mkISO_BartPE_sort.cmd -r -b grldr C:\PEBuilder\OutDir



In addition:
add data from another directory c:\add
CODE
mkISO_BartPE_sort.cmd -r -b grldr C:\PEBuilder\OutDir c:\add


or redirected to a given directory at CD
CODE
mkISO_BartPE_sort.cmd -r -b grldr -graft-points C:\PEBuilder\OutDir "/Programs/=C:/Programs"

knoks
Since the "UFDisk Utilitie" don't work anymore for my new USB-Sticks i use the MP-Tool: sm32Xtest_V58-8.exe. But this tool is much more complex then the UFDisk utillitie. I scan for USB devices (F5) and find my USB-Stick with controller chip: SM3254AE.
Then i klick on Settings (the login password is always "320") and chose the default.ini.
Within Multi-lun-Settings one can define a CDROM partition. But i don't know how to define a iso-image for this partition. After a klick on OK nothing happens. A Klick on Start in the main menu produces the error: Preset File Can't be found!
Can anyone explain how this tool works?
jaclaz
Where exactly you got that tool?
You need to find one of the files that include the documentation (posibly inside an older version).

See if you can find anything of use here:
http://tagievara.narod.ru/pages/programs/flash/smi.html

I would try first the "SMI Update CDROM & Preload Tool" unsure.gif


Remember that some of these utilities if used incorrectly may render your stick UNusable and potentially UNrecoverable. ph34r.gif

cheers.gif
jaclaz
knoks
I got the tool from this site: http://flashboot.ru/index.php?name=Files&a...p=cat&id=10
I also find a documentation (not exactly for this version but similar). But i can't find how to load the iso-image to the CDROM partition. The documentation is to big for attachment (1,42MB).
The tool "SMI Update CDROM & Preload Tool" don't find my stick. The controller chip SM3254AE also is not listed for this tool.
jaclaz
QUOTE (knoks @ Jul 1 2012, 09:13 PM) *
The tool "SMI Update CDROM & Preload Tool" don't find my stick. The controller chip SM3254AE also is not listed for this tool.

This is actually good smile.gif .
You shouldn't even THINK of runnning any production tool with your stick actually connected, until you are perfectly familiar with the options. ph34r.gif
Since I have NO sticks connected and particularly noone with an SMI chip, I can do tests "safely".
The CDROM update tool mentioned has a lot of option "missing", so, if it is actually a CDROM update tool, the options you have actually active should be related to the CDROM update. unsure.gif
One of the remaining options is in the "first tab" of the settings (the one called "Main Flow Setting") and it is called "Make Auto Run", if you enable it, you will see that when you click on the "browse button" ... it is looking for a *.iso.
It is likely that that part is the relevant one, but of course NO GUARANTEE OF ANY KIND IMPLIED, your mileage may GREATLY vary.

BUT, try also, from the page I linked lately:
http://tagievara.narod.ru/pages/programs/flash/smi.html
the file:
SMI MPTool V2.03.34 v7 J1118 [SM3254AE] ; download; 2 026 240 bytes
(which IMHO represents a confirmation of the above hint wink.gif)

cheers.gif
jaclaz
CDROM-part
1) detect controller with ChipEasy v1.5.3 EN or ChipGenius v4.00.0025 RC3
(download from http://tagievara.narod.ru/pages/programs/flash.html


2) download tool for controller


3) settings and Start


PASS!
knoks
It works now. celebrate3.gif
jaclaz
QUOTE (knoks @ Jul 2 2012, 05:45 PM) *
It works now. celebrate3.gif

WHAT EXACTLY works? unsure.gif
I mean it would be nice if you could DETAIL, EXACTLY, WHAT you have done, with WHICH tool, and HOW to be successful.
(this way this thread could be useful to someone else besides you)

cheers.gif
jaclaz
CDROM-part
1) detect controller


2) download tool, open tool and check detect correct info


3) check Support memory chip in tool


4) options: write protect (this image for ~ SM3255- SM3257EN) and replase ISO


PS: Sorry for bad English (I am from Russia)
jaclaz
QUOTE (CDROM-part @ Jul 2 2012, 06:25 PM) *
PS: Sorry for bad English (I am from Russia)

Don't worry smile.gif, we do appreciate your contributions, help and insights thumbup.gif, the main thing is the will to communicate and exchange ideas, the English is just a "common ground" (I am from Italy and a large number of 911CD members are not "mother tongue" English).

cheers.gif
jaclaz
CDROM-part
If you have any questions with pendrive firmware - I am help Your

PS: I am the site administrator specified above flowers.gif
knoks
@cdob
I get a error when running your mkISO_BartPE_sort.cmd. Renaming mkisofs.exe to mymkisofs.exe and change mkisofs.exe to mymkisofs.exe within your script solved the problem.
Also the call: mkisofs.exe -iso-level 4 -r -b grldr -hide boot.catalog -no-emul-boot -boot-load-size 4 -o BartPE_kick.iso C:/temp/usb_bartpe
should use mymkisofs.exe.
With this modifications i can build a BartPE_kick.iso
But i have still problems with the set command within the menu.lst. The set command don't work to me. I use the grldr from Grub4Dos-0.4.4. If you use a other version let me know. Therfore i change %ISO% to /BartPE.iso.core.iso.
Booting the kick-CD work fine, but the handover to the USB-Stick result in a bluescreen Stop:0x0000007B.
Ed_P
QUOTE (knoks @ Jul 4 2012, 07:26 PM) *
I use the grldr from Grub4Dos-0.4.4. If you use a other version let me know.

Based on the link in the menu.lst he posted I suspect he is well beyond 0.4.4.
QUOTE (cdob @ Mar 18 2012, 08:39 AM) *
menu.lst
CODE
color blue/green yellow/red white/magenta white/magenta
timeout 10
default 0

#BartPE CD - fast textmode boot

# grub4dos-chenall
# http://code.google.com/p/grub4dos-chenall/downloads/list

jaclaz
Additionally a "0.4.4" version does not really "exist".
The commonly used (and WRONG, outdated and buggy) 0.4.4 version that most people use is the 0.4.4 2009-03-31.
If you want to use the 0.4.4, you should use at least the 0.4.4 2009-10-16.

But nowadays you should use latest NON-experimental release from Chenall:
http://code.google.com/p/grub4dos-chenall/downloads/list
In this moment it is 0.4.5c 2012-06-19
http://code.google.com/p/grub4dos-chenall/...mp;can=2&q=

cheers.gif
jaclaz
knoks
I tried several versions of grub from the recommended site: http://code.google.com/p/grub4dos-chenall/downloads/list
grub4dos-0.4.6a-2012-06-19 -> My NOD32 Antivirus believes to found a virus and prevent download.
grub4dos-0.4.5c-2012-06-19 -> Works to me. Also the set command work now. But the handover to the USB-Stick furthermore result in a bluescreen Stop:0x0000007B. I also tested the second methode suggested by cdob. I get the error "unknown command: command ()/RAMBOOT.LST". Also the variable %CDsec% is not defined.
cdob
QUOTE (knoks @ Jul 5 2012, 11:59 AM) *
I also tested the second methode suggested by cdob. I get the error "unknown command: command ()/RAMBOOT.LST". Also the variable %CDsec% is not defined.

Did you used mkISO_BartPE_sort.cmd to create the BartPE ISO image?
Does exist a file /RAMBOOT.LST at BartPE CD?

Be aware: menu.lst is a example relating: From a real CD to the same CD drive
You may have to adjust this at a CDFS on USB stick.
knoks
Yes i used mkISO_BartPE_sort.cmd. But this break with a error: boot sector file not found.
The RAMBOOT.LST exists within the PEBuilder\OutDir as well as bootsect.bin.
After that i tried mkisofs.exe -iso-level 4 -r -b grldr -hide boot.catalog -no-emul-boot -boot-load-size 4 -o BartPE_kick.iso C:/temp/usb_bartpe
which result with error "unknown command: command ()/RAMBOOT.LST" at boot from CD.
knoks
@cdob
The command: "mkISO_BartPE_sort.cmd -r -b grldr C:\PEBuilder\OutDir" work now.
I forgot to put grldr in the C:\PEBuilder\OutDir.
But this command creates only a BartPE.iso and no bartpe_kick.iso.
I burn this ISO to DVD and to the CDFS-Stick. Booting from DVD "BartPE Chain CD \nchainboot itself" is faster then "plain BartPE".
But the handover to the USB-Stick dont work. The PC boot from DVD to the end.
I also made some tests with your methode from post #9. I copy the pebuilder.iso to the CDFS-Stick. After that i load the pebuilder.iso with UltraISO an delete some unnessesary files.
Then i build a bartpe_kick.iso from this modified pebuilder-iso with the methode from post #9. But the handover to the USB-Stick results in BSOD Stop:0x0000007B.
It seems this methode work only if the bartpe_kick.iso use the original pebuilder.iso.
cdob
QUOTE (knoks @ Jul 7 2012, 02:54 PM) *
But this command creates only a BartPE.iso and no bartpe_kick.iso.

Did you add applications dd.exe and gsar.exe to search path?
Does protection software interfere?

QUOTE
I burn this ISO to DVD and to the CDFS-Stick. Booting from DVD "BartPE Chain CD \nchainboot itself" is faster then "plain BartPE".
But the handover to the USB-Stick dont work. The PC boot from DVD to the end.

Remove the DVD at end of textmode boot (black window). What happens next?

QUOTE
I also made some tests with your methode from post #9. I copy the pebuilder.iso to the CDFS-Stick. After that i load the pebuilder.iso with UltraISO an delete some unnessesary files.

As for testing purposes: suggestion was to use the pebuilder.iso twice.
PE booting may store CD files system in memory. Using two different ISO file systems is not tested.
Do not modify this file so far.

No idea, it this works at CDFS at USB stick at all. You have the testing hardware.
knoks
@cdob
your method 1 from post #27 work now. It was my mistake. I had stored the BartPE_kick.iso within the BartPE.iso by using UltraISO. The BartPE.iso must not be modified after the generation. Otherwise the kicker.iso don't work. The same applies to the method from post # 9.

knoks
I made the script Build-CDFS.cmd using part's of the wrapper.cmd. The script contains Sherpyas InfCacheBuilder and paragliders sortmenu.
The following files must be present within the BartPE folder:
dd.exe
gsar.exe
mkISO_BartPE_sort.cmd (from post #27)
Build-CDFS.cmd
mymkisofs.exe
sortmenu.exe
InfCacheBuild.exe

After the script has run two iso files reside within the BartPE folder: BartPE.iso and Starter-CD.iso.
To build a CDFS-Stick procede as follows:

1. Make a tmp folder within the BartPE directory.
2. copy menu.lst (from post #27) and grldr (from grub4dos-0.4.5c-2012-06-19) to this tmp folder.
3. Run pebuilder.exe (don't build a iso image)
4. Run Build-CDFS.cmd
5. Make the CDFS-Stick using the BartPE.iso and the apropriate MP-Tool for your stick.
6. Burn Starter-CD.iso to a CD-ROM (only if your pc don't see the Stick at boot time).

Build-CDFS.cmd
CODE
@echo off
rem ------------------ SETTINGS -----------------

set Kicker_ISO=Starter-CD.iso
set tmp_dir=F:\Bart-PE\CDFS\BartPE_Starter
set pedir=F:\Bart-PE\BartPE
set iso=BartPE.iso
set _volid=Notfall-Stick
set _sortfile=sort.txt
set _mkisofsexe=mymkisofs.exe
set _duponce=-duplicates-once
rem set _duponce=

rem low | normal | high | realtime | abovenormal | belownormal
rem set _mkisofspriority=belownormal
set _mkisofspriority=normal

rem Actions
set _runinfcache=yes
set _copyhives=yes
set _sortmenu=yes
set _setupisolinux=no
set _mkisofs=yes
set _kicker_CD=yes

rem ------------------ SETTINGS -----------------
:copyright
echo _
echo *******************************
echo Build Script for BartPE v1.1
echo Copyright (c) 2005 Sherpya
echo *******************************

echo _
echo [Active Actions for %_volid%]
if "%_runinfcache%" == "yes" ( echo : InfCacheBuilder and FileCase : )
if "%_copyhives%" == "yes" ( echo : Copy Hives for HD Install : )
if "%_setupisolinux%" == "yes" ( echo : Isolinux Setup : )
if "%_mkisofs%" == "yes" ( echo : Iso Creation : )
if "%_sortmenu%" == "yes" ( echo : Sortmenu required : )
echo _
echo Source directory: %pedir%
echo Destination iso file: %iso%

:main

if not "%_sortmenu%" == "yes" goto infcachebuild
echo _
echo [Calling sortmenu]
if not exist sortmenu.exe (
    echo  *** Missing sortmenu.exe executable, skipping...
    goto infcachebuild
)

sortmenu "%pedir%\Programs\nu2menu\nu2menu.xml" > nu2menu.xml
if errorlevel 1 (
    echo *** Menu generation failed, aborting build ...
    goto end
)
    
copy nu2menu.xml "%pedir%\Programs\nu2menu\nu2menu.xml"

:infcachebuild
if not "%_runinfcache%" == "yes" goto copyhives
echo _
echo [Calling InfCacheBuild]
if not exist InfCacheBuild.exe (
    echo  *** Missing InfCacheBuild.exe executable, skipping...
    goto copyhives
)

InfCacheBuild.exe "%pedir%"

if %errorlevel% == 2 (
    rem set _caseopt=-U -duplicates-once
    set _caseopt=-U
    echo filecase.ini found and processed correctly, adding -U option
)
    
:copyhives
if not "%_copyhives%" == "yes" goto mkisofs
if exist "%pedir%\Programs\peinst\" (
    echo _
    echo [Copying registry hives for hdinstall]
    ( copy /y "%pedir%\i386\system32\config\default" "%pedir%\Programs\peinst" >NUL: )
    ( copy /y "%pedir%\i386\system32\config\software" "%pedir%\Programs\peinst" >NUL: )
    echo Done
)

:isolinux
set _bootopt=-b bootsect.bin -boot-load-size 4 -no-emul-boot -hide bootsect.bin -hide boot.catalog
if not "%_setupisolinux%" == "yes" goto mkisofs
echo _
echo [Setup IsoLinux]
if not exist isolinux\ (
    echo  *** Missing isolinux directory, skipping...
    goto mkisofs
)
rem set _bootfile=isolinux/isolinux-debug.bin
set _bootfile=isolinux/isolinux.bin
set _bootopt=-b %_bootfile% -boot-load-size 4 -no-emul-boot -hide %_bootfile% -hide boot.catalog -boot-info-table

if not exist "%pedir%\isolinux\" ( md "%pedir%\isolinux" )
copy /y isolinux "%pedir%\isolinux"
echo Done

:mkisofs
if not "%_mkisofs%" == "yes" goto end
if not exist mkISO_BartPE_sort.cmd (
    echo *** Missing mkISO_BartPE_sort.cmd, skipping...
    goto end
)
call mkISO_BartPE_sort.cmd -volid %_volid% -core-iso %pedir%

:kicker
if not "%_kicker_CD%" == "yes" goto end
if not exist %tmp_dir%\menu.lst (
    echo Missing %tmp_dir%\menu.lst skipping...
    goto end
)
if not exist %tmp_dir%\grldr (
    echo Missing %tmp_dir%\grldr , skipping...
    goto end
)
if not exist %_mkisofsexe% (
    echo Missing %_mkisofsexe%, skipping...
    goto end
)
move /Y BartPE.iso.core.iso "%tmp_dir%\"
%_mkisofsexe% -iso-level 4 -r -b grldr -hide boot.catalog -no-emul-boot -boot-load-size 4 -o %Kicker_ISO% %tmp_dir%

:end
echo done
knoks
@CDROM-part
I have 2 questions:

1. I use the SMI-MP tool and try to create a security partition and a hidden partition (see attachment). But i don't know how to access this partitions.
2. I have a SuperTalent Pico-C Stick. ChipEasy tells me that the controller chip is a SM3254AE. I tryed all recommended MP-Tools but none work for me. Can it be that this stick is a fake?

Would it not a good idea to collect all informations about the controller chip of a USB-Sticks within a database. The database should contain the manufactur and model type of a stick, the controller chip and the date of buy. So one has current informations which controller chip is used within which stick.
jaclaz
QUOTE (knoks @ Jul 21 2012, 11:55 PM) *
Would it not a good idea to collect all informations about the controller chip of a USB-Sticks within a database. The database should contain the manufactur and model type of a stick, the controller chip and the date of buy. So one has current informations which controller chip is used within which stick.

It would be a very nice idea, though not entirely "new" whistling.gif (and unfortunately previous attempts have seemingly had NO or very few followers sad.gif, at least here on 911CD):
http://www.911cd.net/forums//index.php?showtopic=15776

Chipgenius is IMHO "better" than other utilities exactly because it contains a sort of database of this kind.

OT ph34r.gif, but not much wink.gif, the good guy at nirsoft, has created something "similar":
http://usbspeed.nirsoft.net/
maybe it could a good idea to contact Nir Sofer and ask him if he could add this type of info for future submissions to that database.

cheers.gif
jaclaz
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-2013 Invision Power Services, Inc.