similar to: syslinux 2.10 - boot floppy forgets the boot parameters

Hello, I'd be very grateful if someone can help me with the process of creating bootable floppy images to be used with isolinux/memdisk. I usually do the following: label image kernel memdisk append initrd=/bootdisk/image.img floppy (lines in isolinux.cfg file) Sometimes I pass memdisk the c/h/s parameters, depending on the image size. I have learned from this mailing list how to

There is a maximum of 255 characters of parameters you can pass to the kernel. At least that's what I recall, but I may be wrong. -----Original Message----- From: Roberto De Leo [mailto:deleo at unica.it] Sent: Thursday, October 03, 2002 5:19 PM To: syslinux at zytor.com Subject: [syslinux] maximum number of characters in APPEND Hi, I wonder whether there is a maximum number of

When I boot from a MoviX cd, Isolinux gives an error: isolinux: Image checksum error, sorry... Boot failed, press a key to retry.... I searched the internet, but I couldn't find a solution, in the changelogs, there where no changes reported on this problem my specs are: AMD k6-2 300 Riva TNT2 M64 32MB 64 MB RAM RedHat and Knoppix work fine on this PC Somebody on the MoviX forum had the same

I have released SYSLINUX 2.10-pre2. I *really* would like testing reports for this one, especially ISOLINUX, since I've included Knut Petersen's fix for Award BIOSes... Changes in 2.10: * MEMDISK: Handle images compressed with zip as well as with gzip. Some Windows-based image tools apparently generate these kinds of images by default. Patch by Patrick

Hi - daft one for Friday morning coffee break: I have been trying to mount floppies on a couple of CentOS5 servers - the usual "mount /dev/fd0 /mnt/floppy" (yes, /mnt/floppy exists!). On both servers, the mount command just doesn't come back and I have to hit CTRL-C. I have tried different media and also changed the floppy drive on one server, /dev/fd0 is seen as present on both

I am trying to get a programmable database working, and what I see as the only solution is a prog like access via wine. The problem is my computer that I wish to install it on has no floppy drive, and this copy (the first version?) comes with about 10 floppies. -- John R. Sowden AMERICAN SENTRY SYSTEMS, INC. Residential & Commercial Alarm Service UL Listed Central Station Serving the San

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

Hello, when testing FreeBSD-7.1-BETA i discovered that the floppy disk controller doesn't work correctly. Trying to format a floppy (perhaps with bad blocks) i get: Processing fdformat: ioctl(FD_FORM): Device not configured instead of the normal E letter. I then checked the same problem is present on FreeBSD-6.3 and it has been reported by Beech Rintoul (*) in 2006! Of course the floppy disk

Yes, really. I've got hundreds of the damn things here at home, and I want to go through them and get rid of them all. But... to do that I want to read them. I have both a 5.25" and a 3.5" drive, both are plugged in, but in the BIOS, all I see is the 3.5". Fine, I figure I'll take care of those. Nope. I see /dev/fd0 once I've booted up, but neither konqueror nor

Hello, i want to encrypt my HDD's with GELI (not the root-fs, though). I want to do the encryption without password, just with a key. The key should be stored in a floppy disk, and the read should be read automatically on boot, from the floppy. There is a problem here, because GELI initializes _before_ mounting the disks from /etc/fstab (for obvious reasons, of course). So GELI is not able

Hi, I've got a couple of questions, I'm trying to get syslinux 2.10 to work on my Apacer Handy Steno TN202 128MB flash drive, I'm getting... root at will # syslinux /dev/sdb1 Total number of sectors not a multiple of sectors per track! Add mtools_skip_check=1 to your .mtoolsrc file to skip this test ...but if I try the same command on a mandrake box the syslinux command is

Dear Sir, I have everything set up on my red hat Linux 7.1 linux box. For sometime I could mount cd's and floppies automatically, but now something seems to have gone wrong. I can't mount my floppy(/dev/fd0) and cdrom(/dev/cdrom) manually or automatically. At startup it says ... /dev/fd0 is not a valid block device. /dev/cdrom is write protected...mounting read only! mount: No

Hi there, http://www.seagate.com/support/disc/download/seatoold_en.exe Seagate offers a Windows executable (needs Win98 or better, 1,9MB) that should create 2 bootable floppy disks that contain a harddrive check program. Invoking "wine seatoold_en.exe" works, but when the floppy should be written, an error occurs "insert 1.44 MB...click retry". I tried to mount a DOS

Hi all, If you are one of the ones who has had problems with 2.10 but not with 2.09; especially for SYSLINUX (as opposed to PXELINUX/ISOLINUX), please try out 2.11-pre2 and let me know if it works or not: ftp://ftp.kernel.org/pub/utils/boot/syslinux/Testing/ -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

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

I have occasional problems booting kernel boot floppies made with syslinux-2.04/2.05. The symptom is that syslinux loads an initial part of the kernel image and then halts with Boot failed: please change disks and press a key to continue. Observations: 1. It's not a media problem. I've switched floppies and reformatted them, but the failure persists. 2. It's not a BIOS problem.

Hello all, I just installed syslinux 2.10 on my usb-stick. It still boots then, but doesn't load initrd.gz (same config file..). Reverting back to syslinux 2.09 works fine, eg: initrd.gz is loaded. Something changed in initrd handling code? greetz, Jaap Crezee NB I am willing to share you more information or hints how to solve the problem. I am using kernel 2.6.7-bk20

Ok, despite what I said yesterday I decided to release a 2.08-pre10. The only difference over 2.08-pre9 is that I have added a small program in the "samples" directory called chain.c32. This allows chainbooting local floppies and hard disks: chain fd0 ; Chainboot the first floppy drive chain hd0 ; Chainboot the first hard drive chain hd1 3 ; Chainboot partition 3 on the second

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