VOGONS


Mouse won't work in Windows 3.11 (works fine in DOS)

Topic actions

  • This topic is locked. You cannot reply or edit posts.

First post, by kanecvr

User metadata
Rank Oldbie
Rank
Oldbie

Hi guys. So my A4Tech serial mouse won't work in windows 3.11. It works fine in dos, using either cutems.exe or mouse.com. Actually it doesn't even work in windows setup... Anybody encounter something like this before?

Reply 1 of 18, by Caluser2000

User metadata
Rank l33t
Rank
l33t

Yes. You need to tell Windows 3.11 what type of mouse it is in it's setup routine. It doesn't rely on the dos driver once you've loaded windows. You can do this by typing setup from inside the windows directory in dos.

When you restart windows you should see a mouse pointer.

There's a glitch in the matrix.
A founding member of the 286 appreciation society.
Apparently 32-bit is dead and nobody likes P4s.
Of course, as always, I'm open to correction...😉

Reply 2 of 18, by kanecvr

User metadata
Rank Oldbie
Rank
Oldbie

I did. At the first setup screen it detected the mouse as "Logitech" but after it was done installing, the mouse didn't work. I tried ALL win3.11 drivers, none work.

If for example I run command prompt under win 3.11 and run cutems or mouse.com and launch notron commander, the mouse will work - but as soon as I return to windows it stops working.

Reply 3 of 18, by kanecvr

User metadata
Rank Oldbie
Rank
Oldbie

Ok, here's what I've done so far:

- tried running win3.11 with a dos mouse driver running (tried both cutems and mouse.com)
- tried reinstalling win 3.11
- tried changing mouse driver from windows (everything from the genius, logitech, mouseware and microsoft drivers)
- tried a different serial / i/o controller
- tried switching from com1 to com2

None of the above got mouse to work in windows...

Reply 4 of 18, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

From my Dosbox guide

When you choose the Tseng drivers when you install Windows, the mouse pointer might not be visible. To fix this go back to the DOSBox prompt, change dir to the Windows directory ("cd windows") , run setup again and then choose the VGA or SVGA drivers that come with Windows 3.1x. Start Windows again (your mouse pointer should be visible now) and then run setup from inside Windows to choose the Tseng drivers.

This might be applicable to real hardware as well. So changing graphics drivers might work for you as well.

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox
DOSBox SVN snapshot for macOS (10.4-11.x ppc/intel 32/64bit) notarized for gatekeeper

Reply 10 of 18, by Caluser2000

User metadata
Rank l33t
Rank
l33t

Try the drivers from this page http://freshreviews.biz/searches/result.php?q … driver+download

There's a glitch in the matrix.
A founding member of the 286 appreciation society.
Apparently 32-bit is dead and nobody likes P4s.
Of course, as always, I'm open to correction...😉

Reply 12 of 18, by Caluser2000

User metadata
Rank l33t
Rank
l33t

It's a 133k *.exe What OS and browser are you using?

Try putting a copy of mouse.com in the windows directory.

There's a glitch in the matrix.
A founding member of the 286 appreciation society.
Apparently 32-bit is dead and nobody likes P4s.
Of course, as always, I'm open to correction...😉

Reply 14 of 18, by kanecvr

User metadata
Rank Oldbie
Rank
Oldbie
Caluser2000 wrote:

It's a 133k *.exe What OS and browser are you using?

Windows 8.1 x64 + latest version of chrome.

Caluser2000 wrote:

Try putting a copy of mouse.com in the windows directory.

Ok I'll give that a try.

NJRoadfan wrote:

Does the mouse have 3 buttons and a switch on the bottom? Make sure its set to 2-button/Microsoft mode.

It has only two buttons, no scroll wheel, and it has no such switch. It will only work in microsoft mode. Like I said, it works fine in dos or dos games ran under win 3.11

Reply 16 of 18, by Marco

User metadata
Rank Member
Rank
Member

All I had similar issues with my serial Logitech mouse. Dos perfect win95 perfect win311 fail. Thus it could only be a sw issue. I managed it by using the Logitech mouseware 6.3 software / lmouse driver included. Mouse works flawless afterwards.
So it indeed was for me an incompatible Logitech mouse driver provided by win311

1) VLSI SCAMP 311 | 386SX25@30 | 16MB | CL-GD5428 | CT2830| SCC-1 | MT32 | Fast-SCSI AHA 1542CF + BlueSCSI v2/15k U320
2) SIS486 | 486DX/2 66(@80) | 32MB | TGUI9440 | LAPC-I