run it with core=normal. (this is very important!)
the changes to config.sys aren't needed

Qbix wrote:

run it with core=normal. (this is very important!)

Why's that important?

Also, the autoexec.bat changes can go in the [autoexec] section of your dosbox config file (Start Menu -> DOSBox -> Edit DOSBox Configuration)

as else it won't run 😀
clipper programs need a special exception which is only supported in that core

Good to know, thanks!

So I guess DOSBox does have some non-game-specific fixes after all - or is there a game out there that uses clipper database stuff?

yeps 😀

@Qbix: I have no problems compiling or running Clipper apps with dynamic core; do you know what special conditions might exist to require the exception you speak of? Is it maybe the Clipper debugger or something that's not part of the standard Clipper libraries? I have tried Clipper Summer '87 and Clipper 5, both of which use Microsoft C runtime code (earlier versions used Lattice C), with Borland's TLINK and the Blinker overlay linker to link the executables.

thanks for the answers

how do I run it with core=normal??????

and with the autoexec.bat config, I just write down those commands at the end of the notepad??

theunfor wrote:

thanks for the answers

how do I run it with core=normal??????

Look for the core=auto in the dosbox config file and change it to core=normal

and with the autoexec.bat config, I just write down those commands at the end of the notepad??[/quote]
that should work, although i'd put it on the line right after [autoexec] just to be safe

I've implement the changes, yet is not working, or do I need to restart my computer?

Just need to restart DOSBox.

still not working 😖

What's the exact error message?

"cannot open config.sys"

"cannot modify autoexec.bat"

Try making dummy (empty) config.sys and autoexec.bat files in your virtual c:\ inside of dosbox.

ripsaw8080 wrote:

@Qbix: I have no problems compiling or running Clipper apps with dynamic core; do you know what special conditions might exist to require the exception you speak of? Is it maybe the Clipper debugger or something that's not part of the standard Clipper libraries? I have tried Clipper Summer '87 and Clipper 5, both of which use Microsoft C runtime code (earlier versions used Lattice C), with Borland's TLINK and the Blinker overlay linker to link the executables.

I don't know the specific version of clipper involved
but it is the exception in this instruction

1 	CASE_B(0x88)												/* MOV Eb,Gb */

If I'm reading the code for that opcode correctly, the exception occurs under protected mode. Clipper was real mode only until sometime after Computer Associates acquired the rights from Nantucket, and linkers like Exospace (another CA acquisition) and later versions of Blinker stared offering pmode. I'm guessing it's a CA-Clipper pmode executable that needs the exception, but real mode executables are probably OK with dynamic core.

HunterZ wrote:

Try making dummy (empty) config.sys and autoexec.bat files in your virtual c:\ inside of dosbox.

how do I Do it?

Create a new text document. Name it config.sys. Repeat and name it autoexec.bat. Place these files in the folder you're mounting as C.

I've done it, but it says

"cannot load z:\config.sys"

and still

"cannot refresh autoexec.bat"