similar to: Installing a Guest that Requires Floppy Booting

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

Hello! Below is an excerpt from the thread in October. I have the same problem, but my laptop (which is a Brand new HP Compaq NC6230) does not have options in the BIOS to enable or disable floppy support. It just doesn't have one. I assume it leaves it enabled for USB Floppy support, but does not come with the drive. My ISOLinux setup is a UBCD. I tried to make my own, but the lack of

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am trying to create a PXE setup with floppy images for all needed utilities - for example, BIOS flash for various motherboards, disk diagnostic tools, memtest86+, etc. I've gotten memtest86+ to work (using the .bin), and some of the disk images work - however, some disk images will not boot. All of the images were pulled from working, bootable

Hello everyone, I am attempting to add another boot option to our multi-boot technical resource CD where I work. I currently have 8 working floppy disk images, but this time I need to add a piece of software which I only have access to through an ISO image. This ISO image, when burned to a CD, boots and runs the software fine. I know that isolinux does not support booting ISO images. I used

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, I suspect this bug has already been reported, but here it is just in case: the bootable floppies I produced with syslinux 2.10 (just by running 'syslinux /dev/fd0') are not able to 'remember' the parameters I pass at the boot prompt. Namely, to boot a USB pen from one of my floppies I pass something like boot: MoviX MEDIA=usb (where MoviX is the boot label) but the usb boot

I realize this is probably the wrong list but since some of the principals this list deals with are similar in nature I figured it could't hurt. What I am looking to do: Provide a solution to either boot from a floppy disk, establish a network connection, give user the ability to run utilities such as fdisk and dd. as well as provide the same solution as a PXE bootable image. My

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

>From NEWS: * MEMDISK: be smarter about incompletely disabled floppies in the BIOS and about being the only BIOS. Shouldn't the second "BIOS" be "floppy"? - Sebastian --- syslinux-3.71-pre4/NEWS.orig 2008-07-05 15:42:50.000000000 +0200 +++ syslinux-3.71-pre4/NEWS 2008-07-05 15:43:33.000000000 +0200 @@ -10,7 +10,7 @@ * EXTLINUX: proper error

I am currently having problems persuading 3.0.4 (binary dist) to boot a virtual machine from a virtual floppy when running in HVM mode. Although I can boot a real computer from a real drive with my floppy image, with Xen it merely hangs after saying: HVMAssist BIOS, 1 cpu, $Revision: 1.138 $ $Date: 2005/05/07 15:55:26 $ If I give it a completely blank floppy image, it does the same

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

I've got a machine running CentOS 3.5 with an Intel D865GBF motherboard and I've been having an occasional "event" where disk-intensive activity (such as running "yum check-update" or starting up OpenOffice) causes the load average to spike and X11 to become unresponsive (as in, the pointer won't even track the mouse) for a few seconds. The machine always recovers

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

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, I have 2 partition o my HD: /dev/hda1 e /dev/hda2 . In /dev/hda2 there is Suse_10.1, /dev/hda1 is empty, and in the MBR there is Grub. Normally, FreeBSD can be installed from a CD or a floppy, but I haven't neither a cd device nor a floppy device. So, I want run the installation of FreeBSD_6.2 from a floppy image. In this thread there is an idea, but I didn't understand it.

This isn't an esp urgent issue, but I'd like to use a certain RAM diagnostic (Doc Mem) which I've already posted a note about a couple of months ago. Simply won't work booting the floppy disk image via MEMDISK. In the interim, I've tried to resolve this by changing things on my side. I'm pretty sure it's a XMS incompatibility, as it fails differently depending on

Anyone know the correct syntax for specifying a floppy image in the /tftpboot/pxelinux.cfg/default file? I am trying to use: label Dos Bootdisk MENU LABEL Dos bootdisk FDIMAGE discimage.img But when I select it the menu, I get a message saying "Automatic boot in 30 seconds" and nothing happens. I would use: label Dos Bootdisk 2 MENU LABEL Dos bootdisk 2

I used to use multiple syslinux floppy images to implement what I call CD-ROM-multiboot (EL Torito supports up to 64 bootable images, Award BIOS 8 images, if not wrey old). Now that floppies are getting too small, I find that I must find a workaround for hard coded isolinux directory name in isolinux. Not a big deal, but there might be also others who would like to have multiboot feature. --

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

>that image under B: or X: or whatever. This will allow us to cross the >size limit of 2.88MB floppies. Ofcourse when I say "mount" I dont expect >memdisk to mount it, just that set things up so that DOS mounts it there. I'm using a 5MB image which emulates floppydisk. label test kernel data/memdisk append initrd=data2/test.img c=80 h=8 s=18 floppy problems are