ftp.wwiv.com

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

/ ftp.wwiv.com / ftp.wwiv.com.zip / ftp.wwiv.com / pub / BBS / 515DISK2.ZIP / DOC515.ZIP / 515-GB.DOC next >

Wrap

Text File | 1993-03-06 | 276KB | 10,883 lines

SERVER AND BBS SOFTWARE FOR THE PACKET RADIO MULTIPORTS, MULTICONNECTION, MULTILINGUAL F6FBB, Jean Paul ROUBELAT TABLE OF CONTENTS ----------------- Page 1 ACKNOWLEDGMENTS ........................................ 4 2 COPYRIGHT .............................................. 5 3 FEATURES ............................................... 6 4 CONTENT OF THE DISTRIBUTION DISK ....................... 8 5 FIRST-TIME INSTALLATION AND SETUP ...................... 12 5.1 First-time setup of different files ........ 15 5.2 APPEL.BAT .................................. 16 5.3 INIT.SRV ................................... 17 5.4 EPURMESS.INI ............................... 25 5.5 PORT.SYS ................................... 27 5.6 SWAPP.SYS .................................. 29 5.7 INITTNCx.SYS ............................... 30 5.8 MAINTx.SYS ................................. 31 5.9 BALISEx.SYS ................................ 32 5.10 BBS.SYS .................................... 33 5.11 FORWARD.SYS ................................ 34 5.12 Start the BBS for the first time ........... 37 5.13 TNC. ....................................... 38 5.14 PK-232 in host-mode. ....................... 39 5.15 Kantronics KAM in host-mode. ............... 40 5.16 DRSI-card. ................................. 41 5.17 G8BPQ-node (uses TNCs in KISS-mode). ....... 43 6 BBS COMMANDS ........................................... 45 7 SERVER COMMANDS ........................................ 51 7.1 Main menu .................................. 51 7.2 Connections-Stats .......................... 52 7.3 Documentations ............................. 53 7.4 Directory/Callbook ......................... 54 7.5 QTH-Locator ................................ 55 7.6 Satellite Orbital Computation .............. 56 8 SYSOP COMMANDS ......................................... 57 8.1 BBS menu commands .......................... 57 8.2 Other commands ............................. 61 9 FBBDOS COMMANDS ........................................ 62 10 CONSOLE COMMANDS ...................................... 65 11 TEXT VARIABLES ........................................ 67 11.1 Variables definitions ..................... 67 11.2 Variables list ............................ 68 12 FULL SCREEN TINY EDIT ................................. 70 13 EMS and XMS ........................................... 72 13.1 EMS ....................................... 72 13.2 XMS ....................................... 73 13.3 FBB and additional memory ................. 74 13.4 Choice of add-on memory ................... 74 FBB 5.15 Feb 06 1993 Page - 1 14 ASYNC PORT DRIVERS AND TELEPHONE MODEM ................ 75 14.1 ESS.COM ................................... 75 14.2 FBBIOS.COM ................................ 76 14.3 TELEPHONE MODEM ........................... 77 15 MISCELLANEOUS TOOLS ................................... 81 15.1 INSTAFBB.COM .............................. 82 15.2 EPURMESS.COM .............................. 83 15.3 EPURWP.COM ................................ 85 15.4 LOGSTAT.EXE ............................... 86 15.5 SATUPDAT.EXE .............................. 87 15.6 SLEEP.COM ................................. 92 15.7 TLABEL.COM ................................ 93 15.8 MAKEPG.COM ................................ 94 15.9 SETUSER.COM ............................... 95 15.10 CLEANUP.COM ............................... 96 15.11 MAINTINF.COM .............................. 97 15.12 MAINTREJ.COM .............................. 98 15.13 CUT.COM ................................... 99 16 WHITE PAGES DATABASE AND SERVER ....................... 100 16.1 DESCRIPTION ............................... 100 16.2 UPDATE REQUESTS ........................... 101 16.3 DATABASE DESCRIPTION ...................... 101 16.4 DATABASE MANAGER .......................... 102 16.5 EPURWP AND UPDATE MESSAGES ................ 102 16.6 WP SERVER REQUESTS ........................ 103 17 SERVERS ............................................... 104 17.1 REQDIR .................................... 105 17.2 REQFIL .................................... 106 17.3 NEWDOC .................................... 107 17.4 REQCFG .................................... 108 18 OTHER FILE-formats (continued from section 5).......... 110 18.1 PORT.SYS .................................. 111 18.2 CRON.SYS .................................. 112 18.3 REJET.SYS ................................. 115 18.4 PASSWD.SYS ................................ 116 18.5 PROTECT.SYS ............................... 117 18.6 LANGUE.SYS ................................ 118 18.7 FORWARD.SYS ............................... 120 18.8 x.TXT, x.HLP, x.ENT, x.INF ................ 128 18.9 FBBLOG.nn ................................. 129 18.10 DIRMES.SYS ................................ 131 18.11 STATIS.DAT ................................ 132 18.12 WFBID.SYS ................................. 133 18.13 INF.SYS ................................... 134 18.14 HROUTE.SYS ................................ 135 18.15 YAPLBL.SYS ................................ 136 18.16 MEMO.SYS .................................. 137 18.17 SATEL.DAT ................................. 138 18.18 nnnnn.SAT (characteristics) ............... 139 18.19 WP.SYS .................................... 140 18.20 MESS.WP ................................... 141 FBB 5.15 Feb 06 1993 Page - 2 APPENDIX ................................................. 142 APPENDIX 1 : EDIT Commands ...................... 142 APPENDIX 2 : PK232 Host-Mode .................... 144 APPENDIX 3 : PROCESS NUMBERS AND HELP ........... 145 APPENDIX 4 : RECORDING A MESSAGE ................ 146 APPENDIX 5 : TRICKS AND TIPS .................... 147 APPENDIX 6 : FBB FORWARD PROTOCOLE .............. 148 APPENDIX 7 : COMPRESSED FORWARDING .............. 151 APPENDIX 8 : FORMAT OF ACK MESSAGES ............. 153 APPENDIX 9 : REPLACEMENT CHARACTERS OR WILDCARDS. 154 APPENDIX 10: PROGRAMMING TECHNICS FOR SERVERS ... 155 APPENDIX 11: CONTENTS OF THE DIRECTORIES ........ 159 APPENDIX 12: CONNECTION FILTERING ............... 161 APPENDIX 13: MESSAGE FILTERING .................. 163 APPENDIX 14: PG PROGRAMS DEVELOPMENT ............ 165 APPENDIX 15: UNPROTO MESSAGE LISTS .............. 167 APPENDIX 16: EXTENSIONS TO THE YAPP PROTOCOLE ... 169 FBB 5.15 Feb 06 1993 Page - 3 1 ACKNOWLEDGMENTS: ------------------ I would like to particularly thank Patrick FC1GHV and Per LA6CU, who have helped me to achieve and set up this software, debugging and documentation, as well as Claude FC1CDC, the "dumb individual", who, with his advices and criticism (often vitriolic!), has given his support over more than four years in the achievement of this task. I would like to thank, as well, all the programmers for the development of applications and complementary tools for this software. Such a support made me free of these tasks, very often ingrate. I thank again all the SYSOPS and users who are confident in the product, and cooperate, thanks to their comments and suggestions, in improving this BBS software package. I would like, at the end, to thank WA8DED for the excellent piece of software, the Host-Mode for the TNC, and also NORD><LINK for the additions made to it. FBB 5.15 Feb 06 1993 Page - 4 2 COPYRIGHT: ------------ This software is delivered at no cost and is free of all charges. It can be freely copied or installed for any HAM-RADIO application. Any other usage for commercial, professional, or industrial purposes is forbidden. Despite the free sharing nature of this product, a participation to the investment and to the mailing cost at the level of 100 FF or 20 US Dollars (or more) would be most welcome. The author can be contacted by mail at the following address: Jean-Paul ROUBELAT 6, rue George SAND 31120 ROQUETTES FRANCE FBB 5.15 Feb 06 1993 Page - 5 3 FEATURES : ------------ The usage of this software is very close to the one made by WA7MBL, whose commands have been kept. It has also a set of specific and original supplementary commands. - Works on any 100 % compatible XT or AT PC fitted with a hard disk and 640 k RAM, monochrome CGA or EGA VDU, 1 up to 8 serial ports. This software allows user-customized colours but works also without any modificati monochrome adapter. - Multiconnections: up to 50 simultaneous channels on 8 TNC (4 or 8 channels per TNC depending on the software used). - Multiplexing: this software supports usage of an external MUX and supports also extension boards in the case of a hardware configuration having more than 2 ports. The MUX connects 4 TNC on 1 serial port, either com1 or com2. Printed board is available from the ATEPRA association, (ATEPRA, 23 rue de Provins, 77520 MONS EN MONTOIS - FRANCE). Operates: - with any TNC2 or clone fitted with the special 27256 eprom containing the WA8DED firmware, or TF4/TF8, with a Z80 clock of 2.5 or, better, 4.9 MHz. - - with a PK232 in Host-Mode (but TFPK software, WA8DED hostmode for PK232 works greater !). - with a G8BPQ node. - With a KAM hostmode (I seem to have still some problems). - Standard BBS: it is a BBS identical to the WA7MBL or W0RLI. It has also server functions (computation of satellite orbits, callbook, and operator customizable chapters, gateway to an other channel, the users being able to chat together in real time on the same or different channels, etc...). - Forwarding: with the other BBS WA7MBL type or compatible, BIDS management (up to 2000 of them, or more depending on a parameter, are saved in a separate file), a BID is automatically generated should the user doesnt provide if. Private message works with the management of MID. The messages are suppressed automatically after a delay which can be user defined. This is true for bulletins and private mail. - The forwarding is optimized between BBS using FBB protocole type. It is more efficient on a VHF/UHF network. This kind of forwarding can be disabled by configuration. - The compressed forwarding allows the reduction by a factor of about 40-50% the quantity of data to exchange in big messages. The messages are protected by checksums, then the transfer is made error-free. - The forwarding is simultaneous on the various ports regardless they are incoming or outgoing. There might be several forwardings outgoing per port which number is set by parameter. The number of incoming forwarding is a function of the available channels. The time and the period of forward can be set separately on each port. - The hierarchical routing is supported. - The ping-pong phenomenon is automatically detected and an information is given to the sysop by a system message. - Messages and bulletins for SYSOP are duplicated to a destination call which can be defined by configuration. FBB 5.15 Feb 06 1993 Page - 6 - A detailed log of the BBS activity is maintained and a statistic analysis program, written by FC1MVP, is also available. - Binary transfer is supported with the usage of the YAPP protocol of WA7MBL. An extension to this protocol has been made, including the automatic restart and the checksum, should a stop has occurred or a disconnection took place during the transfer. This extension to the protocol works with the TPK, packet terminal program written by FC1EBN. - Gateway between connected stations or with another port. - Conference within the limits of the available ports and channels. - Language: at the first connection, the connect language is attributed to the user, depending of the callsign. - Remote SYSOP operation is supported and the housekeeping of the BBS messages, mail and old mail is done each and every night at low activity period which can be parametered, and is done automatically. - Works under DesqView. FBB 5.15 Feb 06 1993 Page - 7 4 CONTENTS OF THE DISTRIBUTION DISK. ------------------------------------ Directory of C:\515\DISK1 INSTA515 BAT 120 28.03.92 20:27 FBB515 ZIP 2454 06.03.93 14:27 514515 BAT 120 18.08.91 12:40 BIN515_2 ZIP 235835 06.03.93 14:27 READ ME 528 13.02.93 15:46 FBBMUX 2190 05.03.93 20:17 PKUNZJR COM 2750 28.12.92 2:04 FWD515 ZIP 626 06.03.93 14:27 STAT515 ZIP 39800 06.03.93 14:27 SYS515 ZIP 5844 06.03.93 14:28 SUITE1 BAT 4491 05.03.93 22:08 SUITE2 BAT 7814 05.03.93 22:10 Directory of C:\515\DISK2 DOC515 ZIP 127982 06.03.93 14:28 BIN515_1 ZIP 197029 06.03.93 14:28 SAT515 ZIP 18420 06.03.93 14:28 Directory of C:\515\DISK3 LANG515 ZIP 199993 06.03.93 14:28 FIRMWARE ZIP 138645 06.03.93 14:28 Directory of C:\515\DISK1\BIN515_2 SERV BIN 562941 06.03.93 14:26 Directory of C:\515\DISK1\STAT515 LOGSTATF EXE 39152 23.01.93 18:31 LOGSTATU EXE 39136 23.01.93 18:39 LISEZMOI DOC 8212 23.01.93 18:51 LOG DOC 918 23.01.93 18:53 LOGCALL EXE 11200 13.09.92 17:24 LOGFBB CNF 358 23.01.93 18:57 FBB 5.15 Feb 06 1993 Page - 8 Directory of C:\515\DISK1\SYS515 BALISE1 SYS 89 22.03.92 2:05 BALISE2 SYS 81 22.03.92 2:05 INITTNC DED 47 15.08.90 11:49 INITTNC PK 44 08.12.90 16:50 INITTNC1 SYS 45 16.12.91 23:03 INITTNC2 SYS 34 13.10.91 20:02 LANGUE SYS 807 05.03.93 20:48 CRON SYS 1009 22.03.92 0:33 MAINT1 SYS 61 22.03.92 0:49 MAINT2 SYS 61 22.03.92 0:49 SWAPP SYS 473 05.03.93 20:12 PROTECT SYS 159 26.08.90 12:49 MEMO SYS 143 11.12.91 22:24 FORWARD SYS 215 05.03.93 20:01 BBS SYS 584 05.03.93 20:01 PASSWD SYS 766 05.03.93 20:03 PORT SYS 2604 05.03.93 20:08 REJET SYS 515 05.03.93 20:11 Directory of C:\515\DISK1\FBB515 INIT SRV 3502 05.03.93 19:52 NEWDOC SYS 14 10.02.91 12:54 EPURMESS INI 1406 05.03.93 19:53 Directory of C:\515\DISK1\FWD515 AMSAT 86 27.05.91 19:02 F6ABJ 491 13.10.91 20:00 LA6CU 244 13.10.91 9:26 Directory of C:\515\DISK2\BIN515_1 APPEL BAT 1231 22.03.92 1:44 EPURMESS BIN 27269 05.03.93 19:25 MAINTINF BIN 14401 05.03.93 19:25 BIPPER COM 12142 10.02.91 17:48 MAKEPG COM 9034 06.03.93 8:29 ICOM COM 6998 27.02.93 17:51 INSTAFBB COM 44758 05.03.93 19:52 REQDIR COM 13810 03.06.92 18:42 REQFIL COM 11940 03.06.92 18:50 TLABEL COM 780 31.08.91 11:35 ESS COM 3128 20.01.93 15:55 CUT COM 7984 08.03.92 14:40 NEWDOC COM 13060 10.02.91 13:09 CLEANUP COM 58064 18.01.93 18:50 CTRLBK COM 174 22.02.92 9:51 FBBIOS COM 5775 10.02.93 1:30 HR2WP COM 17152 27.12.92 17:20 SLEEP COM 8778 10.02.91 16:39 SETUSER COM 8114 04.10.90 18:08 FV COM 8396 10.01.93 1:42 MULTI EXE 15568 10.10.92 7:27 SATUPDAT EXE 47458 22.11.91 6:52 MAINTREJ COM 11500 04.06.92 20:36 EPURWP BIN 19140 05.03.93 19:25 FBB 5.15 Feb 06 1993 Page - 9 Directory of C:\515\DISK2\DOC515 MULTI DOC 5813 22.11.92 19:22 CHANGES DOC 25841 02.02.93 15:56 515-GB DOC 279165 07.02.93 15:42 WA8DED21 DOC 33778 29.10.87 0:24 WA8V21B DOC 21331 20.01.88 22:39 WA8V21C DOC 12483 15.03.88 21:15 FV DOC 7388 10.01.93 1:42 TFPK DOC 9700 02.05.92 15:51 Directory of C:\515\DISK2\SAT515 SATEL DAT 4968 05.03.93 2:39 14129 SAT 964 03.05.92 2:33 14781 SAT 653 09.02.91 11:13 18129 SAT 2981 03.05.92 2:33 19216 SAT 1691 03.05.92 2:33 20480 SAT 1205 04.05.92 2:33 20437 SAT 860 03.05.92 2:33 20440 SAT 356 09.02.91 12:37 20441 SAT 495 04.05.92 2:33 20442 SAT 1293 04.05.92 2:33 20439 SAT 1479 03.05.92 2:33 21087 SAT 5956 03.05.92 2:33 20826 SAT 300 03.05.92 2:33 19336 SAT 306 03.05.92 2:33 20305 SAT 306 03.05.92 2:33 21232 SAT 325 03.05.92 2:33 16969 SAT 298 03.05.92 2:33 20788 SAT 331 04.05.92 2:33 20580 SAT 276 04.05.92 2:33 18820 SAT 305 20.05.91 21:03 19851 SAT 316 03.05.92 2:33 20670 SAT 313 04.05.92 2:33 16609 SAT 1112 03.05.92 2:33 19531 SAT 284 03.05.92 2:33 21089 SAT 538 03.05.92 2:33 21578 SAT 716 05.09.91 17:02 21575 SAT 1400 03.05.92 2:33 21577 SAT 848 03.05.92 2:33 FBB 5.15 Feb 06 1993 Page - 10 Directory of C:\515\DISK3\LANG515 FRANC8 HLP 52571 01.08.92 21:33 FRANCAIS HLP 52578 07.04.92 19:52 FRANCAIS TXT 11280 31.10.92 12:06 ITALIANO HLP 35632 04.08.92 20:42 FRANC8 TXT 14799 15.02.93 22:14 SVENSK TXT 11312 09.08.92 17:05 PORTUGUE TXT 11375 09.08.92 17:05 NORSK TXT 18897 09.08.92 17:05 NEDERLAN TXT 12058 09.08.92 17:05 ITALIANO TXT 13343 09.08.92 17:05 CATALA HLP 18310 12.04.92 10:27 DANSK HLP 31267 13.01.91 5:55 DEUTSCH HLP 52368 20.03.92 2:31 ENGLISH HLP 55909 22.08.92 7:06 ESPAGNOL HLP 18509 12.04.92 10:28 HRVATSKI TXT 10831 09.08.92 17:05 NEDERLAN HLP 16113 18.05.90 16:49 NORSK HLP 62807 14.06.92 12:42 PORTUGUE HLP 19685 01.11.90 19:57 SVENSK HLP 14271 07.03.91 23:29 ESPAGNOL TXT 12430 07.02.93 15:54 HRVATSKI HLP 39541 01.01.80 3:28 ENGLISH TXT 14221 03.02.93 15:20 DEUTSCH TXT 14122 07.02.93 15:53 DANSK TXT 13977 09.08.92 17:05 CATALA TXT 11423 09.08.92 17:05 MODEM ENT 479 17.09.92 2:33 Directory of C:\515\DISK3\FIRMWARE TF4 ROM 32768 17.03.88 20:23 TF18 ROM 32768 14.11.88 10:34 TF24 ROM 32768 14.09.90 9:14 TF8 ROM 32768 23.03.88 12:26 PK88U16K ROM 25508 18.06.90 16:59 PK88U32K ROM 25511 18.06.90 16:59 PK87U16K ROM 25417 06.03.90 21:08 PK87U32K ROM 25420 06.03.90 21:06 TFPK ROM 32768 02.05.92 15:48 TFPKM ROM 32768 02.05.92 15:48 FBB 5.15 Feb 06 1993 Page - 11 5 FIRST-TIME INSTALLATION AND SETUP. ------------------------------------ This part of the manual is intended for the sysop that has never used FBB software before. I hope this part of the manual will help you to get "on the air" with FBB without too many problems. Normally you will install FBB from diskettes. Normally your diskette-drive will be called A, and normally you will install the FBB-program on hard-disk called C. But this is no absolute need, you can use other drives as well. More about this a little later. Your hard-disk is organised in several directories. If you are not familiar with this, you should read in your DOS-manual about how the hard-disk is organised. FBB will normally be installed on your hard-disk in a directory named FBB. This directory should be placed directly under root (C:\FBB). This directory will be automatically created for you. The BBS will also need a lot of other directories, and they can be made directly from root, or they can be made under the FBB-directory. In the procedure I will describe here, only the FBB- directory will be at the root (C:\FBB) of the hard-disk, while all the other directories will be placed under FBB (like C:\FBB\USERS etc). But you can choose this yourself. More about this a little later. You should now be ready to start the installation procedure. Put the first of the diskettes (if you use such a format that more than one diskette is needed) in your disk-drive, and type A: if that drive is named A, or B: if that drive is named B. Press ENTER to execute the command (you must always press ENTER after a command to the PC). Your PC will now answer with something like A:\> or B:\> If you now are ready to install FBB 5.14 for the first time on your PC, you type INSTA514 (For version 5.15 you type INSTA515 and so on..) You will now see at your screen something like this: ---- QUOTE: ---- **** PREMIERE INSTALLATION DE LA FBB 5.14 *** **** FIRST INSTALL OF FBB 5.14 SOFTWARE *** Installation - depuis le disque A: - from disk A: - Programmes du serveur - BBS programs - C:\FBB - Fichiers systeme - System files - C:\FBB\SYSTEM - Messages - Messages - C:\FBB\MAIL - Messages binaires - Binary mail - C:\FBB\BINMAIL - Repertoires utilisateurs - User's directory - C:\FBB\USERS - Fichiers Yapp - Yapp files - C:\FBB\USERS\YAPP - Archive messages - Message archive - C:\FBB\OLDMAIL - Statistiques - Statistics - C:\FBB\STATS Si cette configuration ne convient pas, modifier les chemins par defaut dans le fichier A:SUITE1.BAT If this configuration is not ok, please change it in the A:SUITE1.BAT file. Tapez Ctrl-C si une version precedente existe deja Et utilisez 513514.BAT pour une mise a niveau. Type Ctrl-C if a precedent version already exists FBB 5.15 Feb 06 1993 Page - 12 and use 513514.BAT instead. ----- UNQUOTE. ----- This screen may vary a bit from version to version, but the work you have to do, will still be the same. First of all, you will see that the PC says that you will install from disk A. Is this correct ? If you are installing from disk-drive B, you must stop the installation now. The same applies if you want to use other directory-names or paths for some of the other directories that are listed on your screen now. If you DO want to change any of these things, you MUST do it now. The changes are decribed in this paragraph; if you do NOT want any changes, you can go on to the next paragraph. You stop the installation-batch by pressing CTRL-C. Now you will see the standard A:\> prompt again. Now you must use a normal text-editor and edit the file SUITE1.BAT on your diskette. I presume you have such an editor... Make sure that it is able to save the file again in ASCII (DOS) format ! So if you use for example Word Perfect, you MUST remember to save the file again in DOS-format ! At the beginning of that file, you will see a line saying SET disk=A: If you want to install from B-drive, you edit this line like this: SET disk=B: You change only the letter after '=', nothing else ! You can also change all directory-names or directory-paths in this same way. If you do not want to use C:\FBB\SYSTEM, but want it to be C:\FICHIERS, you just change the line saying SET fichiers=C:\FBB\SYSTEM to SET fichiers=C:\FICHIERS and so on. You must ONLY change the name behind the '=' sign, you must NOT change anything before that in that line. You can do this with any (or all) the directory-names and paths. But remember that you will need to do some extra work with other config-files later if you do not use the default installation. When you have finished doing the changes you want in the lines starting with SET, you must save the file again to disk. When that is done, you start over again from the beginning, by typing INSTA514 etc. OK. That is about all. Now the BBS-program and all its files will be installed on your hard-disk. You only have to change diskettes each time you are asked to (if you install from more than one diskette). When the installation is complete, you will be asked to modify some of the files. We will have a look at this now. If you have a printer, it is a good idea to make a hard-copy of the doc- files now. Go to the DOC-directory and type COPY *.DOC PRN. You will need a lot of paper.... This is the recommended organization for your directories directories will be made like this if you made no changes : FBB INIT.SRV and EPURMESS.INI (configuration) files. | |\__BACKUP Backup important files. | FBB 5.15 Feb 06 1993 Page - 13 |\__BIN All the BAT, COM and EXE files. | |\__BINMAIL | | | |\_MAIL0 Compressed mail files (number ending with 0). | | | :\_MAIL1 | : | : | : | |\_MAIL8 | | | \_MAIL9 Compressed mail files (number ending with 9). | |\__DOCS Files of the DOCS command. | |\__MAIL | | | |\_MAIL0 Ascii mail files (number ending with 0). | | | :\_MAIL1 | : | : | : | |\_MAIL8 | | | \_MAIL9 Ascii mail files (number ending with 9). | |\_OLDMAIL Optional archive for messages. | |\_PG COM and EXE files for the PG command. | |\_USERS Root of the FbbDos directories. | | | \_YAPP | \_SYSTEM System files. | |\_FWD Includes of FORWARD.SYS file. | |\_LANG Texts and help files. | |\_LOG FBBLOG.nn files. | |\_SAT Satellite files. | \_WP White Pages files. The path FBB\BIN must be included in your PATH in AUTOEXEC.BAT. Do this by adding to the PATH line in AUTOEXEC.BAT ";C:\FBB\BIN" like : PATH C:\;C:\FBB\BIN A list of the files of each directory is given in appendix 11. FBB 5.15 Feb 06 1993 Page - 14 5.1 FIRST-TIME SETUP OF DIFFERENT FILES. ----------------------------------------- So far so good... Now we must modify some files, to make the system work. I will describe all the changes you MUST do, and some changes that you CAN do, if you like. Read this section very carefully. For most of the files it is VERY important that the number of non-comment lines must NOT be changed. Later in the sysop-manual you will find more details on some of these files, and also detailes on other files that are not described here in this startup- section. FBB 5.15 Feb 06 1993 Page - 15 5.2 APPEL.BAT. --------------- This is the very first file that FBB will use. You will find it in the main FBB-directory. You don't really need to do any changes in this file, unless you did some changes in SUITE1.BAT during installation. If you did, you must change the pathnames in APPEL.BAT exactly the same as you did in SUITE1.BAT. This is very important ! So look for the lines that I have marked with an <-- - here : set fbb=C:\FBB <-- Defines the base of the FBB file system. echo off cd %fbb% <--- break off echo Program is started, use ^C to interrupt within 3 seconds sleep 3 serv %1 if errorlevel 2 goto direct if errorlevel 1 goto suite goto fin :suite cls echo echo Sorting HROUTE.SYS... copy %fbb%\system\hroute.sys temp.$$$ <--- type temp.$$$ | sort | find /v "# " > %fbb%\system\hroute.sys <--- del temp.$$$ echo echo Backup of important files... copy %fbb%\system\dirmes.sys %fbb%\backup\dirmes.s1 <--- copy %fbb%\system\inf.sys %fbb%\backup\inf.s1 <--- echo Cleaning up message-file... del epurmess.res epurmess echo Cleaning up white pages database... del epurwp.res epurwp :direct if not exist c:%fbb%\system\sat\amsat.txt goto appel <--- cd %fbb%\system <--- tlabel cd %fbb%\system\sat satupdat amsat.txt /n > satupdat.res satupdat amsat.txt >> satupdat.res del amsat.txt cd %fbb% <--- :appel echo Program is started, use ^C to interrupt within 3 seconds sleep 3 serv -t if errorlevel 2 goto direct if errorlevel 1 goto suite :fin echo Program is terminated.. break on Echo on FBB 5.15 Feb 06 1993 Page - 16 5.3 INIT.SRV. -------------- This file is the next file that FBB looks into during startup. This file will be found in the main FBB-directory. All basic data is collected from this file. Use your standard editor (as explained earlier) to edit the following lines: (all lines starting with # are comments) INIT.SRV is now created or updated with a little program named INSTAFBB.COM. This program is organized as pages of menues, and you can edit or change any topic in your configuration. It is no longer necessary to edit the INIT.SRV file. The version of the software is now indicated in the first comment line. This will allow further automatic updates. # FBB5.15 # # Callsign and H-adress (Do not include SSID !) LA1B.#BRG.NOR.EU # # SSID for the BBS 0 # # Qra locator JP20RH # # Qth (variable $c) Bergen # In the above lines you MUST replace the callsign and H-adress with your own BBS-call and H-adress. You also must replace the SSID, that is the number after the callsign. In LA1B-6, the 6 is the SSID. If you do not want any SSID, type 0 here. You also must replace the QRA-locator with your own locator (ask some other ham for help on this, if you don't know the BBSs QRA- locator. Do NOT use the value from this example-file ! You also must replace the QTH (don't make it too long...). If the QTH-name is short, you might add the QRA-locator here too, like I have done. Next we have some filenames and path-names. These filenames and paths are the same as used in the installation-procedure. If you did no changes in this during installation, you will not need to change any of these now. But if you DID make changes during installation (in SUITE1.BAT) you MUST do the exact same changes here ! This is VERY important ! Note the syntax, and note that directory-names MUST end with a \ # Directory for files used by the BBS C:\fbb\system\ # # Directory for messages C:\fbb\MAIL\ # # Directory for binary-messages C:\FBB\BINMAIL\ # # Directory for users DOS C:\fbb\users\ # # Directory for Yapp-files C:\fbb\users\yapp\ # FBB 5.15 Feb 06 1993 Page - 17 # Directory for DOCS C:\FBB\DOCS\ # That was not so difficult ? Next you MUST replace the first-name of sysop, and the callsign of sysop. # First-name of sysop Per # # Sysops callsign LA6CU # In the following line you CAN (not necessary) replace the ***** with a callsign. If you do, that callsign will receive a copy of all SYSOP-messages that arrives. You might want to put your own callsign there. # Callsign (and route if needed) that shall have copy of messages # adressed to SYSOP # (*** for no copy, FD1CDC@FD1CDC.FMLR.FRA.EU if route) ***** # No need to change this: # Path and filname for import-file \FBB\MAIL.in # Here you must first write the code for the kind of monitor you use, and then you must have a number for how many minutes you want before the screen should go blank, after no activity on the keyboard. In this example I have a CGA- monitor, and my screen will go blank after 5 minutes since I last touched the keyboard. # Type video:0=CGA, 1=EGA, 2=VGA Time before screen-blank. # 0 5 # Log complet gives you a log-file for every week. If you write NO here, no log-file will be made. The log-file will appear in the directory named LOG. Direct video uses fast BIOS-calls if you answer OK. If you plan to use Desqview or Windows you must change it to NO. Indication of channels will normally be OK (that means that monitored information on screen will be more complete, with callsign of user before every frame from each user, etc). # Log complet (OK or NO) OK # # Direct video (OK or NO) OK # # Indication of channels OK # FBB 5.15 Feb 06 1993 Page - 18 Next we have Mode Test (NON - OK). If you type OK, the BBS will start, but will not access the TNC(s). Use this the first times, to make sure that everything works fine. When you are sure that all is well, connect the TNC(s) and change this to NO. Restart the FBB, and now the TNCs will be used, as normal. # Mode Test (NO - OK) OK # Forward type FBB is faster and more efficient than standard MBL-type forward. Use this whenever possible (OK). If you type NO, FBB-type forward will not be allowed. The same goes for compressed forward. Compressed forward is very much faster, and should always be used. So, leave these lines un- changed, you can change them later, if you want to : # Use (when possible) forward type FBB OK # # Use (when possible) compressed forward OK # Hroute update validation. If you type OK, the HROUTE look-up will be validated. This takes some tens KB of memory. A route without hierarchical extension will be changed to hierarchical route if found in the HROUTE.SYS database. This database is automaticly updated while receiving headers. # HROUTE look-up and database update validation OK # Informations query. This ensures that the user will give his informations. This will be helpfull for the update of the white pages database. If "OK", the user will prompted until he answers to the queries. # User MUST give Name, HomeBBS, Qth and ZIPcode OK # Next we have 'Masque'. This is a default value that is given to all new users when they log on the BBS for the FIRST TIME. Select the things you want for all new users, and the values for them. If you f.ex. want all new users to get Paging, and be in Guest mode, add 32 and 64, and put the result 96 in the file. If you want none of the things listed here, put in a 0. The "see- all_mail" mask will be active only if the user has the "read-all-messages" security code (see behind). # First connection mask. # 0 : disable. # 1 : Excluded. # 2 : Local. # 4 : Expert. # 8 : Sysop. # 16 : BBS. # 32 : Pagination. # 64 : Guest. # 128 : Modem. FBB 5.15 Feb 06 1993 Page - 19 # 256 : See-all-messages. # 512 : Unproto-list asking is allowed. # 1024: List of new messages given at logon. # Add up the values for your choises. 1568 # Then we have 'Security-codes'. Here we give 3 values. The first says what ALL users are allowed to do. The next says what sysops are allowed to do when they connect the BBS, and the third says what a sysop is allowed to do after he has successfully performed the SYS-command. The same applies here as above; choose the values you want and add them up. # Security-codes. # All users can: # 1 : Read all messages, including all personal messages. # 2 : Kill all messages. # 4 : Send SYS-command. # 8 : Use remote-sysop commands (edit, forward etc). # 16 : Edit labels in YAPP, FBBDOS, DOC. # 32 : Can delete files in YAPP and FBBDOS. # 64 : Have access to all gateways. # 128: Run dos-programs (command DOS in FBBDOS). # 256: Have access to the entire hard-disk. # 512: Have access to command /A (stop BBS) and /R (reboot PC). # # All: Sysop: Sysop after successful SYS-command: 0 127 1023 # Next we have the time for cleanup of messages. This should be done in a low- traffic hour, as the BBS is completely shut down during cleanup. Type also the timeout-values you want, the default values here should be OK. Put also in the number of hours (+ or -) between the PCs local-time and UTC. # Time (hour) for cleanup of messages 02 # # # Time-out for normal use (minutes) 10 # # Time-out during forward (minutes) 15 # # Hours +/- in relation to UTC 0 # Type how many callsigns you want (maximum) in each mail-beacon (variable $Q). If you precede the number by a B, also bulletins to local users (type BN or BY) will be brodcast in the mail-beacon. Like this: # Number of callsigns in mail-beacon B20 # FBB 5.15 Feb 06 1993 Page - 20 Number of lines in scroll-buffer may be changed. Just remember that they use a lot of memory (each line takes 160 bytes of memory, but can be in high memory), so I advice you to use these values: # Number of lines in scroll-buffer # User Console Monitoring 200 100 100 # Leave this one alone: # Text for forward-header (variables OK), appears LAST in the R:line. # Please do not change the contents and the order of the fields except # the FBB$E field which is only an information and can be removed. # $c is the QTH as declared before in this file. [$c] #:%M Z:$z FBB$E # Next you must decide how many BIDs to keep. 3000 is a good value. If you are using EMS or XMS-memory (with a special driver loaded for this..) you should answer OK for BID in EMS/XMS, if not, you must answer NO. # Number of BIDs that are saved (32000 max) # No more than 3000 when EMS/XMS is not used ! 3000 # Leave this one alone. This one means that bulletins that are older than (in this case) 30 days, will not be forwarded again from my BBS, and will go directly to X-status. Be aware: a too low value here will make problems for other BBSs that you forward to.. # Lifetime for bulletins. Number of days from message is written 30 # Here you must say if you use any EMS or XMS memory, or if you have no such memory available. If you DO have such memory available, you should answer 1 or 2 here followed by the list of topics you want to load in high memory. The BBS will do these operations very much faster. # # Use EMS or XMS memory ? 0=No, 1=EMS, 2=XMS. # and optional list of topics to put in high memory # # Topics : BID = Bulletins or messages identifiers # MSG = Message lists # HIE = Hierarchical information # OVR = Software overlays # SCR = Screen buffers # WPG = White Pages database # REJ = Reject/hold informations # FWD = Forwarding informations # 2 BID MSG WPG # FBB 5.15 Feb 06 1993 Page - 21 List of routes to send WP update messages. First, keep this line blank until you have a WP network available, then give the route(s) to send your updates. # List of routes to send WP messages # # Zip code of the BBS. Give the post code area where is the BBS. # ZipCode of the BBS # 31120 # Here you will give the paramaters allowing the list of messages in unproto mode. This list can be interpreted by some terminal softwares (as TPK) and greatly reduce the traffic on the local frequency. The first parameter is the maximum backward number. If a unproto user asks a list which is lower than this number backward, he will be limited to this parameter (IE: if the current message number is 20000 and a user asks the list of the message 15000, he will be then limited to the 19500 if the backward number is 500). The second parameter is the speed of the unproto updates given in seconds. The frames will be sent with this period. # Back number and unproto lists period # 500 10 # Leave this lines alone, unless you are absolutely sure you want to change it: # Intern interrupt (hexadecimal, default 7C) 7C # Then you have two optional programs of batches which are called at the end of the initialization, and just before shutdown. If you don't need them, keep these lines empty. # # BBS-UP program (default empty) # # BBS-DW program (default empty) # You can change these colours if you like: # Colour on texts : # # Black : 0 Dark grey : 8 # Blue : 1 Light blue : 9 # Green : 2 Light green : 10 # Cyan : 3 Light cyan : 11 FBB 5.15 Feb 06 1993 Page - 22 # Red : 4 Light red : 12 # Magenta : 5 Light magenta : 13 # Brown : 6 Yellow : 14 # Light grey : 7 White : 15 # # # COULEUR FONDS # # Status (top) 1 # Bandeau (middle) 7 # Tekst (bottom) 0 # Menues 4 # # Colour of characters # # Status (top) 7 # Bandeau (middle) 1 # Menues 14 # Text sent 10 # Text received 12 # UI (Headers) 15 # UI (traffic) 7 # Console 14 # Beacon 6 # Channel-marking 11 # ------ # You may change these lines if you like. These are the servers that are normally available in most FBB-BBSs, and they are automatically installed for you from the diskettes. So you can leave them alone. Or you can disable them with a # in front of each of these lines. Two built-in servers already exist, but you MUST declare them in this file to make them available. As they are built-in, the program-name MUST be replaced with stars. # List of "servers" : # # To Program-name Description # REQCFG ****** Request configuration WP ****** WP server REQDIR REQDIR Request directory-listings from other BBSs. REQFIL REQFIL Request files from other BBSs. NEWDOC NEWDOC Upgrade files under DOCS. ------ FBB 5.15 Feb 06 1993 Page - 23 # # End of file # Ok. That was the INIT.SRV file. This file is VERY important, so check and double-check to make sure that you have it all OK. FBB 5.15 Feb 06 1993 Page - 24 5.4 EPURMESS.INI. ----------------- This file is also in the main FBB-directory. This is the file that controls the lifetime of messages. Each night EPURMESS will be activated at the time specified in INIT.SRV. Normally you will not need to change this, but if you did any changes in SUITE1.BAT during installation, you must also change the same pathnames here. That goes for these lines: # # File for deciding messages' lifetime.. # # Directory for messages \FBB\MAIL\ # # Directory for binary-messages \FBB\BINMAIL\ # # Directory for "killed" messages \FBB\OLDMAIL\ # # The file DIRMES.SYS (database-file) \FBB\SYSTEM\DIRMES.SYS # # Old database-file (backup) \FBB\SYSTEM\DIRMES.OLD # # New database-file (after EPURMESS (cleanup)) \FBB\SYSTEM\DIRMES.NEW # # Result of cleanup is pu into this file: \FBB\EPURMESS.RES # Next, you decide if you want to save "killed" messages in the OLDMAIL- directory. If you do, write an 1 first, if you want to save old personal messages, and another 1 if you want to save old bulletins. # Personal Bulletins (0=kill 1=archive in oldmail) 0 0 # Next we have the actual parametres (in days) for the lifetimes of bulletins and personal messages. Let me just explain the letters in use here: P=Personal message B=Bulletin N=Not read Y=Had been read F=Forwarded (forwarded to all BBSs that should receive this msg) X=Expired (still readable, but will not be forwarded to other BBSs) K=Killed (readable only by sysop) A=Archived (same as killed, but will be deleted at once, or moved to OLDMAIL) I think this is self-explainatory: # Parametres in days: # # PARAMETRES FOR PERSONAL MESSAGES: # # PN -> PX (days after message is written) FBB 5.15 Feb 06 1993 Page - 25 30 # # PY -> PX (days after changed to Y) 7 # # PF -> PK (days after changed to F) 7 # # PX -> PK (days after changed to X) 0 # # PK -> PA (days after changed to K) 0 # # PARAMETRES FOR BULLETINS # # BN -> BX (days after the message is written) 7 # # B$ -> BX (days after the message is written) 7 # # BY -> BX (days after changed to Y) 7 # # BX -> BK (days after changed to X) 14 # # BF -> BX (days after message is written) 14 # # BK -> BA (days after changed to K) 0 # ------ # At the end of the file, you can have special lifetimes for special messages. In the example below, messages that are TO LA6CU will be 365 days old, messages FROM system will be 0 days, messages @LA will be 365 days. I have an # in front of them, this means they are disabled right now. # List of lifetime-tests # # Type To Days @ VEST 365 @ LA 365 > LA6CU 365 < SYSTEM 0 # # End of this file. # FBB 5.15 Feb 06 1993 Page - 26 5.5 PORT.SYS. -------------- This file is found in the directory called SYSTEM (if you used my default directory-names). In this file we decide what kind of TNCs to use, how many available channels etc. You must do several changes here, and be very careful that you do all changes correctly. If you don't, the BBS cannot operate properly. Remember that a line starting with # is a comment-line, and the BBS ignores these lines. The BBS has built-in drivers for a maximum of 8 serial-ports, named COM1- COM8. It can also use a special port-multiplexer so that you can have up to 4 TNCs per COM-port. First you must type how many ports and TNCs you use, like this: # File for programming of channels and TNCs. # # Ports : How many ports (COM1, COM2, Etc...) # TNCs : How many TNCs and modems in use. With multiplexer # there can be up to 4 TNCs per port. # #Ports TNCs 2 2 # Next you must type one complete line of parametres for each COM-port you use. You must be careful to use the correct values here. If you use external drivers like COMBIOS, BPQ or DRSI-card, you must be careful to give the correct values here. If you use COMBIOS, FBBIOS, BPQ etc, they must always be loaded before you start the BBS-program. In this example I use 2 TNCs, one on COM1 and one on COM3, and I use the internal driver : # Com : COM-number (1,2,...8) # Interface: 1 = External ESS driver # 2 = BPQ-node V 4.05 or up. # 3 = Telephone-modem with FBBIOS # 4 = DRSI card with driver # 5 = TFPCR/TFPCX interface # Adress : Adress of port in hexadecimal (Needed for multiplexor). # Baud : Ports baud rate. Ignored by BPQ. # # Use same number of lines as number of ports. # #Com Interface Adress (Hex) Baud 1 0 3F8 4800 3 0 338 4800 # Once more, the number of lines below must be the same as number of TNCs in use. One line for each TNC. I think most of it is self-explainatory. MultCh will normally be 1. If you use DRSI-card, you can use a value from 0 to 7. If you have a KAM in host-mode, you must use 1 for VHF and 2 for HF. MxBloc decides how many kb will be forwarded one way to another BBS before the forward is reversed. Leave this value at 10 for VHF/UHF and a little smaller for HF. Type host-mode depends on your TNC, and if you use BPQ : # TNC : Number on TNC in use. # NbCh : Number of channels I want to use in the TNC. # Maximum available channels depend on firmware. FBB 5.15 Feb 06 1993 Page - 27 # Com : Number of the COM-port. Com1, Com2 etc. # MultCh : Number of channel if port-multiplexer is used, otherwise 1. # In DRSI use values from 0 to 7, by KAM use 1/VHF and 2/HF. # Paclen : PACLEN on this TNC. # Maxframe: The maximum nb of frames the TNC will send at a time. # NbFwd : Number of channels for OUTGOING forward at same time. # MxBloc : Size of forward-block in kb. # M/P-Fwd : Minute of the hour for start of forward, and period # (how many minutes between each forward-start). # Port mode, one of these: # B : BBS-mode. # G : "Guest"-mode. # U : Normal-mode. # Type host-mode, one of these: # D : WA8DED # K : KAM hostmode. # P : PK-232 # Q : BPQ v 4.x # Addition: One or more of these letters can be used too: # L : Send unproto beacon after each arriving mail. # M : Telephone-modem. # Y : Yapp allowed on this QRG. # W : Gateway allowed TO this QRG. # R : Modem port allowed in Read-only mode. # Freq. : Text to describe this port (max 9 characters, no space) # Same number of lines as number of TNCs. # #TNC NbCh Com MultCh Pacln Maxfr NbFwd MxBloc M/P-Fwd Mode Freq 1 7 1 1 230 4 1 10 30/60 UDYW 433.650 2 1 3 1 80 2 1 5 17/30 GDW 15/20m # At the end of the file, you can specify one (or more) callsigns and SSIDs for some channels. You might use this for special callsigns on forward- channels. If you don't need this (you probably don't, at least not the first times..), place an # in front of the line. This only works with WA8DED interface. # Special callsigns and modes for some channels. # #TNC Nbs Callsign-SSID Mode 1 2 LA1B-1 B # # End of file. # FBB 5.15 Feb 06 1993 Page - 28 5.6 SWAPP.SYS. --------------- This file will also stay in SYSTEM-directory. This file is used for automatically re-route messages. This file normally changes the @BBS-adress, but can also change the TO-field. You might not need so many callsigns etc. here, but you should make one line with only your callsign after the @. In that case the @BBS will be removed from messages to users in your own BBS. For the first tries, it is enough to have one line starting with @, and then your BBS-callsign. You can fill in the rest later. # # File SWAPP.SYS is used to change @BBS-adresses. # For example replace @EUR to @EU # # Change TO-adress... Use > instead of @ # Change @BBS for a specific callsign, ex; > LA8AK @ OZ2PAC # @ LA8AK @ LA9K @ LA5IV @ LA9K @ LA5F @ LA9H @ EUR @ EU @ HF @ EU @ WWW @ WW > LA1B @ LA6CU @ LA6TAA @ LA1Z @ LA9WO @ LA9H > F6FBB @ F6FBB.FMLR.FRA.EU FBB 5.15 Feb 06 1993 Page - 29 5.7 INITTNCx.SYS ----------------- This file is also in the SYSTEM-directory. When the BBS starts, it sends some standard parametres to the TNC, like PACLEN, MAXFRAME etc. These parametres are in PORT.SYS. But in addition to this we may send som more parametres to each TNC. We send parametres to TNC 1 with the INITTNC1.SYS, to TNC 2 with INITTNC2.SYS etc. Here is just one example from LA1B BBS : (you do not need to use the same parametres) C MAIL v LA7QR U 0 N 10 M IU P 64 T 40 C MAIL V LA7QR means that unproto mail-beacon will be sent to MAIL via the digipeater with callsign LA7QR. You may use just C MAIL if you do not want to send via digipeaters. U 0 means that the TNC will not send any TNC-message to user when he connects to the BBS. You should use this parametre. N 10 means that RETRY will be set to 10. M IU means that that all I and UI frames will be shown in monitor-windows. P 64 means a p-persistance value of 64. This is normal. T 40 sets a TXDELAY of 40. This value depends on Transceiver in use. So, you can use any suitable parametres in this file. You need one file for each TNC. The commands sent to the TNC, are the commands described in the documentation for the firmware you use, or in the documentation for PK-232, DRSI, BPQ etc. If you are using BPQ, DRSI, PK-232 or KAM, look in section 14 for special commands for this files. FBB 5.15 Feb 06 1993 Page - 30 5.8 MAINTx.SYS --------------- This file is in the SYSTEM directory. This works exacly like INITTNCx.SYS, but the parametres are sent to the TNC when the BBS is shut down. The file can look like this: Y 1 U 1 BBS ($c) was shut down for service $d $T. Y 1 means that only 1 station can connect my TNC now. U 1 means that the TNC will send this message to any user that connects after the BBS has shut down. If you use a PK-232, the same file would look like this: UR1 CTBBS ($c) was shut down for service $d $T. The commands sent to the TNC, are the commands describ documentation for the firmware you use, or in the documentation for PK-232, DRSI, BPQ etc. FBB 5.15 Feb 06 1993 Page - 31 5.9 BALISEx.SYS ---------------- This file is in the SYSTEM directory. This file makes the text that will be broadcast as mail-beacon from the BBS. (Balise in french means beacon). The first line is a parametre that says how often to send the beacon. %15 means "send one beacon every 15 minutes". The next line says to what unproto- address the beacon will be sent. ! MAIL v LA7QR means send beacon to MAIL via LA7QR digipeater. The next lines are the actual beacon-text. Here we can use variables like $d $T etc. We cannot use variables that are specific to one channel alone. You do not need to change anything else then the !-line in this file. But you will need one file named BALISE1.SYS for TNC1, one calles BALISE2.SYS for TNC2 etc. %15 ! MAIL v LA7QR $d $T <<< Mailbox $O $c >>> $N active messages. Messages for$W$Q FBB 5.15 Feb 06 1993 Page - 32 5.10 BBS.SYS ------------- This file is in SYSTEM directory. In this file you MUST put the callsign of every BBS you will forward directly to. There must be 80 (from 1 to 80) lines, even if you do not use them all. The format is very critical, so do NOT change line-arrangement ! All the BBSs you forward to (the callsigns after A in FORWARD.SYS) must also be in BBS.SYS. Before you start your BBS for the first time, you should remove all not-used callsigns in BBS.SYS, and put in the file only the BBSs that you forward to in your FORWARD.SYS. Later it is recommended that you do NOT replace one callsign with another, as messages then will go to the wrong BBS. This file should speak for itself. FBB 5.15 Feb 06 1993 Page - 33 5.11 FORWARD.SYS ----------------- This file is in SYSTEM directory. In this file all necessary data for forwarding of messages is held. First I will give an example of a file that contains the minimum of data that MUST be in FORWARD.SYS if you have forward to only 1 other BBS, called LA2D in this example. The file is organised in blocks, one block for each BBS we forward directly to. A block starts with A (callsign) and ends with -------- We can have as many blocks as we want in FORWARD.SYS. A LA2D # P C # C C LA2D # B LA2D F LA2D # --------- All lines starting with a '#' are comments-lines, and are ignored by the BBS. The first line must always start with the letter A, and next the callsign of the BBS we want to forward to. Here: A LA2D Then there must be line telling on which port to start the forward. This line must be there even if we only have 1 port. In this example I use port C, which is the same as TNC 3 in my PORT.SYS. Command: P C So I will send the connect-command to the TNC. That line must start with a C before the actual connect-command. So if I call LA2D directly, I need to write C C LA2D. (Only 1 C will not work). And lastly I must write which messages I shall forward to that BBS. In this case I type only B LA2D, which means all messages with @ LA2D, and F LA2D, which means all messages TO LA2D. The forward-file must end with a string of -------. If you have more than one BBS to forward to, you write all data for that BBS in a similar block in this same FORWARD-SYS-file (starting with A, and ending with ----) right after this block for LA2D. You can also use one include-file for every BBS, but we will look at that in section 14 of this sysop-documantation. Well. I expect you do not want to forward only those messages that are TO LA2D or @ LA2D (in this example), I expect you want to forward bulletins also. Just include some lines starting with G, like G EU, G ALL, G WW etc in the file. G EU means all bulletins adressed to @ EU. So may want to add this in each file, like this: A LA2D # P C # C C LA2D # B LA2D F LA2D # G EU G ALL FBB 5.15 Feb 06 1993 Page - 34 G WW --------- OK. Next you may want to forward messages through LA2D, that is not really for LA2D, but that LA2D can forward on to this other BBS. These other BBSs can be included in lines starting with a B, like B LA1G, B LA4O, B LA5G etc. like this: A LA2D # P C # C C LA2D # B LA2D F LA2D # B LA1G B LA4O B LA5G # G EU G ALL G WW --------- Also, if you want to forward ALL messages for other SM-BBSs this way, you can use wildcards (as in DOS) like B SM*, B SK*, B OH* etc. like this: A LA2D # P C # C C LA2D # B LA2D F LA2D # B LA1G B LA4O B LA5G # B SM* B SK* B OH* # G EU G ALL G WW --------- Well. Now the file is almost complete for most needs. We may want to add the possibillity to forward (on VHF or UHF) via several nodes. This is very easy, as we just add another C C (callsign) line for each node we have to call. If i must call first my local node LA7QR, next the local node of LA2D (LA1EAX- 7), and lastly LA2D, the complete file for LA2D will now look like this: A LA2D # P C # C C LA7QR C C LA1EAX-7 FBB 5.15 Feb 06 1993 Page - 35 C C LA2D # B LA2D F LA2D # B LA1G B LA4O B LA5G # B SM* B SK* B OH* # G EU G ALL G WW # R # --------- If you want to forward via KA-nodes etc., look in section 14.7. I put in an R at the end. This forces my BBS to call LA2D BBS and ask him for forward from him to me (revers forward), even if I have nothing to forward to him. Well, this was a simple forward-file. There is a lot more we can do with this file, so you should read section 14 of the sysop-manual very carefully, I think you will find all you need there. FBB 5.15 Feb 06 1993 Page - 36 5.12 Start the BBS for the first time. --------------------------------------- Now you should be ready to start the BBS for the first time. Before you do, make sure that the internal clock of the BBS is correct. If not, you must correct it now with the DOS-command DATE and TIME. In most newer PCs today, the clock is automatically set at each power-up. But in some older PCs you may need to use a special clock/calendar card in your PC, and use a special program to set the date/time at each startup. For this you must look in the manual for that clock/calendar card and include the appropriate command in your AUTOEXEC.BAT file. When this is settled, go to the FBB directory and type APPEL and press ENTER. The first time you start the BBS like this, it will ask you if you want to create some files. Just answer Y (for Yes) every time. Then those files are automatically created for you. The BBS should now be ready for use. You will find a short help-list for all the function-keys by pressing F1. Try a connect to the BBS. Do this by pressing F2. The BBS will ask you for your name and QRA-locator. Next you must define all the BBSs you want to forward to. You do this with the command EU. If you want to have forward to for example LA2D, you type EU LA2D. The BBS will say that this callsign is not known, and ask if you want to create it. You answer Y. Next you will see a line of different options for that user. You only have to type B. Now that callsign (LA2D) will be defined as a BBS. You must press ENTER once more to stop editing the user. Repeat this procedure with the callsign of all the BBSs that you will forward to. You terminate the keyboard-session with the command B (Bye). Well, if all is ok, and you have not encountered any big problems so far, you can stop the BBS (you do this with Alt-F10) now. You can connect the TNCs, and in INIT.SRV you must change from No to Ok in the line that asks 'Mode test ?', or use INSTAFBB to change the field "TEST MODE" to "N". FBB 5.15 Feb 06 1993 Page - 37 5.13 TNC. ---------- This software will work with different kinds of TNCs or TNC-interfaces: - TNC-2 or close clones. The EPROM of type 27256 must be replaced by a special EPROM with the WA8DED host-mode software, or by the german TF4, TF8 or TF18. - PK-232 in host-mode. - Kantronics KAM in host-mode. You need a special driver called ESSKAM. - DRSI-card. - G8BPQ-node (uses TNCs in KISS-mode). The software for the TNC-2 host-mode EPROMs TF4 and TF8, are on the distribution-disks. If you cannot burn new EPROMs yourself, there are a lot of hams around who can. You can also send a new EPROM to F6FBB or FC1GHV (with return-postage and packing material, of course) and they will do the work for you. The TNC should work on 4.9 MHz. The standard is 2.5 MHz, but a modification for this is normally quite simple. In some cases it might be necessary to replace the Z80 and the Z80 SIO by A-versions. If you use standard TNC-2 with one of the mentioned host-EPROMs, you can start again now, and all should work fine. Make sure that the TNCs have the same baud-rate as you wrote in PORT.SYS, and that they really are connected to the COM-ports that you said in PORT.SYS. If you do NOT use a standard TNC-2 with DED-type host, but PK-232, Kantronics KAM, DRSI-card or BPQ-node, you must read about your special TNC- setup in one (or more) of the chapters 5.14 to 5.17 before you can start the BBS again. If the TNCs don't work ok with the software, you will see this when you start the BBS. You will have a lot of error-messages on the screen, and the TNCs may start to resync. Stop the program and go throug all the setup once more. FBB 5.15 Feb 06 1993 Page - 38 5.14 PK-232 in host-mode. -------------------------- If you plan to use a PK-232 with this sofware, you must make some changes. First, check again PORT.SYS. You must have a P in "Type host mode". For example: # #TNC NbCh Com MultCh Pacln Maxfr NbFwd MxBloc M/P-Fwd Mode Freq 1 7 1 1 230 4 1 10 30/60 UPYW 433.650 2 1 3 1 80 2 1 5 17/30 GPW 15/20m # Example of INITTNCx.SYS for PK-232: UNMAIL v LA7QR means Unproto MAIL v LA7QR RY10 " Retry 10 MN6 " Monitor 6 MC6 " Mcon 6 Example of MAINTx.SYS for PK-232: UR1 CTBBS ($c) was shut down for service $d $T. PK-232 host-mode commands (from F6AIW) : 8B 8BITCONV AU AAB AB ABAUD AG ACHG AA ACRDISP AK ACRPACK AT ACRRTTY AE ADDRESS AD ADELAY AI ALFDISP AP ALFPACK AR ALFRTTY AL ALIST AM AMTOR AC ARQ AO ARQTMO AS ASCII AY ASPECT AW AWLEN AV AX25L2V2 AX AXDELAY AH AXHANG BA BAUDOT BE BEACON BI BITINV BK BKONDEL BT BTEXT CL CANLINE CP CANPAC CX CASEDISP CU CBELL CC CCITT CF CFROM CB CHCALL CD CHDOUBLE CH CHSWITCH CK CHECK CQ CMDTIME CM CMSG CI CODE CN COMMAND CE CONMODE CO CONNECT CY CONPERM CG CONSTAMP CI CPACTIME CR CRADD CT CTEXT CW CWID DS DAYSTAMP DA DAYTIME DC DCDCONN DL DELETE DF DFROM DI DISCONNE DW DWAIT EA EAS EC ECHO ES ESCAPE FA FAX FN FAXNEG FE FEC FL FLOW FR FRACK FS FSPEED FU FULLDUP GR GRAPHICS HB HBAUD HD HEADERLN HI HID HO HOST HP HPOLL ID ID IL ILFPACK IO IO JU JUSTIFY KI KISS LR LEFTRITE LO LOCK MX MAXFRAME MB MBX MC MCON MD MDIGI MM MEMORY MI MFILTER MF MFROM MH MHEARD MN MONITOR MO MORSE MP MSPEED MR MRPT MS MSTAMP MT MTO MA MYALIAS ML MYCALL MG MYSELCAL MK MYALTCAL NE NEWMODE NO NOMODE NR NUCR NF NULF NU NULLS OK OK OP OPMODE PA PACKET PL PACLEN PT PACTIME PR PARITY PS PASS PX PASSALL PE PERSIST PP PPERSIST PC PRCON PF PRFAX PO PROUT PY PRTYPE RW RAWHDLC RB RBAUD RC RCVE RE RECEIVE RX RXREV RD REDISPLA RL RELINK RS RESET RP RESPTIME RT RESTART RY RETRY RF RFEC SE SELFEC SP SENDPAC SI SIGNAL SL SLOTTIME SQ SQUELCH SR SRXALL ST START SO STOP TB TBAUD TC TCLEAR TM TIME TR TRACE TW TRFLOW TI TRIES TD TXDELAY TF TXFLOW TX TXREV UN UNPROTO UR USERS US USOS VH VHF WI WIDESHFT WO WORDOUT WR WRU XW XFLOW XM XMIT XO XMITOK XF XOFF XN XON FBB 5.15 Feb 06 1993 Page - 39 5.15 Kantronics KAM in host-mode. ---------------------------------- If you plan to use a KAM with this sofware, you must make some changes. Before you start the BBS, you must load the RS232 driver (ESS). The driver is now working with KAM from the version 1.10. Do not use another driver such as COMBIOS, MBBIOS or ESSKAM. Run it like this: ESS 1 (Com1, Adress and IRQ = defaults) ESS 1 03F8 4 (Com1, Adress=03F8Hex, IRQ4) The KAM must be in the right baudrate, and in hostmode. You put it into hostmode with these commands: INTF HOST PERM There is a special format for INITTNCx.SYS. For HF, use this: UNPROTO MAIL/ MONITOR ON/ MCOM ON/ MCON ON/ MRESP ON/ PID ON/ RETRY 15/ RESPTIM 0/ FRACK 2/ CHECK 30/ HID OFF/ For VHF use this: UNPROTO /MAIL MONITOR /ON MCOM /OFF MCON /ON MRESP /ON PID /ON RETRY /8 CHECK /30 HID /OFF As you can see, the position of the "/" is very important for HF/VHF ! In PORT.SYS you must use 1 for VHF and 2 for HF in MultCh. You must also use K in "Type host-mode". # # Same number of lines as number of TNCs. # #TNC NbCh Com MultCh Pacl Maxfr NbFwd MxBloc M/P-Fwd Mode Freq 1 4 1 1 230 4 1 10 30/60 UKYW 144.675 2 1 1 2 80 1 1 6 15/60 UKYW HF # FBB 5.15 Feb 06 1993 Page - 40 5.16 DRSI-card. ---------------- If you plan to use DRSI-card with this sofware, you must make some changes. Before you start FBB, you must load the DRSI-driver that comes with the DRSI- card. This must be TNCTSR-R or TNCTSR-L with a version-number higher or equal to 2.1. The first DRSI-card (MultCh 0 and 1) must be at adress 300. The second DRSI-card (MultCh 2 and 3) must be at adress 310. The third DRSI-card (MultCh 4 and 5) must be at adress 308. The fourth DRSI-card (MultCh 6 and 7) must be at adress 318. Before installing cards in the PC, use the program CHKADDR to verify that the adresses corresponding to the cards have a value of FF. If there is a problem, check your configuration to find what peripheral is already using this address. Install just one card at the time, and verify each cards presence with CHKADDR. When all cards are ok, configure the driver by means of the TAILORnn program (depending of the version). TNCTSR-S will be ok if you use only a few channels, while TNCTSR-L should be used for big configurations, up to 32 channels. One problem: What DRSI calls DRSI-PORT, is what we call MultCh in FBB ! What DRSI calls PORT, is what FBB calls port or TNC ! We always use FBB-names here... Each DRSI-card works like 2 radio-ports. The first DRSI-card is always MultCh 0 and 1, and the forth card is MultCh 6 and 7. If one radio-port is used on HF, that port must be the second port on the card. All the DRSI-cards together, work like only one COM. And this COM-port does not need to exist in the PC. You may call that port COM 7 or COM 8 and keep free the already existing COMS. Baud-rate does not matter, but should be set to a standard value, to avoid error-messages. Here is an example of PORT.SYS with 2 DRSI-cards (4 radios) : # #Ports TNCs 1 4 # # #Com Interface Adress (Hex) Baud 7 4 0 4800 # # #TNC NbCh Com MultCh Pacl Maxfr NbFwd MxBloc M/P-Fwd Mode Freq 1 8 7 0 230 4 1 10 30/60 UDYW 433.650 2 1 7 1 80 2 1 5 12/30 GDW 15/20m 3 8 7 2 230 4 1 10 36/60 UDYW 433.650 4 8 7 3 230 4 1 5 10/30 GDW 145.300 # If you are using DRSI-card, you also must change the INITTNC1.SYS. You will need only ONE file for all the ports. FBB 5.15 Feb 06 1993 Page - 41 Example of INITTNC1.SYS that initializes 4 ports: MUIS U0 p0 1 64 10 4 4 10 100 18000 30 2 0 p1 1 64 10 4 1 16 100 18000 30 1 0 p2 1 64 10 4 4 10 100 18000 30 2 0 p3 1 64 10 4 4 10 100 18000 30 2 0 The same goes for MAINT1.SYS, only 1 file is needed for all 4 ports, like this: Y 1 U 1 BBS ($c) was shut down for service $d $T. In FORWARD.SYS there is no changes. Use standard syntax. Well, I think that should be all (for DRSI). Oh, bye the way: DRSI cannot limit the number of connections per radio-port. But in FBB we still can have NbCh set to for example 1. When a station then connects to the BBS on that radio-port, and there already is one user connected there, the BBS will send a message to him: "Sorry, no more channels available" and disconnect him. FBB 5.15 Feb 06 1993 Page - 42 5.17 G8BPQ-node (uses TNCs in KISS-mode, DRSI cards, etc...). ------------------------------------------------------------- If you plan to use BPQ-node with this sofware, you must make some changes. Before you start FBB, you must load the BPQ-program. From version 4.05 of BPQcode, separate ports can be declared. Level 2 connections issue to the MultCh in the same order as PORTs declared in the BPQCFG.TXT (G8BPQ distribution) file. First port corresponds to MultCh 0. Level 4 connections (from the network) always issue to MultCh 0. In PORT.SYS you must use 2 in INTERFACE, and Q in type host mode. Version 4.05 or up is recommended. COM can be from 1 to 8, but will exclude existing COMs. Chosing 8 is a good solution to keep existing COMs. Only the INITTNCx.SYS for the 1st port must exist. The parameters for other ports will be taken by default, and then no conflict should happen between ports. If you want to define the streams differently on each port, you can do it with the INITTNCx.SYS file, but be sure to give the right configuration. If paclen is equal to 0, then the default BPQ paclen of the port will be taken, otherwise the specified paclen will overwrite the default BPQ paclen. If you have validated the gateway, you must configure ENABLE_LINKED=A in BPQCFG.TXT to give to the stream the callsign of the user. Here is an example of PORT.SYS with BPQ-node and 2 TNCs: # #Ports TNCs 1 2 # # #Com Interface Adress (Hex) Baud 8 2 0 4800 # # #TNC NbCh Com MultCh Pacl Maxfr NbFwd MxBloc M/P-Fwd Mode Freq 1 8 8 0 230 4 1 10 30/60 UQYW VHF 2 1 8 1 80 1 1 5 30/60 UQYW HF # Example of INITTNCx.SYS for BPQ 4.05 (Only ONE INITTNCx.SYS) : A1 Number of application R0 Returns to node (0=No,1=Yes) UMAIL Unproto MAIL M1 Monitor (0=No,1=YES) N1 Number of first stream The parameters for other ports will be taken by default, For instance, as the first stream of the first port is 1, the first stream of the second port will be 9. (8 channels defined in PORT.SYS for port 1). This will be done automatically, and the second INITTNCx.SYS should not exist. In FORWARD.SYS there are a few changes, here is a short example: A LA2D # P B # C C SWITCH Connect first BPQ switch. FBB 5.15 Feb 06 1993 Page - 43 C C 2 LA2D Connect LA2D on port 2 of BPQ. # B LA2D F LA2D # --------- FBB 5.15 Feb 06 1993 Page - 44 6 BBS COMMANDS: --------------- ? : Reading the help file. Type in "?[COMMAND]" to obtain help on a basic command. > : "Break" between channels. Type in > [CALLSIGN] [TEXT] to send a text to a connected callsign on another channel. You will get back a message from the machine telling you that the text has been delivered. This text cannot be longer than one line. = : Connection between two channels. Type in = [CALLSIGN] to get connected to a callsign on another channel. The callsign can be connected only if it is not busy in a command; the BBS should be idle (waiting for a command). If the callsign is not available, either you wait or you cancel your request. The callsign currently busy in forwarding tasks cannot be connected. A Ctrl-Z is used to leave this mode. ! : Provides a short and minimal information on the BBS usage. A : Aborts the BBS output at any time. B : Disconnects the BBS. C : Enters the conference mode, multiconnection. The command CW yields the list of the callsigns involved in the current conference. Any text typed in while in the conference is sent out to all the parties involved. A header before the text shows its origin. The header is not repeated if the next text has the same origin. In the conference, the commands should begin with a semi-colon in the first column, so as to be interpreted. Commands in the Conference mode: .C[PORT] CALLSIGN : connection to a callsign on a port. The port indication is optional; the port of the connected user is then choosen as a default. .D CALLSIGN : Disconnects the callsign from the conference. .H : Help .W : List of the participants in the conference. .Q : Exit of the conference. D : Invokes the FBBDOS or Receive a file from the BBS if the command is followed by a file name. F : Switches to Server mode, and access to special commands. G : Access to the Gateway. FBB 5.15 Feb 06 1993 Page - 45 Gateway commands: B : Exit the Gateway K : Enters Converse mode. C : Connect. D : Disconnect. H : Help J : Lists the 20 last stations heard on the port. P : Link from one port to another. Once the selection of an authorized port has been made, a channel will be granted, depending upon availability. This channel will use callsign. Switching to converse mode is automatic when the corresponding station is connected; switching back to command mode takes place on a disconnection, or if the Esc character or a > in the first column is sent out. Switching to converse mode can also be made with the command K. The C command must be followed by the destination callsign, and optionnaly by the letter V followed by a string of digipeater callsigns. C Destination call V repeat1 repeat2 ... H : Same meaning as the ? command. I : Informations about this BBS. This command displays the file FRANCAIS.INF (or another language depending upon the configuration and the language attributed to the involved channel). I callsign : Gives the informations on callsign taken from the white pages database. Callsign can include wildcards. I@ bbs : Gives the users of BBS found in the WP database. IH route : Gives the users of the hierarchical route area from WP database (wildcards are allowed). IZ Zip : Gives the users of the ZIP code area from WP database (wildcards are allowed). J : Lists the callsigns heard by or connected on the BBS. JK : Shows the last 20 connected callsigns. JA : Connected callsigns on port A. JB : Connected callsigns on port B, etc... J1 : Heard callsigns on port A. J2 : Heard callsigns on port B, etc... K : Deletes the messages sent by you or to you. K msg# : Deletes a message identified by its number. KM : Deletes all the messages addressed to you, that you don't yet read. The messages not read will not be deleted. L : Lists the new messages since the last usage of this command. FBB 5.15 Feb 06 1993 Page - 46 LB : Lists the Bulletins. LC [mask] Lists the Messages which "TO" filed matches with mask. * (star) allows to list all the messages and should be the default value. Type "LC *" to see all messages. LC alone gives the current mask. Mask is recorded for each user while disconnecting. LD> YYMMDD : Lists the Messages received after the specified date. LD< YYMMDD : Lists the Messages received before the specified date. LM : Lists the TO YOU mesages. LN : Lists the NEW messages TO YOU. LL 10: Lists the last 10 messages. LR : is equivalent to L but the messages are listed in reverse order. LS text : Searchs for a text in the messages titles. Usage of wildcards is allowed. L< Callsign : Lists the message originated from [Callsign]. The wildcards are allowed. L> Callsign : Lists the messages destinated to [Callsign]. The wildcards are allowed. L@ [BBS] : Lists the messages VIA BBS if specified. L@ alone lists the message without route. The wildcards are allowed. L msg#- : Lists all messages, starting from msg# L msg#-msg# : List of messages between the given numbers. M msg# File : transfer the text of the message msg# to the file File. This file will be placed in the directory USERS or from the root in case of a SYSOP user. MH msg# File : Identical, but the format is the R command. MV msg# File : Identical, but the format is the V command. MA msg# File : transfer the text of the message msg# to the file File. This file will be placed in the directory USERS or from the root in case of a SYSOP user. The message is appended to the file. MHA msg# File : FBB 5.15 Feb 06 1993 Page - 47 Identical, but the format is the R command. The message is appended to the file. MVA msg# File : Identical, but the format is the V command. The message is appended to the file. N : Entry or modification of the name (max 12 characters allowed). NH : Entry or modification of the Home BBS. A point deletes the current Home BBS. NL : Entry or modification of the QRA locator. NP : Modification of the password for the access via telephone modem. NQ : Entry or modification of the city (Qth). NZ : Entry or modification of the Zip Code. O : Display or setting of various options. OL : Lists the available languages. OL number : to select a language. ON number : defines the number of the thousand base for the messages. Example: ON 37 defines number 37000 as being the base for numbering the messages. Then the command R 25 will cause the message 37025 to be read, although R 36025 will actually read the message nr 36025. OP : validates or disables the scrolling of pages. OP nbr of lines : Initialization of the page scrolling OR : Validates or disables the list of all messages if the user has access to the whole list of messages (See security code 1 of INIT.SRV). PG [program]: PG alone gives the list of PG programs available in the BBS. If followed by a program name gives the control to this program. The PG program can also be called by its name. If the name is the same that an existing command, the existing command will be replaced with the PG program. PS : Gives the list of servers available in the BBS. R : Reading of messages. R msg# msg# : FBB 5.15 Feb 06 1993 Page - 48 reads the messages by their numbers. RM : reads all the messages TO YOU. RN : reads all the NEW messages TO YOU. S[type] callsign : will send a message or a bulletin. If the type is not specified, it will be processed as a private, provided the destination callsign is a valid one, otherwise it will be considered as a message. SP callsign : sends a private message. S callsign @ BBSCALLSIGN : sends a message to a station AT another BBS through "fo BBSCALLSIGN can be an address of hierarchical type, for F6FBB.FRA.EU. Type in "SB ALL" to send a bulletin addressed to ALL. The message must be terminated by a Ctl Z or /EX followed by a return. Warning: the /EX must be in the first column. SC Msg# Callsign @ BBSCALLSIGN : Copy of a message or bulletin to the specified callsign. Such a copy will always be of the "personnal" type. SR [Msg# [title]] : Reply to a message already read or formerly suppressed, or to a message matching the specified number. If the title is not stated, it will be the title of the read message, with the mention "Re:" placed ahead. T : Paging the SysOp. Should the SysOp be not available within a minute, you will be advised accordingly and automatically returned to the normal BBS menu. U : Sends a file from the user to the server of the BBS. The file will be written in the root directory of the FBBDOS. The U command is to be typed in at the BBS prompt, it is not necessary to go to FBBDOS before. V : Version number of this BBS software. It gives also the number of active messages, and the next message number. V msg# msg# : reads the messages by their numbers, including the headers. VM : reads all the messages TO you, including the headers. VN : reads all the NEW messages TO you, including the headers. W : Lists the files which are within the user directory. This command can be followed by a mask specifying search criteria or a directory name; in the latter case, the directory content will be listed. X : Toggles "normal" or "expert" status. "Normal" grants the extended menus, "expert" provides only minimal informations. FBB 5.15 Feb 06 1993 Page - 49 Y : Binary transfer program using the YAPP protocol. As a user, you should also have the YAPP protocol available your end, in order to be able to transfer binary data. YD File : Reception of a file FROM the BBS TO you. YI [mask] : lists the available binary files, and their description. YN [mask] : lists the NEW binary files since your last connection. YU File : transmission of a binary file from you TO the BBS. You cannot replace or modify an already existing file. YW [mask] : lists the available binary files. YZ Filename : deletes the specified filename in the YAPP directory. Z Filename : deletes the specified filename in the user directory. FBB 5.15 Feb 06 1993 Page - 50 7 SERVER COMMANDS : ------------------- 7.1 Main menu : --------------- The server commands are gathered in groups. C : Connections - Statistics. D : Documentation. I : Informations, documentation. Q : QTH locator. N : Ham Callsigns Directory ("Call-Book"). T : Satellite orbits computation. F : Switches back to BBS mode. B : Quit and disconnects FBB 5.15 Feb 06 1993 Page - 51 7.2 Connections - Stats: ------------------------ Statistical data about the operation of the Server and the Traffic Log. O : Activity of the different groups. G : Global statistics. L : List of connections. H : Hourly usage. J : Daily usage. I : Users Callsign list. O : Percentage of usage for the different activities. G : General informations on the server: - Number of active messages. - Number of connections. - Times of connections. - Peak traffic periods. L : Lists the connections (Traffic Log). For each and every connection, the channel - callsign - date and time - as well as the connection duration are indicated. These informations are listed in reverse chronological order. H : Histogramm by hours. J : Histogramm by days. I : List of the callsigns that have connected the server. This list is given in alphanumeric order. FBB 5.15 Feb 06 1993 Page - 52 7.3 Documentations. ------------------- You will find under these comments the informations or documentations given by various hams. The documentation is organized like the image of a tree structure whose root is defined in INIT.SRV (C:\DOCS). The directories represent the topics and the files represent the documentation. The selection of the topics or the documentation is made through numeral command. The menu is presented with the form of one or several numbers followed with their description (topics or documentations). In the case of topics, the description corresponds to the name of the MsDos directory. This name is eleven characters long, the dot between the name and the extension will not appear. It is possible also to simulate the space character with an underscore character. In the case of documentation files, a label of 30 characters is associated to the name of the MsDos file. The label only will be presented to the user. To optimize the fill up of the screen, each line will contain two labels. In the case of a user, given the right of SYSOP, the display will be different. One line will contain only the name of the MsDos file followed by its label. L gives the list of the documentation on the current chapter. Labellizing of the files is made by the command D, reserved to SYSOP, or automated through the NEWDOC server (See paragraph 15 : SERVERS). Example : D BBS.DOC Documentation of the BBS. FBB 5.15 Feb 06 1993 Page - 53 7.4 Callsigns Directory. ------------------------ You will find in this module the informations that the users will have accepted to leave there: name, first name, address, phone number, etc... You will be able, as well, to update your own various informations. N : to modify your name and address. R : to search for informations about a user. I : to list the connected callsigns. N : Modifies your name and address. If these informations in the file are erroneous, or should they have changed, you can modify them with this command. A space or a return as an answer to the question will not modify the content. If the content of the file is correct, you can modification by replying N to the modification request. R : Search for information about a user. If the user is known in the file, you will get informations for him. You can concatenate the callsign of the user who is searched for behind the command. Ex.: R F6FBB will give informations about F6FBB. I : lists the callsigns of the users who connected the server. This list is sorted in an alphanumeric order. FBB 5.15 Feb 06 1993 Page - 54 7.5 QTH locator. ---------------- The QTH locator is made of 2 letters, 2 figures, and 2 letters yielding the geographical coordinates of a station. You can translate the QTH locator into Longitude/Latidude or vice-versa, compute the distance and azimut between two QTH locator or compute your Log-Sheets for contests (summi distances). Q : Converts QTH Locator into Longitude/Latitude. L : Converts Longitude/Latitude into QTH Locator. D : Distance and Azimut computation between two QTH Locators. C : Sum up all distances between one QTH Locator and several other QTH Locators. F : Switches back to the Server main menu. B : Quit and Disconnect. Q : Converts one QTH Locator into Longitude and Latitude. The West longitude and North latitude are given in degrees minutes, or grades. L : Converts the Longitude and Latitude into QTH Locator. The west longitude and north latitude can be given in centesimal degrees, degrees minutes, or grades. D : Computation of the distance and azimut between two QTH Locators. The distance is given in Kilometres and the azimut in degrees. C : Sum up the distances. After having entered the QTH Locator which will be used as the origin for the computation, you will enter the QTH Locator of the destination. The computed distance can then be summed up with a second or several other computations, thus allowing you to get the total number of kilometres. FBB 5.15 Feb 06 1993 Page - 55 7.6 Satellite orbital computation. ----------------------------------- Satellite orbital parameters computation, and satellite characteristics. P : Display of orbital parameters. C : Amateur Satellites characteristics. F : Switches back to Server main menu. B : Quit and disconnects. T : Satellite orbital computation. To select a satellite, type the number (a list of the satellites can be obtained with the command L instead of the number). Once the satellite has been selected, you will have to supply the date and the time to be taken into account for the computation. If you only answer with a return character, the current date (or time) will be taken. The geographical position is the QTH Locator of the connected user, if it is known in the file. Otherwise, the QTH Locator of the server will be used as a default. Depending on the satellites, the computation step can be variable, and one line of parameters will be displayed per step. This line corresponds to a minimal elevation of -5 degree s, that means the satellite 5 degrees below the horizon. P : Selected satellite orbital parameters display. These parameters will be used for the computation. C : Characteristics and informations regarding the selected satellite. FBB 5.15 Feb 06 1993 Page - 56 8 SYSOP COMMANDS : ------------------ 8.1 Commands available under the BBS menu. ------------------------------------------ DU callsign : Displays the informations related to the given callsign. DB : Lists the BBS callsigns. DE : Lists the EXCLUDED callsigns. DS : Lists the SYSOPS callsigns. DX : Lists the EXPERT callsigns. DP : Lists callsigns which are using the page scroll. E msg# : Edits the message # header. The message header is first displayed, then a string of options will allow you to edit the various fields of this header. A "return" terminates the edit. EU callsign : Edits the main parameters of a user. The user's parameters are first displayed, then a string of options will allow you to edit the various parameters. A "return" terminates the edit. Most of fields can be cleared with a point. A user can be edited while connected and then action is immediate. Flags are : R : All mail (included personnal) can be read P : Paging validated B : BBS S : Sysop X : Expert L : Local (Allowed to all commands on guest access). E : Excluded (cannot connect to the BBS) M : Modem access U : Unproto (Allows unproto list requests). Other commands must be followed with the information : G number : selected language N name : name of the user W password : password of the user V directory: private directory of the user (12 characters max) H home-bbs : home-bbs of the user Z zip-code : zip-code of the user FA msg# BBS : Specifies that the message defined by its number will be forwarded to the specified adjacent BBS. FB BBS : Gives the list of messages which are in the waiting list for this BBS. FC Route : FBB 5.15 Feb 06 1993 Page - 57 Gives the list of BBS routing the specified route. If the route is a possible callsign, will look for BBS routing, if composed with digits will look for NTS routing, otherwise will look for bulletins (group) routing. FD msg# BBS : Removes the message # from the forward to the specified adjacent BBS. FH BBS : Gives the hierarchical extension for BBS. FI BID command: BID maintenance. Command = ? : Gives message number and the message type of the BID/MID. + : Adds the BID/MID to the list. - : Deletes the BID/MID from the list. FL [BBS] : Lists the messages in the queue (for BBS if specified). FN Msg# : List of the BBS which are in the waiting list for this message number, and the BBS already forwarded or named in the preamble. FP command callsign: Swap test. Command = @ : Gives the swap (if existing) for the via callsign. > : Gives the swap (if existing) for the to callsign. < : Gives the swap (if existing) for the from callsign. FR BBS : Forces reverse forwarding to BBS, even if there is no pending mail. FS Argument : Stops the forwarding. If the argument is a callsign of known BBS, the forwarding to this BBS will be stopped. Although the argument can be a port number, in this case the forwarding will be stopped on that port, if 9 is specified then the forwarding will be stopped for all the ports. FT [BBS] : Lists the volume of the messages which are waiting for the BBS if it is specified. FU Channel : Immediately disconnects the specified channel. FV : Recompiles FORWARD.SYS and its include files, SWAPP.SYS and BBS.SYS and then starts scanning the messages to update the forwarding list. This can be needed after a FORWARD file change. FW Argument : Initiates the forwarding if the argument is a callsign of a known BBS. The forwarding throught this BBS is started and the parameters of FORWARD.SYS file are taken into account. The parameter can also be the number of a port, in which case the forwarding will be started for this port, if 9 is specified the forwarding will be initiated for all the ports. IE Callsign : Gives first the WP information using IL format (see below), and then prompts the deletion of the record. If the answer is Y, the record will be deleted, else you enter the edition mode. Type return to exit edition mode. The commands are : U : Updates primary part with the temporary part (2 -> 1). FBB 5.15 Feb 06 1993 Page - 58 N name : Changes the name of the user. 1H Route : Changes the primary route. 1Q Qth : Changes the primary Qth. 1Z Zipcode : Changes the primary ZipCode. 2H Route : Changes the temporary route. 2Q Qth : Changes the temporary Qth. 2Z Zipcode : Changes the temporary ZipCode. IL Callsign : Gives all the information from the white pages database. Kx : The fact that a leading K is entered before a kill command with the letter K (I.E. KK, KK<, ...) triggers immediate killing of the specified message. The archiving will be done at the next epurmess process according to epurmess parameters. The status of the message becomes "A". The syntax is identical to the command "K". K> callsign : Deletion of any message to this callsign. K< callsign : Deletion of any message sent from this callsign. K@ route : Suppresses all the messages which have the specified route. KF : Suppresses all the messages already forwarded. $ msg# : Informations about msg# forwarding: lists the BBS which have not yet received the message #. LU (RU) : Lists (or displays) all the private messages which have not yet been read by their addressee. Mx : Same as the command "L", with the same syntax, but the BID is inserted at the beginning of the field "SUBJECT". This command allows you to do some search or to visualize BIDs in the message lists (commands MS, ML, etc...). PR : Enables or disables the printer from the console. The printer is automatically disabled on disconnect. PR[V] #Msg : Sends [verbose] message to the printer. PR> filename : validates and redirects the printing to a filename. PR> - : validates and redirects the printing to the standard printer. SR [#msg] [+filename] [subject] Reply to a message already read or formerly suppressed, or to a message matching the specified number and appends the contents of filename. If the subject is not stated, it will be the title of the read message, with the mention "Re:" placed ahead. SYS : Enables remote Sysop mode. A callsign validated as SYSOP is permitted to access any message in any circumstance, but he cannot delete or modify data which do not belong to him. The SYS command will grant him these privileges, together with the ability to enter the root of the DOS directory tree in FBBDOS. The SYS command will return a string of corresponding to the position of a letter in a sentence located in the PASSWD.SYS file. If you send back the 5 letters (without any space) matching the 5 numbers, an OK will be sent out to confirm that the SYSOP mode is granted. YL file : Modifies the description of an existing YAPP file. FBB 5.15 Feb 06 1993 Page - 59 8.2 Other commands. ------------------- M : In the SATELLITE ORBITAL COMPUTATION menu, manual modification of the orbital parameters of the satellites. N Callsign : In the NOMENCLATURE menu, this command allows to edit/mo nomenclature informations of a user. S file : In the gateway and in command mode, send an ascii file. W file : In the gateway, opens a capture file. The file is closed with another W command. YU Filename : In gateway mode and only from the console send a binary file to a remote system under the YAPP protocole. YD Filename : In gateway mode and only from the console receive a binary file from a remote system under the YAPP protocole. FBB 5.15 Feb 06 1993 Page - 60 9 FBBDOS COMMANDS : ------------------- The syntax of the various FBBDOS commands is very close to that of MsDos (R). Several specific commands have been added: PUT and GET for ASCII file transfers. XPUT, YPUT and XGET, YGET for binary file transfers. EDIT for ASCII files edition. When entering FBBDOS, the prompt shows the virtual directory in which the user is located. There is no physical drive concept (A, C, etc...), the user is situated in a directory defined in the INIT.SRV file; this directory becomes the root of the available directory tree. Should the user be a SYSOP, and if he successfully validated his privileges using the SYS command, the root of FBBDOS will be the root of the current drive. A file created by a user belongs to this user. Only the owner of the file, or a SYSOP granted writing privileges (SYS command) are permitted to delete or modify this file. CD directory : Changes the active directory. This command allows you to move within the directory tree by changing the active directory. "CD.." changes back by one directory "upstream" towards the root. COPY Origin Destination : Copies a file into another file. If the destination file already exists, it must belong to the user. DEL file : Deletes a file. A file cannot be deleted if it does not belong to the user. DIR [mask] : Displays all the files contained in the directory or these corresponding to the mask if it is specified. If the mask matches a directory name, the content of this directory will be listed. DOS Program Arguments : Allows a remote SYSOP (after SYS command) to run a DOS program. This program can not expect keyboard input. A list of arguments can be specified. The output to the screen will be send to the remote SYSOP at the completion of the program. If the program expects inputs, after a time-out of 2'45, it will be aborted (if possible) and the normal operation will resume. DU [mask] : Gives the size of the tree, and local used disk. EDIT file : Edition of a text file, using the line editor. If the file already exists, it must belong to the user. The instructions to use the line editor can be found in the Appendix 1. EXIT : Exits FBBDOS and brings back to the BBS or server. FBB 5.15 Feb 06 1993 Page - 61 GET file : Displays the content of an ASCII file. Such a display is never scrolled by pages, and ends with a Ctrl-Z, thus allowing ASCII file transfers from the BBS to the user. LIST mask : Displays all the files contained in the directory or these matching the mask specified. if the mask matches a directory name, the content of this directory will be listed. Each line displays the filename and a descriptive comment (cf YI command). MD directory : Creates a new directory. The new directory is appended next to the current directory. O : Display or setting of various options. OL : Lists the available languages. OL number : to select a language. OP : validates or disables the scrolling of pages. OP nbr of lines : Initialization of the page scrolling PRIV : Access to a private directory (or return to Fbb-Dos directories). Each user can have access to a private directory provided it has been defined by the SYSOP (I.E. EU command). Several users can share a private directory. PUT file : Accepts an ASCII file from a user. The file must end with a Ctrl-Z to be validated. If the file already exists, it should belong to the user. RD directory : Deletes a directory. A directory cannot be deleted as long as it is not empty. TYPE file : Displays the content of an ASCII file. Eventually, this list can be scrolled by pages. VIEW mask : Displays the content of all the archive files contained in the directory and corresponding to the specified mask. This function uses the FV.COM shareware. Thanks to the authors of this last one. XGET file [offset]: A binary file is sent by the BBS. The Xmodem protocol is used. This command works only on a PSTN modem port. If offset is specified, download will start from offset. XPUT file : The BBS receives a binary file. The Xmodem protocol is used. This command works only on a PSTN modem port. YGET file : FBB 5.15 Feb 06 1993 Page - 62 Transmission of a binary file by the BBS. Both YAPP and YAPC protocols are used. YPUT file : Reception of a binary file by the BBS. Both YAPP and YAPC protocols are used. FBB 5.15 Feb 06 1993 Page - 63 10 CONSOLE COMMANDS : --------------------- Most of these commands will open a window. The server operations is suspended while this windows stays open, but the user requests are queued and will not be lost. If no reply is given, the window will close down after a few seconds, and the default reply will not be taken into account. Do not forget to validate your replies with "Enter". F1 General help related to commands attribution. F2 Connection to the server in local mode with the callsign specified after "Console:" F3 Manual disconnection of one channel. F4 Manual forwarding request, or cancellation of current forwarding. If a number up to 8 is specified, the corresponding port will be scanned for forwarding. If the number 9 is specified, all ports will be scanned. If a callsign is specified, it will be scanned for forwarding. Preceeding the callsign with + will force reverse even if there is no waiting mail, preceeding the callsign with - will stop the forwarding and disconnect. F5 Split screen. The upper part is for internal server traffic purpose, the lower part shows the traffic flow on the various channels. The up and down arrow keys are used to move the separation border between the two windows. Pressing F5 again toggles back to a single window display. F6 Used to change the console callsign. Thus, you can simulate a call from a user. F7 Direct commands to the TNC. This allows a dynamic modification of the parameters which will be affected as default to the channels of the related port. These parameters will not be taken into account for the channels already connected, and will be transferred to the channel upon disconnection. The commands are specific to the TNC in use: WA8DED with a TNC2, HostMode PK232 with a PK232, or the BPQ node. F8 Server reboot. The cleaning and the housekeeping of the mail is not done. The reboot can take place at once (immediate disconnect of channels in use), or delayed (awaiting the normal disconnect of all the active channels). F9 Traffic with the console callsing (Gateway mode). F10 Switches to chat mode with the user who requested this mode (using the T command), or end of chatting (user is returned to normal BBS usage). ALT-F1 Displays the volume of the forwarding queues sorted per BBS. ALT-F2 Displays the list of the stations connected at the time this command is keyed in. ALT-F3 Starts or stops the messages scanning after the modification of the FORWARD.SYS file. Before starting scanning, FORWARD.SYS and its include files, BBS.SYS and SWAPP.SYS are recompiled. ALT-F4 List the last connections. ALT-F5 Call the full screnn tiny-edit (cf para. 12). ALT-F6 Miscellaneous options: FBB 5.15 Feb 06 1993 Page - 64 - Valid call : Enables the T command. - Connection Bip : Beeps on every connection. - Display calls : Displays the channel and the callsign. - Gateway access : Gatewaying between ports is enabled. - Justification : The texts typed in at the console are justified. ALT-F7 Forward imports out of an external file (MBL compatible). ALT-F8 Forward exports to an external file (MBL compatible). ALT-F9 Jump to DOS (EXIT to return). WARNING: the BBS operation is suspended all this time long. The users will not be disconnected, and their commands will be queued. F10 Complete server shutdown. The shutdown can be immediate (disconnection of the active channels), or delayed (awaiting the normal disconnect of all the active channels). ALT-B Forces screenblank. ALT-D Writes the current screen buffer to a file ALT-R Redisplays the screen ALT-X Server shutdown (idem ALT-F10) ALT-N Allows reprogramming a telephone modem ALT-S Swap to DOS screen Arrow -> Display next channel. Arrow <- Display previous channel. Ctrl -> ou Ctrl <- Return to the display of all channels. PG-UP Display the previous page if it exists PG-DW Display next page. HOME Display the first page. END Display the last page. FBB 5.15 Feb 06 1993 Page - 65 11 TEXT VARIABLES : ------------------- 11.1 Variables definition. -------------------------- Most of the text files support usage of variables. These variables enable text or values to be placed, depending upon the context or the channels in use. These variables are defined with the $ sign, followed by a letter. The meaning will be different if the letter is in capital or in lower case. A second set of variables is defined with the % sign, followed by a letter. They can also be followed by a figure and in this case, this is a parameter whose value is function of the context. These particular variables are used in texts, usually as computation results. Do not use them in other places than text files (*.TXT). The $ sign will have to be written $$, if it is not to be considered as a variable. The % sign will have to be written %%. FBB 5.15 Feb 06 1993 Page - 66 11.2 List of the variables. --------------------------- $0 - $9 : Temporary variables. $A : @ BBS of the message header. $a : Year of the current date. $B : Inserts a Ctrl-G (Bell). $b : Zip code of the user. $C : Number of the next message. $c : City where the BBS is located. $D : Current date (Format : YYMMDD). $d : Current date (Format : DD-Dec). $E : Version number. $F : Minute of the hour for forwarding. $f : File appended to the message header. $G : Destination of the message header. $g : Number of gateway ports available. $H : Current time (Format : HH:MM). $h : Home BBS of the user. $I : First name of the connected user. $i : Date and time of the message header (Format MMDD/HHMM). $J : Date of the message header (Format YYMMDD). $j : Date of the message header (Format 29-Dec). $K : Time of the message header (Format : HH:MM). $k : List of the users involved in the conference. $L : Number of the last used message. $l : Filter value of LC command. $M : Number of the message header. $m : Frequency of the port in use. $N : Number of active messages. $n : Size of the message header. $O : BBS callsign. $o : SSID of the BBS. $P : Origin of the message header. $p : Number of lines of scroll page option, for the connected user $Q : List of the 8 callsigns which have new messages. $q : Base messages number of the user. $R : BID of the message header. $r : L or space character. L means that the message was locally created. $S : Subject of the message header. $s : Status of the message header. $T : Time of message header (Format : HH:MM). $t : Type of message header. $U : Callsign of the connected user. $u : Current drive in FBBDOS. $V : SysOp first name. $v : Complete route (with the hierarchical structure). $W : Inserts a carriage return. $w : Inserts an escape character. $X : Date of the last connection (Format : 881229). $x : Date of the last connection (Format : 29-Dec). $Y : Time of the last connection (Format : 12:30). $y : Year of message. $Z : Last message read by the user (L command). $z : Zip Code of the BBS. $* : Number of active channels. $= : User's current channel. $! : User's current port. $^ : Number of allowed ports. $? : BBS QTH-Locator. $% : List of the connected users. $: : Connection duration (Format : 12mn 05s). $. : Machine operation time (Format : 12mn 05s). FBB 5.15 Feb 06 1993 Page - 67 $$ : Character $ Second set of variables : (unformatted means that text is not padded with spaces) : %A : @ BBS of the message header, unformatted. %G : Destination of the message header, unformatted. %i : Date and time of the message creation (Format MMDD/HHMM). %J : Date of the message creation (format YYMMDD). %j : Date of the message creation (format 29-Dec). %K : Time of the message creation (format HH:MM). %M : Numer of the message, unformatted. %n : Size of the message header, unformatted. %P : Origin of the message header, unformatted. %y : Year of the message creation. %% : Character % FBB 5.15 Feb 06 1993 Page - 68 12 FULL SCREEN TINY-EDIT : -------------------------- The Tiny-Edit is started with the Alt-F5 command. Normal operation of the BBS is maintained, the editing takes place in the console window, above the monitoring area of the display. Most of the text files can be edited with this editor despite of its simplicity. The most concerning drawback is the fact that the line length can not be longer than 79 characters. The language files (xxxx.TXT) therefore cannot be edited. Tabs are not generated and are presentend on the display with a special character. During the editing, the usual BBS command set are no longer available, they are replaced by the tyni-edit commands. Upon activation of the editor, a dialog window ask for the filename to edit. The default directory is the directory "SYSTEM" as defined in INIT.SRV. Examples: FORWARD.SYS will edit SYSTEM\FORWARD.SYS FWD\F6FBB will edit SYSTEM\FWD\F6FBB It will be necessary to specify the full path for a file outside of the default directory root or located on another disk drive. If only the drive name is specified, the current directory on this drive is searched for the filename. Example: C:INIT.SRV will edit C:\FBB\INIT.SRV (while the current directory is c:\FBB). To edit a message, one should give the message number with a leading pound sign ('#'). Example : #42645 will edit the message number 42645. In case the edited file is a compiled one (I.E. FORWARD.SYS) it will be compiled again after the termination of tiny-edit Main Commands : --------------- F1 : Help windows. F2 : The edited file is appended to the incoming mail file of the BBS (MAIL.IN). F8 : Save current file. F9 : Save current file and exit. F10 : Exit Tiny-Edit without saving ! Caution : acted upon ! no confirmation requested before closure of the current edit session. Edit Commands : --------------- Almost all commands are available from the numeric key-pad. up-arrow : the cursor goes up one line FBB 5.15 Feb 06 1993 Page - 69 down-arrow : the cursor goes to next line right-arrow : the cursor moves forward one character. At the end of the line it goes to the beginning of the next line. left-arrow : the cursor moves backward one character position. At the beginning of the line it goes back to the end of the former line. page-down : the cursor moves toward the end of the current page. If it is already at the end of page position, then the next page will be displayed. page-up : the cursor goes back to the first line of the current page. If it is already at the first line, the former page will be displayed. home : the cursor moves to the first character of the current line. end : the cursor goes to the character position next after the last character of the line. insert : toggle the insert editing mode. The cursor is an underscore while in insert mode. It is a cursor block in overstrike mode. delete : erase the character at cursor position, the cursor is not moved. back-space : the character preceding is deleted and the cursor moves backward one position. Ctl right-arrow : the cursor moves to the first character of the next word. Ctl left-arrow : the cursor moves to the first character of the previous word. Ctl home : the first page of the file is displayed and the cursor goes to the first line. Ctl end : the last page is displayed and the cursor goes to the last line of the file. Ctl Y : the current line is deleted. Ctl Q : the current line is deleted from the cursor position up to the end. FBB 5.15 Feb 06 1993 Page - 70 13 EMS and XMS : ---------------- With the PC, DOS is drastically limited to 1 Mo. This limitation has been overcomed, thanks to some tricks of different flavours. Several standards had seen the day light, the most welknown in use to day are LIM-EMS and XMS. Both EMS and XMS are trademarks. 13.1 EMS (Expanded memory) : ---------------------------- EMS stands for Expanded Memory Specification. EMS works on all PC's and compatable, with a paging system for the memory (all the 386 family and some of the 286). Some add-on memory board on XT's or AT's support this feature, using software activated memory bank switches. Several drivers for expanded memory exists. As for examples, QEMM386.SYS (Quaterdeck) and EMM386.SYS (Microsoft) for 386 based machines. These drivers are to adhere to the LIM-EMS (Lotus-Intel-Microsoft). The most versions are 3.2 and 4.0. Several extension were made within the 4.0, nevertheless the FBB software accomodates both. The way it works is quite straightforward. The expanded memory is cut in 16K pages. A window of 4 pages (64K) is set in the standard addressing area of the PC and it allows the access to 4 pages of the extended memory. This window is usualy in the segment D000 or E000 outside of the 640 K. The size of the expanded memory depends on the total memory installed in the PC. The parameters given to the driver will allow the user to set the amount of the available memory which will be used as expanded (paged) memory. A command sent from the application software to the driver will specify the pages to be seen through the window and given access. It is then simple to write and read in the paged memory. This explanation is simplified, the LIM-EMS standard has the provision for many other extended features FBB 5.15 Feb 06 1993 Page - 71 13.2 XMS (Extended memory) : ---------------------------- XMS means eXtended Memory Specification. XMS works on most of the PC's and compatable 286 or 386 with extended memory above 1Mo. One of the drivers based on this standard is the HIMEM.SYS from Microsoft and being part of some software package or operating systems. (I.E. Windows). Other drivers are available on the market which support the same standard. This driver allows also the load and the activation of TSR modules in high memory (HMA). One trick in the behaviour of the 286 and 386, is such that in real mode, (similar to 8086 8088) the addressing does not cover 1Mo only, it covers actualy 1Mo plus 64K. In real mode the addressed segments are of 65536, each segment can be defined on 16 bytes boundaries. Example : Segment 1000 Offset 4000 (1000:4000) is actualy the 14000 address. Should we take the last segment FFFF (FFFF:0000), the address is FFFF0, and this corresponds to the MegaByte minus 16 bytes (each segment can be defined at each 16 bytes boundaries). In theory this last segment would normaly be limited to 16 bytes. In fact we go past these 16 bytes and thus gain access to the first 64Ko of the extended memory. This so called HMA (High Memory Area) is of 65520 bytes, from FFFF:0010 to FFFF:FFFF. Resident program can be loaded in this area, and executed. Beyond the HMA zone, the only way to access the memory is by the virtual mode (extended addressing). This addressing is transparent for the driver HIMEM.SYS and allows depending on the type of processor in use (286 or 386) to access a large amount of memory. This memory zone is called EMB (Extended Memory Blocks). It will be used to store and retrieve data. Access is given through HIMEM.SYS which works by copy, the processor being set in the driver in virtual mode (extended addressing). The copy process can be lengthy for large amount tranfers. The driver is stopped by high level interrupts such as the system clock and the prioritized I/O routines. FBB 5.15 Feb 06 1993 Page - 72 13.3 FBB and the additional memory : ------------------------------------ The FBB knows about the usage of both memory types (EMS or XMS). Messages lists are stored in this memory. Other data will be stored there latter-on. The increase in throughput for search is well noticed, response time for L>, L<, LS ... commands is ten to twenty times better, about 1 second for a 386. XMS release shoud be greater than 2.0. The type of handling is at first depending on the processor, XMS on standard 286, EMS or XMS on 386. The EMS can require an add-on memory board, the system is then rendered very efficient. Some of the 286 machines incorporate the hardware chips to carry on with the bank switching on the mother board. Others support this feature at the expense of heavy! software spoiling sometimes more than 64K of memory. The EMS on 386 machines calls only for a small driver like EMM386, QEMM386 (few Kbytes). 13.4 Choice of the add-on memory : ---------------------------------- The choice of the type of the add-on memory is conditioned by the harware of the machine to be upgraded. To summarize : XT : nothing but mandatory add-on card. AT 286 : always XMS sometimes EMS. AT 386 : all modes possible, EMS is the more efficient. FBB 5.15 Feb 06 1993 Page - 73 14 ASYNC PORT DRIVERS AND TELEPHONE MODEM. ------------------------------------------ 14.1 ESS.COM (BIN). ------------------- ESS is an async port driver optimized for FBB software. It can drive either TNC2/PK232/clones nor KAM. This small device driver is loaded as resident at the beginning of the machine initialization (TSR). One ESS handles one serial line and makes use of one IRQ. The COM number, the address of the serial interface and the IRQ number are given as paremeters appended to the command line. The address should be given as a FOUR digit hex number. Example : Install ESS for COM1 at hex 03F8 and using IRQ 4 : ESS 1 03F8 4 If only the COM number is specified, the address and the IRQ will default to the standard DOS value. Thus ESS 1 would have had the same effect than the example. Any address or IRQ number can be specified. Carefully check that the address and the IRQ number match the board you intend to use, special attention should be given to the IRQ number which should not already be used by another peripheral device in the machine. On a PC the IRQ's can not usually be shared. Should there be more than one port to handle, several ESS can be cascaded. The IRQ should be different for each ESS, except for the case in which the interrupt sharing is supported by the serial card used. Example : ESS 1 03F8 4 ESS 2 02F8 3 This sequence will load ESS's for COM1 and COM2. ESS accommodates also the muxing arrangement of serial ports. FBB 5.15 Feb 06 1993 Page - 74 14.2 FBBIOS.COM (BIN). ---------------------- FBBIOS is a serial line driver dedicated to the usage of a PSTN modem. Binary as well as ASCII file tranfer are supported with the XMODEM protocole. FBBIOS handles one serial line, one IRQ is required. The COM number, the address of the serial interface and the IRQ number are given as parameters appended to the command line, the address should be specified in FOUR hex digits. Example : Install FBBIOS for COM1 at hex 03F8 and using IRQ 4 : FBBIOS 1 03F8 4 If only the COM number is specified, the address and the IRQ will default to the standard DOS value. Thus FBBIOS 1 would have had the same effect than the example. Any address or IRQ number can be specified. Carefully check that the address and the IRQ number match the board you intend to use, special attention should be given to the IRQ number which should not already be used by another peripheral device. On a PC the IRQ's can not usually be shared. If the modem in use is at the HAYES standard, FBBIOS can modify the line speed according to the one of the incoming call connection. In this case the parameter 'A' should be appended to the command line to activate this feature. This is not true with some buffered modems using a junction with a settled speed. Example : FBBIOS 1 03F8 4 A Upon receipt of the string CONNECT 1200 or CONNECT 2400, the driver will adjust its speed to the incoming call. From version 1.30, FBBIOS.COM can run up to 56 KBauds. Be sure that your computer is fast enought ! FBB 5.15 Feb 06 1993 Page - 75 14.3 TELEPHONE MODEM : ---------------------- The FBB software allows the connection of a telephone modem on a serial port. The modem must be declared in PORT.SYS. It is necessary to use the FBBIOS.COM program. This driver performs BBS to Modem interfacing. It is therefore necessary to load FBBIOS prior to BBS start up. A line FBBIOS will be added ahead of APPEL.BAT file. See below an example of the APPEL.BAT file. Of course, the FBBIOS used will have to match the serial port on which the modem is to be connected (address and IRQ). FBBIOS will modify the RS232 speed according to the CONNECT info received from the modem : CONNECT 1200 set the driver to 1200 Baud. CONNECT 2400 set the driver to 2400 Baud. The driver is reset to the default speed rate (specified in PORT.SYS) at disconnect. At connect, the text ; "xxxx BBS. Phone Access" is sent by default. This can be modified by creating a file MODEM.ENT in the SYSTEM directory. You can specify in the PORT.SYS file that you accept connections, even if the user is not registered. In this case, the connection will be "read-only", the user has only a read only-access, he cannot download files or write messages, except to the sysop. When a non-registred user is connected, he will be signified that he only has a "read only access", and will be prompted to go on. If he answers "Y", he will go to the BBS menu, else he will be asked again for a callsign. Type of modem. -------------- Various experiments have been carried out with several different kinds of V22 (external, or internal cards) modems. If possible, modems at 1200 or better 2400 bps should be used; the modem speed is to be declared in PORT.SYS. Some modems can work either 1200 or 2400 bps, with an internal speed conversion between the modem and the computer. For example, the modem can transmit and receive on the telephone line at 2400 bps and talk to the PC at 1200 bps. If the modem uses the HAYES protocole, the INITTNCx.SYS file must hold the correct HAYES init lines. Protocol: --------- The configuration used is 1 start bit, 8 data bits, 0 parity, 1 stop bit, that is to say 10 bits words during the transmission. The Minitel standard is not supported (7 bits, even parity). The software being parametered by default in 8 bits, it was not possible to modify this protocol, as the binary file transfers are carried out on 8 bits. FBB 5.15 Feb 06 1993 Page - 76 The transfer of binary files is made with the Xmodem protocol. The frame size should be specified at 128 bytes. NB.: FBBIOS handles XON/XOFF protocol during the transmissions. Wiring for external modems. --------------------------- The modem must be able to tell the BBS that a call has been detected with the remote modem carrier detection. This is the reason why all the RS232 signals are used by the BBS. The RS232 cable has to be wired up pin to pin with no inversion: pins 2, 3, 4, 5, 6, 7, 8, 20, and 22 of the DB25 connector. Usage. ------ BBS users are not authorized to connect the BBS through a modem as per the default settings. The SysOp must declare the modem users. To do it, perform a user edition (EU call) and put M (for Modem) then W pass_word. A password made of the three last letters of the callsign can be attributed for the first connect. Then the user will be able to change it through the NP command. The authorized callsigns can be listed by the DM command. When a modem call occurs, once the modulations have been detected, the modem advises the BBS that a connection is effective on the telephone line. Then the BBS asks for the caller's call sign and password. The user is granted three tries before being disconnected. If everything is all right, the user can access the same commands like connected on a radio channel, he will have to disconnect using the B command. The log file is maintained for the connections through the modem channel. Keep in mind to add a line in the LOGFBB.CNF file for the modem calls to be processed in the stats analysis by LOGSTAT. Example of APPEL.BAT with FBBIOS for a modem connected to COM3/IRQ4 : echo off break off timer/s echo Appel du serveur ^C pour interrompre sleep 3 fbbios 3 03E8 4 serv %1 if errorlevel 2 goto direct if errorlevel 1 goto suite goto fin :suite etc........ Example of PORT.SYS file with 3 serial port used: COM1 for a TNC, COM2 for a TNC, COM3 for the modem. FBBIOS will have been previously configured for COM3 (3E8, IRQ 4). # Programmation and channel setup file # # number of Coms : COM1, COM2, Etc... # number of TNCs : number of frequencies used. FBB 5.15 Feb 06 1993 Page - 77 # #Ports TNCs 3 3 # # Com : COM number(1,2 .. 8) # Interface: 0 : Mode Direct # 1 : Mode Combios # 2 : Mode BPQ (BPQ in AA4RE mode) # 3 : Mode Modem # Address : in hexadecimal. Ignored if Combios/BPQ/Modem. # Speed : Baud rate of port. Ignored if BPQ. # # There must be as many lines as declared ports # #Com Interface Address (Hex) Speed 1 0 3F8 9600 2 0 2F8 9600 3 3 3E8 1200 # # TNC : TNC number, in increasing order. # Nbvoies : Number of channels dedicated to one TNC, depends on # the firmware used, the DED or the TF4 allowing a max of 4 # channels management, 18 with the TF18. # Com : Number of the Com to which the TNC is connected. # Canal : Number of channel if a MUX is used, or 1. # Paclen : Default TNC paclen value. # Maxframe: Default TNC maxframe value. # M/P-Fwd : start of forward: minute of the hour, and forward # period for corresponding frequency. # Mode : Access - One lettre out of: # B : Mode BBS. # G : Mode invite. # U : Mode Normal # Emulation - One lettre out of: # D : Mode DED. # P : PK232. # Options - Optionally, one or more letters out of: # M : Modem access. # Y : Yapp authorised on this frequency. # W : Gateway authorised to this frequency. # Frequence: Text giving the TNC frequency (9 characters max). # # There must be as many lines as TNC's declared. # #TNC NbCh Com MultCh Pacl MxBloc Fwd M/P-Fwd Mode Freq 1 5 1 1 230 2 1 10/60 UDW 144.675 2 4 2 1 250 3 2 12/30 UDYW 430.675 3 1 3 1 128 2 0 00/60 UM MODEM Example of INITTNCx.SYS file for HAYES modem : # ATZ ATS0=1 Example of FORWARD.SYS file to forward via modem. A protoco correction (like MNP) must be used to avoid any modifications of texts. The HAYES command ATDT diales the line, and when the connection is established, the callsign (preceded with a "." to avoid echoing) is sent twice and then the password. The callsign is sent twice in case of a problem the first time. ^M is the <return> variable. A LA1B FBB 5.15 Feb 06 1993 Page - 78 # P C <-- Modem port. # C C F6FBB ATDT19~~~12345678^M <-- Connects F6FBB using HAYES. V .F6FBB^M~~~.F6FBB^M~~~PASSWORD^M <--sends callsigns and password. # B LA1B F LA6CU # ------ In the PORT.SYS file, the number of forward channels for the TNC (modem) must be 1. #TNC NbCh Com MultCh Pacl MxBloc Fwd M/P-Fwd Mode Freq 1 5 1 1 230 2 1 10/60 UDW 144.675 2 4 2 1 250 3 2 12/30 UDYW 430.675 3 1 3 1 128 2 1 00/60 UM MODEM FBB 5.15 Feb 06 1993 Page - 79 15 MISCELLANEOUS TOOLS : ------------------------ A set of tools is available to the SysOp. These tools are for manual or automatic maintenance. In most of cases, these tools should be handled with caution, the process can be dangerous for the files. Avoid using those tools while the server is in operation (the F9 command, as for an example), because the modification of some files duri operation can yield unpredictable corruptions. FBB 5.15 Feb 06 1993 Page - 80 15.1 INSTAFBB.COM (BIN). ------------------------ This program is a fullscreen configuration of INIT.SRV. Most of commands are documented. You must only follow the instructions. If the INIT.SRV file does not exist, you will be prompted to create a new one. Be sure that you are in the FBB directory when running INSTAFBB.COM. If the INIT.SRV is not of the right version, you will also be prompted, but be carefull, as the results could be hasardous. The comments of the original file are not changed. FBB 5.15 Feb 06 1993 Page - 81 15.2 EPURMESS.COM (BIN). ------------------------ EPURMESS is a DOS tool which allows for modification of messages: status, removal, or archiving. This tool is called every night by the BBS in order to maintain the message list as a function of the time. The EPURMESS configuration is made by the text file EPURMESS.INI. The parameters which are contained are given as a suggestion, and can be edited later if needed, to suit the targeted archiving and the mass of messages and bulletins received. EPURMESS searchs the current directory for its EPURMESS.INI initialization file. In that file, it will find out all the parameters for processing, as well as the file name for the report EPURMESS.RES (this file name can be changed in the EPURMESS.INI file). At the beginning of the process, EPURMESS first copies DIRMES.SYS into DIRMES.OLD to keep an archive trace of the previous file, then creates DIRMES.NEW, in which the processing will take place. At the end of the process, DIRMES.NEW will be copied into DIRMES.SYS. A repor processing will be written in the EPURMESS.RES file. If the last update of the DIRMES.SYS file has been carried out more than 24 hours ago, EPURMESS will not make its process, in order to avoid any loss of data due to a possible clock error in the system. It will report the error in the EPURMESS.RES file. In such a case, after the reason of the error has been detected, it will be necessary to suppress the EPURMESS.RES report file, in order to re-enable the processing. The ARCHIVE line has two digits, the first one applies to private messages and the second to bulletins. The '1' digit validate the archiving while the '0' will suppress the messages once and for all. It is possible to specify origins, destinations or routing for which the obsolete time (X status) are different from the default values. These particular cases are specified at the end of the file with the form of supplementary lines. Each line specifies a particular case. The line should begin with the character which specifies the field to be tested, then the content of the field and then the number of days before the status X is given. Ex : > ALL 1 The messages for ALL will be valide only one day. Example of EPURMESS.INI file: # message file directory \FBB\MAIL\ # # message archive directory \FBB\OLDMAIL\ # # binary messages directory \FBB\BINMAIL\ # # Fichier DIRMES.SYS \FBB\SYSTEM\DIRMES.SYS # # previous file backup FBB 5.15 Feb 06 1993 Page - 82 \FBB\SYSTEM\DIRMES.OLD # # new file backup \FBB\SYSTEM\DIRMES.NEW # # report file \FBB\EPURMESS.RES # # Private and Bulletins : 0=destruction 1=archive 1 0 # # PRIVATE MESSAGES EPURATION PARAMETRES # PN -> PX (days after creation) 30 # # PY -> PX (days after change into Y) 5 # # PF -> PK (days after change into F) 1 # # PX -> PK (days after change into X) 2 # # PK -> PA (days after change into K) 2 # # BULLETINS EPURATION PARAMETRES # BN -> BX (days after creation) 7 # # B$ -> BX (days after creation) 4 # # BY -> BX (days after creation) 4 # # BX -> BK (days after change into X) 4 # # BF -> BX (days after creation) 4 # # BK -> BA (days after change into K) 1 # -------- # # Special cases # > ALL 1 @ FRA 10 # FBB 5.15 Feb 06 1993 Page - 83 15.3 EPURWP.COM (BIN). ---------------------- EPURWP is a DOS tool which allows updates and modifications of the white pages database. An optional parameter can follow and specify the number of days for a data to be valid. If the temporary part of the record has not changed during this number of days, then it will be considered as stable and transfered to the primary (used) part. FBB 5.15 Feb 06 1993 Page - 84 15.4 LOGSTAT.EXE (BIN). ----------------------- Statistical analysis software for the FBBLOG file written by FC1MVP. The configuration file for this software is in the text file LOGFBB.CNF, which should be located in the same directory. LOGFBB.CNF file layout : ------------------------ This file is made of several lines indicating: - BBS Callsign - the name of the SysOp port, a comment. - The abbreviated name of the 1st port, a comment. - The abbreviated name of the 2nd port, a comment. - and so on until the last port (8 ports maximum). - Three stars (***) at the beginning of the line means the end of the ports. - The BIOS screen access option. The BBS callsign must have 6 characters maximum. It will be truncated should it be longer. The abbreviated port name may have up to 10 characters, it is recommended to limit at 4 (ex VHF1 or HF2). A comma separates the abbreviated name from the comment which follows it, without any space. The comment may have 10 characters too (frequency). At the end of the comment, it is possible to add a comment which is internal to the CNF file, and which will not be used elsewhere, using the ":" as a separation. If the BIOS line has a NON at the beginning, the screen access will be direct. The word OUI means that the screen access is made via the BIOS. The direct access improves the processing speed by 50 percent but is careless with DesqView. Example of LOGFBB.CNF file: --------------------------- F6FBB : BBS name. SYSOP,at keyboard : port name @ , comment. VHF, 144.675 : Port A , comment. VHF, 145.275 : Port B , comment. UHF, 430.675 : Port C , comment. HF, 21.107 : Port D , comment. SHF, 1299,675 : Port E , comment. MODEM, Telefone : Port F , comment. *** End of ports definition. NON : Screen access through BIOS (OUI) or Direct (NON). Software limitations : --------------------- The software is able to handle a log file within the following limits: - Maximum number of days : 35, or 5 weeks if you chain 5 log files. - Maximum number of channels: 50 FBB 5.15 Feb 06 1993 Page - 85 - Maximum number of ports : 8+1, corresponding to ports A to H handled by the BBS and the SysOp keyboard "port". - Maximum nr of callsigns : 300 (This is not the number of the call signs known by the BBS, but the number of calls which were used the BBS during the log period. In case an overflow occurs, the mention AUTRES for the callsign and 99 for the day will be displayed in the corresponding areas. Regarding the forward efficiency, only the stations which have actually forwarded will be given a value, the others will be mentioned "nc". Usage : ------- On the same diskette (or the same disk) there should be at least the program LOGSTAT.EXE, the config file LOGFBB.CNF and enough disk free space for the result files to be created. The log file may stay on another diskette. For the startup you should type in LOGSTAT FBBLOG.nn (nn is the number of the week) or A:FBBLOG.nn (if the file is located on A:) The results are recorded into the files LOG.@, LOG.A ... LOG.T being the total of the logs. Archiving : ----------- A suggestion: you should better archive your FBBLOG.nn file rather than the LOG.x files. You should ZIP them (or ARC or LZH) with the name LOG990nn.ZIP (.ARC or .LZH) with 990 standing for 1990 (000 will be for 2000...) and nn is the number of the week. Log structure : --------------- The number of resulting files created is equal to the number of ports of the BBS plus 2. The 2 supplementary files correspond to the console port and the sum of the various ports as being the total result. The first log, named LOG.@ corresponds to the SysOp log (console), the last one, named LOG.T is the summation of the ports. The files LOG.A to LOG.H are the logs of the various ports. Obviously, if a port has not been used, the corresponding file will not be created. For each LOG.x file, you find in the following order: - Diary of the connections per day (y-axix) and the time (x-axix) with the daily total at the end of the line and the hourly total at the bottom of each column. - The total connection time: it is the sum of the connection times of each user. For the LOG.T file, the total connection time per channel will also be given. - Mean time per connection : this is the total connection time divided by the number of connections. - Mean time per user : total connection time divided by the number of users. - Number of killed messages : self explanatory. FBB 5.15 Feb 06 1993 Page - 86 - Number of read messages : idem. - Number of users. - A matrix of forwarded messages per day (y-axix) and per hour (x-axix) is made like before. This matrix will not appear if there has not been at least one forward on this port. - Number of forwarded messages: number of messages sent to another BBS or PMS. - Number of messages received in forward: number of messages transmitted by other BBS in forward. - Number of messages received in back-forward: number of messages received from another BBS when forwarding towards it. - Number of messages refused as already received. - An array giving the number and the size of the messages received from or sent to another BBS and the efficiency in Bits/s (Max 1200 !). The BBS's are sorted by alphanumeric order, and the efficiency indication appears for callsigns having conducted only forwarding operations. This matrix will not appear unless there has been at least one BBS forwarded. - A matrix of the main functions utilized, with on the y-axix the callsigns sorted by alphabetical order, and on the x-axis the total time of connections in minutes, the number of connections, and the various functions used (see the comment following the array). In the LOG.T file, the X.F column (forced disconnection entered by the SysOp) is replaced by the number of killing commands. At the end of each column is the compound sum. Log of a specific station. -------------------------- - The LOGCALL program yields generation of a log for a specific station The principle of operation is the same as for LOGSTAT, except that a supplementary calling parameter is required to define the station. LOGCALL FBBLOG.33 FE1ZZZ The generated file will be of the same format as the FBBLOG, but it will enclose only the lines specific to the callsign. The name of the file will match the format FE1ZZZ.LOG, if the requested callsign is FE1ZZZ. While executing LOGSTAT FE1ZZZ.LOG, you will have the statistics related to that station (in the LOG.A, LOG.B,...). If you specify the SSID, you will create a log corresponding only to the callsign and the specified SSID. Ex: LOGCALL FBBLOG.33 FE1ZZZ-2 Editing the file FE1ZZZ.LOG will allow you to display all the commands sent by that station. FBB 5.15 Feb 06 1993 Page - 87 15.5 SATUPDAT.EXE (BIN). -------------------------- SATUPDAT.EXE will read messages from AMSAT copied via packet radio. This is the english version of AJOURSAT.EXE. This software was developped by F6BVP. It extracts keplerian elements both in NASA and AMSAT formats and updates the results into the satellites data base of the F6FBB's BBS (SATEL.DAT) Loading SATUPDAT without arguments will print the following message on your screen (between lines -----): ------------------------------------------------------------------ Automatic update of satellites orbital parameters for F6FBB's bbs Version 1.77e - June 1991 - Bernard Pidoux, F6BVP Usage: SATUPDAT [file name<.txt>] </option> </option> Reading option: /a AMSAT format (default) /n NASA format Update option: /f merging new and old data (default) /u update only satellites present in the data base /s keep only satellites present in the input file <<767 satellites maximum>> ------------------------------------------------------------------ This version 1.77e verifies checksum both for AMSAT files and NASA files. For automatic update of keplerian elements into F6FBB's bbs just create a virtual BBS into BBS.SYS file. Its name could be AMSAT for example. Then declare the following forward in the file FORWARD.SYS : A AMSAT * G AMSAT P @ C C:\FBB\SYSTEM\SAT\AMSAT.TXT * ------ CAUTION: The name of the disk unit and the path name should be the exact one of your configuration. In order to run automatically SATUPDAT when your computer boots, you must modify the batch file like the following example: :direct if not exist c:\fbb\system\sat\amsat.txt goto appel cd \fbb\system\sat satupdat amsat /n > satupdat.res satupdat amsat >> satupdat.res del amsat.txt cd \fbb :appel echo Running the BBS ^C for stopping sleep 3 serv -t FBB 5.15 Feb 06 1993 Page - 88 if errorlevel 2 goto direct if errorlevel 1 goto suite :suite (Once again be carefull with the disk name and directories !) SATUPDAT OPTIONS ================ The default extention for input file is .TXT, however you can specify another extention. Both arguments after the filename in the command line are optional: the first one indicates the reading format, either the AMSAT format or the NASA "2-line" format. The first one is selected by default. The second option is for the choice of update mode. By default the program will merge the old list with the new one (same if you select option /f). Old data of satellites which are not present in the input file are kept as is and the other one are updated. Option /u can be selected if you dont want to add new satellites to the one already present. Only keplerian elements from known satellites are updated. This prevents the list to grow with incoming satellites that you are not eventually interested in. Option /s, on the contrary, gives you the possibility to keep only in the data base the data from the satellites whose name is in the input file. This can help you to suppress old satellites from the data base. In all cases the program takes care of the permanent data of satellites such as the frequency (for doppler) and the step for computing the tracking (you must provide both manually only the first time). If the keplerian elements of the input file are older than the one already present in the BBS data base, the old one are kept. The list is sorted by name in order to help the finding of the satellite name when someone is connected to the BBS. If elements for one satellite are duplicated in the input file, the program will look again for the newest data. Of course, if CRC computed by the program is not the same as the one in the input file, the program informs you that the CRC is BAD and it does not take the keplerian elements. In the batch file example given above you have certainly noticed that I call twice the program SATUPDAT with two different format arguments. The first time I ask the program to read the NASA format and the second time to read the default format AMSAT. The reason is that the probability for an error to occure in both formats for the same satellite is very small. Thus if an error occurs in one format the program will complete the update when he will found unaffected keplerian elements in the other format. Thanks to the recently adopted checksum by AMSAT! FBB 5.15 Feb 06 1993 Page - 89 15.6 SLEEP.COM (BIN). --------------------- Utility which spends the time (in seconds specified as argument) while doing nothing. It can be interrupted by a Ctrl-C, and allows interruption of a Batch file running. The syntax to call it is of the type : SLEEP nn nn is the number of seconds to wait. FBB 5.15 Feb 06 1993 Page - 90 15.7 TLABEL.COM (BIN). ---------------------- Utility to update the file YAPPLDL.SYS which contains the various labels (informations) of the files received while the YAPP protocol was used. TLABEL renames YAPPLBL.SYS into YAPPLBL.OLD and creates a new YAPPLBL.SYS containing only the labels of the existing YAPP files. This program was written by FC1EBN. The execution of this utility should be done only in the directory SYSTEM. There is no argument for this command. FBB 5.15 Feb 06 1993 Page - 91 15.8 MAKEPG.COM (BIN). ---------------------- Utility used to generate .EXE (or .COM) program file out of the binary file (xxx.BIN) using English or French language. The syntax is of the type: MAKEPG program FR To generate a program in French MAKEPG program GB To generate a program in English. MAKEPG can transform the following programs : SERV.BIN -> SERV.EXE MAINTINF.BIN -> MAINTINF.COM EPURMESS.BIN -> EPURMESS.COM EPURWP.BIN -> EPURWP.COM FBB 5.15 Feb 06 1993 Page - 92 15.9 SETUSER.COM (BIN). ----------------------- Utility giving the property of a file to a user for further use by FBBDOS. The syntax is of the type: SETUSER callsign filename. The command "SETUSER F6FBB TOTO" will allow F6FBB, and him only, to modify or delete the file TOTO. FBB 5.15 Feb 06 1993 Page - 93 15.10 CLEANUP.COM (BIN). ------------------------ Utility killing all messages files unused and not defined in DIRMES.SYS. This program should be run in the SYSTEM directory. The syntax is of the type : CLEANUP mail_directory Be carefull when using this utility. If another directory than MAIL or BINMAIL is specified, it should delete all the files of the directory. FBB 5.15 Feb 06 1993 Page - 94 15.11 MAINTINF.COM (BIN). ------------------------- Utility maintaining the INF.SYS file. The INF.SYS file holds the users' database. In case of problem in INF.SYS file, goto the SYSTEM directory and run MAINTINF followed by a number of monthes. The records of users not connected within this number of monthes will be deleted and these users will be asked as for a new connection. The number 0 will not delete any record and only check the INF.SYS file. FBB 5.15 Feb 06 1993 Page - 95 15.12 MAINTREJ.COM (BIN). ------------------------- Utility maintaining the REJET.SYS file. The REJET.SYS file describes the Reject, Hold and Local hold informations. The program reformats the lines and verify the number of parameters. FBB 5.15 Feb 06 1993 Page - 96 15.13 CUT.COM (BIN). -------------------- Utility allowing to peak a part of a file and copy or append it to another file. The format is : CUT From-file To-file length offset [/A] To-file will have added up to length bytes of From-file, starting at offset. If the switch /A is specified, then datas will be appended to To-file, otherwise To-file will be replaced. This little utility is usefull to take parts or file, or to do copy/paste with either binary nor ascii files. Together with the specification of the offset in the XGET command, in case of crash, first note the amount of datas already received (ie : 50300), save the part of the file already received, and then ask "XGET filename 50000". The transfert will start at offset 50000 and then you will be able to receive the end of the file. The paste the two parts, either with COPY command or with the CUT command. It is more secure to cut the first received part before as the last bytes should be garbaged. FBB 5.15 Feb 06 1993 Page - 97 16 WHITE PAGES DATABASE AND SERVER ---------------------------------- 16.1 DESCRIPTION. ----------------- The White Pages implementation in FBB software has been based upon the W0RLI model (many thanks to Hank for his work). I've tried to maintain a high degree of comptibility whilst making further development to my own criteria. I shall try to explain how FBB White Pages works. I have probably mis-understood some features of W0RLI's specifications but I hope that this will not greatly affect the compatibility. First of all, why do we need White Pages? White pages has some interesting features. Not least : - A dynamic database containing users Name, zip code, HomeBBS and QTH (as well as other fields). - Automatic addressing/routing of mail to the HomeBBS of the destination callsign. - A White Pages server for remote interrogation of the database. The database information is updated, firstly from the information given by users when they exercise the N, NH, NQ and NZ features at their home (or another WP equipped) BBS; and secondly, from information contained within the messages headers as they traverse the Network. The database is dynamic, it is changing constantly, and it updates itself in real time. Either as soon as a line of a message header is received when in ASCII forwarding mode, or when a complete message is decoded in compressed forwarding mode; or else when a user disconnects from the BBS (this is to prevent multiple updates being generated during a session). So, the database can hold many callsigns. In fact it maintains a list of all the callsigns seen from all individuals sending messages as well has all of the BBS's seen in the forwarding paths. More than 10,000 valid records is not impossible today, and this will surely increase as the number of packet radio users grows with each day. This will allow user to send messages to other users around the world without necessarily having to be concerned to find their full Heirarchical Address, the old principle of the user typing: BBS PROMPT > SP K6VAZ @ KM6WU.#CENCA.CA.USA.NOAM should now be replaced by the user entering: BBS PROMPT > SP KM6VAZ The BBS will add the HA and send the response: BBS PROMPT > SP K6VAZ WP ROUTING @KM6WU.#CENCA.CA.USA.NOAM ADDED TITLE ? If the routing destination HA is not recorded in the database then the user will be advised and prompted to enter the address manually. FBB 5.15 Feb 06 1993 Page - 98 Another capability of FBB White Pages is the automatic sending of update messages to other BBS's. These messages are generated every night during House-Keeping and are a listing of the additions and modifications made to the database during thhat day. These messages are sent addressed both to and from WP. When passing through or terminating at another White Pages equipped BBS, the message will automatically update the 'local' WP database at that BBS. This feature MUST BE USED WITH CARE, as updates can generate a lot of traffic and the Network must be able to support it. *** It's not be a good idea to send these update messages on HF ! *** A built-in White Pages server (WP) will provide information from the database in response to a remote request. This server is described in paragraph xx. All files used by White Pages are in the FBB\SYSTEM\WP subdirectory. 16.2 UPDATE REQUESTS. --------------------- The database receives information from three sources. The s indicated on each line of the update message as a suffix to the callsign:- - The /U suffix denotes that the information in this line of the update is User-Generated as is therefore assumed to be CORRECT. This information is collected by the BBS whenever the User responds to the N, NH, NQ or NZ commands. The date associated with the information is the date when the User disconnects that session. - The /G suffix denotes that the information in this line has been gathered by examining the header of a message to GUESS at which BBS the sender is registered. The HomeBBS of the User is assumed to be the BBS shown in the first R: header line. The date associated with this information is the date shown on this R: header line. - The /I suffix denotes information about forwarding BBS's taken from the R: header lines. This information can consist of the HA (the Heirarchical Address), the QTH (within brackets) and the zip code (following the Z:). The date of this information is again taken from the R: header line of the BBS in question. When the BBS is idle the Database Manager is called and the update information detailed above is processed. 16.3 DATABASE DESCRIPTION. -------------------------- The database is composed of individual records. Each record following components : - Callsign and Name. - Active information. - Temporary information. The active and temporary information components are identical and each includes the following fields: FBB 5.15 Feb 06 1993 Page - 99 - Date of the information - Hierarchical Address (one word) - Zip code (one word) - Qth (one or more words) Only the Active information is used for addressing/routing and database requests. 16.4 DATABASE MANAGER. ---------------------- This process freshens the database, following receipt of the new or changed information detailed above. The update subroutine will first look for an entry in the database for the callsign which matches the received information. If it does not exist then a completely new record will be created in the database and the information be used to fill what fields it can, in both the active and the temporary components. The date will be then changed to the one associated with the update information. If the record does already exist, then the unknown fields of both the temporary and active fields will be filled in, and those fields already known in the temporary part will be replaced by the new information if the date new information is younger than that already on file. The date will then be adjusted such that it is consistent with the updated information. If the new information is of the /U category, then the current fields will be replaced by the new information in both the primary and secondary (Active and Temporary) parts of the record, as this information has been input directly from the user. If the information was of another category then only the secondary (Temporary) part of the record will be updated, so the Active or primary record will remain unchanged at this time. If a field is changed, a flag giving the update request type is then validated. If the /U flag is already validated, it will not be replaced. This flag will be used in case the WP update messages are validated. 16.5 EPURWP AND UPDATE MESSAGES. -------------------------------- EPURWP is a maintenance program for the White Pages database which should be run during each House-Keeping cycle. The program conducts a validity check on each of the entries, and discards any "unwanted" records (in the case of an invalid callsign for example). The program also checks the date of the last update of the temporary part of each record. If this date is older than a pre-defined number of days (given as a parameter, default 40 days) then the temporary part is considered as stable, and then the known fields will be transferred to the Primary or Active part, which is then used to answer all addressing/server requests. This process ensures that the database is tolerant of users sending messages from mailboxes other than their normal HomeBBS. Once the Active or primary part of the record is set, then the temporary (or secondary) part can be updated/changed many times. Only once this temporary field has remained unchanged for 40 days, or the user excercises any of the "Nx" options at his new HomeBBs will the Active or Primary record be changed. FBB 5.15 Feb 06 1993 Page - 100 If the changes to the database are validated, then the record is marked with an update flag and a line will be appended to the file MESS.WP Each line of the outgoing WP update messages looks like : On 930123 FD1CDC/U @ F6FBB.FMLR.FRA.EU zip 31240 Claude Saint Jean Any unknown fields are replaced by "?" like : On 930123 FD1CDC/U @ F6FBB.FMLR.FRA.EU zip ? ? Saint Jean The U character is the update type. 16.6 WP SERVER REQUESTS. ------------------------ FBB software has an internal built-in WP server. The format of the WP server requests are as shown below : BBS PROMPT > SP WP @ F6FBB Title of message WP Request (does not matter) Text of message F6FBB ? EA3* ? ^Z (or /EX) The server will answer to the request with a private message, addressed to the sender, and routed to the BBS according to the first R: header line of the incoing request. The reply message is restricted to a maximum of 100 lines, as the use of wildcards in the request could generate a unacceptably long replies. FBB 5.15 Feb 06 1993 Page - 101 17 SERVERS ---------- The BBS software offers various servers which are triggered when machinable messages are received. The number of offered servers is is without limit. The servers are activated when receiving a message whose destination had been given at the end of the INIT.SRV file. Declaration of servers at the end of INIT.SRV : ----------------------------------------------- # # Indicateur de voies 11 # ------ # # Liste des services : # # Desti Nom du programme # REQDIR REQDIR.COM REQFIL REQFIL.COM NEWDOC NEWDOC.EXE # # Fin du fichier d'initialisation # Servers are exec programs whose behaviour is explained in appendix 9. They should be found in the directory containing the exec program SERV.EXE and the configuration file INIT.SRV. When a private message is received, whose destination is defined in the INIT.SRV file, the corresponding program to the destination is called with the name of a temporary file on the command line. This temporary file contains a message function of the requested server (see description of servers below). At the completion of the server program, the incoming mail file is checked to import an answer, should there be one. The message addressed to the server and the temporary file are erased after this processing. Various services can be developped, time available has its limits, but the imagination has not ! FBB 5.15 Feb 06 1993 Page - 102 17.1 REQDIR ----------- The REQDIR server sends back to origin of the machinable message the list of files (total or partial) of a directory. The standard command line of the message is used. The message should be of the private type and addressed to the BBS that we want to ask : SP REQDIR @ bbs-destination The title of the message contains two informations, the mask of the selection (*.EXE, *.*, etc...) and the @ sign followed the return bbs, that is to say yours. The return message will be addressed to the sender of the request via the return BBS. The mask can not be specified. In this case, all the files will be listed. Mask @ bbs-return <- mask of the selection The text of the message is not necessary, its content will be ignored by the server. Example : F6FBB BBS > SP REQDIR @ F6ABJ.FRA.EU Title of message : YAPP\*.ZIP @ F6FBB.FMLR.FRA.EU Text of message : /EX We assume with this example that YAPP is a sub-directory of the USERS directory (this a suggested configuration). FBB 5.15 Feb 06 1993 Page - 103 17.2 REQFIL. ------------ REQFIL server allows to send back the ascii file requested to the originator of the message. The message sent to REQFIL has a well defined syntax. The standard command line of message is utilized. The message should be of the private type and addressed to the BBS which we want to ask. SP REQFIL @ bbs-destination The title of the message contains two informations, the name of the requested file and the @ sign followed by the return BBS, that is to say yours. The return message will be addressed to the originator of the request to the return bbs. filename @ bbs-return The text of the message is not necessary, its content will not be taken into account by the service. Example : F6FBB BBS > SP REQFIL @ F6ABJ.FRA.EU Title of message : DEMOS\ESSAI.TXT @ F6FBB.FMLR.FRA.EU Text of message : /EX This example makes the assumption that DEMO is a sub-directory of the USERS directory. The answer of the remote mailbox will be of the form : SP F6FBB @ F6FBB.FMLR.FRA.EU < F6ABJ Req File: DEMOS/ESSAI.TXT Contents of ESSAI.TXT file ... /EX FBB 5.15 Feb 06 1993 Page - 104 17.3 NEWDOC. ------------ The NEWDOC server allows a simple and fast update of the documentation database (topic DOCS of the server). This server will create the file and will give it a label. It will not create a directory if it doesn't exist. Therefore it is necessary to prepare the directory tree structure before. A message will give a summary to the originator. The standard command line for messages is used. The message should be of type private and addressed to the BBS which will be updated. SP NEWDOC @ bbs-destination The message title contains two informations , the name of the file requested followed by the label to give to the file (see the description of the topics DOCS). Filename Label eventually on several words. The text of the message will be transferred in the documentation file. Example : F6FBB BBS > SP NEWDOC @ F6ABJ.FRA.EU Title of message : BBS\DOC_1.DOC This is the label of the documentation. Text of message : This is the content of the documentation. .... End of documentation. /EX This example assumes that the BBS is a subdirectory of DOCS, thus one of the topics of the documentation. If the NEWDOC.SYS file is specified, the server will be limited to the callsigns declared in this file, one callsign in each line. Example of NEWDOC.SYS file : F6FBB FD1CDC FBB 5.15 Feb 06 1993 Page - 105 17.4 REQCFG. ------------ REQCFG server allows to send back the current configuration of the software. The message sent to REQCFG has a well defined syntax. The text of the message is not used. The message should be of the private type and addressed to the BBS which we want to ask. SP REQCFG @ bbs-destination The title of the message contains the @ sign followed by the return BBS, that is to say yours. The return message will be addressed to the originator of the request to the return bbs. @ bbs-return The text of the message is not necessary, its content will not be taken into account by the service. Example : F6FBB BBS > SP REQCFG @ FD1CDC.FMLR.FRA.EU Title of message : @ F6FBB.FMLR.FRA.EU Text of message : /EX The answer of the remote mailbox will be of the form : SP F6FBB @ F6FBB.FMLR.FRA.EU < F6ABJ ReqCfg V 1.2 (C) F6FBB 1992 - BBS F6FBB Software F6FBB Version 5.15 compiled on Feb 07 1993 Mem Us:14620 Mem Ok:148288 Bid:30000 Ports:4 Ch:12 FBB Ok BIN Ok Available volumes : C: D: E: EMS V4.0 MSG : 29 pages (464 KB) BID : 17 pages (272 KB) HIE : No FWD : 1 pages ( 16 KB) REJ : 1 pages ( 16 KB) OVR : 11 pages (176 KB) SCR : 45 pages (720 KB) WPG : 5 pages ( 80 KB) Total : 109 pages (1744 KB) Languages 1 : ENGLISH 2 : FRANCAIS 3 : ESPAGNOL 4 : ITALIANO 5 : NEDERLAN 6 : DEUTSCH 7 : CATALA FBB 5.15 Feb 06 1993 Page - 106 8 : NORSK 9 : PORTUGUE 10 : DANSK 11 : SVENSK 12 : HRVATSKI 13 : FRANC8 Servers REQDIR : Demande de repertoire REQFIL : Demande de fichier ascii NEWDOC : Ajout de documentation REQCFG : Demande de configuration AUTO7P : Serveur 7plus 7PSERV : Serveur de fichiers 7PLUS SWFMLR : Distribution Infos Reseau WP : Serveur W.P. MULTI : Multi-addresses Port Interface Emulat. Ch Mode Frequency 1 DRSI WA8DED 9 UYWL NODAL 2 ESS/COM. KAM 1 GYW 15M/20M 3 FBBIOS FBBIOS 1 UYM MODEM 4 ESS/COM. KAM 1 GYW HF-PSK /EX FBB 5.15 Feb 06 1993 Page - 107 18 FILE FORMAT : ---------------- The miscellaneous files used for the configuration and the operation of this BBS software have a very accurate syntax. The good behaviour of your software depends upon how these files have been configured. The first file to be configured is INIT.SRV. This file contains the informations on the BBS and about your hardware. The system holds more than 10 text files which can be configured. Do not forget to save the previous content of the file before modification. This will ease the restauration which might be often necessary. Never delete a file, you might loose major data. Never modify a binary file. Some files have a preset number of lines, and adding or deleting lines might generate an error message. This is the case of the configuration files and text files. In most of the configuration files and within the text files, the character # in the FIRST COLUMN means that the line is a comment, and will not be taken into account for the number of lines. Files may stay in different directories, FBB, BIN, SYSTEM, etc... The default directory is indicated after the file name inside parentheses. FBB 5.15 Feb 06 1993 Page - 108 18.1 PORT.SYS (SYSTEM). ----------------------- This file is found in the directory called SYSTEM (if you used my default directory-names). Remember that a line starting with # is a comment-line, and the BBS ignores these lines. The BBS has built-in drivers for a maximum of 8 serial-ports, named COM1-COM8. It can also use a special port-multiplexer so that you can have up to 4 TNCs per COM-port. In addition to the built-in port-drivers, you can use other drivers like COMBIOS, MBBIOS, FBBIOS etc. These drivers must be loaded BEFORE the BBS-program. You can include the drivers in APPEL.BAT for convenience. It is possible to use telephone-modem with the BBS. In that case the number of TNCs include the modem. The FBBIOS- driver must be loaded. Standard PORT.SYS with 1 TNC (COM1) with WA8DED-hostmode, no com-driver, 4 channels, 1 channel for outgoing forward, 1 channel reserved for BBSs with callsign LA1B-1 : # File for programming of channels and TNCs. # # Ports : How many ports (COM1, COM2, Etc...) # TNCs : How many TNCs and modems in use. With multiplexer # there can be up to 4 TNCs per port. # #Ports TNCs 1 1 # # Com : COM-number (1,2,...8) # Interface : # 1 = ESS COM driver (external) # 2 = BPQ-node (version 4.05 and up) # 3 = Telephone-modem with FBBIOS # 4 = DRSI card with driver # 5 = TFPCR/TFPCX interface # # Adress : Adress of port in hexadecimal. Needed for multiplexor. # # Baud : Ports baud rate (up to 56 KBds). Ignored by BPQ. # # Use same number of lines as number of ports. # #Com Interface Adress (Hex) Baud 1 0 3F8 4800 # # TNC : Number on TNC in use. # NbCh : Number of channels I want to use in the TNC. # Maximum available channels depend on firmware. # Com : Number of the COM-port. Com1, Com2 etc. # MultCh : Number of channel if port-multiplexer is used, # otherwise 1. In DRSI use values from 0 to 7, by KAM # use 1 for VHF and 2 for HF. # Paclen : PACLEN on this TNC. # Maxframe: The maximum number of frames the TNC will send at one # time. # NbFwd : Number of channels for OUTGOING forward at same time. # MxBloc : Size of forward-block in kb. # M/P-Fwd : Minute of the hour for start of forward, and period # (how many minutes between each forward-start). # Mode : One of these: # B : BBS-mode. # G : "Guest"-mode. # U : Normal-mode. # Type host-mode, one of these: FBB 5.15 Feb 06 1993 Page - 109 # D : WA8DED # K : KAM hostmode. # P : PK-232 # Q : BPQ v 4.x # Addition: One (or more) of these letters can be used too: # L : Send unproto beacon after each arriving mail. # M : Telephone-modem. # Y : Yapp allowed on this QRG. # W : Gateway allowed TO this QRG. # R : Read-only mode allowed on this port. # Freq. : Text to describe this port (max 9 letters, no # space) # Same number of lines as number of TNCs. # #TNC NbCh Com MultCh Pacl Maxfr NbFwd MxBloc M/P-Fwd Mode Freq 1 4 1 1 230 4 1 10 30/60 UD 433.650 # # Special callsigns and modes for some channels. # #TNC Nbs Callsign-SSID Mode (only with WA8DED host mode) 1 1 LA1B-1 B # # End of file. # In the next examples, all comment-lines are removed, for clarity. Next an example of a file with 4 ports, 13 channels, no com-driver, with a port-multiplexer on COM 1. Port 1 has limited access (guest-user), port 2 and 3 allows YAPP-transfer and port 4 uses a PK-232. #Ports TNCs 1 4 # # #Com Interface Adress (Hex) Baud 1 1 3F8 4800 # # #TNC NbCh Com MultCh Pacl Maxfr NbFwd MxBloc M/P-Fwd Mode Freq 1 4 1 1 230 4 0 1 00/60 GD 433.650 2 4 1 2 230 4 1 5 10/30 UDY 144.675 3 4 1 3 230 3 4 10 20/60 UDYW 433.650 4 1 1 4 80 1 1 5 15/30 BP 15/20m # Next an example of a file with 4 ports, 13 channels, with ESS/COMBIOS. #Ports TNCs 4 4 # # #Com Interface Adress (Hex) Baud 1 1 0 4800 2 1 0 4800 3 1 0 4800 4 1 0 4800 # # #TNC NbCh Com MultCh Pacl Maxfr NbFwd MxBloc M/P-Fwd Mode Freq 1 4 1 1 230 4 0 1 00/60 GD 433.650 FBB 5.15 Feb 06 1993 Page - 110 2 4 2 1 230 4 1 5 10/30 UDY 144.675 3 4 3 1 230 3 4 10 20/60 UDYW 433.650 4 1 4 1 80 1 1 5 15/30 BP 15/20m # Next an example of a file with 1 port with BPQ-node and 4 channels. #Ports TNCs 1 1 # # #Com Interface Adress (Hex) Baud 1 2 0 4800 # # #TNC NbCh Com MultCh Pacl Maxfr NbFwd MxBloc M/P-Fwd Mode Freq 1 4 1 1 230 4 1 1 00/60 UQY 433.650 # Next an example of a file with 1 DRSI-card and 8 channels, max 1 channel on HF. #Ports TNCs 1 2 # # #Com Interface Adress (Hex) Baud 7 4 0 4800 # # #TNC NbCh Com MultCh Pacl Maxfr NbFwd MxBloc M/P-Fwd Mode Freq 1 8 7 0 230 4 1 10 00/60 UDY 433.650 2 1 7 1 80 2 1 10 30/60 GDW HF # FBB 5.15 Feb 06 1993 Page - 111 18.2 CRON.SYS (SYSTEM). ----------------------- This file is in the SYSTEM directory. The BBS looks in this file once every hour. If the hour and date is right, the BBS will execute the commands in this file. DOS-programs are run with X or D command, like X DOTHIS.EXE or D DOTHAT.EXE. When running BAT files, a COMMAND.COM is automaticly first sent. That needs some more memory. With D the screen is saved, and reappears after the program has terminated. With X the program will not write to the scren. # # File CRON.SYS. Here DOS-commands can be executed to fixed # hours, also Gateway, Yapp, Bip and Talk can be turned on or # off. # Format: TALK YES (NO), BIP YES (NO), GATE 1 YES (NO), YAPP 2 # YES (NO). # DOS-program is run like in FORWARD.SYS with D or X command. # # As in FORWARD.SYS, you can use H for hour and D for day. # 0=sunday, 1=monday,.....6=saturday. # Also IF-ENDIF and IF-ELSE-ENDIF is allowed # # Possible formats for time: # IF H 0-9 All hours between 00 and 09. # IF H 0,9 Only at 00 and 09. # IF H 0,9-11 At 00, and all other hours between 09 and 11. # IF D 0-2 Sunday, monday tuesday. # TALK NO BIP NO GATE 1 YES GATE 2 YES YAPP 1 YES YAPP 2 YES IF D 1-5 IF H 15-23 GATE 3 YES YAPP 3 YES ELSE GATE 3 NO YAPP 3 NO ENDIF ELSE IF H 8-23 GATE 3 YES YAPP 3 YES ELSE GATE 3 NO YAPP 3 NO ENDIF ENDIF X DOTHIS ARG1 ARG2 ARG3 D DOTHAT ARG1 ARG2 FBB 5.15 Feb 06 1993 Page - 112 18.3 REJET.SYS (SYSTEM). ------------------------ This file is in SYSTEM-directory. With this file it is possible to reject or hold certain types or sizes of messages. The first letter of each valid line specifies the action : R = Reject : The message will not be received. H = Hold : The message will be received but held untill the sysop reviews. L = Local Hold : Only messages created on this BBS will be held. # File for rejecting messages. They are rejected with N-BID: # # Type, from, @BBS, to, BID, maximum size: # # * and ? can be used as wildcards (as in MS-DOS) # R B TOTO ALL TATA * 0 R B * * VENTE * 0 R B * VENTE * * 0 H * P1RAT * * * 0 L B * * * * 0 FBB 5.15 Feb 06 1993 Page - 113 18.4 PASSWD.SYS (SYSTEM). ------------------------- This file is in SYSTEM directory. The first line in this file is the generic password. That is, this password will be used for all sysops that do NOT have a special password of his own. Be adviced to change this to your own, secret password ! The next line is a special password for one special sysop. In this case LA6CU. The two first numbers correspond to the same "security-numbers" in INIT.SRV (check this). So in this case of LA6CU, I will have the security- number 69 before a successful SYS-command, and 1023 after. In the next line the numbers for LA6IM is 123 and 1023. jkshdfkjasdfuweiuryiusdfashdfabsmfzmxncvbiouweqyriuyweruyasjhf LA6CU 69 1023 jkasdhfiuweyiruyasidkasfuiweriuoasdfkjlahsdfjlha LA6IM 123 1023 uiwyejhaskjdfhasdfiuyaiuowyeruakjsdfhkjahfdlkja Each line in PASSWD.SYS can have a maximum of 255 characters. For the first tests with the BBS-program, you will only need the first line. Write whatever you like in it, and have a copy of it an paper. And let nobody else see that paper (hi). FBB 5.15 Feb 06 1993 Page - 114 18.5 PROTECT.SYS (SYSTEM). -------------------------- This file is in the SYSTEM directory. In this file you can specify some directories in which you do NOT want any sysop to be able to delete any files, without a special syntax. To delete files in protected directories, the command must look like t +FORWARD.SYS In an un-protected directory the command looks like this: DEL FORWARD.SYS. So you can see that you need an extra '+' sign in protected directories. Example of PROTECT.SYS: \ \FBB \TOOLS FBB 5.15 Feb 06 1993 Page - 115 18.6 LANGUE.SYS (SYSTEM). ------------------------- This file is in the SYSTEM-directory. You do not need to change this file for the first startups. First there are 3 numbers. The text in the file explains how to use them. Next there is a list of all available languages. These names must be the same names as used in the .TXT and .HLP files in the directory called LANG. So, there must be an ENGLISH.TXT and ENGLISH.HLP there, if ENGLISH is in LANGUE.SYS file. After some comment-lines, there is a long list of prefixes, and the corresponding number of language that each user will be presented with for his first connect. The user himself, can change language later with OL- command in the BBS. Remember, only the "Number in PC at the time" decides how much memory the languages will use. All languages will be available anyway, but if more then (in this case) 4 are in use at the same time, the BBS will swap the less used language to disk, and load a new one from disk. # # File that decides what language each user will use in the first # connect. He can change language himself later... # All prefixes not listed here, will receive language no 1 (english). # 3 parametres : # Number of languages - Number in PC at the time - Console-language. # 17 4 1 # ENGLISH NORSK NORSK8 FRANCAIS SVENSKA SVENSKA8 DANSK DANSK8 SUOMI PORTUGUE ITALIANO DEUTSCH CATALA ESPAGNOL NEDERLAN RUSSE HRVATSKI # # 1 : English # 2 : Norwegian (7-bits) # 3 : Norwegian 8-bit # 4 : French # 5 : Swedish (7-bits) # 6 : Swedish 8-bit # 7 : Danish # 8 : Danish 8-bit # 9 : Finnish # 10: Portugues # 11: Italian # 12: German # 13: Catalan FBB 5.15 Feb 06 1993 Page - 116 # 14: Spanish # 15: Dutch # 16: Russian # 17: Jugoslavian # CT* 10 CU* 10 C3* 13 DU* 1 D* 12 EI* 1 E* 14 F* 4 etc. etc. FBB 5.15 Feb 06 1993 Page - 117 18.7 FORWARD.SYS File (SYSTEM). ------------------------------- The FORWARD.SYS file defines the setup of the various adjacent BBS's to which we will route the mail. The file is organized in blocks, each block being specific to a BBS. Only the adjacent BBS's should be defined. This file and its includes are compiled at the BBS start-up and after editing with tiny-edit or return from the DOS Shell (AltF9) if one of the files has been modified. If the FORWARD.SYS file or one of its includes has been modified all the active messages are scanned, and new routings will be set according to the updated file(s). The scanning can be stopped with AltF3. (Can be convenient if the modification does not impact the routing.) Every line of the file begins with a letter which defines the function of the line. Any line beginning with a # is regarded as a comment and is ignored. Line types : A (callsign) All blocks must start with a line like this. The callsign is the callsign of the BBS we will forward to. B (callsign) All blocks must include at least one line like this. Personal messages adressed to somebody with adress '@ (callsign)' will be forwarded. C C (callsign1) [V DIGI1 DIGI2 ETC...] The complete line of connection (C calsign V digi1 digi2) must follow the letter C. In most cases, there will be two letters C successively, with a space between them. The letter V, specifying a string of repeaters is optional if PROMs TF4 (or equivalent) are used - see WA8DED.DOC. There may be several lines C, in the case of cascaded connections (use of THENET, as per an example). A line of conditional connection (enclosed between an IF and an ENDIF) allows calls on preset times. Up to 8 lines are allowed, each line can held up to 80 characters. In case of KA-node and X-connect, we can send C X (callsign). When connected to a node, all command after the first C is actually sent to that node. Like here, the X is sent too. D (command) Command to be performed by the DOS (transceiver frequency set, for example). The screen is saved before the command, and restored when done, thus enabling screen access for this command. When running BAT files, a COMMAND.COM is automaticly first sent. That needs some more memory. ELSE Complementary conditional lines to the previous IF. ENDIF End of conditional lines defined by an IF. F (callsign) Callsign which will be automatically routed (except if a routing has been specified) to the BBS which has been previously stated by a B line (must follow a B line). There may be several F lines following a B line. If this line is not preceeded with a B line, then the bulletins will be routed on their destination. FBB 5.15 Feb 06 1993 Page - 118 G (route) Group routing indicator for bulletins (EU for example). This indicator applies only to bulletins. The private messages ar according to the BBS indicator (see line B). There may be several routing indication lines per adjacent BBS. H (route) Route definition using the hierarchical addressing mode. The wildcards (* or ?) must be used to replace the missing part of the address as a function of the destination. IF C1 ... IF C9 Conditional test of the route selection. The value for "n" is a figure, from 1 to 9, depending upon the selection. The first selection is 1, and the maximum is 9. The lines located between the IF Cn and the ENDIF will be taken into account only if the current selection is n. If the connection has not been successful (remote BBS prompt not received), the selection number will be incremented, and the block will be tested again if the port is still the same. If the port is different, the block will be tested during the tests related to the new port. If the connection is successful, the selection number is reset at 1 for the next call, otherwise the selection number is incremented. If all the selections failed, the selection number is reset at 1, the call is given up, and the system manages the next block. IF D xx Conditional test of the days of the week. This line defines a set of lines which will be taken into account if the expression which defines the day(s) following the IF is true. 0 corresponds to Sunday and six to Saturday. The expression 'IF D 0,2,4-6' is true for Sunday, Tuesday, and Thursday to Saturday. There can be several embedded IF's (indentation recommended), they shall never expand outside a block. The ENDIF defines the end of the conditional block. IF H xx Conditional test of the hour (IF). This line defines a set of lines which will be taken into account only if the hour period following the IF is TRUE. The hour period written in the format 0,4,12-23 is true at 0h, 4h, and for the hours from 12h to 23h. There may be several IF conditions embedded (indentation should be used), but never outside of the blocks. IF FREE Conditional test for the availabilite of a port. The test will be true if none of the channels for the port is in use. This test can be a necessity before the autoqsy of a transceiver as for an example. There can be several embedded IF's (indentation is recommended), they shall never expand outside a block. The ENDIF, defines the end of the conditional block. IF MAN Conditional test only true if forward has been asked manually by F4, FR or FW commands. K Channel Forces forwarding to start on the specified channel. If the channel is busy, forwarding will not start. L (command) [value] Parametres programmation for the TNC. The parameters will be assigned to the related channel. The syntax is the one of the TNC hostmode. Only the command B (Paclen = packet size) has been supplied in all cases. B parameter must be used with all TNCs (including KAM) to specify a paclen. The paclen is always managed by the BBS software, as the different host modes are transparent to the paclen. The PACLEN of the KAM should be 0/0 (256) to make the BBS paclen work in all circumstances. FBB 5.15 Feb 06 1993 Page - 119 Those parameters will also be used for "reverse forwarding". N Assigns the standard forward protocol (MBL/RLI) for the specified BBS. O (minutes) Defines a timeout for the specified BBS. Timeout is expressed in minutes. P (port) Selects the port on which the connection is to take place. The port is defined by a letter from A to H for the ports 1 to 8. Q Prevents the reverse forwarding from my BBS to take place. R Specifies that a call should be made to the adjacent BBS even if there is no mail in queue, so as to trigger the reverse forwarding. S Connect Failure Busy It is a set of supplementary test in the case of sequential connections (TheNet network for example). The 3 tests should be defined. The tests "Connect" "Failure" and "Busy" are already defined in the software. Take care to the capital and lowercase letters, the tests take them into account. Ex.: S Conne Echec Occup. The software will interpret "Conne" like Connect, "Echec" like Failure, and "Occup" like Busy. This allows to comply with nodes messages which are not those commonly used by TheNet. Up to 4 S lines (set of tests) can be defined in a forwarding block. T options Definition of the maximum size for a file authorized to be forwarded, type of messages and strategy. This line can be made conditional (between an IF and an ENDIF). T P : means only private T S : means smaller first (instead of older first) T 2 : means only less or equal to 2 KB. It is possible to combine one or more of these option like : T P S 2 : means only private less or equal to 2 KB, smallest first. In all cases, personnal mail is forwarded first, and then bulletins. U ROUTE1 ROUTE2 ... (up to eight routes) Give the priority when forwarding bulletins. Bulletins @ROUTE1 will be forwarded first, then bulletins @ROUTE2, then other bulletins. It may be up to eight specified routings. Private mail (including P, T and A messages) are always forwarded first. V (text) Text sent on connection of the called BBS. (Mandatory on some TCPIP BBS to declare the protocol in use). Allows sending callsign and password when connecting to a phone BBS. X (command) Command to be executed by DOS (Selection of a frequency, as for an example). The screen is not saved before the command, thus, the latter should not access the screen. This command is identical to the D command, but it is transparent and faster. When running BAT files, a COMMAND.COM is automaticly first sent. That needs some more memory. FBB 5.15 Feb 06 1993 Page - 120 Y Automatic time update of PMS having the clock ability. (if SID looks like [PMS-3.0-C$]). PMS is set with the local time. Z route NTS routing indicator for NTS messages. This routing indicator applies only to messages of "T" type. Wildcards can be used to define masks. There may be several routing indication lines per adjacent BBS. ------ (string of dashes) Defines the end of the block for the adjacent BBS. The block begins with an A line. ! Line Defines an exception. Will be used with lines of types B, F, G, H. The exception should always be set before the true condition statement. An exception is always from the same type statement (you cannot have a !F exception to a B line). Ex: ! B F6FBB Except for F6FBB BBS B F* Forward to all the BBS which begin with an F The number of the exceptions is not limited. < File Include the file specified. The name of the file should be in the directory SYSTEM or in one of its subdirectories. # Comment line. Definition of the forward file : A forward file is made of a main file including a set of blocks, each block corresponds to an adjacent BBS, that is to say that can be connected. Definition of the minimum block : A block will be an included file in the FORWARD.SYS file. It is always made with a first line beginning with an A, defining the name of the adjacent BBS, and of a last line made of a string of dashes. Inside this block, there will be at least one P line (port used) a C line (connection request), and a B line (destination BBS). An F line with the SYSOP callsign may follow the B, enabling the automatic routing for his mail. A FC1CDC P A Port A C C FC1CDC-1 F6FBB-5 connection line B FC1CDC BBS desserved by FC1CDC F FC1CDC callsign autimatically forwarded to FC1CDC -------- This type of block is well suited for PMS of BBS which do not support automatic mail forwarding. Example of a more complex block : A FC1HAQ # G EU FC1HAQ will receive G FRA the bulletins for those FBB 5.15 Feb 06 1993 Page - 121 G WW various routings. G AMSAT F AMSAT bulletins to AMSAT are also marked. # H *.NA All the H. routes which end H *.SA with .NA, .SA H *.EU and .EU # O 5 5 minutes timeout. # IF C1 1st choice parameters P C L B 250 Paclen is 250 bytes L N 4 Retry 4 C C FC1HAQ-1 F6FBB-7 019301 ENDIF IF C2 2nd choice parameters P C IF 8-17 from 8h to 17h T 5 files of 5 kb Max. ENDIF L B 250 Paclen is 250 bytes L N 4 Maxframe is 4 C C FC1HAQ-1 F6FBB-7 019002 ENDIF IF C3 3rd choice parameters P A port A is used T P private mail only C C F6FBB-2 Connection of the 1st Thenet. C C FF6KUB-2 Connection of the 2nd Thenet. C C FC1HAQ-1 Final connection. ENDIF # B FC1HAQ Definition of the various F FC1HAQ BBS routed by FC1HAQ and F F6CQU of its SYSOPs and /or direct # specified users. B F6ABJ F F6ABJ Other BBS and miscellaneous # callsigns forwarded by FC1HAQ. B F5LO F F5LO # B G* other BBSs. B ON* B D* B HB* # ------ End of the FC1HAQ block It is now possible to use include-files with FBB. In this way we can have a very small FORWARD.SYS, with only the callsign of the BBSs to forward to, and then we have another directory with all the forward-blocks. One file for each BBS, for example. Just transfer one whole block (starting with A (callsign) and ending with ------) to file, and pu the filename in FORWARD.SYS with a '<' in front of it, like this: Example of FORWARD.SYS file with include-files. FBB 5.15 Feb 06 1993 Page - 122 # # FORWARD FILE F6FBB # ------------------------ # # UHF # < FWD\FE6BIG < FWD\FC1GJC < FWD\FF6KNI < FWD\FC1HAQ < FWD\F1EBV < FWD\FD1JGK < FWD\EA3BKZ # # PMS # < FWD\FD1CDC < FWD\FD1MEU < FWD\FD1OAC < FWD\F8PD < FWD\F6HED < FWD\FE1JYH < FWD\F1LMI # # HF # < FWD\LA1B < FWD\LA6CU < FWD\SV1IW < FWD\4X1RU < FWD\RS3A < FWD\I7XGL < FWD\EA8AML < FWD\EA8RT # # VHF # < FWD\F6CDD # # FILES # < FWD\AMSAT < FWD\MAIL # # Back to the park frequency. # P B IF 0-3,21-23 X ICOM A2E8 M14 ELSE X ICOM A2E8 M4 ENDIF Example of an include file FWD\EA8RT ------------------------------------ A EA8RT # G EU G ALL FBB 5.15 Feb 06 1993 Page - 123 G AMSAT G WW G EA G EANET G LATNET # P B # O 2 # L T 20 L B 80 L O 2 L P 100 L F 2 L @T2 20 # # IF 7-22 X ICOM A2E8 M6 C C EA8RT-2 ENDIF # B EA8RT F EA8RT F E?1* F E?4* F E?7* F E?8* # B E?1* # B E?4* # B E?7* # B E?8* # ---- Automatic forward to a file. ---------------------------- It is interesting to allow automatic routing of messages or bulletins to a file, for further processing, archive, or communication between BBSs which co-exist in the same computer. The communication can be made through files. The incoming mail file (see INIT.SRV) is tested once every minute; in case of existence, the mail it contains is entered into the BBS. On the other hand, a file can be defined in a forward block and updated once every 15 minutes. This file is defined in a block of forward identical to the forward between BBSs, the port being @ and the connection line given the name of the file created or updated. The name of the BBS (possibly dummy) used will be declared in BBS.SYS, of course. Example of a forward to a file (forward to the file B:MAIL.FBB of my own private mail) : A MAIL P @ C B:\MAIL.FBB FBB 5.15 Feb 06 1993 Page - 124 B F6FBB F F6FBB ------ End of file DOS command specific to a port. ------------------------------------------- Each DOS command (D or X line) defined out of a forward block will be run only if the forwarding port matches with the last port selection. Example : You use the autoqsy capabilities of your HF tranceiver with a special programm named "ICOM". To be sure to return to your standby frequency, you must set your frequency at the end of the forward file, only if the forward applies to the HF port. You only have to select the port before running the DOS command. B xxxxxx # ------- End of last forward block # P D Select HF port (port D) X ICOM A3E8 M12 Send the DOS command ICOM with its # arguments if the file is scanned for # D port. IF and ENDIF are allowed. FBB 5.15 Feb 06 1993 Page - 125 18.8 Specific language files x.TXT, x.HLP, x.ENT, x.INF (SYSTEM\LANG). ---------------------------------------------------------------------- These various files have the names of the languages followed by the suffixes TXT, HLP, ENT, or INF. They may content variables and are searched for in the directory holding the files (SYSTEM\LANG). TXT : file which contains text used during the operation of the software. Each line is associated to a text used by the software. The number of lines must not be altered, except for the comment lines which are not taken into account (lines beginning with a # in the first column). HLP : Help file called by the ? or H command. The help is reffered to a word following the command, (ex: ? HELP). Each help block should begin with a line of a special format: @@ 14 S The two @@ characters, without space, in the first column mark the beginning of a help block. They are followed by an identification number for the type of handling (see appendix 3), and of the word which identifies the help, in capital. A block ends at the line beginning with @@ (next block identifier). ENT : Optional file displayed on the user connection, between the header and the list of commands. The FRANCAIS.ENT file will be displayed if it exists and if the caller uses french language. INF : File displayed when the command "I" is used. If the file does not exist, the display of the ! command will take place. FBB 5.15 Feb 06 1993 Page - 126 18.9 FBBLOG.nn File (SYSTEM\LOG). --------------------------------- Most of the executed commands are recorded in the file FBBLOG.nn - n is the number of the week. This yields a weekly archive which is not of a too big size. This file will be updated if the line "Complete Log" of the file INIT.SRV is "OK". It is an ASCII file which is automatically created, and does not request any special care. This single file keeps the activity record for all ports together. All the lines begin with a string of figures, corresponding to the month, day, hour, minute and second of the trace, followed by the channel number, then the executed command. A stats analysis software, LOGSTAT.EXE allows the processing of the log file (see 13.xxx). FBBLOG file sample : 043004460500SI *** BBS Initialize 043004483200SA *** BBS Online 043004483305CB FC1NOU-0 VIA F6FNL-5 043004483905XD 043004484705CB FC1NOU-0 VIA F6FNL-5 043004500905MR 64072 043004511405XB 043005003201CA F1EBV-14 043005012816CC F1EBV-1 VIA FE6BEX-8 {FC1BPS-7,F1EBV-7,FF6KQK-2} 043005020701MW 64081P F:FC1GQL T:FE1JNY@F6DEG [281] S:F6CQP 043005022816MN B:19226_FF6KNL V:F1EBV 043005424401M> 62893 V:F1EBV [2881] 043005463616MN B:4759_EA6RCM V:F1EBV 043005463616MF 62896 V:F1EBV [393] 043005470813CC FC1HAQ-1 VIA F6FBB-7,019101 043005481701M> 62897 V:F1EBV [872] 043005485816MF 62897 V:F1EBV [872] 043005510701M> 62898 V:F1EBV [815] 043005514516MF 62898 V:F1EBV [815] 043005522901M> 62901 V:F1EBV [398] 043005530516MN B:26051_FC1HAQ V:F1EBV 043005530616MF 62901 V:F1EBV [398] 043005533313MW 64084B F:DF9WM T:ALL@EU [1161] S:Address Needed 043005572701M> 62931 V:F1EBV [2728] 043005580113XD 043005584516MF 62931 V:F1EBV [2728] 043006003012CB F6CDD-1 043006211401XT 043006303216CC FC1HAQ-1 VIA F6FBB-8,019101 043006323016MF 64081 V:FC1HAQ [281] 043006340716MF 64082 V:FC1HAQ [830] 043006354116M< 64086B F:DK3GI T:DXNEWS@EU [953] S:BY4AA in RTTY 043006443216M< 64089B F:OZ2FAR T:ALL@WW [1895] S:re qrt 043006452112CB F6CDD-1 043006465112MF 64086 V:F6CDD [953] 043006465212MF 64087 V:F6CDD [2632] 043006465312MF 64088 V:F6CDD [1626] 043006465312MF 64089 V:F6CDD [1895] 043006465412XB 043006474016M< 64090B F:VS6XQF T:ALL@WW [1748] S:CRY FOR TR-9500 FBB 5.15 Feb 06 1993 Page - 127 043006490316M< 64091B F:DJ0AW T:ALL@WW [972] S:mfj-1278 043006534816M< 64092B F:DB2OS T:KEPLER@WW [3684] S:Elements 118. 043007002612CB F6CDD-1 043007005516M< 64095B F:VK5CGB T:ALL@WW [1166] S:RNARS PACKET 043007022116M< 64096B F:DF7MX T:COMMOD@EU [913] S:SUPPORT 043007034316M< 64097B F:I1ZEU T:ALL@EU [1096] S:ID1V 043007065416SQ *** BBS Quit FBB 5.15 Feb 06 1993 Page - 128 18.10 DIRMES.SYS (SYSTEM). -------------------------- This binary file holds the informations on all active messages. This file is very important and must not be edited or changed otherwise the list of the messages could be lost. This file can only be opened for reading. It is organized with records, each record containing information on a message. The first record of the file only contains the number of the last message. Never modify this file while the BBS is running. Structure of one record (C language) : #define NBBBS 80 #define NBMASK NBBBS/8 typedef struct { char type ; /* 1 Type of message (A,B,P,T) */ char status ; /* 1 Status of message ($,A,F,K,N,Y) */ long numero ; /* 4 Number of the message */ long taille ; /* 4 Size of message in characters */ long date ; /* 4 Date of message */ char bbsf[7] ; /* 7 Adjacent BBS giving the message */ char bbsv[41] ; /* 41 Route */ char exped[7] ; /* 7 Destination of the message */ char desti[7] ; /* 7 To field */ char bid[13] ; /* 13 BID or MID */ char titre[61] ; /* 61 Title of message */ char free[16] ; /* 16 Reserved bytes */ long datesd ; /* 4 Date of the message creation */ long datech ; /* 4 Date of last status change */ char fbbs[NBMASK] ; /* 10 Mask of BBSes to forward to */ char forw[NBMASK] ; /* 10 Mask of BBSes already forwarded */ } bullist ; /* 194 bytes = length of one record */ A null type of message (00 hex) invalidates the record. Dates are given as the number of seconds since january 1st, 1970 00:00. Masks are bit fields, number of bit corresponds to the number of the BBS in the BBS.SYS file. In C language, all strings are ended with a NULL (00 hex) character. FBB 5.15 Feb 06 1993 Page - 129 18.11 STATIS.DAT (SYSTEM). -------------------------- This binary file holds the informations on all connections. This file is very important and must not be edited or changed otherwise the list of the connections could be lost. This file can only be opened for reading. It is organized with records, each record containing information on a connection. Never modify this file while the BBS is running. Structure of one record (C language) : typedef struct { char indcnx[7] ; /* 7 Callsign */ char port ; /* 1 (Port x 32) + channel */ long datcnx ; /* 4 Date of the connection */ int tpscnx ; /* 2 duration of the connection */ } statis ; /* 14 bytes = length of one record */ Date is given as the number of seconds since january 1st, 1970 00:00. In C language, all strings are ended with a NULL (00 hex) character. FBB 5.15 Feb 06 1993 Page - 130 18.12 WFBID.SYS (SYSTEM). ------------------------- This binary file holds the last received BIDs. The number of records of this file is defined in the INIT.SRV file. This file is very important and must not be edited or changed otherwise the list of the messages could be lost. This file can only be opened for reading. It is organized with records, each record containing information on a BID. This is a circular file and the first record of the file contains the pointer of the last overwritten record in the msg_number field. Never modify this file while the BBS is running. Structure of one record (C language) : typedef struct { char mode ; /* 1 Type of message (A,B,P,T) */ char fbid[13] ; /* 13 BID of the message */ long msg_number ; /* 4 Number of the message */ } bidfwd ; /* 18 bytes = length of one record */ In C language, all strings are ended with a NULL (00 hex) character. FBB 5.15 Feb 06 1993 Page - 131 18.13 INF.SYS file (SYSTEM). ---------------------------- This binary file holds the informations on all users of the BBS. This file is very important and must not be edited or changed otherwise the list of the users could be lost. This file can only be opened for reading. It is organized with records, each record containing information on a user. Never modify this file while the BBS is running. Structure of one record (C language) : #define uchar unsigned char typedef struct { /* Callsign structure used in info */ char callsign[7] ; char ssid ; } indicat ; typedef struct { indicat indic ; /* 8 Callsign */ indicat relai[8] ; /* 64 Digis path */ long lastmes ; /* 4 Last L number */ long nbcon ; /* 4 Number of connexions */ long hcon ; /* 4 Last connexion date */ long lastyap ; /* 4 Last YN date */ unsigned flags ; /* 2 Flags */ unsigned on_base ; /* 2 ON Base number */ uchar nbl ; /* 1 Lines paging */ uchar lang ; /* 1 Language */ char free[27] ; /* 27 Reserved */ char nom[18] ; /* 18 1st Name */ char prenom[13]; /* 13 Christian name */ char adres[61] ; /* 61 Address */ char ville[31] ; /* 31 City */ char teld[13] ; /* 13 home phone */ char telp[13] ; /* 13 job phone */ char home[41] ; /* 41 home BBS */ char qra[7] ; /* 7 Qth Locator */ char priv[13] ; /* 13 PRIV directory */ char filtre[7] ; /* 7 LC choice filter */ char pass[13] ; /* 13 Password */ char zip[9] ; /* 9 Zipcode */ } info ; /* 360 bytes = lenght of one record */ Dates are given as the number of seconds since january 1st, 1970 00:00. In C language, all strings are ended with a NULL (00 hex) character. FBB 5.15 Feb 06 1993 Page - 132 18.14 HROUTE.SYS (SYSTEM). -------------------------- This ascii file holds the information on BBS hierarchical routing. Each time a "R:" header is received in a message or bulletin, the hierarchical routing found in the line is added to a list and updates the HROUTE.SYS file. This is an example of HROUTE.SYS : # SM2LZK.GSTAD.BD.SWE.EU # VE3JJV.NWON.CAN.NA # W2NRE.NY.USA # W6MCV.AZ.USA.NA # W6MCV.AZ.USA.NOAM V 3B8FP.MRU.AF P 4X1RU.ISR.MDLE V 4Z4SV.ISR.MDLE V 7J1AAA.10.JNET1.JPN.AS V 7K1DJL.11.JNET1.JPN.AS V 7Z1AB.SAU.MDLE The character in first column can be : # The line is ignored (comment, or line disabled). P The line is persistent and will not change. V The line is volatile and will change if a new route exists for this BBS. When a new route is found for a BBS, the old one is commented by changing the V character with a #, and a new line will be appended at the end of the file. HROUTE.SYS is automaticly updated by the software and does not need any maintenance. This file can be sorted and comments deleted with a sequence like : COPY HROUTE.SYS TEMP.$$$ TYPE TEMP.$$$ | SORT | FIND /v "# " > HROUTE.SYS DEL TEMP.$$$ This sequence can be included in the APPEL.BAT loop. This file will be no longer used and updated if the White Pages service is validated, as the WP service helds the same informations. FBB 5.15 Feb 06 1993 Page - 133 18.15 YAPLBL.SYS file (SYSTEM). ------------------------------- This binary file holds the descriptions of the FbbDos files. It is organized with records, each record containing the filename in upcase characters (with the full path including disk name) and the description of this file. Structure of one record (C language) : typedef struct { char filename[40]; /* Complete path of the filename */ char label[80] ; /* Description of the file */ long creation ; /* Date of creation of the file */ long unused ; /* Not used should be 0 */ } YapLbl; Date is given as the number of seconds since january 1st, 1970 00:00. In C language, all strings are ended with a NULL (00 hex) character. FBB 5.15 Feb 06 1993 Page - 134 18.16 MEMO.SYS (SYSTEM). ------------------------ This ascii file will substitute a text when typing CtrL F1 to Ctrl F10. This text can hold variables and is limited to 255 characters. It can include $W variable (CR) and then will be formatted as more than one line. This file will have 10 lines, the first line corresponding to Ctrl F1, and the last one to Ctrl F10. If a line is not used, it must have a dot in first column. Example of MEMO.SYS file : $W$O BBS (FBB$E) in $c ($?).$W . . . . . . . $W Vy 73. Jean-Paul, F6FBB @ F6FBB.FMLR.FRA.EU$W$W/EX$W $W 73 Qro. Jean-Paul, F6FBB@F6FBB.FMLR.FRA.EU$W$W/EX$W FBB 5.15 Feb 06 1993 Page - 135 18.17 SATEL.DAT file (SAT). --------------------------- This binary file holds the informations on the satellite data base of the BBS. This file is very important and must not be edited or changed otherwise the list of the satellites could be lost. This file can only be opened for reading. It is organized with records, each record containing information on a satellite. Never modify this file while the BBS is running. Structure of one record (C language) : typedef struct { char sat_name[18]; /* 18 Name of the satellite */ int year ; /* 2 Year of reference */ double day ; /* 8 Day of reference */ int month ; /* 2 Month of reference */ int hour ; /* 2 Hour of reference */ int minute ; /* 2 Minute of reference */ int second ; /* 2 Second of reference */ double inclination ; /* 8 Inclination */ double raan ; /* 8 R.A.A.N. */ double excentricity; /* 8 Excentricity */ double a_perigee ; /* 8 Argument of perigee */ double mean_anomaly; /* 8 Mean anomaly */ double a ; /* 8 must be 0.0 */ double mean_motion ; /* 8 mean motion */ double dec_rate ; /* 8 Decay rate */ long revolution ; /* 4 Epoch revolution */ double frequency ; /* 8 Frequency for doppler computing */ double v ; /* 8 must be 0.0 */ int step ; /* 2 Step of processing (minutes) */ long last_upd ; /* 4 Date of last update */ long catalog ; /* 4 NASA Catalog Number */ int free[4] ; /* 8 Unused */ } satel ; /* 138 bytes : lenght of one record */ In C language, all strings are ended with a NULL (00 hex) character. FBB 5.15 Feb 06 1993 Page - 136 18.18 nnnnn.SAT (SAT) (Satellite characteristics). -------------------------------------------------- The nnnnn.SAT files (where nnnnn is the NASA catalog numbe satellite) will be displayed when the command C will be typed from the satellite menu. They are text files and are located in the SAT subdirectory. FBB 5.15 Feb 06 1993 Page - 137 18.19 WP.SYS file format. ------------------------- The WP.SYS file is composed of records. Each record is 194 bytes long. typedef struct { char callsign[7] ; // Callsign of the record char name[13] ; // Name of the user char free ; // Unused char changed ; // Flag (U, G, I) of modification unsigned seen ; // Number of updates long activ_date ; // Date of active part long temp_date ; // Date of temp part char activ_homebbs[41]; // Home BBS in active part char temp_homebbs[41] ; // Home BBS in temp part char activ_zip[9] ; // Zip code in active part char temp_zip[9] ; // Zip code in temp part char activ_qth[31] ; // Qth in active part char temp_qth[31] ; // Qth in temp part } Wps; In C language, all strings are ended with a NULL (00 hex) character. This file should NOT be modified while the BBS software is running ! FBB 5.15 Feb 06 1993 Page - 138 18.20 MESS.WP file format. -------------------------- The MESS.WP file is an ascii file composed of standard WP update lines. It has no size limit and will be sent as messages to the different routes defined for WP updates in INIT.SRV. The outgoing messages will be truncated to 5Kb sections if required. This file is read at the end of the BBS start-up. FBB 5.15 Feb 06 1993 Page - 139 APPENDIX -1- Commands of the line editor EDIT (FBBDOS) ------------------------------------------------------ The FBBDOS offers a small line editor allowing the process of ASCII files. It can help the distant SysOp maintening the system files of the software. The commands are straightforward, and for a better efficiency, they can be chained on a single line. List of the commands: ? : Gives the list of the editor's commands. A : Adds one line after the current line. The text of the line follows the command, and must be terminated with the character /. The character / can be imcluded into the character string provided it is preceded by a character \. To include a \ character into the string, this character must be sent twice (\\). The line pointer is on the inserted line. B : places the line pointer at the beginning of the file. E : places the line pointer at the end of the file. F : Search for the first occurence of the character string as specified after the command, starting from the current line. The character string should be terminated by the character /. The character / can be inserted into a string under the condition that a \ character is leading. The \ character must be sent twice if it is to be considered as a valid character. The line pointer stands on the line where the string has been found. I : Inserts a line ahead of the current line. The text of the line follows the command and must be terminated by the character /. The character / can be included into the string provided it is preceded by a character \. The character \ must be sent twice if it is to be considered as a valid character. The line pointer stands on the inserted line. K : Suppresses the number of lines specified before the command, starting from the current line. If the number is not stated, the value 1 is taken as a default. L : moves the pointer of the number of lines specified before the command. This number can be positive or negative. N : Enables or disables the numbering of the lines. P : Displays the number of lines specified before the command, starting at the current line. R : Search for the first occurrence of the character string specified after the command, and replace it by the second character string. The character strings must be terminated by a character /. The / character can be included provided it is preceded by a \ character. The \ character must be sent twice if it is to be taken into account as a valid character. The line pointer stays on the modified line. S : Saves the modified file. Q : Exits the editor. Take care, the file is not automatically saved. Think about doing it before you quit. Examples : EDIT>B5L10P FBB 5.15 Feb 06 1993 Page - 140 places the pointer at the beginning of the file, advances 5 lines, displays 10 lines. EDIT>B4L6K-2L10P Places the pointer at the beginning of the file, advances 4 lines, deletes 6 lines, steps back 2 lines and displays 10 lines. EDIT>BFBonjour/K-2L5P Sets the pointer at the beginning of the file, searches for "Bonjour", suppresses the line (containing "Bonjour"), steps back 2 lines, and displays 5 lines. EDIT>RBonjour/Au revoir/-2L5P Searches for "Bonjour", replaces by "Au revoir", steps back 2 lines and displays 5 lines. EDIT>BFBonjour/IC'est une new line with a \/inside/-1L3P Sets the pointer at the beginning of the file, searches for "Bonjour", inserts a new line, steps back 1 line, and displays 3 lines. This lines includes a character /. A leading \ indicates that it is to be conside red as a valid character and not as a delimiter. EDIT>SQ Saves, and quits the editor. FBB 5.15 Feb 06 1993 Page - 141 APPENDIX -2- Commands corresponding to the PK232 host-mode (as per F6AIW) ------------------------------------------------------------------------- 8B 8BITCONV AU AAB AB ABAUD AG ACHG AA ACRDISP AK ACRPACK AT ACRRTTY AE ADDRESS AD ADELAY AI ALFDISP AP ALFPACK AR ALFRTTY AL ALIST AM AMTOR AC ARQ AO ARQTMO AS ASCII AY ASPECT AW AWLEN AV AX25L2V2 AX AXDELAY AH AXHANG BA BAUDOT BE BEACON BI BITINV BK BKONDEL BT BTEXT CL CANLINE CP CANPAC CX CASEDISP CU CBELL CC CCITT CF CFROM CB CHCALL CD CHDOUBLE CH CHSWITCH CK CHECK CQ CMDTIME CM CMSG CI CODE CN COMMAND CE CONMODE CO CONNECT CY CONPERM CG CONSTAMP CI CPACTIME CR CRADD CT CTEXT CW CWID DS DAYSTAMP DA DAYTIME DC DCDCONN DL DELETE DF DFROM DI DISCONNE DW DWAIT EA EAS EC ECHO ES ESCAPE FA FAX FN FAXNEG FE FEC FL FLOW FR FRACK FS FSPEED FU FULLDUP GR GRAPHICS HB HBAUD HD HEADERLN HI HID HO HOST HP HPOLL ID ID IL ILFPACK IO IO JU JUSTIFY KI KISS LR LEFTRITE LO LOCK MX MAXFRAME MB MBX MC MCON MD MDIGI MM MEMORY MI MFILTER MF MFROM MH MHEARD MN MONITOR MO MORSE MP MSPEED MR MRPT MS MSTAMP MT MTO MA MYALIAS ML MYCALL MG MYSELCAL MK MYALTCAL NE NEWMODE NO NOMODE NR NUCR NF NULF NU NULLS OK OK OP OPMODE PA PACKET PL PACLEN PT PACTIME PR PARITY PS PASS PX PASSALL PE PERSIST PP PPERSIST PC PRCON PF PRFAX PO PROUT PY PRTYPE RW RAWHDLC RB RBAUD RC RCVE RE RECEIVE RX RXREV RD REDISPLA RL RELINK RS RESET RP RESPTIME RT RESTART RY RETRY RF RFEC SE SELFEC SP SENDPAC SI SIGNAL SL SLOTTIME SQ SQUELCH SR SRXALL ST START SO STOP TB TBAUD TC TCLEAR TM TIME TR TRACE TW TRFLOW TI TRIES TD TXDELAY TF TXFLOW TX TXREV UN UNPROTO UR USERS US USOS VH VHF WI WIDESHFT WO WORDOUT WR WRU XW XFLOW XM XMIT XO XMITOK XF XOFF XN XON FBB 5.15 Feb 06 1993 Page - 142 APPENDIX -3- Process number and on-line help identification. ------------------------------------------------------------ The various processing functions contained in the software are identified by three numbers displayed in the status banner. The first of those three numbers is the main process system (BBS, FBBDOS, Satellite Computation, etc...), the second number is the process function (in the BBS, list, message sending, etc..) and the third number is a sub-function (record of the message title, message, etc..) A complete description of these numbers would be useless and time consuming. They are mainly used for debugging purpose. The first number is also used to identify the help block out of the x.HLP file. Upon receipt of the "?" or the "H", the software searches the x.HLP file for a line of corresponding to the language in use, and of the format @@ number word in which "number" stands for the current processing level, and "word" stands for the word following the command "?" or "H". Example : you are inside FBBDOS, and you type in the command "? EDIT", the help block searched for must begin with the line: @@ 9 EDIT It may happen that a block matches several search keywords. It is enough to specify the various words separated by the character "|" (vertical bar), WITH NO SPACE. @@ 9 EDIT|EDITEUR List of the processing levels : 0 Connection. 2 Qra-Locator. 3 Statistics. 4 Informations. 5 Nomenclature. 6 Satellite Orbital Computation. 9 FbbDos. 11 Telefone Modem 14 BBS. 15 Forward. 16 GatewaySysop page. 17 YAPP. 18 Conference. FBB 5.15 Feb 06 1993 Page - 143 APPENDIX -4- Recording a message. --------------------------------- A message can be left by a user or within a forwarding connection. The recording mechanism is always the same. The recording command is always like : Sx desti @ bbs < exped $ ident + filename Only recipient field is mandatory, all other fields are optional. Appending a filename is a possibility reserved to the sysop. The name must be complete, including logic unit and complete path (C:\FBB\SYSTEM\TEST.TXT). When receiving the command line, a first test checks if a route exists when a route has been specified, or if the message must be automatically routed when no route was specified. The title of the message is then asked to the user. If the title is a missing, the message is canceled and the user returns to the main menu. The text of the message is then asked to the user. The software checks possible preamble lines. These lines give informations on the previous BBS having routed this message. They all begin by R: on first column. The BBS callsign is given behind the @ character within the preamble line. All adjacent BBS mentioned in this preamble will be included in the "already forwarded" list, and will not be concerned by this message. This list specific to each message can be displayed with the $ or FN command followed by the message number. When receiving a /EX in first column, or a Ctrl Z, a message number is then assigned, The BID (or MID if private) and the list of adjacent BBS concerned by this message are created. All these informations are sent to the user when acknoledging the message. In case of disconnection before the /EX or Ctrl Z, the whole message will be lost, and the texts already stored are deleted. All informations about the message (sender, recipient, route, MID, title, etc...) are stored in the DIRMES.SYS file. The text of the message is stored in a sub-directory of the MAIL directory. The sub-directory is MAILn where n is the last digit of the message number. The name of the file corresponds to the message number 123 is M_000123.MES, the number is 6 digits wide, in this case it is in the sub-directory MAIL3. The message number uses a long integer (32 bits), the number boundary is very far (more than 4 billions !). FBB 5.15 Feb 06 1993 Page - 144 APPENDIX -5- Tricks and tips. ----------------------------- This rubric is yours, more than mine. I'll try to insert there all tricks you will tell me. A/ Using DesqView (c). ------------------------ There is no particular problem when using DesqView. The minimum window size is 500 KB. You MUST use communication drivers, like ESS, COMBIOS or MBBIOS, as the software does not dispose of the whole process time. B/ Communication errors displaying. ----------------------------------- An error counter can be displayed just right of the date, on the first line of the screen. If you are using TNC2 with WA8DED software, these errors can be minor, but with PK232, error recovery is more difficult, and the system may reboot. With a correct operation of your system, this counter will not appear, or exceptionnaly. If errors are displayed, they can result from : - Using DOS 4.0 or 5.0 : The keyboard driver of these versions is very slow. You must use the ESS driver for RS232 (or COMBIOS). - A too hight baudrate, or RS232 defective cables. The baudrate can be selected down to 4800 Bds. It is not a good idea to go down 4800 Bds, as the performance of the software should be lower. - Change the LM324 fitting out some TNC RS232 line drivers by a TL074 or TL084. - HF detection in the TNC. Errors and resynchronizations will appear when the transmitter is running. There is no real cure, you must investigate. You can also use communication drivers like ESS, COMBIOS or MBBIOS if you are not still using them. C/ Repetition of the last message number. ----------------------------------------- The last message number displayed, read, killed, etc... can be utilised again with the # (pound) character. This short-cut allows as for an example to read a message after a list or to suppress it just after its reading. Example : F6FBB BBS > R 12351 The message is displayed ... F6FBB BBS > K # Message #12351 killed. F6FBB BBS > FBB 5.15 Feb 06 1993 Page - 145 APPENDIX -6- FBB Forward Protocole. ----------------------------------- FBB software includes two forward protocoles. The first one is standard with MBL/RLI protocole. The second one was developped to allow efficiency, particularly on long links where propagation time of data are long. The exchange of commands is reduced to a minimum, and not acknoledged to get time. The data transfer direction is changed every block of data, a block of data holding up to five messages. This uses the "pipeline" effect of long links (Nodes and digipeaters), and gain some time over short links (HF...). FBB protocole is very simple in its principle. It is based on MID/BID usage. The identification is made by the F letter in the SID (system type identifier contained in square brackets). All command lines must start in first collumn with the 'F' character. All command lines are ended by a return (CR) character. Suppose I call another BBS to forward some mail. When I connect another BBS using FBB protocole, I will receive the SID followed by a text and the prompt (">"). If the SID contains the F flag, I will send immediately my SID and the first proposal. Proposals looks like : FB P F6FBB FC1GHV FC1MVP 24657_F6FBB 1345 F> HH FB : Identifies the type of the command (proposal) P : Type of message (P = Private, B = Bulletin). F6FBB : Sender (from field). FC1GHV : BBS of recipient (@field). FC1MVP : Recipient (to field). 24657_F6FBB : BID ou MID. 1345 : Size of message in bytes. F> : End of proposal. HH is optional. It is the checksum of the whole proposal in hexadecimal. ALL the fields are necessary. This kind of command must hold seven fields. If a field is missing upon receiving, an error message will be send immediately followed by a disconnection. A proposal can handle up to five FB command lines. If the total size of messages seems to be too important, the proposal can handle less lines. In FBB software, a parameter is defined in INIT.SRV file to tell the maximum size of the message block. It is set by default to 10KB. Exemple of proposal : FB P F6FBB FC1GHV.FFPC.FRA.EU FC1MVP 24657_F6FBB 1345 FB P FC1CDC F6ABJ F6AXV 24643_F6FBB 5346 FB B F6FBB FRA FBB 22_456_F6FBB 8548 F> HH This proposal is limited to three FB lines, as the amount of messages overran the 10KB limit. When receiving the proposal, the other BBS will reject, accept or defer the message. This command is made by a FS line : FS -+= This means : FBB 5.15 Feb 06 1993 Page - 146 - I don't want the first message (-). - I need the second message (+). - I defer the third message, as I'm still receiving it. It should interesting to defer a message if you are still receiving it on a other channel, or if you think that the size is to big, or for another reason. The message should be proposed again at the next connection. FS line MUST have as many +,-,= signs as lines in the proposal. When receiving the FS lines, I can send the block of messages. Each message is made with the title on the first line, the text, and a Ctrl Z in the last line. The is no blank line between the messages. Title of 2nd message Text of 2nd message ..... ^Z When the other BBS has received all the asked messages, it acknoledges by sending its proposal, and the system is reversed. If it has no message to send, it only sends a line : FF This line must not to be followed by a F>. If the other hand has no message, it sends a line : FQ and asks for the disconnection. Example : --------- F6FBB FC1GHV ---------------------------------------------------------------- Connects FC1GHV Connected [FBB-5.11-FHM$] Bienvenue a Poitiers, Jean-Paul. > [FBB-5.11-FHM$] (F6FBB has the F flag in the SID) FB P F6FBB FC1GHV.FFPC.FRA.EU FC1MVP 24657_F6FBB 1345 FB P FC1CDC F6ABJ F6AXV 24643_F6FBB 5346 FB B F6FBB FRA FBB 22_456_F6FBB 8548 F> HH FS +-+ (accepts the 1st and the 3rd). Title 1st message Text 1st message ...... ^Z Title 3rd message FBB 5.15 Feb 06 1993 Page - 147 Text 3rd message ...... ^Z FB P FC1GHV F6FBB F6FBB 2734_FC1GHV 234 FB B FC1GHV F6FBB FC1CDC 2745_FC1GHV 3524 F> HH FS -- (Don't need them, and send immediately the proposal). FB P FC1CDC F6ABJ F6AXV 24754_F6FBB 345 F> HH FS + (Accepts the message) Title message Text message ...... ^Z FF (no more message) FB B F6FBB TEST FRA 24654_F6FBB 145 F> HH FS + (Accepts the message) Title message Text message ...... ^Z FF (still no message) FQ (No more message) Disconnection of the link. In this example, FBB protocole is used as the two BBS were identified by the F flag in the SID. If F6FBB had sent the SID [FBB-5.11-MH$] when answering FC1GHV, the protocole should be the standard MBL/RLI. All callsigns are only examples ! FBB 5.15 Feb 06 1993 Page - 148 APPENDIX -7- Extension to the protocole. Compressed forward FBB. ---------------------------------------------------------------- The protocole utilized for the transfer of ascii files compressed is an extension to the existing protocole. The compressed forward is validated by the presence of the letter B in the SID [FBB-5.12-BFHM$]. The transfer of compressed files can only take place under FBB protocole. The presence of the letter B in the SID without the F letter will remain without effect. The only difference as regard to the standard protocol is the submit line. It can specify the type of data contained in the compressed message. FA means that the transfer will be an ascii compressed message. FB means that the message will be a binary compressed file (this last possibility is not yet implemented in the version 5.12). The submission of an ascii message will be in the form : FA P FC1CDC F6ABJ F6AXV 24754_F6FBB 345 The submission of a binary file will be in the form : FB P FC1CDC F6ABJ F6AXV 24754_F6FBB 345 The transfered data are of a specific format. The transfer will be done in binary mode. This last one is derived of the YAPP protocol which is very reliable. All transfer is made of a header, a block of data, an end of message and a checksum. Each transfer is equivalent to the transfer of one message of the standard protocol and shall not be followed by a control Z, the end of file specifier is defined in another way. Format of header for an ascii compressed message (submission FA) : <SOH> 1 byte = 01 hex Length of the header 1 byte = Length from the title, including the two <NUL> characters. Title of the message 1 to 80 bytes <NUL> 1 byte = 00 hex Offset 1 to 6 bytes <NUL> 1 byte = 00 hex Format of header for a binary compressed file (submission FB) : <SOH> 1 byte = 01 hex Length of the header 1 byte = Length from the filename, including the two <NUL> characters. Name of the file 1 to 80 bytes <NUL> 1 byte = 00 hex Offset 1 to 6 bytes <NUL> 1 byte = 00 hex As to follow the french regulation, the title of the message or the file name are transmitted in ascii, not compressed. The offset is also transmitted in ascii and specifies the offset at which the data should be inserted in the file (in case of a fragmented file). In the version 5.12, this parameter is not utilized and is always equal to zero. A data block contains from one to 256 bytes. It begins by two bytes which specify the format. Data block format : <STX> 1 byte = 02 hex Number of data 1 byte = 00 to ff hex. (00 if length = 256 bytes). FBB 5.15 Feb 06 1993 Page - 149 Data bytes 1 to 256 bytes The last data block is followed by the end of file specifier and the checksum. End of file specifier format : <EOT> 1 byte = 04 hex Checksum 1 byte = 00 a ff hex The checksum is equal to the sum of all the data bytes of the transmitted file, modulo 256 (8 bits) and then two's complemented. The checking of the checksum is very simple : The sum of the datas from the file and the checksum received modulo 256 (anded with FF) shall be equal to zero. In case of a checksum error, the message or the file is not taken to account and the system issues a disconnect request after having sent the comment : *** Checksum error FBB 5.15 Feb 06 1993 Page - 150 APPENDIX -8- Format of the ACK messages. ---------------------------------------- The ACK messages on receiving have a simple and compact format. The aim is to have a message as short as possible in order to avoid an unnecessary usage of the network. The title of the message is the title of the original message with a leading "ACK:". Example : ACK:Title of the original message. These ACK messages are true messages strickly speaking. They carry the origin, the destination, the route and the MID but they are of a particular type, the type A (private are of type P, bulletins of type B, etc...). This difference allows the routing of these messages without the lines "R:". This is done again with the aim of avoiding an excessive load by data which are of no use in this case. To keep the compatibility with the existing forwarding protocol, the type of these messages is changed to P (private) if the receiving BBS of the forwarding does not know the type of ACK messages (specified in the SID [FBB- 5.12-ABFHM$] by the letter A). In this case, the ack message will continue on its route as a private message. The ACK messages are of the following form : ACK:Message test. <-- Title of message Msg FD1CDC@F6FBB - 22-dec 17:28z <-- Text of message It tells that the message that you had sent to FD1CDC at F6FBB and whose title is "Message test" has been received in the BBS F6FBB on 22 dec at 12:28 GMT. FBB 5.15 Feb 06 1993 Page - 151 APPENDIX -9- Replacement characters or wildcards. ------------------------------------------------- Most of the search commands or list commands and some configuration files as well, accept replacement characters or wildcards. Character Replaces ----------------------------------------------------------------- @ a letter ? an alphanum character (letter or number) = a printable character # a numeral character or the # character * a string of printable characters. & a dot followed by printable characters. (equiv to .* ) ----------------------------------------------------------------- FBB 5.15 Feb 06 1993 Page - 152 APPENDIX -10- Programming technics for servers. ----------------------------------------------- The servers are exec programs (.COM or .EXE). They are compact and fast. They will work as the function of the messages which are addressed to them. They should be compact because the available memory to run their application is limited (check the information Ok:nnnn in the status window). They should be fast because they are executed in the MsDos environment which is not multi-task. The programming language can be of any kind provided that it could be compiled and that it is able to read parameters which are given appended in the command line. I wrote three servers in TurboC but I have no equivalent in TurboPascal or in TurboBasic, since I usually don't write in these languages. The working principle remains always the same whatever language is utilized. The program is called with the following manner from the MsDos (Example for the REQDIR.COM command) : C> REQDIR.COM TEMP.$$$ TEMP.$$$ is the name of the file in which the message addressed to REQDIR is located. It is necessary to read the name of this file in the command line, as the one can change from one call to another. The file TEMP.$$$ contains the message with the following format : SP REQDIR < F6FBB Title of message Text of message line 1 Text of message line 2 ... Text of message last line. /EX The server should then eventually work as a function of the contents of this message. The server can read and make use of the configuration file of the BBS software (in particular INIT.SRV) to execute its process. If the server generates a return message, it should be APPENDED to the incoming mail file to the BBS. The name of this file can be found in INIT.SRV. Take care : it is necessary to open the incoming mail file in APPEND as to add the answer at the end of the file. If it is not done this way, the messages which could be waiting in this file are destroyed. The incoming mail file is tested each and every minute, except in the case of the usage of a service, where it is tested right after. The format of the messages in the incoming mail file is identical to the format of the file given to the server. Several messages can be written sequentially in the file. There should not be blank lines or separations between the messages. The routing fields (@ field), and the originator (< field) should mandatory be specified. The originator field is the callsign of the BBS which is taken from the INIT.SRV file. FBB 5.15 Feb 06 1993 Page - 153 Example of server REQFIL written in C language. /* * REQFIL.C Server example. * * This server is called with a command line like this : * * REQFIL.COM FILE * * FILE is the filename of the message to be answered. * * * This server answers to a message like this : * * SP REQFIL < FC1EBN * TEST.TXT @ F6ABJ * Text is not necessary * /EX * * by a message like this * * # <- This is a local message * SP FC1EBN @ F6ABJ < F6FBB <- command line * Req File : TEST.TXT <- subject * Contents of the file <- text * etc..... * /EX <- end of text (must be in 1st column) * * Appent to mail in bbs file. * * * The server receives from FBB software 1 argument : * * argv[1] = Name of the file including the message received from * FBB software. * * ============================================ * The server must APPEND its answer to MAIL.IN * file to avoid destroying existing mail. * ============================================ * * As this server opens the INIT.SRV file, it must be in the same * directory. * */ #include <stdio.h> #include <fcntl.h> #include <sys/stat.h> /* Offsets of parameters from INIT.SRV */ #define BBS_CALL 1 #define USER_DIR 8 #define MAIL_IN 14 main(int argc, char **argv) { #define LINE 80 int end = 0; int index = 0; FILE *fptr; FBB 5.15 Feb 06 1993 Page - 154 char buffer[LINE]; char sender[LINE]; char route[LINE]; char file[LINE]; char bbs_call[LINE]; char base_dir[LINE]; char mail_in[LINE]; if (argc != 2) exit(1); /* Check the number of arguments */ /* The first task is to open and then read the message */ fptr = fopen(argv[1], "rt") ; /* Open the received message */ if (fptr == NULL) exit(1); fgets(buffer, LINE, fptr); /* Read the command line */ sscanf(buffer, "%*s %*s %*s %s\n", sender); *file = *route = '\0'; fgets(buffer, LINE, fptr); /* Read the subject */ strupr(buffer); /* Capitalize */ /* Scan dir and route */ sscanf(buffer, "%[^@\n]%[^\n]", file, route); fclose(fptr); /* All needed is read in the message */ /* We must get some informations from the INIT.SRV file */ fptr = fopen("INIT.SRV", "rt"); /* Open the file */ if (fptr == NULL) exit(1); /* Scan the file to get the requested lines. */ while (!end) { fgets(buffer, LINE, fptr) ; if (*buffer == '#') continue; /* Comments ignored */ switch (++index) { case BBS_CALL: sscanf(buffer,"%[0-9A-Za-z]", bbs_call); break; /* Callsign */ case USER_DIR: sscanf(buffer,"%s\n", base_dir); break; /* Users directory */ case MAIL_IN : sscanf(buffer,"%s\n", mail_in); end = 1; /* Mail in file */ break; } } fclose(fptr); /* Append the answer to mail in file */ /* Mail in file is opened in appent text mode */ if (fptr = fopen(mail_in, "at")) { /* Tell that this is a message from this BBS */ FBB 5.15 Feb 06 1993 Page - 155 fprintf(fptr, "#\n"); /* Send command line */ fprintf(fptr, "SP %s %s < %s\n", sender, route, bbs_call); /* Send subject and requested file */ send_file(fptr, base_dir, file); /* Send end of message */ fprintf(fptr, "/EX\n"); /* That's all ! */ fclose(fptr); } exit(0); /* Tell BBS all is correct */ } int points(char *ptr) /* Looks for a ".." sequence in the path */ { while (*ptr) { if ((*ptr == '.') && (*(ptr+1) == '.')) return(1); ++ptr; } return(0); /* ".." not fond ! */ } send_file(FILE *fptr, char *base_dir, char *filename) { #define BUF_SIZE 1000 int fd; int nb; char path[256]; char buffer[BUF_SIZE]; char last_char; sprintf(path, "%s%s", base_dir, filename); /* Complete path */ fprintf(fptr, "ReqFil 1.1 : %s\n", filename); /* Subject */ if ((!points(path)) && ((fd = open(path, O_RDONLY | O_TEXT)) != -1)) { while (nb = read(fd, buffer, BUF_SIZE)) { fwrite(buffer, nb, 1, fptr); last_char = buffer[nb-1]; } close(fd); /* Be sure /EX will be in first column */ if (last_char != '\n') fputc('\n', fptr); } else fprintf(fptr, "File not found !\n"); } FBB 5.15 Feb 06 1993 Page - 156 APPENDIX -11- Contents of directories. -------------------------------------- These files and directories are mandatory. Other files may reside but will be created by the system or by the sysop. Directory FBB : [BIN] BAT, COM and EXE files. [BINMAIL] Compressed messages. [DOCS] Files used for DOCS command. [OLDMAIL] Archives of messages. [MAIL] Ascii messages. [PG] COM and EXE files for PG command. [SYSTEM] System files. EPURMESS INI Init file for EPURMESS. INIT SRV Init file for SERV. NEWDOC SYS Configuration for NEWDOC server. Directory BIN : APPEL BAT Batch file running the software. CLEANUP COM Program to clean MAIL and BINMAIL directory. CUT COM Copy/paste utility. EPURMESS COM Message processing. EPURWP COM White Pages processing. ESS COM RS232 driver. ESSKAM COM KAM RS232 driver. FBBIOS COM MODEM driver. FV COM FV shareware used for LIST command in FbbDos. LOGSTAT EXE Log statistics. MAINTINF COM INF.SYS maintenance program. MAINTREJ COM REJET.SYS maintenance program. MKINF514 COM Change INF.SYS for 5.13 to 5.14 NEWDOC COM NEWDOC server. REQDIR COM REQDIR server. REQFIL COM REQFIL server. SATUPDAT EXE Automatic update of satellite database. SERV EXE FBB software EXE file. SETUSER COM set a user owner of a FbbDos file. SLEEP EXE waits for some seconds. TLABEL COM processes label file of FbbDos. Directory BINMAIL : [MAIL0] [MAIL1] [MAIL2] [MAIL3] [MAIL4] [MAIL5] [MAIL6] [MAIL7] [MAIL8] [MAIL9] Directory MAIL : [MAIL0] [MAIL1] [MAIL2] [MAIL3] [MAIL4] [MAIL5] [MAIL6] [MAIL7] [MAIL8] [MAIL9] Directory SYSTEM : [FWD] Directory for FORWARD.SYS includes [LOG] Directory for FBBLOG.nn files. [LANG] Directory for .TXT .HLP .ENT language files. [SAT] Directory for satellite files [WP] Directory for White pages database BALISEn SYS Beacon file. BBS SYS BBS callsigns CRON SYS Hour work. INITTNCn SYS Initialization of TNC. FORWARD SYS Forwarding description. LANGUE SYS Language description MAINTn SYS Housekeeping text. FBB 5.15 Feb 06 1993 Page - 157 MEMO SYS CtrlF0 to CtrlF9 aliases PASSWD SYS Password file. PORT SYS Port description. PROTECT SYS Directories protection. REJET SYS Messages reject. SWAPP SYS Swap file. FBB 5.15 Feb 06 1993 Page - 158 APPENDIX -12- CONNECTION FILTERING. ----------------------------------- FBB software allows filtering on connection. Filtering is not done by the BBS software but by external programs developped by users. Connection filter may be interactive and allows to incorporate some features like dedicated information for predifined callsigns, password filtering, etc... I did not develop such programs, but this is an open door to many applications. The C_FILTER program must be found by the PATH of MsDos. Its extension can be COM or EXE, and it must be little and fast as multitasking is stopped during the activity of this program. If this program is not found, it will not be called until the BBS is rebooted. When receiving the connection, the C_FILTER program (if found) is called with some arguments including a level number. This number is incremented each time the program is called in the same connection session. The first time the level number will be 0. The line arguments given to the C_FILTER program are : - Callsign (format as F6FBB-8). - Level number (0 is the first time, up to 99). - Flags of the user (binary number as user's mask of INIT.SRV). - New : Flag indicating if the user is unknown in the BBS database. - Record number of the user in INF.SYS. - Received data (each word is a new argument). The C_FILTER program ends with an exit value. This value is very important and tells the BBS what to do : 0 : end of session and return to the BBS menu. 1 : the program will be called again and the level number is incremented. 2 : the user will be disconnected. /* * C_FILTER.C * * Connection filter for FBB BBS software. (C) F6FBB 1991. * */ #include <stdio.h> /* * Connexion filter called for each connection. * All datas sent to stdout will be sent to the user. * * Filter is called with some arguments on the command line : * C_FILTER CallSign Level Flags New Record ReceivedData.... * * The return value tells the BBS if C_FILTER must be called again or not * 0 if the BBS can go on, * 1 if the C_FILTER must be called again * 2 if the user must be disconnected. * * Callsign is in the FORM CALLSIGN-SSID (F6FBB-0). FBB 5.15 Feb 06 1993 Page - 159 * * The first time C_FILTER is called Level=0, and then will be incremented * each time it is called for the same connection. * * Flags give the flags of the user (MGPBSXLE) in a bit field. as defined * in the INIT.SRV user's mask. (0x80=Modem, 0x40=Guest, etc...) * * If New=1, then this is the first connection of the user on the BBS. * Record is the record number in the INF.SYS file. * * All other arguments are the words sent by the user * (password for instance). * * The number of arguments is variable and depends of the number of words * in the answer of the user. * */ /* * This is only a little example to test the system. It will be called * four times and will give the list of arguments. * * The fourth time, the hand will be given back to the BBS. */ main(int ac, char **av) { int i; int level = atoi(av[2]); /* Get level from argument list */ /* and transform it to integer */ if (level == 0) { /* Is level equal to 0 ? */ printf("Connection line :\n"); /* This is the first call */ for (i = 0 ; i < ac ; i++) /* List line arguments */ printf("%s ", av[i]); putchar('\n'); return(1); /* C_FILTER must be called again */ } else { printf("Following line :\n"); /* These are other lines */ for (i = 0 ; i < ac ; i++) /* List line arguments */ printf("%s ", av[i]); putchar('\n'); if (level == 4) /* Is it the last time ? */ return(0); /* Yes, go on BBS */ else return(1); /* No, call once more C_FILTER */ } } FBB 5.15 Feb 06 1993 Page - 160 APPENDIX -13- MESSAGE FILTERING. -------------------------------- FBB software allows filtering messages. Filtering is not done by the BBS software but by external programs developped by users. may be interactive and allows to incorporate some features like dedicated information for predifined callsigns, password filtering, etc... I did not develop such programs, but this is an open door to many applications. The M_FILTER program must be found by the PATH of MsDos. Its extension can be COM or EXE, and it must be little and fast as multitasking is stopped during the activity of this program. If this program is not found, it will not be called until the BBS is rebooted. The message filter is called (if found) each time a message is ready to be recorded (when Ctrl Z or /EX is received). The decision to validate or not the message is function of the exit value of the M_FILTER program. The M_FILTER program (if found) is called with some arguments including a level number. This number is incremented each time the program is called in the same connection session. The first time the level number will be 0. The line arguments given to the M_FILTER program are : - File name including the text of the message. - Type of the message (P, B, T). - Sender. - "To" field. - Record number of DIRMES.SYS file. The M_FILTER program ends with an exit value. This value is very important and tells the BBS what to do : 0 : Message is recorded. 1 : Message is killed (status = K). 2 : Message is archived (status = A). 3 : Message is held (status = H). /* * M_FILTER.C * * The message filter MUST be named M_FILTER (COM or EXE). * * This example only writes its call arguments in the TEST.MES file. * * It is called with 5 arguments : * File name of the message. * Type . * Sender. * To. * Number of the record in the DIRMES.SYS file. * * If it returns 0 : The message is accepted. * 1 : The message is killed (status K). * 2 : The message is archived (status A). * */ #include <stdio.h> FBB 5.15 Feb 06 1993 Page - 161 main(argc, argv) int argc; char **argv; { int i; FILE * fptr = fopen("TEST.MES", "at"); for (i = 0 ; i < argc ; fprintf(fptr, "%s ", argv[i++])); fputc('\n', fptr); fclose(fptr); return(0); } FBB 5.15 Feb 06 1993 Page - 162 APPENDIX -14- PG programs development. -------------------------------------- PG programs are in the PG subdirectory. They are little programs allowing interactivity with the user. COM or EXE programs can be called. PG programs must be little as the amount of memory is limited and fast because the multitasking is stopped during its activity. To run a PG program and start a session, the user must type the command PG followed by the name of the program. The PG command alone gives the content of the PG subdirectory. The PG program is particularly developped for FBB software but can be an interface to a standard program. Each time a complete line (up to the return character) is received, the PG program is called with some arguments including a level number. This number is incremented each time the program is called in the same PG session. The first time the level number will be 0. The line arguments given to the PG program are : - Callsign (format as F6FBB-8). - Level number (0 is the first time, up to 99). - Flags of the user (binary number as user's mask of INIT.SRV). - Record number of the user in INF.SYS. - Received data (each word is a new argument). The PG program ends with an exit value. This value is very important and tells the BBS what to do : 0 : end of session and return to the BBS menu. 1 : the program will be called again and the level number is incremented. 2 : the user will be disconnected. 3 : the receive datas will be sent as a BBS command and return to BBS. 4 : the receive datas will be sent as a BBS command, level incremented. 5 : the program will be called again, but the level is not incremented. The datas sent by the PG program to the standard output will be sent to the user. This allows a real interactivity between the user and the PG program. FBB 5.15 Feb 06 1993 Page - 163 Here is an example of a little program : /* * TST_PG.C * * Little test program of "PG" command for FBB BBS software. * * (C) F6FBB 1991. * * FBB software 5.14 and upper. * * * This program echoes to the user what he types * or executes a BBS command preceeded by "CMD" * until "BYE" is received */ #include <stdio.h> main(int argc, char **argv) { int i; int level = atoi(argv[2]); /* Get level from argument list */ /* and transform it to integer */ if (level == 0) { /* Is level equal to 0 ? */ /* This is the first call */ printf("Hello %s, type BYE when you want to stop !\n", argv[1]); return(1); /* program will be called again */ } else { strupr(argv[5]); /* Capitalise the first word */ if (strcmp(argv[5], "BYE") == 0) { /* is BYE received ? */ printf("Ok, bye-bye\n"); return(0); /* Yes, go on BBS */ } else if (strcmp(argv[5], "CMD") == 0) { /* is CMD received ? */ for (i = 6 ; i < argc ; i++) /* List line arguments */ printf("%s ", argv[i]); /* sent by user */ putchar('\n'); for (i = 6 ; i < argc ; i++) /* List line arguments */ printf("%s ", argv[i]); /* sent by user */ putchar('\n'); return(4); /* Yes, send command */ } else { printf("You told me : "); /* These are other lines */ for (i = 5 ; i < argc ; i++) /* List line arguments */ printf("%s ", argv[i]); /* sent by user */ putchar('\n'); return(1); /* No, call again program */ } } } FBB 5.15 Feb 06 1993 Page - 164 APPENDIX -15- UNPROTO LISTS. ---------------------------- FBB software allows sending unproto lists of message. This is validated separately on each port (letter L in PORT.SYS). Unproto address is FBB with the following header : fm F6FBB-1 to FBB ctl UI An unproto list line is sent on every validated port each time a message is recorded. The line is in the form : 12345 B 2053 TEST@ALL F6FBB 920325 This is the subject If a message number is missing or does not exist the line will be : 12346 # This allows a system listening to the UI packets on a frequency to create a list identical to the one of the BBS, and then the user will not have to connect the BBS to know the list of messages and bulletins. A control can be done on the number of the messages to check if a line is missing. If the remote system receives a new line, and a line is missing, it only has to send an unproto frame addressed to the BBS callsign like this : fm FC1EBN-3 to F6FBB-1 ctl UI ? 00002EE00E This will be taken in account only if the user has the U flag validated (EU command). If the user has not his flag validated in the BBS, he will receive a line like : fm F6FBB-1 to FBB ctl UI 12200 / callsign In this case, the the remote software MUST stop asking unprotoes. The first 8 digits are the hexadecimal number of the requested start of the list (here 00002EE0 -> 12000) and the last two digits are the sum of the four bytes anded with FF (0E). The BBS will then starts sending lines from the requested number up to the last message number. If the number requested seems to be too far from the current line, the BBS can reajust the request of "callsign" while sending : fm F6FBB-1 to FBB ctl UI 12200 ! CALLSIGN 12201 B 2040 TEST@FRA F6FBB 920325 This is a bulletin 12202 # 12203 P 206 F6ABJ@F6ABJ F6FBB 920325 Hello Remy. etc... and then starts sending lines from 12201. The remote system must change its base number to 12201. FBB 5.15 Feb 06 1993 Page - 165 If the number requested is greater than the last message received in the BBS, the BBS will send a line like : 12300 !! This indicates that the list in the remote system is up to date. The last received message in the BBS is 12300. The remote system can also connect the BBS and ask for messages in binary compressed mode using the following sequence : BBS Remote system -------------------------------------------------------------------------- Connection request Connection. [FBB-5.14-ABFHM$] Welcome in Toulouse, Gerard. F6FBB BBS> [TPK-1.80-$] 1> F< #Msg Binary compressed message #Msg is sent using format described in appendix 7 1> Disconnect. From TPK version 1.80 (packet communication program developped by FC1EBN), this protocole is implemented. FBB 5.15 Feb 06 1993 Page - 166 APPENDIX -16- EXTENSIONS TO THE YAPP PROTOCOLE. ----------------------------------------------- These extensions are used in TPK 1.65a (and up) and FBB 5.14 and up. HEADER extension. The header now carries the DATE and TIME of the file being transmitted. [SOH] [Len] [Filename] [NUL] [File Size] [NUL] [Date] [Time] [NUL] The Date and Time are the values reported by DOS, coded in 4 hexadecimal digits and are sent in ASCII (8 characters). The receiver has the choice of using either extended Yapp with checksum or normal Yapp. The normal Yapp reply is RF, as before and the receiver can keep the date and time information . The extended Yapp reply is : RT Receive_TPK and is coded : [ACK] [ACK] If the receiver reply is RT the protocol used will be what I have called YappC for Yapp with checksum. When the sender gets this packet he MUST use YappC. Data Packets extension. If the receivers reply is RT the protocol used will be YappC. The checksum allows detection of packets corrupted along the link, particularly on the RS232 lines where there is no error control or correction (or it's very poor!) Data packets : [STX] [Len] [Datas] [Checksum] Checksum is the sum of all datas bytes anded with FF in 8 bits like Xmodem. If the checksum is bad then the receiver must send a Cancel and enters CW state. Crash Recovery. A new field has been added to the resume reply to tell the sender if the receiver can use YappC or not. Resume is sent instead of RF (or RT). Resume reply for Yapp: (as used before by TPK and FBB) [NAK] [Len] [R] [NUL] [Received Length] [NUL] I I I I I +-- in ASCII as in the header I +-- as Resume ! I +------- len of the following bytes Resume reply for YappC: [NAK] [Len] [R] [NUL] [Received Length] [NUL] [C] [NUL] I Tells sender I can use YappC -----+ When the sender gets this packet then he must also use YappC. FBB 5.15 Feb 06 1993 Page - 167