From: Frederic Herman <fherman@inferential.com>
To: Paul Crawford <psc@sat.dundee.ac.uk>
Cc: Devyn Collier Johnson <devyncjohnson@gmail.com>,
linux-msdos@vger.kernel.org
Subject: Re: Resurrect DOSEMU
Date: Thu, 11 Jul 2013 08:31:47 -0600 [thread overview]
Message-ID: <51DEC1D3.20604@inferential.com> (raw)
In-Reply-To: <51DEB983.5020109@sat.dundee.ac.uk>
I am hoping that whatever is decided, that the result is an emulator
that works properly in a 64 bit, particularly AMD, environment. I have
an old reliable accounting package which I rely on, that crashes with op
code errors under the 64 bit environment.
I have given up sometime ago with running it under x86_64,and have
resorted to using another machine with 32 bit hardware and OS just so I
can run the accounting package via a remote ssh session. I have been
using Fedora Linus, but recently tried a Ubuntu linux (64 bit) and have
the same problem.
I think I tried DOSbox, but I remember a show-stopper, maybe lack of
printer support.
DOS emulation is not just for running games. There are legacy business
packages such as the one I use, that require a good emulator. These
packages were typically written in assembly language. In my case,
switching to a modern accounting package is not a just a matter of the
cost of software. The greater cost is the huge amount of time I would
need to spend to manually convert about 10 business general ledgers to a
new accounting package.
Fred
On 07/11/2013 07:56 AM, Paul Crawford wrote:
> Dear Devyn,
>> 3. What is we spoke with the DOSbox developers about merging the two
>> projects? Why have two DOS emulators for Linux? Why have to separate
>
> I am not very sure about how DOSbox is implemented, but I think they
> have rather different approaches to the issue of running DOS
> applications under alternative operating systems. There is also the
> option of booting MS-DOS, etc, in a VMware virtual machine, etc, to add
> to the list of options for DOS software.
>
> However, in our case the attraction of dosemu for Linux comes down to
> two points:
>
> 1) The option for direct hardware access, thus allowing old software to
> communicate with old hardware, but under the management of a secure
> networked system (e.g. access to NFS drives, remote log-in via SSH, time
> keeping accurate using NTP, etc).
>
> 2) Good emulation of file system access, so DOS applications can work
> with Linux file systems and see them in a reasonably sensible manner
> (e.g. all file names mapped to lower case on the Linux side, upper on
> DOS side, etc). VMware's shared folders do not work very well in this
> aspect (though using Samba you can get something reasonable, but then
> with Windows networking, so not really a DOS solution).
>
> These are not generally requirements for running an old DOS game, but
> they are exceedingly useful for keeping tried & trusted hardware &
> software going where the alternative of a new system involving a
> complete re-write may be either impossible (no source code, etc) or
> simply impractical.
>
> Regards,
> Paul
next prev parent reply other threads:[~2013-07-11 14:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 13:11 DOSEMU Version 2 has been Released (DevynCJohnson@Gmail.com) Devyn Collier Johnson
2013-07-09 13:42 ` Mateusz Viste
2013-07-09 20:25 ` Stas Sergeev
2013-07-09 16:30 ` Frantisek Hanzlik
2013-07-09 20:14 ` Stas Sergeev
2013-07-10 2:13 ` Bart Oldeman
2013-07-10 6:50 ` Stas Sergeev
2013-07-10 10:16 ` Devyn Collier Johnson
2013-07-10 10:30 ` Stas Sergeev
2013-07-10 11:52 ` DOSEMU Version 2 has been Released Ivan Baldo
2013-07-11 13:44 ` Resurrect DOSEMU Devyn Collier Johnson
2013-07-11 13:56 ` Paul Crawford
2013-07-11 14:31 ` Frederic Herman [this message]
2013-07-11 13:58 ` Mateusz Viste
2013-07-15 10:50 ` Stas Sergeev
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=51DEC1D3.20604@inferential.com \
--to=fherman@inferential.com \
--cc=devyncjohnson@gmail.com \
--cc=linux-msdos@vger.kernel.org \
--cc=psc@sat.dundee.ac.uk \
/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