1.2  Cloaking Feature

     The MouseWare 6.40 DOS mouse driver is designed to work
     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 your DOS applications. For more information on how
     to install this new feature, refer to the section:
     "Installing Cloaking Feature."




5.5  Installing Cloaking Feature

     Cloaking works in conjunction with a supported memory
     manager to enable the mouse driver to load in extended
     memory. Without cloaking, the DOS mouse driver consumes
     about 27k of conventional or upper memory. Working in
     conjunction with the cloaking interface, however, it
     uses a mere 1k of conventional or upper memory!  This
     1k size footprint is called the stub. The main part of
     the DOS Mouse driver will be loaded in extended memory.
     If the cloaking interface is present the DOS mouse
     driver program will automatically load in extended
     memory.

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

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

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

     Installing Cloaking:
     MouseWare 6.40 copies CLOAKING.EXE in the mouse
     directory but doesn't enable cloaking. You must do it
     manually. Locate the line which loads your extended
     memory manager and insert the cloaking driver right
     after. Extended memory managers are generally loaded in
     the config.sys file.

     Example:
       DEVICE = C:\DOS\EMM386.EXE
       DEVICE = C:\MOUSE\CLOAKING.EXE

     The first line loads the EMM386 memory manager;
     The second line loads the cloaking driver;
     The DOS mouse driver MOUSE.EXE is usually loaded in
     AUTOEXEC.BAT.

     DOS Mouse Driver MOUSE.EXE Memory Management
     Parameters:

     By default, the DOS mouse driver will try to load as
     high as possible in memory following this order:
       1) Extended memory
       2) Upper memory
       3) Conventional memory

     By default, the stub will try to load as high as
     possible in memory following this order:
       1) Upper memory
       2) Conventional memory

     You can customize the DOS driver memory location by
     using the following command line parameters:
     /MEMSA    Loads the stub in upper memory
     /MEMSC    Loads the stub in conventional memory
     /MEMA     Loads the mouse driver in extended memory
     /MEMU     Loads the mouse driver in upper memory
     /MEMC     Loads the mouse driver in conventional memory

     Example
       C:\MOUSE\MOUSE /MEMU /MEMSC

     It should be noted that if the driver can not be loaded
     in the region specified, it will automatically attempt
     to load in the next lowest region of memory.

     Troubleshooting:
     If you experience difficulties with the cloaking
     driver, your system might be incompatible with the
     current version of the cloaking driver.

     To disable the cloaking driver:
     If you run DOS 6.0 or above:
       1. Reboot your computer;
       2. During the reboot process press the F5
       key to disable CONFIG.SYS and
       AUTOEXEC.BAT;
       3. Edit CONFIG.SYS and remove the cloaking
       driver line.
     If you run DOS 5.0 or under:
       1. Reboot your computer;
       2. During the reboot process press
       simultaneously the CTRL SHIFT ALT key.
       This will prevent the cloaking driver from
       loading;
       3. Edit CONFIG.SYS and remove the cloaking
       driver line.