search for: bootfloppies

Hello all. I am pretty new to this list but I have looked through the archives and did not see any reference to this problem. I have an MS-DOS boot floppy image that I am trying to load using MEMDISK. The disk is simply a boot floppy made using XPSP2. I have tried it on 4 different machines, all Dells. PowerEdge 2650 Server, Latitude D610 Notebook, Optiplex GX280 Desktop and Optiplex GX520

Hi, The bios is not able to boot from usb, but only from floppy. I want to boot an Ubuntu-installation from usb. The iso-file was moved with usb-creator to the usb-stick. I have got a boot-floppy, which starts an DamnSmallLinux usb-stick. But this bootfloppy doesn't start the Ubuntu-usb-stick. Which parameters in syslinux.cfg I must change to start Ubuntu-Linux? There are the following

I am using the following command below to create a boot floppy file. Am I not doing the correct thing? mkbootdisk --device bootfloppy.img 2.6.9-34.0.1.EL cp: writing `/tmp/mkbootdisk.Jb5537/vmlinuz': No space left on device cp: writing `/tmp/mkbootdisk.Jb5537/initrd.img': No space left on device cat: write error: No space left on device cat: write error: No space left on device Jerry

After thinking a bit of the multi-file support in 3.31-pre1, and considering a few users' feedback on the subject, I have made a couple of changes: 1. The dummy filename ~ can be used to mean "the main config file". 2. There is a MENU INCLUDE directive now. -hpa

I have spent a couple of days and quite some time during the nights googling and experimenting in pursuing subject objective and I feel like failing, if I cannot get competent help: My objective: boot a FreeBSD-package over the network by Systems lacking HW-Support for PXE My Testconfiguration: Server IBM-PC300 Client Siemes Fujitsu ErgoPro with freeBSD6.0 installed Network card in

rename the VMlinuz*.* to file 'vmlinuz' (no quotes ofcourse). a bootfloppy leaves me enough diskspace, not 860KB. format as FAT12 (ofcourse), install Syslinux (I do this on Win2K with syslinux.exe A:, win9x: syslinux.com A:) my example: http://www.fdos.org/ripcord/beta9rc4/fdboot.img unfortunately no Linux involved. If I could only show a Knoppix bootfloppy (but it's part of a

Hi, I'm trying to get the above working, without success so far: UNDIS.DOS refuses to load with an invalid NDIS stack message (from memory). keeppxe has some effect: it reduces the available conventional memory by 140 kbytes or so... still, the packet driver doesn't seem to find the interface. Does anybody have a working setup I could look at? -- Thanks, Feri.

I'm thinking it's time to release klibc-1.5; however, before releasing klibc-1.4.31 as klibc-1.5, I wanted to give a call to see if there is anything that either really needs to be done, or any bug reports I've missed... -hpa

Hello, many of our platforms do not have a integrated floppy, some even don''t have a floppy controller. As pxelinux still has a problem with machines without a floppy in combination with some bios versions I need to chainload a different bootstrap loader which works on the floppyless platforms. But I also need to load a BartPE and the other BS loader does not support that. So I tried to

Hi friends, I am new to this list and have some questions about PXE Booting, because its not working well. My Situation: I was preparing my Server like described on http://unattended.sourceforge.net And everything was working well, this means I was able to install Windows XP via PXE onto my clients. But now, I thought, It would be really a great Idea to make my clients able to

Howdy, I've got syslinux 1.71 and I'm having a strange booting problem with isolinux. I am constructing a bootable cd as per the example, and I'm using the redhat 7.1 boot floppy as a base (so effectively, I've got the redhat 7.1 bootfloppy as a cdrom - needed because I have a larger kernel). My symptoms are, the system boots from cdrom and presents me with the boot menu (hurrah,

Hi, is there an easy way to circumvent the SYSLINUX novice protection thing? intended users don't know about CTRL key to circumvent it. I'm trying to make a generic bootdisk for systems of 8086 - Pentium4. however the bootdisk is slow, so I'd like to use Syslinux + Memdisk to load a diskette image. then the text displayed to user will be: 1) FreeDOS bootdisk (accelerated, 386

Just for the record, I want to let the list know that I succeeded in booting a modified Universal TCP/IP Network Bootdisk floppy from http://members.iinet.net.au/~bdriver/bootdisk/ I started with a Win98 Bootfloppy from http://www.tobs.uku.co.uk. Then I made a disk image from this, using dd.exe from cygwin. Then I converted this disk image from 1.44MB to 2.88MB with winimage. Then I copied

Hello, many of our platforms do not have a integrated floppy, some even don''t have a floppy controller. As pxelinux still has a problem with machines without a floppy in combination with some bios versions I need to chainload a different bootstrap loader which works on the floppyless platforms. But I also need to load a BartPE and the other BS loader does not support that. So I tried to

First off I love syslinux and it has worked flawless for us on the unix side of the realm. We're trying to use our ghost images within a dos netboot using syslinux. Unfortunatly we can only pass DHCP ip's to hosts that exhibit a vendor code 'like windows/pxe/and other os's do". Unfortunatly DOS does not, so we cannot request a second IP after the pxe process to map samba