General Release Notes
=====================

Multiview Mascot

Problem with Multiview Mascot: If you are running a Mascot session on
the server, and paste a large amount of text (more than about 100 
chars) from the clipboard to TelStar, Mascot locks up completely.
You can perform the same operation running the same program
without Mascot, and get normal operation.

The solution is to enable output throttling. This forces TelStar to
send output in smaller packets, with a delay between each.

---
SCO 3.2v4.2

Setting environment variables doesn't seem to work on SCO 3.2v4.2, even
though the 'handshake' completes correctly. If anyone knows why, I'd
like to be informed.

---
ANSI & CUSTOM SEQUENCES

Ansi/vt100 code sequences that start with "ESC[?" and "ESC[=" seem to
be implementation-specific or custom implementations. Certainly I've
found no documentation delineating any standards for any of these
sequences. If anyone can point any out, I'd appreciate it.

---
ANSI & COLOR

The Ansi spec seems to assume that only 8 colours are available for
foreground and background. Because Windows doesn't impose those
limitations, I've expanded the spec. See term definitions in the
help file for details.

---
NAWS (Negotiate About Window Size)

The telnet client and server should be able to negotiate NAWS at any
time (the server may refuse to accept a change - this is still
"successful" negotiation). In practice, I've found that (with SCO and
Linux at least) the server ignores attempts to negotiate NAWS after the
initial flurry of handshaking. This is not correct behaviour, but doesn't
seem to be doing any harm.

---
NAWS (Negotiate About Window Size) Problems

Some Unix hosts - in particular SUN - take NAWS very seriously. Even
if the term size is changed later, the host will remember the original
setting. This causes vi to get stubborn. If you have such a system,
disable NAWS using the SETTINGS program.

---
SETTING ALTERNATE TERM SIZES

Although you can set an initial screen size through SETTINGS, SCO
in particular seems to want to set it back to "default" size through
init strings.

---
ANSI vs SCOANSI

ANSI term type uses the 'standard' definitions for colors. SCOANSI uses
its own definitions. Unfortunately, if you are using ANSI, the color
combinations that SCO uses are truly awful. So the ANSI term type has
an "ignore color settings" setting. 

---
COLOR DEPTH AND TELSTAR

For some unknown reason, Windows dies when attempting to load ".FNT"
font files when in 16-color mode. Since TelStar uses FNT files,
the program cannot be used in 16-color mode.

