Seems weird. Does it happen under DOSBox only? Can the game be run natively?

Well, the game can't run under windows at all.
The game runs fine under pure DOS mode.

I don't know if this may help or not, but I remember when I had the original version of this game (A very long time ago), it had weird problems when you press the "Turbo" button. (That useless button they put in the very old cases). Whenever you pressed the Turbo button a similar behavior happened in this game. It freezed (and sometimes the game just slowed down to a crawl). I am not sure if this is at all relevant. I am just trying to help! 😀 😁

1. What version of DOSBox are you using?
2. Have you tried changing the cycles setting? (maybe it needs to be higher?)
3. Have you tried different core settings? (simple, normal, full, dynamic)

1. What version of DOSBox are you using?

I am running version 0.63

2. Have you tried changing the cycles setting? (maybe it needs to be higher?)

Nope! Never knew I could do this

3. Have you tried different core settings? (simple, normal, full, dynamic)

Nope! Never knew I could do this

<silently walks away, embarrased, looking for the FAQ to read before asking any other questions!!> 🙄 🙄

abcdefg wrote:

<silently walks away, embarrased, looking for the FAQ to read before asking any other questions!!> 🙄 🙄

That's VERY WISE of you. Honesty is good.

Ah. Yeah, you'll definitely want to read the Readme that comes with DOSBox and contains a FAQ inside of it.

Ok, I have done my homework, and now I assume I understand what I am talking about 😀

The game still freezes in area 1-2. Even if I added a few frames in the frameskip, and even if I increase or decrease the CPU cycles.

The interesting part, though, is that I tried the game on another PC, and it freezed too, but in a totally different area. I could play the game till I reached area 2-1 and the game freezed there. I am not really sure what is going on.

Is there some kind of a debug version, where the program monitors what is going on so that I can send it to you?

Thank you very much

DOSBox debugger

You may also want to try a recent CVS build (which contains experimental and work-in-progress changes since 0.63 was released) to see if your problem has been fixed since 0.63 came out.

Also, did you try running with different core settings?