GPFAX Version 2.21 Release Notes

     In our  efforts to  continually improve  GPFax we have added or changed
     the following since the manual was printed.

     Please note: GPFax efficiently performs detection between FAX  and DATA
     if  supported  by  the  modem.   However, because of slightly different
     methods implemented by different manufacturers this feature can only be
     guaranteed on certain brands of modems.
      

     We thank  you for  your support  in purchasing our products and welcome
     any suggestions you may have for added features  in future  releases of
     GPFax.


     Release Notes: Version 2.21  December 1992

     The following  changes have  been made  since the  release of the  2.01
     version.  These changes are to add some extra features, fix a  few bugs
     and add functions available with the new ROMS from Supra for the V32Bis
     modems (1.2E or greater)

      MINOR CHANGES

     .    More optimisation for Supra 14.4 mode fax capability
     .    More optimisation for adaptive  answering for  Supra V32bis modems
          with new version ROMS.
     .    Hangup codes are now limited to 0-255. Some modems actually return
          hangup values >255 for some reason. Hangup codes  NOW displayed as
          HEX values (as in modem manuals.)
     .    Improved BBS interface (see below)
     .    Added ability to use Users WB colours (see below)
     .    Fixed GPFax/18  font for our Northern European users. Now contains
          the AE character.
     .    FileRequester now has FAXIN/FAXOUT gadget
     .    FAXIFF files now padded to even lengths.
     .    The Busy pointer no longer changes pointer colours.
     .    If 'BUSY' is detected when attempting to dial a number,  GPFax now
          no longer aborts the attempt.  It now retries.
     .    The  method  of  printing  of  faxes  has  been re-written to work
          correctly with postscript page orientated printer drivers (such as
          available in WB2.1 and 3.0)
     .    Changes the  way the parallel port is used to overcome the problem
          of other programs using the port while GPFax is running. 
     .    Changes  to  viewfax  screen.  Now  users  WB2  standard  overscan
          settings



     MAJOR CHANGES

     1.   Modem Initialisation String

     For the Supra version, we have changed the default modem initialisation
     string to 'AT&F2E0' as recommended by  Supra.   You may  change this to
     other settings by changing the Environment. 

     2.    New Printer Driver

     The  Printer  Driver  for  version  2.21 has been rewritten to overcome
     incorrect paging on some software. Paging now works correctly with most
     software  including  ProfessionalPage,  Pagestream, Prowrite, FinalCopy
     etc.

     For Prowrite, in the Printer Setup  Menu  select  the  'no  gap between
     pages' option.

     For  PageStream,  select  the  'Configure Printer' menu and then select
     Preferences.Printer.   Use densities  1-6. Do  not use  density 7. This
     does not page correctly.

     3.   Better Aspect Ratio when Printing Faxes

     The printing  of faxes  code has  been re-written  to overcome problems
     with incorrect aspect ratios on some printers. 

          NOTE: Because printers are normally based  on an  8 inch wide
          page, and  a fax is designed to reproduce an A4 width page of
          210mm or  8.26 inch  wide, some  printers drivers  may not be
          able to  print a  fax at full width. In such cases GPFax will
          auto-scale the width and height fax  to fit  the 8  inch page
          while retaining  the correct aspect. For many printer drivers
          this can be overcome  by setting  the printer  preferences to
          use  DIN  A4  (if  your  driver  supports  this!!)  or a wide
          carriage or WIDE TRACTOR setting.    This  will  not actually
          print off  the edge of the paper but may allow the printer to
          print the full 210mm or 8.26 in wide fax.

     4.   Silent Answer for Supra Modems ONLY

     The 'Silent Answer' capability of the new Supra  ROMs is  now supported
     in the  Supra version  of GPFax.  This may be selected from the Options
     menu. Select either Fax Only, Fax/Data, or 'Silent Answer' mode.  Refer
     to your  instructions from  Supra about how to set up Silent Answer but
     note that Fax/Data detection is not  possible in  'Silent Answer' mode.
     It is a FAX only mode.

     5.   Names of Services

     Many users wanted to see the NAME of the service that was called in the
     logbook and in the scheduler.    This  has  now  been  changed  and the
     logbook and  scheduler now  show NAME of the service if possible. If no
     name is possible then the  number  is  shown.    This  only  applies to
     transmitted faxes.   Incoming  faxes are  reported according  to the ID
     received from the remote system.

     6.   Ring Detection count

     GPFax now supports a variable for number of RINGS before  answering the
     phone. This  is a  new setting in the Environment.  The minimum setting
     is two (2) rings.

     7.   AUTO Detection of modem speed capability

     GPFax now automatically interrogates the modem to determine the maximum
     speed capability  for fax  transmission. For  the Supra  V32 J ROMs and
     other high speed modems this will now be 14,400.  

     It is possible to override this check by setting the  internal MAXSPEED
     variable  in  the  software.    This  may  be  done by either setting a
     tooltype in the GPFax icon to MAXSPEED=<value> or by running GPFax from
     the  cli  with  the  option  -F<value>, where value is 0-5 (2400, 4800,
     7200, 9600, 12000,  14400)
     We do not  recommend  that  this  override  be  used  unless absolutely
     necessary.    In  conjunction  with the modem, GPFax will intelligently
     determine the optimum speed for sending and receiving faxes.

     SPECIAL NOTE: AUTO detection of maximum fax speed is NOT done if either
     (a) GPFax  is run  with no  serial option,  or (b) Modem is not on when
     program starts.  In such cases, the maximum  speed will  be set  to the
     default value of 9600 cps.

     8.   New tooltypes and command line switches

     Icon Position

     This allows  you to set the X and Y coordinates of the application icon
     on the Workbench screen.

          Use tooltypes

                ICON_X=<val> 0-600 and        ICON_Y=<val> 0-250/190

          or from the cli

               -X<val> -Y<val>

     Workbench Colours

     You may override the default colours used by GPFax.  It is not possible
     to set  the colours  directly but  it is  possible to tell GPFax to use
     your standard workbench colours instead of its own.

     This option is mainly for  use  with  greyscale  monitors  such  as the
     Commodore 2024. Set the tooltype of     USEWBCOLOURS = TRUE
     or run GPFax with the CLI option '-w'.


     9.   Phonebook Wildcards.

     The  phonebook  wild  cards  search  may  be  either UNIX style '*?' or
     standard AmigaDos type using '#?'

     10.   New Arexx commands

     After various suggestions from users we have added  several extra AREXX
     commands.  These  are  listed  below.    Most of these new commands are
     designed specifically for use with BBS programs with TrapDoor and Getty
     for Amiga UUCP

     Note1:  ONLY  the  RECEIVENOW  and  FCONRECEIVE  commands automatically
     handle listen/unlisten.  Other commands  do not.  You MUST specifically
     listen  or  unlisten  the  serial  device if required according to your
     needs and that of other  cooperating  software  also  using  the serial
     port. If the serial device is not in the correct state an error will be
     returned. 

     Note2: Some  commands  either  close  the  serial  port  or  perform an
     unlisten.  If this is done, GPFax does not guarantee that the modem has
     been correctly  initialised and  internally flags  this fact.   In such
     cases,  the  next  time  the  modem  attempts to answer a call, it will
     re-initialise the modem with the default initialise string.

     OPENSERIAL

          Opens serial device, sets 19200 baud  and starts  listening to the
     serial port.  Does not initialise modem

     CLOSESERIAL

     Closes the serial device and flags that modem is not initialised. (This
     will cause the modem to be initialised when  doing a  manual receive or
     transmit.)

     INITMODEM

     Sends to  the modem  the init  sequence defined in the Environment plus
     other commands to initialise  the modem  to receive  faxes. Serial port
     MUST be open!

     LISTEN/UNLISTEN

     These  commands  do  ONLY  what  they suggest. Listen will NOT open the
     serial port or initialise the modem.    If  the  serial  port  has been
     closed, listen will return an error.  Unlisten also flags the fact that
     the modem initialisation is no longer valid.

     SCHEDULEFAX <TIME in MINS> <file,file> TO <num,num,..(group)>

     The command is effectively the same as sendfax but has  extra parameter
     of TIME.  The TIME variable is in minutes AHEAD of current time and the
     value must be greater than zero.

     RESETSCHEDULES <TIME mins>

     This command resets ALL the currently scheduled faxes to be sent to the
     current system  time +  TIME   (This command  does not  check status of
     schedules. It resets all schedules irrespective to what the error was.)

     COVERPAGES <ON/OFF>

     Allows you to determine if cover pages are to be sent when using Arexx,
     send or   schedule commands. If a phone number or group number is found
     in phonebook and has an attached cover page, this setting allows you to
     override the default and not send the cover. (Default ON.)


     RECEIVENOW and FCONRECEIVE

     These are  probably the main commands for running GPFax in  conjunction
     with BBS software and external 'trapdoor' style or UUCP/Getty programs.


     When an  external program causes the modem to answer the phone, it must
     determine if the call is fax or data.  The best  method of  detecting a
     fax call is to look for a +FCON command from the modem.  GPFax provides
     two commands to initiate receipt of a fax depending on  exactly how the
     external program works.

     Both commands  effectively perform  the same  operation, however, there
     are some very important differences between FCONRECEIVE and RECEIVENOW.
     FCONRECEIVE is  designed to  be called immediately after the +FCON from
     the modem.  (At this point, the calling program must have the baud rate
     set to  19200 and  must also be in 'unlisten' mode.) GPFax will process
     any handshaking commands while waiting for  the subsequent  OK from the
     modem before initiating the receive. On the other hand, RECEIVENOW does
     not wait for the OK and  is designed  to be  called where  the external
     program has received the OK from the modem AFTER the +FCON. 

          The actual function of the commands are as follows  
       
                Do a default LISTEN if required
                begin received fax and save incoming files
                do UNLISTEN
                returns to calling rexx script


     Creating AREXX Scripts

     Creating  an  AREXX  script  to  run  BBS  and  GPFax together is not a
     difficult problem but several aspects  need  to  be  considered. Before
     writing  the  script  it  is  important  to  clearly  map out the exact
     functions you expect each program to perform.

     With the FCONRECEIVE command, GPFax expects  that the  external program
     will have  sent ATA  (or auto  answer) to  the modem, has swallowed the
     FAX/DATA result to determined if it is a FAX call, then waited  until a
     +FCON response is received.

     Depending on  exactly which  external program you are using, it is best
     if you allow GPFax to  send  the  main  modem  initialisation commands.
     This will  ensure that  the modem  has been correctly set up to receive
     fax or data calls. 
     NOTE:  It  is  important  to  realise  that  once  GPFax  has  done the
     initialisation,  the  modem  should  not  be reset. I.E. Do not send an
     'ATZ' or similar  command, switch  the modem  off, or  have any setting
     that will cause the modem to be reset. 

          A sample setup would be
               run GPFAX with FAX/DATA modem set
               wait for GPFax to startup (e.g. using 'waitforport')
               send it an UNLISTEN
                run BBS and frontend
                 then
                    START
                         wait for serial
                         get RING
                         issue ATA
                         determine FAX or DATA
                         if FAX response received
                              wait for +FCON
                              call GPFAX with FCONRECEIVE
                         goto START

     With both FCONRECEIVE and RECEIVENOW, time delays can be critical.  The
     fax call will not wait for  more  than  about  THREE  SECONDS  (MAX) to
     continue with fax reception.  
      
     Be careful  about the  modem initialisation between Fax and Data calls.
     Under some circumstances, it also may be necessary to re-initialise the
     modem  (using  LISTEN/INITMODEM/UNLISTEN  commands) after receiving the
     call and especially after the external program makes data calls.

     USING GPFAX v2.2 and TRAPDOOR or GETTY
       
     The information supplied  herein  should  be  sufficient  to  get GPFax
     working  with  TrapDoor  v1.80,  TrapDoor  v1.83  and  FaxGETTY.    The
     information should also provide a basis  for development  of scripts to
     work with  other programs  including DLG (with or without TrapDoor) and
     other BBS packages.

     Any people developing scripts which work with GPFax are urged  to place
     their scrips  in the  PUBLIC DOMAIN and send them to GPSoftware so they
     may be included in any new distributions.  GPSoftware can  be contacted
     by the addresses shown at the end of this document.

     Shell Scripts

     All  AmigaDOS  scripts  mentioned  in  this  document MUST have the 'S'
     (script) protection bit set and therefore you should be using  AT LEAST
     AmigaDOS 1.3  SHELL.   As we  cannot test  under every possible machine
     configuration, it is advisable that you use a STANDARD AmigaDOS 1.3 (or
     higher) SHELL.

     ARexx Scripts

     ARexx will  look for  scripts in  the default directory, from where the
     GPFAX has been run, and in the REXX: directory.   It is  advisable that
     all scripts  be located  in GPFAX:  directory and that you CD to GPFAX:
     before executing the program.

     Definitions: Modem Configuration, LISTEN and UNLISTEN

     It is important that  you  understand  your  modem,  it's configuration
     settings and  some things  about handling the serial port on the Amiga.
     If you do not know whether  your modem  supports DTE  baud rate locking
     then you  should read  your modem manual to understand what is meant by
     this term.  Most new high-speed modems support baud rate locking.

     Note: We  use the  term 'baud  rate' to  refer to  the connection speed
     between the  computer (DTE)  and the  modem (DCE).  In other words, the
     speed of the Amiga serial port. It is does not refer to the actual bits
     per second used by the modem when date is being sent or received from a
     remote DCE.  This will vary  between 2400  b.p.s (bits  per second) and
     14,400 b.p.s depending on your modem and the quality of the phone line.

     Baud rate locking

     Baud  rate  locking  means  that  the  communication  speed (DTE speed)
     between the computer and the modem  is  locked  at  a  particular speed
     (normally 19200  for Fax),  regardless of the modem to modem connection
     rate (DCE speed). The modem then buffers the data and  sends it  out at
     the DCE speed.  Usually the DCE speed is less than the DTE speed so the
     modem must control the flow of data from the computer with some form of
     handshaking  to  start  and  stop  the  data flow as required. Normally
     RTS/CTS hardware (Fax CLASS 2) or XON/XOFF (Fax Class 1) handshaking is
     used. 

     LISTEN, UNLISTEN and Shared Serial Ports

     The  Amiga  provides  only  a primitive mechanism for allowing multiple
     programs to access the one  serial  port.    However,  this  works well
     providing all programs observe a few simple rules.

     Several programs  can productively access to the Amiga's serial port at
     once providing they all open the device using the SHARED SERIAL option.
     But  only  one  program  may  effectively control the port at any given
     time. Note however  that  when  two  programs  share  the  serial port,
     neither program  will be able to drop DTR to disconnect the modem while
     the other program still has the serial device open.  If you  cannot use
     the the  '+++ATH' command method, you will have to physically close the
     serial device on both programs to drop DTR. (Don't forget  to reopen it
     afterwards!)

     In  order  to  process  incoming  data  from the modem at high speed, a
     program sends a request to the  serial device  for one  character, then
     goes to  sleep (WAITs)  until notified that the character is available.
     After processing this character, and any other incoming characters, the
     program then sends another request for one character and returns to the
     wait state.  In this state, a program is said to be in 'LISTEN' mode.

     While in LISTEN mode, other programs will not  be able  to successfully
     access the Amiga's serial port nor change the baud rate.
      
     If a  second program  wishes to access the port, the first program must
     be told to cancel its waiting request   and then  not look  at the port
     (UNLISTEN), leaving it free for the use of the second program.

     LISTEN  is  the  GPFax  ARexx  command which tells the program to watch
     (listen to) the serial  port  for  serial  DATA.    As  defined  by the
     standard, GPFax ALWAYS watches for data at 19200 baud. Therefore, it is
     important that when any application tells GPFax to  talk to  the modem,
     it  must  have  the  baud  rate  set  to  19200  baud.  Most FAX modems
     automatically set the speed  to 19200  baud when  they enter  FAX mode.
     TrapDoor and  FaxGETTY both have them modem ready at 19200 baud when it
     comes time for GPFax to take over the connection.


     UNLISTEN is the GPFax ARexx command  where you  and tell  GPFax to stop
     waiting for  serial data.   This  means other  programs can talk to the
     modem while GPFax is running (if in SHARED serial mode)  AFTER you have
     issued the unlisten command.

     Using TRAPDOOR v1.80 and GPFax

     To use  TrapDoor v1.80  (any version  less than  1.83), you need to use
     GPFax to answer the incoming call.   This  is because  TrapDoor version
     below 1.83 cannot answer FAX calls.

     Calls are answered in the following sequence:

          a.   GPFAX answers the call and determines if the call is a FAX or
               DATA connection.

          b.   If the call is a FAX call, GPFAX  processes  the incoming fax
               and returns to wait for the next call.

          c.   If  the  call  is  a  DATA  call, the DataMessage.txt file is
               displayed (if it  exists)  and  then  the  DATACALL.GPF ARexx
               script  is  executed.    That  script  should run trapdoor in
               ANSWER IMMEDIATE mode.

          d.   If the DATA call is a FIDO MAIL call, trapdoor  can handle it
               and then will return


          e.   If the  DATA call is a user for the BBS, then you must set up
               trapdoor to work with your BBS and modem configuration.


     The following configs/scripts should be  used  if  your  modem supports
     BAUD RATE  LOCKING   (eg: Supra,  ZyXEL) and the baud rate used MUST be
     set to 19200.  You should also make  sure that  GPFax is  run in LOCKED
     baud rate  modem if  your modem supports it, and that you interpret the
     result of the BAUDRATE ARexx command correctly.

     GPFax  MUST  be  in  SHARED  (see  Environment)  serial  mode  with the
     following options set:
                  Auto Answer
                  FAX/DATA mode
                  ARexx DATA

     ---------- DATACALL.GPF script starts here -----------
     /*
      * $VER: DataCall.GPF 0.03 (5.11.92) rsc
      * this script will start TRAPDOOR v1.80 or below
      */
     options results
     address rexx_gpfax
     baudrate
     baud = result
     address command 'FIDO:trap/trapdoor' ANSWER IMMEDIATE
     ----------------- script ends here -------------------


     The following  modifications are  required when a non-locking baud rate
     modem is used (eg: Maestro 9600XR  FAX/DATA)   TrapDoor will  require a
     different config  depending on  baud rate used, and the LOCK command in
     the TrapDoor.cfg CANNOT be specified.


     ---------- DATACALL.GPF script starts here -----------
     /*
      * $VER: DataCall.GPF 0.03 (5.11.92) rsc
      * this script will start TRAPDOOR v1.80 or below
      */
     options results
     address rexx_gpfax
     baudrate
     baud = result
     if  (baud = 300) then CONFIG = "mail:TrapDoor300.cfg"
     else if (baud = 1200) then CONFIG = "mail:TrapDoor1200.cfg"
     else if (baud = 2400) then CONFIG = "mail:TrapDoor2400.cfg"
     else if (baud = 4800) then CONFIG = "mail:TrapDoor4800.cfg"
     else if (baud = 7200) then CONFIG = "mail:TrapDoor7200.cfg"
     else if (baud = 9600) then CONFIG = "mail:TrapDoor9600.cfg"
     else if (baud = 19200) then CONFIG = "mail:TrapDoor19200.cfg"
     else say "funny baudrate"
     address command 'trapdoor' 'config' CONFIG  ANSWER IMMEDIATE
     ----------------- script ends here -------------------

     Each of the MAIL:TrapDoor<baud>.cfg  files should  have the appropriate
     BAUD keyword set and any other settings specific to the modem.

     NOTE: The above procedures are NOT recommended.  It is recommended that
     you obtain TRAPDOOR v1.83  and use  it if  you intend  to use  your FAX
     modem with DATA/MAIL calls.



     Using TRAPDOOR V1.83 and GPFax

     Using TrapDoor  v1.83 and  GPFax is quite simple.  All that is required
     are changes to  two  (2)  lines  of  your  TRAPDOOR.CFG  file.    It is
     necessary for  GPFAX to be in SHARED serial mode and already running is
     the UNLISTENED state before TrapDoor is started.  An INIT_FAX script is
     supplied below to do this automatically.

     Some background on how things work:

     TrapDoor  v1.83  has  two  new  commands specifically for use with FAX.
     These commands are FAXSTRING and FAXCOMMAND  and work  in the  same way
     and the BBSCOMMAND does.

     FAXSTRING   should   be   set   to   "+FCON"   and  FAXCOMMAND  set  to
     "MAIL:rec_fax". The REC_FAX script is listed below.

     This will instruct TRAPDOOR to start  the MAIL:rec_fax  script when the
     string +FCON is received from the modem.

     TrapDoor's baud  rate should  be set to 19200, however, for faster DATA
     communications, the BAUD can be set to anything.  If you have problems,
     we advise that BAUD be set to 19200.



     The  MAIL:rec_fax  script  is  shown  below  and is a standard AmigaDOS
     script which should have the 'S' (script) bit set.

     We have presented below, two examples of different  methods in handling
     TrapDoor.

     The following  script uses  the LISTEN/UNLISTEN  commands, and although
     GPFax is UNLISTENED, it still has the serial device open.   Hence, your
     config for Trapdoor would require MODEMHANGUP string to be "~+++~ATH|".

     --------- start of the MAIL:rec_fax script ----------
     rx "address rexx_gpfax fconreceive"
     wait 5
     ;
     ; place other commands in here to automatically VIEW/PRINT/LOG any
     ; activity.
     ;
     ---------- end of the MAIL:rec_fax script -----------

     The INIT_FAX  script is  shown below  and can   be EXECUTEd  or run  if
     the  'S' bit is set.

     -----------------  start of INIT_FAX ----------------
     ;
     ; execute this to start GPFax and trapdoor
     ;
     cd gpfax:
     run gpfax -np -q
     waitforport rexx_gpfax
     rx "address rexx_gpfax unlisten"
     run mail:bin/trapdoor answer
     cd mail:
      -----------------  end of INIT_FAX ------------------


     This second script uses the OPENSERIAL/CLOSE SERIAL commands,  and thus
     will permit Trapdoor to use its "Toggle DTR" option to hang up any data
     orientated calls.

     --------- start of the MAIL:rec_fax script ----------
     rx "address rexx_gpfax openserial"
     rx "address rexx_gpfax fconreceive"
     rx "address rexx_gpfax closeserial"
     wait 5
     ;
     ; place other commands in here to automatically VIEW/PRINT/LOG any
     ; activity.
     ;
     ---------- end of the MAIL:rec_fax script -----------

     The INIT_FAX script is shown below and can  be EXECUTEd  or run  if the
     'S' bit is set.

     -----------------  start of INIT_FAX ----------------
     ;
     ; execute this to start GPFax and trapdoor
     ;
     cd gpfax:
     run gpfax -np -q
     waitforport rexx_gpfax
     rx "address rexx_gpfax closeserial"
     run mail:bin/trapdoor answer
     cd mail:
     -----------------  end of INIT_FAX ------------------


     Using FaxGETTY and GPFax

     Using FaxGETTY and GPFax is equally easy.  All that is required are two
     scripts, an appropriate UULIB:PASSWD file and standard UUCP set-up.

     Some background on how things work:

     FaxGETTY is different from the normal  GETTY because  it watches  for a
     FAX connection.   When  it receives  a FAX connection, it looks for the
     USER FAX in the PASSWD file and then  runs a  script to  start whatever
     you want  to do  to get it going.  This document covers the FAX side of
     GETTY and GPFAX and not how to set up GETTY for general usage.

     You will require a  startup  script  for  which  can  automatically set
     things up  for you and a script which initiates a FAX receive.  The two
     scripts are documented below:

     --------------- startup script  INIT_FAX-----------------
     ; execute this to start GPFax and FaxGETTY
     ;
     cd gpfax:
     run GPFax -np -q  ; start GPFax quietly without the printer driver
     waitforport rexx_gpfax
     rx "address rexx_gpfax unlisten"
     cd uucp:
     run >nil: <nil: uucp:c/getty -Mh -B2400 -d0 -F AT
     ; run >nil: <nil: uucp:c/getty -Mh -B19200 -A -d0 -F AT
     ; use the line above for SUPRA modems (19200 MAY be changed to higher
     ; values for better throughput in DATA mode)
     ;
     ; end
     -------------- end of script ----------------------


     GPFax is started in QUIET mode without the  printer driver,  so it does
     not interfere  with normal system running.  GETTY is then started for a
     Maestro modem which DOES NOT  support  baud  rate  locking.    For more
     information on the GETTY commands, read the FaxGetty.doc and Getty.doc.

     An example of a UULIB:PASSWD entry could be:

          fax,*,0,0,Mr FAX,GPFAX:,uucp:rec_fax

     and  the  rec_fax  script  (have  'S'  [script]  bit  set) could do the
     following:

     -------------- start of uucp:rec_fax script ------------
     rx 'address rexx_gpfax FCONRECEIVE'
     wait 5
     ; do other logging stuff here
     -------------- end if uucp:rec_fax script--------------