VOGONS

Common searches


Tiny mouse driver ?

Topic actions

Reply 20 of 25, by Jo22

User metadata
Rank l33t++
Rank
l33t++
red_avatar wrote:

Anyone know another low-memory mouse driver?

CuteMouse not working properly
😀

"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel

//My video channel//

Reply 21 of 25, by Paralel

User metadata
Rank Member
Rank
Member

This entire discussion on cloaking is fascinating. I wonder if I can use it to hide the TSR's that certain games hate since the use DOS extenders and allow the TSR to continue to function.

Reply 22 of 25, by dr_st

User metadata
Rank l33t
Rank
l33t
red_avatar wrote:

Sorry to dig up this topic - I actually used Cutemouse but its compatibility with DOS games is rather iffy. In fact, the first game I tried, the mouse went haywire when I pressed the right mouse button. I had to revert back to my old PS/1 mouse driver. Anyone know another low-memory mouse driver?

You probably were 'lucky' to try the only DOS game (well, probably one of very few) that actually has problems with Cutemouse. I have tried it with dozens of games and don't recall any issues like that. I stopped using any drivers except Cutemouse years ago. However, there may be some dependency on CPU speed, motherboard or other system components.

https://cloakedthargoid.wordpress.com/ - Random content on hardware, software, games and toys

Reply 23 of 25, by akula65

User metadata
Rank Oldbie
Rank
Oldbie

The following is from the Logitech MouseWare Version 7.30 Readme:

2. Cloaking Feature for DOS and Windows 3.1 The MouseWare DOS mouse driver works in conjunction with a special interfac […]
Show full quote

2. Cloaking Feature for DOS and Windows 3.1

The MouseWare DOS mouse driver works in conjunction with a
special interface program called "Cloaking". The CLOAKING.EXE
interface program allows the DOS mouse driver, MOUSE.EXE, to be
loaded in extended memory, freeing valuable conventional and
upper memory for DOS applications. CLOAKING.EXE is
automatically installed during the standard MouseWare
installation for Windows 3.1.

Cloaking works in conjunction with a supported memory manager
to enable the mouse driver to load in extended memory, using a
mere 1k of conventional or upper memory.

CLOAKING.EXE will work with any of the following extended
memory managers:

EMM386.EXE Microsoft
HIMEM.SYS Microsoft
RM386.EXE 3.03 or later Helix
QEMM386.SYS 7.1 Quarterdeck
386MAX.SYS 5.0 Qualitas

You will need to be running one of these programs in order to
use CLOAKING.EXE. The EMM386.EXE and HIMEM.SYS programs are
included with DOS versions 5.0 and above, and with Windows.

Installing Cloaking:

Under Windows 3.1, the installation program copies CLOAKING.EXE
in the mouse directory and loads CLOAKING.EXE in your
AUTOEXEC.BAT file. This will occur if your DOS version is 6.0
or greater, you are running EMM386.EXE, and you are not already
loading a version of CLOAKING.EXE.

I you are running DOS only, you will need to do the changes
manually. If you wish to install CLOAKING.EXE in the CONFIG.SYS
file, add the line: "DEVICE=C:\MOUSE\CLOAKING.EXE" after the
supported memory manager is loaded. If you wish to install
cloaking in the AUTOEXEC.BAT file, add the line:
"C:\MOUSE\CLOAKING.EXE" before the mouse driver is loaded.

This MouseWare package (LOGI730.ZIP) can be found at Uwe Sieber's site among others:

https://www.uwe-sieber.de/util_e.html

Reply 24 of 25, by rasz_pl

User metadata
Rank l33t
Rank
l33t

Cloaking sounds like switching execution context nightmare? Wonder if it had any performance overhead versus running normal driver.

Open Source AT&T Globalyst/NCR/FIC 486-GAC-2 proprietary Cache Module reproduction