Dec 082017
 
Chatter - Chat program for Novell Networks (new version).
File CHATR2.ZIP from The Programmer’s Corner in
Category Network Files
Chatter – Chat program for Novell Networks (new version).
File Name File Size Zip Size Zip Type
CHATTER.C 37679 8450 deflated
CHATTER.DOC 10788 4124 deflated
CHATTER.EXE 15955 9642 deflated
CHATTER.OBJ 8876 5047 deflated
IPXLIB.C 5285 859 deflated
IPXLIB.H 9885 2357 deflated
IPXLIB.OBJ 1385 731 deflated

Download File CHATR2.ZIP Here

Contents of the CHATTER.DOC file


CHATTER V1.20
Copyright (c) 1992 by Kurt Duncan - All Rights Reserved

This program is provided as FreeWare - You are granted a license to use
this program on any number of workstations, or to install it on any number
of file servers, without recompense. You may distribute ONLY the original
ZIP file, which is the sole medium of release of this software. You may
NOT distribute the separate files to any outside organization or any other
parties, except in the form of the original ZIP file.

All rights remain the sole property of Kurt Duncan -
Regardless of any claims to the contrary by CompuServe Information Service

The usage of this software is entirely at the risk of the user. Kurt Duncan
does not accept responsibility for any damages caused by, or incurred through
the use of, this software. No warranties are expressed or implied. The
software is provided as-is, and is not subject to update or maintenance.
Be that as it may, you may leave comments or questions to:

Kurt Duncan
CompuServe user-id 70262,40

If this software just totally fails to operate, go ahead and leave a message.
Also, if you have any inkling as to why it failed, PLEASE don't hesitate
to suggest solutions.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Files you should have received include:

CHATTER.C The source code (surprise!)
You do not need ANY developer kits to compile this code.
It was compiled under MS C5.1

CHATTER.OBJ The object file for CHATTER.C

IPXLIB.C More source code!
A variety of C functions which make it easier to communicate
using IPX as a transport.

IPXLIB.OBJ The object file for IPXLIB.C

IPXLIB.H The header file required for using IPXLIB functions.

CHATTER.EXE The executable code for CHATTER

CHATTER.DOC This file.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

This program is a simple vehicle for conferencing between multiple
workstations which are connected to a Novell Network. The only purpose for
the development of this software was to gain some experience in programming
for NetWare. The software was developed on a 486DX/33 system, and verified
on various 386 & 486 platforms. IPXODI V1.20 was used during development
and testing. NETX is not necessary for the operation of this software.
The compiler was MicroSoft 6.0. Personally, I preferred 5.10.

For the sake of simplicity, I write directly to screen memory, starting at
address B800:0000. This should work for most video adapters that are
currently on the market. CHATTER.EXE has been tested in a normal DOS
environment, and in a DOS non-windowed application environment under Windows
3.1 enhanced mode.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

To execute the program, enter:

CHATTER [switches] [identifier]

[identifier] is the unique code by which your messages will be identified.
You may use up to eight characters. If you do not specify an identifier,
your messages will be identified as "".

[switches] are one or more of the following:

-rnn nn indicates the number of rows on your display.
The following line might be used on a VGA display:
CHATTER -r50
Note that CHATTER does NOT change your video mode.

-m used to indicate the presence of a monochrome monitor.
This will affect the colors used on the display.
CHATTER will STILL write to B800:0000 - this option is NOT
for use with old-style monochrome text-only video boards.

-shhhh hhhh is a hex value indicating the IPX socket number to be
used for communication. You will normally not need to alter
this value, which defaults to 5000 (hex). You may use this
option to provide separate channels for conferencing.

-bnn nn indicates the number of buffers that are to be allocated.
Messages are sometimes received faster than the polling
algorithm can handle, so several buffers are set up to help
cushion the various bursts of traffic. Such bursts are
particularly noticeable when workstations respond to a probe
message. This value defaults to 16, which is a reasonable
minimum value. You should, however, set it no less than the
maximum number of concurrent CHATTER users.

-nhhhh hhhh is a hex value indicating the initial number to which
messages are to be sent. Multiple networks may be specified
by using multiple occurrences of this switch. If not given,
the local network is assumed. More on this later.

The display is made up of two areas. The top area, consisting of the
entire display except for the last line, is the message display area. The
last line is used for message input. Two types of messages will be
displayed in the message display area.

Messages that are read from the network will be prefixed by the identifier
associated with the sender. In other words, if someone who executed
CHATTER with an identifier of JOE-S sent a message, it would appear as:

JOE-S Hello, World!

Messages that are displayed by CHATTER to the local display do not have
such a prefix. These message may include help text and trace information.

When you execute CHATTER, the cursor, which is a solid underline, is placed
in the first column of the message input area. Several messages will be
displayed, including the name and level of the software, along with the
current settings. You may begin entering text. When you hit the return key,
the text that you keyed into the input area will be broadcast to the network,
to be picked up by all CHATTER users including yourself. The input area is
cleared, and the cursor is returned to the first column. You should
immediately see your message appear at the bottom of the display area,
prefixed by your ident code. That same message will appear in the display
area of all other CHATTER users.

If the text you enter is preceeded by a backslash (\), CHATTER will try to
interpret your input as a CHATTER command, rather than as a message. The
following command are recognized:

\EXIT (or ESC key) - terminates CHATTER
\HELP (or F1 key) - displays a list of valid commands
\TRACE (or F2 key) - toggles trace mode on and off
\WHO (or F3 key) - sends a probe message, causing all CHATTER users
to send respond messages to you. This happens
transparently to the other users.
\NETS (or F4 key) - lists active network numbers

While trace mode is active, all network traffic to and from your workstation,
on the specified socket number, will be monitored. A message will appear in
your display area for each packet. This is an interesting, if not very
useful, feature. It was useful primarily during development.

Common Messages:

xxxxxxxx << Joining Conference >>
The user identified by xxxxxxxx just executed CHATTER, and is now able
to send and receive messages.

xxxxxxxx << Leaving Conference >>
The user has issued the \EXIT command or pressed the ESC key, terminating
CHATTER.

xxxxxxxx << Responding to Probe >>
This is the result of a \PROBE command from you. It is the means by
which you can identify all of the current conferencees. When you
execute chatter, a probe is automatically sent.


About multiple network numbers: (new with v1.20)

In its initial state, CHATTER will send messages only to the local network.
This disallows sending messages across routers into other networks. However,
CHATTER maintains an internal list of networks from which it has received
messages, and all output is sent to each network in this list. In other
words, all it takes to get CHATTER to send messages to network (x) is to
receive a message from network (x). Henceforth, all CHATTER sends will go
to network (x) as well as any other networks from which it has received
messages. This list will naturally include the local network, as CHATTER
will almost immediately receive its own messages at startup time, from the
local network.

So the big question is, how do we get someone else's CHATTER, on a distant
network, to send the message which allows our CHATTER to respond? Some
client on our network has to send a message to that distant network first.
The propagation scheme sounds good, but how do we get that first message
going?

A new switch has been added to allow CHATTER users to specify network
numbers which are placed in the initial table. The initial list *MUST*
include the local network number as well as the network numbers of all
remote networks which are to be included in communication. The format of
the switch is:

-nhhhh where hhhh is a hexadecimal network number

For example, if your local network number is 00000002, and you wish to
communicate with the local network as well as network 1234ABCD, you would
invoke CHATTER as follows:

CHATTER JOE-BLOW -n2 -n1234ABCD

If you do not specify your local network, you will not see your own traffic,
or any other traffic that is sent to or exists on the local network.

You might ask why we add network numbers to our internal list "on the fly",
if we specify them up front. The idea is that Joe and Marty, on net 2, may
be chatting. Now Mary comes in from net 3 with -n2 and -n3 specified. Her
initial message will cause Joe and Marty's lists to be updated such that they
can communicate with Mary. This allows some latitude for users which are
not aware of the -n switch, or are unaware of various network numbers.

Due to the complexity of the processor call line in a multiple network
environment, you will probably wish to invoke CHATTER via a simple batch
file, which can be set up in any search drive on the file server.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

I am heavily indebted to Charles G. Rose, who authored the Programmer's
Guide to NetWare, without which this project would not have been possible,
and to Peter Norton, whose Programmer's Guide to the IBM PC is still on
my desk, although it is about to fall apart.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Release History:

CHATTER V1.00 - the original program, which was only released to one person.

CHATTER V1.10 - This release, which is the first official release.

CHATTER V1.20 - Support multiple network numbers


 December 8, 2017  Add comments

Leave a Reply