similar to: pxelinux+memdisk

Like a lot of people, I am using SYSLINUX + MEMDISK to make a technician universal boot disk on a USB key (I have done the same with ISOLINUX and MEMDISK for a CD using Bart's method for bootable CDs) I *LOVE* Syslinux and MEMDISK, and what I can do with floppy images! I have a few problems that have cropped up, most notably the DOCMEMORY program (www.simmstester.com) boots fing, but the

I am using the following simple menu and have noticed that items at the bottom are dropping off. I seem to be limited to 12 items. Is there a limit to how many items can be on the simple menu? default pxelinux.cfg/menu.c32 prompt 0 MENU TITLE UWSP PXE Boot Menu # TIMEOUT 200 LABEL bartpe MENU LABEL Build 12 KERNEL /STARTROM.0 APPEND keeppxe LABEL 11dnet MENU LABEL Build 11DNET beta

Hello, I am a *nix newbie I am trying to boot a DOS boot disk using PXE (to Ghost on windows images). We have an existing PXE server which successfully serves out PXElinux and Fedora builds based on that but my floppy disk image with memdisk isn't working I have tried a few different floppy images which people have posted as ones that work for them but I doubt the disk is the problem

Hello, I am using syslinux 3.63 and I am trying to get an image file going for ghost. I was able to get the unicast image working by using winimage and creating the format for the image as 2.88mb and saving the boot sector as win 95/98. I tried the same thing with a ghost multicast image and it doesn't work, says invalid system disk.. Lots are variables so I am not sure where

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

perhaps the boot-from-cdrom code in Smart Boot Manager? Bernd >>> No, since booting from CD-ROM requires that the El Torito part of the BIOS is activated, which it won't be if it didn't boot from CD-ROM in the first place. ---------------------------------------------------------------- Op deze e-mail zijn de volgende voorwaarden van toepassing:

Dear Syslinux folks, For a firmware update I am following the Gentoo Wiki [1] to create a floppy image of 20 MB, so that the vendor update utility fits. Unfortunately, FreeDOS does not load, and it seems to hang loading the FreeDOS kernel. The original FreeDOS image boots. Do you know if that issue is memdisk related? It?s started from GRUB with the commands below. linux16 /boot/memdisk

In other words: I'm suggesting to use WinImage as it also allows easy injection of new files *and* updating of already existing files. May I ask which vendor is distributing a DOS FW update that is 20MB? I'd like to see the files. Sometimes you just need the .bin/.rom and the actual FW update EXE and it would fit a 5MB FDD image. On Mon, Jun 18, 2018 at 2:03 PM, R S <rene.shuster at

[Redirecting to the syslinux mailing list.] anutma at cmsd.bc.ca wrote: > First of all THANKYOU! > I am a tech at Coast Mountains School District, we have 6 techs and close to > 3000 computers. We have need using Neboot, and have recently switched to grub > using nbgrub. With Memdisk, life has been great (well easier) > What I am trying to do is create a small windows 9x

>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

Hi Peter, I'm using isolinux and memdisk to create a multiboot rescue cd for personal use as described on Bart's page (www.nu2.nu). One boot item is to boot DOS 7.1 from Win98SE with a lot of other staff for emergencies. This DOS bootimage puts all necessary stuff into it's own ramdisk (XMSDSK). Some progs on the ramdisk needs access to floppy drive A: and unfortunately I've no

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

On Thu, Feb 2, 2017 at 1:26 PM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > Hi all, > > > > I have observed a problem where, under legacy BIOS booting mode on the > > DL360g9, memdisk fails to execute. The same mechanism works fine on the > > DL360g8. The system displays the below on the console and ceases to > > respond and must be

HPA, a longterm reminder. See below. Can you also make a LABEL ignore other labels if no KERNEL statement is found in between? That way you could define multiple aliasses for an entry. label foo label bar label memtest kernel memtestp foo ignores 'label bar' , 'label memtest' and executes 'kernel memtest' bar ignores 'label memtest' and executes 'kernel

Has anyone had a problem with afud408 (Award flash program) freezing the system when ran from memdisk? The freeze occurs when just running afud408 (not attempting to update bios, although it freezes then as well.) I was using pxelinux/memdisk 3.36, I upgrade to 3.51, and also fell back to 2.11 all have the same issue. I have tried all the switches for memdisk that I saw posted on the memdisk

Hi all, I have observed a problem where, under legacy BIOS booting mode on the DL360g9, memdisk fails to execute. The same mechanism works fine on the DL360g8. The system displays the below on the console and ceases to respond and must be power cycled. Updating the firmware didn't help. There didn't appear to be any similar issues on the mailing list unless I missed them. Wondering if

using winimage, create a custom image size using [b]total number of sectors[/b], any size, unsure of max change [b]boot sector properties[/b] to [b]win 95/98[/b] and save the file to the isolinux directory as floppy.ima then using isolinux.cfg file add this default 1 prompt 1 label 1

Hello all, I've been following this project with interest, and have had great fun implementing Isolinux within the FreeDOS cdrom distribution. Since I'm not that an expert at Linux, I would like to know how I can *succesfully* generate a bootable image from a partition. Situation is like this: (640MB RAM on system) 60GB IDE harddisk, primary partition 1 win98 500MB extended partition

To: Syslinux From: John Plunkett When Syslinux is used with floppy disks with a 1.44 MB format the boot proceeds at a good speed with no problems. When a format over 1.44 MB is used, the boot takes up to ten minutes. Is there a special setting for booting from floppy disks over 1.44 MB's? Is there documentation on how to configure with floppy disks with a format over 1.44 MB's? Thanks,

forgive me.. i have no idea what im asking or if its possible... i have 2 partitions as follows and am using the std windows xp bootloader to boot xp - ntfs (windows xp) - fat16 stupid question is... can i use syslinux, isolinux, memdisk or some combo there of to place a bootable cdrom iso image on the fat16 partition and then have a boot menu with something to the effect of : 1) winxp as