Don't get it? Mouse works fine in Windows 3.x running in Dosbox. What is your exact problem?

That's how the mouse works in DOSBox. It's either captured or released. Ctrl-F1 will open the key mapper and you can assign Cap Mouse to something else.

try the autolock setting

Windowed mode with autolock=false usually works, but it messes up with Win3 for some reason, probably because of how it uses the mouse.

When using the S3 driver we actually know where the pointer is 😉

it does work, but the mouse pointer goes back to the host while it doesn't even come close to windows 3.1 edge.
Any fixes for this? What level of sensitivity do I need to set it to?
Now currently at 400, it is quite acceptable, what do you guys have?
Thanks
Jack

Just turn on the autolock.

I've done that. But the mouse is pretty uncontrollable. When it hasn't reached the top, it already slipped out to windows 7.....
Thanks
Jack

With autolock enabled, it shouldn't be able to escape dosbox' window. That is with lock stock dosbox, not sure whether you patched it...

I beg your pardon, autolock enabled is the expected behaviour. am i able to release the mouse automatically when I move to the edge of dosbox? autolock = false is what I want but i am not able to control the mouse in anyways.
Thanks
Jack

That's the way it works.

I am also seeing some kind of issue with Win3 where the usual autolock=false behavior does not function correctly. It's like DOSBox (or SDL) is confused about where the edges of the window are. Perhaps the issue is related to the S3 video driver for Win3 as hal seems to suggest, although I'm not sure what his point was.