search for: superfloppies

Hello, are there known issues with some bioses not booting from Superfloppy format? All I get is the Syslinux (c) line and nothing else happens afterwords. Everything works fine if a partition is added to the device. Unfortunately however the target device can not be partitioned. Any hint? Sven -- Why are there so many Unix-haters-handbooks and not even one Microsoft-Windows-haters

...a suggestion in this thread, as well as the approach from the previous paragraph per another suggestion, and personally chose to settle on the previous paragraph as being easier for my particular situation. 9) As an alternative to all this work, if you trust the source, there are mostly blank superfloppies of many different sizes at various websites, for example http://bootcd.narod.ru/images_e.htm . That is, instead of enlarging an existing image, just start with a working one of the size you need. I tried the 11.52mb one in a VM and it booted. Our building's HVAC system mysteriously stopped...

I try two ways to use syslinux for USB key (2GB USB key), and one approach can boot from machine, another approach can not. Could you review the following steps and tell me why #2 can not boot? Thanks very much! approach #1 steps: mkfs.vfat -F 16 -n USB /dev/sdb -I (pay attention, it uses "-I" here) syslinux /dev/sdb (pay attention, it is "sdb", not "sdb1" here)

...--force -f Ignore precautions (DOS/Win32/mtools installers only) Note: geometry is determined at boot time for devices which are considered hard disks by the BIOS. Unfortunately, this is not possible for devices which are considered floppy disks, which includes zipdisks and LS-120 superfloppies. The -z option is useful for USB devices which are considered hard disks by some BIOSes and zipdrives by other BIOSes. $ ./syslinux-git/working-directory/linux/syslinux Usage: ../syslinux-git/working-directory/linux/syslinux [options] device --offset -t Offset of the file system on the...

Hi, this is a forward from the debian bug tracking system, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595170: "syslinux for Windows provides the options -m (write an MBR) and -a (make partition active). These options make it easy to provide instructions for Windows users to make a bootable USB drive: just run "syslinux -m -a" on the drive, then drop some files on the drive

Good day Ercolino, Are you using the ELTORITO.SYS DOS CD-ROM drive driver? You should be, if you're using MEMDISK. You might also enjoy some of the discussion here[1]. Also, as an aside, you can create an 8 MB superfloppy image which could contain your BIOS/firmware upgrade. Maybe search the mailing-list archive for "superfloppy". Have a nice day. - Shao Miller [1]

On 07/15/2014 06:57 PM, Ady wrote: > > Finally, when using MEMDISK to boot floppy images, these images > should not use partial "cylinders". In other words, use exact CHS > values for floppy images, instead of building the images by means of > the desired megabytes size. Then use the selected CHS values as > parameters for MEMDISK. > If you have a proper set

On 07/08/2014 05:55 PM, H. Peter Anvin wrote: > On 07/08/2014 03:05 PM, Alexander Perlis wrote: >> >> Question: what's special about the transition from 8203KiB to 8204KiB? >> Both have CHS=8/64/32 and both involve a fractional end cylinder. > > Fractional cylinders with floppy disks is almost certainly a very bad thing. > Agreed, but that doesn't appear to

I used syslinux 4.03 for my brand new usb-stick (16GB FAT32, no Partition Table). It works, but on some computers i get "boot error". My investigation reveals three bugs in the boot code. Int 13 function 8 destroys the contents of register ES. Ah, now it is corrected in version 4.04 pre 5. Well done. I am happy now. But there are still other bugs. Look on version 4.04 pre 5,

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

> > I am still interested in improving the isohybrid wiki > and will watch for pointers to descriptions of the FAT > production process (with GRUB/GRUB2 if not with SYSLINUX). > > If no such descriptions appear within the next weeks, > then i plan to state in > http://www.syslinux.org/wiki/index.php/Isohybrid#UEFI > > "The SYSLINUX project cannot yet provide

...read, as well as the approach from the previous > paragraph per another suggestion, and personally chose to settle on the > previous paragraph as being easier for my particular situation. > > 9) As an alternative to all this work, if you trust the source, there > are mostly blank superfloppies of many different sizes at various > websites, for example http://bootcd.narod.ru/images_e.htm . That is, > instead of enlarging an existing image, just start with a working one of > the size you need. I tried the 11.52mb one in a VM and it booted. Our > building's HVAC system m...

Hello, CONFIGURATION Syslinux "old": 3.36 Syslinux "new": 5.01 (B)LFS i686-pc-linux-gnu 3.8.0 Machine #1: ASUS P5E-VM HDMI. Latest BIOS. circa 3 years ago. Machine #2: ASUS P8H77-I. Latest BIOS. This year. USB Flash stick: Kingston "Data Traveler" 4GB. Clean (blank) STRANGE (UNEXPLAINED) syslinux BEHAVIOR DIFFERENCE Steps: 1. Set up KNOPPIX 7.05

Greetings one and all. I'm a unix newbe....so deal with me here. I have a .iso copy of syslinux 1.67 (which actually might be ISOlinux??) that I boot from CD (ramdisk version...no HD needed)... but my version doesnt have the mkdosfs utility on it. I was looking for an executable that would work with this version... can someone point me toward such an animal??? :Pat

since a few of you asked what I use it for...since I'm not a unix person.. I started using it back in 2002...to update hard drives that used a 'superfloppy format' (if anyone remembers the old DigitalWallet from Minds at work!) I fixed several of them after the company went belly up for photographer friends of mine. I mostly use it to do HD maintance...fixing fats...restoring backup

Do you have an example on how I use this? My goal is to boot into DOS so I have access to my dos apps Den 22. dec. 2017 kl. 14.24 skrev Ady Ady via Syslinux <syslinux at zytor.com>: >> How can I boot into dos with different kinds of dos command with PXELinux? >> >> My menu is working fine, but I'm not sure what I should add to run into dos. >> >> My

I have many hp laptops that boot msdos with memdisk + pxelinux perfectly. However, I recently have the need to usb boot msdos with syslinux. And memdisk. When the dos Image loads I get "loading bootsector..." and then it halts. Sometimes I can get "starting ms-dos" but freezes as well. I'm trying to boot clean msdos floppy image created with winimage. I'm using

Hi, Ady wrote: > This could be misinterpreted by some users as: "if > you want to build an isohybrid image, then you cannot use > 'syslinux.efi'". This would be incorrect. I don't know whether syslinux.efi can be used for booting from ISO 9660 via UEFI. Currently there is no example around which would succeed without GRUB or GRUB2. When describing the UEFI

Does someone know where I could get my hands on an ima that's larger than 2.88meg... I use winimage for all my ima's and stuff but i'm having trouble configuring a custom size. If anyone has a large ima I could utilize that would be great, preferably one fitting this memdisk supported size: 3,932,160 bytes (3840K) c=80 h=2 s=48 3.5" DSED (extended) If not instructions on making

On 07/09/2014 04:00 PM, H. Peter Anvin wrote: > > So this would seem consistent that this is the FAT12/FAT16 boundary that > breaks stuff. Perhaps FreeDOS has a problem with FAT16 on floppies? If I understand things correctly, a bootable floppy has two key pieces of executable code: the 512-byte boot sector, and the kernel loaded by that boot sector. The kernel can be large, and thus