search for: bootfloppy

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 files in Ubuntu-casper: initrd.gz vmlinuz The syslinux.cfg at bootfloppy begins with: DEFAULT linux24 APPEND ramdisk_size=100000 init=/etc/init lang=de apm=powe...

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

...king HW-Support for PXE My Testconfiguration: Server IBM-PC300 Client Siemes Fujitsu ErgoPro with freeBSD6.0 installed Network card in client intel82558, which I believe to be sufficiently equal with 82559er (hence covered by eepro100) when producing the boot-floppy Status achieved: # Bootfloppy on ErgoPro boots Etherboot # Etherboot loads pxelinux.0 # Pxelinux loads pxe.cfg/00:10:DC:0E:3F:31 # Pxelinux completely loads pxeboot.0 # ErgoPro stops without additional signs of life (exitus) More Details: # Bootfloppy prepared with www.rom-o-matic.net/5.4.1 <http://www.rom-o-matic.n...

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

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

...orks: --------------- default boot IMPLICIT 1 ALLOWOPTIONS 1 PROMPT 0 LABEL boot kernel multinet.bs --------------- multinet.bs is a 3COM bootstrap loader V1.10 which also supports menus, but no chain loading. multinet.bs is configured to directly load a DOS bootfloppy image without showing a menu. The following default does not work correctly: --------------- DEFAULT menu.c32 PROMPT 0 NOESCAPE 1 IMPLICIT 1 ALLOWOPTIONS 1 MENU TITLE PXE boot menu # Dos multinetwork LABEL DOS MENU LABEL Boot DOS with multiple LAN support kernel multinet.bs # Win...

...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 start Partition Magic over the Net via PXE. Because of this Idea, I first tried to make a bootable network floppy, that connects me to my Server Share. I made this Bootfloppy with the software "BackMagic Netboot" and everything was working, this means my client was able to boot with this floppy and to connect to the server share. No I was reading some articles about PXE and made a floppy Image of this boot floppy disc. But when I now start my client in...

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, everything worked up to that point). I then select which image I'll boot, and syslinux gives me: boot: Loading vmlinuz........... Loading initrd.img.......

...eric 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 computer minimum) 2) FreeDOS bootdisk #load 360KB diskette image from the bootfloppy into RAM - speedup!!! label 1 kernel memdisk append initrd=fdboot.img label 2 kernel freedos.bss the novice protection will warn too early. A: is accessed a lot, so a speedup by using Memdisk is welcome. However the SYSLINUX warning won't let the bootdisk boot on a 8086/80286 system I guess....

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 the files from the Universal TCP/IP Network bootdisk to the image, by mounting the file on a linux computer (mount -t...

...Message: 3 Date: Fri, 02 Dec 2005 13:46:19 +0100 From: Alexander Heinz <mailsanmich@gmx.li> Subject: Re: [syslinux] PxeLinux menu.c32 chaining > multinet.bs is a 3COM bootstrap loader V1.10 which also supports menus, but no chain loading. multinet.bs is configured to directly load a DOS bootfloppy image without showing a menu. > # Dos multinetwork > LABEL DOS > MENU LABEL Boot DOS with multiple LAN support > kernel multinet.bs > Does anybody see a solution? rename multinet.bs to multinet.0, make the according changes to the configuration file and try again....

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