similar to: MEMDISK workaround for no-floppy systems

I apologize for the long delay in testing this. I can only reproduce the problem on fancy new laptops, and those do not stay in my hands for very long. As you may recall, certain floppyless laptops have a BIOS bug which prevented them from working with MEMDISK. Around a month ago, Robert Wruck contributed workaround patches, and hpa included a modified version of them in 2.07-pre1. He asked

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

Hi all, I have pushed out a SYSLINUX 3.32-pre4. This version attempts to work around the "missing floppy drive" issue. If you have systems on which MEMDISK doesn't work without a floppy drive, I would appreciate it if you would test this out. -hpa

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

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

I found that if I do not have a local floppy installed and enabled on my client, I will get the error 'Non-system disk' when I try to boot DOS floppy images. NT or Syslinux floppy images boot fine. If I enable the floppy in the BIOS, then it boots the DOS floppies just fine. Is this normal? Is there a workaround? There are MS-DOS images, so perhaps this is an MS-DOS limitation. --

Im trying to boot memtest86 via pxelinux, memdisk, I found this advice on http://forum.x86-secret.com/viewtopic.php?t=2906 folks are making the image match a floppy size by one of the following: dd if=memtest86+-1.xx.bin of=memtest.img bs=360k count=1 conv=sync or dd bs=360k count=1 conv=sync if=memtest86+-1.xx.bin|gzip > memtest.gz I did the former, it did suppress the warning/errors I saw

I just wanted to chime in and mention that I'm running into the problem with getting a "Non-system disk..." error on a system using a USB floppy when the floppy is not attached when I try to boot the system over the network using memdisk to boot a floppy image. Its actually fairly important to be able to do this, as the architecture of the hardware that I'm working with utilizes

Hi, I was wondering if 1680K floppy support in memdisk was planned, impossible or undesirable :) I noticed RIP is providing a slightly more stuffed 1680K floppy (but no 2880K floppy) and I had hoped memdisk could support this. Kind regards, -- dag wieers, dag at wieers.com, http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power]

I am trying to use syslinux on a floppy image to create a bootable CD. When I boot (on a number of computers) I only get "Boot error", using the image file on a floppy works. I realize the correct way to do this is using isolinux with no emulation but but I need to do this with syslinux :( I've looked into it and older versions of syslinux dont have this problem. From my research

Hi, I am trying to load an disk image as Floppy=1, og B: using ISOLINUX. My Config file reads: ------- Begining Of File ------- KERNEL MEMDISK APPEND raw floppy=1 initrd=CERC6.IMG ------- End Of File ------------ --- MEMDISK Output Snip ------ Ramdisk at 0x03b58000, length 0x00168000 command line: initrd=CERC6.IMG raw floppy=1 BOOT_IMAGE=MEMDISK Disk is hard disk, 1440 K, C/H/S =

>that image under B: or X: or whatever. This will allow us to cross the >size limit of 2.88MB floppies. Ofcourse when I say "mount" I dont expect >memdisk to mount it, just that set things up so that DOS mounts it there. I'm using a 5MB image which emulates floppydisk. label test kernel data/memdisk append initrd=data2/test.img c=80 h=8 s=18 floppy problems are

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! Below is an excerpt from the thread in October. I have the same problem, but my laptop (which is a Brand new HP Compaq NC6230) does not have options in the BIOS to enable or disable floppy support. It just doesn't have one. I assume it leaves it enabled for USB Floppy support, but does not come with the drive. My ISOLinux setup is a UBCD. I tried to make my own, but the lack of

2018-06-26 2:10 GMT+08:00 H. Peter Anvin via Syslinux <syslinux at zytor.com>: > On 06/18/18 13:06, R S via Syslinux wrote: >> The narod.ru images are super outdated (FreeDOS kernel 2028) unfortunately. >> >> If you are interested I could provide a 5MB FDD image template based on >> FreeDOS 2041 kernel (the latest available at that time in 2014) where you >>

Hi, just tried memdisk - it works, even with token-ring network cards! I've some problems with dos 6.22 on one machine, though. This one doesn't have a floppy controller (e.g. linux reports that it didn't find any controller). The Dos 6.22 boot disk is loaded, then the boot sector is started and tells me that it can't load the system (German message: 'Kein System oder

Are their any plans to allow compressed floppy images in later versions of memdisk? Right now Im using isolinux/memdisk on a cd with quite a few floppy images, each image has a different purpose as you can imagine. Many of the floppy imaages are not 'full' and would benifit greatly from compression. Is their a standard(ish) way to compress a floppy image, maybe compress is misleading, Id

Hi, bit of a newbie if I'm honest but was wondering if issue mentioned here: http://syslinux.zytor.com/archives/2006-October/007586.html was ever fixed? basically I have the same issue with the same machine. I have 4 different types of PC's here that i'm trying to boot by USB stick. It works fine on 3 of them, but on the 4th, A HP/Compaq dx2200 MT, memdisk will not boot the .ima

I search for long time to make works ghost floppy image "out of the box" with syslinux without success. The only solution i found is to modify the the file generated by ghost boot wizard. the ghost boot wizard generate a "file.sys" i made (with the help of irc helper) a script to modify this file : you have to put the file.sys without extension as parameter #!/bin/bash

Just for the record, I want to let the list know that I succeeded in booting a modified Universal TCP/IP Network Bootdisk floppy from http://members.iinet.net.au/~bdriver/bootdisk/ I started with a Win98 Bootfloppy from http://www.tobs.uku.co.uk. Then I made a disk image from this, using dd.exe from cygwin. Then I converted this disk image from 1.44MB to 2.88MB with winimage. Then I copied