----------------------------------------------------------------------
Help file for ECOMM.EXE
Chapters:
  1 -- Top menu
  2 -- Configuration
  3 -- Mailboxes
  4 -- Sending messages
  5 -- Personal configuration editor
  6 -- Port configuration
  7 -- Timeouts
  8 -- Port configuration editor
  9 -- Timeout sets
 10 -- Broadcast subscription lists
 11 -- Routing file editor
 12 -- Routing file description
 13 -- Site characterization
 14 -- WW resending
 15 -- Redirection
 16 -- aliases
 17 -- mailbox window
 18 -- sending text message
 19 -- sending files
 20 -- sending menu
 21 -- transmitting
 22 -- ASCII
 24 -- text editing window
 25 -- scrolling list editing window
 26 -- general field movement
%%
1,0:90         Welcome!
1,1:5          File
1,2:1          Config
1,3:2          Mailbox
1,4:3          Send
2,1:11           Routing
2,2:40           Personal configuration
3,0:2          Mailbox
4,1:70           Text
4,2:71           File
4,3:72           S-records
5,0:40         Personal Configuration Editor
5,1:41           mailbox path
5,2:42           In-box path
5,3:43           Out-box
5,4:48           network path
5,5:48           network Out-box
5,7:47           flag -- NET
5,8:47           flag -- BEEP
5,9:47           flag -- FATALERR
5,10:47          flag -- RTS/CTS
5,11:49          timeouts
5,12:34          redirection
5,13:37          WW resending
5,14:36          aliases
5,15:44          modem initialization string
5,16:45          modem dialing prefix
5,17:33          WW priority codes
6,0:46         Port config editor
7,0:49         Timeouts
8,0:46         Port config editor
8,1:50           ID
8,2:53           miscellaneous glinlen
8,3:53           miscellaneous gloutlen
8,4:51           hardware
8,5:49           timeout set
8,6:59           message life
8,7:54           baud
8,8:54           baud
8,9:54           baud
8,10:54          baud
8,11:54          baud
8,12:54          baud
8,13:54          baud
8,14:54          baud
8,15:55          bridge gap
8,16:55          bridge gap
8,17:55          bridge gap
8,18:55          bridge gap
8,19:55          bridge gap
8,20:55          bridge gap
8,21:55          bridge gap
8,22:55          bridge gap
8,23:55          bridge gap
8,24:55          bridge gap
8,27:10          bridge gap
9,0:49         timeouts
9,2:60           set #1
9,3:60           set #1
9,4:60           set #1
9,5:61           set #2
9,6:61           set #2
9,7:61           set #2
9,8:61           set #2
9,9:62           set #3
9,10:63          set #4
9,11:63          set #4
9,12:63          set #4
9,13:62          set #3
9,14:62          set #3
10,0:56        broadcast subscription list
11,0:11        routing file editor
12,0:12          routing table
13,0:20          site characterization
13,1:21            personal description
13,2:24            phone #
13,3:22            ID
13,4:22            ID
13,5:25            comm params
13,6:25            comm params
13,7:25            comm params
13,8:30            protocols
13,10:26           channel type
13,11:28           relay
13,12:28           relay
14,0:37        ww resending rules
15,0:34        redirection rules
16,0:36        alias list
17,0:64        mailbox window
18,0:70        text message
19,0:71        files message
20,2:73        File read/write
20,3:75        Transmit normal/urgent/flash
20,4:3         Reply
21,0:75        transmit Normal/Urgent/Flash
22,0:73        file Read/Write
23,0:5         OS Shell/Quit
24,0:15        Text editing keys
25,0:6         Scrolling list editing keys
26,0:7         General movement
27,0:90        Help, intro
%%
.1
Configuring ECOMM
Under normal operation, ECOMM makes use of a @11[routing table] which
contains a list of all of the valid sites with which you can communicate.

The identity and characteristics of any given site are maintained in that
site's @40[personal configuration].

There are a variety of keystroke conventions which are used to interact
with ECOMM including:

    @7[Standard keystrokes   ]
    @6[Editing lists         ]
    @8[General field movement]

In addition, ECOMM fully supports @9[mouse usage] with Microsoft (R)
compatible mouse drivers.

ECOMM's behavior can be configured by @4[command-line options] typed on the
DOS command line or included in an "ECOMM.CFG" configuration file.


@0[<< OK >>]                                    Hugh R. Kern  --
.2
The Mailbox
There are two mailboxes: an In-box containing incoming messages from other
sites, and an Out-box containing submitted messages that are waiting to be
sent.

When reading In messages, you have the option of reading just new messages
or all messages in the mailbox.

When leaving the mailbox, if the <Cancel> button is not used, all changes
made to mailbox messages will be made permanent (e.g. the read/ unread
status will be updated and deletions become effective).

You can read messages in your mailbox with the 10[mailbox editing keys].

In addition, all messages appear in a terse @64[mailbox format] that
indicates the message content.

See @81[command-line option -I] for way to tell ECOMM to use personal
directory and alias list on a LAN.


@0[<< OK >>]                         @-1[Previous]
.3
Sending Messages
ECOMM allows you to send three classes of message:

  @70[Text] -- A text message consists of a subject line and a main message
      body.  Text messages can be read from and saved to external ASCII
      files and can have an optional file attached.

  @71[File] -- You can also send simple files without any text message.

  @72[S-records] -- The most innovative feature of ECOMM is its ability to
      send and receive custom designed forms.  The information in these
      forms is referred to as an "S-record".  The forms can be designed
      using the .SRC language (described in a file called SRECORDS.TXT)
      and the compiling the .SRC file using the @81[-E command-line option].

Once the information for the message is entered, the message can be
@75[transmitted] to any recipient in the @12[routing file].

Sending messages makes use of most of the @7[keyboard conventions] used in
ECOMM.  See @81[command-line option -F] for auto file sending.

@0[<< OK >>]                         @-1[Previous]
.4
Command-Line Options
Command-line options can be typed at the DOS command-line or in a DOS batch
file, or they can be listed in an ECOMM.CFG file for automatic inclusion
each time ECOMM is run.

The ECOMM.CFG file can exist either in your current directory or in the
directory that contains ECOMM.EXE.

Command-line options consist of a '-' character followed by some
characteristic letters (e.g. 'C') and the value with which to set the
parameter.

The @80[command-line] parameters can be anything from characters to numbers
to a string of text characters and are used to specify special graphics
modes, password protection, alternate TCOMMCFG.BIN and ROUTING.BIN files,
auxiliary routing files and more.





@0[<< OK >>]                         @-1[Previous]
.5
File - OS Shell, Quit
You can exit ECOMM in one of two ways: temporarily or more permanently.

If you need to "step out for a moment" to DOS.  Just use the OS Shell
option and when you get done, type EXIT to return to ECOMM.

When you are finished using ECOMM and want to shut it all down, you can do
so by either going to the File menu and selecting Quit, or you can press
Alt-X at most places in ECOMM and go directly out of ECOMM, without passing
GO nor collecting $200.











@0[<< OK >>]                         @-1[Previous]
.6
List Editing
When you are presented with a list of selections, move your cursor to the
selection you desire and press [Enter].  Quicker moving is possible by
typing the first letter of the desired selection and you are sometimes
allowed to delete the entry with the [Del] key.

In some instances, you will be allowed to edit entries in a fixed length
list.  Use @7[standard keyboard] for moving and selecting items to be edited:

     1.  [Enter] opens up an editing window.
     2.  [Up] and [Down] arrow keys move your cursor through the list.

In other instances, you will be allowed to add and delete elements from a
variable length list.  This instance adds the following editing commands:

     1.  [Del] deletes the current entry from the list.
     2.  [Ins] adds a blank entry to the list.

ECOMM also supports a @9[mouse], and @8[standard field movement].


@0[<< OK >>]                         @-1[Previous]
.7
The ECOMM Keyboard
There are a number of keyboard conventions which are gaining wide usage in
the PC community, and which ECOMM fully supports.  These are summarized as
follows:

  [Esc] -- Leave the current window/mode and return to the previous.
      Usually ECOMM will save any current changes when [Esc] is pressed.
  [Enter] -- Select the current item for editing/processing.
  [Del] -- Deletes the character directly under the cursor.
  [Backspace] -- Deletes the character to the left of the cursor.
  [Ins] -- Toggles the insert mode to/from Overwrite mode.
  [Alt-X] -- Leave the entire program.
  [F1] -- HELP!
  [F10] -- Go to the menu at the top of the screen.

ECOMM also supports a number of standard @8[field movement] conventions,
@9[mouse], and special @6[list editing] features.




@0[<< OK >>]                         @-1[Previous]
.8
Field Movement Keys
  [Up / Down] -- Go to previous / next field on screen.
  [PgUp / PgDn] -- Go up or down through a list or some text, one
      screenful or window at a time
  [Ctrl-PgUp / Ctrl-PgDn] -- Jump up or down out of a sub-window on the
      screen to the previous or next field or window controlled by the parent.
  [Tab / Shft-Tab] -- Go to a field on the right or left.
  [Left / Right] -- In text fields move left or right one character. In
      menu options move right or left one field.
  [Home / End] -- In text fields move to the beginning or end of the
      field.  In menu options move to first or last field on the screen.

ECOMM uses a @7[standard keyboard], @9[mouse], and a set of special @6[list
editing] keys.







@0[<< OK >>]                         @-1[Previous]
.9
Mouse Usage
The mouse is used in a point-and-shoot manner to select fields for editing
or modification.  The left button is used to select and is usually
synonomouse with pressing the [Enter] key.   The right button is used in an
auxiliary role and sometimes marks an item for deletion or expands that
item into its set of elements (e.g. a directory).

Your mouse must have a Microsoft (R) compatible driver and that driver must
be loaded for mouse support to work.  Consult the manual that comes with
the mouse for details.

ECOMM also uses a @7[standard keyboard], @8[field movement], and a set of
special @6[list editing] keys.








@0[<< OK >>]                         @-1[Previous]
.10
Mailbox Keyboard
When you review an In or Out box you can use any of the following keys:

  [Enter] / Left click -- Read this message.
  [Del] / Right click -- Mark / unmark this message for deletion.
  [Shft-Del] -- Mark / unmark all messages for deletion.
  [Grey+] -- Expand a compressed message.
  [Grey-] -- Compress an expanded message.
  [F2] -- Forward this message to someone else.
  [F4] -- (Unsent mailbox only) Try sending the message again.
  [F9] -- Check error status on outgoing file.

Use these keys in addition to the @7[standard ECOMM keyboard],
@6[list editing keys], @8[field movement keys], and @9[mouse].







@0[<< OK >>]                         @-1[Previous]
.11
Routing File Editor
The description field is used to distinguish different routing files and
should be set to a short, meaningful summary of the @13[communication network]
described by this routing table.

The window with site summaries is the actual @12[routing table].

After @6[editing] the routing table, you will be asked if you wish to save
your changes.  If you answer "Yes", not only will your routing table be
saved, but your personal configuration file will also be automatically
updated to reflect any changes to your own sites.

The routing file is stored in a file called ROUTING.BIN which is contained
in the main mailbox directory.







@0[<< OK >>]                         @-1[Previous]
.12
Routing Table
A routing table is a phonebook of all the sites with which your computer
can communicate.

Each site has a @21[personal description], a @22[unique id] number (composed
of a group id and a personal id), @25[communications parameters], and
several miscellaneous parameters which can be custom modified to fit that site.

The routing file is physically stored in a file called ROUTING.BIN which
can be found in your main mailbox directory.

Editing is done using @6[list editing keys].









@0[<< OK >>]                         @-1[Previous]
.13
Communication Network
A communication network is the set of people who can communicate with each
other.

For simple networks, everyone in the network can have the same routing
table.  However, when more complicated features of TSRCOMM (such as
forwarding through intermediate sites) are used, some of the sites MUST be
individually customized.













@0[<< OK >>]                         @-1[Previous]
.14
Hexadecimal Numbering
Base 16 numbering is common in computer applications due to the byte
oriented nature of computers, and is discussed at great length in most
introductory computer science text books.

A summary is that whereas decimal (base 10) numbers are composed of 10
digits (0-9), a hexadecimal number is composed of 16 digits (0-9 and A-F).
Use the following table for a quick reference:

  Decimal (base 10)     -- 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
  Hexadecimal (base 16) -- 0 1 2 3 4 5 6 7 8 9  A  B  C  D  E  F 10










@0[<< OK >>]                         @-1[Previous]
.15
Text Editing
The following keystrokes are used to edit most text boxes:

  [Ctrl-PgUp / Ctrl-PgDn] -- go up / down out of this edit box
  [Ctrl-Home / Ctrl-End] -- go to beginning / end of text
  [Ctrl-Left / Ctrl-Right] -- go left or right by one word
  [Ctrl-Y] -- delete current line
  [Home / End] -- go to beginning / end of current line

  [Alt-S] -- search for text
  [Alt-R] -- search-and-replace text

  [Alt-M] or [F7] -- mark / stop marking a block
  [Grey+] -- non-destructive copy of block into paste buffer
  [Grey-] -- destructive copy of block into paste buffer
  [PrtSc] -- copy paste buffer to current location

When moving or editing fields outside of the editing box use the @7[ECOMM keyboard],
@6[list editing keys], @8[field movement], @9[mouse], and @10[mailbox keys].


@0[<< OK >>]                         @-1[Previous]
.20
Site Characterization
A site has the following parameters:

     1.  @21[Personal description]

     2.  @22[Unique ID]

     3.  @24[Phone number]

     4.  @25[Communications parameters]

     5.  @28[Forwarding c/o ID]









@0[<< OK >>]                         @-1[Previous]
.21
Personal Description
This description is different than the overall routing file @11[description]
in that this sentence / phrase is your only way to identify this @20[site]
from a mailing menu.

Be concise when setting the field.  In the mailbox, a message subject will be
followed by the first letters of the sending site's description. Therefore,
if you have two sites named with the same first letters (e.g. "Union
Township, Fire Dept." and "Union Township, Police Dept.") and only the first
14 letters show up next to a message subject, they will both look the same
(e.g. "Union Township").

A solution to the problem in this example is to name the two sites "UnTwp
Fire" and "UnTwp Police", thus ensuring that a relevant name will be
associated with any messages to or from these sites.

                                                      




@0[<< OK >>]                         @-1[Previous]
.22
Identification Numbers
Every site in a communications network MUST have a unique identification
number (a lot like a social security number).

This number is a @14[hexadecimal] (base 16) integer, and has two parts, a
group ID and a personal ID.

@23[Group IDs] are very meaningful and are used to tell ECOMM about
incompatible groups of computers that must be segregated.  Computers with
different group IDs can only talk to each other through a common gateway,
or, if they have compatible hardware and communications parameters, by
setting the appropriate group IDs in the @55["compatible groups"] boxes.

Use one group ID for modems, another for packet radios, another for RS-232
connections, etc.

The personal ID is a unique number within a group and is not allowed to be 0.




@0[<< OK >>]                         @-1[Previous]
.23
Group ID
Group IDs have the special significance of indicating a certain type of
channel in a communication network.  For example, group 0100 might refer to
all of the Hayes modems on the network, and group 0101 might be used to
identify a special satellite system.

The reason for making these distinctions is to prevent a computer from
unsuccessfully trying to contact a packet radio from a modem.  Another
bonus of this system is that 2 or more modems can be attached to a single
computer and if one is busy, another could be used for an outgoing call.
Of course, the free one could also be available for an incoming call.

Another example of the usage of group IDs is to imagine a computer
connected to two other computers (A&B) via a direct link with identical
communications parameters.  In order for the middle computer to be able to
distinguish between the two ports and not attempt sending a message to A
over B's line, each of the two lines must be associated with its own unique
group ID.  A similar case can be made for a distinction between similar but
distinct modems (e.g. cellular v. non-cellular).

You can @55[bridge the gap] between similar hardware and dissimilar group IDs.
@0[<< OK >>]                         @-1[Previous]
.24
Telephone Numbers
The telephone number is used in situations where a @20[site] has some
real-world identification number or string.  For modem applications, this
means a normal telephone number.

However, when direct communications are used (e.g. over a serial line with
a NULL modem, or with some X.25 networks with permanent virtual circuits
(PVCs) already established), this field is not used.

Packet radio applications should use this field to store the site's packet
radio call sign.










@0[<< OK >>]                         @-1[Previous]
.25
Communications Parameters
The baud rate can be thought of as the rate in bits per second at which your
equipment can communicate, although this is not technically accurate.

Every byte which is sent is "packetized" by a 1 bit start-bit and 1 or more
stop-bits which allow the the asynchronous adapters to stay in sync.
Choosing the wrong stopbit setting will cause a "failure to communicate".

Parity serves as a simple error detection method.  Parity is the same as
adding another bit to the byte packet which identifies whether there is an
even or odd number of bits ON in the byte.  Usually, we leave error
detection to communications protocols, using no parity.

Communication @30[protocols] supported by TSRCOMM are: Hmodem, Xmodem,
Xmodem-1K, and Weather-wire.

Channel @26[types] supported by TSRCOMM are: modems, direct serial, and
packet radio.



@0[<< OK >>]                         @-1[Previous]
.26
Channel Types
The channel type refers to the media used to communicate.  Three types are
supported:  modem, direct serial RS-232, and packet-radio.

"Modem" supports Hayes modems, and uses the Hayes AT-command set to
establish communications parameters and to dial the phone using the
@24[phone number] field of the site characterization.

"Direct" serial supports RS-232 connections and a wide variety of media
that "look" like serial connections (e.g. data-ready radios, and PVCed
satellite links).

"Packet" supports a limited number of TNCs that use the TAPR command set.
See your TSRCOMM documentation for a list of currently supported brands of
packet radio controllers.






@0[<< OK >>]                         @-1[Previous]
.28
Forwarding c/o: (Relays)
This relay mechanism is a means of sending messages from incompatible sites to
each other through an intermediary gateway.  This is one of the instances in
which each site might have a customized routing table.

A forwarding ID is an ID number to which a message should be sent instead of
to the current site, and, like a @22[site ID], is composed of two @14[hexadecimal]
identification numbers, the @23[group ID] and the personal ID of the relay site.

In ECOMM releases 1.10 and above, the relay ID supports a special case of FFFF
in the group or personal part of the ID.  If either of these numbers is set to
FFFF, that number will be set to the same number as the ID of this site.
Hence, by using this feature on simple relays, you can have the site and its
relay in the same routing table entry instead of requiring two separate
entries.

In ECOMM releases 1.10 and above, you can also establish store-and-forward
sites by setting the relay to the same ID as the site itself.  When this is
done, no messages will ever be sent to that site until the site sends a
message in to the central repository.
@29[Example ...]                     
@0[<< OK >>]                         @-1[Previous]
.29
Forwarding c/o -- Example
If site A is a modem with ID 0010 0001, site B has a modem with ID 0010 0002
and a satellite port with ID 0011 0002, and site C has a satellite port with
ID 0011 0003, the following routing table modifications should be made:

Site A:  Put site B's ID 0010 0002 in the Forward c/o field of site C's entry.
Site B:  Requires no modification.
Site C:  Put site B's ID 0011 0002 in the Forward field of site A's entry.

This way, when site A is told to send a message to site C, it looks up site
C in its routing table, but finds a relay ID of site B.  The message gets
sent to B where it is found that B is not the final destination of the
message and the message gets forwarded on to site C.








@0[<< OK >>]                         @-1[Previous]
.30
Communications Protocols
With ECOMM versions 1.10 and above, we have added a new protocol called
Hmodem.  Hmodem is the same as Xmodem-1K with three exceptions.  Hmodem
is a variable length packet protocol so no extra bytes are sent.  Hmodem
is a "streaming" protocol so multiple messages are sent in the same phone
call.  And finally, Hmodem supports return streaming so that all messages
that are queued up at both ends are sent back and forth until there are
no more at either end.

Hmodem is the best protocol to use for most applications.

Of the protocols supported by TSRCOMM, @31[Xmodem] is the most reliable
and well used.  @31[Xmodem-1K] has a larger packet size and works faster
for most applications, especially when large delays are present (e.g. on
satellite based systems).

The @33[Weather-Wire] protocol is only needed for listening to National
Weather Service forecast services.                       



@0[<< OK >>]                         @-1[Previous]
.31
XMODEM communications protocols
Xmodem-CRC

Xmodem is a widely used protocol which was developed by Ward Christiansen.
It is a packetizing protocol which uses 128-byte packets with some header
and footer bytes.  This protocol only requires half-duplex channels.

The original Xmodem employed checksum error checking.  However, a more
reliable CRC based flavor has been developed and is the only flavor
supported by TSRCOMM.


Xmodem-1K

Xmodem-1K (sometimes mistakenly referred to as Ymodem) is a protocol
with all the same characteristics as Xmodem except for its 1024 byte
packet sizes.




@0[<< OK >>]                         @-1[Previous]
.33
Weather-Wire
The National Weather Service (NWS) weather-wire has a simple stream format
consisting of a "ZCZC" string followed by an ASCII message and terminated
by a "NNNN" string.

These messages can be picked up by TSRCOMM on a Weather-Wire protocol port.

In the event of NOAA Weather-Wire reception, the incoming messages are
assigned priorities according to the middle 3 characters of the
"product-ID".  You are allowed to establish the set of high priority
products using a string of 3-letter codes separated by commas in the
personal configuration screen.

Example:  "TOR,FLW,FLS" tells TSRCOMM to assign high priorities to any
incoming messages pertaining to tornados, flood warnings, and flood
statements.





@0[<< OK >>]                         @-1[Previous]
.34
Redirection
TSRCOMM's flexible architecture allows the communication network to be
configured for a variety of purposes, including monitoring usage, and
optimizing the cost of mass distribution of messages such as Weather-Wire
messages.

The "Redirection" editor lets you set up of rules for duplicating and
relaying on messages based on the addressing information in the message.

Redirection is done by the NET.EXE program, not by TSRCOMM, and allows the
communication load to be distributed evenly throughout the communications
network.

The redirector examines the final destination and the broadcast IDs of all
incoming messages and forwards the message if:

      the destination of the message bitwise AND'd with the destination
      mask equals the given destination ID...

  AND the broadcast ID of the message bitwise AND'ed with the
      broadcast mask equals the given broadcast ID.           @35[more...]
@0[<< OK >>]                         @-1[Previous]
.35
Redirection -- (continued)
The forwarding addresses consist of a destination and a broadcast code.
These numbers are placed in the addressing information of the message with
the following single exception.

If the upper or lower half of the broadcast code is 0xffff, the original
number will not be replaced.  The advantage to this exception is that (for
mass distribution of broadcast messages) half of the broadcast code can be
used to route the message to the correct final locations while the other
half can be used to carry a code indicating the content of the message
without being modified.

The fact that redirection is based on final destinations, in addition to
broadcast codes, means that the final destination can be used to broadcast
messages when used in conjunction with relays and a redirection service.






@0[<< OK >>]                         @-1[Previous]
.36
Aliases
ECOMM not only performs background communications tasks on individual PCs.
It also performs most electronic mail (E-mail) services required on a local
area network (LAN).

In order to establish the set of users on a given LAN using a single
comm-server, an alias list can be built.  Use the @6[list editing] keys to
add and delete names from the list and simply select new users from your
routing table.

Note:  Passwords are kept in this list although no one but the original
user is allowed to modify their password.  However, by deleting and
re-adding a name to the list, the password will be reset to nothing.








@0[<< OK >>]                         @-1[Previous]
.37
Weather-Wire resending
When a Weather-Wire message is received, the NET.EXE program can be used to
determine the relevance of the message based on the product ID, and to
subsequently distribute the message to other sites in the communications
network.

The "WW Resending" editor allows the user to establish a set of rules for
distributing Weather-Wire products based on the product ID of the message.
The priority of the distributed message can be customized or kept at the
default established by the @33[high priority string] when the message was
originally received.

The rules simply contain a list of product codes to watch for, and a set of
forwarding sites for the resulting messages.  When the message is
originated, you can set a broadcast ID for the message which is used in
general distribution.

Product code names can include the wildcard characters '*' and '?' similar
to the use of wildcards in most operating systems.


@0[<< OK >>]                         @-1[Previous]
.40
Personal Configuration Editor
This screen allows you to edit all site specific information including:

     1.  @41[Mailbox paths]
     2.  @44[Modem initialization strings]
     3.  @51[Serial port configuration]
     4.  @47[Flags]
     5.  @49[Timeout sets]
     6.  @37[Weather-Wire resending rules]
     7.  @34[Redirection rules]

This information is physically stored in a file called TCOMMCFG.BIN, which
is kept in your main mailbox directory.








@0[<< OK >>]                         @-1[Previous]
.41
Mailbox Paths
The mailbox main, in, and out paths are the directories in which the main
TSRCOMM information and programs, the incoming messages, and the outgoing
messages are stored, respectively. These paths are user-selectable and can
all be the same but it makes the most sense for most applications to have a
main "MBOX" directory with a subdirectory called "IN" for incoming messages
and another subdirectory called "OUT" for outgoing messages.

The main "MBOX" directory is where the TCOMMCFG.BIN and ROUTING.BIN files
must be kept and is also where all of your TSRCOMM executable program
(files with ".EXE" and ".BAT" extensions) should be kept.

The @42[In-box], or "IN" directory is where all incoming messages are
placed after they have been received.

The @43[Out-box], or "OUT" directory is where all messages which are to be
sent are kept until they are received at the destination or intermediate
destination (@28[relay]) site.

@48[LAN] directory configurations are slightly different.

@0[<< OK >>]                         @-1[Previous]
.42
The In-box
When a file is received, a random name is generated and the file
information is placed in the In-box or "IN" directory as it is received.

When the transmission is complete without errors, the filename is given an
extension of the ".I??" format (usually ".IN"), and the file is made
available for reading / processing.














@0[<< OK >>]                         @-1[Previous]
.43
The Out-box
The TSRCOMM background communications program accepts requests to send
files provided those files are first placed in the Out-box or "OUT"
directory and follow certain file format guidelines.

Once the outgoing file has been successfully received at the other end, the
file in the Out-box is deleted by TSRCOMM.

By perusing this directory, you will be able to tell which files have not
been sent and when they were last attempted.

In general, files that are to be sent should have the extension ".O??" in
order to be compatible with most mailbox managers, although TSRCOMM
requires no extension nor file naming conventions.







@0[<< OK >>]                         @-1[Previous]
.44
The Modem Initialization String
In order to set a modem's configuration upon port initialization /
re-initialization, a number of Hayes AT commands are sent to the modem
including "ATZ" and this user definable string.

The meaning and syntax of these commands and the @45[dialing prefixes] are
found in your modem manual. Some Hayes-compatible modems do not support all
of the default commands.  For these modems, experiment with the default
string to find out which commands do not work and delete them.

If your modem continues to fail to initialize, and you are sure it is
getting accessed correctly (e.g. the lights blink on and off), use the
@47[fatalerr] flag to tell TSRCOMM to ignore modem initialization errors.
Also, remember that the original Hayes 1200B modems were set with jumpers
and switches inside the modem, not with a modem initialization string.

TSRCOMM is not guaranteed to work with modems which fail the default
initialization string.



@0[<< OK >>]                         @-1[Previous]
.45
The Dialing Prefix
Hayes modems require a certain documented command in order to dial the
phone.  In general, this command is "ATDT", which means dial the phone
using touch-tones.

However, some phone systems do not support touch-tone signals and require
pulse dialing, in which case you should substitute "ATDP" for the dialing
prefix.

Another trick which can be used on some PBX systems, is that if a number
code must be dialed in order to get an outgoing line, (e.g. "9"), you can
make your dialing prefix "ATDT9,".

See your modem manual for more information on dialing commands.







@0[<< OK >>]                         @-1[Previous]
.46
Editing Port Configurations
Up to 16 ports can be used at once by TSRCOMM, assuming your machine is
fast enough to keep up with the processing required.

Each port configuration must have:

     1.  A physical serial (RS-232) port
     2.  An ID number in the routing table
     3.  A set of timeout parameters
     4.  Miscellaneous other parameters

In some cases (e.g. broadcast satellite situations), a broadcast subscription
list can be associated with the port.

In other cases (e.g. modems with multiple baud rate capabilities), the
capabilities and limitations of the modem can be recorded for multi-baud
rate communications.

Finally, since group IDs usually determine the channel used by the port,
a number of compatible group IDs can also be associated with the port.

@0[<< OK >>]                         @-1[Previous]
.47
Miscellaneous Flags
There are a number of flags that can be set to customize a site's behavior:

     1.  @48[Network] -- this flag tells mailbox managers and TSRCOMM that
     this site is a communications server for a local area network (LAN).
     Sites with comm-servers generally need different path configurations
     than non-network sites.

     2.  Beep -- tells TSRCOMM whether to beep when incoming messages arrive.

     3.  Fatalerr -- tells TSRCOMM whether to relax its standards on port
     reinitializations.  If Fatalerr is "Yes", any errors initializing
     ports will cause TSRCOMM to fail loading itself.  If Fatalerr is "No",
     TSRCOMM will continue to load itself in memory even if the port fails
     to initialize properly.

     4.  RTS/CTS -- tells TSRCOMM whether to use hardware flow control.




@0[<< OK >>]                         @-1[Previous]
.48
Local Area Network (LAN) Configuration
The LAN mailbox is where workstation accessible versions of TCOMMCFG.BIN
and ROUTING.BIN are kept.  Using these files, LAN work-stations determine
their identity, and identify message recipients.

The LAN In-box is where incoming messages are placed by NET once they have
been received.

On a network communications server, TSRCOMM works in tandem with another
program called NET.EXE, which handles requests from the LAN, puts incoming
files in the appropriate mailboxes, and in some cases filters, duplicates
and @35[redirects messages] and duplicating / re-routing incoming
@37[Weather-Wire] messages.

Since it is desirable to have as many TSRCOMM disk activities occur on a
local drive as possible in order to reduce network load, the @42[In-box]
should be a local directory, as should the @41[main mailbox] directory.

@58[Example ...]
   

@0[<< OK >>]                         @-1[Previous]
.49
Timeouts
Each port uses a set of timeout values to customize its behavior while
communicating.

Up to eight sets of timeouts can be set and customized to fit your
individual circumstances and channel characteristics.

Each @52[timeout set] also includes a description string which can be used
to document the situation characterized by this set of timeouts.

Some values which are zero are set at run-time depending on the packet
size, communication rate, channel delays, etc.









@0[<< OK >>]                         @-1[Previous]
.50
ID -- (Index into the Routing Table)
Each port must be associated with an entry in the @12[routing table]. This
determines the port's default communication parameters (e.g. baud rate,
parity, stopbits, protocols, comm channels etc.)

This is the port's only way of establishing its own identity, and it is
therefore essential that this entry be correct.














@0[<< OK >>]                         @-1[Previous]
.51
Hardware
Since up to 16 serial ports are supported by TSRCOMM, but only 2 ports were
originally supported by IBM asynchronous adapters, a number of alternatives
have been developed by independent hardware vendors, of which DigiBoard is
one.  DigiBoard produces 4 and 8 port boards for PC and PS/2 model computers.

Note: Only UN-intelligent DigiBoards are supported by TSRCOMM, and must be
configured using the default parameters on IRQ #3.

In general, if you are using a normal COM1 or COM2 port, select "IBM_COM1"
or "IBM_COM2", respectively.

For DigiBoard use, select the appropriate entry (DGPS means a PS/2 model,
whereas DGPC means a PC or compatible model).

Note: Due to quirks with the PS/2 DigiBoards, on these systems be sure to
initialize the ports sequentially or your machine will "hang".

In the future, TSRCOMM will support more brands of multi-port boards.


@0[<< OK >>]                         @-1[Previous]
.52
Timeout Sets
Due to the imperfect world we live in, there is always a chance that any
aspect of a communications session will fail.  Not only could the call not
go through because of a BUSY signal, but once it goes through, the line may
be hit by bursts of noise, or even the destination computer could be turned
off in mid-transmission.

A timeout set is a group of parameters (usually measured in seconds) after
which at any time in a communication session, TSRCOMM should give up and
try again if this time or event is achieved without the desired condition
or response.

Naturally, this covers a wide variety of possible events and situations, so
the timeout set is fairly large.







@0[<< OK >>]                         @-1[Previous]
.53
Miscellaneous Port Configuration Settings
The input buffer length is the amount of memory which is allocated for
receiving incoming information.  The only restriction on this number is
that it be large enough that anything that comes in will not arrive so fast
that the buffer overflows before the processor gets around to processing
the new information.

The output buffer length is the amount of memory which is allocated for
outgoing information.  This buffer must be larger than the largest packet
which goes out.  Hence, if you are using the @32[Xmodem-1K] protocol this
buffer size must be greater than 1K.

In addition to buffer lengths, you are allowed to notify TSRCOMM of:

     1.  @54[Compatible baud rates] of your communications equipment

     2.  @55[Compatible group IDs]

     3.  @56[Broadcast subscription] lists


@0[<< OK >>]                         @-1[Previous]
.54
Compatible Baud Rates
If you have a 2400 baud modem which is also capable of communicating at
1200 and 300 baud, you can inform TSRCOMM of that fact by adding 1200 and
300 in the capabilities box.  By doing this, it won't be flagged as an
error when you try transmitting to a 300 baud site.
















@0[<< OK >>]                         @-1[Previous]
.55
Compatible Group IDs -- (Bridge the Gap)
TSRCOMM segregates communications channels by group number.  If you try to
send something to a site in group 10, the transmission will not normally be
attempted over a port with group ID 11.  This way, not only is the
communications world made less complicated, but, by registering unique
group sets on different communications networks, there is less chance of
having conflicting ID's in the world on the whole.

However, eventually one network with modems occupying group ID 10 is going
to need to bridge the gap to another network with modems occupying group ID 20.

This can be accomplished by putting 20 in the compatibility box of the group
10 sites and by putting 10 in the compatibility box of the group 20 sites.

Each group can have up to 64K sites in it.






@0[<< OK >>]                         @-1[Previous]
.56
Broadcast Subscription Lists
In the special situations in which broadcast communication is possible,
it may be desired to send a message for general reception. In this case,
the message gets associated with a broadcast number which has a group and
personal ID (the group ID must be the group ID of the channel which
supports broadcasting but the personal ID has no relationship to actual
site personal ID's in the communications network).

When all of the sites "hear" the message, they check their broadcast
subscription lists.  If they find the broadcast code in their own broadcast
subscription list, they listen to and receive the message passively,
otherwise they ignore it.

You can build a list of broadcast subscriptions by adding new entries and
editing them or by deleting unwanted existing subscriptions:

@57[Example...]




@0[<< OK >>]                         @-1[Previous]
.57
Broadcast Subscriptions -- Example
Assume the Weather-wire messages for the Eastern United States have broadcast ID 0010 0079 and messages for the Western United States have
broadcast ID 0010 0050.  A city in Maryland would have 0010 0079 in its
broadcast list, whereas a city in California would have a 0010 0050 in its
broadcast list, and a city in Missouri might include both IDs in its broadcast
list.

In order to know what the possible IDs mean, you must consult the originator
of the messages.












@0[<< OK >>]                         @-1[Previous]
.58
Network Paths -- Example
Assuming the shared network drive is M: and the local disk is C:, valid
paths would be:

      Main directory -- "C:\MBOX"
      In-box --         "C:\MBOX\IN"
      Out-box --        "M:\MBOX\OUT"
      Network --        "M:\MBOX"
      Network In-box -- "M:\MBOX\IN"

Since copies of the ROUTING.BIN and TCOMMCFG.BIN files must be maintained
in both the main and the network directories, this administrative task can
be simplified by making the local main directory point to the network at
the expense of increased network load, ie:

      Main directory -- "M:\MBOX"
      In-box --         "C:\MBOX\IN"
      Out-box --        "M:\MBOX\OUT"
      Network --        "M:\MBOX"
      Network In-box -- "M:\MBOX\IN"

@0[<< OK >>]                         @-1[Previous]
.59
Message Life
TSRCOMM tries its hardest to send your message to its destination. However,
sometimes this just can't be done.  The message life parameter is your way
of instructing TSRCOMM how long to try sending your message to its recipient.

TSRCOMM will try to send the message "Life * <message priority>" times
before giving up and marking the message as "dead".

In other words, if you send a normal priority message and the lifetime
parameter on the sending port is 3, TSRCOMM will try sending the message 3
* 2 times.  An urgent message with a lifetime parameter of 4 will be
attempted 4 * 4 times.  A flash RSVP message on a port with a life- time
parameter of 4 will be attempted 4 * 7 times.

If you want your message to be attempted continuously until you personally
cancel it, set the message lifetime on your port to 0.





@0[<< OK >>]                         @-1[Previous]
.60
Timeouts -- Detailed
Receive Weather-Wire -- If a Weather-Wire message gets interrupted in
  mid-transmission, this parameter indicates the maximum number of seconds
  to wait before abandoning this reception.  This parameter only applies to
  ports which are using "Weather-Wire" @33[protocol].

Wait for Connection -- After finding an inactive port, the port is
  re-initialized and a connection request is submitted.  This parameter
  indicates the maximum number of seconds to wait for a response from the
  destination.

Wait for Acknowledgment From Receiver -- When a message is sent, it is
  first separated into "packets".  After the transmission of each packet,
  the receiver sends an acknowledgment (ACK) if the packet was received all
  right and a negative acknowledgment (NAK) if the packet was somehow garbled.

  This parameter indicates the maximum number of seconds for the sender to
  wait for one of these two responses, before resending the packet.



@0[<< OK >>]                         @-1[Previous]
.61
Timeouts -- Detailed
Wait for Transmit Buffer to Empty -- After submitting a packet to be sent,
  if the communications interrupts somehow stop, this is the maximum number
  of seconds to wait for the buffer to empty before re-initializing the
  port and trying later. This parameter will vary with baud rate and the
  protocol packet size.

Maximum Consecutive Failed Blocks -- This parameter indicates the maximum
  number of consecutive failed blocks which are allowed before determining
  that the channel is unsuitable for communicating and should be tried later.

Receive an Entire Correct Block -- This is the maximum number of seconds to
  wait for a good (error free) packet before aborting the connection.

Max Time in the Middle of a Block -- After the first part of a packet is
  received, this parameter indicates the maximum number of seconds to spend
  waiting for the rest of the packet.




@0[<< OK >>]                         @-1[Previous]
.62
Timeouts -- Detailed
Wait for Next Block -- In the middle of a transmission, after acknowledging
  a block, this parameter indicates the maximum number of seconds to wait
  for the next block before resending the acknowledgment.

Maximum Wait -- This parameter tells TSRCOMM how many acknowledgments to
  send for any given packet without receiving the next before giving up.

Sending Delay -- For automatic computation of some parameters the average
  delay between sending a message and having it received at the other end
  is used.

  In long-delay environments (e.g. packet radios and satellites) this
  parameter can be crucial.

  The sending delay is measured in seconds.





@0[<< OK >>]                         @-1[Previous]
.63
Timeouts -- Wait Carrier Detect (CD), Wait for First Block, Max NAKs
On modem connections, after a connection is requested, Wait-Carrier- Detect
tells TSRCOMM how long to wait for a CD before giving up and resetting the port.

After the connection is established, the receiver sends negative
acknowledgments (NAKs) to let the sender know the receiver is there and
ready to receive.

The Wait-First-Block parameter indicates the maximum number of seconds to
wait after the connection is established without receiving the beginning of
the first block before giving up and hanging up the phone.

The Max-NAK parameter indicates the maximum number of NAKs to send in
hopes of receiving a first block.

These last two parameters are closely related and may be combined in a
future release.




@0[<< OK >>]                         @-1[Previous]
.64
Mailbox Message Format
Each message has four fields indicating the contents starting on the left
of each line of the mailbox:

  @65[Status/Type] -- The current status of the message and the message type.

  Time -- The time on Incoming messages represents the time the message was
      originally submitted to be sent.  On outgoing messages, the time
      represents the last time the transmission was attempted.

    Note: On outgoing messages if the time is set to -5:00 and it stays
    that way, the message is not getting attempted due to an error in the
    configuration.  In this event, review your configuration for errors and/
    or use the tracing version of TSRCOMM to detect the source of the error.

  Subject -- A brief description of the message content.

  @66[Origination/Destination] of the message.

Use the @10[mailbox keys] to review the mailbox.

@0[<< OK >>]                         @-1[Previous]
.65
Message Status/Type
There are a number of different message types:

  * -- Normal text message
  w -- Weather-Wire information
  r -- An RSVP from any message
  f -- File
  s -- An S-record message

To the left of the message type indicator is the current status of the message

  R -- This message has been previously read
  D -- This message is marked for deletion, and the deletion will take
       place when the mailbox is exited.  Use the <Cancel> button to
       abandon the most recent mailbox changes.

To the right of the message type, a '.' or ':' indicates that the message is
currently compressed.



@0[<< OK >>]                         @-1[Previous]
.66
Origination / Destination
The field to the right of the subject varies in meaning depending on
whether you are currently in the In-box or the Out-box.

In the Out-box, this site is the site to whom the unsent message was sent.

In the In-box, this site is usually the originator of the message. However,
if the originator is in brackets, the message is simply a message that was
"retained" when sending, and the site represents the site to whom the
message was sent (the message destination).











@0[<< OK >>]                         @-1[Previous]
.70
Text Messages
Text messages are simple ASCII messages composed of three parts:

  Subject -- a concise description of the contents of the message

  Message area -- the main body of the message

  File -- (optional) a file can be attached to any text message

The main body of the message can be read from an external ASCII file using
the File/Read menu option.  Also, the main body of the message can be
saved to an ASCII file using the File/Save option.

After the message has been entered, it can be @75[transmitted].







@0[<< OK >>]                         @-1[Previous]
.71
Sending Files
An alternative to attaching a file to a text message is to send a file with
no corresponding text.

To send a file, select it and @75[transmit].
















@0[<< OK >>]                         @-1[Previous]
.72
S-Records
ECOMM is designed to have other applications built around it.  One of the
most flexible aspects of ECOMM is its S-record capabilities.  An S-record
is a custom designed record whose format is stored in a file called CUSTOM.S.

Provided that both the sending and the receiving ends of the transmission
have the same S-record in their CUSTOM.S file, the message will be the same
at both ends.

S-records allow the following types of applications to be built:

  Distributed database update and query -- ECOMM can be loaded on several
      distributed machines for sending database updates to a central machine.

  Retail order processing -- S-records of custom order forms can be used to
      order new products and in automatic order processing and billing.

Create your own S-records by using the .SRC examples and compiling your own
using the @82[-S command-line] option.  The syntax of the .SRC examples is
discussed at length in a documentation file called SRECORDS.TXT

@0[<< OK >>]                         @-1[Previous]
.73
Reading and Writing Data from External Files
Text messages and S-records can be saved to and read from external DOS files.

There is some bookkeeping required on the part of the user to keep track of
what data was saved in which files.  ECOMM not only distinguishes between
text files and S-records, but between different kinds of S-records (e.g.
"phonemsg" v. "techsupport").

ECOMM will not allow you to read a file that was saved as a "phonemsg" into
a "techsupport" S-record.

Text files are not only interchangeable, but also serve as an excellent
import / export mechanism for ECOMM messages.








@0[<< OK >>]                         @-1[Previous]
.75
Transmitting / Submitting a Message to be Transmitted
When a message is prepared to be sent, pressing [Esc] or [F10] brings up the
Transmit menu option from which the priority of the outgoing message is
selected.

Choosing the destination sites is as simple as putting the cursor over the
desired sites and clicking the mouse or pressing [Enter].  When all of the
sites have been chosen, simply select or click on the <<Send>> or <<RSVP>>
buttons to submit the request.

Choosing <<Send>> simply sends the message to the designated sites.
However, sending the message using the <<RSVP>> method ensures that a short
statistical summary will be generated and returned to the sender as soon as
the receiver has read the message.

Use of <<RSVP>> messages should be limited in busy or congested networks
since they increase the overall network traffic.




@0[<< OK >>]                         @-1[Previous]
.80
Command-Line Options [-B=fastpath] [-C=tcommcfg]
-B=fastpath                             default: current directory
  Specifies the path to a large and fast directory which can be used for
  temporary storage and working.  For instance, if you have a 1 MB virtual
  disk (using the DOS VDISK.SYS driver) on drive F:, use -B=f:\

-C=tcommcfg                             default: -c=TCOMMCFG.BIN
  Tells ECOMM to use a personal configuration file OTHER than TCOMMCFG.BIN.
  Mostly used on networks to look on shared drive.

  Example:  -C=k:\tcommcfg.bin looks for TCOMMCFG.BIN on the K: drive










@0[<< OK >>]                         @81[< PgDn >]                         @-1[Previous]
.81
Command-Line Options [-E=ecommsrc] [-F=file2send] [-I=myID] [-J{country info}]
-E=ecommsrc                             default: none
  Identify name of source file for producing ECOMM user-interface S-records.
  To make a new user interface for a 66-line adapter, copy ECOMM.S to
  ECOMM66.S  Then "ECOMM -Eecommsrc -DRrb+" recompiles ECOMM for 66 lines.

-F=file2send                            default: none
  Specify filename to be sent automatically.  Goes into Send/File and leaves.

-I=personalID                           default: -i=0
  Tells ECOMM what the personal ID of a network user is.  That user must also
  be listed in the alias list and may be assigned a password using "-y1".

  Example:  -I=10020 uses personal mailbox for someone with ID 0001 0020

-JD=dateformat   default: 0      Allowed: 0=MMDDYY, 1=DDMMYY, 2=YYMMDD
-JN=nostr        default: No     Allowed: Any language's word for "No"
-JY=yesstr       default: Yes    Allowed: Any language's word for "Yes"
-JR=radix        default: .      Allowed: Any character used as decimal point
-JS=separator    default: ,      Allowed: Any char that separates thousands

@0[<< OK >>]                         @82[< PgDn >]                         @80[< PgUp >]
.82
Command-Line Options [-Mmouse] [-N=netdat] [-P=myrouting] [-R=routing]
-Mmouse                                 default: -m+
  Lets you tell ECOMM not to enable its mouse support, even if it finds one.

-N=netdat                               default: -n=NETWORK.DAT
  Tells ECOMM to use a network semaphore filename OTHER than NETWORK.DAT

-P=myrouting                            default: none
  Tells ECOMM to use an auxiliary (personal) routing file IN ADDITION to
  the ROUTING.BIN file.  This is used to maintain personal address lists in
  addition to the central ROUTING.BIN file on the network.

  Example:  -P=c:\mbox\myroutin.bin looks for MYROUTIN.BIN on the C: drive

-R=routing                              default: -r=ROUTING.BIN
  Tells ECOMM to use a personal configuration file OTHER than ROUTING.BIN

  Example:  -R=k:\routing.alt looks for ROUTING.ALT on the K: drive



@0[<< OK >>]                         @83[< PgDn >]                         @81[< PgUp >]
.83
Command-Line Options [-S=ecommsrecs] [-V=videomode] [-W?=weatherwiresrec]
-S=ecommsrecs                           default: none
  If you define your own S-record in a .SRC file, you can compile the new
  S-record using the -S option.  Note: You must compile the .SRC file
  separately for all the different video modes you use.

-V=videomode                            default: current mode
  You can specify ECOMM's videomode using this hexadecimal number.  If you
  want ECOMM to autodetect, use a negative decimal number (-1<=VGA, -2<=EGA,
  -3<=CGA, -4<=Compaq, -5<=Hercules).  Autodetection uses maximum #lines/screen.

-W?=weatherwireid                       default: none
  If you receive raw data in Weather-Wire format and want to associate an
  S-record with the data, weatherwireid is the ID number of the port
  receiving the data, and ? is a number (0..3) that helps specify the name
  of the S-record.

  Example:   -W3=01004567 tells ECOMM to use an S-record called "wsfile3" to
             display data received by the port with ID: 0100 4567


@0[<< OK >>]                         @84[< PgDn >]                         @82[< PgUp >]
.84
Command-Line Options [-Ysetpassword] [-Z-autocompression] [-Z+autodecompression]
-Ypasswordflag                          default: -y-
    Tells ECOMM that you want to set a password for this account.  You will
    be prompted for the password from within ECOMM.

    Example:  -Y+ tells ECOMM to set a password on this account.

-Z-autocompression                      default: -z-2
    This flag can be used to disable automatic compression by ECOMM.
    Compressed messages are not supported by the EIS.

    Example:  -Z-- disables auto-compression
              -Z-1 makes compression default to the slower but more
                   effective LZH method

-Z+autodecompression                    default: -z++
    This flag can be used to disable automatic replacement of compressed
    messages with their decompressed counterparts (to save on disk space).

    Example:  -Z+- disable automatic decompression
                                 
@0[<< OK >>]                         @-1[Previous]                         @81[< PgUp >]
.90
              Welcome to the world of background communications!
ECOMM lets you send and receive electronic messages in the background of
your MS-DOS PC without requiring special multitasking environments such
as DesqView or Windows.

You will find that ECOMM/Lite incorporates quite a few unique capabilities to
simplify your life and to let you design programs around its e-mail motif.
Its automatic data compression will reduce your communications costs, and its
S-records let you design custom-format messages to fit your own applications.
ECOMM/Lite was created to provide you with state-of-the-art background
communications and is being distributed as shareware.  The only way we can
continue to develop and enhance ECOMM/Lite is with your support.

This introductory screen will continue to show up until you set up your own
copy of ECOMM with a personal configuration.  For your convenience, we have
included a default simple routing file with two entries for setting up two
computers connected via a serial null-modem.



@91[How to register ECOMM/Lite          ]    @92[Advantages of registering ECOMM/Lite]
@94[Setting up and running ECOMM/Lite   ]    @95[Read about possible applications    ]
.91
How To Register ECOMM/Lite
We depend on your support to continue to enhance and improve ECOMM/Lite.

When you start using ECOMM/Lite on a permanent basis, and you decide to
purchase your own legal, registered copy, just print and fill out the
ORDER.FRM file that is included with ECOMM/Lite.

Then send it with your check for $50 or your Visa/Mastercard number to:

     HXJ, Inc.
     966 Hungerford Drive, Suite 3
     Rockville, Maryland 20850

Or fax the order to us: (301) 738-1026

Or call us to place your order: (301) 424-0070

Once you become a registered user, you get 90 days of free technical support
and free access to the HXJ bulletin board, as well as your own personal ID
number.  We are sorry, but our free technical support service is ONLY
available to registered users.
@0[<< OK >>]                         @-1[Previous]
.92
The Advantages Of Registering Your Copy of ECOMM/Lite
When you register your copy of ECOMM/Lite, you get a license to use your copy
for personal and commercial use.  Without this license, it is illegal for you
to use ECOMM/Lite on anything other than a trial/evaluation basis.

However, you also get numerous tangible benefits when you register:

-- A printed reference manual that is chock full of examples and information on
setting up strange and unusual hardware (e.g. packet radios) for ECOMM/Lite.

-- Our 90-day technical support is only provided to registered users.

-- Your own personal ID.  As you use ECOMM/Lite, you will find that everyone
wants to use the personal ID #1.  This will, sooner or later, result in a
conflict.  When you register you get your own ID that HXJ will not to give
to anyone else.





@0[<< OK >>]                         @-1[Previous]
.94
Setting Up And Running ECOMM/Lite
ECOMM/Lite 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/Lite you need to:

  1.  Make a @12[routing table] for your communications network.

  2.  Set your @40[personal configuration] to tell TSRCOMM what directories and
      hardware to use.

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

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

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




@95[More about ECOMM's unique capabilities]  @-1[Previous]
.95
Applications that you can build around ECOMM/Lite
ECOMM was designed to be adapted to YOUR applications no matter what you do.

Using ECOMM you can send and receive e-mail messages and perform background
file transfers over LANs or whatever standalone mobile telecommunications
equipment you have.

In addition, if your particular application calls for messages that must be
custom designed to match your existing databases or fulfill your own particular
needs, you can use the S-record capabilities to design and use WHATEVER kind
of message you desire.

Since pictures are worth thousands of words, let's look at three applications
that are perfectly solved using ECOMM:

  - @96[Delivery vehicles]

  - @97[Mobile communications and remote database queries]

  - @98[Order tracking]

@0[<< OK >>]                         @-1[Previous]
.96
Delivery Vehicles
A driver starts his / her route with an itinerary and a list of pickups /
deliveries to make.  You would like to: 1) send updates for new pickups,
2) get status reports on the deliveries and pickups as they are made.

By equipping the vehicle with a laptop computer and either cellular or packet
radio communications and designing two S-records: one that lists a new
(previously unscheduled stop), and one that the driver uses to lists the items
picked up or delivered at the previous stop; you can accomplish the stated
objective.

However, to add an interesting twist, you could write a SIMPLE database
program that "hooks" into ECOMM to intercept the incoming reports from drivers
and insert them automatically into database.  This database can be used to
prepare for returning drivers, make new schedules, and calculate delivery
efficiency.

In addition, if your vehicles were equipped with navigational sensors, ECOMM
could automatically receive and forward to your headquarters positional
information that gets plotted automatically on an electronic map.

@0[<< OK >>]                         @-1[Previous]
.97
Mobile Communications and Remote Database Reporting / Queries
There are two conventional approaches to mobile database applications: 1) use
spread-sprectrum wide area network (WAN) technology to access databases
directly, and 2) use "dumb" mobile data terminals to log onto a mainframe.

Both of these methods suffer from inefficient use of the spectrum and excessive
complexity from the hardware viewpoint.

However, with ECOMM you have lower bandwidth requirements and hardware costs
by "hooking" incoming ECOMM requests into your own database program running
on an inexpensive PC.  Since no one is ever permanently logged on, wasting
valuable hardware, multiple users share the same serial ports and communications
equipment.

Furthermore, by relegating database searches and updates to the local database
servers, you reap all the benefits of client-server database architectures.

All it requires is that you create ECOMM's S-records that are appropriate to
your application and that you write a SIMPLE database program that hooks into
ECOMM to field requests and reports asynchronously.

@0[<< OK >>]                         @-1[Previous]
.98
Order Tracking
In a situation where a form is generated and must be approved or reviewed and
finally filled, it is often desirable to know:

  -- who placed the order, and when they placed it
  -- who approved it and when they did so
  -- and who filled the order and when was it filled

ECOMM's automatically filled in time/date and identification strings make this
chore a breeze.  See the SRECORDS.TXT file to find out how to make S-records
and how to specify automatically filled in fields.

ECOMM's power is in its hooks that let the final stage of the order process
get filled and logged automatically interfacing with your own database system.
For example, the person filling the order might simply send it to the database
and your program would intercept it and perform the necessary data
manipulations.




@0[<< OK >>]                         @-1[Previous]
.End
