VOGONS


MASM on DOSBOX

Topic actions

First post, by mars_zg

User metadata
Rank Newbie
Rank
Newbie

-1_774462.jpg
-1_774463.jpg
why AX don't change AND why CS:IP don't point to second ASM

Reply 1 of 8, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

The image doesn't display.

Maybe even post (part of) the source code.

Reply 2 of 8, by eL_PuSHeR

User metadata
Rank l33t++
Rank
l33t++

I can see the images.

[MOVED]

Intel i7 5960X
Gigabye GA-X99-Gaming 5
8 GB DDR4 (2100)
8 GB GeForce GTX 1070 G1 Gaming (Gigabyte)

Reply 3 of 8, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

I can't and i don't see a reason to post images instead of code.

Reply 4 of 8, by mars_zg

User metadata
Rank Newbie
Rank
Newbie

1.jpg
2.jpg

Reply 5 of 8, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Works fine for me.
What debug is that?

Reply 6 of 8, by ripsaw8080

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Looks like the debugger from some version of MS-DOS. The CS:IP is 0703:0000 and the SS:SP is 0703:0002 when you start off... not saying that's why the instruction isn't properly stepped in this case, but having the stack pointer on top of the code being executed can't be good...

Reply 7 of 8, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Looks like the debugger from some version of MS-DOS.

Guess it's rather far from a fullblown 3d-flightsim indeed.

But right, could be due to the bad stack setup, though i'd expect it to behave
a bit different then.

Reply 8 of 8, by mars_zg

User metadata
Rank Newbie
Rank
Newbie

thx for your reply