From: Julius Schwartzenberg <julius.schwartzenberg@gmail.com>
To: linux-msdos@vger.kernel.org
Subject: Re: dosemu2 very interesting results
Date: Thu, 8 Apr 2021 21:12:16 +0200 [thread overview]
Message-ID: <fc75f59d-c7d0-34c9-8548-6d500c4ca148@gmail.com> (raw)
In-Reply-To: <alpine.NEB.2.23.451.2104071544420.19093@panix1.panix.com>
I forgot to include the list:
Glad you got dosemu2 to run!
The standard installation indeed doesn't have all the typical utilities.
A script to install these is available through an extra package:
https://github.com/dosemu2/install-freedos
I don't think SDL will help you. There is also X11 mode with -X, but I
think the text modes help you most, -t is the regular terminal mode.
Op 07-04-2021 om 21:54 schreef Jude DaShiell:
> A contact built dosemu2 on debian and I installed it.
> When I ran dosemu -dumb it came up and left me at the c: prompt. A tmp
> directory on the hard disk in /home/jude/.dosemu/drive_c/ but no more
> than that. edlin wasn't there among other expected utilities one would
> find in dos.
> I can live with that.
> When I tried running without dumb though I got a boot.log.3 that was
> over 1,000 lines long. radeon and dosemu2 don't get along all that
> well. I was curious to find out what would happen with sdl and the sdl
> package is on this debian instance. The deb packages are not in the
> debian archive this was another debian user who had a slow day at work
> and built this for me.
> I'll try putting some dos utilities and programs in the drive_c
> directory then find out if they can run on next boot into dosemu2.
> More later as I figure it out.
>
prev parent reply other threads:[~2021-04-08 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 19:54 dosemu2 very interesting results Jude DaShiell
2021-04-08 19:12 ` Julius Schwartzenberg [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=fc75f59d-c7d0-34c9-8548-6d500c4ca148@gmail.com \
--to=julius.schwartzenberg@gmail.com \
--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