Sept. 22, 1984

Changes for MEX version 1.12
----------------------------

1) Fixed a bug in the READ processor, where spurious characters were
   generated under certain conditions, when parameter arguments were
   passed.

2) Fixed a buffer bug that affected term-files after a protocol send.
   When this happened, there would be garbage at the beginning of the
   term file.

3) The DEL command now asks for confirmation if the term-file being
   writing to has been appended to with the A secondary option.

4) STAT FILTER ON now suppresses all characters except carriage-return,
   linefeed, tab, backspace, and control-L (clear-screen on many term-
   inals).

5) The high bit is now stripped from all characters unconditionally in
   the character output routine.  Note that some terminals may use the
   high bit for control sequences, thus preventing the use of remote
   text editors.  If this is the case with your terminal, the following
   command (and subsequent CLONE) will correct this:

		POKE $46BC $0 $0

   (note that you should STAT FILTER OFF if you're using a remote screen
   editor).

6) Modified the logic in Christensen protocol receives:  if an EOT char-
   acter is received when a SOH is expected, it must be followed by 100
   ms of quiet time (otherwise, it's considered a noise burst, and causes
   a NAK to be transmitted).  This should reduce the number of partial
   file receives.

7) A period ('.') at the beginning of a command line now signifies a com-
   ment (intended generally for READ files).  Note that the comment line
   does not cross multiple command boundaries; thus,

	.This is a comment;DIR

   will execute the DIR command.

8)  An 'L' secondary option is no longer ignored after an S or R.

9)  Fixed a bug wherein the WECHO variable was being ignored in SENDOUT.
   
10) The '*' character may now be passed to the modem within a number, ex-
    cept that it must not be the first character of the number.

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

Note: these changes involved a new assembly of the program.  Thus, patch
files such as MXKPHKxx.ASM are no longer valid.

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

				Ron Fowler
				Fort Atkinson, WI