Yes, you need to install a mouse driver for Windows (using setup.exe). A DOS mouse driver is not going to work in Windows.

derSammler wrote:

Yes, you need to install a mouse driver for Windows (using setup.exe). A DOS mouse driver is not going to work in Windows.

So would this be a second mouse driver just for Windows or should I remove the DOS driver and then install the Windows driver for support in both Windows and DOS?

The Windows mouse driver is completely independent and used for Windows only. You need both.

derSammler wrote:

The Windows mouse driver is completely independent and used for Windows only. You need both.

Ah, OK. Well, I will have to look into getting that setup and working. Thanks!

You can enable seamless mouse support in Windows 3.1 DOS boxes,
if you are also loading the original MS-Mouse (Version 8.?? ) driver for DOS at the outset.

Also, I recall that there was an issue with the latest version of CuteMouse.
For serial mice, an older version might be a better choice.

But I'm speaking under correction here.
Could well be possible that my information is oudated by now.. 😅

Anyway, using a serial mouse for Windows 3.1 is a wise choice.
In stark contrast to PS/2 mice. They behave "jumpy" or jerky in Windows 3.1.
Has something to do with lost packets..

(By the way, here's a good DOS driver that helped
me a few times with troublesome mice.. ^^)

derSammler wrote:

A DOS mouse driver is not going to work in Windows.

Are you sure about it? I'm using Microsoft Mouse Driver 8.20 and it works well under both DOS and Windows 3.11.

True, MS-Mouse driver 8.2 (DOS) is compatible with both DOS and Windows 3.x DOS boxes.
But I assume he meant that Windows 3.x requires a separate Windows mouse driver also (mouse.drv in system.ini).

The original MS-Mouse floppy disks contained both of them (DOS/Windows), I believe.

That's right. I have an original Microsoft Mouse disk and there are both files on it:
- mouse.com
- mouse.drv

And it also contains a mouse.sys file.