It is currently Fri Mar 06, 2015 6:10 am

All times are UTC - 8 hours

Post new topic Reply to topic  [ 2 posts ] 
Author Message
PostPosted: Fri Mar 21, 2014 6:59 am 

Joined: Fri Mar 21, 2014 6:50 am
Posts: 1
Hi Everyone!

I am having issues adding Linux System Rescure CD, Ophcrack Vista, Trinity Rescue Kit ISOs to UBCD and it seems like I am doing something wrong for all three as they boot and fail at "half way", while ophcrack boots and is missing tables.

Here is what I got:
Each having issues booting, booting up initially but not completely.
- Linux System Rescure CD boots half way and errors out
- Ophcrack won’t load tables
- Trinity Rescue Kit shows: “TRK not found on CD” error at half way…

There is an ISO file for each utility in the custom folder (Ubcd\custom\) with those files:

[User Defined]

# Useful resources for UBCD customization:
# - ... UX_Project
# -

color cyan/black black/light-gray green/black yellow/black

title ..
configfile /ubcd/menus/grub4dos/main.lst

title Your own boot image here\n Your help message goes here.
map --mem /ubcd/custom/boot.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

MENU INCLUDE /ubcd/menus/syslinux/defaults.cfg
UI /boot/syslinux/menu.c32

COM32 /boot/syslinux/menu.c32
APPEND /ubcd/menus/syslinux/main.cfg

MENU LABEL Linux-System-Rescure-CD
LINUX /boot/syslinux/memdisk
INITRD /ubcd/custom/Linux-System-Rescure-CD.iso
APPEND iso raw

MENU LABEL Ophcrack-Live-CD
LINUX /boot/syslinux/memdisk
INITRD /ubcd/custom/Ophcrack-Live-CD.iso
APPEND iso raw

MENU LABEL Trinity-Rescue-Kit
KERNEL /boot/syslinux/memdisk
INITRD /ubcd/custom/Trinity-Rescue-Kit.iso
APPEND iso raw

Am I missing something? As I think it is not pulling the config files for each ISO and is failing to boot...

Any help would be greatly appreciated! Thanks!

Reply with quote  
PostPosted: Sun Mar 23, 2014 10:03 am 

Joined: Sat May 08, 2010 5:26 am
Posts: 782
I don't know which version of UBCD you are using. I also don't know which version of Syslinux you are using.

Whichever the versions, memdisk requires RAM for the ISO image. If the ISO image you are trying to load is "too big" for the RAM available, it might probably fail.

Another detail might probably be the "raw" parameter you are using in the append line. Why you think you need it?

An alternative method to memdisk, would be to expand each ISO image and use ISOLINUX/SYSLINUX directly. I won't get into the technical details. You might be interested in using auxiliary tools such as YUMI, SARDUCD, LILI, or some of their alternatives under Linux.

Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 2 posts ] 

All times are UTC - 8 hours

Who is online

Users browsing this forum: No registered users and 3 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  

Protected by Anti-Spam ACP Powered by phpBB® Forum Software © phpBB Group