BGFAX 1.10  MON  4 JAN 94
-------------------------

The expiration date has been changed to March 31, 1994.  (BGFAX 1.08
expired on December 31, 1993.)

1. Added /OU command line parameter.  This indicates you are using an old
   USR modem (i.e., 09/20/93 supervisor date).  /SEND mode does not work
   with the /OU command line parameter.  (I had quite a few people mad that
   I took 09/20 support out of BGFAX 1.09.  I didn't think anyone was
   actually using it with the HST adaptive answering bug in the firmware.)

2. Russell Kroll at 1:128/152 write a small utility that he has authorized
   me to include in BGFAX archive.  This utility (NEWFAX.EXE) will put a
   fax alert message on your screen whenever there is a new incoming fax
   that you have not yet processed.  If you wish to do this, you must put
   NEWFAX.EXE in your AUTOEXEC.BAT file and include the /NF command line
   parameter on BGFAX like so:

       BGFAX /FCO C:\BGFAX 1 Z /50 /NF

   So how's this work?  NEWFAX.EXE is a TSR program (uses about 6K).
   When BGFAX receives a fax (with the /NF parameter), it will execute the
   following lines of code:

      var
        regs : registers;
      begin
        writeln('Talking to RKWARE "NEWFAX" interrupt.');
        regs.ah := 30; { rk-function }
        regs.al := 21; { rk-sub function }
        regs.bl := 95; { rk-"FAX" attribute, white on purple }
        intr($55, regs); { rk-tsr }
      end;

   When you want to turn off the "FAX" alert message, you need to run the
   included "FAXOFF.COM" file.  It basically issues the same code above
   except that "regs.al := 22" instead of 21.  (Go into DEBUG and do an
   unassemble on the .COM file to see exactly how to turn it off.)

3. Better Caller ID support for Supra Fax modem in BGFAX /HOST mode.

BY THE WAY ... I've finally taken a look at Binkley 2.59.  In my opinion,
it is taking much too much time to exit upon receipt of the fax string.
For Rockwell modems (like the Supra) that report "FAX" it should be plenty
of time, but for other modems like the PPI and USR that don't report the
"FAX" pre-result code, it may be pushing the timing too tight.  I did get
Binkley 2.59 to work using the BGFAX /FCOS option on my USR.  (The /FCOS
means use Class 2.0 on a slow machine, while I use just /FCO with FD 2.11
which seems to always catch the "OK" message from the modem when it exits.)

I am running a 386DX40 with 4 megs of RAM (1.5 meg disk cache), DOS 6.2.
Here are some log results from Binkley and FD 2.11 that may be useful to
those who are close to Binkley development:

= 11:35:16  RING    { these are clips of the FD.LOG from FD 2.11 }
= 11:35:23  +FCO
- 11:35:23  Exiting with user defined errorlevel: 255

= 11:26:44  RING
= 11:26:51  +FCO
- 11:26:51  Exiting with user defined errorlevel: 255

# 04 Jan 12:10:25 BINK Ring
# 04 Jan 12:10:31 BINK +Fco
: 04 Jan 12:10:33 BINK Exiting to external mailer with Errorlevel 255

# 04 Jan 12:08:53 BINK Ring
# 04 Jan 12:09:00 BINK +Fco
: 04 Jan 12:09:02 BINK Exiting to external mailer with Errorlevel 255

Am I doing something wrong?  Why is Binkley taking two seconds to exit ??