another .iso question

[veggy]

so how do you add .iso images? I'm not sure the other thread is the same problem. I don't know if command line switches are involved. I didn't want to hijack that thread with something that may be different and confuse the issue.

viewtopic.php?f=10&t=2651

what I'm trying to do is simply drop in .iso images into the /images folder, just like I do with .img, .ima and .igz floppy images. and edit the menu accordingly.

those work no problem, but .iso images don't. just like in the other thread, they are on the menu and can be selected, but when it goes to actually boot from them it fails. unlike the other thread, he has error codes. I don't, it just says failed to boot.

there shouldn't be any problem with the .iso images themselves, they're factory images, when burnt to a cd they boot up with no problem.

what am I doing wrong? what do I have to do to get an .iso image to load?

[Icecube]

Not all ISO's can be booted. It depends on the OS. If your ISO is DOS-based, you normally won't have any problem.

See the Syslinux wiki page about MEMDISK for more info about this topic:
http://syslinux.zytor.com/wiki/index.ph ... ISO_images

Which ISO's are you trying to boot (a link would be nice too).

[veggy]

gigabyte XpresRecovery .iso doesn't work.

http://download.gigabyte.us/FileList/Ut ... ty_xr2.exe

HDShredder 3.6 Free: it makes an .iso (for CD) that doesn't work with UBCD, but also makes an .img (for floppy) that does work with UBCD. when I burn the .iso to CD and run it, I don't think it has a different boot setup than the .img version, because the stuff that runs across the screen looks the same, and the GUI looks and works exactly the same, so I would guess not.

http://www.miray.de/public/download/hds ... .fe.en.zip

[veggy]

the wiki page link you gave me says this:

ISO images

For ISO images, the parameter 'iso' must be passed to MEMDISK.

LABEL hdt_iso
LINUX memdisk
INITRD hdt.iso
APPEND iso

Sometimes

APPEND iso raw

is the better "APPEND" option. For example, some Windows ISO's need the 'raw' option on some PCs.

does that refer to what goes on the menu? or somewhere else? because my menu isn't quite the same. that says LINUX but mine says KERNEL:

MENU INCLUDE /menus/defaults.cfg

LABEL back
MENU LABEL ..
KERNEL menu.c32
APPEND /menus/main.cfg

LABEL bootimg
MENU LABEL Your own boot image here
KERNEL memdisk
APPEND initrd=/custom/boot.img

LABEL hdshred_img
MENU LABEL hd shredder 3.6.4 free
KERNEL memdisk
APPEND initrd=/images/hdshred.img

LABEL gbyte_xr2
MENU LABEL gigabyte xpress recovery 2
KERNEL memdisk
APPEND initrd=/images/xr2.iso

I don't want to simply substitute LINUX for KERNEL in what might be the wrong place and cause a meltdown!

if that is the right answer, then would it look like this?

LABEL gbyte_xr2
MENU LABEL gigabyte xpress recovery 2
LINUX memdisk
INITRD /images/xr2.iso
APPEND iso

[Icecube]

KERNEL and LINUX will do the same in this case. When you use KERNEL, Syslinux looks at the file extension to know how to boot the file. When you use LINUX, it will always boot the file as a linux kernel.
Some programs that need to be booted as a linux kernel have a .bin extension. Syslinux interprets this as a ISOLINUX bootsector image, when you use LINUX, it will boot it as kernel.

This works for me:

Code: Select all

LABEL hdshredder
MENU LABEL HD shredder
LINUX /boot/syslinux/memdisk
INITRD/custom/hdshredder.iso
APPEND iso

LABEL gbyte_xr2
MENU LABEL gigabyte xpress recovery 2
LINUX /boot/syslinux/memdisk
INITRD /images/xr2.iso
APPEND iso

It seems to me that you still use the old Syslinux syntax, so I suspect that you have not the last version of UBCD.
Only MEMDISK 3.84 or higher support booting ISO images.