I just installed Win 3.11 over Win 3.11 and nothing at all changed.
The cursor is still there, stuck in the middle not moving by a single pixel whatever I do with the mouse.
Now the famous C:\WINDOWS\SETUP.EXE works as it should, showing me the correct thing with the options, from which I tried every single one of the available mice selection, but NONE of them works, all doing the same thing except Logitech.
With "Logitech" the cursor disappears completely.
I also tried "Other", put in the directory where I copied my CTMouse, but it can't find some "OEMFILE.INF" file, I also tried from the floppy, but this file is nowhere to be found...

It's strange, this NEVER happened to me before, I always used Win3.11 with this exact mouse and I never had this problem at all... and the strangest fact is that it's happening on MS-DOS 6.22 !!!

Okay and what does ctmouse say when it loads the first time ?
Knowing this could perhaps help us to understand how your mouse is handled by the computer.

Ok, it says this:

1CuteMouse v2.0 alpha 4 [FreeDOS]
2Installed at PS/2 port (wheel present)
3MSCDEX Version 2.23
4Copyright (c) Microsoft Corp. 1986-1993. Tutti i diritti riservati.

if I launch it a second time, it says this:

1CuteMouse v2.0 alpha 4 [FreeDOS]
2Resident part reset to PS/2 port (wheel present)

MSCDEX is the DOS CD-ROM driver. Apparently it gets loaded just after your mouse driver, so the message shows up just after the message about the mouse driver loading.

What happens if you remove the DOS mouse driver completely, reboot, and then try to install the Windows mouse driver?

You mean leaving there only Windows 3.11's "MOUSE.DRV" ?
But that way shouldn't I have problems getting the mouse to work in DOS ???

Yes. The objective is to check whether there is some kind of incompatibility between the two drivers. If the mouse works that way in Windows, you'll need to find another DOS mouse driver that doesn't have this problem.

Although it might be that it's just a problem when combining FreeDOS and Windows 3.11.

but I'm on MS-DOS 6.22 !!!
Anyway, let's try out this experiment 😁

It still doesn't move...

Elia1995 wrote:

but I'm on MS-DOS 6.22 !!!

Oh, got things mixed up with your other thread. 😊

Anyway, let's try out this experiment 😁

It still doesn't move...

Weird. What make is your mouse?

It's an optical PS/2 "Manhattan" mouse with a scrolling wheel. Model: 176972

I NEVER had issues with this mouse with Windows 3.11/DOS, it ALWAYS worked just fine on my 386, 486, on this very PC except this time.....

Elia1995 wrote:

It's an optical PS/2 "Manhattan" mouse with a scrolling wheel. Model: 176972

I NEVER had issues with this mouse with Windows 3.11/DOS, it ALWAYS worked just fine on my 386, 486, on this very PC except this time.....

Okay, that should exclude the mouse itself, especially since you wrote the same happens with a serial mouse. Did you change anything on the computer itself besides the software? An IRQ conflict is explicitly mentioned as a cause for a mouse failing to work in Windows in my manual.

I must say I've only used Microsoft- or Logitech-compatible mouses in Windows 3.11, together with the appropriate OEM drivers...

So... any idea ?

PS/2 uses IRQ12 - is it beeing used by something else (network card, etc.) ?

hmmm.... nope, no sign of IRQ 12 usage in the boot screen where it lists all the IRQs and ISA PnP devices.

Hmm.. Your PC is really strange, but interesting! 😀
My last idea so far: If you have got some spare time, try to install Win9x and check the device manager.
Especially for yellow marks. If you can, write down (or copy&paste or print) the important/strange devices your PC has installed.
Maybe this helps you to find out about their oddities on the web.. Or if you PC has Plug&Pray already, run NSSI or Speedsys.
These are also able to list ISA PnP/PCI devices..

NSSI ?

Elia1995 wrote:

NSSI ?

Navrátil Software System Information.

http://www.navsoft.cz/products.htm

Ah that one... yeah...

anyway I got the mouse finally working... with another mouse driver. Screw CTMouse !!!

I looked for another DOS mouse driver and I found one at a site called "bootdisk.com" or something like that, it's made of a single file "mouse.com", I put it in my C:\ and in C:\WINDOWS and I edited the autoexec so it would "LH C:\MOUSE.COM" at boot.
I then changed the mouse in Windows 3.11 again into "Microsoft or IBM PS/2", rebooted Windows 3.11 and BINGO the cursor FINALLY moves again in Windows 3.11 !!! And it works in DOS aswell.

Well... apparently this CTMouse driver is full of crap, loads of files for a buggy driver which gets stuck in Windows 3.11... this one instead is made of just ONE file (mouse.com) and works in both DOS and Windows 3.11 !! 😁

Elia1995 wrote:

Ah that one... yeah... […]
Show full quote

Ah that one... yeah...

anyway I got the mouse finally working... with another mouse driver. Screw CTMouse !!!

I looked for another DOS mouse driver and I found one at a site called "bootdisk.com" or something like that, it's made of a single file "mouse.com", I put it in my C:\ and in C:\WINDOWS and I edited the autoexec so it would "LH C:\MOUSE.COM" at boot.
I then changed the mouse in Windows 3.11 again into "Microsoft or IBM PS/2", rebooted Windows 3.11 and BINGO the cursor FINALLY moves again in Windows 3.11 !!! And it works in DOS aswell.

Well... apparently this CTMouse driver is full of crap, loads of files for a buggy driver which gets stuck in Windows 3.11... this one instead is made of just ONE file (mouse.com) and works in both DOS and Windows 3.11 !! 😁

So it was the DOS driver. Great it all worked out! FYI, according to my Windows manual, MOUSE.COM or the alternative MOUSE.SYS might be included on the Windows floppies. This driver should also support use of the mouse in windowed DOS programs running under Windows.

Then it's weird that I didn't find it in my C:\WINDOWS directory (when I copied this mouse.com driver from the floppy, it didn't ask me to replace anything)

Elia1995 wrote:

[…]
Show full quote

Copy code to clipboard

1CuteMouse v2.0 alpha 4 [FreeDOS]
2Installed at PS/2 port (wheel present)

I vaguely recall older versions of CuteMouse being recommended in some situations.