Linux MS DOS discussions
 help / color / mirror / Atom feed
From: Jan Willem Stumpel <jstumpel@planet.nl>
To: dosemu <linux-msdos@vger.kernel.org>
Subject: Some further questions about booting
Date: Mon, 18 Jun 2007 15:57:53 +0200	[thread overview]
Message-ID: <46768F61.1070005@my.home> (raw)
In-Reply-To: <46757803.8080100@my.home>

Sorry to ask one more question about this... I want to have some
good understanding of these things in order to modernise my
"Dosemu for dummies" page.

With a default .deb or .rpm install of 1.4, I can make the C:
drive equal to the existing C: drive of a previous installation of
dosemu. Say my previous version's C: drive is $HOME/olddos. Then I
can do either

1) create a $HOME/.dosemurc file with a line in it
   $_hdimage = "$HOME/olddos"

2) go to $HOME/.dosemu/drives and do
   ln -nsf $HOME/olddos c

3) go to $HOME/.dosemu and do
   mv drive_c drive_c.orig
   ln -nsf $HOME/olddos drive_c

(BTW which of these 3 methods would be the best?)

This works OK. This I understand, because the "olddos" from my
existing installation is a "pseudo-C:" drive with the proper "boot
files" in it (msdos.sys, io.sys, command.com, or in the case of
freedos: kernel.sys and command.com).

But what I do not understand is how the original C: drive (just
after a fresh install), namely $HOME/.dosemu/drive_c, could work.
It does not contain the .sys files that a DOS boot disk should
have. Just AUTOEXEC and CONFIG. So how can it boot?

Regards, Jan


  reply	other threads:[~2007-06-18 13:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-17 11:51 Drives directory Jan Willem Stumpel
2007-06-17 15:51 ` Bart Oldeman
2007-06-17 18:05   ` Jan Willem Stumpel
2007-06-18 13:57     ` Jan Willem Stumpel [this message]
2007-06-23 21:34       ` Some further questions about booting Bart Oldeman

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=46768F61.1070005@my.home \
    --to=jstumpel@planet.nl \
    --cc=linux-msdos@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox