similar to: Syslinux fails with floppy emulation

Thomas Schmitt wrote: > So if we had a MBR which prints the content of the first 512 read bytes > we could tell whether they are block aligned and from which block they > come. Ok. I'll try. Is it the isohdppx or isohdpfx (or both) that is relevant? Meanwhile I have a hacked isohdppx.bin that prints: G if GPT M if MBR <nothing> if no partition info E if EBIOS C if not EBIOS

Hi, Ady wrote: > [hard disk emulation boot image works with VirtualBox] For a reader of the UEFI specs this comes very unexpected. Together with the report of Pascal that a hard-disk-emulation works even with mkisofs option -b (i.e. Platform Id x86 BIOS) it appears that the UEFI implementation treats the El Torito boot image like the whole device, regardless of Platform Id. On (virtual)

Hello, I'm trying to create and boot a Win98SE-DOS OS through Hard Disk emulation. My src files are from a Win98SE 1440K floppy image file, with a x86 boot sector (dl'd from the net - I have no floppy drive and a slow net link 3.2KB). I don't know what to put into the partition boot record of my image and how to load dos.bss properly (the docs explain for floppy images not for HD

Changes in 3.10: * gcc 4.0.1 compilation fixes. * Add support for querying the PCI BIOS in libcom32 (used by ethersel et al.) * Fix PCI handing (ethersel etc) on several old chipsets (and VMWare.) * Try to deal with systems with broken EBIOS. * New API call to do "localboot". * New API call to query features.

I tried to use memdisk 2.06 to boot a floppy image on my notebook which doesn't have a floppy drive. The boot failed, because the bootstrap code tried to reset the floppy drive (int13, ah=00). Memdisk passes reset calls on to the original int13 handler, which returns failure, because there is no floppy drive to reset (#1). Also i noted that some boot records (notably some created by

Is it possible to boot a no-emulation boot image from ISOLinux? I am particularly interested in having the WinXP Install CD, as one of the boot images in ISOLinux. - Murali ################################################################ # Ry 254, Ryerson Hall, # Ph : +1 773 702-1031 (Off) # # 1100 E 58th Street # +1 773 575-4836 (Cell) # # Chicago, IL - 60637, #

Hi as described on the syslinux pxe webpage: A multi-hardware boot floppy is included with Windows Server 2000 and 2003. A company called Argon Technology used to offer a free-as-in-beer updated version, but is seems to have gone fully commercial. This floppy (which can also be burned to a CD using El Torito in floppy-emulation mode), is known to work with PXELINUX 2.03 or later only I'm

Hi, Is it possible to somehow mix syslinux and isolinux so that I boot from a floppy disk and then load the kernel+initrd from a CD? Reading the docs it seems to me that syslinux and isolinux are quite independent tools, they work differently, the installation method is different etc... so I'm afraid I'll get a negative answer... but I hope I won't :-) Thx, Egmont

After formatting a floppy to MSDOS format and using syslinux /dev/fd0, I successfully installed ldlinux.sys to the root directory of the floppy. Then I created a syslinux.cfg under the root directtory of this floppy to load the linux kernel in my first hard disk, 3rd partition, boot folder. The file system of this partition is ext3. The floppy has a FAT file system. This config file is listed

Thomas Schmitt wrote: > My main point of interest is which block is really loaded as first one > of isolinux.bin. [Program snipped.] > (It could be shorter if i did not insist in big endian words.) Why insisting? Anyway appended is a dumper version. I could put up a binery version if needed. Let me know if so. -- MartinS /*

> > I ponder whether it would be possible to create a diagnostic MBR > which does not necessarily have to boot but rather tells what the > isohybrid MBR would perceive: Presence of partition table, > EBIOS or CBIOS, block address used with INT 13, content of the block > read by the first INT 13, ... > > One could preserve the isohybrid MBR of an ISO and replace it by >

> Hello, > > Ady via Syslinux said on Mon, Apr 06, 2015 at 09:57:02PM +0300: > >Can 'syslinux.efi' v.6.03 boot some media formatted with ISO9660? > > Not at this time, no. > > It took me quite some time to find that :-( Google didn't really help. > > I'd like to get a bit more details on this issue: > > 1/ Using syslinux.efi for PXE

On Fri, Mar 24, 2017 at 05:38:31PM +0100, Thomas Schmitt via Syslinux wrote: > isohdpfc pushes the CX value to the stack which it gets from INT 13 AH 41. > Quite surely bit 0 of that CX is not set. But bit 2 "Enhanced Disk Drive" > could be set. > https://en.wikipedia.org/wiki/INT_13H > > I understand on David's BIOS after > > andw $1,%cx

At first I thought, I was dealing with the known EBIOS/CBIOS-problem. The symptom was exactly the same (hangs at ...EBIOS). As 3.10-pre8 and 3.10-pre9, in contrary what was mentioned in the ML, did not bring any improvement, I looked deeper into what could be my specific problem. I found out that the program just halted at 'cmp [esi],edx' (line 658; ldlinux.asm 3.10-pre9)! By replacing

(Sorry, Outlook webmail prohibits me from proper replying/quoting) >it has the nice effect that you can load the El Torito >CD-ROM driver. Which seems logical if you boot a kernel (like Linux, or Memdisk with an imagefile), but not when doing a local boot (diskette/harddisk) In other words: boot from cdrom, and if you then load a disk-image, eltorito.sys should load. If not loading a

I am in the process of trying to update a bootable Linux CD that I initally built some time ago using RedHat 7.3 and syslinux 1.x (I believe that x = 52, but this doesn't seem to be relevant). In order to do this, I first built a floppy disk image and made it bootable by running "syslinux -s" on the image; then I incorporated this image into a CD using "mkisofs -b boot.img -c

eparam would only be used if EBIOS is available. If it is not, then there is no reason to allocate eparam. Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> --- com32/lib/syslinux/disk.c | 10 +++++----- 1 files changed, 5 insertions(+), 5 deletions(-) diff --git a/com32/lib/syslinux/disk.c b/com32/lib/syslinux/disk.c index 093751a..d96acbf 100644 ---

Hi, i am looking now at the code which i assume loads the rest of isolinux.bin. The entry point for program execution from the MBR is obviously at http://git.zytor.com/syslinux/syslinux.git/tree/core/isolinux.asm#n186 (Do i get it right that this is the Intel syntax ? (Gronfff)) If POP yields the victim of the most recent not yet popped PUSH, then this does not look correctly coordinated

Hi, Ady wrote: > the UEFI specs do state that the ESP is supposed > to be set/used as no-emulation mode > ... > the UEFI specs should tolerate / accept this situation, rather than < restricting the ESP to no-emulation mode. My criticism towards this UEFI implementation is that it probably cannot serve as realistic test bed for the first stage of UEFI booting. It seems far too

eparam will only be used if EBIOS is available on the underlying disk. If not so, then there is no reason to allocate eparam. --- com32/lib/syslinux/disk.c | 13 +++++++------ 1 files changed, 7 insertions(+), 6 deletions(-) diff --git a/com32/lib/syslinux/disk.c b/com32/lib/syslinux/disk.c index 093751a..554bed3 100644 --- a/com32/lib/syslinux/disk.c +++ b/com32/lib/syslinux/disk.c @@ -73,7