This file lists changes to Chat.

Last updated 1/6/1994

Version 1.0

This is the first full-featured release of Chat.

    Added Private channel support.

    Cleaned up the interface for selecting a channel; the seperate Open
    and Pick channel functions have been merged into Open channel.

    Better handling of low memory conditions.

    Numerous small bug-fixes.

Version 0.9b

    Added code to detect OS/2 2.1 DOS box and give up spare timeslices.

Version 0.9a

    Added code to detect Windows 3.x enhanced mode, OS/2 2.0 DOS box or
    Desqview and give up timeslices when appropiate.

Version 0.9

This is the second public release of Chat. There have been numerous 
changes, as listed below:

    Chat now allows monitoring multiple channels simultaneously.

    43/50 line mode is now supported on EGA/VGA cards.

    The editor has been greatly improved, and now features automatic
    word-wrapping.

    Private messages may be sent between chat users.

    A list of chat users is now available.

    The communications routines are more reliable than in previous
    releases.

    The help has been expanded greatly.

    The documentation is greatly improved (believe it or not!)

    Mouse support is more consistent.

Version 0.5

This version was the first public release of Chat. It was intended as an 
extended beta program, and had a limited feature set and a rather clunky 
editor.

Known bugs:

    Chat uses Novell's IPX protocol for sending messages between 
    systems. This protocol does not guarantee that messages will be 
    delivered. I have never personally seen a packet fail to be 
    delivered in this program, but it is possible. This could result in 
    messages not being sent, or the user list being incomplete. Unless 
    your network is particularly flaky, however, I doubt you will ever 
    see a missed packet.

    Chat has a limited number of buffers for handling cummunications. If 
    a large number of users are logged on to chat, it is possible that 
    packets will be dropped, resulting in symptoms like the above. 
    Again, I have never seen this problem arise in practice, but Chat 
    has not been extensively tested with more than ten users. However, 
    if you have slow workstations or a large number of users, you may 
    experience lost messages.

    The program does not handle low memory conditions very well. If Chat 
    runs out of memory, it will display a message explaining that it has 
    run out, and quit immediately. It requires approximately 300K to run 
    in initially.