Changes since v3.45

Bugfixes:
	The distribution version of RBCONFIG in 3.45 triggered a
	code-generation bug in Turbo C 2.0 which would trash much of the
	dialing directory when moving an entry.  This has been worked
	around.  (technical details: the bug involves doing far pointer
	arithmetic multiple times on the same pointer when passing
	function arguments in small-data models if the size of the far
	pointer's data type is a power of two, and only when generating
	8086 code, not 80186; the result is that the segment of one of
	the function's arguments gets trashed.)  I did not discover the
	bug before release because I had been compiling with 80186 code
	until building the final release version.


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

Changes since v3.41

Bugfixes:
	OPEN_LOG inside a MULTI now works properly.

	BREAK inside a MULTI will now work for all re-compiled macro files

	Selecting [W]rite from the scrollback screen will no longer present
	the dialing directory file as the default destination

	When dialing a list of numbers, the correct item is deleted from the
	list on a successful connect (previously, the *following* item was
	deleted)

Enhancements:
	more efficient screen updates under DESQview will allow RBcomm to
	  handle higher speeds on incoming data before invoking flow control
	  (at the cost of increased jerkiness when it is spending most of
	  the available CPU time handling incoming characters)

	by request: increased number of COM port definitions in the
	  configuration from four to eight

	by request: WHENI command which is identical to WHEN except that it
	  ignores the case of the characters in the string to be matched.

	new command: EVERY
	  similar to DELAYED, but repeats execution indefinitely

	the receive buffer size is now adjustable.  A larger buffer may
	  give better performance at high speeds, while a smaller buffer
	  will save memory.

Known problems:
	You may need to run RBcomm via LOADFIX if your DOS's low-memory use
	  is sufficiently small.  This will be corrected in the next release,
	  but I didn't have time to make the necessary internal changes
	  which will completely avoid the problem.

	I've been experiencing occasional lockups when returning to RBcomm
	  from a file transfer.  This started in RBcomm 3.41 when I upgraded
	  QEMM from 7.04 to 7.50 and appears to be related to a known hardware
	  bug in my Pentium's "Neptune" chipset's 16550 emulation.
	  Unfortunately, nothing I've tried has completely fixed the trouble.
