try autolock=true

autolock is already true, the problem is elsewhere...
read carefully the first post from the link i provided to understand the problem...

i think reading that carefully won't help,
is you English that broken too? if not, describe it again.

well, it has happened that in a single map game, after many hours of playing, the cursor started to get stuck on the horizontal axis. scrolling around the map unlocked it for a while...
i use WinXP and dont remember if DosBox 0.73 or 0.74.

so try to remember as we don't care about 0.73

i guess it was 0.74, because i remember no music, as i didnt use GOG's DosBox setup (0.73).

are you trying to say you haven't bothered to configure the game properly before playing?

no, just dont care about music..

Does it help if you save a game, quit dosbox, start dosbox again, load game and continue playing?

it does help, but doesnt fix the bug...
what i really would like to know is if this issue is related to DosBox or not....
is it possible no one else has experienced it in past??

today the issue has happened again!
I'm using DosBox 0.74 with default config, an AthlonXP, a Nvidia 7900GS, WinXP Pro SP3.
after 4h15m of playing on a free scenario, the mouse pointer got stuck on the horizontal axis, starting to move only vertically.
after some attempts, by means of the scrolling mode too, I was able to unlock the horizontal axis, but strangely the mouse didn't move anymore to the right over an invisible vertical line inside of the screen.. it was like the mouse pointer was reaching the right border of the screen, but in fact it didn't!
any help? my big worry is to understand if this bug is related to DosBox or to the game itself....
thanks in advance.

may anyone else try to repeat the issue playing with DosBox please?

When I played Settlers II last time, I had that bug, too. I dont remember the version of DosBox I used back then. The bug was exactly as in your description. It also occured after some hours of gameplay. For this reason I really dont want to reproduce it, sorry.

Don Meu wrote:

after 4h15m of playing

^ I don't think you'll get much feedback because of this.

If it's really that important to you, I suggest you try some things yourself, like watching the mouse-related messages in a debug build of DOSBox to see if erroneous ranges or some such are being given to the mouse driver by the game, or try using Microsoft mouse drivers, or cutemouse.

I've tried to debug this long time ago but it really happens only after several hours of gameplay so you can't really get anywhere that way.

Just remember to restart dosbox after two hours 😉

wd wrote:

I've tried to debug this long time ago but it really happens only after several hours of gameplay so you can't really get anywhere that way.

if you don't have the time to reproduce the bug, I can do that for you!
just let me know what to do to help you to debug it!
p.s.
I'm currently playing (testing) for hours Settlers II without DosBox and the bug doesn't occur...

At the moment I don't remember exactly how saves work in S2gold, but I think they can be created/loaded arbitrarily (if not ignore the text below).
A savegame that can reliably reproduce the bug *without* playing for too long would be nice.
Like "load the game, wait for 10 seconds and it always crashes" could help.

But iirc it only happened after long in-game time so savestates would not work to reproduce it,
but maybe it works out differently for you.

Thanks for offering your help!

Wonder if the turbo button could speed it up...

have your game so the opponent can't do anything, set cycles rather low, frameskip 10 then keep ALT-F12 pressed.