davemguru |
11-17-2011 07:54 AM |
Quote:
Originally Posted by googleplus
(Post 4526460)
Now, I have gone through some of this forum to find out what in God's name this applies to when extracting it from a "livecd" file, but I am at the point of despair. Please explain in clear english what I should do. TIA.
JR
|
Hi, I can only explain what vesamenu.c32 is for - not "what I should do" because, you have not explained your desire/goal in extracting files from your livecd. Are you installing? Trying to create your own livecd? Re-mastering? Trying to build a PXE/Boot server?
Anyway - vesamenu.c32 is part of the "SYSLINUX" suite of Bootloaders. To quote from the website ( http://freecode.com/projects/syslinux)
Quote:
SYSLINUX is a suite of lightweight bootloaders, currently supporting DOS FAT filesystems (SYSLINUX), Linux ext2/ext3 filesystems (EXTLINUX), PXE network booting (PXELINUX), or bootable "El Torito" ISO 9660 CD-ROMs (ISOLINUX). It also includes a tool, MEMDISK, which loads legacy operating systems (such as DOS) from these media
|
Quote:
There are two menu systems included with Syslinux, the advanced menu
system, and the simple menu system.
|
Quote:
+++ THE SIMPLE MENU SYSTEM +++
The simple menu system is a single module located at
com32/modules/vesamenu.c32 (graphical) or com32/modules/menu.c32 (text
mode only). It uses the same configuration file as the regular
Syslinux command line, and displays all the LABEL statements.
To use the menu system, simply make sure [vesa]menu.c32 is in the
appropriate location for your boot medium (the same directory as the
configuration file for SYSLINUX, EXTLINUX and ISOLINUX, and the same
directory as pxelinux.0 for PXELINUX), and put the following options
in your configuration file:
UI menu.c32
|
So... a simple answer to your plea is --> vesamenu.c32 is a program which displays the boot menu that you see when you boot your cd/dvd/usb thing. It is the program that displays in a graphical format - the contents of the "default" menu. It should reside in the same folder/directory as your ".cfg" file.
Sorry, that's about as far as I can help until I know more about what it is you are trying to achieve.
Dave
|