search for: g2ldr

...> ? ??? 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 > ??? initrdg.gz > ??? initrd.gz > ??? ldlinux.c32 > ??? ldlinux.sys > ??? linux > ??? menu.cfg > ??? NvVars > ??? prompt.cfg > ??? rqgtk.cfg > ??? rqspkgtk.cfg > ??? rqtxt.cfg > ??? setup.exe > ??? spkgtk.cfg > ??? splas...

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

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

...? ??? 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 > > ??? initrdg.gz > > ??? initrd.gz > > ??? ldlinux.c32 > > ??? ldlinux.sys > > ??? linux > > ??? menu.cfg > > ??? NvVars > > ??? prompt.cfg > > ??? rqgtk.cfg > > ??? rqspkgtk.cfg > > ??...

...? ??? syslinux.c32 ? ??? vesa.c32 ? ??? vesainfo.c32 ? ??? vesamenu.c32 ? ??? vpdtest.c32 ? ??? whichsys.c32 ? ??? zzjson.c32 ??? 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 ??? 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....

...??? vesamenu.c32 > ? ??? vpdtest.c32 > ? ??? whichsys.c32 > ? ??? zzjson.c32 > ??? 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 > ??? initrdg.gz > ??? initrd.gz > ??? ldlinux.c32 > ??? ldlinux.sys > ??? libcom32.c32 > ??? libutil.c32 > ??? linux > ??? menu.cfg > ??? NvVars > ??? prompt.cfg > ??? rqgtk.cfg > ??? rqspkgtk.cfg > ??? rqtxt.cfg > ??? s...

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

...:09:45 debian -> ./ dr-xr-xr-x 1 root root 2048 2017/01/16 02:09:47 dists/ dr-xr-xr-x 1 root root 4096 2017/01/16 02:09:46 doc/ dr-xr-xr-x 1 root root 2048 2017/01/16 02:09:49 efi/ dr-xr-xr-x 1 root root 2048 2017/01/16 02:09:59 firmware/ -r--r--r-- 1 root root 180335 2017/01/10 13:19:04 g2ldr -r--r--r-- 1 root root 8192 2017/01/10 13:19:04 g2ldr.mbr dr-xr-xr-x 1 root root 2048 2017/01/16 02:09:45 install/ dr-xr-xr-x 1 root root 2048 2017/01/16 02:09:49 install.386/ dr-xr-xr-x 1 root root 4096 2017/01/16 02:09:49 isolinux/ -r--r--r-- 1 root root 268674 2017/01/16 02:11:29 md5sum....

...? whichsys.c32 > > ? ??? zzjson.c32 > > ??? 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 > > ??? initrdg.gz > > ??? initrd.gz > > ??? ldlinux.c32 > > ??? ldlinux.sys > > ??? libcom32.c32 > > ??? libutil.c32 > > ??? linux > > ??? menu.cfg > > ??? NvVars > > ??? prompt.cfg > >...

On 03/18/2017 01:18 AM, Ady Ady via Syslinux wrote: > Some of the things you should / could (re)test / (re)try: > > _ Verify the md5sum of the ISO image. SHA256 verified for downloaded image and for contents of USB flash drive (see below). > _ Is this particular USB device _still_ capable of booting newer > computers? Yes. > What happens if you would try _again_ to boot a