** CAUTION ** CAUTION ** CAUTION ** CAUTION ** CAUTION ** CAUTION **
  **									  **
 **                Because XRS now uses longer records for                 **
 **  the RESPONSE.XRS file (to allow for 71-character subjects), messages  **
 **  written with previous versions of XRS will *NOT* pack correctly with  **
 **  XRS 3.22 (or later)...  YOU MUST PACK ANY EXISING OUTBOUND MAIL THAT  **
 **  YOU HAVE *before* YOU UPGRADING TO 3.22 BETA VERSIONS (OR LATER)!!!   **
  **									  **
     ** CAUTION ** CAUTION ** CAUTION ** CAUTION ** CAUTION ** CAUTION **


XRS now comes with a list of bulletin boards that support it in "XRS_BBS.TXT"
inside "XRS_BBS.ZIP".  This list is a compilation of all SysOp registrations
I have onfile.  Due to the fact that I lost records of some registrations, I
need each SysOp to verify that he/she is in the list, and if not, let me know
(soon!) so I can make sure their BBS is listed!


Changes from XRS 3.20 -=> XRS 3.30:

1) In a further effort to cleanup the echos, since I'm definitely guilty of
 making *too* easy to quote tons of mail, I added a background procedure to
 the routine run during message creation - it checks the ratio of quoted to
 non-quoted text lines in the message and displays the percentage of quotes
 if there is >= 50% quotes in the message.

2) Cleaned up the "DualList()" centering routines so that foreign native
 language configurations should display correctly if the text is longer than
 the English text.  In other words, all users should see the two windows
 (left being the current settings, right being the corresponding change)
 centered and side-by-side.  If the text is *way* too long, the right window
 will hit the right margin and not center properly, partially covering the
 left window, though.  C_Worthy automatically adjusts windows which would
 otherwise display paritially off-screen...


3) XRS uses a "Del ??.MSG" command rather than finding each ??.MSG file and
 using an 'unlink' on them one at a time - it's much faster if you wrote many
 messages.  This does call a spare COMMAND.COM at that point (once), but if
 you don't have enough room to do that, you probably don't have room to run
 XRS, anyway.

4) A 32bit x 32bit ICON for Windows 3.0 is included.  The filename in the
 archive is XRS_????.ICO - use the <ALT-F> "Properties" function after
 highlighting your XRS item, enter the appropriate filename as the icon file.

5) XRS displays "INSERT" or "TypeOver" in upper left corner and the relative
 screen position is shown in the upper right corner of edit screens during
 message creation.  If "Mark" is on, that is displayed in the center of the
 top border.  The updates only occur when they change, so there should be no
 problem with CGA snow.

6) XRS displays the name of the mailbag in the far-right top corner during
 both display and edit modes (it only works for "new" mailbags - if this is
 an existing one, it will show ">OldMail").  With named mailbags, this should
 help keep the various boards you use straight when you're replying.

7) XRS tries to figure how much space it will take to pack up your outbound
 mailbag by taking (5000 + size_of_??.MSG_files) * 1.5 as the guestimate.  If
 there isn't that much space free on your current drive, XRS will balk at
 packing mail until you delete enough space.  This won't fix all the problems
 and will *overestimate* if you have "BundlePath xxxx" on a different drive,
 but it *should* help in most all cases where the mail would simply evaporate
 before (because for some strange reason, PKZip doesn't bother to return a
 non-zero errorlevel under the "Disk Full" condition).

8) If your "BundlePath A:\" points to a root directory rather than a sub-dir,
 XRS should allow you to pack mail there - previously it would give an error
 message that the sub-directory didn't exist.
 
9) Added " þ EZ " to the "Nuke Garbage Filter".  This is yaglabupde (Yet
 Another Garbage Line Added By a Unique Proceessor Due to Ego).  Nuke Garbage
 filter includes " . EZ " as well (to filter out extra tear lines).

10) You can have two "USERLIST xxxx" files (with paths).  XRS doesn't bother
 to display the name of a secondary one if you use it - note that the first
 and last USERLIST parameters are used if XRS finds more than two.

11) You can chose not to clear previous tags when doing an <F8> search.

12) You can have up to ten "AutoMatch" parameters.  Using these last two, you
 should be able to mark multiple topics either automatically or from within
 the program.  XRS 4.0 will have a more flexible method of doing this.

13) XCS version number is no longer added to the tear line (jeez!  Some guys
 think they own the net just because we *let* them be our NC - whatever!).

14) The file "RESPONSE.PIF" is a 386-optimized windows 3.0 "PIF" file for
 RESP_286.EXE - for XRS's new unique ICONs, please see #4 above!


15) New configuration parameter "TAB x" controls the tab expansion of any
 imported files - default is 8 spaces per tab if not specified here. (the
 earlier versions of XRS didn't expand tabs at all...)  Note that values
 must be in the range 1..10 - otherwise XRS will return to the default 8.

16) I shortened the tear lines, to cut it back a bit.  Total (per message)
 savings is from 6 to 14 bytes depending on which BBS you use.  XRS still
 shows which BBS (or "XCS") you use in the origin line right before the
 network address field).

17) New CONFIG.XRS parameter "Hide Search" disables display ofthe matches <F8>
 finds (speeds up seaching 2 to 3 times or more depending on the video card).

18) XRS no longer gives up timeslices to Desqview during the logo display or in
 between cycles while color-cascading a match found during a search.

19) Fixed the ".x" portion in the disk size display. (it was always zero)

20) "BUFFER xxxxx" is back in the CONFIG.XRS file - default is 8192 if not
 set.  Minimum is 512 bytes, maximum is 32768 - anything outside that range
 will be ignored (and the default 8192 will be used).

21) In an attempt to fool TosScan into sending netmail messages created by XRS,
 *LOCAL* [32] bit is set in all messages and *FORWARD* [256] (some people call
 this "In Transit") bit is set in netmail message headers.

22) Both display of and reaction to High message numbers generated by RA only
 (i.e. those > 32767) will not blow XRS's mind.  Display of message numbers
 during mass export is also correct for message numbers > 32767.

24) If unused mailbags are found at exit time, you are given the opportunity
 to automatically restart the program.  Note that you must actually exit the
 program "normally" first (via <ESC> from the main menu, or using the hot-exit
 <ALT-F10> key) and run through the "cleanup" exit procedure (like "Do you
 want to pack mail...", etc) first.

25) Fixed the "Environment restored problem" by using the recursive technique
 to make sure the prompt is set correctly.  This eliminates the need for the
 special "Warning with beep" displayed when you <F10> hot-key to DOS Shell.
 It also means XRS "eats" an extra 96 bytes when you first start it, instead
 of the first time you restart the program.

26) The "XRS_Pack" banner was changed slightly to indicate XRS has its own
 integral FTS-0001 (Fidonet Technical Standard) packet file generator.  (it
 always has...)

27) XRS allows a subject up to 71 bytes long and captures the imbedded subject
 inside messages when the subject exceeds 25 characters (displayed in green).
 This extended subject is used for the subject of the response, unless you
 change it using <F3> on "Create/Delete/Edit" outbound message pop-up list.
 XRS also strips the imbedded "RE: " line out of the message text body.  Note
 that the "Date:" field displayed in the header is moved over to the right to
 allow 35 characters of the subject to show for private messages, and up to
 45 characters for public messages.  The entire subject (up to 71 characters)
 is actually copied into the outbound response message.  This makes records in
 RESPONSE.XRS 157 bytes each instead of 111 bytes.

28) The AREA: name is correct on private replies.

29) When you have several mailbags to pick from, XRS displays the filesize and
 and creation date and time of each mailbag.  Instead of depending upon the
 "COUNTRY=" setting, a new CONFIG.XRS paraemter "EuroDate" forces dates to
 display using DD.MM.YYYY instead of american MM-DD-YYYY format.

30) XRS doesn't add an extra blank line to the end of each echomail message.

31) "Re:" lines in netmail are recognized, and highlighted in green just like
 the have been in echomail.  The extended subject is also remembered for any
 quote or reply.

32) Support for seven new BBSID fields:
	a) "Cxxx" = eXpress Conversion System version x.xx
	b) "MAXI" = Maximus BBS
	c) "FIDO" = Fido/12 BBS
	d) "MGCK" = Magic BBS
	e) "MAX2" = OS/2 Maximus
	f) "SCRM" = Scream
	g) "PCBO" = PCBoard


33) If the BBS-ID field in "USERx.XRS" is not recognized, XRS no longer puts
 in the default name of "TComm" - in other words it just calls itself "XRS".

33) XRS does not have a problem if you try to eXport a message to "CON" twice.

34) Marking of messages in the Outbound "Create/Edit/Delete" list using <F5>
 allows mass eXport or deletion.  (tagging a message has the side-effects of
 both changing the on-screen color to the "Foreground Intense", and also if
 you highlight a marked message with the selection bar, it will blink.  <F7>
 is the "Cancel" or "UnMark All" key - it removes tags from all messages in
 the list.  Note, also that <F5> is a toggle switch - in other words it will
 also turn *off* any message you previously highlighted with <F5>.  All the
 tagged messages can be either eXported (with the <TAB> key) or deleted.

35) "Unregistered Evaluation Copy" no longer blinks.

36) XRS checks to make sure the "BundlePath" (if given) exists, and if it
 does not, a siren will sound & display an error message letting you know
 it is going to pack mail into the current directory instead.  This avoids
 the problem(s) with accidentally evaporated mailbags.  If the outbound
 path happens to be on a diskette, the critical error handler will give
 you a chance to insert a diskettes if necessary (if there is no diskette
 in the drive).

37) If CONFIG.XRS is not found in the current sub-directory, the PATH is
 searched to try to find one.

38) To protect archived messages, if you select "eXport in Quoted Format"
 (which exists solely for the purpose of exporting a message to quote in
 a second reply - not for archival purposes) and the filename you give is
 already exists, you are prompted whether to overwrite it.  If you answer
 "No" (the default) - the file is *not* exported.  If you answer yes, the
 file is overwritten.  Note that there is no prompt about overwriting if
 the filename given does not exist when you export in quoted format.  You
 should also remember that exporting "normally" (not quoted) always will
 appended to the file if it exists.

39) <E>xit "unmarks" a read message, so you see it again (only significant
 if you are in "Read Only New" mode).

40) You can "<J>ump" to a twitted message (if you insist <grin>...).

41) Critical Error Handler is back (trapping of "Abort, Retry, Ignore").

42) Several displays of signed numbers were fixed to be unsigned to correct
 the display of message numbers 32768-65534 in mailbags downloaded from RA.

43) All of the annoyances for unregistered users except entry of a temporary
 registration key are removed.  (a compromise for the ASP...)

44) Several type mismatches between functions were fixed.

45) If more than one new mailbag is found, a pop-up window allows you to
 select which one you want to un-compress and read first.  Note:  It will
 still process all .ZIP'd files first, then any existing .LZH'd mailbags,
 and finally any .ARC'd files after all the above have been read.  (in other
 words, you have to read all .ZIP'd mailbags before XRS will even look for
 any other .LZH/.LXR or .ARC/.AXR mailbags, etc.)

46) Removed several ancient variables that were no longer used.

47) Began nuking the RESPONSE.EXE and RESP_286.EXE files with "LZExe", which
 is a very fast on-the-fly decompression program for non-overlayed EXE files.
 The filesizes of each are now < 100k, and penalty is under three seconds of
 time during program load at most (not even noticable on a '386).

48) e<X>port in quoted format to another drive does not cause a rename error.

49) XREd was fixed so it can edit files not on the current drive.  Version is
 now 1.01...  (found inside XRS33NEW.ZIP - which augments XRS32KIT.ZIP)

50) A check is made for a device name instead of filename when you give the
 filename to e<X>port messages so the proper STDIO device handle is used if
 needed.

51) Support for "Named Mailbags" - i.e. ones with BBS names prefixed instead
 of only "BATxMAIL.ZIP", .ARC & .LZH).  Allowable names are "xxxxxxxn.ZXR",
 .LXR & .AXR, which denote .ZIP'd, LHArc'd and PKArc'd files respectively.
 The 'xxxxxxx' portion may be any unique BBS identifier picked out by the
 SysOp, and the 'n' must be the node number (or 1 for single-line systems).
 None of the BBS-side programs support it yet, but this will keep XRS one
 step ahead of those programs (so users will not end up with mailbags that
 the older versions of XRS do not recognize).  As soon as XRS 3.30 is out,
 I will update QMX to use the "Include" parameter to name the mailbag;
    Example:  "Include EZBOARD.XRS" will result in "EZBOARD1.ZXR", etc.
 This will make it *much* simpler to manage mailbags for users that pack
 up mailbags in more than one place.

52) A first attempt at putting together a world-wide XRS compatible BBS list
 is included in the XRS33COR.ZIP archive as "XRS_BBS.LST".  It is by no means
 even close to complete, since I lost over 100 SysOp registration forms to
 Hurricane Hugo.  If your BBS runs XRS and you are not listed, *please* send
 a message to me by *netmail* to update the list!  If you registered a BBS in
 the last week before the release date (July 4th), my apologies - you likely
 did not make this first release version...