The Equalizer BBS

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

/ The Equalizer BBS / equalizer-bbs-collection_2004.zip / equalizer-bbs-collection / BBS-PCBOARD-STUFF / FP14S.ZIP / FIDOPCB.DOC < prev next >

Wrap

Text File | 1993-08-12 | 79KB | 1,623 lines

██████ ▄▄ ██ ██████ ██████ ██████ ┌──────────────────────────────┐ ██ ██ ██ ██ ██ ██ ██ │ User Reference Manual: │ ████ ██ ██████ ██████ ██████ ██ █████ │ │ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ │ PROGRAM & UTILITIES │ ██ ██ ██████ ██████ ██ ██████ ██████ │ │ ───────────────────────────────────────────── │ (c) MicroArt d.o.o., 1991-93 │ FidoNet to PCBoard 15.x mail interface └──────────────────────────────┘ by Matjaz Koce [Manual revised and enhanced by Jeffrey Boyd] Lazy Sysop's rule: "Long manuals are never printed and read completely" FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual ───────────────────────────────────────────────────────────────────────────── TABLE OF CONTENTS Trademarks and Warranty . . . . . . . . . . . . . . . . iii Typographical Conventions . . . . . . . . . . . . . . . . iv Naming Conventions. . . . . . . . . . . . . . . . . . . . iv Distribution Archive Contents . . . . . . . . . . . . . . v Distribution Rules. . . . . . . . . . . . . . . . . . . . v Unregistered Version. . . . . . . . . . . . . . . . . . . vi License of Use. . . . . . . . . . . . . . . . . . . . . . vi Contacting The Author . . . . . . . . . . . . . . . . . vii Summary of Features . . . . . . . . . . . . . . . . . . . 3 Limitations . . . . . . . . . . . . . . . . . . . . . . . 4 Installation and Setup. . . . . . . . . . . . . . . . . . 5 Command Line Parameters . . . . . . . . . . . . . . . . . 7 Configuring FidoPCB . . . . . . . . . . . . . . . . . . . 9 Lost Mail Handling. . . . . . . . . . . . . . . . . . . . 16 NetMail Handling. . . . . . . . . . . . . . . . . . . . . 17 FidoPCB and UUCP Domains. . . . . . . . . . . . . . . . . 19 Running FidoPCB as a Door . . . . . . . . . . . . . . . . 21 Using AreaFix . . . . . . . . . . . . . . . . . . . . . . 22 The FPCONFIG Utility. . . . . . . . . . . . . . . . . . . 24 Common Questions. . . . . . . . . . . . . . . . . . . . . 26 Support and Distribution. . . . . . . . . . . . . . . . . 28 Credits . . . . . . . . . . . . . . . . . . . . . . . . . 29 Glossary. . . . . . . . . . . . . . . . . . . . . . . . . 30 iii FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual ───────────────────────────────────────────────────────────────────────────── TRADEMARKS AND WARRANTY All of the programs mentioned in this documentation, whether included in the following list, or not, are copyrighted and/or trademarked by their respective authors. Any omission from the list is unintentional. Please refer to each individual program to determine the actual copyright/trademark owner(s) as appropriate or needed. IBM is a trademark of International Business Machines, Inc. MS-DOS, Windows, TrueType and Microsoft Word, are copyrighted products of Microsoft Corporation. WordPerfect is a copyrighted product of Word- Perfect Corporation. PCWrite is a product of QuickSoft, Inc. PCBoard and the PCBSetup Utility are products of Clark Development, Inc. BinkleyTerm is a product of Bit Bucket Company. FrontDoor and the FM Editor are products of Advanced Engineering sarl. D'Bridge is a product of Chris Irwin. ZIP, the ZIP utilities, PKARC and PKXARC are products of PKWare, Inc. ARC/ARCE are products of System Enhancements Associates (SEA), Inc. ARJ and the ARJ utilities are products of Robert K. Jung. LHA and LHARC utilities are products of Haruyasu Yoshizaki. AreaFix is copyrighted by Greg Dawson and George Peace. The X00 Fossil Driver is a product of Raymond L. Gwinn. LANTastic is a product of Artisoft, Inc. DR-DOS is a product of Digital Research, a division of Novell, Inc. Novell and NOS are also products of Novell, Inc. IN NO EVENT SHALL THE AUTHORS OF FIDOPCB AND ITS ASSOCIATED UTILITIES (HEREAFTER, THE PROGRAM), BE HELD RESPONSIBLE IN ANY WAY, FOR THE BEHAVIOR OF ANY VERSION OF THE PROGRAM. NEITHER THE AUTHOR, OR ANY OTHER PARTY AUTHORIZED BY THE AUTHOR TO MODIFY AND DISTRIBUTE THE PROGRAM, SHALL BE HELD LIABLE FOR DAMAGES INCURRED, INCLUDING LOST INCOME, AND/OR OTHER SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE, OR INABILITY TO USE THE PROGRAM. THIS INCLUDES, BUT IS NOT LIMITED TO LOSS OF DATA, DATA BEING RENDERED INACCURATE, LOSSES SUSTAINED BY THIRD PARTIES, OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER SOFTWARE. THE ABOVE TERMS APPLY IN ALL CASES AND SITUATIONS, EVEN IF THE AUTHOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR FOR ANY CLAIM BY ANY OTHER PARTY. PLEASE, SUPPORT SHAREWARE! FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual iv ───────────────────────────────────────────────────────────────────────────── TYPOGRAPHICAL CONVENTIONS [] Square brackets in the text, or in command line samples, generally enclose optional commands. Text of this sort should not be typed verbatim. <> Angle brackets in text, or in command line samples, encloses alternate options for a given command. They are also used to indicate variable characters in filenames. | Pipes within bracketed commands or alternate options in the text or in command line samples, separate the possible choices for the command or options NAMING CONVENTIONS FidoPCB is distributed using the following file naming convention: FP<v><b>.<ext>, where <v> represents the version number, <b> refers to the release code (A = alpha, B = beta, S = shareware), and <ext> refers to the compression method used on the distribution archive. Example: The Shareware release of FidoPCB version 1.3 (ZIP format) is distributed under the filename, FP13S.ZIP. v FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual ───────────────────────────────────────────────────────────────────────────── DISTRIBUTION ARCHIVE CONTENTS The following files should be present within the program distribution archive: │ FILE │ DESCRIPTION │ ╞══════════════╪════════════════════════════════════════════╡ │ FILE_ID.DIZ │ Archive description │ │ DESC.SDI │ Archive description │ │ MICROART.BBS │ MicroArt BBS Phone numbers and information │ │ ORDERFRM.DOC │ FidoPCB Order Form (ASCII) │ │ HISTORY.DOC │ FidoPCB Revision history (ASCII) │ │ FPCONFIG.EXE │ FidoPCB Configuration Utility │ │ FIDOPCB.DOC │ FidoPCB Users Manual (ASCII) │ │ FIDOPCB.EXE │ FidoPCB Executable program │ │ FIDOPCB.FD │ Sample FrontDoor/IM Configuration file │ │ FIDOPCB.BT │ Sample BinkleyTerm Configuration file │ │ FIDOPCB │ Sample DOOR Batch file │ │ LOST │ PCBoard Message file for LOST messages │ │ LOST.NDX │ Index file for LOST Message file │ │ MATRIX │ PCBoard Message file for NetMail messages │ │ MATRIX.NDX │ Index file for MATRIX Message file │ │ RUNFD.BAT │ Sample Batch file for use with FD or IM │ │ RUNBT.BAT │ Sample Batch file for use with BinkleyTerm │ └──────────────┴────────────────────────────────────────────┘ Alpha/Beta distribution archives only contain the Revision History and executable program files, however additional files such as the sample configuration, may be included occasionally. It is strongly suggested that HISTORY.DOC be consulted for descriptions of changes and fixes made to the program. DISTRIBUTION RULES SysOps are permitted to add comments to the FidoPCB distribution archive, only if they normally do so with all of their downloadable files. Additional files, such as README.1ST or BBS_AD may be added as well, provided that the filenames do not conflict with the filenames already listed in the distribution archive, and that this practice is adhered to for each downloadable file. Alpha and Beta version distribution is restricted to those systems with specific permission to distribute them. The distribution of registered versions of FidoPCB, and of Key Files is prohibited. FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual vi ───────────────────────────────────────────────────────────────────────────── UNREGISTERED VERSION Running FidoPCB will indicate whether you are using the shareware, or the registered version. In the unregistered version, FidoPCB appends FidoPCB [NR] to the tearline, whereas the registered version appends your Serial Number. The unregistered version supports a maximum of 20 configured Message Areas. There are no other limitations to the unregistered version of the program. FidoPCB is classified as Shareware (US$ 39, or 62 Deutsch Marks for the 256 area version). The registered version has enhanced capabilities, as well as additional features. Registration and Price information can be found in the file ORDERFRM.DOC. You may also inquire via NetMail, or leave a message on the MicroArt BBS. LICENSE OF USE FidoPCB and its associated utilities are classified as Shareware, therefore you may operate the unregistered version for a reasonable period of time in order to evaluate its suitability to your needs. If, upon evaluation, you decide to use FidoPCB on a permanent basis, you are required to register your copy. Registration allows you to operate any current and future releases of FidoPCB version 1, including Beta Test releases. You can always obtain the latest Beta and Public release distribution archives from the MicroArt BBS. The FidoPCB distribution archives are also available from the FidoPCB Support Boards, but these systems are not obligated to make Beta releases available. Please inquire from the Support BBS SysOps as to their availability. Your registration also gives you access to the FidoPCB Support Conference on the MicroArt BBS, where you can share your experiences with other registered users, make suggestions, report bugs, and so on. vii FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual ───────────────────────────────────────────────────────────────────────────── CONTACTING THE AUTHOR Problems, questions, and suggestions about FidoPCB should be directed to Matjaz Koce via: Data: +38 66 34 986 [v.32bis] Mail: MicroArt d.o.o. +38 66 33 816 [v.32] Ferrarska 10 +38 66 37 536 [v.32bis] * 66000 Koper, Slovenia +38 66 37 499 [v.32bis] * +38 66 33 111 [Voice] * Open: 17:00-7:00 CET +38 66 34 986 [Fax] AdriaNet: Sysops, Shareware, HomeMadeSW Conferences FidoNet: FidoPCB, Enet.Sysop Conferences NetMail: 2:380/100@fidonet.org Salt Air BBS: Sysop Chat, Net_Mail, Utility, FidoPCB Conferences FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual 3 ───────────────────────────────────────────────────────────────────────────── SUMMARY OF FEATURES FidoPCB is a utility designed to import and export FidoNet type messages into PCBoard Message files, a process knows as Tossing. Messages are transferred between many different Bulletin Boards in a special packet format, referred to as the Fido FTS-2+. FidoPCB's features include: - Internal support for FrontDoor, InterMail, BinkleyTerm, D'Bridge, and TEMS Mailer software. - Create all the necessary handling files for FrontDoor and InterMail. - Create all the necessary handling files for BinkleyTerm. - Support for networks and multi-node PCBoard systems with file sharing. - Recognition of the CRASH, DIRECT, INTL and other message status flags. - Recognition of the ^aINLT and ^aFMPT flags for imported NetMail messages. - Unpacking of compressed packets received in ZIP, ARC, ARJ and LHA formats. - Importing of PKT files containing EchoMail from various areas into predefined PCBoard Message files, without intermediate conversion to MSG format. - Exporting of new messages from PCBoard message bases, and packing into FTS-2+ archives. - Handling of AreaFix commands (if you are a host, new areas can be connected or removed automatically) with connection security levels and passwords. - Bi-directional NetMail (private FidoNet mail) handling. - Recognition of PCBoard's "Private Message" flag. - Duplicate Message checking. - Support for up to 10 AKA Aliases. - Configurable as a Door (requires a Fossil driver). 4 FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual ───────────────────────────────────────────────────────────────────────────── LIMITATIONS As mentioned previously, unregistered versions FidoPCB will handle a maximum of 20 configured Message Areas (18 Message areas, 1 NetMail area, 1 Lost Mail area). On the other hand, when a Key File is used, FidoPCB will handle 256, 512, 1024 or more Message Areas, depending on your needs. If you are a Network Hub or an Echo Host, FidoPCB can process mail for a maximum of thirty (30) configured Nodes, when you set FILES=65 in CONFIG.SYS. The program will handle messages of up to 64Kb in size without difficulty. Future versions will be able to accommodate messages of unlimited size. FidoPCB does not check how much disk space is available. It is advised that you have at least 1Mb of free disk space available, although the actual amount of space you will actually require depends on the size of the packets you receive and send out, as well as on the number of configured Nodes and Message Areas. A minimum of 350Kb of free RAM is required, most of which is used to run archiver software such as PKUNZIP. For the exact memory requirements of your archive software, please check that program's User Manual. FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual 5 ───────────────────────────────────────────────────────────────────────────── INSTALLATION AND SETUP Sample Configuration files are included in the distribution archive, and should be used as a model for configuring FidoPCB for your BBS. Familiarity with PCBoard's Conference setup procedures is also necessary, as you will have to create at least two additional conferences in order to run FidoPCB. Installation is divided into four steps, of which the third is the longest. 1] Create the directory where you will be running FidoPCB in, and change to it. While the manual refers to the directory wherein FidoPCB resides in, as FIDOPCB, you may place the program files in any directory. Just remember that if you are placing the program files in another directory, you will have to substitute all directory references with the one you are using. 2.1] Extract the following files from the distribution archive into the directory created in step 1: FPCONFIG.EXE FIDOPCB.* FIDOPCB.DOC RUN??.BAT The distribution archive contains two sample configuration files: FIDOPCB.FD and FIDOPCB.BT. The latter is for use with the BinkleyTerm mailer only, whereas the former is meant for use with all other mailers. Whenever a reference to the FIDOPCB.CFG Configuration file is made in this manual, please refer to the proper version of this file. The manual also refers to the sample RUNFD.BAT file. For BinkleyTerm mailer users, all references should be made to the sample RUNBT.BAT file instead. 2.2] Extract the following either into the directory where you keep your message areas, or into the FIDOPCB directory: MATRIX.* LOST.* 3.1] Using the FPCONFIG Configuration program, edit the FIDOPCB.CFG Configuration file. For additional information on this program, please refer to the section devoted to it, later in this manual. You can also edit it with an ASCII text editor. If you choose this method, please note the following: All lines should end with a Carriage Return and Line Feed (CR/LF). Under no circumstances should you use CHR(9) (TAB) characters in the Configuration file. The sample Configuration file contains a brief description of all the commands and parameters. A more detailed description of the Configuration file can be found later in this manual. 6 FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual ───────────────────────────────────────────────────────────────────────────── 3.2] Load PCBSetup, and select J (Conferences) from the menu, in order to set up all of the conferences you specified in the Configuration file with the AREA parameter. Next, create an area where duplicate messages, and EchoMail for undeclared areas will be placed. The Message file name for this Conference must be LOST, and the path to it must be the one declared with the LOST_MAIL command in FIDOPCB.CFG. Finally, create an area where NetMail messages will be placed. The Message file name for this Conference must be MATRIX, and the path to it must be the one declared in FIDOPCB.CFG with the NET_MAIL command. 3.3] Log onto the BBS in order to create the respective Message files by using the J (Join) command to access the new conferences, and then log off. 3.4] Invoke FidoPCB using the SET ALL TOP parameters. This serves the double function of checking for errors in the Configuration, and to set the Last Message Read (LMR) pointers. If FidoPCB reports an error, repeat Step 3.1 3.5] Log onto the BBS and select one of the areas you created, and enter one or two messages in order to test your setup. 3.6] Run FidoPCB with the export parameter to export the test messages. 3.7] Check the results by looking in the directories specified with the PACKET and MAIL commands in FIDOPCB.CFG, and by examining FIDOPCB.STA. If nothing is there, you will have to repeat Step 3.1. 4] Add a command line invoking FidoPCB in your Mailer's batch file. 5] Install FidoPCB as Door (optional), If you are unable to set up FidoPCB, feel free to contact me, or one of the support sites listed at the end of this manual. We'll be there to help you. FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual 7 ───────────────────────────────────────────────────────────────────────────── COMMAND LINE PARAMETERS Invoking FIDOPCB.EXE without any command line parameters, or with the ? option will display all of the command line parameters on the screen. FidoPCB operates with very simple, intuitive commands, as Most of the information is read from the Configuration file. Syntax: FIDOPCB [?|command <areaname> <areanumber> [switch]] ? Displays a short description of all commands and switches Valid commands are: EXPORT, IMPORT, TOSS, SET, LIST, STAT, NOTIFY, REV Valid switches are: FORCE, RESET, STRIP i) Commands: EXPORT - Exports any new messages (since the last execution of FidoPCB), and updates the Last Message Read (LMR) pointers. IMPORT - Looks for new Mail Packet files in the directory specified with the FILES Configuration parameter, and imports them into the appropriate PCBoard message bases. It also updates the LMR pointers, without regard to the existence of messages requiring exporting. TOSS - Combines the functions of the IMPORT and EXPORT commands by processing any messages waiting to be exported, any Mail Packets waiting to be imported, and then updating the LMR pointers. SET - Sets the LMR pointer for a specific, or all configured areas, depending on the subcommand you use. If you wish to update the LMR pointer for a particular message area, you need to specify its name on the command line. If you wish to update the LMR pointers for all message areas, then the ALL parameter must be provided. Using the TOP parameter in place of a number will set LMR pointer(s) to the highest message in the conference message file(s). The LMR pointer can be advanced, but if the number provided is higher than the High Message number, then the pointer will be set to the High Message number. Negative numbers may also be used in order to roll the LMR pointer(s) back from the current value, by the number of messages specified. Command Syntax: SET <areaname>|<ALL> <number>|<TOP> LIST - Displays the current value of the LMR pointer of a specific message area, as well its traffic flow type. Substituting the areaname with the ALL parameter will display this information for all of the configured areas. Command Syntax: LIST <areaname>|ALL STAT - Displays message traffic statistics for all inbound and outbound mail. NOTIFY - Sends a listing of connected areas to your links. REV - Displays the version and revision number of your FidoPCB executable file. 8 FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual ───────────────────────────────────────────────────────────────────────────── ii) Switches: DOOR - Permits FidoPCB to operate as a stock PCBoard Door. In order to use this switch, you must have a Fossil Driver, such as X00 or BNU, installed. When using FidoPCB as a Door, the program will need to obtain operating information from PCBOARD.SYS. This switch can be combined with all the other commands and switches. RESET - Resets all Message Traffic statistics to zero. This switch is used with the STAT command. STRIP - Scans the messages being exported for any characters with a value of 127 (7Fh) or higher (known as High Bit Characters), and converts all occurrences into asterisks (*). This switch is used in combination with the EXPORT and TOSS commands. FORCE - Overrides checking for '* Origin:' lines, thus permitting messages with such lines (Received messages) to be sent out (Messages of this kind are skipped by default). As with the STRIP switch, this switch is also used in conjunction with the EXPORT and TOSS commands. iii) Examples: FIDOPCB LIST ALL - Lists all configured areas by name, their LMR pointer, and traffic flow types. FIDOPCB STAT - Shows import export statistics for all configured areas. FIDOPCB STAT RESET - Resets statistics for all configured areas to zero. FIDOPCB SET NET_MAIL TOP - Sets the LMR pointer for the NetMail conference (MATRIX) to the highest message number. FIDOPCB SET ALL -10 - Rolls the LMR pointers back by 10 messages for all configured areas. FIDOPCB SET FIDOTEST 1 - Sets the LMR pointer for the area called FIDOTEST to 1. FIDOPCB TOSS STRIP - Exports any new, unprocessed messages from PCBoard into message packets, converting all characters with a value above CHR(127) into asterisks (*). Then FidoPCB looks for unprocessed message packet archives, and imports the messages they contain, into PCBoard. Finally, outbound message packet archives are created and routed to those nodes defined in the Configuration file. FIDOPCB EXPORT FORCE - Exports any new messages from PCBoard into message packets, including messages with '*Origin:' lines in the message body, creates the outbound message packet archives, and routes them to those nodes defined in FIDOPCB.CFG. FIDOPCB IMPORT - Scans for unprocessed message packet archives, and imports the messages they contain, into PCBoard. FIDOPCB TOSS DOOR - Works like the TOSS command described above, but with the difference that output is sent to the Modem instead of a file. FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual 9 ───────────────────────────────────────────────────────────────────────────── CONFIGURING FIDOPCB The runtime configuration for FidoPCB is contained in the file, FIDOPCB.CFG. This file is a standard text file, and it should be created and edited with the FPCONFIG utility, or a standard ASCII text editor such as QEdit, PCWrite, or as a last resort, EDLIN. Never use Word Processors such as MicroSoft Word, WordStar or WordPerfect, as this type of program will place additional, unwanted characters into the file, and produce errors. The maximum length for any line in the configuration file is 1024 characters, with the exception of Directory paths, which are limited to 64 characters each. Lines starting with a semi-colon (;) are treated as comments and ignored. Commands are specified on a separate lines, and no TAB characters (CHR(9)) should be imbedded in them (use spaces instead. Do not leave any blank lines between commands. While these lines are ignored altogether, FidoPCB will wind up pointing to the wrong line number, in the event of an error in the Configuration file. Instead, simply place a semi-colon on these blank lines. In this fashion, FidoPCB will be able to point to the correct line. Any defined File paths must exist before FidoPCB is run, as the program will not create them if they are missing. Most of the commands have default values so it isn't necessary to use them in your Configuration file. The sample FIDOPCB.CFG included in the distribution archive, and reprinted later in this manual, should be used as a point of reference for their usage. The commands themselves, can be separated into several groups, some of are strictly connected. Any references to FrontDoor in this section, unless otherwise indicated, also applies to the InterMail Mailer. Commands fall into the following categories: i) File Paths: These commands define the location of specific files and work areas. Each string is limited to a maximum of 64 characters. Do not include associated filenames in the path strings, or end them with a back slash (\), as FidoPCB appends these as needed. ARCMAIL - destination of ARCMAIL (compressed mail packet) file attach messages. If you are using FRONTDOOR/INTERMAIL this should be the same as the MAIL directory. If you are using DBRIDGE it should be the \DB\QUEUE directory. BAD - Defines the path to which any incoming mail packets that could not be processed, are placed. FILE - Defines the path where your Front End places all incoming mail packets. LOST_MAIL - Defines the path to the Lost Mail Message file (LOST) is located. This message file is used to place messages for which no area has been defined, as well as any duplicate messages. The path to this message file must agree with the path defined in PCBSetup's Conference Configuration for this file (See step 3.2 under the section titled "Installation and Setup", earlier in this manual). 10 FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual ───────────────────────────────────────────────────────────────────────────── MAIL - Defines the path that corresponds to where your mailer finds the MSG files. MAILER - Defines the path to the Mailer directory. FidoPCB will put the appropriate semaphore files here. NET_MAIL - Defines the path to the NetMail Message file (MATRIX) is located. This message file is used for personal mail messages to and from your specific system. The path to this message file must agree with the path defined in PCBSetup's Conference Configuration for this file (See step 3.2 under the section titled, "Installation and Setup", earlier in this manual). PACKET - Defines the path where FidoPCB will place all of the outbound mail packets it creates. PCBOARD - Defines the path where FidoPCB will find PCBOARD.SYS. This path must agree with the one defined in PCBSetup for the location of this file. WORK - Defines the location of FidoPCB's work directory. If at all possible, this should be a RAM Disk, as it will provide even greater speed when processing mail packets. FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual 11 ───────────────────────────────────────────────────────────────────────────── ii) Archiver definitions: UNZIP, ARC, UNARC, ARJ, UNARJ, LZH ,UNLZH, ZIP - These commands are used to identify both the location and names of your archiving utilities. If you have already defined this location with the PATH environment variable, the use of these definitions is not required. The inclusion of command line switches is not necessary, as all the necessary switches have already been coded into FidoPCB. Syntax: <command> [<drive>:\[path]]<utility name> %a %f %a is the archive name %f is the file name (ZIP,ARC,ARJ,LZH) or the name of the work directory (UNZIP,UNARC,UNARJ,UNLZH) Defaults: If you don't use parameters, the defaults are: ZIP pkzip -M %a %f UNZIP pkunzip -O %a %f ARC pkarc -M %a %f UNARC pkxarc -R %a %f ARJ arj M %a %f UNARJ arj E -U %a %f LZH lha M %a %f UNLZH lha E /m %a %f iii) Switches: These commands are used to enable or disable features within FidoPCB, and in some cases, to choose a particular mode of operation of the feature. BELL - When enabled, causes FidoPCB to issue a beep over your system's Speaker if an error occurs during Packet processing. NOTE: Due to possible lockups under LANTastic or NOS 4.0, this switch should be set to off, if you're running either of these environments. If you experience lockups under other LAN environments, disable this switch. Options: ON, OFF Default: On CHECK_NAMES - this tells FidoPcb whether to unpack all received compressed packets or just those from declared nodes. Options: ON, OFF Default: Off COMPRESS - This command is used with each system declaration, and defines the compression method that will be used on Outbound EchoMail packets, and that is expected on the inbound EchoMail packets from the site associated with the definition. Options: ARC, ARJ, LZH, ZIP Default: Zip 12 FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual ───────────────────────────────────────────────────────────────────────────── DUPE_CHECK - Specifies the number of messages that will be checked for duplication in the areas containing the dupe flag, in the Area Declaration section of the Configuration file. FidoPCB checks the FROM, TO, SUBJ, DATE, TIME and ^aMSGID fields, as well as the first ten characters of each processed message. Duplicates are copied into the lost mail conference. Range: 1 - 9999 Default: 200 EXPORT_PRIVATE - If set to ON, FidoPCB will export all messages, whether they are marked private or not. If set to OFF, FidoPCB will export only public messages from echomail conferences. All MATRIX conference messages will be exported. Options: ON, OFF Default: On FLAGS - When disabled, forces FidoPCB to ignore any CRASH and IMM status flags that may be attached to NetMail messages. This is to keep regular users from sending Crash Mail to systems all over the world, if you allow public access to the NetMail area. Options: ON, OFF Default: On IGNORE_ECHO - When enabled, FidoPCB will export only those messages that have PCBoard's echo flag set. If disabled, then FidoPCB will ignore the state of this flag, and export all messages. Options: ON, OFF Default: On IMPORT_PKT - If ON, FidoPcb will look for PKT files in FILE directory (and not just in WORK directory) and process them. This is useful if you are using FrontDoor's /NOUNPACK switch. I recommend this for all FrontDoor users, since this will leave all mail processing to FidoPCB. Options: ON, OFF Default: On INTERFACE - Selects the Front End interface you are using on your system. Options: NONE, BINKLEY, FRONTDOOR, INTERMAIL, DBRIDGE, TEMS Default: None LEVEL_MATCH - Default is OFF. If set to ON, FidoPcb uses " = " (equal) condition when checking AreaFix areas access. If OFF, FidoPcb uses " =< " (equal or less) condition for AreaFix areas access. MAX_MSGS - Specifies the number of messages FidoPCB will export in a session. Range: 1 - 9999 Default: 9999 NET_TOSS - Selects the system to which NetMail will be sent. Setting this command to both will place NetMail in both FrontDoor and PCBoard. Options: PCBOARD, FRONTDOOR, BOTH Default: PCBoard FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual 13 ───────────────────────────────────────────────────────────────────────────── NETWORK - When running FidoPCB in a multitasking and multinode environments, this command enables File Locking. NOTE: If this command is enabled, SHARE.EXE must be loaded at boot time, otherwise you will create File Locking, Sharing Violation, and other errors on your system. Options: ON, OFF Default: Off PCB_VER - Defines the version number of PCBoard you area using. If set to 14.5 FidoPCB will use .NDX index files. If set to 15.0 FidoPCB will use .IDX index files. Options: 14.5, 15.0 Default: 14.5 iv) Strings: These commands are used to identify your system, as well as any messages originating from it. AKA - This command is used to assign an alias address by which your system can be known. Up to ten (10) aliases can be defined. This command connects to the AKA_TAG and AKA_DOMAIN commands. Format: Z:NNN/SSS.PPP (Zone:Net/Site.Point) AKA_DOMAIN - This command is used to declare a UUCP organization identifier. This identifier will be appended to the ^aMSGID flag of any messages sent out under the associated AKA command. The string can be up to 20 characters in length. Default: fidonet.org AKA_TAG - This command defines the tagline that will be appended to any messages sent out under the alias defined by the associated AKA command. DOMAIN - This command is used to declare a UUCP organization identifier. This identifier will be appended to the ^aMSGID flag of all messages sent out by your system, with the exception of those messages sent out under an alias (see AKA_DOMAIN, above). The string can be up to 20 characters in length. Default: fidonet.org ORIGIN - This command defines the main address for your system. Format: Z:NNN/SSS.PPP (Zone:Net/Site.Point) SYSOP - This command defines the name of the SysOp whose system is specified with the ORIGIN command. It is also used to define the name of the SysOp identified with the NODE command, in the System Declaration section of the Configuration file, for whose system, FidoPCB will create EchoMail packets. TAG - This command defines the tagline that will be appended to all messages sent out by your system, with the exception of those messages sent out under an alias (see AKA_TAG, above). 14 FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual ───────────────────────────────────────────────────────────────────────────── v) Message Area Definition: These commands are used to define the message areas your system will be processing. AREA - This command is the area declaration itself. It requires three parameters, and an optional flag. Syntax: AREA <number> <areaname> <path> [nomsgs|dupe] The number which makes up the first parameter corresponds to the current sequential message area. Its value may range from 1 to the limit of your version of FidoPCB. It is used by the NODE command in the Node Declaration section of the Configuration file. The areaname defined by the second parameter, is the EchoList name by which the current area is known in the network. The third and last required parameter is the path defined in PCBSetup, where the PCBoard message file is located in. The optional flag, NOMSGS, is used if the associated area will not be processed on your system, but passed on instead to other systems. If the DUPE flag is used, then all incoming messages for the associated area (up to the limit defined by the DUPE_CHECK command) will be checked for duplication. A control file consisting of 4 bytes per checked message will also be created for the area, in the same directory as the Message file. AREA_LEVEL - This command sets a security level for the associated area. It is referenced through the NODE_LEVEL command of the Node Declaration section of the Configuration file, when an AreaFix request is received to forward the area. Range: 1 - 9999 Default: 0 AREA_MSGS - This optional command is used if you wish to assign a name to the PCBoard Message file associated with this area. If this command is not used, the Message File name will default to MSGS. Either way, the filename must agree with the one you defined within PCBSetup. FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual 15 ───────────────────────────────────────────────────────────────────────────── vi) Feed Definition: These commands are used to define the systems with which your site exchanges EchoMail with on a regular basis. NODE - This command is the System declaration itself. It is followed by the network address, using the Z:NNN/SSS.PPP (Zone:Net/Site.Point) format, of the site with which you're exchanging EchoMail, and a list of the areas that are exchanged. The areas to be exchanged must be defined with the AREA command in the Area Declarations section of the Configuration file. Individual areas can be separated by commas, and consecutive areas can be ranged with hyphens. If you do not define any areas whatsoever, the packets created by FidoPCB will contain messages from all areas. NODE_LEVEL - This command is used to assign a security level to the associated site. The security level is used by AreaFix to forward only those areas assigned an equal, or lower security level under the AREA_LEVEL command in the Area Declarations section of the Configuration file. Range: 1 - 9999 Default: 0 PASSWORD - This command defines a password the associated site will be using in conjunction with AreaFix requests. The password itself is limited to twenty (20) characters. SYSOP - This command defines the name of the SysOp whose system is specified with the associated NODE command. It is also used to define the name of the SysOp identified with the ORIGIN command in the System Declaration section of the Configuration file. COMPRESS - This command defines the archiving method used to create the EchoMail packets for the associated site. FidoPCB will also expect all inbound packets from the site to be archived in this format. Options: ARC, ARJ, LHA, ZIP Default: Zip FLOW_TYPE - This command sets the status flag that will be applied to the outbound EchoMail packets that your system creates for the associated site. Options: NORMAL, HOLD, IMMEDIATE, CRASH Default: Normal USE_AKA - This command assigns the number corresponding to one of the alias address, UUCP organization identifier, and tagline sets, specified with an AKA, plus its related AKA_DOMAIN, and AKA_TAG commands. These will be applied to all messages in the EchoMail packets destined to the associated site, under the connected NODE command. 16 FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual ───────────────────────────────────────────────────────────────────────────── LOST MAIL HANDLING The LOST, and associated LOST.NDX files, are conventional PCBoard message files. FidoPCB will place into it any Echo- Mail that is destined to areas that have not been defined in the Configuration file. In addition, FidoPCB will also place any duplicate messages found during an import session into this message area. For these reasons, and because this area in particular is one of the means by which you're able to verify that your system is set up properly, you should be sure that it was set up with PCBSetup when you installed FidoPCB, and scan it occasionally. The area names attached to incoming messages are compared to the ones that have been defined in the Configuration file with the AREA command. If FidoPCB is unable to match area names (ie. the area name was not defined), the message associated with the area name in question will be tossed to the Lost Message area, and identified as being destined for an undefined area. This identification consists of the statement, AREA: <areaname>, being inserted in the first line of the message body. In this way, you can easily identify the area to which the message was destined, and either move it to the proper area, or kill it. When a message are being imported, there is a small chance that one or two may be duplicated. Should this happen, the duplicate messages are also placed in this area, and an identifier inserted in the message body. For duplicates, this identifier consists of the statement, DUPLICATE - AREA: <areaname>, being inserted on the first line of the message body. In this manner, you will be able to check the messages easily, and then move or kill them as necessary. FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual 17 ───────────────────────────────────────────────────────────────────────────── NETMAIL HANDLING The MATRIX, and associated MATRIX.NDX files, are conventional PCBoard message area files. FidoPCB will place into it any NetMail messages (private FidoNet messages) that are addressed to your system address. If you are using FrontDoor or InterMail as your mailer, FidoPCB will automatically scan for new MSG files. If any are found, and you defined NET_TOSS as either PCBOARD or BOTH, they will be imported into this area. Compressed NetMail messages are imported automatically without intermediate conversion into MSG files. Also, if FrontDoor or InterMail is your Mailer, and you set the NET_TOSS command to BOTH in the Configuration file, you should not use FM to read messages, as doing so will generate duplicate messages within the PCBoard Message area. When entering NetMail messages while logged into PCBoard, you must place the recipient's Network Address, enclosed in parenthesis, at the start of the first line of the message body, using the format, Z:NNN/SSS.PPP, where: Z = Zone number (Default = 2) N = Net number S = Site (Node) number P = Point number (optional) This is the only format FidoPCB will recognize. Messages that do not conform to this format will not be exported, and will cause unexpected errors. Exported messages are con- verted into the MSG format used by FrontDoor, and placed in the directory specified with the MAIL command in the Con- figuration file, from where they are routed by the mailer. Special flags may be added to a message. They are placed in parenthesis, at the start of the second line of the message body. FidoPCB recognizes the following flags: HOLD, IMM, CRASH and INTL. Multiple flags can be entered by separating them with commas, and no intermediate or trailing spaces. HOLD - Use of this flag signals your Mailer to hold the message on your system, for pickup by its recipient. IMM - Use of this flag signals your Mailer to forward the message immediately, along the normal distribution path. CRASH - Use of this flag signals your Mailer to deliver the message directly to its recipient. INTL - Use of this flag signals your Mailer to route the message via the Zone Gate for delivery. This applies only if your message will be delivered outside your zone, and therefore you should NEVER use this command in conjunction with the CRASH flag. 18 FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual ───────────────────────────────────────────────────────────────────────────── A sample NetMail message would look like this: To: Matjaz Koce From: Joe User Subject: Inter-zone NetMail ---------------------------------------------------------- (2:380/100) (INTL) This is an example of NetMail that will be sent from one zone to another, assuming "Joe User" is not in Zone 2. When FidoPCB imports newly received NetMail messages, the message header information is inserted in the message body, just above the message text, in order to facilitate your replies. This header information begins with the sender's network address, enclosed in parenthesis, using the Z:NNN/SSS.PPP format. Subsequent lines contain additional header information, including the contents of the ^aMSGID, ^aINLT, and ^aFMPT lines. If a NetMail message isn't entered correctly, FidoPCB will create a "warning" message, addressed to the user that improperly entered the message. If you don't like the default warning message, FidoPCB will use the contents of a text file, named MATRIX.ERR, to create the warning message. Place MATRIX.ERR in your FidoPCB directory. FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual 19 ───────────────────────────────────────────────────────────────────────────── FIDOPCB AND UUCP DOMAINS The UUCP family of networks are accessible to FidoNet, and vice-versa. You have the ability to send NetMail messages entered via PCBoard, into a UUCP domain, through FidoPCB. This is possible because until the message reaches the UUCP gateway, it is treated like any other. To send a message into a UUCP domain from within PCBoard, enter a message in your NetMail area, as you would any other (see the section titled, "NetMail Handling", earlier in this manual), but the message must be addressed to UUCP, in order for it to be forwarded into the UUCP domain. On the first line of the message body, enter the Fido address of the UUCP Gateway that handles mail for your Net, using the standard NetMail Message addressing format. If your Net doesn't have an assigned Gateway, you must route the message via 1:1/31. This completes the Fido side of the message format. In column 1 of line 2 of the message body (or line 3, if you inserted a status flag), enter the UUCP address of the intended recipient, using the format, To: <USER>@<SITE>.<DOMAIN>. Skip two lines to complete the message header, and begin the text of the message you wish to send. When FidoPCB exports your message, the Gateway's address and any status flags are removed from the message body. The UUCP routing line is moved up to the first line of the message, which is where most UUCP Gating software expects to find it. If there is a problem with the message, it will be returned as undeliverable. A sample inter-domain message would look like this: To: UUCP From: Matjaz Koce Subject: Fido->UUCP Mail ---------------------------------------------------------- (1:1/31) To: netbuddy@goodtime.uucp This is an example of NetMail that will be sent to user, "netbuddy" at a UUCP site called, "Goodtime". It is routed into the UUCP domain by the UUCP gate at 1:114/15. In order for someone in a UUCP domain to send you NetMail, the sender doesn't need to know any specific gateways to FidoNet. As long as the message is addressed to the FidoNet domain, it will be delivered to you automatically. A Fido domain address uses the format: <FIRST>.<LAST>@[p<POINT>.]f<SITE>.n<net>.z<ZONE>.fidonet.org Point addresses should only be used if the recipient has one. 20 FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual ───────────────────────────────────────────────────────────────────────────── A message sent from a UUCP domain would be addressed like this: From: netbuddy@goodtime.uucp To: matjaz.koce@f100.n380.z2.fidonet.org Subj: UUCP->Fido Mail ---------------------------------------------------------- This is an example of a message entered at a UUCP site, that will be sent to Matjaz Koce at 2:380/100 via the closest Fido gateway. A final word about mail in a UUCP environment. Never use mixed case on a UUCP style address, as they will cause messages to go astray or get lost. The only valid, mixed case statement in a UUCP address, is the To: Keyword. Likewise, replace any spaces in a UUCP address, with periods, as any characters following a space will be ignored. FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual 21 ───────────────────────────────────────────────────────────────────────────── RUNNING FIDOPCB AS A DOOR One of the advantages FidoPCB has to offer, is the ability to run as a BBS Door. This allows both you and your users to process mail independently from your Mailer, and from other events. In order to do this, you need to have a Fossil Driver, such as BNU or X00, loaded. You also need to have a current copy of PCBOARD.SYS residing in the directory defined with the PCBOARD configuration command, in order to obtain supplementary information when operating in Door mode. On the PCBoard side, you need to enter PCBSetup Conference options screen for the conference(s) in which you wish to use FidoPCB as a Door in, and enter Door Path Editor. The PASSWORD and SECURITY options may be set as you desire, while the LOGIN, USER.SYS and DOOR.SYS options must be set to NO. For best results, the SHELL option should be set to either YES or SWAP. The reason for this is that when you exit PCBoard completely, the last command in the batch must reload PCBoard. In situations where a Front End is in use, it may be necessary to reload the BBS in a particular fashion, and the possibility of an inadvertent, incorrect call to the wrong batch file may take place. By shelling or swapping, this danger is eliminated completely. Next, create a batch file to invoke FidoPCB in the directory you specified for the location of the file. You can do this from within the Door Path Editor, by highlighting the door name, and pressing the F2 key to load the editing utility you defined for use with the PCBoard setup programs. The batch file is constructed in the same way as any other Door batch file would be, and should contain at the very least, provisions to change to the directory where FidoPCB is located, and to invoke FidoPCB with the toss door options. As with normal operation, FidoPCB will also generate the FrontDoor or InterMail semaphore files when running in Door mode. This is a function which is of particular help in the case of multinode systems. NOTE: You might want to restrict access to FidoPCB if you are using it in Door mode in order to prevent its abuse, and also to keep dummy NetMail or duplicate messages from circulating around the world. Remember that if a NetMail message contains the CRASH flag, the destination system will be called directly (and that can be an expensive proposition)! The ideal solution is to only permit a few, trustworthy and reliable users, to have a security level that is high enough to access the door. 22 FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual ───────────────────────────────────────────────────────────────────────────── USING AREAFIX AreaFix commands are active when you're operating as an Echo Host, or a Network Hub. Only systems declared in the Configuration file are allowed to access the commands, permitting them to list, select and deselect areas that you have available on your system. All of these functions can be performed by simply sending a NetMail message. When sending a message to AreaFix from within PCBoard, it must be addressed to AREAFIX, and bear an AreaFix command as the message subject. At the moment, FidoPCB's internal AreaFix only supports the -q command, and therefore this is the only valid command that may be sent to a Hub running FidoPCB. Stand alone AreaFix systems support additional commands (please check with your Hub SysOp to find out which commands are valid). If a node was assigned an AreaFix password, the AreaFix command must be preceded by this password on the Subject line. If this isn't done, then FidoPCB's AreaFix will respond as being unavailable to the node. When entering the message in PCBoard, it begins as any other NetMail message, with the recipient's network address enclosed in parenthesis at the start of the first line of the message body, using the Z:NNN/SSS.PPP format. Only one entry per line is permitted. Every AreaFix message must end with a tearline, but unless you are entering the message with your Mailer's editor, you do not need to add one at the end of the message, because FidoPCB automatically inserts a tearline when exporting messages from PCBoard. By specifying an Area name on its own, or preceding it with a Plus symbol (+), AreaFix will add the Area name in question to your area selections list. If the Area name is preceded with a Minus symbol (-), AreaFix will remove that Area name from the area selections list. These are, in essence, instructions to AreaFix. A sample AreaFix message entered within PCBoard, looks like this: To: AreaFix From: Matjaz Koce Subject: fidopcb -q ---------------------------------------------------------- (2:380/100) -SYSOP.033 -NET_DEV +CLIPPER Fidopcb FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual 23 ───────────────────────────────────────────────────────────────────────────── When FidoPCB processes your AreaFix message, it will add or delete the areas you specified from your area selections list, and respond with a message like this: From: Fidopcb(AreaFix) Date: 22 Jun 92 To: Matjaz Koce Time: 22:32:11 Re: Node change request ---------------------------------------------------------- MSGID: 2:380/100@FIDONET.ORG 7116606c This report was generated by AREAFIX command Areas available to 2:380/101.0 on 2:380/100.0 (level 100): [1] Area name Level [2] --------------------------- * SYSOP.033 0 * NET_DEV 0 NETSYSOP.333 100 * ENET.SOFT 110 * VIRUS_INFO 110 ENET.SYSOP 10 FIDOPCB 10 CLIPPER 0 From total 7 areas, 4 are selected for you (marked with '*'). Action Area Name [3] ------ ------------------------ Dropped SYSOP.033 Dropped NET_DEV Added CLIPPER Added FIDOPCB --- FidoPCB 1.3 [NR] ------------------------------------------------ [1] The level listed on the available areas line, is the level defined with the NODE_LEVEL command. [2] The level listed after an Area name, is the level defined with the AREA_LEVEL command. [3] The Actions portion of the message indicates what changes were made to the area selections list, based on the instructions you included in the message. 24 FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual ───────────────────────────────────────────────────────────────────────────── THE FPCONFIG UTILITY FPCONFIG is a Configuration File Editor for FidoPCB. You can use it to create a new Configuration file, or edit an existing one. The discussion of FidoPCB commands in this section is brief, as they have been discussed in detail, earlier. Detailed help is always available by pressing the F1 key within the editor. In addition, the following keys facilitate navigation within the program: - To move between fields: L-Arrow, R-Arrow,Dn-Arrow, Up-Arrow, Home, End, Tab, Shift+Tab - To confirm fields: Enter - To bring up Picklists: F2 - To move between input screens: PgUp, PgDn - To erase lines: ^Y - To restore previous field content: ^U - Hot keys: Alt+highlighted letter In order to load the Configuration editor, the path and the name of PCBoard's Extended Conference file, CNAMES.@@@, must be specified. Syntax: FPCONFIG [d:[path]]CNAMES.@@@ [/m] Switch: /M - Forces monochrome mode. After loading, FPCONFIG will scan the current directory for the existence of a FidoPCB Configuration file (FIDOPCB.CFG). If the file exists, then the parameters for the various commands will be loaded. For those commands that have not been included, their respective defaults will be assumed. Should no Configuration file exist, you will be asked if you wish to proceed with a blank configuration. Choose YES to create a new file. At this point the program will display a list of configurable sections. Use the arrow keys to select the section you wish to edit. After completing the configuration, press the ESC key to exit the program. You will be asked if you wish to save the changes. These will be written to FIDOPCB.NEW, which can later be renamed to FIDOPCB.CFG. If you are editing an existing Configuration file, the suggested procedure is: FPCONFIG FIDOPCB TOSS COPY FIDOPCB.NEW FIDOPCB.CFG FIDOPCB SET ALL TOP i) GENERAL INFORMATION: This option requests information about your system. If you registered FidoPCB, then the information stored in the Key File overrides some of these options. ii) ARCHIVERS: This option requests the path and names for the various utilities which FidoPCB uses to create and extract Mail archives. You don't have to specify any of these utilities if their location has been defined with a path environment variable. FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual 25 ───────────────────────────────────────────────────────────────────────────── iii) AKA's: This option lets you assign aliases by which your system is known. With the current version of FPCONFIG, you can declare up to 10 aliases, along with their associated taglines and UUCP Organization identifiers. To declare additional aliases, you will have to edit the Configuration file manually. iv) AREAS: This option lets you assign the EchoMail areas you will be carrying on your system. Although FidoPCB itself will handle the number of conferences allowed by your Key File (or 20 when unregistered), the current version of FPCONFIG will only handle 1024 areas. Additional areas can be added manually to the Configuration file. Press the ENTER key on a field in order to bring up the Area Editor. Pressing F2 on the NAME, FILE or PATH fields, will allow you to copy the information from the PCBoard Extended Conference picklist, into the Configuration file. ESC will close the picklist. v) NODES: This option lets you define up to 30 nodes with which your system will be exchanging messages. Press the ENTER key while in the Node Declarations screen to define a node. After the definition has been completed, you will be returned to the Declarations screen. At this point, press F2 to bring up the Areas picklist. This picklist contains the areas you defined previously. To make a selection, highlight the area you wish to add, and press the SPACEBAR to toggle it. Selected areas will be marked with a check mark (√). You can deselect marked areas in the same fashion. To return to the Declarations screen, press the ESC key. 26 FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual ───────────────────────────────────────────────────────────────────────────── COMMON QUESTIONS Q: When I run FidoPCB, it exports mail without a hitch, but it doesn't see archives sent by my hub. How come? A: There are several archive naming conventions available to FidoNet technology. FidoPCB uses the FTS-2+ convention. If this problem occurs, chances are that the archive name is not in this format. First, make sure that your hub is using FTS-2+ naming. Next, extract the PKT files contained in the archive to the directory specified by the WORK command and try to import them with FidoPCB. Assuming this works, and your hub is sending FTS-2+ archives, the error is in the Node number defined in FIDOPCB.CFG, for that site. Q: How do I determine the correct FTS-2+ archive names expected by FidoPCB? A: The prefix name is composed of hexadecimal values calculated from the Region, Net and Node numbers involved, and the extension consists of the day of week plus a packet number. The prefix is composed of two values of four characters each, the first representing the Region and Network, the second representing the Node number of the destination. To obtain the first value, the recipient's Network number, is subtracted from the sender's, and the result is then converted to a Hexadecimal value. For the second value, the recipient's Node number is subtracted from the sender's and converted to Hexadecimal. For example, if the sender is 1:273/214, and the recipient is 2:380/100, the packet prefix would be FF950072, and 006DFF8E going the other way. This breaks down as follows: 273-380 = -107 or FF95h, and 214-100 = 114 or 0072h 380-273 = 107 or 006Dh, and 100-214 = -114 or FF8Eh The extension consists of the first two letters for the day of week, followed by the packet number for that day. For example, SU0 would be the first packet on a sunday, or FR3 would be the fourth packet on a Friday. Q: FidoPCB doesn't see inbound Message Archives, and yet their names conform to the FTS-2+ standard, and are the ones FidoPCB expects to receive. What is wrong? A: This problem occurs when you use the FrontDoor Mailer, and invoke it with the /nounpack switch. This switch causes FrontDoor to not process incoming Message Archives. Remove this switch, and things should work properly. Q: Does FidoPCB work with operating systems other than MS-DOS? A: Absolutely! While most SysOps use Microsoft's MS-DOS, version 3.0 or later, some use other operating systems, such as Novell's DR-DOS v6.0 on their computers. FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual 27 ───────────────────────────────────────────────────────────────────────────── Q: When FidoPCB tosses messages to the BBS, they wind up in the wrong conference, or in the Lost Mail area. Why? A: The problem lies in the Area declarations section of your configuration file. In the case of messages being placed in the wrong conference, you should check the path and optional filename you specified, against the ones defined in PCBSetup. Messages that end up in the Lost Mail area, usually do so because the area they belong to, has not been defined in FIDOPCB.CFG. Q: Can the Area Declarations in FidoPCB be assigned any number, so as to coincide with the respective Conference numbers within PCBoard? A: This is not a recommended practice. While feasible, it can lead to unpredictable results. For ease of mind's sake, it would be better to start your Area Declarations with 1, and be increment them sequentially. Q: Does FidoPCB support File Request and File Attached messages? A: At the moment, these types of messages are not supported internally. It is possible that these features will be included in a future release. Q: Is FidoPCB capable of sensing the compression method used on inbound archives from undeclared systems, and using the correct extraction utility to process them? A: No, this is a feature that will become available in a future release, but since FidoPCB is only capable of processing mail archives from declared systems, archives from undeclared sites need to be processed manually in any case. Q: How large is the control file that is created when the DUPE flag is set, and where is it created? A: The Duplicate Message control file generated by FidoPCB, uses the same root name as the message file, but has a .DUP extension, and is located in the same directory as the Message Files. It consists of 4 bytes per checked message, with the number of messages checked, corresponding to the value assigned to the DUPE_CHECK command. For instance, if you specify that 200 messages be checked, each control file will take up 800 bytes of disk space. 28 FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual ───────────────────────────────────────────────────────────────────────────── SUPPORT AND DISTRIBUTION A support echo for FidoPCB has been established, and is carried by most FidoPCB support sites. The network of FidoPCB support and distribution sites all carry the latest Shareware release version of FidoPCB. Most sites also distribute FidoPCB Beta releases to registered users. If you encounter any problems with the program, simply join the support conference. The Support SysOps, my partners and myself, are here to answer your questions. All we ask is that you be patient for your answer, due to the intercontinental nature of the support echo. Here is the list of FidoPCB support sites around the world: COUNTRY BBS NAME ADDRESS TELEPHONE PROTOCOL SYSOP Slovenia MicroArt BBS 2:380/100 +38 66 349-86 V.32b Gregor Rudolf MojsteR BBS 2:380/101 +38 68 237-31 V.32b Matjaz Potrc Italy Fido_TS_1 2:333/603 +39 40 378-3111 HST/DS Pietro Budicin USA The Corner Pub 1:18/14 703 963-3878 V.32b Jeffrey Boyd Olympus 1:271/265 804 595-0117 HST/DS Frank Royalty Second Sanctum 1:130/69 817 784-1178 HST Mark Robbins ASA CompuHelp 1:226/600 614 476-3723 V.32b Jeff Binkley LiveWire Online 1:2320/110 502 933-4725 HST/DS Allen Prunty Shareware Depot 1:157/561 216 886-2321 HST/DS Don Patrick Modern BBS 1:273/730 215 638-1299 V.32b Rick Kosick Canada SMARTalec 1:250/114 416 763-5019 V.32b Glenn Menzie Akasha's Emporium 1:163/403 613 744-5750 V.32b Susan Duncan FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual 29 ───────────────────────────────────────────────────────────────────────────── CREDITS The author would like to extend special thanks to the following people, who have assisted various ways in order to make FidoPCB possible: - All Support Sites. - Gregor Rudolf, who helped me with advice. - Damjan Pavlovec, Matjaz Potrc, George Silberstern, and Mike Waldron, for their help with the documentation. - George Silberstern, for starting USA FIDOPCB Support and working with the documentation. - Mosaic v1.0 and other PCBoard mailer/tossers. Their bugs, slow processing, and other shortcomings made me feel so awful, that I decided to write a tosser/scanner of my own. 30 FidoPCB: FidoNet to PCBoard 15.x mail interface - User's Manual ───────────────────────────────────────────────────────────────────────────── GLOSSARY FIDONET - An amateur, worldwide network of over five thousand Computer Bulletin Boards of all types, dedicated to the interchange of messages. The network was started in San Francisco, Ca. in 1984 by Tom Jennings and John Madill. FTS - Acronym for Fido Technical Standard. FTS standards define the format of various aspects of FidoNet interactions and protocols, including EchoMail (FTS-4), Nodelist formats (FTS-5), Addressing formats (FTS-2), and so forth. FOSSIL - Acronym for Fido/Opus/Seadog Standard Interface Layer. It is a memory resident program that works with a computer system's Serial Communications hardware. HUB - A system on the FidoNet Network that routes messages to other systems. LMR - Acronym for Last Message Read. A pointer to the last message number processed (or read, depending on the use) by a reader or mail managing utility. NODE - An individual BBS system in the network. Also refers to individual dial-in lines of a multi-user system. PASS-THROUGH - A message area that is not received for publication on the system handling it, but that is sent along to another system in the network. POINT - FidoNet node serving an individual end user, who receive large quantities of NetMail and EchoMail, but don't necessarily terminate in a BBS. SHAREWARE - Software that has been released to the public for use over a specific trial period. If after this trial period, the user continues to use the software, the user purchases a registration license from the author(s). UUCP - Short for Unix to Unix CoPy. An electronic network messaging format, similar in capability to that of FidoNet, but usually running on Unix or Xenix based systems, and funded by various Educational, Government and Corporate institutions. Several networks use the UUCP messaging format, including USENET, Internet, ARPANet and Bitnet. ZONE GATE - A Hub on the FidoNet network that transfers messages and mail between Network regions. FidoNet currently consists of five regions: Region 1 covers the United States and Canada. Region 2 covers the European Continent. Region 3 covers Oceania (Australia, New Zealand and the Pacific Island Chains). Region 4 covers Central and South America. Region 5 covers the African Continent. Region 6 covers Asia and the Far East. Other Zone numbers are used for networks that use Fido Technology to interchange messages, and can also be gated (tied into) FidoNet.