--------------------------------------------------------------------------
Setup hints for BGFAX with US Robotics V.34 modem and Binkley/2   12-13-95
B.J. Guillot
FidoNet 1:106/400                         InterNet: bjg90783@jetson.uh.edu
--------------------------------------------------------------------------

NOTE: THIS SETUP FILE IS FOR THE *OS/2* VERSION OF BINKLEY

The following is the important parts of the BINKLEY.CFG file...

Port       1
Baud       115200             ; useless when used with SIO locked port
AutoBaud                      ; useless when used with SIO locked port
DtrHigh                       ; see notes
Carrier    80                 ; my guess is that this is not used in SIO
PreInit    |v``^``ATZ|~AT+FCLASS=2\.0|~
Init       AT+FAA=1;+FLI="713\ 555\ 1212";+FNR=1,1,1,1|
PreDial    `
Prefix     AT+FCLASS=0;DT
Answer     ATA|
;FaxInDir  NOT_USED           ; must be COMMENTED OUT for BGFAX to work!!!
;ModemFax  NOT_USED           ; comment out...useless when used with BGFAX
;FaxBaud   NOT_USED           ; comment out...useless when used with BGFAX
ExtrnMail  123 +FCO
Extern     spawn

Miscellaneous notes about BINKLEY.CFG...

  1. I am NOT using any of those "ModemIgnore", "ModemFailure", etc.
  2. I did NOT make any modifications to the BINKLEY.EVT file
  3. The "123" number I choose in the "ExtrnMail" verb above is just a
     dummy number.  Since we are spawning to EXTMAIL.CMD, the number
     itself does not make any difference
  4. The "\" character used in the PreInit and Init strings allow
     Binkley to "escape" the following character, e.g., \. sends a
     period.  If we did not put a "\.", Binkley would convert the
     period to a comma, and we do not want that.
  5. The dial Prefix "AT+FCLASS=0;DT" instead of just "ATDT" is to make
     sure the modem is in data mode (+FCLASS=0) when making outgoing
     calls.
  6. Regarding the "DtrHigh"... When I first put this file together, I
     could not get fax to work without this verb set.  Bob Juge said
     it was not necessary, so I tried it again, and now it works without
     the verb being set.  I do not know why I could not get it working
     without it originally.
  7. It is recommended that you use SIO's PMLM (Poor Man Line Monitor)
     to verify that Binkley is correctly initializing the modem when
     it first starts.  Binkley will NOT report modem initialization
     errors and this makes finding errors almost impossible.

It is NORMAL to see the ARQ/FAX light blink when Binkley is running when
using this configuration.  If it does NOT blink, something is wrong.

The other important file we must create is EXTMAIL.CMD, which will reside
in the Binkley directory.

EXTMAIL.CMD
~~~~~~~~~~~
@c:\bgfax\bgfax2 /fco:4 c:\bgfax h%3 z
        *** or ***
@c:\bgfax\bgfax2 /fco:4 c:\faxworks h%3 f

Miscellaneous notes about EXTMAIL.CMD...

  1. This file contains just the one line.
  2. The first one makes BGFAX save faxes in ZyXEL's ZFAX format ("z")
  3. The second one makes BGFAX save faxes in Faxwork's format ("f")
     Faxworks is the fax utility that comes with OS/2 Warp's bonus pack.
  4. The "h%3" just tells BGFAX to use the com port HANDLE as provided
     by Binkley during the spawn.  DON'T CHANGE IT.
  5. Since we are using a USR (Class 2.0) modem, we do not have to worry
     about all that port lock-unlock garbage.  You should NOT need to use
     the SU utility for anything.
  6. You might have to make changes to the "/fco:4" parameter depending upon
     how fast or slow your machine is.  The /fco:4 requires a pretty fast
     machine (my 486dx4/100 seems to work okay with it).  On slower machines,
     you might want to try a /fco:0 or /fco:2

Just so that we are on the same wave length, I tested this using...
BT32.EXE, 328512 bytes, dated 2-22-95

If Binkley/2 is working correctly, your BINKLEY.LOG will show an entry
like this...

+ 13 Dec 00:05:22 BINK begin, BinkleyTerm-OS/2 Ver. 2.59 -IBMC/2
# 13 Dec 00:05:31 BINK Ring
# 13 Dec 00:05:38 BINK +Fco
: 13 Dec 00:05:39 BINK Spawning external mailer
: 13 Dec 00:06:00 BINK Returned from external mailer
* 13 Dec 00:06:04 BINK Seconds: 31  Tariff: 0  Fee: 0  System: FAX
: 13 Dec 00:06:04 BINK Exit after receiving mail with errorlevel 20
+ 13 Dec 00:06:04 BINK end, BinkleyTerm-OS/2 Ver. 2.59 -IBMC/2

Notice that after the fax is received, Binkley will go ahead and exit
with the errorlevel defined by E2= in the BINKLEY.EVT file after BGFAX/2
releases control back to Bink.  Again, this happens AFTER the BGFAX
transfer has already happened.

And the BGFAX.LOG should look something like this...

  12-13-95  150d/2  C:\BGFAX\BGFAX2.EXE /fco:4 c:\bgfax h3 z
00:05:40  Port H3, Initial DTE 115200
00:05:40  f=[+FTI:"        713 893 9124"]
00:05:40  Remote Identity [713 893 9124]
00:05:40  f=[+FCS:0,3,0,2,0,0,0,0]
00:05:40  c2dcsf [0,3,0,2,0,0,0,0] Low Res, 9600, 1D-MH, 0 ms/sl
00:05:40  f=[OK]
00:05:40  ->[AT+FDR]
00:05:40  Sending +FDR
00:05:40  f=[AT+FDR]
00:05:42  f=[+FCS:0,3,0,2,0,0,0,0]
00:05:42  c2dcsf [0,3,0,2,0,0,0,0] Low Res, 9600, 1D-MH, 0 ms/sl
00:05:44  f=[CONNECT]
00:05:51  page [#1]  size [7815]  cps [1200]  lines [399]
00:05:51  Extra Bytes; BOP=0, EOP=85
00:05:51  f=[+FPS:1,404,0,0,0]
00:05:51  Page transfer status [+FPS:1,404,0,0,0]
00:05:52  f=[+FET:2]
00:05:52  f=[OK]
00:05:52  ->[AT+FDR]
00:05:52  Sending +FDR
00:05:52  f=[AT+FDR]
00:05:55  f=[+FHS:00]
00:05:55  call termination status code [00]
00:05:55  Successful fax reception
00:05:55  All pages received
00:05:55  Fax saved [C:\BGFAX\FAX1167.FAX]
00:05:55  size [7831]  pages [1]  lines [399]  elapsed time [00:15]
00:05:55  Successful fax reception
00:05:58  a=[OK]
00:05:59  ->[ATH0]
00:05:59  i=[ATH0]
00:05:59  i=[OK]
00:05:59  ->[AT+FCLASS=0]
00:05:59  i=[AT+FCLASS=0]
00:05:59  i=[OK]
00:06:00  ->[ATZ]
00:06:00  i=[ATZ]
00:06:00  i=[OK]
00:06:00  Shutdown

Regards,
B.J. Guillot
bgfax author


