[shamurshamur]

Is there any method to make bcdw menus nice ................similiar to menus by vesamenu.c32.

like background image,transparency....etc.

if you have made one for yourself can u provide it here?

Thanks in advance.

[Jotnar]

I don't think you can do that with BCDW. You can't do it with GRUB/GRUB4DOS either. At least you'll be able to use pngs with GRUB2. I'd stick with ISOLinux for now if you want a pretty menu unless there's some reason to use BCDW.

FYI...You can load both BCDW or GRUB4DOS from ISOLinux.

Cheers

[shamurshamur]

Jotnar, on Apr 15 2009, 10:19 AM, said:

I don't think you can do that with BCDW. You can't do it with GRUB/GRUB4DOS either. At least you'll be able to use pngs with GRUB2. I'd stick with ISOLinux for now if you want a pretty menu unless there's some reason to use BCDW.

FYI...You can load both BCDW or GRUB4DOS from ISOLinux.

Cheers

Problem is , i am booting two .iso files and three .img files from bcdw as a primary bootloader. ( also i have some linux distros but they can loaded directly by isolinux.bin so don't need bcdw there )


In the case of using isolinux.bin as the primary bootloader.
what i have tried till now is that i can load the bootsector file of bcdw ( ie loader.bin ) from isolinux.bin .
sequence is like this :

isolinux.bin <====> vesamenu.c32 <=====>isolinux.cfg
|
|
\/
loader.bin (bootsector file for bcdw )
|
|
\/
bcdw.bin <===>bcdw.ini
|
|
\/
bcdw menu


Now i have to go to the bcdw menu for loading these .iso and .img files.

Is there any way that i can skip the bcdw menu and directly loads .iso files by invoking bcdw.bin from isolinux.bin.

[Jotnar]

If you get the latest GRUB4DOS there is a workaround that I use. I'll post more detailed instructions this evening but here's the quick and dirty.

GRUB4DOS includes a file called grldr. This is the boot loader and it points to menu.lst by default (in a folder called BOOT if I remember correctly). What you can do is hex edit grldr and change the path to ISOLINUX/menu.lst. In doing so you can also change the name of the menu file. You then edit the menu.lst (or whatever you renamed it) file to boot your iso by default and set it to not show the GRUB menu. You'll need one copy of grldr and one menu.lst per each ISO you want to boot (this is why renaming menu.lst comes in handy...menu1.lst, menu2.lst...etc). You then make an ISOLinux entry for each of the grldr files and voila! you're good to go. Be aware that GRUB4DOS is case sensitive when you make your menu.lst files.

You should be able to boot your floppy images from ISOLinux using memdisk (my preferred method) but you can also load them from GRUB4DOS if you want. You can even zip up the .img files to save space. ISOLinux/Memdisk understands zip and gzip, GRUB4DOS only understands gzip.

Cheers

This post has been edited by Jotnar: 15 April 2009 - 11:01 AM

[shamurshamur]

Jotnar, on Apr 15 2009, 09:29 PM, said:

If you get the latest GRUB4DOS there is a workaround that I use. I'll post more detailed instructions this evening but here's the quick and dirty.

GRUB4DOS includes a file called grldr. This is the boot loader and it points to menu.lst by default (in a folder called BOOT if I remember correctly). What you can do is hex edit grldr and change the path to ISOLINUX/menu.lst. In doing so you can also change the name of the menu file. You then edit the menu.lst (or whatever you renamed it) file to boot your iso by default and set it to not show the GRUB menu. You'll need one copy of grldr and one menu.lst per each ISO you want to boot (this is why renaming menu.lst comes in handy...menu1.lst, menu2.lst...etc). You then make an ISOLinux entry for each of the grldr files and voila! you're good to go. Be aware that GRUB4DOS is case sensitive when you make your menu.lst files.

You should be able to boot your floppy images from ISOLinux using memdisk (my preferred method) but you can also load them from GRUB4DOS if you want. You can even zip up the .img files to save space. ISOLinux/Memdisk understands zip and gzip, GRUB4DOS only understands gzip.

Cheers

Thanks , that was very helpful.

what do you think , which one is more robust and functional grub4dos or bcdw ??..................cause i am thinking of making grub4dos my primary boot loader for multiboot dvd.

Also can grub4dos do everything of which bcdw is capable of??

I have notice that entries in menu.lst of grub4dos are more complicated than entries in bcdw.ini of bcdw when making a multiboot dvd.


can u post some example of entries in menu.lst for :

1) booting .iso file
2) booting .img file
3) corrosponding to a entry in bcdw for booting isolinux.bin :
/folder1/folder2/isolinux.bin ; linux ; ^ linux ; /folder1/folder2/vesamenu.c32 /folder1/folder2/isolinux.cfg


waiting for reply .
thanks

[shamurshamur]

one more question , can we hex edit loader.bin and bcdw.bin to look for bcdw.ini for different places.
If it is possible that i can load an . iso or .img file by invoking loader.bin ( of bcdw ) from isolinux.bin ( as a primary bootloader )

isolinux.bin <======> vesamenu.c32 <=========>isolinux.cfg
|
|
\/
losder1.bin / loader2.bin / loader3.bin

|
|
|
\/
bcdw1.bin / bcdw2.bin / bcdw3.bin
|
|
|
\/
bcdw1.ini / bcdw2.ini / bcdw3.ini
|
|
|
\/
image1.iso / image2.iso / image3.iso



No need to watch pixelated menu of bcdw

[Jotnar]

I think ISOLinux is probably the better of the three, but GRUB4DOS would be a close runner up.

Here's some pros and cons:

ISOLinux

Quote

Pros:
- Pretty! supports PNG and JPG backgrounds and a nice popup password box
- Menu syntax is easy to understand
- Granular password protection...you can password protect one menu and leave the others with full access
- Haven't met anything DOS/WinPE/Linux that I couldn't boot with it yet
- Can boot zipped floppy images (zip or gzip)
- Hotlinks for menu options
- Under active development
- Documentation is excellent
- Has a plethora of included modules (.c32)

Cons:
- Can't boot ISOs
- Some people have issues getting some specific floppy images working
- Can't boot OpenSolaris (at least I haven't gotten it to work yet...something to do with RockRidge extensions i'm sure)

GRUB4DOS

Quote

Pros:
- Can have a background image
- Granular password protection (I think?)
- Can boot some ISOs
- Can boot zipped floppy images (gzip)
- Floppy images that people couldn't get working with memdisk work
- You can do some other cool stuff from the GRUB command line

Cons:
- The background image is in a weird format and limited to 16 colors
- Password prompt is not as pretty as ISOLinux
- It only supports gzipped floppy images (no zip support)
- Can't have blank lines in menus
- No menu hotlinks
- Syntax can be daunting at first
- Documentation is ok, can be hard to find some stuff (Like how to boot an ISO!)
- Customization factor is low unless you like to hex edit
- Lead developer said he's taking a break from development but others will be taking over

Bootable CD Wizard (BCDW)

Quote

Pros:
- Can boot some ISOs
- Can be password protected
- Easy to understand syntax

Cons:
- No background image support
- No menu hotlinks
- No zipped floppy image support
- Password protection applies to entire menu
- No longer under active development

Example Main Menu

ISOLinux



GRUB4DOS


Bootable CD Wizard (BCDW)


I spent more time on the ISOLinux menu since that's my main menu so the others could probably look a little nicer.

I recommend using HxD for hex editing because its easy, powerfull and best of, its free!

It turns out you can hex edit loader.bin and have it look at a different ini file.
For BCDW look at offset 00000760 of loader.bin and change bcdw.ini to bcda.ini or bcdb.ini...etc. You don't need a seperate bcdw.bin for each, you can just use the original one. You will need seperate loader.bin and bcdw.ini files though.

For GRUB4DOS 4.4 look at offset 000003C0 of grldr and change /menu.lst to /ISOLINUX/menu1.lst...etc
To change the title look at offset 000320D0 of grldr and chage to what you want...I'd keep it the same length though since there's no free space afterwards. You'll need seperate grldr and menu.lst files.

For some reason I tacked a .bin onto grldr (so it looks like grldr.bin) I'm sure I had a good reason for it but I don't remember what it was. If booting grldr from ISOLinux without the .bin doesn't work try adding it.

Example ISO config for GRUB4DOS:

Quote

title Paragon Partition Manager 9.0
find --set-root /LINUX/PARAGON/PM/bootcd.iso
map --mem /LINUX/PARAGON/PM/bootcd.iso (hd32)
map --hook
root (hd32)
chainloader (hd32)

Example Floppy config for GRUB4DOS

Quote

title 2) Boot DOS with Network Support
map /DOSAPPS/IMAGES/BOOT/NETBOOT.IMG (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

Example Floppy config for GRUB4DOS using syslinux's memdisk

Quote

title 2) Boot DOS with Network Support
kernel /ISOLINUX/memdisk raw
initrd /DOSAPPS/IMAGES/BOOT/NETBOOT.ZIP

For general support for each of these fine tools,

ISOLinux:
Syslinux Mailing List
MSFN ISOLinux Disc Topic
Bootable CD Forum at 911cd.net

GRUB4DOS:
GRUB4DOS Forum at boot-land.net
Bootable CD Forum at 911cd.net

Bootable CD Wizard:
Bootable CD Wizard Help Index
Bootable CD Forum at 911cd.net

Hope I helped,
Cheers

[shamurshamur]

Jotnar, on Apr 16 2009, 07:42 AM, said:

It turns out you can hex edit loader.bin and have it look at a different ini file.
For BCDW look at offset 00000760 of loader.bin and change bcdw.ini to bcda.ini or bcdb.ini...etc. You don't need a seperate bcdw.bin for each, you can just use the original one. You will need seperate loader.bin and bcdw.ini files though.

Now , that was the perfect answer , thanks for your awesome explanation ........

i tried your advice of hex editing loader.bin ( of bcdw ) .........and guess what?........it worked like charm !!

i now decided to make isolinux.bin my primary bootloader and using bcdw and grub4dos (after hex editing them) for booting iso and img files.

Thank you very much .................. can't wait to try hexediting of grldr .

[Jotnar]

Happy Hexing!

[mr.xx]

mr Jotnar I would ask you about

how to add password protection on isolinux.cfg

seam this pic



can give me example

thank you very much

[shamurshamur]

mr.xx, on May 20 2009, 01:36 PM, said:

mr Jotnar I would ask you about

how to add password protection on isolinux.cfg

seam this pic



can give me example

thank you very much

See the help documentation (menu.txt) in syslinux program .( there are also many other tips for customizing the menu in help documentation )
You can download it from here "http://www.kernel.org/pub/linux/utils/boot/syslinux/"

i am giving a quote from that documentation for your quick reference.......

-----------------------------------------------quote start-------------------------------------------------------------------
MENU PASSWD passwd

(Only valid after a LABEL statement.)

Sets a password on this menu entry. "passwd" can be either a
cleartext password or a password encrypted with one of the
following algorithms:

MD5 (Signature: $1$)
SHA-1 (Signature: $4$)
SHA-2-256 (Signature: $5$)
SHA-2-512 (Signature: $6$)

Use the included Perl scripts "sha1pass" or "md5pass" to
encrypt passwords. MD5 passwords are compatible with most
Unix password file utilities; SHA-1 passwords are probably
unique to Syslinux; SHA-2 passwords are compatible with very
recent Linux distributions. Obviously, if you don't encrypt
your passwords they will not be very secure at all.

If you are using passwords, you want to make sure you also use
the settings "NOESCAPE 1", "PROMPT 0", and either set
"ALLOWOPTIONS 0" or use a master password (see below.)

If passwd is an empty string, this menu entry can only be
unlocked with the master password.


MENU MASTER PASSWD passwd

Sets a master password. This password can be used to boot any
menu entry, and is required for the [Tab] and [Esc] keys to
work.

--------------------------------------------quote end--------------------------------------------------

This post has been edited by shamurshamur: 28 May 2009 - 05:04 AM

[sbaeder]

Jotnar, on 15 April 2009 - 09:12 PM, said:

For some reason I tacked a .bin onto grldr (so it looks like grldr.bin) I'm sure I had a good reason for it but I don't remember what it was. If booting grldr from ISOLinux without the .bin doesn't work try adding it.

this is because of the loading of different kinds of data into memory...isolinux usesw extensions to figure out what to do - or use the other keywords as specified in the docs.

[Icecube]

You can boot grldr from Syslinux (and ISOLINUX) in different ways:

# From ISOLINUX (old syntax):
#   when using KERNEL Syslinux looks at the file extension
#   to know how it should boot the file ==> not preferred
#   .bin extension needed to tell ISOLINUX that it is a CD boot sector
LABEL 1
KERNEL /grldr.bin

# From SYSLINUX (old syntax):
#   when using KERNEL Syslinux looks at the file extension
#   to know how it should boot the file ==> not preferred
#   .bs extension needed to tell SYSLINUX that it is a (HDD/floppy) boot sector
LABEL 2
KERNEL /grldr.bs

# From ISOLINUX/SYSLINUX (new syntax):
#   BOOT tells Syslinux that the file should be treated as a:
#     - CD boot sector (ISOLINUX)
#     - (HDD/floppy) boot sector (SYSLINUX)
LABEL 3
BOOT /grldr

# From ISOLINUX/SYSLINUX (new syntax) + with chain.c32 (Method 1):
#   Will do the same as "BOOT /grldr"
LABEL 4
COM32 chain.c32
APPEND file=/grldr

# From ISOLINUX/SYSLINUX (new syntax) + with chain.c32 (Method 2):
#   Will load grldr like ntldr
LABEL 5
COM32 chain.c32
APPEND ntldr=/grldr

When using chain.c32, you can specify from which drive grldr thinks it is booted (will search menu.lst on that device first):

# "boot" = same drive as Syslinux boot drive ("boot" is assumed when hd* isn't specified)
LABEL 6
COM32 chain.c32
APPEND file=/grldr boot

# set device to first HDD
LABEL 7
COM32 chain.c32
APPEND file=/grldr hd0

# set device to second HDD
LABEL 8
COM32 chain.c32
APPEND file=/grldr hd1

# Swap second HDD (=hd1) with first HDD (=hd0)
# In grub4dos (hd0) will in reality be hd1
LABEL 9
COM32 chain.c32
APPEND file=/grldr hd1 swap

You can take a look at: http://www.boot-land...&st=10&start=10
MEMDISK of the Syslinux package can boot floppy images (since the beginning), HDD images and ISO images (recently):

# Boot floppy image (new syntax):
#   "APPEND floppy" can be used to force MEMDISK to see the image as a floppy (normally not needed)
LABEL 10
LINUX memdisk
INITRD floppy.img

# Boot floppy image (new syntax):
#   "raw" is needed on some PCs with some DOS images (when they use memory extenders)
LABEL 11
LINUX memdisk
INITRD floppy.img
APPEND raw

# Boot HDD image (new syntax):
#   "APPEND harddisk" can be used to force MEMDISK to see the image as a hard disk (normally not needed)
LABEL 12
LINUX memdisk
INITRD hdd.img

# Boot ISO image (new syntax):
#   "APPEND iso" is needed to boot ISO's with MEMDISK
LABEL 13
LINUX memdisk
INITRD iso.iso
APPEND iso

More info about ISO booting with MEMDISK: http://www.boot-land...?showtopic=8258

This post has been edited by Icecube: 07 January 2010 - 06:13 AM