auron wrote on 2024-10-19, 08:09:

i'm wondering why the logitech drivers even report a VGA being present - doesn't seem like something that should concern a mouse driver, or maybe it does, given all the options with blinking cursors and such.

The mouse driver can be told to render the mouse cursor (including in graphics mode) so the application doesn't have to do it. This involves saving what it draws over (so it can restore it when the cursor moves) and detecting when the video mode is changed.

wbahnassi wrote on 2026-09-30, 22:59:

You try to nudge one pixel, but CuteMouse resists that nudge until you make a bigger movement on the physical device, making you lose accuracy and precision

Well there is this part : https://github.com/FDOS/mouse/blob/master/ctmouse.asm#L992
They are ignoring (i.e. dropping) small mouse movements (<=4) when the sensitivity is at the default value or higher (faster).
I never got the point of that.
Is it possible this is what you're seeing? Does it still happen if you set the sensitivity via /R to something like /R3 or the like (which seems to disable this, and I think should match "sensivitity = 30" in MS Mouse, but I'm not sure).

Maraakate wrote on 2026-10-01, 12:39:

You're taking it very personally. If this driver does everything for you then keep using it. Nobody is forcing you to use a different mouse driver. Good thing you can pick and choose one easily under DOS.

My mouse driver is on a different thread 😀
I'm not taking it personally, but please understand I can object to your critique, in the same way you can criticize whatever software you want . it's not an attack on you either, ignore it if you don't like it.

This is not really a complicated concept, there is a incoming mouse delta, you multiply it by a factor, and you get the final mouse movement.
If two mouse drivers use the same factor, then the speed/sensitivity is identical between them.
There is some magic in what you do to compute that factor (because often it will be hidden behind some "easy to use" setting),
there is some magic in what you do with the "remainder" of the division (e.g. if your factor is less than 1.0 and your final movement is less than one pixel),
and then to top it off there is some very heavy black magic called "acceleration", where you may change the factor based on the previous speed. But luckily Cutemouse already doesn't have that to begin with.
"programmers make bugs" here is not the point, my point is more "there are too few degrees of freedom to make a bug".
If there's a difference in behavior, it's going to be an interesting story behind it.

based and ctmouse-pilled. thanks so much!