VOGONS


First post, by HwAoRrDk

User metadata
Rank Newbie
Rank
Newbie

I'm having trouble getting the Logitech MouseWare driver to work on an MS-DOS system, and I can't figure out what the problem is. Other drivers work with the same mouse.

The Logitech driver appears to load fine, and claims it recognises a Microsoft-compatible serial mouse on COM1. Even running the "mouse ?" command after loading shows a mouse type of "Serial (M)" on the correct port, baud rate, etc. But when I start any program that uses the mouse, for example MS-DOS EDIT, the mouse doesn't work. No mouse pointer is even shown on screen. Depending on the driver version, it also for some reason makes EDIT take longer than usual to start. CheckIt doesn't acknowledge any presence of a mouse in its startup checks.

I've tried MouseWare versions 6.30, 7.30, and 8.60. None of them work.

I'm wondering whether the problem is anything to do with the system I'm running it on. It's a Socket A Duron 950MHz with VIA KLE-133 chipset. I saw a thread here (which I can't find again right now, sorry) that said that the Logitech mouse driver doesn't run properly on systems that are too fast. But, apparently newer versions (I forget whether a specific version was mentioned) supposedly work fine? Could that be my problem? I can't find anything newer - version 8.60 seems to be the latest version that has a DOS driver; all 9.x seems to only be for Windows/Mac.

What's odd is that if I load up an 86Box VM emulating a PII 450 and configure that with a 3-button Microsoft Serial mouse on COM1, the Logitech driver (at least, v8.60) works fine there. 😕

Anyone got any idea what the problem is?

By the way, a disclaimer: it's not technically an actual mouse I'm using. It's a device that emulates a serial mouse, that I am 99% sure behaves correctly. Uses the so-called MS+ protocol (1200 baud, 7N1, 3 byte packets with optional 4th byte for middle button), identifies with "M3" response to toggle of RTS line. Works perfectly with Cutemouse and MS driver. I even went to the extent of digging in to the 86Box source code, and I don't see any difference compared to the behaviour of that either.

Reply 2 of 6, by HwAoRrDk

User metadata
Rank Newbie
Rank
Newbie

Primarily I just wanted to check that a common, period mouse driver works with the device I'm using, but I'm also intrigued (or maybe also concerned) by it not working in such an odd way - detecting but not functioning. My quandary is with whether there's a problem with the system I'm trying it on, the driver itself, or the device I'm using.


By the way, I found a MouseWare 9.42 CD image on archive.org that contains the DOS driver - in fact, two copies: one in a 'DOS' subdirectory that reports as driver version 8.50, and one in a 'WIN31X' subdirectory that reports as driver version 8.32. 😕 Neither work. And in fact I have found that these are no newer than on the MouseWare 8.60 disc, which amusingly also contains both versions - v8.50 in the root, v8.32 in 'WIN31X' folder. I also realise I had been using the newest v8.50 all along, because I was trying the one from the root directory.

Nothing newer on archive.org contained a DOS driver, so it appears this 9.42 MouseWare release was the very last to contain Logitech DOS mouse driver.

Reply 3 of 6, by weedeewee

User metadata
Rank l33t
Rank
l33t

As far as I know all the old serial logitech mice had to use their own logitech mouse driver.
The normal microsoft mouse drivers didn't work with them.
It is also the reason I remember not wanting a logitech mouse at the time, needing the logitech driver is annoying.
Something about the logitech mice was different from the mainstream mice. It's probably documented somewhere on the internet.

So you trying to use the logitech mouse driver on something that mostly emulates a "normal" microsoft compatible serial mice will not work, ever,
unless there is a way to convince the driver to use a different method to have the mouse talk to it.

Right to repair is fundamental. You own it, you're allowed to fix it.
How To Ask Questions The Smart Way
Do not ask Why !
https://www.vogonswiki.com/index.php/Serial_port

Reply 4 of 6, by HwAoRrDk

User metadata
Rank Newbie
Rank
Newbie
weedeewee wrote on 2026-01-21, 18:20:

As far as I know all the old serial logitech mice had to use their own logitech mouse driver.
The normal microsoft mouse drivers didn't work with them.

That's not true. The original C7/R7 Logitech serial mice (the square, angular models) did support the Microsoft protocol. In fact they supported several, and were run-time configurable via serial commands or by opening up the mouse and switching jumper links to permanently set the default mode. The whole reason why they would have done that is for compatibility with existing software that only spoke protocols of other pointing devices. In fact, it seems they didn't even have their own protocol, and by default used the 5-byte Mouse Systems protocol. (Source: Logimouse C7 Technical Reference Manual). I believe the following Series 9 (a.k.a. C9) were the same.

As far as I can tell, the later MouseMan series implemented and used by default the 4-byte 'M3' extension to the Microsoft protocol, but possibly also still supported other protocols via serial configuration commands. Haven't been able to confirm the latter, though. (Source: SCO Unix Support Archive: Differences between the Logitech Mouseman and C7/C9 Serial Mouse?)

As you can see, I have already done a lot of research into how Logitech mice are supposed to work. 😜

weedeewee wrote on 2026-01-21, 18:20:

So you trying to use the logitech mouse driver on something that mostly emulates a "normal" microsoft compatible serial mice will not work, ever,
unless there is a way to convince the driver to use a different method to have the mouse talk to it.

The Logitech driver does work with Microsoft-compatible mice, as evidenced by the fact I have it working within an 86Box VM configured for a Microsoft serial mouse.

The attachment Monitor_1_20260122-010651-812.png is no longer available

Reply 5 of 6, by NeoG_

User metadata
Rank Oldbie
Rank
Oldbie

I would expect that since every version of mouseware acts the same, but MS mouse and cutemouse works fine that there is a compatibility issue between the serial mouse emulator and the mouseware driver. It may be one of those things where for example the timing on commands and responses are on the opposite ends of tolerance.

98/DOS Rig: BabyAT AladdinV, K6-2+/550, V3 2000, 128MB PC100, 20GB HDD, 128GB SD2IDE, SB Live!, SB16-SCSI, PicoGUS, WP32 McCake, iNFRA CD, ZIP100
XP Rig: Lian Li PC-10 ATX, Gigabyte X38-DQ6, Core2Duo E6850, ATi HD5870, 2GB DDR2, 2TB HDD, X-Fi XtremeGamer

Reply 6 of 6, by Yoghoo

User metadata
Rank Member
Rank
Member
HwAoRrDk wrote on 2026-01-22, 01:11:

The Logitech driver does work with Microsoft-compatible mice, as evidenced by the fact I have it working within an 86Box VM configured for a Microsoft serial mouse.

It works indeed with all non Logitech mouses that I tested. I like especially the later versions of Logitech MouseWare with the cloaking option. Uses only 1Kb conventional memory.