577 BN 2282 ALL DL5YBZ 870204 Neuer TNC2 Nachbau fertig Neuer TNC2 Nachbau loest DB3IG Konzept ab. ------------------------------------------ Nach dem Erscheinen des TCM3105 Modem IC's bestand der Wunsch,die fuer den PR Betrieb guenstigen Eigenschaften dieses ICS (klein,wenig Aussenbeschaltung, geringer Stromverbrauch und unipolare Versorung) auch fuer eine neues TNC2 Konzept zu nutzen. Dieses Konzept wurde nun von Mitgliedern der Rhein-Main Packet Gruppe entwickelt und aufgebaut. Herrausgekommen ist dabei eine 2 seitig durchkontaktierte Eurokarte,die sowohl Modem als auch CPU afnimmt. Die TNC Hardware entspricht dabei dem bekannten TNC2a konzept,wobei allerdings wie auch schon beim db3ig Konzept die Taktfrequenz des Z80 verdoppelt wurde, als 4.9Mhz Taktfrequenz.Weiterhin wurden einige Verbessrungen bei der Backupfunktion der Rams vorgenommen,die aber alle dei Software Kompatibiltaet nicht betreffen,es lauft also nach wie vor jede TNC2a Soft auch auf der neunene Frankfurter Version. Allerdings geht die Uhr nach dem Mond,wenn man nicht die Software auf die dopplete Clock hin anpasst (eine Speicherstelle aendern). Auch bei der Interrupt steuerung der Uhr wurde eine Veraenderung an der Software vorgenom,mmen (db1zg schlugzu..) ,die eine verbesserte Ganggenauigkeit zur Folge hat. (Weniger Interrupts der Uhr...) Doch nun zu den einzelnene Daeten: ICs: alles in CMOS Rechner: Z80,SIO,32k EPROM,32k RAM Modem: TCM 3105 Schnittstelle: ---------------- V24 /24 pol Stecker (wahlweise TTL pegel,da dPie Anpassung TTL/V24 mit MAX 232 passiert (ein IC ! kann man also einfach statt IC Brueken einbauen) Nf+PTT -------- ueber einen 5pol Dinstecker. zusatzmodem ueber den bekannten MODEM DISCONNECT Stecker vom TNC2a. Stromversorgung: ----------------- Unipolar 7-15 V DC ueber die V 24 Buchseoder einfach mit AC auf die Platine,Gleichricher ist schon auf der Karte mit drauf. Stromaufnahme : ca 50 mA,wenn alle Leds aus sind... Preis: (so ca.) Bausatz etwa 300 DM/Einzelplatinen auf Anfrage Bezug: DF5FF,Hellmut Landolt 6457 maintal 1 Wingerstr. 114 Tele# 06181/4593 Diese obige Konzept loest die alte alte 2 Eurokarten Bauform des Unter "DB3IG TNC2eknnten ab. Infos wie immer ohne Gewaehr... Tschuess aus Coesfeld de Olaf,DL5YBZ. WA7MBL MailBox - Version 2.04 - 01/17/86 [These notes have not been updated to fully describe all of the latest commands - Better documentation is coming!] This is an adaptation of the W0RLI MailBox and GateWay for the IBM PC series of computers and compatibles. The W0RLI system is written in Z-80 assembly language for use on the Xerox 820 computer under CP/M. Version 2.04 is released for the purpose of BETA testing to selected sites. It is not intended for general distribution at this time. Source code is NOT available at this time. Jeff Jacobsen, WA7MBL 1400 E 900 N Logan, UT 84321 I may also be contacted by the following methods: BITNET - BOBW @ USU Compuserve - 72446,2557 Phone - 801-753-0099 ------------------------------------------------------------------- Distribution is now being handled by: Arizona Packet Radio Association (AzPRA) PO Box 8642 Scottsdale, AZ 85252-8642 Phone: 602-947-0362 (Wes Morris, K7PYK) 602-946-8356 (Answering Machine) UPS address: Wes Morris 7422 E McKinley St. Scottsdale, AZ 85257 ACKNOWLEDGEMENTS I used the following as a starting point for this translation: W0RLI MailBox/GateWay - Version 10.2 - W0RLI The W0RLI Mailbox Sysop Documentation - Revision 10.2.0 - WB2MNF Log File Analyzer - WB7DCH .......... The W0RLI system for the Xerox 820 was written by: Hank Oredson, W0RLI 19 North Hill Road Westford, MA 01886 .......... The SYSOP Manual was written by: Jon Pearce, WB2MNF 109 Pine Cone Trail Medford, NJ 08055 .......... The log file analyzer was written by: Tom Hogan, WB7DCH 26911 S E 456 St. Enumclaw, WA 98022 ........... The Tucson Amateur Packet Radio Corporation (TAPR) has helped support this effort. If you are not already a member, I suggest that you join. (TAPR, Box 22888, Tucson, AZ 85734.) I would like to thank Robert Wood, WA7MXZ for help in local testing and for the use of his BITNET account. I would also like to thank all Beta testers. A list of current beta test sites will be included on the distribution diskette as SITE.DOC Many of them made financial contributions which helped make this possible. Finally, I would like to thank Randy Forgaard, a regular on the CompuServe Borland SIG, for offering routines to solve problems associated with the Turbo Database Access Tools. RELEASE NOTES: For the present time, I assume that all Users are familiar with the W0RLI system. This documentation will therefore be quite skimpy and will mainly detail the differences between this verision and the original W0RLI version. To speed development of this system, I used the TURBO Access B-tree routines available in TURBO DATABASE TOOLBOX from Borland International. These routines are used to keep both the User records and the Mail header records. The mail messages themselves are kept as seperate files rather than as one big file. This was also done in the interest of getting a system up and running rapidly. It may prove to be a problem with a large number of messages (it certainly would be a limitation if an attempt was made to modify this code to run under CP/M.) The files are stored under the names MSG00001.MAI etc. I have not yet written anything to renumber the messages & files, so if you approach message # 32000 too soon, you may find yourself in a bit of a bind. To keep the mail and download/upload files seperate from everything else, I recommend that each be placed in seperate subdirectories. The path names for both may be specified in the BBSxxx.CNF file. The sub-directories must exist, BBS will not create them. I use the following setup (with the main program in a subdirectory called \BBS) on my hard disk: \BBS\ BBS.COM BBSxxx.CNF FWD.TNC LOG.TNC MESSAGES.DAT MESSAGES.IDX USERS.DAT (etc) \BBS\MAIL\ MSG00001.MAI MSG00002.MAI (etc) \BBS\FILES\ BBS.DOC GT851112.TXT TNC2.MOD (other user uploaded/downloadable files) If you want the users to be able to download LOG.TNC, FWD.TNC, etc, place them in the FILES\ subdirectory and set the files names in BBSxxx.CNF accordingly. For the present, BBSxxx.CNF must reside in the current directory. If you want users to be able to download it, you will have to place a copy into FILES\. The recommended setup parameters for the TNCs are in .SET files, TNC1.SET for a tnc1, TNC2.SET for a tnc2. RELEASE NOTES (Cont): The file BBSxxx.CNF is a text file that contains all site-specific parameters. Edit it to have the proper parameters for your site. 'F' qualifier (applies to commands D, F, M, U and W) When a remote user uses any of the file commands (D, U or W) the "file" path from CONFIG.TNC will be added to the file name entered, thus D BBS.DOC will refer to \BBS\FILES\BBS.DOC. The path name is not added in sysop mode unless the qualifier 'F' is specified, thus W will do a directory listing of the current subdirectory (in my case \BBS) while WF will do a directory list of \BBS\FILES (the same listing a remote user will get by typing just W). The 'F' qualifier may be a 2nd qualifier in the case of the F or M commands (ie FAF or MPF W1XX ). Killed traffic does not generate a Service Message at this time. Flags in User record for Local User, Mail Drop, and Call Back are not used or set at this time. Configuration file name may be specified on command line BBS may be started with the command line BBS /a which will bypass the hit any key prompt and go immediately into answer mode (use for batch file start ups) The W command has been modified to allow WN (Whats New) which lists only the files that are new since the last log on. Perhaps it should be changed in the future so the W command (like the L command) only lists what is new and perhaps a WA (all) command is required to list all files (comments...??) The W command also now lists free space. The 'Is BBS' flag has been added to the user record. Users who have the Is BBS flag set (Use the EU command and enter a Y at the appropriate question to set it) can do the following: 1 - Use the *** LINKED to to change users 2 - Use the < FROM with the S command (ignored from non BBS stations) 3 - Max # of digipeaters is ignored for BBS stations Also, allow connect from BBS only on TNCA or TNCB may be set in the Config file (thus keeping non BBS stations off of one or both ports) RELEASE NOTES (Cont): CTS/RTS handshaking is used to/from the TNC. Early versions of the TAPR TNC contain a 6551 chip which has a problem with hardware handshaking: one character may get trashed when it is told to stop sending. If using only one TNC, it may be used on either COM1 or COM2. The cable should have pins 1-8 and 20 connected. The same cable (straight through) should work on both the TNC1 & TNC2. Configure the TNCs as shown in the appropriate .SET file, TNC1.SET for a tnc1, TNC2.SET for a tnc2. Note that several of the parameters differ depending on which type of tnc you have on the port. You can send the parameters to the tnc using the BA or BB commands, for example BA TNC2.SET. I have tried both the TNC1 and TNC2 v1 and both seem to work ok. In one instance when downloading a file using a TNC2 on the BBS, the TNC2 decided to stop handshaking correctly halfway through the file transfer and hung the system. I could not duplicate the problem later. I was using 9600 baud to communicate with the TNC at the time. System development was done on an IBM PC/AT under PC DOS 3.1 using TURBO PASCAL version 3.01A from Borland International. The software uses interrupts for input from the TNC's. It also uses timer tick interrupts from the PC. Thus interrupt vectors $0B, $0C, and $1C are modified when the program starts. On most errors the interrupt vectors are restored before the program is exited, but it is possible that they will not be reset. If not restored, the vectors will still be pointing to where the program used to reside and if you try to run another program you may hang the system. LOCAL COMMANDS The following commands are on the local menu only. The local menu also allows the same set of message commands as the remote menu. See BBS.DOC for a list of remote menu commands. B - Send a file to the TNC. Qualifier: TNC to send file to (A or B). Argument: Name of file to send. C - Connect to user. D - Display a file. Qualifier: P - Page mode. (local mode only) U - List the user file. 2nd Qualifier: F - Use File path. Argument: File name. (Legal commands are D, DF, DP, DPF, and DU) E - Edit a message header, or user record. Qualifier: U - Edit a user record. Argument: Message number or user call. F - Make a file from a message. Qualifier: A - Append to existing file. 2nd Qualifier: F - Use File path. Arguments - (Note: the 2nd qualifier may appear in place of the qualifier or in addition, thus the following commands are legal: F 6 TEST.TXT create TEST.TXT in current subdir FA 6 TEST.TXT append to TEST.TXT in current subdir FF 6 TEST.TXT create FILES\TEST.TXT FAF 6 TEST.TXT append to FILES\TEST.TXT ) G - Enable / Disable GateWay. Qualifier: Y - Enable, N - Disable. H - Toggle short / long local menu. M - Make a message from a file. See 'S' command. Arguments: [@ call] (This also allows a 2nd qualifier of 'F' to specify that the file is in the upload/download area. Note: The case of MF will create a message with a blank message type (normal) from the file area rather than a message type of 'F'. MFF will create a message type F from the file area. If you really need to create a message type F from outside the file area, you can always use something like MA to create message type A, then edit the message header. LOCAL COMMANDS - Cont P - Enable Sysop Paging Qualifier Y-Allow it N-Sysop not Available P - Display last connect path. Q - Quit (return to DOS). T - Go to terminal mode. Qualifier selects TNC (A or B). U - Upload a file from the console. Qualifier: A - Append to existing file. F - Use File path. (UAF is an allowed form of this command) X - Trigger an auto-forward. Qualifier: I - Ignore times in FWD.TNC Argument: If present, call of station to forward to. Other entries in FWD.TNC ignored. Y - Set file name - Allows switch of forwarding file. Qualifier: F - FWD.TNC Argument: Z - Delete a file. Argument: Qualifier: F - Use File path. REMOTE SYSOP The commands D,E,F,G,M,Y,Z are available to the remote sysop. @ - Switch remote user between the standard remote menu and the remote sysop commands. Must have S privilege. FILE LAYOUTS The Configuration File - BBSxxx.CNF (xxx = current version #) The file BBSxxx.CNF is a text file that contains all site-specific parameters. Edit it to have the proper parameters for your site. The form $x is a variable text field. The "$x" is replaced by the current value for that text. $A - @ BBS of the current message. $B - Bell - insert an ASCII BEL (CTL-G). $C - Next available message number. $D - The current date. $E - Version number. $F - Clear Screen. $G - TO of the current message. $H - Hang at end of line (suppress carriage return). Use at end of line only. DO NOT USE on lines that go to tnc.