From: Frederic Herman <fherman@Inferential.com>
To: 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 12:20:11 -0600 [thread overview]
Message-ID: <554A5B5B.3040805@Inferential.com> (raw)
In-Reply-To: <554A5802.1060308@viste.fr>
I have had the same problem with another accounting program for a LONG
(many years) time. The accounting program (ACCPAC) will run on a 32 bit
machine but generates op code errors on a 64 bit machine. I have had to
resort to running it on the one 32 bit machine remotely via ssh.
It is likely a memory management issue that has never been fixed. Yes,
some programs will run on a 32 bit machine but not ones that require
larger memory.
I have tried all different configuration combinations, but after wasting
a lot of time, I just bit the bullet and ran the accounting program on a
32 bit machine.
Fred
On 05/06/2015 12:05 PM, Mateusz Viste wrote:
> On 06/05/2015 19:17, John R. Sowden wrote:
>> I thought I heard that you cannot run 16 bit DOS programs on a 64 bit
>> box. And I thought that applies to wither Windows or Linux.
>> Let me know as I have a 64 bit box that I am not using because of this
>> DOS issue.
>
> Must be some old limitation, because I use DOSEmu on a x86_64 system,
> and I run 16bit DOS programs without any troubles.
>
> Mateusz
> --
> 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 18:20 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 [this message]
2015-05-06 22:05 ` Paul Crawford
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=554A5B5B.3040805@Inferential.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox