UBCD50RC1 uses the new Syslinux syntax.
It uses LINUX instead of KERNEL and INITRD on a separate line instead of on the APPEND line as "initrd=".
You used something like this:
Code: Select all
LABEL -
MENU LABEL Acronis Disk Director Suite 10.0
TEXT HELP
Acronis Disk Director Suite brings together the most popular disk management
functions, partition recovery tool, and boot disk manager.
ENDTEXT
KERNEL /ubcd/custom/adds/kernel.dat
APPEND rw initrd=/ubcd/custom/adds/ramdisk.dat /S ramdisk_size=32000 mbrcrcs=on vga=791 quiet
Your syslinux menu entry in custom.cfg, should be:
Code: Select all
LABEL -
MENU LABEL Acronis Disk Director Suite 10.0
TEXT HELP
Acronis Disk Director Suite brings together the most popular disk management
functions, partition recovery tool, and boot disk manager.
ENDTEXT
LINUX /ubcd/custom/adds/kernel.dat
INITRD /ubcd/custom/adds/ramdisk.dat
APPEND rw /S ramdisk_size=32000 mbrcrcs=on vga=791 quiet
My syslinux2grub4dos script isn't smart enough (or I am not
) to handle the old syntax too. I tried it, but all my config files where messed up, so I stopped with it.
Running the script now, should give the following Grub4dos syntax:
Code: Select all
title Acronis ^Disk Director Suite 10.0\n Acronis Disk Director Suite brings together the most popular disk management\n functions, partition recovery tool, and boot disk manager.
kernel /ubcd/custom/adds/kernel.dat rw /S ramdisk_size=32000 mbrcrcs=on vga=791 quiet
initrd /ubcd/custom/adds/ramdisk.dat
You got the "Kernel panic: VFS: Unable to mount root fs on 01:00" message because grub4dos didn't load the initrd file. Grub4dos doesn't understand the APPEND line, it uses a 'kernel' line which contains the kernel filename, which you want load and the parameters that you want to pass to the kernel (the values that are on the APPEND line in syslinux syntax, execpt the initrd= part), and an 'initrd' line, which will load the initrd file.