similar to: files in CRAN/src/devel/floppies

I'm having trouble getting memdisk 6.03pre18 to boot large floppies and wondering whether I'm doing something incorrectly. 1) Download http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz 2) gunzip FDOEM.144.gz 3) newmkfloppyimg.sh 8 FDOEM144.img fdoem_8mb.img 4) newmkfloppyimg.sh 9 FDOEM144.img fdoem_9mb.img 5) Use following pxelinux.cfg: LABEL works LINUX syslinux/memdisk INITRD

Hi All, I am following: http://www.linuxinsight.com/how-to-flash-motherboard-bios-from-linux-no-dos-windows-no-floppy-drive.html to make a bootable CD to flash my bios I get to mkisofs step, but what I get is not what I think I want. I dont understand if I unmount /tmp/floppy how the Mkisofs command of: mkisofs -o bootcd.iso -b FDOEM.144 FDOEM.144 how I get everything in /tmp/floppy Here is

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

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

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

I''ve noticed that fstyp on a floppy media formatted with "pcfs" now needs somewhere between 30 - 100 seconds to find out that the floppy media is formatted with "pcfs". E.g. on sparc snv_48, I currently observe this: % time fstyp /vol/dev/rdiskette0/nomedia pcfs 0.01u 0.10s 1:38.84 0.1% zfs''s /usr/lib/fs/zfs/fstyp.so.1 seems to add about 40 seconds to that

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 am working on a project where I have to move some parts files from an old Unix server. I have tared the files to floppy disc, but I can't mount them. After doing some reasearch I have found that the SCO Unix ver 3.2 uses a System V filesystem I think. From the article that I have read I need to add this filesystem to my kernel to be able to mount and read the floppy discs. Can

I have periodically been trying to get memdisk to boot images larger than your average 1.44Mb floppy and have always been unsuccessful. I cannot boot anything greater than 1.44Mb. The systems I'm attempting to do this with are not too old but they are not recent either. One is a Asus P5A and the other is a Intel SE440BX both with the most recent bios firmware patches available applied. If

The following patch allows memdisk to support compressed floppy images created by WinImage. WinImage creates a PKZIP-style archive with a single member, the .img (or .ima) file containing the floppy image. WinImage names such archives with a .imz extension. This patch lifts the header/trailer checking code from gunzip() to a new function, check_zip(), which both checks for a valid ZIP image and

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

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

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

Hello All: I've recently had to provision some RHEL and CentOS VMWare instances. There was no network connectivity so I had to use a kickstart floppy and DVD iso rather than installing from our repository. To create the floppy I used the following: As root: dd if=/dev/zero of=floppy.flp bs=1k count=360 mkfs.vfat floppy.flp mount -o loop floppy.flp /mnt/floppy cp base_kickstart.ks

First I'd like to thank you, and everyone who has contributed to the isolinux development. It has been the solution to many of my development needs. Currently I am creating a Linux system that runs directly from CD. Currently the CD is working and I am using isolinux to boot the CD. The compressed kernel is approximately 2 meg and the compressed initial ramdisk is approximately 4 meg.

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

I am in the process of trying to update a bootable Linux CD that I initally built some time ago using RedHat 7.3 and syslinux 1.x (I believe that x = 52, but this doesn't seem to be relevant). In order to do this, I first built a floppy disk image and made it bootable by running "syslinux -s" on the image; then I incorporated this image into a CD using "mkisofs -b boot.img -c

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

Hello list, My set up is almost complete in booting DOS through PXELinux, but I need to create a DOS boot image from (2 )DOS floppies. I've search the archives and google but didn't find any relavant info... My current set up now works with the standard setup (with one DOS floppy): kernel: memdisk append: initrd=floppy.img ramdisk=10000 My goal to is create a floppy.img from 2 DOS

Hi, I'm the maintainer ROCK Linux (www.rocklinux.org). We are using isolinux on our Install-CDs for x86 systems. We - as most other distributions too - are running in the problem that even minimalistc kernels are slowly growing and sometimes don't fit on 1.44 MB floppies anymore. 2.5.x kernels with initramfs are even bigger than 2.88 MB in some cases... Until now it always has been