similar to: SYSLINUX 3.20-pre1

Hi, I'm trying to boot Feature Tool 2.08 (free download from http://www.hitachigst.com/hdd/support/download.htm) from a pen drive via memdisk. QEMU can boot the pen drive all right, my ThinkPad can't: Loading ftool208.img.........................ready. MEMDISK 3.53 2007-11-17 Copyright 2001-2007 H. Peter Anvin e820: 0000000000000000 000000000009f000 1 e820: 000000000009f000

This isn't strictly speaking a SYSLINUX release, it's a change to MEMDISK and mkdiskimage to allow the creation of hard disk images with DOSEMU headers. This should make it easier to create bootable DOS hard disk images under DOSEMU. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

Some additional fields from the EDD-4 spec. draft for the Device Parameter Table have been added into the structure in setup.c and memdisk.inc. These were added in the hopes of resolving a FreeDOS MEMDISK bug on IBM ThinkPads. --- memdisk/memdisk.inc | 11 +++++++++++ memdisk/setup.c | 10 ++++++++++ 2 files changed, 21 insertions(+), 0 deletions(-) diff --git a/memdisk/memdisk.inc

>information a bit closer; it'd find that it's marked accordingly. UDMA2.SYS author now worked around it, it seems you do something with "DPTE" in isolinux.asm but not using it (probably for memdisk or direct floppy/harddisk emulation?). also something about EDD v1.1 and v3.0 specifications and setting bits to 1. Anyway, the driver works now on: BIOS -> cdrom ->

(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

Hi We have a couple of FSC Computers here which seem to have a very strange bios. I am trying to boot a MS-DOS disk to flash an Scsi Raid controller. Since the computer doesn't have a floppy anymore I tried syslinux from an usb stick. The menu loads fine but I cannot boot disc images with memdisk on this computer. It works fine on others, of course. But now comes the weird part, if I use the

On Thu, Feb 2, 2017 at 1:26 PM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > Hi all, > > > > I have observed a problem where, under legacy BIOS booting mode on the > > DL360g9, memdisk fails to execute. The same mechanism works fine on the > > DL360g8. The system displays the below on the console and ceases to > > respond and must be

Hi all, I have released SYSLINUX 3.35-pre5 to the Testing directory; this is a release candidate and I intend to release this as 3.35 early next week unless I hear of any showstopper bugs, so please, pretty please, try it out. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ kernel.org has been overloaded lately, so it might take a while to show up. Changes in 3.35: *

Okay, nothing like user mail at 3 am to keep one awake... I have implemented a filename-based syntax for downloading from an alternate TFTP server in PXELINUX. If the filename starts with IP address:: it will: a) Download from the alternate TFTP server; b) Suppress the common pathname prefix. I was considering also adding a configuration file option to set the default TFTP server, but I

Hi all, I have observed a problem where, under legacy BIOS booting mode on the DL360g9, memdisk fails to execute. The same mechanism works fine on the DL360g8. The system displays the below on the console and ceases to respond and must be power cycled. Updating the firmware didn't help. There didn't appear to be any similar issues on the mailing list unless I missed them. Wondering if

I have added the "raw" mode support to MEMDISK, and released it as 2.13-pre1. Please see memdisk.doc. Unfortunately it turns out the command-line parsing in MEMDISK 2.12 is completely buggered, so I'm afraid I'm probably going to have to release a 2.13 in very short order. Therefore, if you can, please try out this prerelease -- especially MEMDISK -- and give me the thumbs

Hello, I am using the pxelinux.0 and memdisk files from distribution syslinux-3.36. I am no longer able to access the real floppy disk drive B: instead I just get a mirrored copy of the emulated floppy disk A: The default config file is as follows label 1 kernel memdisk append initrd=kd202.img I was previously using the sysliunx-3.20 distribution which gave me access to the real floppy

Hello, I'm experiencing an issue where if I use vesamenu.c32 with PXELINUX 6.03 when network booting a virtual machine hosted on VMware ESXi 6.0, it hangs (the version message is printed and then nothing - the VM has to be powered off and back on again). This happens no matter if I choose the E1000 network interface or the VMXNET3 network interface when creating the VM. The same problem

I am trying to PXE boot an ISO image using ISOLINUX. I am starting small just trying to get anything working but seem to be having problems. I followed the instructions on the isolinux page (http://syslinux.zytor.com/iso.php) but still cannot get it to work. I can get the ISO image to try to load but then it stops at the booting message. Any help would be greatly appreciated. Here is

A kind request for help please. MEMDISK is causing an issue with the Dell OptiPlex GX280 and GX620 platforms. Booting a PC-DOS/Ghost, disk image is successful (and proper) when using version 3.83. See results below: MEMDISK 3.83: Ramdisk at 0x07eeaa00, length 0x007bc000 command line: initrd=images/ghostclient/280_620/osbootc.img BOOT_IMAGE=memdisk MEMDISK: Image seems to have fractional end

hpa, Seeing your post about 3.71, I wanted to get a message out even though I don't have the stats right now. I am having a problem with memdisk with a lot of shuttle computers, but also affects a variety of other hardware (low though, 5%? less?). The image that I can most reliably test against is the Hitachi Drive fitness Test.

Hello, Thanks very much for your suggestions. I have double checked that all .c32 files are from the same version of syslinux. What I don't know - I only put those .c32 files I have in there on the basis of trial and error - is what .c32 files are actually needed for menu.c32 and/or vesamenu.c32. I thought perhaps there might be a .c32 file missing that I needed to put in there (though

After a couple of very late nights I actually have a VERY preliminary test of the rewritten SYSLINUX available for preview. However; don't expect it to do anything miraculous yet; the testing it has gotten can best be described as infinitesimal. In theory, though, it should now support EDD and FAT32, as well as FAT filesystems with very large clusters (up to 64K). NOTE: The Win32

I have a USB flash drive that I'd like to image, and then load that image via pxelinux and memdisk. The flash drive was formatted under Windows 98 SE as FAT, and boots just fine on its own. The PXE boot process gets as far as loading the image via memdisk, but then when the boot process switches over to the RAM disk, it fails: [...PXE diagnostic information...] Loading boot

It appears that the 3.74 completely broke the "keeppxe" directive -- not due to the command-line parser, but due to mishandling of the flag later. I consider this to be severe enough to do a short-cycle 3.75. As a result, I would like help with: a) are there any other bugs that snuck through? b) once I have a 3.75-pre1, I would really appreciate help testing it. The goal is to have