Category : Network Files
Archive   : EIMAIL.ZIP
Filename : README.TSR
³ Notes on EEMail's TSR Mode ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
With EEMail's optional TSR mode, you can now run EEMail as a resident
program. This means you are able to load EEMail then run any other
program, such as WordPerfect, and have the ability to "hot key" right
into EEMail without having to first leave WordPerfect. When you leave
EEMail and return to WordPerfect, you are returned to the same point in
where you left.
A key point to the new ability is that it is Optional. If you already
have a task switching program such as Software Carousel or Windows, you
may not need this ability. If you need to run EEMail in normal mode,
simply run the program without specifying parameters on the command line.
If you choose to run EEMail using the Task Switching facilities built
into the program, you'll need to follow a few guidelines:
1. Always run the program from the parent command prompt. If you load
the program from a Child Environment process, the program may hang
when it tries to reallocate memory. Some menuing systems run
programs by opening another copy of COMMAND.COM, thereby creating
a new child process for this program to run in. If your menuing
system does this, you'll need to run EEMail from the command line
first, then load your menuing system.
2. The Swap Path parameter tells EEMail where to write temporary data
files in the event your memory fills up. You must have sufficient
access rights to this swap directory. In addition, increased network
traffic can occur if you write these files to a network volume. You
should always specify a local drive with at least 1M free for your
swap path location.
3. If you plan to exit EEMail and remove the TSR from memory, EEMail has
to be the last TSR loaded.
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ Recommended Configuration ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
EEMail's TSR works best on at least the following configuration:
386SX 16Mhz (or better, of course) w/2M or more RAM.
HIMEM.SYS or any other EXTENDED memory manager. Extended memory is
the preferred memory type to use.
Hard Disk If EEMail runs out of XMS or EMS memory for swap files,
a local hard disk is preferred to write the overflow data.
Use the [swap path] parameter discussed below to specify
the location of your swap files.
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ New Novell Shells ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
EEMail TSR has been found to work best using the latest Netware Shells.
These new shells support all DOS versions above 3.0. The package comes
with NETX.COM, EMSNETX.EXE, and XMSNETX.EXE. No matter what version of
DOS your users are running, they can use any of these shells. Not only
is it convenient for you to run these shells, but it is also slightly
faster, and EEMail seems to like these the best!
You can find these shells on Netwire (CIS) and on our Tech Support BBS.
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ Getting Started ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
If you want to run EEMail in resident mode, create a batch file similar to
the following:
@echo off
cls
map m:=sys1:eemail
m:
mail /t c:\swappath
f:
menu
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ Startup Parameters ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
/t This parameter tells EEMail to run in resident
mode.
c:\swappath This parameter tells EEMail where to write any
temporary swap files. Replace "swappath" with
any valid drive/path. Local drive is highly
recommended!
Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!
This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.
But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/