Illegal op ff e8 2c in newer dosemu

Illegal op ff e8 2c in newer dosemu

[Martin Hicks]

Hello,

I'm trying to run the NewViews 1.41b accounting program, which has been
happily working in dosemu / DR DOS v6.0 for years.  Now it gives an Illegal
Op error and exits when trying to open the accounts books directory.

The machine is running ubuntu/x86_64, and NewViews works correctly up to
package version dosemu_1.4.0+svn.1999-1 but the next package release
does not work (dosemu_1.4.0.7+20130105+b028d3f-1).

The following excerpt from the boot.log was with the latest git tree from the
'devel' branch.  The Illegal Op is always the same, although the CPU exception
code seems to vary depending on the release of dosemu.  Various parts of the
application can be navigated through, but as soon as the directory containing
the accounting books is selected the crash occurs.  I presume it is scanning
the directory and opening files.

I tried various cpu emulation options.  I also found one similar crash report in
the bug system that mentioned setting vm.mmap_min_addr to 0.  Neither
option helped.

Excerpt from boot.log follows.
The full Debug +a log is at http://www.bork.org/~mort/boot.log

Please let me know if any other info might help.
Thanks,
mh

!!! Illegal op ff e8 2c
==============================================================
CPU exception 0x0d err=0x00000000 cr2=00013aee eip=00472bda
==============================================================
ERROR: unexpected CPU exception 0x0d err=0x00000000 cr2=00013aee while
in vm86 (DOS)

Program=sigsegv.c, Line=200
EIP: 04f5:0000460f ESP: 23a9:000039e2  VFLAGS(b): 00000 00110111 00000110
EAX: 00008400 EBX: 00000012 ECX: 00006662 EDX: 00000000 VFLAGS(h): 00003706
ESI: 0000274f EDI: 0000069d EBP: 000039f6 DS: 274f ES: 0288 FS: 0000 GS: 0000
FLAGS: PF TF IF DF RF VM VIF  IOPL: 3
STACK: 80 c0 4f 27 9d 06 f6 39 4f 27 -> 00 00 f5 04 88 02 46 32 2c 03
OPS  : 0e 0a 00 00 89 0e 0c 0a e9 52 -> ff e8 2c 01 c7 06 06 0a 0e 00
        ffe8                04f5:460f jmp  far ax

-- 
Martin Hicks P.Eng.      |         mort@bork.org
Bork Consulting Inc.     |   +1 (613) 266-2296

Re: Illegal op ff e8 2c in newer dosemu

[Andrew Bird]

On Wed, 6 May 2015 11:16:18 -0400
Martin Hicks <mort@bork.org> wrote:

> Hello,
> 
> I'm trying to run the NewViews 1.41b accounting program, which has been
> happily working in dosemu / DR DOS v6.0 for years.  Now it gives an Illegal
> Op error and exits when trying to open the accounts books directory.
> 
> The machine is running ubuntu/x86_64, and NewViews works correctly up to
> package version dosemu_1.4.0+svn.1999-1 but the next package release
> does not work (dosemu_1.4.0.7+20130105+b028d3f-1).
> 
> The following excerpt from the boot.log was with the latest git tree from the
> 'devel' branch.  The Illegal Op is always the same, although the CPU exception
> code seems to vary depending on the release of dosemu.  Various parts of the
> application can be navigated through, but as soon as the directory containing
> the accounting books is selected the crash occurs.  I presume it is scanning
> the directory and opening files.
> 
> I tried various cpu emulation options.  I also found one similar crash report in
> the bug system that mentioned setting vm.mmap_min_addr to 0.  Neither
> option helped.
> 
> Excerpt from boot.log follows.
> The full Debug +a log is at http://www.bork.org/~mort/boot.log
> 
> Please let me know if any other info might help.
> Thanks,
> mh
> 
> !!! Illegal op ff e8 2c
> ==============================================================
> CPU exception 0x0d err=0x00000000 cr2=00013aee eip=00472bda
> ==============================================================
> ERROR: unexpected CPU exception 0x0d err=0x00000000 cr2=00013aee while
> in vm86 (DOS)
> 
> Program=sigsegv.c, Line=200
> EIP: 04f5:0000460f ESP: 23a9:000039e2  VFLAGS(b): 00000 00110111 00000110
> EAX: 00008400 EBX: 00000012 ECX: 00006662 EDX: 00000000 VFLAGS(h): 00003706
> ESI: 0000274f EDI: 0000069d EBP: 000039f6 DS: 274f ES: 0288 FS: 0000 GS: 0000
> FLAGS: PF TF IF DF RF VM VIF  IOPL: 3
> STACK: 80 c0 4f 27 9d 06 f6 39 4f 27 -> 00 00 f5 04 88 02 46 32 2c 03
> OPS  : 0e 0a 00 00 89 0e 0c 0a e9 52 -> ff e8 2c 01 c7 06 06 0a 0e 00
>         ffe8                04f5:460f jmp  far ax
> 
> -- 
> Martin Hicks P.Eng.      |         mort@bork.org
> Bork Consulting Inc.     |   +1 (613) 266-2296
> --
> 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

Hi Martin,
	I think you'll need to report this over at http://sourceforge.net/p/dosemu/bugs/ as this list is very quiet these days, especially for development.

Hope it helps,

Andrew



-- 
Andrew Bird <ajb@spheresystems.co.uk>

Re: Illegal op ff e8 2c in newer dosemu

[John R. Sowden]

On 05/06/2015 09:09 AM, Andrew Bird wrote:
> On Wed, 6 May 2015 11:16:18 -0400
> Martin Hicks <mort@bork.org> wrote:
>
>> Hello,
>>
>> I'm trying to run the NewViews 1.41b accounting program, which has been
>> happily working in dosemu / DR DOS v6.0 for years.  Now it gives an Illegal
>> Op error and exits when trying to open the accounts books directory.
>>
>> The machine is running ubuntu/x86_64, and NewViews works correctly up to
>> package version dosemu_1.4.0+svn.1999-1 but the next package release
>> does not work (dosemu_1.4.0.7+20130105+b028d3f-1).
>>
>> The following excerpt from the boot.log was with the latest git tree from the
>> 'devel' branch.  The Illegal Op is always the same, although the CPU exception
>> code seems to vary depending on the release of dosemu.  Various parts of the
>> application can be navigated through, but as soon as the directory containing
>> the accounting books is selected the crash occurs.  I presume it is scanning
>> the directory and opening files.
>>
>> I tried various cpu emulation options.  I also found one similar crash report in
>> the bug system that mentioned setting vm.mmap_min_addr to 0.  Neither
>> option helped.
>>
>> Excerpt from boot.log follows.
>> The full Debug +a log is at http://www.bork.org/~mort/boot.log
>>
>> Please let me know if any other info might help.
>> Thanks,
>> mh
>>
>> !!! Illegal op ff e8 2c
>> ==============================================================
>> CPU exception 0x0d err=0x00000000 cr2=00013aee eip=00472bda
>> ==============================================================
>> ERROR: unexpected CPU exception 0x0d err=0x00000000 cr2=00013aee while
>> in vm86 (DOS)
>>
>> Program=sigsegv.c, Line=200
>> EIP: 04f5:0000460f ESP: 23a9:000039e2  VFLAGS(b): 00000 00110111 00000110
>> EAX: 00008400 EBX: 00000012 ECX: 00006662 EDX: 00000000 VFLAGS(h): 00003706
>> ESI: 0000274f EDI: 0000069d EBP: 000039f6 DS: 274f ES: 0288 FS: 0000 GS: 0000
>> FLAGS: PF TF IF DF RF VM VIF  IOPL: 3
>> STACK: 80 c0 4f 27 9d 06 f6 39 4f 27 -> 00 00 f5 04 88 02 46 32 2c 03
>> OPS  : 0e 0a 00 00 89 0e 0c 0a e9 52 -> ff e8 2c 01 c7 06 06 0a 0e 00
>>          ffe8                04f5:460f jmp  far ax
>>
>> -- 
>> Martin Hicks P.Eng.      |         mort@bork.org
>> Bork Consulting Inc.     |   +1 (613) 266-2296
>> --
>> 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
> Hi Martin,
> 	I think you'll need to report this over at http://sourceforge.net/p/dosemu/bugs/ as this list is very quiet these days, especially for development.
>
> Hope it helps,
>
> Andrew
>
>
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.

John

Re: Illegal op ff e8 2c in newer dosemu

[Mateusz Viste]

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

Re: Illegal op ff e8 2c in newer dosemu

[Frederic Herman]

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
>

Re: Illegal op ff e8 2c in newer dosemu

[Paul Crawford]

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

Re: Illegal op ff e8 2c in newer dosemu

[Martin Hicks]

Thanks everyone for the advice.  Sounds like using a 32-bit host OS
fixes this class of problems.

mh

On Wed, May 6, 2015 at 6:05 PM, Paul Crawford <psc@sat.dundee.ac.uk> wrote:
> 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



-- 
Martin Hicks P.Eng.      |         mort@bork.org
Bork Consulting Inc.     |   +1 (613) 266-2296
--
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

Re: Illegal op ff e8 2c in newer dosemu

[Paul Crawford]

I have a VM with Ubuntu 12.04 32-bit for running such stuff, also useful
for compiling Linux code for 32-bit machines (where the dosemu problem
with interrupts prevents 64-bit use).

Regards,
Paul

Re: Illegal op ff e8 2c in newer dosemu

[solarflow99]

ya, I also noticed some games that would exit immediately, that were
known to work in 32 bit.  Has anyone simply tried using the 32 bit
package for this?  or even a 32 bit VM perhaps?

As someone already mentioned, 64 but dosemu can't run dos the same
way, it uses vm86 to do this and I guess not all the problems have
been ironed out yet.


On Thu, May 7, 2015 at 6:00 AM, Paul Crawford <psc@sat.dundee.ac.uk> wrote:
> I have a VM with Ubuntu 12.04 32-bit for running such stuff, also useful
> for compiling Linux code for 32-bit machines (where the dosemu problem
> with interrupts prevents 64-bit use).
>
> Regards,
> Paul
> --
> 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

Re: Illegal op ff e8 2c in newer dosemu

[John R. Sowden]

On 05/06/2015 11:05 AM, 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
>
excellent-thank you!