From: Bernd Blaauw <bblaauw@home.nl>
To: freedos-user@lists.sourceforge.net
Cc: xen-devel <xen-devel@lists.xensource.com>,
Miguel Filho <miguel.filho@gmail.com>,
xen-users-request@lists.xensource.com
Subject: Re: [Xen-devel] Unable to boot FreeDOS 1.0
Date: Sun, 23 Mar 2008 12:03:41 +0100 [thread overview]
Message-ID: <47E6390D.50309@home.nl> (raw)
In-Reply-To: <faf3083f0803200941q10388c1cob758580d2865787d@mail.gmail.com>
Geraldo Netto schreef:
> Hi Guys,
>
Hello Geraldo,
> It seems command.com is missing
> could you try any iso from this site?
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.0/
>
The FreeDOS 1.0 ISO is confirmed to be working under normal PC BIOS when
booting from CDROM.
I guess your environment is a modern CPU with virtualisation extensions
present and enabled? (as I don't think Syslinux, Memdisk nor FreeDOS
kernel have built-in support for acting as XEN client).
FreeDOS 1.0 ISO works like this:
1) Boot from CDROM in non-emulation mode
2) Load isolinux.bin (old version, version 3.62 is latest release)
3) Load isolinux.cfg configuration file
4) Press 1 to load FreeDOS (loads Memdisk, then loads
/ISOLINUX/DATA/FDBOOT.IMG, which is a compressed 360KB bootable floppy
image file )
5) FDBOOT.IMG gets uncompressed in RAM, then is being executed (in RAM)
by Memdisk in uncompressed form.
6) Bootsector is loaded, which in turn loads Kernel.sys (FreeDOS kernel)
7) Kernel.sys goes looking for \FDCONFIG.SYS and if that doesn't exist,
\FDCONFIG.SYS. If that also fails, \COMMAND.COM
8) Selecting an option loads drivers and COMMAND.COM, then starts batchfile
Knowing the layout of the 360KB diskette, I'd say the FreeDOS kernel is
not able to find any files (don't see any menu option in your screenshot
which points to no config.sys being found..nor can kernel find
command.com). I don't know if XEN is to blame for this, or Syslinux,
Memdisk or FreeDOS, or any combination of these issues.
Could you refer me to the site which has a web-archive of the responses
for the XEN mailinglists? Can't see if any threads with solutions were
formed there.
Alternative options are to remaster the ISO with 1.44MB floppy emulation
enabled instead of non-emulation with Isolinux. Or ofcourse try a
bootdisk first, instead of a bootable cdrom.
> Geraldo
> ps: sorry for crossposting, at least i hope it helps :)
>
Bernd
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
prev parent reply other threads:[~2008-03-23 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 16:31 Unable to boot FreeDOS 1.0 Miguel Filho
2008-03-20 16:41 ` Geraldo Netto
2008-03-23 11:03 ` Bernd Blaauw [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47E6390D.50309@home.nl \
--to=bblaauw@home.nl \
--cc=freedos-user@lists.sourceforge.net \
--cc=miguel.filho@gmail.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users-request@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.