search for: superfloppy

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

...t 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 running a minute later, but I understand that can't be related. 10) Finally, having learned all this, it's not so hard to just construct a superfloppy of your desired size from scratch entirely within Linux: use mkdosfs to create an empty image file and hold on to the output for FAT type and geometry info. Then use sys-freedos-linux.zip from paragraph 7 to put boot code into sector 0 of that image. Finally, loop mount the image and copy in an...

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)

Why doesn't the Windows Syslinux installer show: --offset and --directory too (I know it is not supported)? Because the Linux versions show the Windows/dos specific commands: --mbr --active and --force I didn't check the DOS version. If all options will be displayed unconditionally for all installers, it might be a good idea to add: --offset -t Offset of the file system on the

...steps for Linux users, to write an MBR and to make sure the partition has the bootable flag set. Please consider adding support for the -m and -a options. (Also, if they don't already, please consider making the -m and -a options check for a valid partition table first to avoid mangling "superfloppy" partitionless USB drives.)" it would be nice if you could add said functionality. Regards, Daniel -- Address: Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: daniel.baumann at panthera-systems.net Internet: http://people.panthera-systems.net/~daniel-...

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] http://www.boot-land.net/forums/index.php?act=Search&CODE=show&searchid= 7cead5c1ec2f697ace0ac12184aeb326&search_in=posts&r...

..."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 of C/H/S parameters on a FAT-formatted superfloppy, then MEMDISK can autodetect them from the FAT superblock. -hpa

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

...ns the isohybrid tools. (In fact, the UEFI specs are not very clear for common users about the "no-emulation" part. The UEFI specs categorize it as "no-emulation", except that it is not a bootloader as 'isolinux.bin' is (located in the same ISO9660 filesystem) but a superfloppy image, which is closer to a floppy-emulation type (but not exactly the same). In any case, this is more technical than what most users want to know. Users usually want to know which steps to perform and move on.) I said it before: frequently the confusion starts with "guides" making...

...> the size you need. I tried the 11.52mb one in a VM and it booted. Our > building's HVAC system mysteriously stopped running a minute later, but > I understand that can't be related. > > 10) Finally, having learned all this, it's not so hard to just construct > a superfloppy of your desired size from scratch entirely within Linux: > use mkdosfs to create an empty image file and hold on to the output for > FAT type and geometry info. Then use sys-freedos-linux.zip from > paragraph 7 to put boot code into sector 0 of that image. Finally, loop > mount the...

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 copies..etc. I found it simplier (and more dangerous) to use th...

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

...l not be noted by EFI from USB stick. Only with EFI from CD-ROM (and DVD or BD). I assume most EFI implementations ignore the Boot Media Type fields in the El Torito boot catalog and only look for Platform ID 0xef. In UEFI specs, El Torito just serves as substitute for a partition table. > a superfloppy image, It's more like a twenty years old hard disk. UEFI 2.6, 12.3 "File System Format": "EFI encompasses the use of FAT32 for a system partition [...] The definition of the EFI file system will be maintained by specification and will not evolve over time to deal with errata...

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