What has the subject line to do with the content? Neither vpc nor dos32a are 16bit pmode apps,
and the former is not related to dosbox, the latter usually not relevant.

wd wrote:

What has the subject line to do with the content? Neither vpc nor dos32a are 16bit pmode apps,
and the former is not related to dosbox, the latter usually not relevant.

Beg your pardon, I'd like to know how to run a 16bit protected mode program in DOSBox. In one of my attempts, I tried to run watcom protected mode debugger in DOXBos, I tried to patch it and still crashed, sorry, this may sound irrelevant, but could you please lend me a hand?
Thanks in advance
Jack

With the information you gave you can ask a clairvoyant for help

you should start with the basics...
dosbox version, host system (OS, specs), program/game name, mounts and steps to start...

Dominus wrote:

With the information you gave you can ask a clairvoyant for help

you should start with the basics...
dosbox version, host system (OS, specs), program/game name, mounts and steps to start...

Sorry:
DOSBOX - 0.74
Host - win7 ultimate 64bit
program - wd.exe (watcom protected mode debuggger)
Patched with bd.exe which came with dos32a.
The patch was successful, but then I ran wd.exe, crashing occurred.
DOS/32A runtime (6005): DOS/4G API calls not supported

does it run unpatched?

Dominus wrote:

does it run unpatched?

Suddenly it works....
I have re-installed it, maybe I have stuffed it up before
Just one question, are all 16bit protected mode programs
supported by DOSBOX?

Thanks for your help

tried different cores, memsize?

Dominus wrote:

tried different cores, memsize?

Thanks it works now (see previous posting)
I wonder are all 16bit protected mode programs supported by DOSBox 0.74?
Update: Now that I understand why, i used ver. 0.72 debug before.
Was there a problem with ver. 0.72 with 16bit protected mode programs?
And also how do I compile ver. 0.74 with VS2008 to activate the debugger?
I have tried to put --enable-debug in "command argument" of the properties window but no good
Thanks it really great help

16bit protected mode programs are supported, but what is not supported are dos debuggers because afaik debug registers are not included in the cpu emulation.

Debuggers are supported (trace flag, int3) in real/v86/pmode, just as gulikoza
says the debug registers are just dummies because they're not used by games
and very hard to emulate.

Other than that, since the full x86 cpu is emulated all 16bit and 32bit pmode
applications *should* work cpu-wise minus emulation bugs.

wd wrote:

Debuggers are supported (trace flag, int3) in real/v86/pmode, just as gulikoza says the debug registers are just dummies because […]
Show full quote

Debuggers are supported (trace flag, int3) in real/v86/pmode, just as gulikoza
says the debug registers are just dummies because they're not used by games
and very hard to emulate.

Other than that, since the full x86 cpu is emulated all 16bit and 32bit pmode
applications *should* work cpu-wise minus emulation bugs.

Thanks, both of you. So I might as well give up.
But one thing, where do I get libcurses, hard to find really
Jack

AFAIK gnu.org ncurses

About debuggers in dosbox: *what* do you want to debug? pmode applications
are usually tricky to debug due to mode switches (dunno how good the watcom
debugger is at this in general) so you're best off with the dosbox debugger.

wd wrote:

About debuggers in dosbox: *what* do you want to debug? pmode applications
are usually tricky to debug due to mode switches (dunno how good the watcom
debugger is at this in general) so you're best off with the dosbox debugger.

I want to have a call stack. That's all 😀
Thanks wd
Jack

Well that's why i'm asking what application you want to debug,
anything coming from assembler or including some nice hacking
may destroy any possibility of having a call stack.
Your best bet is "watcom compiled -> watcom debugger" and similar,
but for the general case i don't know anything that could provide much
more than easy access to the regular stack.

wd wrote:

Well that's why i'm asking what application you want to debug, anything coming from assembler or including some nice hacking may […]
Show full quote

Well that's why i'm asking what application you want to debug,
anything coming from assembler or including some nice hacking
may destroy any possibility of having a call stack.
Your best bet is "watcom compiled -> watcom debugger" and similar,
but for the general case i don't know anything that could provide much
more than easy access to the regular stack.

A Chinese Game Called Etin Tao Lung Kee By Soft World.....

Any common pmode extender?

wd wrote:

Any common pmode extender?

I think the DOSBox debugger is sufficient, because the game doesn't require a protected mode extender, but on the other hand, because of my lack of experience in debugging, I'd like to get a call stack while I am debugging, so I want to use Watcom Debugger side-by-side with the DosBox debugger. That's the story.

http://img269.imageshack.us/img269/8089/game3f.jpg

This is the screenshot of the game. If you have already known where the problem is, I can avoid the extra debugging efforts.
You could give me some hints where to attack this problem if you can...😀

Thanks
Jack

I wish there was a way to run windows 95 games without actually having to install windows, making a windows game behave like a dos one without those little details of making a image, booting, navigating to the folder etc.

There isn't though.