From: Paul Crawford <psc@sat.dundee.ac.uk>
To: Frederic Herman <fherman@Inferential.com>,
Mateusz Viste <mateusz@viste.fr>,
linux-msdos@vger.kernel.org
Subject: Re: Illegal op ff e8 2c in newer dosemu
Date: Wed, 06 May 2015 23:05:09 +0100 [thread overview]
Message-ID: <554A9015.9010705@sat.dundee.ac.uk> (raw)
In-Reply-To: <554A5B5B.3040805@Inferential.com>
There is a difference in 64-bit vs 32-bit, and it is more than just the
problems of no vm86() call so hardware interrupts are not properly
handled (aside - is that fixed now/soon?).
I found I could use the MS C6.0 compiler and the 'PWB' (programmers
workbench) for compiling the DOSD software OK under 32-bit Linux, but
not under 64-bit as the dosemu instance would simple exit, as if exitemu
was called (but it wasn’t). While I know MS had a lot of dubious and
undocumented calls, the difference I saw was definitely a memory issue,
and maybe related to the various XMS/EMS extenders that were needed at
one time, when 640k was no longer enough for everyone...
Regaeds,
Paul
--
Dr. Paul S. Crawford
c/o Satellite Station
University of Dundee
Small's Wynd, Dundee, DD1 4HN
Email: psc@sat.dundee.ac.uk
The University of Dundee is a Scottish Registered Charity, No. SC015096
--
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-05-06 22:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 15:16 Illegal op ff e8 2c in newer dosemu Martin Hicks
2015-05-06 16:09 ` Andrew Bird
2015-05-06 17:17 ` John R. Sowden
2015-05-06 18:05 ` Mateusz Viste
2015-05-06 18:20 ` Frederic Herman
2015-05-06 22:05 ` Paul Crawford [this message]
2015-05-07 12:52 ` Martin Hicks
2015-05-07 13:00 ` Paul Crawford
2015-05-08 6:18 ` solarflow99
2015-05-06 18:33 ` John R. Sowden
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=554A9015.9010705@sat.dundee.ac.uk \
--to=psc@sat.dundee.ac.uk \
--cc=fherman@Inferential.com \
--cc=linux-msdos@vger.kernel.org \
--cc=mateusz@viste.fr \
/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.