1. Wonder what the best way would be to go about adding another c:\ubcd-extract\menus\.*.cfg file besides the ones already present plus the overflow c:\ubcd-extract\custom\custom.cfg
A nice feature to have.
Already tried creating a c:\ubcd-extract\menus\bootdsks3.cfg and putting inside this a Linux boot LiveCD that was working fine in c:\ubcd-extract\bootdsk2.cfg\
When the new UBCD.ISO (version 4.1.1) was created and launched, selecting just the bootdsk3.cfg itself caused the screen to go all blank even before any attempt to select proper boot disk
2. Another nice feature to have is the ability boot a Windows 9x system from a rescue image.
Already tried using Windows 98 rescue images from http://www.allbootdisks.com/download/98.html to rescue-boot a Win98 system.
No luck.
Maybe creating a Win98.igz from an ISO at http://www.allbootdisks.com/download/iso.html and placing it in c:\ubcd-extract\images to boot via c:\ubcd-extract\menus\bootdsk1.cfg would work
Would sort of have to use c:\ubcd-extract\menus/bootdsk1.cfg until the requested feature of adding another boot menu.cfg becomes available.
Have already downloaded the updated syslinux-3.71 updates and repeatedly copied over the required files to c:\ubcd-extract\isolinux\
Adding UBCD411 menu(s) and Win9x Rescue Image(s)
Moderators: Icecube, StopSpazzing
See the following topic to see how the directory layout of UBCD5 will be (and why):
viewtopic.php?t=1521
Read the following links carefully to understand how syslinux, isolinux, memdisk and the menu system work.
General info about syslinux / isolinux / memdisk:
http://syslinux.zytor.com/faq.php
Information about the menu system of syslinux:
http://syslinux.zytor.com/menu.php
You can find those files also in the syslinux package in the doc directory.
I would recommend that you use UBCD5 beta v5 to add custom images. It won't take that long untill the final comes out. Else you have to edit a lot of cfg files again.
viewtopic.php?t=1521
What are the contents of the c:\ubcd-extract\menus\bootdsks3.cfg file?coin wrote:Already tried creating a c:\ubcd-extract\menus\bootdsks3.cfg and putting inside this a Linux boot LiveCD that was working fine in c:\ubcd-extract\bootdsk2.cfg\
When the new UBCD.ISO (version 4.1.1) was created and launched, selecting just the bootdsk3.cfg itself caused the screen to go all blank even before any attempt to select proper boot disk
Read the following links carefully to understand how syslinux, isolinux, memdisk and the menu system work.
General info about syslinux / isolinux / memdisk:
http://syslinux.zytor.com/faq.php
Information about the menu system of syslinux:
http://syslinux.zytor.com/menu.php
You can find those files also in the syslinux package in the doc directory.
You can make as many cfg files as you want (the filename must be 8 characters at maximum + 3 for the extension). Read the links above to understand how syslinux works.coin wrote:Would sort of have to use c:\ubcd-extract\menus/bootdsk1.cfg until the requested feature of adding another boot menu.cfg becomes available.
I would recommend that you use UBCD5 beta v5 to add custom images. It won't take that long untill the final comes out. Else you have to edit a lot of cfg files again.
Overflow from bootdsk1.cfg and bootdsk2.cfg
Sure thing.What are the contents of the c:\ubcd-extract\menus\bootdsks3.cfg file?
Contents of current c:\ubcd-extract\menus\bootdsk3.cfg :
Code: Select all
MENU INCLUDE /menus/defaults.cfg
LABEL back
MENU LABEL ..Back one level
KERNEL menu.c32
APPEND /menus/bootdsk.cfg
LABEL baslin35
MENU LABEL Basic Linux 3.50
KERNEL /baslin35/baslinux
APPEND root=/dev/ram0 ramdisk_size=22000 initrd=/baslin35/baslinux.gz
LABEL dsl3
MENU LABEL Damn Small Linux 3.4.12
CONFIG /dsl3/isolinux.cfg
LABEL rescuecd
MENU LABEL SystemRescueCD 1.1.0
CONFIG /rescuecd/isolinux/rescuecd.cfg
LABEL slax
MENU LABEL Slax 6.0.7
KERNEL /slax/slax
APPEND initrd=/slax/slax.gz ramdisk_size=10000 root=/dev/ram0 rw autoexec=xconf;telinit~4 changes=/slax/
LABEL slax2ram
MENU LABEL Slax2RAM (loads slax to ram)
KERNEL /slax/slax
APPEND initrd=/slax/slax.gz ramdisk_size=10000 root=/dev/ram0 rw copy2ram autoexec=xconf;telinit~4
LABEL w98
MENU LABEL Windows 98 Boot Disk
KERNEL memdisk
APPEND initrd=/w9xboot/w98.img
Possibility that a 'KERNEL chain.c32' would have to replace the above 'KERNEL memdisk'menu directive in order to keep this bootdsk3.cfg from falling flat again
Doin' my homework!
To Replace or Not to Replace; That is the Question .
Makes some sense, yet network-carrier reps don't prefer imminent (or possible future) use of [bit]torrentsI would recommend that you use UBCD5 beta v5 to add custom images. It won't take that long untill the final comes out. Else you have to edit a lot of cfg files again.
See viewtopic.php?t=1398