Displaying 20 results from an estimated 297 matches for "freedos".
Did you mean:
freedom
2012 Jul 01
2
booting FreeDOS ISO image using syslinux hangs
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 = 5...
2014 May 24
2
Syslinux DOS-based installer in FreeDOS
> 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 interaction.
>
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 wou...
2014 May 23
2
Syslinux DOS-based installer in FreeDOS
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 c:
will not write to the MBR, and will ruin the VBR.
To be clear, the "-m" parameter...
2014 May 30
2
Syslinux DOS-based installer in FreeDOS
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 that there are several (open source) DOS programs that
> > are capable of successfu...
2012 Mar 26
1
Help: Boot FreeDOS from the second pri. partition
...ot 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 FreeDOS and I have copied
necessary files to the partition. Here's my syslinux.cfg in /dev/sdb1.
UI menu.c32
TIMEOUT 300
default localboot
MENU TITLE System Rescue Flash Disk
LABEL memtest
MENU LABEL Memtest86+ (4.20)
KERNEL memtest
LABEL freedos
MENU LABEL FreeDOS 1.1
COM32 chain.c32
APPEND h...
2009 Mar 23
1
Memdisk + Freedos problem
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-defensi...
2013 Jan 31
5
Request for built-in DOS launch module
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 making a custom FreeDOS ISO image or...
2014 Jul 15
4
Possible memdisk issue
...ernd 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. For newer hardware those update programs are
huge, so require enlarged floppy images. (I prefer floppy images over
hard drive images because it seems easier to quickly loop mount and
modify a floppy image in Linux, than to loop mount a buried partition
from wi...
2018 Jun 18
3
Memdisk and big floppy images
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 F...
2014 May 24
0
Syslinux DOS-based installer in FreeDOS
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 interaction.
I vaguely recall FreeDOS having some sort of HDD-acceleration
(caching/prefetching). A quick Google returns "lbacache" and
"uide.sys". If so, a te...
2018 Jun 18
4
Memdisk and big floppy images
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 floppy
initrd16 /boot/freedos.img
boot
Kind regards,
Paul
[1]: http...
2004 Jan 26
7
Problem with FreeDOS + himem64 + PXELINUX + 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
prov...
2003 Dec 16
2
syslinux bootsector info?
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 found a way around the 386-dep...
2006 Feb 15
0
Freedos mount/boot Linux ISO's
Hello:
I read the archive posting for September 2005, http://syslinux.zytor.com/archives/2005-September/005809.html, where you stated that you have a freedos diskette that allows you to download and run an iso like it was a cd in a drive. I am in need of the ability to have a freedos bootable cd that contains other Linux ISO's that I could mount and boot to. In your experience with freedos is this possible? I have not found good instructions...
2013 Oct 15
2
syslinux.com 6.02 Invalid Opcode under FreeDOS
_ 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:...
2013 Mar 01
2
Booting an ISO with FreeDOS over PXE with memdisk
...OS 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 in DOS, there is no access to the
CD. The CDROM driver doesn't load due to "no cdrom found". Does this
ring a bell with anyone?
The ISO is from a manufacturer, but I can modify it if needed (change
the DOS setup for instance).
>From th...
2014 Jul 16
0
Possible memdisk issue
...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. For newer hardware those update programs are
> huge, so require enlarged floppy images. (I prefer floppy images over
> hard drive images because it seems easier to quickly loop mount and
> modify a floppy image in Linux, than to loop mount a burie...
2007 Jul 13
1
[memdisk] collision between memdisk and emm386 (FreeDOS)
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:
...
1?DEVICE=HIMEM.EXE /VERBOSE
1?DEVICE=...
2001 Oct 12
2
BoxOS
Dear WINE Users/Programmers/Developers,
I am currently starting a new project called BoxOS. We are going to try
port the WINE System to a FreeDOS Enviroment.
Here is a more information on the project:
The BoxOS Kernel is based upon FreeDOS Beta 7 ("SPEARS"). That version of
FreeDOS includes the Kernel 2023b and sys updated to 2024h and the FreeCom
0.82 updated to 0.83beta28. We have edited these Kernel's a fair bit.
We are...
2007 Oct 09
1
DOS/Freedos: Can't use mkfloppyimg.sh or mkdiskimage for +8M images ( Murali (????? ?????) )
...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 expected.
To create my dos image, I did use Murali
script and pick the freedos floppy image from
http://www.fdos.org/bootdisks/autogen/FDSTD.144.gz
I modify cwhosthe script, put FDSTD.144 as the OLDIMAGE
I set NEWIMAGE to dexter1.img
I set the SIZEMB to 10
The script return the following information
Your floppy image is in dexter1.img. When using it in iso/pxelinux, dont fo...