19 replies to this topic

[kodiak]

Hi there.

Used YUMI to create my own bootable USB flash drive.

This is the syslinux.cfg and works ok.

# Menu Entry Created by Lance http://www.pendrivelinux.com for YUMI - (Your USB Multiboot Installer)

default vesamenu.c32

prompt 0

timeout 300

menu title Your Universal MultiBoot Installer

menu background yumi.png

MENU TABMSG  http://www.pendrivelinux.com

MENU WIDTH 72

MENU MARGIN 10

MENU VSHIFT 3

MENU HSHIFT 6

MENU ROWS 15

MENU TABMSGROW 20

MENU TIMEOUTROW 22

menu color title 1;36;44 #66A0FF #00000000 none

menu color hotsel 30;47 #C00000 #DDDDDDDD

menu color sel 30;47 #000000 #FFFFFFFF

menu color border 30;44 #D00000 #00000000 std

menu color scrollbar 30;44 #DDDDDDDD #00000000 none



label Boot from first Hard Drive

menu label Continue to Boot from ^First HD (default)

KERNEL chain.c32

APPEND hd1

MENU DEFAULT



label Directly Bootable ISOs

menu label Directly Bootable ISOs ->

MENU INDENT 1

KERNEL /multiboot/grub.exe

APPEND --config-file=/multiboot/menu/menu.lst



label System Tools

menu label System Tools ->

MENU INDENT 1

kernel vesamenu.c32

APPEND /multiboot/menu/system.cfg

When I go to system.cfg I got this:

# Menu Entry Created by Lance http://www.pendrivelinux.com for YUMI - (Your USB Multiboot Installer)

default vesamenu.c32

prompt 0

menu title System Tools

menu background yumi.png

MENU TABMSG  http://www.pendrivelinux.com

MENU WIDTH 72

MENU MARGIN 10

MENU VSHIFT 3

MENU HSHIFT 6

MENU ROWS 15

MENU TABMSGROW 20

MENU TIMEOUTROW 22

menu color title 1;36;44 #66A0FF #00000000 none

menu color hotsel 30;47 #C00000 #DDDDDDDD

menu color sel 30;47 #000000 #FFFFFFFF

menu color border 30;44 #D00000 #00000000 std

menu color scrollbar 30;44 #DDDDDDDD #00000000 none



label <-- Back to Main Menu

kernel vesamenu.c32

append /multiboot/syslinux.cfg

MENU SEPARATOR



label System Rescue CD

menu label System Rescue CD

MENU INDENT 1

kernel vesamenu.c32

APPEND /multiboot/menu/sysrescuecd.cfg





label Parted Magic (Partition Tools)

menu label Parted Magic (Partition Tools)

MENU INDENT 1

kernel vesamenu.c32

APPEND /multiboot/menu/partedmagic.cfg

Again, It's all working ok.

Now, on my USB, I have a folder containing Hiren's Boot CD. Its located in /multiboot/HBCD
The menu from Hirens is located in /multiboot/HBCD/isolinux and its called hiren.cfg

This is the hiren.cfg file

INCLUDE header.cfg

#-------------------------------------------------

label 0

menu label ^Boot From Hard Drive

localboot 0x80

TEXT HELP

Boot first hard drive.

ENDTEXT

menu separator

#-------------------------------------------------

label hbcd

menu label HBCD Programs Dos Boot ^Menu ...

# kernel /isolinux/memdisk

# append initrd=/HBCD/Dos/dos.gz

kernel /bootprog/grub.exe

append --config-file="find --set-root /HBCD/Dos/dos.gz; map --mem /HBCD/Dos/dos.gz (fd0); map --hook; chainloader (fd0)+1; rootnoverify (fd0); map --floppies=1 "

TEXT HELP

Norton Ghost, Acronis, Paragon, Rescue,

and all the other HBCD Dos Boot utilities...

ENDTEXT

#-------------------------------------------------

menu separator

#-------------------------------------------------

INCLUDE miniwin.cfg

menu separator

# -------------------------------------------------

INCLUDE hd.cfg

# -------------------------------------------------

INCLUDE antivirus.cfg

#-------------------------------------------------

INCLUDE linux.cfg

# -------------------------------------------------

INCLUDE hw.cfg

#-------------------------------------------------

INCLUDE password.cfg

menu separator

#-------------------------------------------------

LABEL Plop

MENU LABEL Pl^op Boot Manager

LINUX /bootdisk/plpbt.bin

TEXT HELP

Boot from HD, CD, USB even if BIOS cannot.

ENDTEXT

menu separator

menu separator

#-------------------------------------------------

label grbdos

menu label ^Alternative Boot Method (Grub4DOS) ...

BOOT /HBCD/grldr

TEXT HELP

Use this option if any of the above fails to boot.

ENDTEXT

All the INCLUDE files are on the same location that hiren.cfg.

Now I go to system.cfg and will add the Hiren's to the menu. I've added this on system.cfg.

label Hiren

menu label Hiren

MENU INDENT 1

kernel vesamenu.c32

APPEND /multiboot/HBCD/isolinux/hiren.cfg

But it is not working. When I go to the menu and press enter in the Hiren entry nothing happens.

What am I doing wrong?

Thanks,

kodiak

[steve6375]

I would guess that it cannot find the header.cfg file as it is not pathed??
from the manual

Set Syslinux' home dir to </path/to/cfg/file> and load new config file:
LABEL new_config2
CONFIG </path/to/cfg/file>/<configfile.cfg> </path/to/cfg/file>

[kodiak]

I would guess that it cannot find the header.cfg file as it is not pathed??
from the manual

Thanks Steve6375

Added /multiboot/HBCD/isolinux/header.cfg to th hirens.cfg and it didn't do anything.

Here it's something strange. I've mede a copy of sysrescuecd.cfg and rename it to sysrescuecd1.cfg (the contents on the two files are the exact same)

Now, putted this on system.cfg

label Hiren

menu label Hiren

MENU INDENT 1

kernel vesamenu.c32

APPEND /multiboot/menu/sysrescuecd1.cfg

Now it does nothing when press enter at Hiren entry...

[steve6375]

Are you sure the extension does not end in .txt (if saving with Notepad?).

[kodiak]

Are you sure the extension does not end in .txt (if saving with Notepad?).

Yes All files end with .cfg

[ady]

Try changing from

label hiren

menu label Hiren

MENU INDENT 1

kernel vesamenu.c32

APPEND /multiboot/HBCD/isolinux/hiren.cfg

to

LABEL hiren

MENU LABEL Hiren

MENU INDENT 1

CONFIG /multiboot/HBCD/isolinux/hiren.cfg  /multiboot/HBCD/isolinux/

And in hiren.cfg add at the end

MENU SEPARATOR



LABEL Back to main menu

MENU LABEL Back to main menu

CONFIG /multiboot/syslinux.cfg /multiboot/

[kodiak]

Try changing from

label hiren

menu label Hiren

MENU INDENT 1

kernel vesamenu.c32

APPEND /multiboot/HBCD/isolinux/hiren.cfg

to

LABEL hiren

MENU LABEL Hiren

MENU INDENT 1

CONFIG /multiboot/HBCD/isolinux/hiren.cfg  /multiboot/HBCD/isolinux/

And in hiren.cfg add at the end

MENU SEPARATOR



LABEL Back to main menu

MENU LABEL Back to main menu

CONFIG /multiboot/syslinux.cfg /multiboot/

Hi ady.

Just the same. Problem still exists

[ady]

If the hiren.cfg menu doesn't show up, then it seems that either some info you provided is not exact (some path for example, or some name), or alternatively something else is wrong (like with the versions of syslinux in HBCD and in YUMI just for an example).

What I mean is that according to the info you provided, the cfg files are correct; so either the info needs some correction, or something else (not the cfg files, which is what you are asking for) is the problem.

[kodiak]

If the hiren.cfg menu doesn't show up, then it seems that either some info you provided is not exact (some path for example, or some name), or alternatively something else is wrong (like with the versions of syslinux in HBCD and in YUMI just for an example).

What I mean is that according to the info you provided, the cfg files are correct; so either the info needs some correction, or something else (not the cfg files, which is what you are asking for) is the problem.

Hi ady.

Path and name are correct.

How can I find the syslinux veresion? On YUMI source code I can see that version 4.06 was used to give NTFS support. ON HBCD/bootprog theres a syslinux.exe there but I don't know how to see what version it is.

[ady]

For the syslinux version, open a cmd in the specific folder and type:

syslinux.exe --version

Although the different versions might give you some problem, I'm not sure that these different versions should be enough in this case to prevent you from seeing the menu. I think at least should show you some error message.

Moreover, YUMI also supports HBCD, and there are other alternatives to YUMI too. So if you are having problems building the menu manually, simply use the capabilities already there in YUMI (or in some alternative tool that would work for your needs).

[kodiak]

For the syslinux version, open a cmd in the specific folder and type:

syslinux.exe --version

Although the different versions might give you some problem, I'm not sure that these different versions should be enough in this case to prevent you from seeing the menu. I think at least should show you some error message.

Moreover, YUMI also supports HBCD, and there are other alternatives to YUMI too. So if you are having problems building the menu manually, simply use the capabilities already there in YUMI (or in some alternative tool that would work for your needs).

Hi ady.

YUMI - version 4.06 HBCD - version 4.04

I don't know if this is enough to dosn't work.

I know that there are some other alternatives but at this point was just curiosity

Does the USB be formated as NTFS be the responsible?

[Wonko the Sane]

Does the USB be formated as NTFS be the responsible?

Yes, most probably

Here :
http://reboot.pro/15086/


Wonko

[kodiak]

Yes, most probably

Here :
http://reboot.pro/15086/


Wonko

Will test formatting the USB as FAT32 and then will post here the results....

Thanks for all the help.

[ady]

As I said, YUMI can add HBCD to the same USB drive, so use it. If that works, you can see how YUMI builds the menu files so to boot HBCD (which doesn't mean is the only method).

YUMI uses syslinux 4.06 (but not the latest 4.06, which is still under development), but that doesn't mean you need to use NTFS, nor that the software you add to the USB drive can run under NTFS. For example HBCD includes some DOS tools, that might not run correctly under these conditions.

So considering all this, I would suggest using FAT if possible.

[kodiak]

As I said, YUMI can add HBCD to the same USB drive, so use it. If that works, you can see how YUMI builds the menu files so to boot HBCD (which doesn't mean is the only method).

YUMI uses syslinux 4.06 (but not the latest 4.06, which is still under development), but that doesn't mean you need to use NTFS, nor that the software you add to the USB drive can run under NTFS. For example HBCD includes some DOS tools, that might not run correctly under these conditions.

So considering all this, I would suggest using FAT if possible.

Ok. Thanks for all the help and explanations.

One last question.

I know we can partition our USB drives. Is it safe? ie does it damages our drives?

[ady]

I know we can partition our USB drives. Is it safe? ie does it damages our drives?

Partitioning would "erase" the previous information. If by "(un)safe" you mean some phisical damage, not "per se". But, generally speaking, the possibility that your drive get damaged at some point, for whichever reason, indeed exists.

If you don't need to partition, don't do it (except if you indeed have some specific positive goal in mind). Instead, format the same current USB drive partition to FAT32 (which will erase the data on that partition, so have a backup copy elswhere of any data you would need to save).

[kodiak]

(except if you indeed have some specific positive goal in mind)

The USB its 16 GB. Will give 6 gb for the FAT32 and the rest for the NTFS. Why? I don't know if I would need to store files bigger than 4 GB. And yes, I was talking about physical damage. The information is always backed up.

[kodiak]

Yes, most probably

Yep. Changed to FAT32 and all works

Thanks all for the help and explanations..

[Wonko the Sane]

Yep. Changed to FAT32 and all works

Sure , however the hint was towards leaving it as NTFS and try the Syslinux version that does support NTFS....


Wonko

[kodiak]

Sure , however the hint was towards leaving it as NTFS and try the Syslinux version that does support NTFS....


Wonko

When I have the time I will look into that

Thanks for the hint