Viper/LITE v2.0 - (c)1992-94 Chris Lautenbach
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Additional notes - September 14 1994

The VIPER.EXE file included in this archive is a scaled-down version of
Viper, known as Viper/LITE.

Installation:

1. Unzip/INSTALL the normal VIPER200.ZIP distribution archive.  Only
   VIPER.EXE is a protected mode program, so the installation/setup can
   be performed without it.

2. Unzip this file (VLITE200.ZIP) over your \VIPER directory files, it
   will replace your VIPER.EXE file with the real mode version.

3. That's it!  :)  You're done.  Take a break.

Unlike the normal distribution version of Viper, this version runs in
real mode rather than protected mode (DPMI), and uses no EMS/XMS for it's
own data.  It does however, use EMS for it's overlays and while shelling
to external programs (if available).

Since Viper/LITE uses overlays, do NOT use any EXE compression programs on
it, or any of Viper's EXE files.  It will not work, and will corrupt your
VIPER.EXE.  (Examples of these programs: PKLite, LZEXE, Diet, etc)

Viper/LITE may be used in these instances:

1. There is not enough memory for the normal version (eg: less than 2
   megabytes).

2. The memory is oddly configured (eg: 640k + a memory expansion board whose
   driver does not provide DPMI memory, only EMS/XMS)

Viper/LITE has these differences from Viper:

1. Macros are disabled.  The macro code can gobble up a fair amount of RAM,
   and the routines are not totally debugged for real mode, so you can't
   use them in Viper/LITE (actually, they aren't even compiled into the EXE).

2. Internal LZH is not present.  The internal LZH routines require about a
   32k static buffer, and therefore not having them frees up about 40k of
   RAM (32k buffer + 8k code).

It is important to watch your available memory, since it is possible to
run out of memory.  Under most circumstances, Viper will recover gracefully
from such an error, but this version is not as well tested as the normal one,
so be careful.

If you do run out of memory; here are some things you can keep in mind to
reduce memory consumption:

1. Try to keep as few TSR's loaded as possible.

2. Try using an external editor such as QEdit or Boxer.  When shelled, Viper
   will swap itself to disk, making room for the editor you've selected.

3. Keep your packets smaller -- the one thing that makes more difference
   than any other is the number of conferences.  If your BBS allows you to
   send only the conferences you have selected (eg: Small CONTROL.DAT), do
   it.

4. Turn Other Options|Load Only Confs with Mail ON.  This will make Viper
   only load those conferences which actually have mail in them.

Enjoy!