similar to: Windows harddisk images.

>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

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

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

I am using PXELINUX, ISOLINUX, and memdisk in my project (http://unattended.sourceforge.net/). When memdisk gained support for compressed images, I started using it because it is cool. I used gzip to compress floppy.img to create floppy.imz, and all was good. But now my users are complaining that they cannot use WinImage (a Windows floppy image editing tool) to edit my floppy.imz files. I have

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 would just inject your ROM and EXE (and possibly adjust autoexec.bat to autostart/apply the FW update). It's a minimal FreeDOS FDD image that defaults to a clean boot with

This is a minor tweak on 3.11-pre2. If nothing new comes up, I will release this as 3.11 probably early next week. -hpa

I read the following about memdisk : .... For any other size, the image is assumed to be a hard disk image, and should typically have an MBR and a partition table. The disk C/H/S geometry is determined by examining the partition table, so the entire image should be partitioned for proper operation. .... I'd like to create a bootable cd, wich boots a linux and some other tools. While

Does SYSLINUX have any idea which DOS driveletter would be assigned to the disk it is booting from? At www.veder.com someone is trying to build a USB flash drive. However, FreeDOS does not seem to boot correctly from it (bootsector trouble maybe, or kernel itself is confusing drives), thus we're thinking of using Syslinux + Memdisk + bootimage, but somehow we want to be able to also access the

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 have been trying to track down information on building HD boot images for ISOLINUX and MEMDISK, and so far, haven't had a whole lot of luck. I've found a number of sources describing the process of setting up ISOLINUX and MEMDISK, and how to configure the boot CD to boot various OS's. I've also read through Bart Lagerweij's BootCD/ModBoot pages, and Mikhail

Hi there, I am using memdisk with pxelinux, i have created ms-dos boot disk from windows xp, but when i boot from it stops on starting.... what is the problem can anybody tell me.. Regards, Yogesh

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

I have an application/program which shows 'bios EDD error' when using Isolinux (with either loading an image directly through MEMDISK, or booting to A:), and not when using a bootdisk directly or booting a bootdisk directly which has SYSLINUX on it. configuration: bootable cdrom with Isolinux 2.11/2.12pre9 as bootloader. 1.44MB bootdisk with MSDOS.SYS/IO.SYS and the UDMA2 dos driver,

Mr Anvin, is there a specific loading address used with the Syslinux bootsector (to load ldlinux.sys)? like msdos 0x70, freedos 0x60 we're trying to have a SYS program that can create bootsector for other OS's than FreeDOS only. not much luck though :( this way I'm trying to avoid the use of syslinux.exe/com (need the diskspace that it would save by not including this program) I

Hi, I'm trying to use pxelinux+memdisk to boot to dos. And using dos tcp/ip connect to windows network. I've used winimage to create (dos.ima) image of dos bootable floppy. But when I type dos at boot: prompt, it doesn't boot to dos instead show a multi-coloured screen. At this moment ctrl+alt+delete also doesn't work. Pls help Jitender

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

Hi, I'm sorry to bring this up again but I can't quit get this too work. I'm trying to build a 2.88 floppy image so that I can use PXE to load Ghost. I'm useing the following to get a copy of the bootsector: dd if=/dev/fd0 of=bootblock bs=512 count=1 Then I build the image file with: mformat -C -t 160 -s 18 -h 2 -B bootblock x: Then use mcopy to put the required

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

I've recently purchased an SSD with the goal of having a portable MS-Windows installation, something which Windows 8's "Windows to Go" feature allows (install to, and boot/run from, USB flash device). Housing the SSD in an external Zalman VE300 case allows presenting ISO files as hardware CD/DVD/BD drive with inserted medium. Having the ISO files present, it's tempting

[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