Dec 082017
Powerful E-Mail messaging system.
File ECLITE11.ZIP from The Programmer’s Corner in
Category Network Files
Powerful E-Mail messaging system.
File Name File Size Zip Size Zip Type
CUSTOM.S 32695 6051 deflated
ECOMM.EXE 336150 136633 deflated
ECOMM.HLP 66760 21282 deflated
ECOMM.S 39429 7721 deflated
ECOMMZIP.DOC 1573 674 deflated
HOTROD.DOC 11390 3607 deflated
ORDER.FRM 2319 574 deflated
README.DOC 14789 5222 deflated
ROUTING.BIN 1024 165 deflated
SRECORDS.DOC 25004 6747 deflated
SRECORDS.ZIP 22343 18373 deflated
TCOVL.EXE 41742 23232 deflated
TCOVLTRC.EXE 49980 27293 deflated
TSR.EXE 31733 16741 deflated
TSRCOMM.BAT 69 65 deflated

Download File ECLITE11.ZIP Here

Contents of the README.DOC file

Welcome to ECOMM!

This file contains useful information about:

- the files that ECOMM uses

- how to set up and run ECOMM

- new (as yet undocumented) features of ECOMM

You are heartily encouraged to examine and evaluate ECOMM. However, this
is NOT public domain software, and only with your support will we be able
to continue to enhance ECOMM and to bring more of such high quality
software to the shareware market.

Registered users of ECOMM/Lite get:

* 90 days of free technical support
* A unique personal ID number
* A version of ECOMM with:
- No registration reminders
- Interprocess communications hooks to let you build your own custom,
background programs around ECOMM (includes examples in C)
* The ECOMM Reference Manual

ECOMM/SA, ECOMM/LANmail, and ECOMM/Weather users also get:

* 1 full year of free technical support
* Support for DigiBoard multi-port serial boards

To register or buy ECOMM software, you can
- Call HXJ with your Visa / Mastercard handy.
- Fill out and send or fax to us the enclosed ORDER.FRM file.
- Fill out the Order_ECOMM_Today S-record in ECOMM and send it to HXJ.

HXJ, Inc. Phone: 301-424-0070
966 Hungerford Drive, Suite 3 Fax: 301-738-1026
Rockville, Maryland 20850

Files used by ECOMM:

As you will find out shortly, ECOMM is a background processing
communications / e-mail program. In order to make ECOMM work for you,
the following is a list of the files that ECOMM uses, and the
significance they have. Please read this list and keep it handy as you
set up ECOMM and make it work.

EXE - executable files
ECOMM.EXE - this is a foreground program that serves as a mailbox
manager, lets you set up your own configuration, and lets you create
and send messages (including compiling new S-record formats).
ECOMM.EXE has an EXTENSIVE on-line context-sensitive help system that
should help most users with most problems. ECOMM.EXE also accepts a
number of command-line arguments that are documented in the help system
and that are briefly listed when you enter an illegal option or you use
the -? option.

TSR.EXE - a utility program that lets you send commands to the
communications TSR once it is loaded. TSR.EXE also loads the
communications program into memory by determining where unused user
interrupts can be found and creating a batch file that loads the
communications TSR into memory and runs any auxiliary programs.
TSR.EXE is executed within the TSRCOMM.BAT file to determine whether
the TSR has already been loaded, and, if not, it creates a batch file
called TCOMM2.BAT that loads TCOVL.EXE into memory. TSR.EXE is also
used to:

- stop the TSR from beeping,

- determine the current version loaded in memory,

- unload the TSR from memory,

- various other asundries.

TCOVL.EXE, TCOVLTRC.EXE - these are two versions of the communications
TSR. The latter prints tracing messages to the screen and can be
useful when trying to determine why something isn't working. Both of
these programs have little or no error checking and require a very
strict set of command-line arguments, since all of the error checking,
etc. is performed by TSR.EXE when it creates the TCOMM2.BAT batch file.
The standard method for loading one of these TSRs into memory is to
type "TSRCOMM" at the DOS command-line, (or "TSRCOMM TRACE" to run the
tracing version).

NET.EXE - for purchasers of ECOMM/LANmail, a full-featured LAN e-mail
system, the NET.EXE program is a hook into the communications TSR that
puts messages in the appropriate mailboxes and submits externally bound
messages to the communications TSR to be sent out, and notifies LAN
workstations when a personal message has arrived for the user of that

BEEP.EXE - for purchasers of ECOMM/LANmail, the BEEP.EXE program is a
TSR that is loaded on an individual workstation that receives NetBios
datagrams from NET.EXE and conducts the beeping on that workstation to
notify its user that a message has arrived.

MUTATE.EXE - this file is not used by ECOMM, but rather is used when
the installation batch file modifies the appropriate ECOMM batch files
to reflect the configuration on this machine.

BIN - binary (configuration / data) files
ROUTING.BIN - the entire routing table is store in this file. This
includes every site that you might want to communicate with and amounts
to nothing more than a glorified telephone directory. This is a binary
file and can only be modified through the Config/Routing option in

This file MUST contain a definition of your own site as well as
everyone else's, since your ports and communications parameters are
always defined in terms of the routing table. Hence, you cannot
configure TSRCOMM nor communicate at all until you have set up your
routing table. For your convenience, we include a standard routing
file with ECOMM that should help you get started.

TCOMMCFG.BIN - this file contains a definition of your computer's
communications environment. This includes: mailbox directories,
network directories, serial ports, communications parameters, and
hardware, timeout sets, network aliases, redirection and resending
rules, modem initialization and dialing strings, etc. This file is
created and modified through the Config/Personal configuration menu in

This file MUST exist and it must define your communications system
for anything in ECOMM to work right or even for the communications TSR
to load into memory. If you ever decide to rearrange your computer or
change things radically, you can just delete this file in DOS and
create a new one.

MESSAGEQ.BIN - a current list of all the messages that TSRCOMM has
queued up to be sent. Messages that are sent must be placed in the OUT
box first, and then submitted to TSRCOMM using the ECOMM.EXE program.
The are removed from the MESSAGEQ.BIN file when they have been
successfully received at the destination, or if they cannot be sent.
If they cannot be sent, they are marked with an error, and the current
status can be seen in the Mailbox/Unsent messages part of ECOMM.EXE.

To truly clear out your entire mailbox and start fresh, you should
delete all the files in your OUT box, and delete the MESSAGEQ.BIN file.

BAT - batch files
TSRCOMM.BAT - the batch file that executes TSR.EXE to determine whether
the communications TSR can be loaded and if so, runs the TCOMM2.BAT
file that is created by TSR.EXE

TCOMM2.BAT - this file is not included with ECOMM, but is created by
TSR.EXE when you want to load the communications TSR. It is a
transient file and can be deleted with no side affects.

S - resource files
ECOMM.S - this is a resource file used by ECOMM.EXE. It contains a
definition of ECOMM's user interface. This means that every word,
color, phrase, menu item, field, and window you see when you run
ECOMM.EXE is contained in this externally defined file. Although
If you do, ECOMM.EXE will surely crash. When you want to redefine any
item in ECOMM using the ECOMM.S file you MUST do so by changing the
appropriate .SRC file and recompiling it using the -E command-line
option. See the SRECORDS.DOC file for a description of how you can do

When you use ECOMM with different screen modes, you are encouraged to
create a new version of this file for every mode you use. For example,
if you start using ECOMM in 43-line EGA mode, copy ECOMM.S to ECOMM43.S
and recompile the ECOMM .SRC files. For 50-line VGA mode, you would
create a file called ECOMM50.S, etc.

CUSTOM.S - similar to the ECOMM.S file this contains the definitions of
all of the S-records supported by your ECOMM. The correct definition
of an S-record must exist in your CUSTOM.S file in order for you to
read a message created with that S-record. Like the ECOMM.S file,
although this file is an ASCII file, you MUST NOT edit it with a text
editor. Instead you should recompile the appropriate .SRC files (as
per the SRECORDS.DOC file) for the appropriate video mode.

Like the ECOMM.S file, the CUSTOM.S file can come in different flavors
to support different video modes (e.g. CUSTOM43.S, CUSTOM50.S, etc.).

HLP - help system
ECOMM.HLP - contains the entire context-sensitive help system. Please
do not modify this file unless you really know what you are doing.

CFG - program configuration (command-line option) files
ECOMM.CFG, TSR.CFG - you can put any standard command-line options for
the ECOMM.EXE or TSR.EXE program in an ASCII file called ECOMM.CFG or
TSR.CFG, respectively. Each parameter must occupy its own line and
start in the first column of that line.

DOC - documentation
README.DOC - this file.

SRECORDS.DOC - details creating S-records through the ECOMM S-record
compiler and describes the supported commands and caveats.

HOTROD.DOC - a guide to using ECOMM with: Windows 3.0, DesqView,
QEMM386, 386^max, and the ALL Charge Card.

ECOMMZIP.DOC - a listing of the ECOMM distribution zip file, to verify

FRM - order form
ORDER.FRM - a form that can be printed, filled out, and sent to HXJ to
order ECOMM software products.

ZIP - zipped up files and directories
SRECORDS.ZIP - the resource definitions for the ECOMM.S and CUSTOM.S
files. The .SRC files are stored with pathnames to keep them separate.
To unzip into appropriate directories, use the syntax:


Setting up and running ECOMM:

ECOMM is composed of two parts: TSRCOMM (a terminate-stay-resident
program that communicates in the background); and ECOMM (a mailbox
manager that lets you read and send messages).

In order to successfully load and run ECOMM you need to:

1. Make a routing table for your communications network.

2. Set your personal configuration to tell TSRCOMM what directories
and hardware to use.

3. Load the communications software by going to DOS and typing

4. Re-enter the mailbox manager and send a message.

To unload TSRCOMM from memory, simply type "TSR REMOVE" at the DOS prompt.

A candid note from the president of HXJ, Inc.

A lot of improvements have been made to ECOMM in order to make this
shareware offering possible. A number of further improvements are in the
works and include:

a full duplex communications protocol - This will improve the
communications throughput of ECOMM.

support of 16550 UARTS and intelligent serial port controller cards -
By using on board/chip processing power instead of your computer's

already overloaded CPU even higher communications speeds are possible.

porting ECOMM to a number of other platforms and operating environments
- Including Windows 3.0, X-Windows, Sun Sparcstations, and Unix.

implementing an X.400 gateway - for interoperability with other e-mail

producing some very interesting hooks into ECOMM - For example, a
remote control hook will be designed such that when a RemoteLogon
S-record arrives with the correct password, the sending and receiving
machines turn into a Carbon Copy-like session.

better LAN support - By implementing versions of ECOMM/LANmail
specifically designed for particular LAN vendors (instead of the
NetBios version currently available), network workstations will realize
a memory and performance improvement.

better facilities for editing and sharing sections of routing tables.

Some of these enhancements will be available in the shareware version and
some will not. The extent that the shareware version will improve will
depend completely on the extent to which this shareware offering is

On a different note, as you may already know, with this version of ECOMM,
almost every word, phrase, window, color, etc. can be externally defined
using the S-record compiler. This has obvious implications for creating
versions of ECOMM in other languages.

However, the standard version of ECOMM that we distribute does not
include complete source code for the user interface. The reason for this
is simply one of technical support rather than of the proprietary nature
of the S-record source code. The simple fact is that S-records are very
dangerous and can easily lock up your machine or worse. If we let
everyone change the most minute details of the ECOMM S-records, our
technical support costs would become astronomical. We make the S-record
source code available on three conditions:

1. You must ask for it.

2. Once you have it, you waive your right to technical support
(although we will still help you in all likelihood.)

3. The copyright to your modified .SRC files belongs to HXJ.

Note that this only applies to the .SRC files used to create ECOMM.S, not
your own S-records that you use in the CUSTOM.S file.

Suggestions, comments, etc. are welcome but the best vehicle for getting
my attention in particular is to send a message to HXJ via ECOMM.

Hugh R. Kern

 December 8, 2017  Add comments

Leave a Reply