search for: stdmenu

...riginal isolinux.cfg: ***************************+ include menu.cfg default vesamenu.c32 prompt 0 timeout 300 gfxboot bootlogo ************************* and here is the menu.cfg file: ***************************** menu hshift 13 menu width 49 menu margin 8 menu title Installer boot menu include stdmenu.cfg include text.cfg include amd.cfg include gtk.cfg include amdgtk.cfg menu begin advanced menu title Advanced options label mainmenu menu label ^Back.. menu exit include stdmenu.cfg include adtext.cfg include adamd.cfg include adgtk.cfg include adamdgtk.cfg menu end label help menu la...

...7.txt ??? f8.txt ??? f9.txt ??? g2ldr ??? g2ldr.mbr ??? gtk.cfg ??? initrdg.gz ??? initrd.gz ??? ldlinux.c32 ??? ldlinux.sys ??? libcom32.c32 ??? libutil.c32 ??? linux ??? menu.cfg ??? NvVars ??? prompt.cfg ??? rqgtk.cfg ??? rqspkgtk.cfg ??? rqtxt.cfg ??? setup.exe ??? spkgtk.cfg ??? splash.png ??? stdmenu.cfg ??? syslinux.cfg ??? txt.cfg ??? vesamenu.c32 ??? win32-loader.ini carl at twist:/media/carl/Debian Inst$ cat syslinux.cfg # simple syslinux.cfg DEFAULT linux LABEL linux KERNEL linux INITRD initrd.gz > > BTW, Debian "Testing" ATM has the most up-to-date binaries of Syslinux,...

...> ??? libcom32.c32 > > ??? libutil.c32 > > ??? linux > > ??? menu.cfg > > ??? NvVars > > ??? prompt.cfg > > ??? rqgtk.cfg > > ??? rqspkgtk.cfg > > ??? rqtxt.cfg > > ??? setup.exe > > ??? spkgtk.cfg > > ??? splash.png > > ??? stdmenu.cfg > > ??? syslinux.cfg > > ??? txt.cfg > > ??? vesamenu.c32 > > ??? win32-loader.ini > > > > carl at twist:/media/carl/Debian Inst$ cat syslinux.cfg > > # simple syslinux.cfg > > DEFAULT linux > > LABEL linux > > KERNEL linux > > I...

....mbr > ??? gtk.cfg > ??? initrdg.gz > ??? initrd.gz > ??? ldlinux.c32 > ??? ldlinux.sys > ??? linux > ??? menu.cfg > ??? NvVars > ??? prompt.cfg > ??? rqgtk.cfg > ??? rqspkgtk.cfg > ??? rqtxt.cfg > ??? setup.exe > ??? spkgtk.cfg > ??? splash.png > ??? stdmenu.cfg > ??? syslinux.cfg > ??? txt.cfg > ??? win32-loader.ini > > except that PATH into the bios files is a problem for efi, or is it? I just realized maybe efi can avoid that file, and so path to bios files is fine. > so I'm > trying to move syslinux.cfg > into target...

...Looks like it is surrounded by a little empire of .cfg files: /isolinux/adgtk.cfg /isolinux/adtxt.cfg /isolinux/exithelp.cfg /isolinux/gtk.cfg /isolinux/isolinux.cfg /isolinux/menu.cfg /isolinux/prompt.cfg /isolinux/rqgtk.cfg /isolinux/rqtxt.cfg /isolinux/spkgtk.cfg /isolinux/stdmenu.cfg /isolinux/txt.cfg The "append" statements are in several of the subordinate files. E.g. in /isolinux/txt.cfg: append desktop=xfce vga=788 initrd=/install.386/initrd.gz --- quiet > Thanks, everyone, for your patience and assistance. :-) Martin and me will probably ask you...

> > > > You should be able to see the effects of the DISPLAY directive when > > testing the floppy image I sent you, because it starts with the boot > > prompt, not with a menu. > > I see the effects, both good and bad. I'm having trouble knowing how > bad the bad is. How about comparing it with the current behaviour in BIOS mode? > I'm not

...4.txt ??? f5.txt ??? f6.txt ??? f7.txt ??? f8.txt ??? f9.txt ??? g2ldr ??? g2ldr.mbr ??? gtk.cfg ??? initrdg.gz ??? initrd.gz ??? ldlinux.c32 ??? ldlinux.sys ??? linux ??? menu.cfg ??? NvVars ??? prompt.cfg ??? rqgtk.cfg ??? rqspkgtk.cfg ??? rqtxt.cfg ??? setup.exe ??? spkgtk.cfg ??? splash.png ??? stdmenu.cfg ??? syslinux.cfg ??? txt.cfg ??? win32-loader.ini except that PATH into the bios files is a problem for efi, so I'm trying to move syslinux.cfg into target/boot/syslinux but I can't figure out how to do it. this file gives me a boot: prompt # target/boot/syslinux/syslinux.cfg # path...

...g |-- lxde | |-- adgtk.cfg | |-- adgtkdt.cfg | |-- adtxt.cfg | |-- adtxtdt.cfg | |-- gtk.cfg | |-- gtkdt.cfg | |-- menu.cfg | |-- prmenu.cfg | |-- prompt.cfg | |-- txt.cfg | `-- txtdt.cfg |-- menu.cfg |-- prompt.cfg |-- rqgtk.cfg |-- rqtxt.cfg |-- spkgtk.cfg |-- splash.png |-- stdmenu.cfg |-- txt.cfg |-- vesamenu.c32 `-- xfce |-- adgtk.cfg |-- adgtkdt.cfg |-- adtxt.cfg |-- adtxtdt.cfg |-- gtk.cfg |-- gtkdt.cfg |-- menu.cfg |-- prmenu.cfg |-- prompt.cfg |-- txt.cfg `-- txtdt.cfg 3 directories, 60 files Q1. Can the TC-64bit /boot/isolin...

...> ??? ldlinux.c32 > > ??? ldlinux.sys > > ??? linux > > ??? menu.cfg > > ??? NvVars > > ??? prompt.cfg > > ??? rqgtk.cfg > > ??? rqspkgtk.cfg > > ??? rqtxt.cfg > > ??? setup.exe > > ??? spkgtk.cfg > > ??? splash.png > > ??? stdmenu.cfg > > ??? syslinux.cfg > > ??? txt.cfg > > ??? win32-loader.ini > > > > except that PATH into the bios files is a problem for efi, > > or is it? > > I just realized maybe efi can avoid that file, and so path to bios > files is fine. for bios: # target...

David Christensen wrote: > This is how I prepared an ADATA USB Flash Drive 4 GB: ... install-mbr /dev/sdb ... [Rest of very clear description snipped.] What's that? That desn't exist in the Debian I'm running. Otherwise you gave a very good description of what you're doing. >From another message: > Please provide a URL for documentation that explains how to build a >

...? ??? libutil.c32 ? ? ??? vesamenu.c32 ? ??? SYSLX64.CFG ??? exithelp.cfg ??? f10.txt ??? f1.txt ??? f2.txt ??? f3.txt ??? f4.txt ??? f5.txt ??? f6.txt ??? f7.txt ??? f8.txt ??? f9.txt ??? initrd.gz ??? linux ??? menu.cfg ??? prompt.cfg ??? rqtxt.cfg ??? splash.png ??? stdmenu.cfg ??? txt.cfg + cat target/boot/syslinux/syslinux.cfg # D-I config version 2.0 # search path for the c32 support libraries (libcom32, libutil etc.) PATH ./ DEFAULT debian PROMPT 0 LABEL debian CONFIG ../../debian.cfg ../../ + cat target/debian.cfg include menu.cfg default vesamenu.c32 prompt 0...

...gt; ??? initrd.gz > ??? ldlinux.c32 > ??? ldlinux.sys > ??? libcom32.c32 > ??? libutil.c32 > ??? linux > ??? menu.cfg > ??? NvVars > ??? prompt.cfg > ??? rqgtk.cfg > ??? rqspkgtk.cfg > ??? rqtxt.cfg > ??? setup.exe > ??? spkgtk.cfg > ??? splash.png > ??? stdmenu.cfg > ??? syslinux.cfg > ??? txt.cfg > ??? vesamenu.c32 > ??? win32-loader.ini > > carl at twist:/media/carl/Debian Inst$ cat syslinux.cfg > # simple syslinux.cfg > DEFAULT linux > LABEL linux > KERNEL linux > INITRD initrd.gz Thank you for posting the info. I...

I want to eufi boot this image: http://cdn-fastly.deb.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/boot.img.gz there is a bug against it: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913523 I'd like to fix the resulting usb stick for my use, and also fix it in a way that can be used to fix the upstream bug. I'm trying to follow the guids

....c32 (2.2 KB) Extracting: F:\EFI\BOOT\pxechn.c32 (14.6 KB) Extracting: F:\EFI\BOOT\reboot.c32 (1.9 KB) Extracting: F:\EFI\BOOT\rosh.c32 (16.6 KB) Extracting: F:\EFI\BOOT\sanboot.c32 (2.3 KB) Extracting: F:\EFI\BOOT\sdi.c32 (3.9 KB) Extracting: F:\EFI\BOOT\splash.png (4.1 KB) Extracting: F:\EFI\BOOT\stdmenu.cfg (509 bytes) Extracting: F:\EFI\BOOT\sysdump.c32 (18.5 KB) Extracting: F:\EFI\BOOT\syslinux.c32 (10.1 KB) Extracting: F:\EFI\BOOT\tails.cfg (219 bytes) Extracting: F:\EFI\BOOT\vesa.c32 (4.2 KB) Extracting: F:\EFI\BOOT\vesainfo.c32 (2.9 KB) Extracting: F:\EFI\BOOT\vesamenu.c32 (31.6 KB) Extractin...

On Mon, Dec 3, 2018 at 10:02 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > Now it is just dd, mkfs and copy in the files we need. > > One less thing to worry about keeping versions consistent. > > > > > > I just noticed those 2 files that were added by > > > > syslinux -i boot.img > > > > (right?) > > > >

On 3/3/2016 07:43, Pete Batard via Syslinux wrote: > [...] as far as I am concerned, 'A "version" such as "6.03" [is not] > enough'. [...] I'd like to help to improve Syslinux with regards to version-related concerns. Having typed that, perhaps we could discuss your (or Rufus') specific needs, in parallel? Do I understand correctly that the primary