-------------------------------------------------------------------------- Setup hints: BGFAX, US Robotics, and Binkley 2.60 (DOS & OS/2) 03-01-97 B.J. Guillot bgfax@blkbox.com FidoNet 1:106/400 http://www.blkbox.com/~bgfax/ -------------------------------------------------------------------------- YOU MUST BE USING BINKLEY 2.60... DO NOT USE THE 2.59 BETAS OR EARLIER. Here is a clip from the BINKLEY.CFG file... ;****************************************************************** ;* Fax Related Section of Binkley.CFG for a Class 2.0 * ;* US Robotics fax modem; NOT for ZOOM, SUPRA, HAYES, PPI, etc. * ;****************************************************************** PreInit |v``^``ATZ|~ATS0=0+FCLASS=2\.0|~ Init AT+FAA=1;+FLI="713\ 555\ 1212";+FNR=1,1,1,1| PreDial ` Prefix AT+FCLASS=0;DT Answer ATA| DtrHigh ;MailNote ; must be COMMENTED OUT for BGFAX to work!!! ;FaxInDir NOT_USED ; must be COMMENTED OUT for BGFAX to work!!! ;FaxBaud NOT_USED ; useless when used with BGFAX ExtrnMail 123 +FCO Extern spawn ; this causes Bink to spawn EXTMAIL.BAT|CMD ModemFax +FCO ModemIgnore RINGING ModemIgnore RING RESPONSE ModemRinging RING ModemConnect CONNECT ModemIgnore RRING ModemRetry BUSY ModemFailure VOICE ModemFailure ERROR ModemFailure OK ModemFailure NO CARRIER ModemIncoming NO DIAL ModemIgnore DIALING ModemFailure NO ANSWER ModemIgnore DIAL TONE Miscellaneous notes about BINKLEY.CFG... 1. 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 2. 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. 3. 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. 4. 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.BAT|CMD, which will reside in the Binkley directory. EXTMAIL.CMD (If you are using Binkley and BGFAX for OS/2) ~~~~~~~~~~~ @c:\bgfax\bgfax2 /fco:4 c:\bgfax h%3 z EXTMAIL.BAT (If you are using Binkley and BGFAX for DOS) ~~~~~~~~~~~ @c:\bgfax\bgfax /fco:4 c:\bgfax 1 z Miscellaneous notes about EXTMAIL.BAT|CMD... 1. This file contains just the one line. 2. The "h%3" just tells BGFAX to use the com port HANDLE as provided by Binkley during the spawn. OS/2 version. Do not change. 3. The DOS version of BGFAX does not use com port handles, so you must tell it which com port to use (thus, the "1" for COM1). 4. 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. 5. 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 If Binkley/2 is working correctly, your BINKLEY.LOG will show an entry like this... + 18 Apr 00:05:22 BINK begin, BinkleyTerm-OS/2 Ver. 2.60 -IBMC/2 # 18 Apr 00:05:31 BINK Ring # 18 Apr 00:05:38 BINK +Fco : 18 Apr 00:05:39 BINK Spawning external mailer : 18 Apr 00:06:00 BINK Returned from external mailer * 18 Apr 00:06:04 BINK Seconds: 31 Tariff: 0 Fee: 0 System: FAX : 18 Apr 00:06:04 BINK Exit after receiving mail with errorlevel 20 + 18 Apr 00:06:04 BINK end, BinkleyTerm-OS/2 Ver. 2.60 -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 releases control back to Bink. Again, this happens AFTER the BGFAX transfer has already happened.