From: Paul Crawford <psc@sat.dundee.ac.uk>
To: "Mgr. Janusz Chmiel" <chmiel@deep.cz>
Cc: ronin@aristotle.net, linux-msdos@vger.kernel.org
Subject: Re: Why dosemu can not access internal harddisks while running from latest GRML in live CD mode?
Date: Thu, 13 Oct 2011 23:51:23 +0100 [thread overview]
Message-ID: <4E976B6B.6020304@sat.dundee.ac.uk> (raw)
In-Reply-To: <4E974A5E.5080605@deep.cz>
Dear Janusz,
> Why Dosemu can not phisically access The harddrive, IDE or SATA, when
> some DOS compatible application is executed by running Dosemu? Why only
> RAM disks can be accessible?
It can, but not safely.
dosemu normally provides a replacement for the DOS file system to safely
use the Linux file system in a reasonably compatible manner.
You can enable direct hardware access in dosemu.conf for specific I/O
ranges, etc, and run dosemu with root privileges to punch a hole through
the kernel security & moderation layers, but you should think twice
about doing so.
If you want to repair a HDD with DOS-based tools, make a bootable CD
with fredos on it and use that to run them. Look at 'UNetbootin' for
such support.
Regards,
Paul
--
Dr. Paul S. Crawford
c/o Satellite Station
University of Dundee
Small's Wynd, Dundee, DD1 4HN
Email: psc@sat.dundee.ac.uk
Tel: +44 (0)1382 38 4687
The University of Dundee is a Scottish Registered Charity, No. SC015096
next prev parent reply other threads:[~2011-10-13 22:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 14:43 pasting into 1.4.0.1 inside KDE 4.60 Dave Williams
2011-10-13 20:30 ` Why dosemu can not access internal harddisks while running from latest GRML in live CD mode? Mgr. Janusz Chmiel
2011-10-13 22:51 ` Paul Crawford [this message]
2011-10-16 10:30 ` Mgr. Janusz Chmiel
2011-10-16 20:29 ` Paul Crawford
2011-10-17 1:57 ` Ivan Baldo
2011-10-17 11:37 ` Mgr. Janusz Chmiel
2011-10-17 12:07 ` Ivan Baldo
2011-10-17 12:20 ` Mgr. Janusz Chmiel
2011-10-15 2:22 ` pasting into 1.4.0.1 inside KDE 4.60 Ivan Baldo
2011-10-21 1:43 ` Dave Williams
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=4E976B6B.6020304@sat.dundee.ac.uk \
--to=psc@sat.dundee.ac.uk \
--cc=chmiel@deep.cz \
--cc=linux-msdos@vger.kernel.org \
--cc=ronin@aristotle.net \
/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