Beijing Paradise BBS Backup

home *** CD-ROM | disk | FTP | other *** search

/ Beijing Paradise BBS Backup / PARADISE.ISO / software / BBSDOORW / FONDIR59.ZIP / FONDIR.DOC < prev next >

Wrap

Text File | 1992-01-18 | 70.1 KB | 1,727 lines

╔═══════════════════════════════════════════════════════════════════════╗ ║ ║ ║ ╔═══ ╔══╗ ╔╗ ╗ ╔══╗ ═╦═ ╔══╗ User's Guide ║ ║ ╠═══ ║ ║ ║╚╗ ║ ║ ╚╗ ║ ║ ╚╗ to Operation ║ ║ ║ ║ ║ ║ ╚╗║ ║ ║ ║ ╠═╦═╝ ║ ║ ╚ ╚══╝ ╚ ╚╝ ╚═══╝ ═╩═ ╚ ╚══ ║ ║ ║ ║ ║ ║ FONDIR - BBS Text File to Phone Directory Translate Utility ║ ║ Copyright (C) 1988-1991 Henry C. Clark, All rights reserved. ║ ║ ║ ╚═══════════════════════════════════════════════════════════════════════╝ Software Mechanics P.O. Box 832052 Richardson, TX 75083 214-881-2627 12/24/96/14400 bps 24hr FidoNet 1:124/6119 'Phone Dear' is not the type of program you run everyday, but it will save you countless hours of manual data entry, and help open the door to the world of electronic communications for you. ╔═══════════════════════════════════════════════════════════════════════╗ ║ What is FONDIR ║ ╚═══════════════════════════════════════════════════════════════════════╝ FONDIR reads from a list of phone numbers, like a BBS list, and creates a communications program dialing directory. It's very fast, and it does a bundle of translations, such as : - supports 20 comm programs - long distance, local, metro EMS dial code conversions - modem speed adjustment - transfer protocol, terminal emulation, script support - import from and export to almost any BBS list FONDIR is distributed as Shareware, you get to try it before you are required to pay a license fee. ╔═══════════════════════════════════════════════════════════════════════╗ ║ WHATS NEW ║ ╚═══════════════════════════════════════════════════════════════════════╝ FONDIR Version 5.9 implements support for Qmodem 5 and K9X 8.8. Also tested, but unchanged were Telemate 3.01 and Telix 3.15. A bug was fixed in certain situations of metro number translation. The next release of FONDIR, version 6, will most likely change all the program type identifiers ( the /o: option ) to a three character identifier. Watch for details. Enjoy. ╔═══════════════════════════════════════════════════════════════════════╗ ║ TABLE OF CONTENTS FONDIR Version 5.9 ║ ╚═══════════════════════════════════════════════════════════════════════╝ Chap. 1 -- FONDIR ARCHIVE. Installation Overview History Chap. 2 -- HOW TO IMPORT A BBS LIST TO YOUR PROGRAM. Quick Start Section Fondir Uses Default Directory Name Fondir Renames Existing Directory File Chap. 3 -- HOW TO EXPORT FROM YOUR PROGRAM TO A BBS LIST. Fondir Appends To Existing BBS List Chap. 4 -- ONLINE HELP. Chap. 5 -- THE COMMAND LINE OPTIONS. Comm Program type ( /o: option ) Assume Protocol ( /p: option ) Keep Date ( /k option ) Local Area Code ( /l: option ) Prefix Phone Number ( /a: option ) Metro Number ( /d: option ) Format Specification Key ( /c option ) Modem Speed ( /m: and /b: options ) Export ( /x option ) Support file path ( /s: option ) Filter mask ( /f: option ) Chap. 6 -- FONDIR DOS COMMAND SYNTAX EXAMPLES. Transform Example Error Checking of Input ( semantic ) Error on Input ( logical ) Chap. 7 -- BBS LIST FORMAT SPECIFICATIONS. Format Specification Coding Format Specifier Stacking Format First Word Length Format Header Specification Comm Program Field Support Chap. 8 -- BBS LIST CONTENTS. Protocol Field Format The Bps Modem Rate Modem Type Parity Indicator File Transfer Protocol Type Terminal Emulator Mode Codes Examples of BBS Lists Chap. 9 -- PROGRAM SWITCHES AND DEFAULTS. Comm Program Type Codes Speed Code Parameters Warnings and Other Notes Chap. 10 -- SHAREWARE LICENSE REGISTRATION. Mail-in License Registration Form Chap. 11 -- LICENSE AGREEMENT. The Terms of The Agreement Note from the Author ╔═══════════════════════════════════════════════════════════════════════╗ ║ 1 -- FONDIR ARCHIVE ║ ╚═══════════════════════════════════════════════════════════════════════╝ FONDIR is shipped in an archive file, FONDIRxx.ZIP. The 'xx' is the version number. The archive file should contain the following files : FONDIR.EXE - 8088 compatible version, FONDIR.DOC - this document file you're reading now, FONERR.DOC - list of displayed output from FONDIR operations meaning and possible solutions to problems FONMAN.EXE - an interactive approach to FONDIR METRO.214 - sample DFW 214 metro exchange list, LDAREA.214 - sample Dallas 214 long distance exchange list, METRO.817 - sample DFW 817 metro exchange list, HCC.LST - sample empty BBS list with format line use with conversions COMCOL.EXE - program to convert comma separated files to the columnar format used by FONDIR, COMCOL.DOC - document for that program. ┌───────────────────────────────────────────────────────────────────────┐ │ OVERVIEW │ └───────────────────────────────────────────────────────────────────────┘ FONDIR will convert a text list of BBS phone numbers, names and other information into a file which can be used by your Comm Program. That bears repeating : FONDIR will convert a text list of BBS phone numbers, names and other information into a file which can be used by your Comm Program. You may have to ADD CONTROL CODES TO THE TEXT LIST to show FONDIR where the information is. The control codes are called the Format Specification Key in this documentation. FONDIR can also convert back to a text list format from your Comm Program phone directory file. BBS List -> FONDIR Import -> Comm Program directory file Comm Program directory file -> FONDIR Export -> BBS List You can use this two step processes to convert from one comm program to another. COMCOL will convert a text file with comma separated fields to a vertical column field text file. There is a separate document covering that program. FONDIR likes columns of data. ┌───────────────────────────────────────────────────────────────────────┐ │ INSTALLATION │ └───────────────────────────────────────────────────────────────────────┘ FONDIR is short for Phone Directory. Un-zip the FONDIRxx.ZIP file and either : a.) keep the .exe program and exchange lists with your BBS list files, or b.) keep the .exe program and exchange lists with your Comm Program files. FONDIR will work from a pathed sub-directory. See the section on Support file path for information regarding the specification of subdirectories for the different files FONDIR uses. No, FONDIR is not crippled or copy protected or any of that. ┌───────────────────────────────────────────────────────────────────────┐ │ HISTORY │ └───────────────────────────────────────────────────────────────────────┘ FONDIR, Version 5.9 is the result of continual upgrades, including : as BF.EXE ( Boyan Phone, the original Procomm beater ! ) V 1.0a initial release, options h,s,n,p,b,m,d, CARR to BOYAN V 1.1a correct 9600 bps value for BOYAN as XLATE.EXE ( Translate for Carr/Farmer BBS list format ) V 2.0a add procomm 2.4.2, procomm plus, qmodem, gt-powercomm, telix V 3.0b corrected gt-power headers, added options x, k V 3.1b on /b set speed option, move speed text into name area at end V 3.2 correct end of gt file handling, pibterm support ( /o:I ) V 3.3 correct less than 8 char phone number length V 3.4 new BBS list system name formats as FONDIR.EXE ( "Phone Dear" ) V 4.0a any list using format specification, /l, /a area code options V 4.1a gt v.14, format codes for elapse, upload, download V 4.2 telix 3, pibterm 4.1 V 4.3a metro number support V 4.4 Boyan 4 support, any two metro areas, Qmodem 4.0 support V 4.5 gt 1500, area headers, stacked format fields V 4.6 telemate 1.10 V 4.7 telemate memo & passwords, blank field bug fix, Zmodem default V 4.8 telix export bug fix, /x:dirfile name option V 4.9 Qmodem index number bug fix V 5.0 PC-Talk4, Rcomm, K9-Express support, 80 exchange tables V 5.1 Mirror 3 support V 5.2 telemate 2.0, PC Anywhere 3.11, Carbon Copy Plus 4.01, |g logfile key, |i port key V 5.3 gt-15.50, MSC 6.0, remove 's' functions, first word on file names V 5.4 ADialer 2.0, remove duplex, fix telemate speed code V 5.5 Commo 4.3, Qmodem 4.2, fix count truncate bugs V 5.6 Unicom 2.0, Procomm + 2.0, test GT 16 V 5.7 Unicom 3.0, Commo 5, Boyan 5 tests, Qmodem 4.3 tests, /s: support file path parameter V 5.8 Ultiterm 2.0, GT 17.00, Pilot 2.0, /f: filter, |K mask field V 5.9 qm 5, k9x88, telix 3.15, telemate 3.01, fix bug in metro logic. ╔═══════════════════════════════════════════════════════════════════════╗ ║ 2 -- HOW TO IMPORT A BBS LIST TO YOUR PROGRAM ║ ╚═══════════════════════════════════════════════════════════════════════╝ ┌───────────────────────────────────────────────────────────────────────┐ │ QUICK START SECTION │ └───────────────────────────────────────────────────────────────────────┘ Most BBS lists are distributed in text file format. The list entries are arranged 'one BBS system per line of text', and the data for each BBS is arranged in columnar format. FONDIR will convert a BBS list text file to the binary file that your Comm Program uses in it's dialing directory. For example, let's suppose you have a BBS list file, and each line of data looks something like this : 03/24 MY BBS OPUS 214-881-2627 #Z Henry Clark 03/24 Joe's BBS OPUS 214-555-1234 #Z Joe Modem 03/24 RBBS Central RBBS 900-555-0000 #Y Huck Finn You need to add a set of codes to the list file so that FONDIR knows where the information about each BBS system is : |d5 |n20 |f4 |#12 |p2 |i11 03/24 MY BBS OPUS 214-881-2627 #Z Henry Clark 03/24 Joe's BBS OPUS 214-555-1234 #Z Joe Modem 03/24 RBBS Central RBBS 900-555-0000 #Y Huck Finn The codes ( for Format Specification ) I have used include the date last called ( |d ), the BBS system name ( |n ), a Script File name ( |f ), the phone number ( |# ) and some protocol codes ( |p ) and an information field ( |i ). The important field is the phone number ( |# ), which must exist, and the phone numbers must begin with a digit ( 0 through 9 ). After each code letter is the width of each columnar field. Given the above two lines in a file called BBS.LST, I could then create a Comm Program directory file, for example the Boyan Version 5 BOYAN.FON file, with the DOS command : C:>fondir bbs.lst /o:b /k That's all there is to it. To do a QMODEM.FON file, just change the /o:b parameter to /o:q. ┌───────────────────────────────────────────────────────────────────────┐ │ MORE DETAIL ABOUT FONDIR IMPORT │ └───────────────────────────────────────────────────────────────────────┘ I don't know which Comm Program you use. I do know that the /o: option is REQUIRED. You must use the /o: option to tell FONDIR which Comm Program you use. You must figure out which /o: option is for your Comm Program. Is that so hard ? Target phone directory filenames : "BOYAN.FON" use the /o:b option Boyan "PROCOMM.DIR" use the /o:p option Procomm "PCPLUS.DIR" use the /o:+ option Procomm Plus 1.1 "PCPLUS.DIR" use the /o:2 option Procomm Plus 2.0 "QMODEM.FON" use the /o:q option Qmodem "GT.DIR" use the /o:g option GT Powercomm "TELIX.FON" use the /o:t option Telix "PIBTERM.FON" use the /o:i option Pibterm "TM.FON" use the /o:m option Telemate * See note below "PC-TALK4.DIR" use the /o:c option PC-Talk "PC-TALK.DIR" use the /o:r option Rcomm "K9X.P" use the /o:k option K9 Express "DIALDIR.DAT" use the /o:o option Mirror "DIALDIR.PRM" use the /o:a option PC Anywhere "CC30.CFG" use the /o:y option Carbon Copy "BBS.DAT" use the /o:d option A Dialer "COMMO.FON" use the /o:f option Commo "UNICOM.DIR" use the /o:u option Unicom "ULTITERM.NUM" use the /o:l option Ultiterm "PILOT.DAT" use the /o:e option Pilot "Boyan, Procomm, Procomm +, Qmodem, Gt-Powercomm, Telemate, Telix, Pibterm, PC-Talk4, Rcomm, K9-Express, Mirror 3, PC Anywhere, Carbon Copy Plus, A Dialer, Commo, Unicom, Ultiterm and Pilot"... ...are all Copyrighted by their respective authors. ( A note to comm program AUTHORS and COPYRIGHT/TRADEMARK holders : At no time have I ever release the source to FONDIR nor the structures of phone directories sampled for this utility. ) In general, the contents of the phone file reflect your programs dialing directory information. The above file names are the defaults for your Comm Programs. * File create name note : For Telemate, when using the System ID ( |i ) specification, a file called "TM.MEM" is created. This is the Telemate memo file and it's contents is seen in the online dialing directory. FONDIR refers to it as the 'auxiliary' file. ┌───────────────────────────────────────────────────────────────────────┐ │ FONDIR USES DEFAULT DIRECTORY NAME. │ └───────────────────────────────────────────────────────────────────────┘ FONDIR always uses the above file names, and they are assumed to be in your current directory. It is an ERROR to enter a file name of these types as a parameter for FONDIR. You specify one of the file names above using the /o:? parameter. The valid characters for the '?' are shown above. FONDIR is going to convert from the text file to the Comm Program directory file, or vice versa. You specify the Comm Program type with the /o:? option, and you specify the BBS List text file name explicitly. ┌───────────────────────────────────────────────────────────────────────┐ │ FONDIR RENAMES EXISTING DIRECTORY FILE. │ └───────────────────────────────────────────────────────────────────────┘ When FONDIR is going to write a directory file with one of the above names, AND that file already EXISTS : FONDIR will rename the existing file by changing the last letter of the 'filename' part of the complete file name to a unique number. For example, BOYAN.FON might become BOYA1.FON. This technique is used when the BBS list contains more entries than the Comm Program file will support. FONDIR will continue to rename the file to a unique name, for each directory file that is necessary to COMPLETELY convert the BBS list. For example, you might end up with the following files, ( again, I'll use the BOYAN.FON example ) : boyan.fon - the last file boya1.fon - the first file ( assuming none existed previously ) boya2.fon - the second file ( second set of entries ) etc. There are two ways to use these 'numbered' files. The first is to simply copy it to the actual name required by your Comm Program. The second way is to use your Comm Program's "select phone directory file" option, many Comm Programs support this function. Any auxiliary file generated will follow this same naming convention. WARNING : the maximum number of BBS list entries supportable is dependent upon the number of entries per file your Comm Program supports. If FONDIR has to create more than 10 directory files, the numbering system will fall into the characters which logically follow the '9' character; this is not fatal, just be sure to watch the file names to get the idea. After '9' comes '@', then 'A', 'B', etc. ┌───────────────────────────────────────────────────────────────────────┐ │ USAGE EXAMPLE ( Import BBS list to Comm Program ). │ └───────────────────────────────────────────────────────────────────────┘ The following command is an example. To convert to Procomm Plus 2.0 : FONDIR bbslist.txt /o:2 ^ ^ | | | | | | | `- translate to the Procomm + 2.0 format `- translate from this BBS list file The BBS list file must contain a Format Specification which FONDIR uses to determine how the data in the list file is organized. YOU MUST MANUALLY enter the specification if it is not already there. See Chapter 7 for more information on the Format Specification. ╔═══════════════════════════════════════════════════════════════════════╗ ║ 3 -- HOW TO EXPORT FROM YOUR PROGRAM TO A BBS LIST ║ ╚═══════════════════════════════════════════════════════════════════════╝ The idea of exporting TO a BBS list text file from your program phone directory is to support the changes you are still making manually, so that you don't have to enter them again every time a BBS list changes. The Export feature is also useful for translating between two or more Comm Programs. The BBS list file must contain a Format Specification. See Chapter 7 for more information on the Format Specification. For example purposes, create a text file called BBSLIST.TXT with the following line in it : |d5 |n20 |#12 |p4 Make sure your text file does NOT contain a CONTROL-Z ( ascii EOF ), such as DOS EDLIN would generate. The FONDIR export command has three parameters : FONDIR bbslist.txt /o:b /x ^ ^ ^ | | | | | `------ the export option | `--------- the program type Boyan option `------------------ a BBS text file to write to The above command will append list information from your Boyan program phone file directory ( boyan.fon ), to a file called "bbslist.txt" which would look like this : |d5 |n20 |#12 |p4 03/24 MY BBS 214-881-2627 #Z 03/24 Joe's BBS 214-555-1234 #Z 03/24 RBBS Central 900-555-0000 #Y You can specify WHICH Comm Program directory file to export using the option /x:filename format, but you can only export one comm program dialing directory file at a time. See the /x option description for more information. ┌───────────────────────────────────────────────────────────────────────┐ │ FONDIR APPENDS TO EXISTING BBS LIST. │ └───────────────────────────────────────────────────────────────────────┘ FONDIR always writes it's export text to the file name given. It does NOT overwrite an existing text file of that name, it adds it's export data to the end of existing data. These are also called 'append' writes. You may specify a fully qualified path name for your BBS list text file. ╔═══════════════════════════════════════════════════════════════════════╗ ║ 4 -- ONLINE HELP ║ ╚═══════════════════════════════════════════════════════════════════════╝ You can get the following help information by entering the FONDIR command with NO parameters, with the /h parameter, or with the /? parameter. Command format is >FONDIR BBSLIST.FIL /o:x [options] BBSLIST.FIL is the text file /o:x x = Program Types with the format specification. B - Boyan R - Rcomm OPTIONS : P - Procomm K - K9-express /m:n - max modem speed 3,1,2,4,9,a,b + - Procomm+1 O - MirrOr /b:n - speed always : 3,1,2,4,9,a,b 2 - Procomm+2 A - PcAnywhere /c:c - BBS list format key, default '|' Q - Qmodem5 Y - CarboncopY /p:c - protocol always 'c' G - Gt-power D - ADial /k - keep dates from BBS list T - Telix F - F-Commo /l:ddd - LOCAL area code 'ddd' is not LD I - PIbterm U - Unicom /a:ddd - prefix LD phone number 'ddd' M - TeleMate L - ULtiterm /d:ddd - METRO exchange area code 'ddd' C - PC-talk4 E - Pilot /f:ccc - filter mask field for 'ccc' 4 - Qmodem45 /s:pppp - support file path /x[:dirname] - Export to BBS list 24hr. Help/Register at Fidonet 1:124/6119 MY BBS 214-881-2627 9600,HST,V32 Error messages, if any, would be displayed immediately following this screen of data. See the document named FONERR.DOC for a description of each error message. ╔═══════════════════════════════════════════════════════════════════════╗ ║ 5 -- THE COMMAND LINE OPTIONS ║ ╚═══════════════════════════════════════════════════════════════════════╝ ┌───────────────────────────────────────────────────────────────────────┐ │ COMM PROGRAM TYPE ( /o: option ). │ └───────────────────────────────────────────────────────────────────────┘ It's required and fully described in Chapter 2, section More Detail on Import. OK, one more time : /o:x x = Program Types B - Boyan R - Rcomm P - Procomm K - K9-express + - Procomm+1 O - MirrOr 2 - Procomm+2 A - PcAnywhere Q - Qmodem Y - CarboncopY G - Gt-power D - ADial T - Telix F - F-Commo I - PIbterm U - Unicom M - TeleMate L - ULtiterm C - PC-talk4 E - Pilot ┌───────────────────────────────────────────────────────────────────────┐ │ ASSUME PROTOCOL ( /p: option ). │ └───────────────────────────────────────────────────────────────────────┘ If you specify a protocol using the /p option, then FONDIR will always set the protocol in each phone directory entry to the letter you specify in the /p option. In the absence of the /p option, FONDIR will use the Format Specification for PROTOCOL Code ( |p5 ), as you specified in the text file, and look there for a file transfer protocol code. The codes are defined in Chapter 8. ┌───────────────────────────────────────────────────────────────────────┐ │ KEEP DATE ( /k option ). │ └───────────────────────────────────────────────────────────────────────┘ If you want to import the date of the last call into your Comm Program phone file directory, then use the /k option. If you do NOT use the /k option, then your phone file directory will contain a blank date. In a special case, a Qmodem 4.3 entry will contain the date that FONDIR created the FON directory. ┌───────────────────────────────────────────────────────────────────────┐ │ LOCAL AREA CODE ( /l: option ). │ └───────────────────────────────────────────────────────────────────────┘ The /l: option allows you to specify which area code is your local area code, and FONDIR will remove the area code digits from the phone number in the text list entry. The phone numbers in a BBS list are best kept as full 10 digit phone numbers. Like this : 214-881-2627. If this is a local call to you, then you want FONDIR to remove the 214- code. They do not HAVE to be 10-digit, but the FONDIR /l, /d and /a options function best when you use 10 digit codes. For your local calls, area code dialing will not be required or desired. See Chapter 7 for |L format options that allow use of 7 digit numbers in the list, with an area code 'header'. For example, if you live in the 214 area code, you may want to use the option /l:214- to remove ONLY those digits from the start of a phone number. /l:214 is the same, because FONDIR always puts the trailing - character on area codes. Of course, many numbers in your local area code are still long distance. FONDIR will attempt to read a file called LDAREA.xxx, where 'xxx' is the three digit local area code. Each exchange in the LDAREA.xxx file is assumed to be not local, but long distance. Since I don't know all the long distance areas and phone exchanges, I leave it up to you to make your own LDAREA.xxx files, if you need them. Just make sure you use the same format that the METRO.xxx files use, ie. one three digit code per line. Here's an example : You live in the 214 area code, and you have a BBS list like this -- |d5 |n20 |#12 |p4 03/24 MY BBS 214-881-2627 #Z 03/24 Joe's BBS 214-555-1234 #Z 03/24 RBBS Central 900-555-0000 #Y You also have a file called LDAREA.214 that contains two lines : 555 666 When you use the /l:214 and /a:1- options, FONDIR will create phone numbers that look like this : 1 MY BBS 881-2627 2 Joe's BBS 1-214-555-1234 3 RBBS Central 1-900-555-0000 Why ? The first entry was 214-881 and 881 is NOT in the LDAREA.214 file, so it must be local. FONDIR stripped the area code. The second entry was 214-555 and 555 IS in the LDAREA.214 ( remember this is just an example ). 555 then must be long distance, so FONDIR prefixed the number using the 1- code. The third entry is area code 900 and in not involved with this type of translation. On export, FONDIR will add back the area code to any phone number which is 8 digits or less, prior to writing to the BBS list file, if you use the /l: and /a: options. If you use the /s: path option, it affects where FONDIR looks for the LDAREA exchange file. Use the /s: option before the /l: option, and the LDAREA file is searched from the path. Use the /s: option after the /l: option, and the LDARDA file is searched from the default subdirectory. See the section on the /s: option for more information. ┌───────────────────────────────────────────────────────────────────────┐ │ PREFIX PHONE NUMBER ( /a: option ). │ └───────────────────────────────────────────────────────────────────────┘ The phone numbers in a BBS list may not always be fully dialable phone numbers. Some examples of this are 'local 7 digit numbers' which are not local to you, incomplete phone numbers which are not stand alone numbers, or when you need to use access codes before you dial the number, such as the standard 1+ access code. The /a: option, only works on Long Distance numbers outside your local area code as specified by the /l: option, unless the additional LDAREA.xxx file has been used. Use /a: followed by one or more prefix digit codes. For example, you need to dial 10288-1- to get the correct long distance carrier : use /a:10288-1- to prefix every LD phone number in the BBS list. Most people with standard 10 digit phone lists will use : /a:1- The prefix is not recommended for PBX ( dial 9 to get out ) type functions. In these cases, where ALL your phone numbers must be prefixed, use your Comm Program's dialing prefix feature, or set your modem dial string to something like ATDT9, which causes every phone number to begin with the 9. ┌───────────────────────────────────────────────────────────────────────┐ │ METRO NUMBER ( /d: option ) │ └───────────────────────────────────────────────────────────────────────┘ The files METRO.214 and METRO.817 contain sample exchange code listings. The sample represents the 214 and 817 area codes. Each file can contain none, one or up to 50 'exchange' codes. An exchange is the first three digits of a 7 digit number. Certain areas of the country allow callers to dial 'toll free' calls with 10 digits, ie. using the area code, but not the 1+ format. These extended area calls are typically called Metro numbers ( EMS service ). FONDIR looks for a METRO.xxx file. The 'xxx' is changed to the area code digits you specify in the /d: option. If FONDIR finds such a file in the current directory, it will enable the logic to determine from your /d: option ( a metro area ) and the /a: option ( the long distance prefix ), whether or not a number is truly long distance, a metro number, or a local phone call, and how to encode the number correctly for dialing. Since I don't know all the metro areas and phone exchanges, I leave it up to you to make your own METRO.xxx files, if you need them. Just make sure you use the same format that the files are in now, ie. one three digit code per line. You must insure that the 'xxx' extension matches your /d:xxx code. An example : You live in the 214 area code and you can dial some 817 area code numbers without dialing 1 first. Your BBS list looks like this : |d5 |n20 |#12 |p4 03/24 MY BBS 214-881-2627 #Z 03/24 Joe's BBS 817-100-1234 #Z 03/24 RBBS Central 817-555-0000 #Y You have a file called METRO.817 that contains two lines : 555 666 When you use the /d:817 and /a:1- options, FONDIR will create phone numbers that look like this : 1 MY BBS 1-214-881-2627 2 Joe's BBS 1-817-100-1234 3 RBBS Central 817-555-0000 Why ? Well the first entry was just like the example used in the /l: option description, but I didn't specify a /l: option ! The second entry is 817-100, but 100 is not in the METRO.817 file, so FONDIR translates it as a long distance number. The third entry is 817-555, and 555 IS in the METRO.817 file, so FONDIR knows its a metro type number and does not prefix it with the 1- digits. If you use the /s: path option, it affects where FONDIR looks for the METRO exchange file. Use the /s: option before the /l: option, and the METRO file is searched from the path. Use the /s: option after the /l: option, and the METRO file is searched from the default subdirectory. See the section on the /s: option for more information. ┌───────────────────────────────────────────────────────────────────────┐ │ NOTES ON /l, /a, /d OPTIONS │ └───────────────────────────────────────────────────────────────────────┘ The use of '-' dash characters is pretty much the norm for a phone number. They are transparent to your modem ( yes, you probably send dashes to your modem all the time ). You will note that I have demonstrated the /l, /a, and /d options using the '-' dash symbols. If your particular BBS list format does not use dashes, then you should not use them in your option parameters. On the off chance that your BBS list format uses the space ' ' character for a separator, you will have to code the options in a special way, using quotes around the whole option. For example : "/l:214 " Note the trailing space after the 214 digits. This coding format would be used when your phone numbers look like this : 214 881 2627, instead of like this : 214-881 2627. Because of restrictions imposed by the logic in FONDIR's phone number functions, only '-' dash or ' ' space or no separator code at all may be used. You may use any of these three choices, at any time, but no other separator codes are useable. ┌───────────────────────────────────────────────────────────────────────┐ │ FORMAT SPECIFICATION KEY CHARACTER ( /c option ). │ └───────────────────────────────────────────────────────────────────────┘ The Format Specification is a text line that you must place in your BBS List file. The Format Specification marks the data columns for the information fields in each entry. The default character is the '|' character. You may use any marker character by selecting it with the /c: option, and by using that character within your BBS list file. See Chapter 7 for more information on the Format Specification and which programs support which fields. ┌───────────────────────────────────────────────────────────────────────┐ │ MODEM SPEED ( /m: and /b: options ) │ └───────────────────────────────────────────────────────────────────────┘ The /m option allows you to specify your modems maximum speed. For example, if you have a 2400 bps modem, and your BBS list contains entries with faster rates, you must use the /m:2 option so that FONDIR will set the rates for the faster entries back to 2400 bps. The /b option allows you to set ALL entries to a specified speed. This is useful for 'locking' your modem rate to a fixed speed, regardless of the speed of the modem at the other end, or the connected rate. For example, if you want to lock your modem at 38400 bps, then use the /b:B option and FONDIR will set all the entries to 38400 bps, regardless of the speed code in the BBS list. See Chapter 11 for the valid Speed Codes. ┌───────────────────────────────────────────────────────────────────────┐ │ EXPORT ( /x option ) │ └───────────────────────────────────────────────────────────────────────┘ The /x option can be used in one of two formats : 1) /x = with default Comm Program directory name assumed, or 2) /x:dirname = specified Comm Program directory name. If you use the /x option with no directory name, FONDIR export assumes the standard Comm Program directory name, and that file must be located in the current sub-directory. If you use the /x:dirname option, and specify the directory name, that file must also be located in the current directory. Further, you may NOT specify a drive, path or file extension in the 'dirname' field. Even though you specify the directory FILENAME, the EXTENSION is assumed. This is because certain Comm Programs follow naming conventions with the directory file name, and/or auxiliary or secondary file name. Example using BOYA1.FON : fondir bbs.lst /o:b /x:boya1 You can use the /c, /l, /d, /k and /s options with the Export ( /x ) option. The BBS list filename is mandatory, and must contain a Format Specification as is the /o: option. See Chapter 3 for more information on Export. ┌───────────────────────────────────────────────────────────────────────┐ │ SUPPORT FILE PATH ( /s: option ) │ └───────────────────────────────────────────────────────────────────────┘ In response to requirements for a multiuser FONDIR, such as with the online directory creation doors, or for LAN usage, the /s option allows you to specify a subdirectory where FONDIR support files are located. The support files include : LDAREA exchange file ( if /l specified after /s ) METRO exchange file ( if /d specified after /s ) comm program directory ( both import and export ) auxiliary file ( both import and export ) Path information for the BBS text file may be specified in that filename parameter. FONDIR looks for the LDAREA or METRO exchange files in the current subdirectory unless the /s:path option is specified before the /l:ddd or /d:ddd options. On Import : FONDIR creates the comm program directory files in the /s:path subdirectory whenever the /s option is used. In the absence of the /s: option, the comm program directory files are created in the current subdirectory. Same for the auxiliary files. On Export : FONDIR looks for the comm program directory file ( whether the default or the /x: specified file ) in the /s:path subdirectory whenever the /s option is used. In the absence of the /s: option, the comm program directory file is searched in the current subdirectory. Same for the auxiliary file. For example, suppose you have 2 subdirectories called USER1 and USER2. FONDIR.EXE is located in the subdirectory called UTIL, and the default or current directory is COMM. In order for two users to run the program at the same time, you would need to code the FONDIR command for each to use the different subdirectories, as follows : User 1's call : \util\fondir \user1\bbs.lst /o:q /l:214 /d:817 /a:1- /s:\user1 User 2's call : \util\fondir \user2\bbs.lst /o:q /l:214 /d:817 /a:1- /s:\user2 The users can share the LDAREA and METRO exchange files located in the COMM directory ( /s is after the /l and /d options ). The Qmodem .fon files will be created in each users separate directory. If I put the /s: before the /l: and /d:, then the METRO and LDAREA files must be located in the \userx directory, as in : \util\fondir \user1\bbs.lst /o:q /s:\user1 /l:214 /d:817 /a:1- ┌───────────────────────────────────────────────────────────────────────┐ │ FILTER IMPORT ( /f: option ) │ └───────────────────────────────────────────────────────────────────────┘ Use the /f: option to select particular types of BBS list records to import into your dialing directory. When active, the /f: option lets you specify a mask, which must be found in the BBS list entry. Most likely, your BBS list has some kind of 'special character' or 'protocol' field which specifies some special characteristics of the system. Use the |K format specifier field ID to show FONDIR where this special data or coding is located in the BBS list. An example : |d5 |n20 |#12 |p4 |K4 03/24 MY BBS 214-881-2627 9Z b 03/24 Joe's BBS 817-100-1234 2Z $ 03/24 RBBS Central 817-555-0000 2Y r where b = 38400 bps, 2 = 2400 bps, $ is commercial BBS, and r is restricted membership. If you used the /f:$ option, you would only import Joe's ( the 2nd ) entry. If you used the /f:b option, you would only import MY BBS. Note that if the |K field is not specified, then the /f: option defaults to using the |p protocol field. So you could have this : |d5 |n20 |#12 |p4 03/24 MY BBS 214-881-2627 9Zb 03/24 Joe's BBS 817-100-1234 2Z$ 03/24 RBBS Central 817-555-0000 2Yr and get the same results. If you use more than one character, like /f:b$, then both characters ( 'b' and '$' ) must be found before the entry is imported. In our example above, NO entries would be imported because no entries contain both the 'b' and '$' characters. ╔═══════════════════════════════════════════════════════════════════════╗ ║ 6 -- FONDIR DOS COMMAND SYNTAX EXAMPLES ║ ╚═══════════════════════════════════════════════════════════════════════╝ >FONDIR bbslist.txt /o:b /s Import into Boyan from bbslist.txt, using system type for script name. >FONDIR bbslist.txt /o:+ /b:a Import into Procomm Plus, make all speeds 19200, typically of 'locked rate' option. >FONDIR bbslist.txt /o:+ /b:a /l:214 Import, local area code is 214. LDAREA.214 may contain exchanges in the 214 area which are still long distance to me. >FONDIR bbslist.txt /o:+ /b:a /l:214 /a:1- As above, long distance prefix is 1-. >FONDIR bbslist.txt /o:+ /b:a /l:214 /a:1- /d:817 As above, a metro area is 817. METRO.817 may contain exchanges in the 817 area which are still local calls to me. Most people will use the /l, /a, /d options all the time if they live in a long distance or metro area. >FONDIR c:\new\bbslist.txt /o:+ /m:2 Import into Procomm Plus from bbslist.txt, max speed of my modem is 2400 ( over 2400 is changed to 2400 ). >FONDIR bbslist.txt /o:q /k Import into Qmodem from bbslist.txt, use the date from the list. >FONDIR bbslist.txt /o:g /p:O Import into GT-Powercomm, default file transfer protocol is 'O'. >FONDIR bbslist.txt /o:g /f:+ Import into GT-Powercomm, only those entries with the '+' mask present. >FONDIR bbslist.txt /o:p /x Export from Procomm 2.4 to bbslist.txt. >FONDIR bbslist.txt /o:b /x:boya1 Export from a specified Boyan 5 phone file to bbslist.txt. Yes, you can use this command : FONDIR bbslist.txt /o:+ /b:a /m:a /l:214 /d:817 /a:10777-1- /k /p:Z /f:+ The above command Imports from the text file bbslist.txt into Procomm Plus format. All modem speeds are set to 19200. My area code is 214 and I have a metro area 817. Both my LDAREA.214 and METRO.817 files are present. True long distance calls will use the 10777-1- prefix. I want to stuff the date from the bbslist.txt file into Procomm Plus, and I want the default file transfer protocols to be 'Z' type. I only want to import entries with a '+' identifier. ┌───────────────────────────────────────────────────────────────────────┐ │ TRANSFORM EXAMPLE. │ └───────────────────────────────────────────────────────────────────────┘ FONDIR hcc.lst /o:b /l:214 /a:1- /d:817 /k /x FONDIR hcc.lst /o:q /l:214 /a:1- /d:817 /k The above two commands will export from Boyan format, writing the text file hcc.lst and import that text file into Qmodem format. The file hcc.lst is included with the FONDIR release. It looks like this : |n30 |#16 |p8 |d8 |f8 |i25 MY BBS 214-881-2627 bZ 01/01/92 OPUS Home of FONDIR ┌───────────────────────────────────────────────────────────────────────┐ │ ERROR CHECKING OF INPUT ( SEMANTIC ). │ └───────────────────────────────────────────────────────────────────────┘ FONDIR pretty much validates everything you enter, and it HAS to be valid or FONDIR will generate a message, usually telling you ( by re-displaying your input ) the part which FONDIR did not understand. ┌───────────────────────────────────────────────────────────────────────┐ │ ERROR ON INPUT ( LOGICAL ). │ └───────────────────────────────────────────────────────────────────────┘ FONDIR does not know what protocol letter you need to use, so it allows you to input any character. FONDIR will ignore otherwise valid options which can not be implemented for a particular Comm Program. For example, you could specify /p:} and FONDIR will merrily put the '}' character into your dialing directory's transfer protocol field. I don't know that your comm program will do with that. ╔═══════════════════════════════════════════════════════════════════════╗ ║ 7 -- BBS LIST FORMAT SPECIFICATION KEYS ║ ╚═══════════════════════════════════════════════════════════════════════╝ Most any BBS list can be supported. What FONDIR is looking for in the text list file is a Format Specification which tells FONDIR where the information fields are for each entry. YOU MUST SUPPLY THE FORMAT SPECIFICATION, if it is not already in the BBS List file you are working with. The Format Specification works best with columnar ( readable ) fields, arranged with one list entry per text line. As an example, here is the format of a full featured BBS list. Note that the following text lines are longer than 80 characters, so an 80 column display or printer will not allow you to see it as a single line. But it IS a single line, and you should obtain a text editor that supports line lengths greater than 80 characters if you want all the information available all the time. |n32 |f4 |i8 |#15 |p4 |c5 |t5 |m8 MY BBS Henry Clark OPUS 124/6119 214-881-2627 2U Z 04/21 23:31 PASSWORD MY Other BBS Henry Clark OPUS 214-555-1212 9U Z 04/21 23:42 PASSWORD Joe's Board TBBS 212-999-9999 AU Z 04/21 23:31 PASSWORD Ed's Mobile BBS QUIC 124/120 805-555-5555 9H Z The first line is the Format Specification. The remaining lines are BBS List entries. Note that each '|' character is placed directly above the start of column data in the list entry. Some entries do not have all available data, that's ok. Most Comm Programs do not support all the fields. That's OK too. Your BBS list file MUST contain a Format Specification. This includes the file that you will EXPORT to. A brand new Export file will have to contain the one line of Format Specification, as this is the only place FONDIR will look for it. WARNING : Inconsistent results occur when the text line length is less than the format specification position. Make sure that empty columns of data are SPACE FILLED out to the end of the format specification. FONDIR export does this. ┌───────────────────────────────────────────────────────────────────────┐ │ FORMAT SPECIFICATION CODING │ └───────────────────────────────────────────────────────────────────────┘ Each field contains three parts, all of which are required. They are : Field-separator Code Length (1) (2) (3) '|' is the default field separator key. It appears in the same column as the applicable list entry data. Think of it as a marker or position indicator. You can use any character by selecting the /c: option on the FONDIR command line. Code is one of the field codes listed below. Length number is a decimal value from 2 to 255. The field identifier codes are : n - BBS Name, any ascii characters i - ID or Info, additional description of BBS, ascii characters # - Dial Digits, 0-9, -, etc., must begin with a digit 0 through 9 p - Protocol Modifier Codes, see protocol codes below. d - Last Call Date, mm/dd/yy t - Last Call Time, hh:mi:ss f - Script File name, typically a logon script g - Log File name or Macro File name w - Password e - Emulation type, such as ANSI or VT100 c - Call count, numbers of times connected o - Hours of operation, when the BBS is available h - elapsed hours online m - elapsed minutes online $ - elapsed total hours online r - uploads received count x - downloads transmitted count @ - comm port, first character 0 ( default ), 1 or 2 y - city code, useful for network dialing ( - Dialing script or Keyboard file K - mask for /f: option ( defaults to p field ) For example, |n32 means the following : the | character is positional, it shows where the column containing the BBS name is located. The n character, specifies that this is the BBS name. The 32 is the total length of the BBS name field. The |# phone number field is REQUIRED and a valid entry is a line of text that has a numeric digit ( 0 through 9 ) in the first character of the phone number field. The Format Specifiers are based upon the available fields in the comm programs that FONDIR supports, except for the |k, which is the filter mask field : see the section on /f: filter option. ┌───────────────────────────────────────────────────────────────────────┐ │ FORMAT SPECIFIER STACKING │ └───────────────────────────────────────────────────────────────────────┘ If a column of BBS list data is to be used as more than one field, you may 'stack' the specifiers behind a single | character. For example, suppose you want a script file ( |f option ) to be the first four characters of the BBS name ( |n option ). Stack the format specifiers like this : |n32f4 |#15 |p4 |c5 |t5 |m8 OPUS MY BBS Henry Clark 214-881-2627 2U Z 04/21 23:31 PASSWORD OPUS MY Other BBS Henry Clark 214-555-1212 9U Z 04/21 23:42 PASSWORD TBBS Joe's Board 212-999-9999 AU Z 04/21 23:31 PASSWORD QUIC Ed's Mobile BBS 805-555-5555 9H Z WARNING : Do not use a width longer than the actual width of the column of data. This is important for both import and export. A larger width specification will result in 'spill' from the next column of data into this column, and will cause extra ( usually unwanted ) data to be placed in your Comm Program directory file. ┌───────────────────────────────────────────────────────────────────────┐ │ FORMAT FIRST WORD LENGTH │ └───────────────────────────────────────────────────────────────────────┘ Some of the Comm Program directory fields specify file names. These include : |f - Script File |g - Log File or Macro File |( - Dialing Script File or Keyboard Map File It is not useful to have a file name with a space character it. For example, |f8 on the field "OPUS MY BBS", would normally generate a script file named "OPUS MY ", which is not valid file name. To avoid these problems, FONDIR automatically translates only the first whole word of the BBS list field for the above three format keys. The field length in the format key becomes a maximum length, and not a specific length. "OPUS MY BBS" using |f8 translates to "OPUS", the first word, and a useful script file name. "PCBOARD Joe's BBS" using |f4 translates to "PCBO", since the maximum length is 4. ┌───────────────────────────────────────────────────────────────────────┐ │ FORMAT HEADER SPECIFICATION │ └───────────────────────────────────────────────────────────────────────┘ L - long distance area code During processing of the BBS list file, FONDIR will look for the |L characters in the first column of each line. If this is found, FONDIR looks further in the line for an Area Code of three digits. If the area code is found, FONDIR assumes that this area code applies to all subsequent phone number entries until a new |l is found. For example : |d5 |n20 |#12 |p2 03/24 MY BBS 214-881-2627 #Z 03/24 MY BBS 214-881-2627 #Z 03/24 MY BBS 214-881-2627 #Z could be listed as : |d5 |n20 |#12 |p2 |L Dallas 214 03/24 MY BBS 881-2627 #Z 03/24 MY BBS 881-2627 #Z 03/24 MY BBS 881-2627 #Z This encoding format is useful when the BBS list entries are very wide. FONDIR does not support this convention on export to the BBS list file. ┌───────────────────────────────────────────────────────────────────────┐ │ COMM PROGRAM FIELD SUPPORT │ └───────────────────────────────────────────────────────────────────────┘ The following table shows which format key fields are used by each of the supported programs. You may specify a field in your BBS list, that is not supported by your Comm Program. Note that the last date |d, and last time |t fields are only modified when you use the /k 'keep date' command line parameter. .-- Name |n | .-- Phone |# | | .-- Script |f | | | .-- Speed |p | | | | .-- Parity |p | | | | | .-- Xfer protocol |p | | | | | | .-- Emulation |e | | | | | | | .-- Last Date |d | | | | | | | | .-- Call count |c | | | | | | | | | .-- Password |w | | | | | | | | | | Boyan 5.0 x x x x x x x x Procomm 2.4.3 x x x x x Procomm + 1.1 x x x x x x x x x Procomm + 2.0 x x x x x x x x x x Qmodem 5.0 x x x x x x x x x x Qmodem 4.5 x x x x x x x x x GT 17.00 x x x x x x x x x x Telix 3.15 x x x x x x x x x x Pibterm 4.1 x x x x x x x x Telemate 3.01 x x x x x x x x x x PC-Talk4 1.39 x x x x Rcomm 2.1 x x x x K9-Express 8.8 x x x x x x x Mirror 3 1.01 x x x x x x x x PCAnywhere 3.11 x x CC Plus 4.01 x x x A Dialer 2.0 x x x x x Commo 5.0 x x x x Unicom 3.0 x x x x x x x x x Ultiterm 2.0 x x x x x x x x x x Pilot 2 x x x x x .-- Macro file |g | .-- Keyboard file |( | | .-- Comm Port |@ | | | .-- Information |i | | | | .-- Last Time |t | | | | | .-- Log File |g | | | | | | .-- Hours |o | | | | | | | .-- Minutes |m | | | | | | | | .-- Elapsed |$ | | | | | | | | | .-- Uploads |r | | | | | | | | | | Boyan 5.0 Procomm 2.4.3 Procomm + 1.1 Procomm + 2.0 x x x Qmodem 5.0 x x Qmodem 4.5 GT 17.00 x x x x x x Telix 3.15 Pibterm 4.1 x Telemate 3.01 x x x PC-Talk4 1.39 Rcomm 2.1 K9-Express 8.8 x Mirror 3 1.01 x x x x PCAnywhere 3.11 x CC Plus 4.01 A Dialer 2.0 Commo 5.0 x Unicom 3.0 Ultiterm 2.0 Pilot 2 x .-- Downloads |x | .-- City Code |y | | | | Boyan 5.0 Procomm 2.4.3 Procomm + 1.1 Procomm + 2.0 Qmodem 5.0 Qmodem 4.5 GT 17.00 x x Telix 3.15 Pibterm 4.1 Telemate 3.01 PC-Talk4 1.39 Rcomm 2.1 K9-Express 8.8 Mirror 3 1.01 PCAnywhere 3.11 CC Plus 4.01 A Dialer 2.0 x Commo 5.0 Unicom 3.0 Ultiterm 2.0 Pilot 2 ╔═══════════════════════════════════════════════════════════════════════╗ ║ 8 -- BBS LIST CONTENTS ║ ╚═══════════════════════════════════════════════════════════════════════╝ ┌───────────────────────────────────────────────────────────────────────┐ │ PROTOCOL FIELD FORMAT │ └───────────────────────────────────────────────────────────────────────┘ The protocol field is specially coded, and contains several characters of information, including modem speed, parity, file transfer protocol and modem type. Some examples : |p5 2 EX The above specifies a 2400 bps, Even parity connection using Xmodem for a file transfer protocol. |p5 BZ The above specifies 38400 bps and Zmodem protocol. The protocol modifier codes are described in the following sections. Support for protocol modifiers will be based on these lists. Trademarks and Copyrights exists for several of the names included below. ┌───────────────────────────────────────────────────────────────────────┐ │ THE BPS MODEM RATE. │ └───────────────────────────────────────────────────────────────────────┘ ! or 3 - 300 bps @ or 1 - 1200 bps # or 2 - 2400 bps ( the default ) 4 - 4800 bps ^ or 9 - 9600 bps a or A - 19200 bps 8 or b or B - 38400 bps c or C - 57600 bps d or D - 115200 bps ┌───────────────────────────────────────────────────────────────────────┐ │ MODEM TYPE │ └───────────────────────────────────────────────────────────────────────┘ This field is reserved but presently not used by any Comm Program. I'm trying to avoid the use of these characters in the protocol field. U - U.S. Robotics H - Hayes F - Fastcomm T - Trailblazer V - any V.32 ┌───────────────────────────────────────────────────────────────────────┐ │ PARITY INDICATOR. │ └───────────────────────────────────────────────────────────────────────┘ e or E - Even parity ┌───────────────────────────────────────────────────────────────────────┐ │ FILE TRANSFER PROTOCOL TYPE. │ └───────────────────────────────────────────────────────────────────────┘ The following are only a few of the many available. Z - Zmodem X - Xmodem Y - Ymodem K - Kermit I - Imodem G - Ymodem-G T - Telink S - SeaLink 7 - Modem 7 ┌───────────────────────────────────────────────────────────────────────┐ │ TERMINAL EMULATOR MODE CODES │ └───────────────────────────────────────────────────────────────────────┘ The following are the supported terminal emulator codes. TT - TTY AN - ANSI VT - VT100 TV - Televideo HE - Heath AD - AD 31 - Model 31 32 - 3270 WY - Wyse Register if you want custom BBS list translations. ┌───────────────────────────────────────────────────────────────────────┐ │ Examples of BBS Lists │ └───────────────────────────────────────────────────────────────────────┘ A few BBS list Format Specifications are presented for examples. Many of these are longer than 80 characters. This first list, HCC.LST, is included with the FONDIR release archive. Henry's List Format |n30 |#16 |p8 |d8 |f14 |i25 MY BBS 214-881-2627 bZ 01/17/92 OPUS Home of FONDIR Darwin National BBS List : |#12 |f1 |p2 |n20 214-881-2627 O bZ MY BBS Fido Nodelist ( use COMCOL /m:15 /c:; to convert to vertical column format ) : |n15 |#15 |p1 MY BBS 214-881-2627 9 XLATLIST Text Output of Nodelist : |n20 |#14 |p1 MY BBS 214-881-2627 9 Carr/Farmer Dallas/Ft. Worth BBS List : |L area code header 214 |n29f8 |#8 |P9 |I24 |d5 OPUS MY BBS 881 2627 bZ Home of FONDIR 01/17 ╔═══════════════════════════════════════════════════════════════════════╗ ║ 9 -- PROGRAM SWITCHES AND DEFAULTS ║ ╚═══════════════════════════════════════════════════════════════════════╝ The default protocol is 'Z', Zmodem ( thanks Chuck. ) The default bps rate is 2400 bps (2). The default maximum rate is 38400 (b). The default I/O port number is 0 ( not COM1, Telemate only ). The default Format Specification Field Separator key character is '|'. The default last date called is blank ( today's date, Qmodem only ). The maximum line length of a BBS text file is 255 characters. ┌───────────────────────────────────────────────────────────────────────┐ │ Comm Program Type Codes │ └───────────────────────────────────────────────────────────────────────┘ Here are the valid program type codes used in the /o: parameter. 'B' Boyan 5.0 'P' Procomm 2.4.3 '+' Procomm Plus 1.1 '2' Procomm Plus 2.0 'Q' Qmodem 5.0 '4' Qmodem 4.5 'G' GT-Powercomm 17.00 'T' Telix 3.15 'I' Pibterm 4.1 'M' Telemate 3.01 'C' PC-Talk4 1.39 'R' Rcomm 2.1 'K' K9 Express 8.8 'O' Mirror 3 1.01 'A' PC Anywhere 3.11 'Y' Carbon Copy Plus 4.01 'D' A Dialer 2.0 'F' Commo 5.0 'U' Unicom 3.0 'L' Ultiterm 2.0 'E' Pilot 2.0 Upper or lower case letters are acceptable. As you can see, I'm running out of matching letters <grin>. If you don't use something, you will see an error message. The Comm Program type field is REQUIRED. You can use an upper or lower case letter to specify your Comm Program. ┌───────────────────────────────────────────────────────────────────────┐ │ Speed Code Parameters │ └───────────────────────────────────────────────────────────────────────┘ The valid speed codes for use with the /m: and /b: parameters are : 3 - 300 bps 1 - 1200 bps 2 - 2400 bps ( the default ) 4 - 4800 bps 9 - 9600 bps A - 19200 bps B - 38400 bps C - 57600 bps D - 115200 bps ( not fully supported ) Upper and lower case letters are acceptable. ┌───────────────────────────────────────────────────────────────────────┐ │ Warnings and Other Notes │ └───────────────────────────────────────────────────────────────────────┘ GT 17.00 modifies the phone directory header record after every use of the program. FONDIR sets the phone directory header to the same values generated by use of the GT_UTIL program when upgrading from version 16. ╔═══════════════════════════════════════════════════════════════════════╗ ║ 10 -- SHAREWARE REGISTRATION ║ ╚═══════════════════════════════════════════════════════════════════════╝ Print out this following page. Write a check. Address an envelope. Mail it. You will feel really good when that new program or version of your favorite is released, and FONDIR is right there, ready to support your upgrade. ╔═══════════════════════════════════════════════════════════════════════╗ ║ ║ ║ FONDIR Phone List Translator Utility Registration Form and ║ ║ Payment Invoice #921001 for Version 5.9 ║ ║ ║ ║ License for use is granted under the terms of the FONDIR ║ ║ License Agreement. ║ ║ ║ ║ ║ ║ Name ─────────────────────────────────────── ║ ║ ║ ║ Address ─────────────────────────────────────── ║ ║ ║ ║ ─────────────────────────────────────── ║ ║ ║ ║ ─────────────────────────────────────── ║ ║ ║ ║ Phone ─────────────────────────────────────── ║ ║ ║ ║ ║ ║ Version ──────────────── Date Received ──────────────── ║ ║ ║ ║ ║ ║ Check one : ║ ║ ║ ║ ( ) Enclosed is U.S. ──────────── Dollars for ─────────── copies ║ ║ ║ ║ at U.S. 20 Dollars each. ║ ║ ║ ║ ║ ║ ( ) Enclosed is U.S. ──────────── Dollars for ─────────── copies ║ ║ ║ ║ of customized versions at U.S. 40 Dollars each. ║ ║ ║ ║ ║ ║ Enter customization parameters : ────────────────────────────── ║ ║ ║ ║ ─────────────────────────────────────────────────────────────── ║ ║ ║ ║ ─────────────────────────────────────────────────────────────── ║ ║ ║ ║ ( ) Enclosed is U.S. 200 Dollars for 10 or more users ║ ║ ║ ║ on a site license ( make your own copies, documents ). ║ ║ ║ ║ Send this form with check or money order, ║ ║ payable to Hershel Enterprises, Inc. to : ║ ║ ║ ║ Software Mechanics, FONDIR ║ ║ P.O. Box 832052 ║ ║ Richardson, TX 75083-2052 ║ ║ U.S.A. ║ ║ ║ ╚═══════════════════════════════════════════════════════════════════════╝ ╔═══════════════════════════════════════════════════════════════════════╗ ║ 11 -- LICENSE AGREEMENT ║ ╚═══════════════════════════════════════════════════════════════════════╝ The SOFTWARE is FONDIR, the Phone Directory Translate Utility, Copyright (C) 1988-1991 Henry C. Clark, Hershel Enterprises, Inc. and FONMAN, the Phone Dear Interactive Interface. By using or distributing, or allowing to be distributed, this SOFTWARE, you are agreeing to be bound by the terms of this agreement. If you do NOT agree to the terms of this agreement, promptly destroy any and all copies of the SOFTWARE that you may have. ┌───────────────────────────────────────────────────────────────────────┐ │ The Terms of this Agreement : │ └───────────────────────────────────────────────────────────────────────┘ 1 You may NOT accept money, or otherwise charge a fee for the SOFTWARE because you transfer a copy of the SOFTWARE to another party. You may NOT alter the SOFTWARE files, nor distribute the files using a file name other than that name which you received, except for the extension as relates to compression techniques. The SOFTWARE may be compressed using different techniques, only if all the component files of the original package are included. You may NOT decompile or reverse engineer the SOFTWARE. You may NOT include the SOFTWARE in another work, without written permission from Hershel Enterprises, Inc. dba Software Mechanics. 2 You may NOT accept money, or otherwise charge a fee for ANY usage or operation of the SOFTWARE, without written permission from Hershel Enterprises, Inc. dba Software Mechanics. 3 You may NOT accept money, or otherwise charge a fee for ANY medium upon which the SOFTWARE is transferred, including but not limited to modem carrier, diskettes, CD-ROM, magnetic tape, etc. without written permission from Hershel Enterprises, Inc. dba Software Mechanics. We invite your requests to include our SOFTWARE in your compilations. 4 You may NOT use or distribute the Software in ANY manner for or by commercial or governmental entities without first correctly filling out and sending the registration agreement and payment. US Government restricted rights are set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013(Oct. 1988) and FAR 52.227-19(June 1987). Contractor is Hershel Enterprises, Inc. 5 You accept and understand that NO warranty is expressed or implied. The person using the SOFTWARE bears all risk as to the quality and performance of the SOFTWARE. In no event shall Hershel Enterprises' liability for any damages ever exceed the price paid to Hershel for the license to use the SOFTWARE, regardless of the form of the claim, even if Hershel Enterprises has been notified of such a possibility. 6 You MAY freely distribute the Software within the above license restrictions. You may use the Software on a trial basis, and you are required to pay for the Software if you use it on a regular basis. ┌───────────────────────────────────────────────────────────────────────┐ │ Note from the Author : │ └───────────────────────────────────────────────────────────────────────┘ As the task of keeping up with the latest Comm Programs increases, take time to reflect on the effort expended to produce this program. When you run this program, watch how fast it finishes. This program is not the type you run everyday, but it will save you countless hours of manual data entry, and open up the door to the modem world for you. When you fill out the registration slip, write a check and use an envelope, you ensure that improvements are made before you need them. My compilers, software tools, PCs, modems and especially my time, are not free. Shareware is not a type of software, it is a form of distribution. You get to make sure this program works for you before you pay for you license to use it.