similar to: Request for built-in DOS launch module

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

_ Vbox 4.2.18 VM booted with FreeDOS floppy, kernel 2041, no config.sys, no autoexec.bat, no TSR's, no memory managers. _ The booting floppy includes syslinux.com 6.02. _ Two HDD images attached to the VM, MBR + 1 FAT16 formatted partition each. Executing syslinux.com -i c: (or "d:") results in the following error: "Invalid Opcode at AD04 5080 0206 5080 2021 3666 FFFD 0083

On 08Jul2014--09Jul2014, Ady, Peter Anvin, Gene Cumm, Bernd Blaauw, Shao Miller, Kenneth Davis, wrote: > [...] Thank you all for your responses. You helped me solve my problem. For anyone else that runs into similar trouble and finds this thread, here follow summaries of what I've learned. To recap, our PXE server holds Dell BIOS updates in FreeDOS floppy images booted via MEMDISK.

Warning, Complete NOoB! Ok here's the deal, I'd like to use this flash tool to flash a new ROM to my Sony X10 using my Mac. I found wine and am having trouble because I don't understand prefixes or how to make them. My Mac's stats. 2 Ghz Intel Core Duo Memory 2gb 667 Mhz DDR2 SDRAM Mac OS X 10.5.8 And I have Wine 1.1.44 , tried Update and says I am using the latest

Hallo, I try to boot the windows 98 bootdisk via memdisk. It doesn't work completely. Booting a freedos FD image works, booting the windows 98 image works too. But the windows 98 boot disk then should extract the file "ebd.cab" with the file "extract.com", and that step fails. Is that a syslinux problem or a windows problem? Viele Gruesse! Helmut

Testing the DOS-based Syslinux installer, syslinux.com, with the "-m" parameter, I found that it works as expected under MS-DOS and its DOS variants, but it seems to fail under FreeDOS (please correct me if I'm wrong). Using FreeDOS kernel v.2041 (386f32), Syslinux v.6.03-pre11 and either FAT16 or FAT32 partitions, executing: syslinux.com -m -i c: or: syslinux.com -f -m -i

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

On 07/08/2014 05:55 PM, H. Peter Anvin wrote: > On 07/08/2014 03:05 PM, Alexander Perlis wrote: >> >> Question: what's special about the transition from 8203KiB to 8204KiB? >> Both have CHS=8/64/32 and both involve a fractional end cylinder. > > Fractional cylinders with floppy disks is almost certainly a very bad thing. > Agreed, but that doesn't appear to

(FreeDOS developers, I apologize for the redundant parts of this message. But I want to bring the SYSLINUX folks into the discussion, and the SourceForge mailing list archives are broken.) Background: I have a little Sourceforge project (http://unattended.sourceforge.net/) for which I use SYSLINUX to provide CD-ROM and PXE boot support for my boot disk. And it works great with MS-DOS. However,

> On Fri, May 23, 2014 at 8:29 AM, Ady <ady-sf at hotmail.com> wrote: > > Testing the DOS-based Syslinux installer, syslinux.com, with the "-m" > > parameter, I found that it works as expected under MS-DOS and its DOS > > variants, but it seems to fail under FreeDOS (please correct me if > > I'm wrong). > > This sounds like either a bug in

I'm trying to use this universal DOS TCP/IP boot disk available here: http://members.iinet.net.au/~bdriver/bootdisk/ It requires an MS-DOS formatted disk created by Windows XP. It works great as a floppy but doesn't boot at all with memdisk. The problem can be simplified down to just the XP boot disk. If you make an MS-DOS startup disk with XP on a floppy, dd the floppy to an image

I've got $SUBJ almost working except for the DOS bit where the CD needs to be read. My pxe config: label Firmware menu label Update IPMI firmware kernel memdisk append keeppxe raw iso initrd=<isofile> The ISO is about 400Mb, and works fine when I boot it from an actual CDROM drive. It also boots fine over PXE, I can see FreeDOS being booted up etc. The problem is - once

2018-06-26 2:10 GMT+08:00 H. Peter Anvin via Syslinux <syslinux at zytor.com>: > On 06/18/18 13:06, R S via Syslinux wrote: >> 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 >>

On 07/09/2014 04:00 PM, H. Peter Anvin wrote: > > So this would seem consistent that this is the FAT12/FAT16 boundary that > breaks stuff. Perhaps FreeDOS has a problem with FAT16 on floppies? If I understand things correctly, a bootable floppy has two key pieces of executable code: the 512-byte boot sector, and the kernel loaded by that boot sector. The kernel can be large, and thus

On Tue, 08 Jul 2014 15:54, H. Peter Anvin wrote: > >On 07/08/2014 11:26 AM, Ady wrote: >> >> It's interesting that you ask this, because every document related to >> newmkfloppyimg.sh specifically recommends adding: >> floppy c=$CYLINDERS s=$SECTORS h=$HEADS >> to the MEMDISK arguments. >> > >It would be important for floppies to know

I'm having trouble getting memdisk 6.03pre18 to boot large floppies and wondering whether I'm doing something incorrectly. 1) Download http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz 2) gunzip FDOEM.144.gz 3) newmkfloppyimg.sh 8 FDOEM144.img fdoem_8mb.img 4) newmkfloppyimg.sh 9 FDOEM144.img fdoem_9mb.img 5) Use following pxelinux.cfg: LABEL works LINUX syslinux/memdisk INITRD

I would like to boot FreeDOS ISO image from USB memory stick using syslinux. I have done following: 1) I created a partition to my 2GB memory stick: root at debian64:~# fdisk -lu /dev/sdb Disk /dev/sdb: 2013 MB, 2013265920 bytes 62 heads, 62 sectors/track, 1022 cylinders, total 3932160 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I am having trouble with memdisk not freeing all all memory - mem /c shows only about 570K memory (and I happen to need that extra memory in DOS ... :-( ). I found some (rather old) information about this issue. It seems as if this is just what is happening to me: http://syslinux.zytor.com/archives/2003-June/002213.html

On 01/13/16 00:13, Tal Lubko via Syslinux wrote: > > OK. I'll try that. > Any thoughts regarding the requirement to store the bootloader inside the BIOS chip? > That is fundamentally up to your BIOS. The best is to expose the bootloader in the BIOS as a (readonly) disk drive using standard BIOS or EFI interfaces. -hpa

It seems that quite a bit of stuff built up very quickly after the 2.07 release: Changes from 2.07 to 2.08-pre6: * Add new configuration command "ontimeout" to allow timeout to have a different action than just pressing Enter. * Add new configuration command "onerror" to allow a custom command to be executed in case the kernel image is