BGQWK 1.0 BETA 21
--------------------------------

1. Fixed a MAJOR problem with the net status logic.  Net status would never
   work properly on conferences 0, 128, 256, etc, and on all the rest, the
   positions were shifted over one causing much trouble.  Thanks to Richard
   Walker for discovering this bug.

2. The P)revious command off the S)elect meny now works properly when in
   the first screen.

3. Fixed some problems with linking message reply numbers.  When a
   reference number was used, the "see reply" flag was being used instead of
   the "see original".  Fixed that and now also flag the other message header
   so that a reference pointer is generated.  This is probably a bug that goes
   all the way back to the BGPCK days.  Fixed.

4. Jerry Hook and others discovered that if you specified a file to be
   inserted as a new file list (via the UP= directive), it wouldn't be
   inserted.  This feature is now BACK!  (Remember, this is completely
   optional).

5. Fixed a rather peculiar problem with the index/hashing logic.  I have
   two users on my board "Clif Davis" and "Greg Miller".  Because their hash
   codes just happen to be the same, BGQWK would assume "Clif Davis" was on
   the board when, in actuality, it was "Greg Miller".  (Yes, that may have
   caused some potential security problems).  All is fixed now, I believe.

6. Fixed a few minor problems with the ansi driver (that's why ASCII
   screens were having double linefeeds, etc and also the <ESC>[xH commands
   were not being treated properly.  Fixed another bug in the ansi driver
   that caused background attributes to be brough up rather than blinking
   attributes.  Fixed a bug that caused BGQWK to lock up if an illegal ansi
   call was read.

BGQWK 1.0 BETA 20  SAT 11 JAN 92
--------------------------------

ATTENTION ALL REGISTERED USERS: Chris Cook discovered quite a big bug in
the registration logic that causes all registered BGQWK's beyond serial
number 29 to assume they are unregistered.  This problem has been
corrected, BUT in order to do so, I had to change the format of the
BGQWK.KEY file.  You will need to pick up a new KEY file in door number 4!

We've overshot the tentative release date a month already, so we might as
well keep beta testing, <grin>.

Several bugs have been reported, but I just didn't have the time to get all
of them.  I have corrected as many as I could for this beta.

This release will only contain the regular version of BGQWK.EXE.  From my
experience, the AT version ran about the same speed as the XT version.  Do
any of you have any comments about the difference in XT and AT versions?

Well, the source code to BGQWK has gotten so large that I can't even use
the Turbo Pascal 5.5 internal editor anymore, so all future versions will
be compiled under Turbo Pascal 6.0.  (I'll just use it's command line
processor since I _hate_ the 6.0 environment!)

Beta 19 was very buggy.  Numerous bugs have been fixed in this release.

1. The problem John Ferra's users have been reported has finally been
   corrected (the problem with private messages sent through Winqwk were being
   marked <RCV'D> before it actually was).

2. I have again tried to fix the problem with the garbled select screens on
   some systems running high speed modems and I belive I fixed it.  Let me
   know please!

3. A bug since long betas since has been fixed.  If a user dropped carrier
   on the board, BGQWK would not clean up its work directory.  Fixed.

4. Finally!  Errors will now be logged in the BGQWK.LOG file that is
   created in the GTPATH directory.  The log file will probably be changing
   all the time to suit the needs of the sysops running the door.  Let me know
   what all you want me to add to the log file.

5. Dan Mancuso has suggsted that BGQWK not bomb out when it encounters a
   missing .MSG or .MES file.  This is now done and BGQWK will report the
   error on screen and in the log file.

 1-10-92 19:27 Guest Account~Houston, Texas
 1-10-92 19:28 CORRUPTED [D:\MAIL\GENERAL\GTMSGS\00100.MES] SOM2
 1-10-92 19:28 CORRUPTED [D:\MAIL\GENERAL\GTMSGS\00100.MES] SOM4
 1-10-92 19:28 CORRUPTED [D:\MAIL\GENERAL\GTMSGS\00100.MES] SOM7
 1-10-92 19:28 user returns to the board

   If you are using GT 16 or later, the SOM id will also be given for
   debugging purposes.

6. Jerry Deguzman reported a bug that has now been fixed.  BGQWK was not
   "trimming" imbedded spaces from the end of some strings in the BGQWK.CNF
   file causing problems with PKZIP.

7. Fixed some little strang things with the strip bit routines.  If BGQWK
   displays a "unregistered" tagline, high bit characters were not being
   stripped.  Fixed.  Also, when the bits are stripped, if it happens to come
   out to be an ^X, ^Z or null, they will be converted to "~".  (Those some
   redifintions will be used on normal conferences as well).  Also, in strip
   bit conferences, any ESC character will be changed to "~" as well.

8. Several people reported a major bug in prepack mode.  If no new messages
   were available, the program would get stuck in an infinite loop.  Fixed.

BGQWK 1.0 BETA 19  SUN 29 DEC 91
--------------------------------

... Finally! ... DOCUMENTATION! ... take a look at BGQWK.DOC.

We are getting ready to release BGQWK offically (as soon as I get the time
to type out a good BGQWK.DOC and BGQWK.HLP files).  Please report ANY bugs
or quirks IMMEDIATELY to my board or to my conference, E02/758.  DO NOT
SEND NETMAIL (Russell and I are still experimenting with netmail).

All UNregistered users ... please remove your BGQWK.KEY.  It has expired.
Remember, BGQWK is not crippleware.  The only difference between the
registered version and unregistered version is a tagline that is appended
to messages uploaded through the door that says "Unregistered Evaluation
Copy".  This is shareware.  Please support it if you haven't already.

8088 and 80286+ versions of the EXEs are included with this beta release.

UTIEXPRT: two changes, 1) if a message is longer than 70 lines, it will be
split into multiple 70 line messages so TNet doesn't lock up.  I probably
could go to 100 lines, but I'm keeping it low just to be safe.  2) I
discovered that if a message starts with a blank line that UTIEXPRT had a
bug that made it think that no message was there.  Fixed.

1. Well, I thought I fixed the [H]angup bug in the last release, but
   apparently not so.  I have fixed it this time.  I hope.  <grin>.

2. BGQWK now supports full duplex file transfers via the HS/Link protocol.
   Users can now drive themselves crazy trying to upload a REP file and
   download a QWK file at the same time, <grin>.  You must have HSLINK.EXE
   somewhere in your DOS PATH if you want BGQWK to use it.  And, of course,
   this is TOTALLY OPTIONAL.  If you have the "s" parameter on the BGQWK
   command line (for DSZ "ho sl", handshake slow), BGQWK will also start
   HS/Link in -HS (handshake slow) mode.  I don't know if this feature will
   get much use, but it was pretty easy to implement and all the PC Board
   authors are starting to do it too.

3. I changed around some of the command strings sent the DSZ.  You
   shouldn't notice any difference.

4. More cosmetic changes.  Also, stacking of commands can now be done with
   the ";" as well as the " ".

5. Added two options in the C)onfig menu.  It allows users to disable the
   door to send users their own messages.  Another allows the door to send
   zero message QWK packets (some networks and users prefer that way).

6. The 'test mode' code has been removed.

7. If a FILES.BBS is not found, BGQWK will automatically skip the new file
   scan regardless of the user's new file scan setting.  Thanks for Jim
   Kreyling for discovering this bug.

8. Bug in /PP, prepack mode, fixed.

BGQWK 1.0 BETA 18  SUN 22 DEC 91
--------------------------------

Just a reminder ... if you have not registered BGQWK yet and are using an
old BGQWK.KEY file that was included in some of the older beta copies (the
ones that say for use by GT Power Beta Testers only), that key expires on
January 1, 1992.  Just delete that key when that date roles around.

The UTIs included have changed slightly to work better with networks.

1. People have still reported that BGQWK is placing its CTL file in some
   strange places.  Therefore, in order to keep everything running
   smoothly, I have decided that from now on, BGQWK.CTL _must_ be in the
   same directory as your USER.CTL file.  (If you are running a LAN, that's
   your LANPATH directory.  If not, your GTPATH directory).  PLEASE MOVE
   BGQWK.CTL TO THE SAME DIRECTORY AS YOUR USER.CTL FILE.  Thanks.  And
   remember to delete all occurrences of it elsewhere.

2. I've heard reports from all over the place that sometimes BGQWK gives
   callers a bunch of garbage on the S)elect screen half way through.  I have
   attempted to fix this, but I don't know if the code I added really will be
   helpful or not.  Ask your callers if they notice the garbage or not.  Also,
   the little 'SD' indicator on the BGQWK status line wasn't really
   functioning correctly in previous betas.  I've attempted to fix that.

3. Some people have told me that DSZ seems to not allow uploads or
   downloads sometimes in BGQWK but it works just great when in GT.  Well,
   I've also attempted to fix this.  I do a closeport() before shelling and an
   openport() after shelling.  This should release the interrupts and should
   cure the problem.  If it doesn't, I don't know what else to do.  Let me
   know how this goes.

4. Some QWK reader authors have got in touch with me and informed me of
   some errors in QWK packets created with BGQWK.  I've tried to correct
   these.  The first was that BGQWK was creating zero-length NDX files in some
   conferences.  I wasn't aware this was happening, but I checked it out and
   sure enough, it was.  That has been corrected.

5. There are some cosmetic changes.

6. Well, I tried a pre-release of this beta on a system that is having
   problems with people uploading REP packets and it still didn't work.  I
   have given it another shot in this beta.  I think the problems may have
   something to do with DSZ receiving files in that little window, so the
   window will no longer be used when doing so.  Yes, it was the little
   window that was causing the problem with DSZ receiving files.  From now
   on, when BGQWK receives files, it will not use the window.  DSZ when
   sending doesn't seem to have a problem with it.

7. Douglas Pippel reported several months ago that BGQWK seemed to let
   users download packets even if it took them over their time limit.  I have
   finally been able to re-create the event, and I believe the bug is fixed.

8. Fixed a bug that sometimes caused a user's timebank credits, when
   deducted, to actually increase.  <blush>.

9. Fixed in a bug in which BGQWK didn't remind first time users to config
   their setup and select their conferences.  It now does this, but the
   first time welcome is now configurable.  See the "$newuser" directive in
   the BGQWK.HLP file.

10. Paul Schwarz discovered that if the G)oodbye command was disabled, the
   user was still given the option to [H]angup after the download.  This has
   been fixed.

BGQWK 1.0 BETA 17  MON  9 DEC 91
--------------------------------

Attention: Andy Mcclung -- your registration came in and you haven't picked
up it yet.  Call my board at 713-893-9124 and open door 4.

It's been quite a bit of time since the last beta of BGQWK.  Several people
reported bugs in Beta 16, I was tied up a bunch, and this version kept
locking up on my system, but I think it's working decent now.

1. If you don't want to read a bunch of mombo-jumbo about BGQWK's new
   feature dealing with networks, ignore the included UTI*.EXE files and
   skip to new feature number 2, way, way down in this file, <grin>.

   The biggie in this release is that BGQWK now fully supports the creation
   of "net status" QWK packets and the insertion of "net status" REP packets.
   Thanks to Greg Hewgill, the author of SLMR and TNet for helping me find
   the information for the NETFLAGS.DAT file.  (Had to make several calls
   to Canada, but I guess it was worth it in the long run).  If you wish to
   grant a user "net status", the format for doing so has changed YET
   AGAIN, <grin>.  Take a look at this excerpt from my BGQWK.CNF file:

ns=B.J. Guillot/LO RN             <- he has net status in those nets
ns=Node C-tech/RN TX              <- he has net status in those nets
ns=Node 001-056/GT                <- he has net status in those nets

   As many NS= entries can exist as need be.  Simply put the user name,
   followed by a slash and then the two-letter "net indicators" that let
   BGQWK know which conferences that user can net to.  For example, I gave
   myself net status in my local conferences and RelayNet conferences.  Say
   that I wanted to set up a second node to my system in a distant part of
   the city, I could just make a script to call up my board, make a QWK
   packet then logoff.  Once I have that QWK packet on my hypothetical
   distant system, I would run TNET or GTQWK (aka MERLIN) to import them,
   etc.  Duplicates are taken care of as best as possible.

   Also note the NS= entry for the "Node 001-056".  It is now possible
   (I know Warren isn't going to like this, <grin>) for non-GT systems to
   join GT Network echomail conferences.  I granted that guy NS access in
   the GT conferences I carry.  The other non-GT system will have to run
   some form QWK network software such as QNet, RNet, TNet, etc.

   I have recently added a QWK network to my board, TexasNet using the TNet
   software.  TNet was originally designed for WildCat, but Greg added UTI
   driver support.  Since I happen to have written some of those for GT,
   you can conviently join any QWK network such as SmartNet or ILink.  (Of
   course, you can also do this with MERLIN as well).

   I have posted TNET21.ZIP on my board and the three new UTI drivers are
   included in this beta relase of BGQWK.  (IF YOU PLAN TO USE TNET, DO NOT
   ATTEMPT TO USE PREVIOUS VERSIONS OF MY UTIs, TNET WILL CHOKE).  Of
   course, the same UTIs you use with TNet can be used with the PC-Relay
   software if you are currently joined in with RelayNet (aka RIME).

   Here are some sample files which drive my system allowing it to access
   the TexasNet network:

   HOPPER.CFG (configuration file used by TNET)
--------------------------------------------------------------------------
SYSTEM      = UTI2
WORK        = D:\RELAY\WORKIN
QWKDIR      = C:\GT\SPECREQ
REPDIR      = C:\GT\UPLOADS
LOGFILE     = TNET.LOG
PACKER      = PKZIP -es ! , PKUNZIP -o !
APPEND      = Y
ATFILTER    = N
VERBOSE     = N
TTAG        = Y
PRIVNAME    = B.J. GUILLOT
IMPORTTAG   = T , Ed Hopper's TexasNet
EXPORTTAG   = T , Tranquility Base - 713-893-9124 - Houston, Tx

CONF        = $D:\MAIL\TNET001
  HUBNUM    = 208
  PRIVATE   = N
  TAG       = T
  NEXTMSG   = 76

CONF        = $D:\MAIL\TNET002
  HUBNUM    = 221
  PRIVATE   = N
  TAG       = T
  NEXTMSG   = 84

CONF        = $D:\MAIL\TNET003
  HUBNUM    = 218
  PRIVATE   = N
  TAG       = T
  NEXTMSG   = 68

CONF        = $D:\MAIL\TNET004
  HUBNUM    = 209
  PRIVATE   = N
  TAG       = T
  NEXTMSG   = 114

CONF        = $D:\MAIL\TNET005
  HUBNUM    = 271
  PRIVATE   = N
  TAG       = T
  NEXTMSG   = 76
--------------------------------------------------------------------------
   Note that all the CONFs have little dollar signs in front of them.  Make
   sure you leave them there so that TNet runs my UTIs in "Bridge" mode.

   The TNet users guide explains what all that stuff means.  Note that the
   "NEXTMSG =" lines are maintained by TNet.  Also note the "SYSTEM = UTI2"
   line up there.  Shh!  That's a secret.  It's not documented in the TNet
   manual because Kip Compton (the guy that came up with the UTI format)
   doesn't want Greg Hewgill (TNet author) to support level two UTIs
   because Kip came up with the UTI concept.  Well, I don't care which
   programs use my UTI drivers!  Just don't spread around the word of this
   undocumented tid-bit or Greg could get in a heap of trouble.

   TEXAS.BAT
--------------------------------------------------------------------------
@echo off
d:
cd \relay
copy c:\gt\uploads\hopper.rep .\backup
del c:\gt\uploads\hopper.rep
copy c:\gt\specreq\hopper.qwk .\backup
del c:\gt\specreq\hopper.qwk
tnet export hopper
echo athm1 > com1
gr1700 hopper *xxxx-xxxx
echo ath1m0 > com1
d:
cd \relay
tnet import hopper
d:
cd \relay
--------------------------------------------------------------------------

   That batch file simply packs up any new TexasNet messages on my system
   for exporting, calls Ed Hopper's BBS (my TexasNet hub) via a GT script,
   uploads the REP file TNet made.  Downloads a QWK file made by Ed's
   MARKMAIL board, exits GT, and then runs TNet again to import my new
   TexasNet mail.

   My script file is still under construction so I won't post it yet.

   BTW ... several people asked if I am going to update all the UTI files
   to support Megamail.  The answer: NO.  I will only update the UTI files
   that are required by PC Relay and TNet.  I do not agree with Kip's
   attitude, and secondly, if you users still want to use the MegaReader,
   they still can -- Kip's MegaReader supports QWK packets!

2. I have added better error handling routines.  There is no more need for
   the 'x' experiemental mode option because BGQWK will now inform you what
   file the problem is occuring with (or it will, at least, attempt to).  This
   will help all those sysops that have BGQWK runtime error out when the door
   attempts to initialize.

3. BGQWK should never put the BGQWK.CTL file in the root directory (unless
   for some reason, you have the GTPATH or the BBSPATH set to the root
   directory.  Check your root directories for any BGQWK.CTLs.  If you find
   them, delete them at once.  Let me know if they pop up again as this causes
   BGQWK serious problems (such as the non-saving of new configuration
   information, etc).  This error was previously caused by a blank BB=
   entry in the GT.CNF file.

4. Several people complained that the logoff screen when users G)oodbye
   from within the door lacked CR/LFs.  They are there now.

5. I reworked the colors, again, in the execute window.  Hopefully, the
   monochrome sysops will be able to see whats going on again, <grin>.

6. A few of you have asked if I can add a H)elp screen to the S)elect menu
   before it goes into the conference screen.  This is now done.  Take a look
   at the BGQWK.HLP file under the "$selcon" directive.

BGQWK 1.0 BETA 16  SAT 23 NOV 91
--------------------------------

*** IMPORTANT -- DELETE BGQWK.CTL -- THE FORMAT CHANGED YET AGAIN ***

The following people have picked up their registration keys:

10-27-91  12:52  Site #1: Tranquility Base - 713-893-.... - Houston, Tx
10-28-91   7:02  Site #2: The Event Horizon 813-726-.... Safety Harbor, FL
11-02-91   6:16  Site #3: The ...Engage BBS þ 618-244-.... þ Mt.Vernon, IL
10-28-91   9:11  Site #4: Club PC BBS - 804-357-.... - Smithfield, Va.
11-05-91   9:27  Site #5: Jack's Board - 404-798-.... - Augusta, GA
10-29-91  15:06  Site #6: Christian Resources BBS -804-543-.... -Norfolk-Va
11-03-91  16:18  Site #8: The Rib 'n Rail BBS (519)264-.... Mount Brydges
11-09-91  16:56  Site #9: One Step Beyond - 808-695-.... - Waianae, Hi
11-15-91   0:05  Site #12: B. F. P. Services - 713-492-.... - Houston, TX
11-22-91  19:27  Site #14: SKYLINER

The following people have sent in registrations but have not yet opened
door number 4 on my board to pick up their reg keys.

007 ../../.. Ken Opdycke
010 ../../.. James Gunnells
011 ../../.. Ken Kirkland
013 ../../.. Dan Mancuso

1. Beta 14 added support for 510 conferences, but I just now noticed that
   the ALL/BRF flags in the BGQWK.CTL file only supported 256, <grin>.  I
   needed to expand the CTL to accomodate 510, thus the reason for having to
   delete the CTL file again.  Sorry.

2. Beta 14 introduced "net indicators".  These now will do something.  When
   the user selects S)elect, it will now give them the option to list J)oined
   conferences, U)njoined conferences, A)ll [default], or they can enter the
   two letter "net indicator" to list only conferences in specific networks or
   groups or whatever you choose to use the two-letter "net indicators" to
   represent.  And yes, blank lines are no longer left when displaying the
   conferences.

3. Another neat feature that sysops have been asking for has been
   implemented as well.  BGQWK can now "prepack" user QWK packets.  Here is
   an example batch file:

      @echo off
      rem -- this batch file runs as an event during some time
      bgqwk n f: /pp:John Doe
      copy c:\gt\specreq\tranquil.qwk c:\gt\uploads\forjohn.zip

   Notice the "/pp:John Doe".  The "/pp" is for "prepack" and the users
   name, John Doe in this case, is entered using correct case.  Please note
   that the QWK file generated will be sent to YOUR download path.  It will
   be YOUR responsibility to copy the file to some directory where the user
   can access it.  It will be the users responsibility to rename the file
   to the correct name if you named it otherwise.  In the above example,
   when John downloads the file from GT in my new uploads directory, he'll
   download the file called "FORJOHN.ZIP" he'll need to rename it to
   "TRANQUIL.QWK" or whatever name it should be called.

4. PLEASE NOTE -- some of the default options are now initialized
   differently.  Be sure to check the descriptions of the options carefully.
   Notice some flags such as "G" are now "don't allow goodbye" when it used
   to say "allow goodbye".  I'm doing this so people that don't read the
   docs can see all the features of BGQWK without having to ask me "can you
   add a feature to allow BGQWK to let the users logoff from inside the
   door", etc, etc.  If you wish to run BGQWK with no options, an example
   command line would be so:  BGQWK . F:  (just use a "." in place of the
   command options).

  x - experimental mode      unlisted menu commands:
  5 - using with gt 15.50         v - version bgqwk
  m - using moby turbo            t - test mode toggle
  g - using ymodem-g         conference options
  s - ha slow, not ha both        g* - guest, application
  a - force news always           a= - access level only and sy
  k - kill protect incoming       n~ - netmail conf
  h - don't allow goodbye         p^ - public msgs only
  r - don't use ref num           r< - read only
  d - don't move if flag wrong    x$ - private only
  n - don't allow file scan       s  - strip hit bit
  l - don't allow tagged d/l
  b - don't allow timebank

BGQWK 1.0 BETA 15  SUN 17 NOV 91
--------------------------------

1. A major problem in the last beta has been corrected.  Last read message
   base pointers were going beserk.  Fixed, I hope.

2. Fixed a problem with GT 15.01 systems.  Because the BB= (bbs/cbs path
   entry) was not included in GT.CNF files of those types, BGQWK was getting
   confused.

I was very busy this weekend so I was unable to make any new changes except
for fixing the above two bugs.

BGQWK 1.0 BETA 14  SAT  8 NOV 91
--------------------------------

1. BGQWK now supports up to 510 conferences (conferences 0 to 509).

2. Because GT boards now have the ability to join multiple networks (using
   for UTIs for RelayNet, the MDRIVER software for GTN, AFSN, etc, GTQWK, and
   TNet 2.1 and my UTIs), support has been added for a "net" indicator on the
   S)elect screen.  This is completly optional, and if not used, the "net"
   indicator will be set to "LO" (for local conference).  To add "net"
   indicators, use this format in the BGQWK.CNF file:

034 | z | Wire Wrap  | RN=D:\MAIL\RNET199
015 | z | GraphicsBB | rn=D:\MAIL\RNET261
037 | Z | Test-1     | D:\MAIL\TEST,$
038 | Z | Test-2     | D:\MAIL\TEST2,^
040 | z | Netmail    | gt=D:\MAIL\NETMAIL,NP
039 | z | Bg Qwk     | gt=D:\MAIL\E02-758,P
041 | z | AnsiArt    | GT=D:\MAIL\E10-037,P
080 | 0 | General    | tx=D:\MAIL\TNET001,P
120 | 0 | Aggies     | tx=D:\MAIL\TNET003,P

   Notice, in this cross section, the indicators before the message
   directory path.  I use "RN" for RelayNet, "GT" for GT, and "TX" for
   TexasNet.  The two letter indicators (they MUST be two and only two
   letters) will be converted to caps.

   In a future beta, I hope to add some additional support for these
   indicators (so that when the S)elect screen is used, the users can
   choose to list all confs, or only those confs in certain networks.

3. There were a few cosmetic changes such as the opening logo.

4. Fixed a major bug in the last beta that caused uploaded messages to be
   messed up.  Several people reported this.  Thanks guys!

5. Support for the AP= command, until further notice, has been removed
   because of lack of interest.  (This used to allow you to set an
   alternate path).  Support for priority conferences has also been
   removed.  They may pop back later, but I am in the process of expanding
   the total number of conferences and have to get some other changes set
   right first.

6. The work directory was not being deleted in the last beta because the
   .PTR file was remaining in the directory.  This has been fixed.

7. The number of characters available for use in the message paths has been
   reduced from 50 to 30 so I have more memory to work with.

BGQWK 1.0 BETA 13  SAT  2 NOV 91
--------------------------------

Before I start ... for the sysops who sent in the registration checks for
BGQWK, you may pick up your BGQWK.KEY files by calling my board and opening
door 4.  The complete process only takes a few minutes...  just enter your
birthdate to confirm your identity and then enter a site line, whatever you
want to put on it (except someone else's name of course, <grin>).

1. THE FORMAT OF THE BGQWK.CNF FILE HAS CHANGED -- nothing to do with the
   conferences themselves, just the configuration info -- no need to yell or
   scream, <grin>.  The CNF file is now "flexible", i.e., you can put any
   information anywhere in the file and BGQWK will pick it up.  You don't
   even have to give BGQWK all the information you gave it before--all
   config info is now optional (but I would HIGHLY recommend to use certain
   fields).  Anyway, here's an example of how it works now:

      id=tranquil          <- board id, defaults to NONAME
      sn=B.J. Guillot      <- sysop name, defaults to SYSOP
      bn=Tranquility Base  <- board name, defaults to No Name
      bc=Houston, Texas    <- board city, defaults to Planet, Earth
      bp=713-893-9124      <- board phone, defaults to 000-000-0000
      up=c:\gt\up          <- upload directory, defaults to default ul dir
      we=c:\qwk\hi.ans     <- welcome file, defaults to GTWELCOM.CBS
      ne=c:\qwk\news.ans   <- news file, defaults to GTBULLET.CBS
      by=c:\qwk\bye.ans    <- bye file, defaults to GTBYE.CBS
      ap=c:\gt             <- alt path, defaults to root directory
      ma=250               <- max msgs per area, defaults to 200
      mp=2500              <- max msgs per packet, defaults to 2000
      ns=04zE              <- net status access levels, defaults none

   Notice, this is all the same info that was in the file before, you just
   have to add the config-id to it so BGQWK knows what is what.  The new
   things are AP, MA, MP and NS.  Previously you could execute BGQWK like:

     bgqwk nlhw f:(c:\gt) 250

   This is no longer possible.  BGQWK now REQUIRES the options and the drive
   letter for the work driectory in order to run.  The (altpath) directory
   can now be specified as AP.  The 250, or max msgs per conf, is now MA.
   Several people went crazy because I made up by own authority NS for the
   GTPASSWD.BBS file in the last beta.  Ok, you guys won!  The NS
   information is now placed in the BGQWK.CNF file under NS, and it's
   optional.  Example to run:

     bgqwk nlhw f:

   Is what is needed to run BGQWK.  Remember the config info can be placed
   anywhere in the CNF file now--it can be split between conferences, put
   at the front, but at the end, in backwards order, no order, etc.  If you
   take a look at the example CNF file I include, you will not notice all
   the config options present--that's because I use the defaults.

2. I believe Russell and I have discovered the file sharing problems BGQWK
   has having with DV'd systems.  BGQWK was opening files in compatibility
   mode rather than share mode <blush> and this was problably the culprit.
   Douglas Pippel and several others reported this bug.

3. If a user attempted to upload a dummy REP packet (a 128-byte packet with
   a REP header and no message), BGQWK would error out.  This has been fixed.

4. If a user attempts to send a message with netmail "dot" commands in it,
   the "." character will be changed to a "*" so the netmail programs don't
   process it.  Now, in order for a user to send "dot" commands, they must
   have SY authority.  It was brought to my attention that users could get
   away with .FRs and .DXs in netmail messages.  This is now fixed.

5. Dan Mancuso reported that the download function left the last MES file
   it processed open until the door was shut.  This has now been fixed.

6. Russell Kroll suggested that the user should be able to abort the
   download process (the packing of messages) by being able to hit ^C, ^K,
   or ESC during the packing.  Done.

7. Several little changes have taken place.  PNT files are now called PTR
   files.  The WELCOME/GOODBYE screen option is now always|never rather than
   updated|never.  Prompts have changed somewhat to allow more commands to
   be displayed on the line.

8. Jerry Hook discovered a bug in the "don't move" feature.  If a user
   entered a public message in a private only base, BGQWK informed the user
   taht the flag was changed to private, but it actually wasn't.  It is now.
   BGQWK was handling the private->public flags okay.

9. The BGQWK.HLP file has been updated.

I hope all this stuff makes everyone happy, ... at least for an hour, <grin>.

---------------truncated to save space