similar to: BoxOS

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

> 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

On Sat, May 24, 2014 at 11:22 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 05/24/2014 01:58 PM, Ady wrote: > > > > My guess is that if this was a bug in FreeDOS (as in "something" that > > has nothing to do with the syslinux.com command) then it would be > > somehow triggered by other DOS programs trying to write to the MBR. > > Considering

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.

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

I and some other people have problems with running the freedos image included in Ultimate Boot CD (UBCD), when using memdisk for floppy emulation. Memdisk starts booting the image and freedos shows the following menu: 0 Boot Clean 1 Boot UMBPCI (silent) 2 Boot UMBPCI (optimal) 3 Boot UMBPCI (semi-defensive) 4 Boot EMM386 (optimal) 5 Boot EMM386 (semi-defensive) 6 Boot no UMB (defensive) 7 Boot

Hi all, I'm going to create an USB flash disk. Here's the partition structure. Device Boot Start End Blocks Id System /dev/sdb1 * 1 537911 268955+ 83 Linux /dev/sdb2 537912 1598793 530441 c W95 FAT32 (LBA) /dev/sdb1 I used for installing boot loader(syslinux) and other small standalone utilities. /dev/sdb2 is used for

To make say a BIOS flash tool available over PXE, my impression is that a typical procedure goes like this: modify a generic FreeDOS 1440K disk image to contain the EXE and change the AUTOEXEC.BAT to launch that EXE, then make the 1440K IMG available on the PXE server. But more recent BIOS flash EXE are too large and won't fit on the 1440K, not even 3840K, so now we have to look into

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

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

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

(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,

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

Hi, I saw the Nov. 2006 message on Memdisk having a problem with ThinkPads. I also saw the comment in the memdisk code enabling and disabling A20. I've got a ThinkPad x61t that memdisk is not loading disk images on. The symptom is that it gets as far as saying "Loading boot sector... booting..." Then image partially runs - FreeDOS prints out its kernel message and it's

Helle, I'm facing a strange issue with memdisk The context : syslinux 3.75 gpxelinux.0 the gpxe stript called from a menu executed through menu.c32 : #!gpxe kernel /modules/memdisk initrd=/freedos initrd /freedos The output before the freeze : /boot.gpxe. ok /modules/memdisk. ok /freedos...... ok MEMDISK 3.75 3.75 Copyright 2001-2009 H. Peter Anvin et al e820: 0000000000000000

Hi, I'm doing a small hobby project writing some tools to put DOS boot images and Linux rescue images on a USB stick. For this I have partitioned my USB stick in 2 partitions, one 192MB partition with a VFAT filesystem (for the normal use) and a second partition with an ext3 filesystem. My aim was to provide a graphical menu (grub) to access the different images using memdisk. Since

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

Hi Peter, Here are the details of a problematic ThinkPad model (an R50e): BIOS version: 2.06 (1WET86WW) BIOS date (YYYY-MM-DD): 2005-11-15 Embedded controller version: 1.04 System-unit serial number: 1834-S5 GL3-BRGZL System board serial number: 1ZB6L5AC1E3 CPU Type: Intel Celeron M CPU Speed: 1.40 GHz Installed memory: 512 MB Booting FreeDOS via current memdisk

On 2019-4-10 1:20, Ady Ady via Syslinux wrote: >>>> #This item fails >>>> label dos >>>> menu label MS-^DOS 7.1 >>>> com32 chain.c32 msdos7=io.sys >> >> IO.SYS and COMMAND.COM are copied from a Windows98 system on another >> computer, which is MSDOS7.1; and BOOTSECT.W98 is from Bootpart tool (I >> compared it with the one from

Sorry for the delay, I should not send email on an holiday week-end. I'll try to answer all the questions by explaining what does work for me right now, and what I'd like to do. I have a script to create the a USB stick or an ISO image. The boot media contains many DOS images, and I use versamenu to select one of them. If my DOS image is smaller than 8megs, everything is working fine as