It supports direct mappping of noncontinuous files.
For more info (you may like Google Translate):Installation:
1, Boot from harddisk
copy buldr and buldr.mbr to C:\, create burg boot menu using boot.ini or bcdedit.
Then, download resource package and extract to C:\
http://grub4dos.sour...et/bucfg_v1.zip
bucfg is a fb archive, you can use it as a whole or extract its content to C:\
2, Boot from fbinst
Use fbinst to format a flash drive, add buldr to fb hidden partition. Then, download resource package from the above url, copy bucfg to data partition or extract its content to fb hidden partition, for example:
Code: [Select]
fbinst DISK format -e 8m
fbinst DISK add buldr buldr
fbinst DISK load bucfg
Command usage:
1. Direct map:
map (hd0,1)/floppy.img (fd0)
It supports noncontinuous file.
2, Map to memory:
map --mem (hd0,1)/floppy.img (fd0)
Since burg need memory for its own operation. The memory allocated to map command can be calculated using the following formula:
When M < 256: 1/2 M
When M >= 256: M - 128m
3, Remove a mapping:
map -r (fd0)
4, Remove all mappings:
map -R
5. Show map status:
map
In BURG, you can use device (map0), (map128), etc, to access the map drive, no need for --hook option.
6, Boot image
map --mem (hd0,1)/floppy.img (fd0)
set root=(map0)
chainloader +1
boot
It can be simplified as (more about the --set option later):
map --set --mem (hd0,1)/floppy.img (fd0)
chainloader +1
boot
7, Insert drive
map --insert (hd0,1)/disk.dsk (hd0)
After using --insert, the map drive becomes (hd0), and the original hard disk shift by one, so (hd0)->(hd1), (hd1)->(hd2). Without --insert, the new drive will replace (hd0).
Please note that the behavior described above happens after boot. Inside BURG, (hd0) is still (hd0) and the new map drive can be accessed using (map128).
8, Write protect
You can add --rdonly option to indicate the map drive is read-only:
map --rdonly (hd0,1)/disk.dsk (hd0)
9, Embedded map
You can map files inside another (map) device, for example:
map (hd0,1)/disk.dsk (hd0)
map (map128)/floppy.img (fd0)
However, there is a small limitation about file continuity when using embedded map:
Old drive direct map Old drive memory map
New drive direct map no limit file must be continuous
New drive memory map no limit no limit
10, Map iso file
map (hd0,1)/aa.iso (cd96)
or
map --mem (hd0,1)/aa.iso (cd96)
The corresponding map device is (map224), since bios number is 96 + 128 = 224.
11. Show iso boot catalog:
cdinfo (map224)
12. For iso that has emulated floppy/harddisk, you can use map to boot it, for example:
map (hd0,1)/aa.iso (cd96)
map --image=0 (map224) (fd0)
set root=(map0)
chainloader +1
boot
Option --image=0 select the image from boot catalog. The index for multiple boot iso can be shown using cdinfo command.
13, For noemu iso file, you can use cdload to boot it, for example:
map (hd0,1)/aa.iso (cd96)
cdload --image=0 (map224)
boot
14, You can also use cdload to chainload some boot file directly, for example:
map (hd0,1)/aa.iso (cd96)
cdload (map224)/grldr
boot
map (hd0,1)/aa.iso (cd96)
cdload (map224)/isolinux.bin
boot
map (hd0,1)/aa.iso (cd96)
cdload (map224)/bucd.bin
boot
The cd boot file for BURG is generated using the this command:
cat cdboot.bin core.img > bucd.bin
cdload can also load files from real cdrom, for example:
cdload (hd96)/isolinux.bin
boot
15, Set variable
You can use --set to assign the newly map drive to a variable, for example:
map --set (hd0,1)/aa.iso (cd96)
cdload --image=0 ($root)
boot
map --set=maproot (hd0,1)/aa.iso (cd96)
echo map device is $maproot
If the variable name is skipped, it would use root.
16, dd command
The option for dd is --if, --of, --bs, --seek, --skip, --count and --str. --str is used to write a string to output file, while the other options are the same as the dd command from linux, for example:
dd --if=(hd0,1)/aa --of=(hd0,1)/bb --bs=512 --count=1
dd --str=HELLO --of=(hd0,1)/bb --seek=32
http://www.burgloade...php?topic=101.0
More info about the menu system:
https://help.ubuntu.com/community/Burg