similar to: 1992k 2m floppy

Hi! A friend of mine has tried a PXE floppy (build from the new etherboot 5.3.12) to load PXELINUX.0; a menu voice of the pxelinux.cfg use the LOCALBOOT statement. Selecting this statement, the PC retry to boot from the floppy... is this normal? The user expected that LOCALBOOT would have tried the NEXT boot device (ie CDROM or HD), not the FIRST boot device (the floppy)... (note: this has

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 =

syslinux 3.11 (from debian's 3.11-3 package) does it job. The machine boots as expected with an 1.44 floppy. Yet the floppy driver's led doesn't turn off. 1) Is this a syslinux issue? 2) Can I safely remove the boot floppy (media) without dameging it? From memory: $ cat syslinux.cfg say linux 2.6.14 (probably with debian modifications) default linux append root=/dev/nfs

Hello syslinuxers I'm stuck with a scientific problem which gives me headaches: I have a laptop (Gateway MX3410) which has a SD memory card reader. Recently an interesting thought crossed my mind: why don't I setup a 2GB SD card as a harddrive and put some rescue tools on it. So I dug on the net and I came across the idea of using memdisk to boot floppy images without the need of a

Hi, It is becoming a bad habit for big OEM vendors to sell computers & servers without floppy drives. Unfortunatly both Windows and Linux (RedHat) need a floppy drive to load storage drivers etc. during installation. This is what I was thinking: Use ISOLINUX and MEMDISK to load a floppy image of a driver disk into memory as a viritual floppy drive "A:"/"/dev/fda" And then

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

Hi, I stumbled on a rather odd problem. A brand new HP Compaq dx2200 computer didn't want to boot up pxelinux+memdisk image. The computer just gave "Disk I/O error" and stopped there. Workaround was rather simple... Just attach regular floppy drive to the motherboard and everything started working fine. I tried with older 2.05 (pxelinux+memdisk) and newer 3.31. Both produced

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

I have been trying to find the information by searching through the archives and google, so I am sorry if this question has been asked before I just have not been able to find an answer. I have a syslinux boot floppy which loads to the boot prompt, I wish to load a .gz image which is on my hd0 0 by using memdisk as the kernel. I have tried to kernel memdisk append root=/dev/hd0 0 (also just

I would like to be able to create a 2.88MB bootable floppy image to hold the kernel and initrd -- will be used for automated install. In various newsgroups there have been many posting attempting to describe how to achieve this, but none of them is complete. Can syslinux be used to achieve this? What about memdisk? Thank you in advance. Fet

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

I'm reading the docs accompanying SYSLINUX where it says:- ++++ CREATING A BOOTABLE LINUX FLOPPY +++ In order to create a bootable Linux floppy using SYSLINUX, prepare a normal MS-DOS formatted floppy. Copy one or more Linux kernel files to it, then execute the DOS command: syslinux [-s] a: Now before I run this program, I'd like to know which 'one or more Linux

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 list, I've used sys & pxelinux now many times, it's really a useful toy. I found esp. syslinux very helpful as it allows to COMPLETELY boot from multiple disks. However, I could never use a 'vanilla' syslinux for that. I'm doomed to use Distributor patched versions, which I don't really like. Why is that? Read on: Well, I can't manage to boot of a 1.44 MB

Hi. We've been using PXELINUX for years, to kick off OS installations (floppy images) and booting assorted tools. The addition of ISO support in memdisk opened up some new alternatives that we also use, e.g. booting WinPE ISO images over PXE. Today I downloaded a BIOS for a HP EliteBook 8440p and discovered that the BIOS file is 3 MB. I could probably squeeze it onto a 2.88 MB floppy image

Hi, The link given in your http://syslinux.zytor.com/pxe.php#config page points to the http://www.argontechnology.ca/rbfg/index.shtml site. This site talks only of Win2k and .Net server. There is no mention of GNU/Linux. Is it possible to use rbfg.exe to create a pxelinux bootable stack on a floppy. If so how ? Rom-O-Matic has a pxe loadable ROM image. Is there a way to use this to

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

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 would just inject your ROM and EXE (and possibly adjust autoexec.bat to autostart/apply the FW update). It's a minimal FreeDOS FDD image that defaults to a clean boot with

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

Hi! I'm preparing what should be a general "network boot" solution for the ones that needs to do network boot on PC without BIOS support / ROM chips. It supports both PXE (like pxelinux.0) and NBI images. I've prepared a precompiled multi-driver image that can autodetect and handle nearly 30 PCI and ISA NICs. My "remote boot kit" contains the same image in 4