BGFAX 1.06  TUE 14 SEP 93
-------------------------

Changes between BGFAX 1.0 Beta 5 and BGFAX 1.06 ...

1. People with EXAR based fax modems are having problems sending faxes.
   The EXAR, at various points, spits out the response "CED".  When dialing
   out, BGFAX would see the "CED" response and think it was some kind of error
   (such NO DIALTONE, BUSY, etc.)  Now, BGFAX ignores the "CED" response.

2. Attempted to add support for the new USR Class 2.0 Courier faxmodems that
   should begin shipping on or about September 20.  At present, I have not
   been able to get in contact with anyone that has one of these modems
   readily available for testing, so I have NO IDEA if it will work with
   them or not.  I also heard that the NetComm modems in OZ may use Class
   2.0 already?  If so, I'd appreiciate a looksee from a NetComm owner.

3. New things in the BGFAX.CNF file for frontend, /INIT, and /SEND people:

   tc=ATHMH1
   ; tc ... string bgfax sends to modem to terminate communications
   sw=10
   ; sw ... seconds to wait before redialing when sending faxes
   ky=P,170
   ; ky ... alt-key, errorlevel to exit on when waiting for calls

   Also, make sure your ds= entry is set to ds=ATDT *instead of*
   ds=AT+FCLASS=2;DT as was included in the BGFAX.CNF on Beta 5.  Because
   of the changes done for Class 2.0 support, any +FCLASS entry you set in
   the ds= entry will make BGFAX fail.  It will handle the FCLASS itself.

4. Added optional parameter when sending faxes.  Normally to send you do it
   like so:

        BGFAX /SEND C:\BGFAX\FAX0001.ZFX 893-9124

   You can still do that, or, you can also tell BGFAX to force the maximum
   fax rate down to a certain speed like so:

        BGFAX /SEND:7200 C:\BGFAX\FAX0001.ZFX 893-9124

   Valid rates are 2400, 4800, 7200, 9600, 12000, and 14400.  When you use
   the rate option on the /SEND parameter BGFAX will *NOT* check your modem
   capabilties, so it will assume you know what your doing.  (For example,
   telling a faxmodem with a maxmium rate of 9600 to fax at 12000 or 14400
   may yield unpredictable results.)

5. In /SEND mode, if a fax is successfully transmitted, BGFAX will now exit
   with an errorlevel of 5 instead of no errorlevel.  (It will continue to
   exit with an errorlevel of 1 if transmission is unsuccessful.)  Also,
   BGFAX will now reserve all single digit errorlevels for future use.  So
   make sure that if you use any events in front end mode that the
   errorlevel number is greater than 9.

6. The way the DOPRINT.BAT is handled has changed again.  Here is a sample:

       CALL C:\BGFAX\EXEPRINT.BAT C:\BGFAX\FAX0158.ZFX
       CALL C:\BGFAX\EXEPRINT.BAT C:\BGFAX\FAX0159.ZFX
       CALL C:\BGFAX\EXEPRINT.BAT C:\BGFAX\FAX0160.ZFX

   As you can see, every time a fax is received, the DOPRINT.BAT file is
   appended.  Remember to delete the DOPRINT.BAT file after you process it.

7. BGFAX was incorrectly reporting "Finished" on all documents in the
   FAXIN.LOG file whether all pages were received or not.  Fixed.

8. For BGFAX frontend users ... When BGFAX goes to its waiting for event
   mode, it will now busy out the telephone line instead of letting the line
   ring as it did before.

9. When I fixed the Beta 4 EOL bug, I introduced a new bug.  (These EOL
   things aren't really bugs, just logic errors.)  This version should have a
   perfect EOL determination engine.  (i.e., to determine whether the
   two-to-three byte sequence is an End-Of-scan-Line marker.)