home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 3 Comm
/
03-Comm.zip
/
fax067.zip
/
fsend.cfg
< prev
next >
Wrap
Text File
|
1997-02-03
|
15KB
|
376 lines
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; FAXSEND.CFG
;
; Created by Harald Pollack
;
; Configurations for FSEND.EXE Vers. 0.08b, Sept 4, 1994
; Version 0.09b, working in Class 2.0 on Zyxel :-)
; Version 1.01b, some enhancements like retransmission of bad page if
; receiving a ReTrain Negativ (RTN) from remote.
; Each entry must start on FIRST position in line
; Each line can be 255 characters long (incl. CR+LF)
; Character-values may be up to 40 characters
; Only ';' as comment is valid
; Leading blanks in values are ignored, trailing blanks NOT !!!
;
; ComPort for transmission. THIS IS A MUST !!!
ComPort COM2
; New for some reasons in WARP:
;
; The priority of Load TIF and the writing in the debug file is handled
; by priority:
;
; DebugThread's priority is adjusted by ...
; DosSetPriority(PRTYS_THREAD,DebugPriorityType,DebugPriorityValue,0);
; and tif_thread() is adjusted by ...
; DosSetPriority(PRTYS_THREAD,LoadPriorityType,LoadPriorityValue,0);
;
; You can select either IDLE or REGULAR priority for each of the both
; threads AND you can select a value (-31 to +31) with:
; DebugIdlePriority <-31 - +31> selects IDLE for debug writing
; DebugRegularPriority <-31 - +31> selects REGULAR for debug writing
; LoadIdlePriority <-31 - +31> selects IDLE for TIF loading
; LoadRegularPriority <-31 - +31> selects REGULAR for TIF loading
; You MUST use either ...Idle... or ...Regular... (the later entry overwrites
; the former) !!!
; Default (for OS/2 2.1x) is 'DebugIdlePriority 0' and 'LoadIdlePriority 0'
; Recommanded for OS/2 WARP is
DebugIdlePriority 30
LoadIdlePriority 31
; In either case, Load...Priority MUST be greater than Debug...Priority !!!
; The two following values are used in the headerline of each page. LocalID
; is also send to the modem.
LocalID +43 1 70199 3414
LocalName Dr. Harald Pollack
LocalPhone +43-1-70199-3102
; Optinaly, a coverpage is generated.
CoverPage Yes
; Declare a predefined graphic (BMP, black & white)
CoverGraphic d:\tif\cover1.bmp
; FSEND is able to colaborate with FAXWORKS (tm):
;
; Use commandline switch '-#nnnnnn' to select a FXnnnnnn.FAX or
; '-#?' to send last edited fax (FAX.IDX - 1). Both FaxIdx and FaxLog
; MUST be defined to use this feature!
FaxIdx fax.idx
FaxLog fax.log
FaxPath e:\faxworks
; DialRetry 1
; Time to wait between redial in seconds
;DialWait 5
; Some FaxModem need fixed speed for data and fax transmission
; for Class 2 (except Zyxel) you must use 'FaxBaudRate 19200'. Baudrate
; is switched in modem_init(), see below for explanation.
;DataBaudRate 2400
;FaxBaudRate 19200
; FSEND must know, what your modem is able to do. Use a terminalprogram and
; enter: AT+FCLASS=?
; If your modem responses with ERROR, then forget FSEND, else if a value
; of '2' or '2.0' is reported, you can use FSEND. Enter AT+FCLASS=2 (or
; AT+FCLASS=2.0 if possible) and if 'OK' is reported then AT+FDCC=? (or
; AT+FCC=? in Class 2.0). Chose the highest value for first, second, forth and
; fifth value and the lowest for the eighth value. You can simulate it by
; entering AT+FDCC=x,x,x,x,x,x,x,x and receiving 'OK'.
; for highres, 9600 bps max
Capabilities 1,3,0,2,0,0,0,0
; for normal, 14400 bps max
;Capabilities 0,5,0,2,0,0,0,0
; for highres, 14400 max and 2-D Read compression
;Capabilities 1,5,0,2,1,0,0,0
; Bring your modem in a stable and repoduceable state. 'ModemReset' is sent
; as FIRST command after initialising the ComPort (at DataBaudRate).
Reset ATZ
; Finaly, you can make a controlled cleanup with
CleanUp ATZ
; It is a very bad kind of doing, to initialise a modem with a long, cryptic
; string. Store all the values in a profile (with AT&Wn) and recall them with
; the above ATZ. Normaly, the manufacturer of your modems knows it better than
; you, so once AT&F and AT&Wn should be enough for proper working.
;Init AT&FE1M1L2V1X3&D3S0=0S7=100w1
; The above string as that kind of doing you should omit!
; Possibility for sending some extra commands, response is checked for 'OK'
; In Class 2.0 you MUST enter the +FNR=1,1,1,1 or FSEND will NOT work!
Init ATE0m2
Init AT+FBOR=0
;Init AT+FBO=0
;Init AT+FNR=1,1,1,1
; Choose a fax class your modem can handle:
FaxClass 2
;FaxClass 2.0
; Dialprefix, here and only here you should add dial modifier eg. X3 or 0W.
Dial ATDT
; FSEND is able to use either TIFF or plain ASCII (8-Bit) Text to send.
; To distinguish between them, FSEND uses 'TextExtention'. If the file
; (entered with '-i') has TextExtention, than it is handled as ASCII text,
; else a TIFF with Compression=3 is expected.
TextExtention .TXT
; Normally, FSEND creates each time called, a file FSEND.DEB and stores
; all activities in it. You can redefine this filename and prefix it with '+'
; to get a continous logfile. Try '?' as filename :-)
FaxDebug +D:\POINT\LOG\FSEND.LOG
; Some older (or cheaper) faxmodems echo all faxdata they receive from FSEND.
; To suppress the recording of this in the log, use
NoGarbage
; You do not want to have a headerline ?
; NoHeaderLine 1
; You do not want to have a footerline ?
; NoFooterLine 1
; FSEND is able to work 100% in accordance to CCITT T.30 ! In fact, some
; equipment does NOT so. One of the 'unknown facts' is EOM (EndOfMessage)
; handling in faxmodems (Class 2 or Class 2.0) or faxsoftware (Class 1).
; To work-a-round (and make FSEND to be understood by such crippeled products)
; use the keyword 'NoEOM' here or the commandline option '-NOEOM'.
; NoEOM
; To accelerate reading of this file, use ConfigEnd as the absolut last
; keyword here. Comments may follow as much as you like ...
ConfigEnd
; Some explantion for the initialisation of your modem:
; FSEND, in modem_init() does the following
; 1) setting baudrate to <DataBaudrate>
; 2) sending <ModemReset> and waits for <OK>
; 3) sending <ModemInit> and waits for <OK> (up to 10 times)
; 4) sending <ModemAT> plus <ModemFCLASS> and waits for <OK>
; 5) setting baudrate to <FaxBaudrate>
; 6) sending <ModemAT> and waits for <OK>
; 7) sending <ModemAT> plus <ModemFLID> plus '=' plus <LocalID> and waits
; for <OK>
; 8) sending <ModemAT> plus <ModemFCR> plus '=0' and waits for <OK>
; 9) sending <ModemAT> plus <ModemFDCC> plus '=' plus <Capabilities> and
; waits for <OK>
;10) sending 'AT+FCLASS?' and waiting for '2' or '2.0' response. If none of
; them is received, FSEND aborts.
;11) sending <ModemAT> plus <ModemFBUF> plus '?' and stores the first numerical
; value received for elsewhat.
; Each of this steps you can verify in FSEND.DEB or what name you ever gave
; these file.
; At first tries, FSEND aborts often while doing the above. Try ATE1V1&W to
; switch to verbose mode and echo mode.
; FSEND works well in Class 2 with Zyxel and Rockwell chipset based Modems.
; Class 2.0 is implemented yet only by Zyxel and USR. Class 2 works fine,
; Class 2.0 was only tested on Zyxel (ROM 6.12 and 6.13) and works fine too.
; FSEND with USR was not tested by the autor. Users had reported, they can not
; bring USR to work with FSEND in Class 2.0.
; FSEND Class 2.0 is implemented 'from the paper' of the standard.
; Maybe FSEND is wrong.
; Maybe the standard is wrong.
; Maybe manufacturers had not made their homework.
; Finaly, FSEND will never be ported to DOS, but for serious callers, the
; source code is available from the autor. There is NO copyright. You can
; do anything with FSEND or the source code EXCEPT:
; DO NOT RENAME FSEND to elsewhat and distribute it!
; DO NOT ALTER THE SOURCE CODE, COMPILE AND NAME IT "FSEND".
; Please fell free to contact the autor:
; FidoNet 2:313/9.59
; Internet HPOLLACK@gw1-x203.uibk.ac.at
; Error reports without a copy of the FSEND.DEB are SENSELESS.
; Many thanks to Bernhard Seidl, Gerold Pummer and Wolfgang Hoffmann
; for excessive tests of various (beta) versions of FSEND.
; Commandline parameters:
;C:\FSEND /?
;-------------------------------------------------------
;FaxSend/2 for IBM OS/2 32 Bit Version 1.10b Sep 01 1995
;No Rights Reserved Dr.H.Pollack & B.Seidl
;-------------------------------------------------------
;FSEND.EXE -p<phonenumber> -i<filename> [options]
;Options: -i<filename> . file(s) to send [*.TIF, *.BMP or *.TXT]
; -i@<filename> points to a file containing filenames
; -p<number> ... phone number to call
; -#<fax> ...... send fax from faxlog
; -c<filename> . configuration file [FSEND.CFG]
; -d<name> ..... recipient of fax
; -m<comment> .. short message to recipient
; -NoCover ..... no coverpage at all
; -NoEOM ....... special parameter to suppress
; interpage negotiation
; -testdcdoff... do NOT check carrier (DCD)
; -FastLoad .... do NOT read diskdata in IDLETIME
; -r[n] ........ fill order of fax raw file [1]
; -t ........... trace activities on screen
; -x ........... save each page as FXDTnnnn.BMP
; -h|/h|-?|/? .. shows this command summary.
; -i
; You can enter input file as much as you like (and the OS/2 can handle :-).
; Wildcards like '*' and '?' are supported. Filenames without extention are
; treated as '*.TIF'. Single and multi page TIFF is supported. Plain ASCII
; text files are eccepted, as well as OS/2 and WINDOWS Bitmaps (*.BMP) if they
; are well formed and in accordance to WINDOWS SDK or OS/2 redbooks !!!
; Keep in mind, BMP or often 'crippeled' and and they only SEEM to be a bitmap!
; -i@
; This feature gives you the ability to construct a textfile as an input to
; FSEND, which contains all filenames to transmit like with '-i'.
; -p
; You can enter the phone number in one string or splitted by blanks (e.g.
; '-p0321 543 76 98') but do not use dashes or slashes inbetween the number.
; The phone number is put in the headerline of the fax.
; -d
; The same rule as in '-p'. There is no casetranslation.
; -c
; selfexplanating, I hope :-)
; -testdcdoff
; FSEND tests (in a background thread) the existence of Data Carrier. Some
; modems do not handle this signal in the right way, so you can switch off
; this test. An idication is, if an error is reported while 'handshaking sound'
; is produced. FSEND will (should :-) never hang to infinity even if this test
; is disabled, because all is checked by timeout. Checking DCD only speeds up
; the aborting sequence.
; -r[#]
; FSEND can send raw fax data (in the form BinkleyTerm produces PAGEnnnn.FAX),
; but it is strongly recommanded, to DO NOT USE THIS FEATURE because
; unpredictable results are the rule :-). This switch is only for testing.
; -t
; All informations which are written to FSEND.DEB is copied to the screen.
; Senseful while testing, but timeconsuming.
; -NoEOM
; It seems (to me), creators of faxmodems or faxsoftware cannot READ the
; appropriate standards (like CCITT T.30 or EIA/TIA-592) in order to well
; implimate the neccessary protocols in their products. The well defined
; signal EOM (EndOfMessage = multi documents in ONE faxsession) is missed in
; a lot of products. Therefore, you can 'switch off the brain' of FSEND and
; let it act in a more simple way ...
; For clearnes:
; In a faxsession (one call) you can transmit any number of pages. If ALL pages
; have the same resolution and are of the same kind of contents (text or
; black & white graphics or even dithered grayscale images) you can transmit
; them in ONE document. If contents changes (some pages are text, some are
; grayscale images and others are b/w images) you can split your session into
; more documents and use dedicated session parameters for each type of image:
; for text, 'normal' resolution and 2-D Read compression, for dithered
; grayscale images 'fine' resolution and 1-D Huffman compression or for simple
; b/w images 'fine' resolution and 2-D Read compression. This changes are
; signaled by an EOM which forces the receiver to change its capabilities.
; This method yields in more efficient transmission and SHORTER connect times.
; By this methode you can save MORE money than by using higher transmission
; speed !!!!
; -x
; For checking the validy of your source (TIF or TXT or RAW). A file
; FXDTnnnn.BMP is stored for each page. The BMP is inverse (last scanline
; first). This switch should be used only to test pagegeneration.
; Finaly:
; There is, in fact, no purpose, why FSEND should realy work. The Class 2
; fax communication rules (right, there is NO STANDARD) are crippled and each
; manufactuerer of faxmodem uses its own rules. Commercial faxprograms works
; fine with a great number of modems, but in fact, they tread each modem in a
; certain manner. It can not be the result of a free available faxprogram
; to work with each and every modem on the market. But it works with a lot
; of modems, more then expected :-).
; Class 2.0 is an adopted and recommanded standard, but at the time, FSEND
; was written, only two modems (Zyxel and USR) was available with this class.
; Hint (in case of errors :-)
; 1) You are misinterpreting this document
; 2) FSEND could not interpret some lines, because you had mixed up Class 2
; and Class 2.0 commands.
; 3) FSEND could not handle your TIF.
; 4) Your modem is misinterpreting commands from FSEND (the normal case :-)
; 5) Public telephone lines were NOT build for fax. Each errorfree page
; should be treaded as a surprise.
; 6) Do NOT try to transmit at high speeds. Faxmachines normally sends with
; 4800 bps or less!
; 7) Your preferred faxprogram works well, FSEND not. Well that's a fact.
;ErrorLevels returned by FSEND.EXE:
; ErrorLevel 1 ..... falscher Kommandozeilenparameter
; ErrorLevel 2 ..... keine Telephonnummer
; ErrorLevel 3 ..... keine oder falsche Konfigurationsdatei
; ErrorLevel 10 .... UserExit (exit/retry or ESC)
; ErrorLevel 100 ... DebugThreadError
; ErrorLevel 101 ... TIFFThreadError
; ErrorLevel 102 ... HUFFThreadError
; ErrorLevel 103 ... ComInThreadError
; ErrorLevel 104 ... TimeThreadError
; ErrorLevel 251 ... Abbruch nach verbindungsaufbau
; ErrorLevel 253 ... ModemError
; ErrorLevel 254 ... ComPortError
; ErrorLevel 255 ... Speicher nicht ausreichend