similar to: booting FreeDOS ISO image using syslinux hangs

Hello, there is a "fdboot.img" floppy drive image included with FreeDOS ISO file. It's a floppy image file: root at debian64:~# file -s /home/martin/FreeDOS/isolinux/fdboot.img /home/martin/FreeDOS/isolinux/fdboot.img: x86 boot sector, FREE-DOS BEta 0.9 Bootloader KERNEL.SYS, code offset 0x40, OEM-ID "FreeDOS ", sectors/cluster 2, root entries 112, sectors 720 (volumes

Hi, I'm trying to install debian-6.0.5-amd64-CD-1.iso from USB memory-stick. The problem is, that Debian-Installer is not able to "Detect and mount CD-ROM" during the installation process. The USB memory-stick is a 2GB model containing MBR and FAT32 file system: # fdisk -lu /dev/sdb Disk /dev/sdb: 2013 MB, 2013265920 bytes 62 heads, 62 sectors/track, 1022 cylinders, total 3932160

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

> 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

_ 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

Hi, I did found the problem, a combination of 2 factor. 1- I taught that I did install the latest syslinux, but in fact it was the 3.36 version. 2- Thank to kevin Connelly, he point me to a problem he got with mkdosfs command. The default FAT16 do not work, but the FAT12 do. By adding -F12 to the mkdosfs command fix the problem. The default F16 do seem to work for <8M floppy image. Thank you

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

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 I'm using memdisk as part of CD Shell' isolinux. I've created custom floppy disk image 8440kB size. I've put FreeDOS kernel and bootsector into the floppy. Boot process goes fine with this command: isolinux /boot/memdisk initrd=/ximg/fdos.img c=60 h=8 s=36 floppy The problems begin when I try to run FreeDOS memory manager emm386 from the floppy image. my config.sys: ...

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

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

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 FreeDOS or another undesirable negative

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

Hi, I'd like to create a bootable CD to run Ghost. Before generating the .iso, I tested it on a system with a FAT partition and had syslinux-4.05 installed. However it failed. Here are the steps : 1. copied "memdisk" to the FAT partition. 2. as my copy of Ghost (v11.50 from solution suite v2.5) no longer fits on a single floppy, I created a "large" floppy image of size

Hi Maybe HPA or Murali could help me with this one, or anyone who got the following working. I spend numerous hours reading the list and googling without success. I'd like to create a bootable USB stick and CDROM that will do the following. I will have a menu, from which I could pick a specific dos image (not partition). The dos images could have up to 20Megs in size. The goal is to have

> On 2019-4-11 13:29, Lu Wei wrote: > > 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 >

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

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