VOGONS

Search

Common searches

Possible CPU emulation bug...

Topic actions

First post, by madcrow

Posted on 
User metadata
Rank Newbie
Rank
Newbie

... found using Borland Paradox 4.5

I know that Databases aren't games, but when trying to use one, I encountered something odd: Borland Paradox 4.5 always seems to crash and burn within a minute or so of being started, always with the same error message: "Unexpected condition: GP 76fc AT PARADOX:03:70c1 -- Leaving Paradox"

I'm using vanilla 0.72 with standard settings, so there may be some tweak to work around this (and if there is, please share" , but otherwise I may have uncovered some kind of bug in the emulated CPU.

Reply 1 of 3, by MiniMax

Posted on 
User metadata
Rank Moderator
Rank
Moderator

You could try different CPU emulation methods in DOSBox.

Before running your program, issue of the commands:

C:\>core simple
C:\>core
C:\>paradox

C:\>core normal
C:\>core
C:\>paradox

C:\>core dynamic
C:\>core
C:\>paradox

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 2 of 3, by madcrow

Posted on 
User metadata
Rank Newbie
Rank
Newbie
MiniMax wrote:
You could try different CPU emulation methods in DOSBox. […]
Show full quote

You could try different CPU emulation methods in DOSBox.

Before running your program, issue of the commands:

C:\>core simple
C:\>core
C:\>paradox

C:\>core normal
C:\>core
C:\>paradox

C:\>core dynamic
C:\>core
C:\>paradox

Tried that and Paradox appears to crash the same way no matter which core I use. Other Borand programs from the area (dBase IV 2.0, dBase V and Quattro Pro 5) seem to work fine, so I doubt this is a manifestation of the "Borland runtime libraries hate fast CPUs" bug, so I'm totally puzzled as to what it might be.

Go to top of page Go to top of page
Back to DOSBox Development
Close window
Close window