search for: spkgtk

...the later > > amendment in order to workaround a known bug in the PATH directive. > > moving the binaries into boot/syslinux > and changing the path in /syslinux.cfg > > path /boot/syslinux > > doesn't break anything... > > target/ > ??? adgtk.cfg > ??? adspkgtk.cfg > ??? adtxt.cfg > ??? boot > ? ??? syslinux > ? ??? libcom32.c32 > ? ??? libutil.c32 > ? ??? vesamenu.c32 > ??? disk.lbl > ??? exithelp.cfg > ??? f10.txt > ??? f1.txt > ??? f2.txt > ??? f3.txt > ??? f4.txt > ??? f5.txt > ??? f6.tx...

...isolinux/isolinux.cfg. 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 m...

> > > > 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

...y tree, the list of file > names in each directory and the complete resulting content of all the > cfg files, without pointing us to a script? carl at twist:/media/carl/Debian Inst$ tree -d ??? EFI ??? BOOT ??? syslinux carl at twist:/media/carl/Debian Inst$ tree ??? adgtk.cfg ??? adspkgtk.cfg ??? adtxt.cfg ??? disk.lbl ??? EFI ? ??? BOOT ? ? ??? BOOTX64.EFI ? ? ??? ldlinux.e64 ? ??? syslinux ? ??? cat.c32 ? ??? chain.c32 ? ??? cmd.c32 ? ??? cmenu.c32 ? ??? config.c32 ? ??? cptime.c32 ? ??? cpu.c32 ? ??? cpuid.c32 ? ??...

...t; posted (and that you followed) in a prior email, plus the later > amendment in order to workaround a known bug in the PATH directive. moving the binaries into boot/syslinux and changing the path in /syslinux.cfg path /boot/syslinux doesn't break anything... target/ ??? adgtk.cfg ??? adspkgtk.cfg ??? adtxt.cfg ??? boot ? ??? syslinux ? ??? libcom32.c32 ? ??? libutil.c32 ? ??? vesamenu.c32 ??? disk.lbl ??? exithelp.cfg ??? f10.txt ??? f1.txt ??? f2.txt ??? f3.txt ??? f4.txt ??? f5.txt ??? f6.txt ??? f7.txt ??? f8.txt ??? f9.txt ??? g2ldr ??? g2ldr.mbr ??? gtk.cfg ???...

...|-- txt.cfg | `-- txtdt.cfg |-- 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...

...known bug in the PATH directive. > > > > moving the binaries into boot/syslinux > > and changing the path in /syslinux.cfg > > > > path /boot/syslinux > > > > doesn't break anything... > > > > target/ > > ??? adgtk.cfg > > ??? adspkgtk.cfg > > ??? adtxt.cfg > > ??? boot > > ? ??? syslinux > > ? ??? libcom32.c32 > > ? ??? libutil.c32 > > ? ??? vesamenu.c32 > > ??? disk.lbl > > ??? exithelp.cfg > > ??? f10.txt > > ??? f1.txt > > ??? f2.txt > &g...

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 >

...e > > > cfg files, without pointing us to a script? > > > > carl at twist:/media/carl/Debian Inst$ tree -d > > ??? EFI > > ??? BOOT > > ??? syslinux > > > > carl at twist:/media/carl/Debian Inst$ tree > > ??? adgtk.cfg > > ??? adspkgtk.cfg > > ??? adtxt.cfg > > ??? disk.lbl > > ??? EFI > > ? ??? BOOT > > ? ? ??? BOOTX64.EFI > > ? ? ??? ldlinux.e64 > > ? ??? syslinux > > ? ??? cat.c32 > > ? ??? chain.c32 > > ? ??? cmd.c32 > > ? ??...

...ory and the complete resulting content of all the > > cfg files, without pointing us to a script? > > carl at twist:/media/carl/Debian Inst$ tree -d > ??? EFI > ??? BOOT > ??? syslinux > > carl at twist:/media/carl/Debian Inst$ tree > ??? adgtk.cfg > ??? adspkgtk.cfg > ??? adtxt.cfg > ??? disk.lbl > ??? EFI > ? ??? BOOT > ? ? ??? BOOTX64.EFI > ? ? ??? ldlinux.e64 > ? ??? syslinux > ? ??? cat.c32 > ? ??? chain.c32 > ? ??? cmd.c32 > ? ??? cmenu.c32 > ? ??? config.c32 > ? ??...

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