similar to: Boot ISO Using Memdisk on UEFI ONLY System

What ISOs are we talking about? If it is linux, they can usually be booted from UEFI. On Tue, 12 May 2020 at 19:10, Justin Rivers via Syslinux <syslinux at syslinux.org> wrote: > > Hello, > I'm sorry to bother, but was hoping that someone might be able to help me > with this situation. I have a multiboot that I've maintained now for years, > with no issues running on

Hi all, My computer is booted with UEFI and Grub2. I tried to load VHD files with memdisk and boot from there. memdisk is extracted from 'bios/memdisk' in syslinux 6.03 zip file. In Grub2, I executed: linux16 /memdisk harddisk initrd16 /Win10.vhd Then the system frozen at 'initrd16' line. The VHD file is 8192MB, fixed image. I also tried to boot a small floppy disk (FreeDOS), and

Im a long time PXE boot fan. I use it for wimbooting windows PE, linux images via http, and memtest mainly. Ive got it nicely customised with my own graphics etc. Then UEFI booting came along. Till now ive been content simply setting bios's to CSM mode and doing my thing.... Ive had another go at EFI PXE booting and can now get the menus and grahics from syslinux working, but I cannot get

Hello, I'm investigating ways to boot a DOS floppy image stored on the FAT32 EFI System Partition using Syslinux and Memdisk. The system will be running Win8 using UEFI mode (GPT disks) and secure boot off. Change the Windows efi boot loader is the easy part... With the current syslinux's alpha version (6.0), is it possible to boot the syslinux's efi module from the FAT32 EFI

Hello! I'm trying to chain a ISO file in UEFI mode, Do you have any release for Memdisk for UEFI? If you don't, what do you recommend me? Thanks a lot! Diego

> Im a long time PXE boot fan. I use it for wimbooting windows PE, linux > images via http, and memtest mainly. > > Ive got it nicely customised with my own graphics etc. > > Then UEFI booting came along. Till now ive been content simply setting > bios's to CSM mode and doing my thing.... > > Ive had another go at EFI PXE booting and can now get the menus and

I am getting the following error with memdisk when attempting to boot. I am booting UEFI device using elilo.efi and loading a elilo.conf file with below configuration. Attached is also a print sceen of the error I am getting about memdisk. # force chooser to textmenu chooser=textmenu delay=20 prompt # # the files containing the text (with attributes) to display # message=textmenu-message.msg

Hi. I prefer using the syslinux boot loader and recently undertook a project of creating a multiboot USB drive that boots using syslinux. The aim is to create a medium from which various live linux environments can be run for things like system maintenance, installation, and perhaps demonstration. I anticipate using this multiboot USB drive on mostly legacy, BIOS systems, if that matters. As

Hi all, I currently use iPXE to load memdisk and, subsequently, a FreeBSD disk image to perform an OS installation to disk. This works great in BIOS, but upcoming requirements make UEFI a prerequisite. Because memdisk is not UEFI-aware, new UEFI-aware media is necessary. The current plan is to integrate the installation scripts (currently in the hard drive image) into a bootable FreeBSD ISO

Hello, I am trying to make a usb stick full of utilities. However some of the utilities do not use syslinux, and are iso's. Is there any method available for turning the iso into a bootable drive img to be used with memdisk? -- Dimeneira aka Dime

I have used syslinux 4.0x and earlier for many years, with Puppy Linux and more recently Quirky Linux. Though, my knowledge of all the capabilities of syslinux remains rudimentary. I am new to UEFI. I recently got my hands on a win8.1 laptop, 64-bit system, and decided to tackle booting Quirky on it, from a USB stick. I turned off Secure Boot. I wrote /usr/share/syslinux/gptmbr.bin to the flash

Ady, Thanks for taking the time to respond to my lengthy post. Here are my answers: On 11/5/14, Ady <ady-sf at hotmail.com> wrote: > >> I have used syslinux 4.0x and earlier for many years, with Puppy Linux >> and more recently Quirky Linux. Though, my knowledge of all the >> capabilities of syslinux remains rudimentary. >> >> I am new to UEFI. I recently

Hi, I installed CentOS 7.4 on a modern Lenovo ThinkSystem SR630 server which uses UEFI. So far so good CentOS 7.4 works fine so then I went on to install the Xen hypervisor by following the instructions from the wiki (https://wiki.centos.org/HowTos/Xen/Xen4QuickStart). Unfortunately when I reboot after having installed the xen package the system does not boot into "CentOS Linux, with Xen

> I have used syslinux 4.0x and earlier for many years, with Puppy Linux > and more recently Quirky Linux. Though, my knowledge of all the > capabilities of syslinux remains rudimentary. > > I am new to UEFI. I recently got my hands on a win8.1 laptop, 64-bit > system, and decided to tackle booting Quirky on it, from a USB stick. > > I turned off Secure Boot. > > I

Hi all, I need some suggestions or hints which syslinux version I shall use. The main focus will be on PXE boot. I have to upgrade due to (expected) performance problems (tftp), so I will swich to HTTP boot ! existing system: - syslinux version 4.05 (tftp only) - used modules : pxelinux.0, memdisk, vesamenuc32, patched startrom.0 - I boot .nbi , .iso, .ima and sometimes files (clonezilla etc.) -

Hi Peter, I'm using isolinux and memdisk to create a multiboot rescue cd for personal use as described on Bart's page (www.nu2.nu). One boot item is to boot DOS 7.1 from Win98SE with a lot of other staff for emergencies. This DOS bootimage puts all necessary stuff into it's own ramdisk (XMSDSK). Some progs on the ramdisk needs access to floppy drive A: and unfortunately I've no

Peter, I am trying to get memdisk to work with grub and have run into a problem. Grub loads memdisk into the 0x9000 segment and then starts it at location 0x90200. I run into problems in the first printf statement. It turns out that printf uses a switch statement that compiles into a jump table. When I reach this jump table, I believe the code is jumping into hyperspace due to the jump table

I need to create one bootable UEFI disk partition that contains all the space on the disk. The steps must work in a shell script. Ideally with syslinux/extlinux but if not possible then grub. How to do this? Surely it should be dead easy, a handful of lines? Nothing I do works. This is what I have so far: DISK_DEVICE_NAME_CURRENT_OS=hda echo remove all partitions sudo /usr/local/sbin/sgdisk -Z

Ady Ady via Syslinux wrote: > >> However, I have just tested the exact same boot procedure using a Dell >> laptop (Latitude 7480) - and it all worked without a problem - that is, >> syslinux.efi and ldlinux.e64 were downloaded without a problem - and >> from a tcpdump, there was *no* DHCP transaction between downloading >> syslinux.efi and ldlinux.e64 >>