BGFAX 1.09  WED 22 DEC 93
-------------------------

ATTN: Gary Jipp         I don't know your mailing address!
ATTN: Georges Bourne    I don't know your mailing address!
ATTN: Cliff Reid        The post office didn't like your address!
ATTN: Michael Kramm     The post office didn't like your address!

:::::: NEW STUFF ::::::

0. If you DON'T own a USR modem, go to #2 ...

   IF YOU PLAN ON USING BGFAX 1.09 WITH A USR MODEM, YOU MUST BE USING THE
   BETA FIRMWARE (12/08/93 SUPERVISOR DATE)!  If you are using the 09/20/93
   Supervisor date, STAY WITH BGFAX 1.08 until the new firmware is publicly
   released.  There were many minor changes (bug fixes, improvements, etc.)
   since the 09/20 date that make a big enough difference so that this
   version will not work on the non-Beta models.

   Now, anyone want to take a guess on how many netmail messages or voice
   calls I get asking why people are getting unreadable faxes with BGFAX
   1.09 and their 09/20 USR modems??  <grin>.

   12/08 USR users: Note that you should be using +FNR=1,1,1 instead of
   +FNR=1,1 which I was previously saying to use.  (The extra one will
   allow for the USR modem to report the inbound fax identity.  I'm don't
   think this works in the 09/20 models.)

   Also, note that BGFAX no longer shifts to 19200 when receiving a fax in
   Class 2.0 mode.  EXCEPTION: If you are locked at 38400, it WILL shift to
   19200 because of a small bug in the 12/08 firmware.  (Remember that in
   the 09/20 firmware, I believe the shift had to happen.  So, again,
   another reason why BGFAX 1.09 won't work with 09/20 models.)

   Another note, in the 12/08 firmware, the fax is received in DIRECT bit
   order, not REVERSED bit order (the case in 09/20).  Direct bit order is
   the order that the ZyXEL receives faxes into.  Reversed bit order is the
   order that most draft-based Class 2 modems receive into.  (This is the
   reason some USR beta testers experienced "unreadable faxes" when they
   were using BGFAX 1.08).

1. BGFAX now adds Class 2.0 /SEND mode.  AGAIN YOU MUST BE USING THE 12/08
   BETA FIRMWARE TO TRY THIS OPTION!  IF YOU ARE USING THE 09/20/93 MODEL,
   YOU MUST BE BGFAX 1.08 (NO /SEND MODE).

2. Attempted to address problems people have reported with BGFAX and
   Desqview.  Previous versions of BGFAX were giving ticks away to DV while
   receiving the fax.  This is no longer done.  Now, BGFAX only gives away
   ticks when in /HOST mode waiting for calls.  (It will also do an Int28h
   while waiting for calls as well, in case your running /HOST mode under
   an OS/2 DOS box.)

3. BGFAX will now not allow dialing of any number (in send mode) that
   starts as "911".  BGFAX will just pretend the modem is generating a
   "BLACKLISTED" response code.

   BGFAX (send mode) will now exit with an errorlevel of 7 on black listed
   numbers.  (This should never happen in the United States with the
   exception of the "911" number that is internally blacklisted by BGFAX.)

4. BGFAX, when trying to send an outgoing fax, would not count "failed"
   fax calls as "failed" if the connect had made it past the "+FCON" state.
   Now, it should correctly incorrect the number of failed connects, thus, no
   longer getting stuck in a loop calling some poor fax machine.

5. Now will support 43/50 line EGA/VGA text mode, by adding a /50 to the
   BGFAX command line, i.e.:

       BGFAX /FAX C:\BGFAX 1 Z /50

6. If you don't like to use environment variables, you can now specify the
   pathname to the BGFAX.CNF file by using the "$" modifier.  ex:

   BGFAX /HOST /50 $C:\BATMAN\ROBIN.CNF
   BGFAX /SEND C:\BGFAX\FAX0001.ZFX 893-9124 $C:\BATMAN\BATGIRL.CNF

   The "$" modifer must be the last thing on the command line.  Instead of
   looking for a BGFAX.CNF file as specified by the BGFAX environment
   variable, this will cause BGFAX to look for a "ROBIN.CNF" (in host mode)
   or "BATGIRL.CNF" if sending.

   The "$" modifer has NO EFFECT on rear end mode operation.