home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Beijing Paradise BBS Backup
/
PARADISE.ISO
/
software
/
BBSDOORW
/
BW311RA.ZIP
/
README.311
< prev
next >
Wrap
Text File
|
1995-12-06
|
3KB
|
77 lines
The Blue Wave Offline Mail Door Version 3.11
Copyright (C) 1992-1995 by Cutting Edge Computing
All Rights Reserved.
[ALL] Affects all platforms
[MAX] Affects only the Maximus door (DOS)
[MAX2] Affects only the Maximus door (OS/2)
[OPUS] Affects only the Opus door
[PRO] Affects only the ProBoard door
[QBBS] Affects only the QuickBBS door
[RA] Affects only the RemoteAccess door
[SBBS] Affects only the SuperBBS door
[TAG] Affects only the T.A.G. door
[TG] Affects only the Telegard door
============
INSTALLATION
============
If you are upgrading from version 3.10 of The Blue Wave Offline Mail Door,
simply unpack the contents of the BWMAIL.ZIP archive into your mail door
directory. (Note that the documentation and other support files were not
updated, since version 3.11 is only a minor upgrade/bug-fix from version
3.10.)
If you are upgrading from an earlier version of The Blue Wave Offline Mail
Door, refer to the README.1ST file for installation instructions.
============================
WHAT'S FIXED IN VERSION 3.11
============================
[ALL] Output via the FOSSIL driver could occasionally overrun the
output buffer, resulting in garbled displays on the remote side.
This usually happened if the size of the FOSSIL output buffer
was set to less than 1024 bytes.
Note that though this bug has been fixed in the door code, we
recommend that you set the size of your FOSSIL output buffer to
1024 bytes or larger (if possible), especially if you are using
a high-speed modem (14.4K or faster).
[MAX] Users were unable to tag message areas which contained non-
numeric characters in the message area number.
[QBBS] All messages uploaded to the mail door were being addressed to
[SBBS] "All" instead of to the person listed in the To: field, due to a
bug in the code that checked for Group messages.
[RA] When configuring the Fido->Internet Gateway, BWSETUP would not
insert the proper area number when selecting the Destination
NetMail Area Tag.
[RA] BWSETUP could not always find the MESSAGES.RA file in a multi-
node configuration.
[TG] Messages uploaded to Squish bases were reporting "unable to open
message base". The messages actually *were* being written to
the Squish base; however, the door was then trying to write them
to non-existant JAM bases(!).
[TG] BWSETUP's user editor was mis-numbering areas when <F5> was
pressed to edit the user's tagged message areas.
==================================
WHAT'S NEW/CHANGED IN VERSION 3.11
==================================
[ALL] The NEWFILES.BW file will no longer be created if there were no
new files detected on the BBS.