@DATABASE "A Guide To TrapDoor" @INDEX index @AUTHOR "Maximilian Hantsch" @(C) Copyright 1994 by Maximilian Hantsch, all rights reserved. @NODE MAIN "A Guide To TrapDoor" @{B}Table of Contents@{UB} @{" 1. Introduction " link 1} @{" 2. Installation " link 2} @{" 2.1. The Keyfile " link 2.1} @{" 2.2. Point Setup " link 2.2} @{" 2.3. Node Setup " link 2.3} @{" 2.4. The Modem " link 2.4} @{" 2.5. Example Modem Settings " link 2.5} @{" 2.5.1. Ordinary 2400 Baud Modems " link 2.5.1} @{" 2.5.2. US Robotics Courier HST Modems " link 2.5.2} @{" 2.5.3. Internal Supra 2400zi Modems " link 2.5.3} @{" 2.5.4. Supra V.32bis " link 2.5.4} @{" 2.5.5. ZyXEL Modems " link 2.5.5} @{" 3. Basics " link 3} @{" 3.1. FidoNet " link 3.1} @{" 3.2. Mailer Operation " link 3.2} @{" 3.3. Nodelist " link 3.3} @{" 3.4. Compatibility " link 3.4} @{" 3.5. Custom Configuration Entries " link 3.5} @{" 3.6. Accounting " link 3.6} @{" 3.7. Security " link 3.7} @{" 3.8. File Tagging " link 3.8} @{" 3.9. Refusing and Pickup Preferences " link 3.9} @{" 3.10. The Keyboard " link 3.10} @{" 3.11. Return Values " link 3.11} @{" 3.12. Fax and Voice Support " link 3.12} @{" 3.13. Automatic Buffer Sizing " link 3.13} @{" 3.14. ARexx " link 3.14} @{" 3.15. Dial Scripts " link 3.15} @{" 3.16. Multiple Lines " link 3.16} @{" 3.17. Logfile Buffering " link 3.17} @{" 3.18. OwnDevUnit.library Support " link 3.18} @{" 4. Configuration Commands " link 4} @{" 4.1. Embedded Percent-Commands " link 4.1} @{" 4.2. Modem Commands " link 4.2} @{" 4.3. Keywords " link 4.3} @{" 4.3.1. (NO)7WIRE " link 4.3.1} @{" 4.3.2. ABORT signals " link 4.3.2} @{" 4.3.3. (NO)ABS " link 4.3.3} @{" 4.3.4. (NO)ACCOUNTING " link 4.3.4} @{" 4.3.5. ACCTMAX limits " link 4.3.5} @{" 4.3.6. ADJUST factor " link 4.3.6} @{" 4.3.7. AFTERSESSION command-string " link 4.3.7} @{" 4.3.8. AKA akalist " link 4.3.8} @{" 4.3.9. (NO)ALLOWREFUSING " link 4.3.9} @{" 4.3.10. ANSWER " link 4.3.10} @{" 4.3.11. ARQSTRING string " link 4.3.11} @{" 4.3.12. (NO)AUTOADJUST " link 4.3.12} @{" 4.3.13. (NO)AUTOOVERSCAN " link 4.3.13} @{" 4.3.14. (NO)BACKGROUND " link 4.3.14} @{" 4.3.15. BANNER bannerline " link 4.3.15} @{" 4.3.16. BAUD baudrate " link 4.3.16} @{" 4.3.17. BBSCHAR character " link 4.3.17} @{" 4.3.18. BBSCOMMAND command-string " link 4.3.18} @{" 4.3.19. BBSINOUT device " link 4.3.19} @{" 4.3.20. BBSMESSAGE text " link 4.3.20} @{" 4.3.21. BBSMODE mode " link 4.3.21} @{" 4.3.22. (NO)BEEPDISPLAY " link 4.3.22} @{" 4.3.23. BOSS zone:net/node.point " link 4.3.23} @{" 4.3.24. CALL number | fido-address " link 4.3.24} @{" 4.3.25. COLORS palette-specification " link 4.3.25} @{" 4.3.26. COLOURS palette-specification " link 4.3.26} @{" 4.3.27. CONCEPTS " link 4.3.27} @{" 4.3.28. CONFIG config-file " link 4.3.28} @{" 4.3.29. COST cost-value " link 4.3.29} @{" 4.3.30. CREDITS " link 4.3.30} @{" 4.3.31. DIALER command-string " link 4.3.31} @{" 4.3.32. DIALTIMEOUT seconds " link 4.3.32} @{" 4.3.33. (NO)DIETIFNA " link 4.3.33} @{" 4.3.34. (NO)DIRECTZAP " link 4.3.34} @{" 4.3.35. DISPLAYID integer " link 4.3.35} @{" 4.3.36. DROPBBSSECS seconds " link 4.3.36} @{" 4.3.37. (NO)DSR " link 4.3.37} @{" 4.3.38. (NO)EMSI " link 4.3.38} @{" 4.3.39. (NO)ESCAPERESETSMODEM " link 4.3.39} @{" 4.3.40. (NO)FASTEMSI " link 4.3.40} @{" 4.3.41. FAXCOMMAND commandline " link 4.3.41} @{" 4.3.42. FAXSTRING string " link 4.3.42} @{" 4.3.43. FKEY function-key-assignment " link 4.3.43} @{" 4.3.44. (NO)FLOATLOCK " link 4.3.44} @{" 4.3.45. (NO)FORBID... " link 4.3.45} @{" 4.3.46. FREQUEST command-string " link 4.3.46} @{" 4.3.47. HELP " link 4.3.47} @{" 4.3.48. (NO)IMMEDIATE " link 4.3.48} @{" 4.3.49. INBOUND inbound-mail-directory " link 4.3.49} @{" 4.3.50. (NO)INTERLACE " link 4.3.50} @{" 4.3.51. (NO)KEEPALL " link 4.3.51} @{" 4.3.52. (NO)KEEPXMAIL " link 4.3.52} @{" 4.3.53. (NO)KIWIPULSE " link 4.3.53} @{" 4.3.54. (NO)LISTEN " link 4.3.54} @{" 4.3.55. (NO)LOCK " link 4.3.55} @{" 4.3.56. LOG level:text " link 4.3.56} @{" 4.3.57. LOGCALLERID filename " link 4.3.57} @{" 4.3.58. LOGFILE filename " link 4.3.58} @{" 4.3.59. LOGLEVEL group:level " link 4.3.59} @{" 4.3.60. LOGWINDOW window-specification " link 4.3.60} @{" 4.3.61. (NO)MAXBAUD " link 4.3.61} @{" 4.3.62. MAXLOGLINES number " link 4.3.62} @{" 4.3.63. MAXLOGSECS seconds " link 4.3.63} @{" 4.3.64. MINBAUD baudrate " link 4.3.64} @{" 4.3.65. MODEMANSWER modem-answer-string " link 4.3.65} @{" 4.3.66. MODEMDIALPRE modem-pre-dial-string " link 4.3.66} @{" 4.3.67. MODEMDIALPOST modem-post-dial-string " link 4.3.67} @{" 4.3.68. MODEMHANGUP modem-hangup-string " link 4.3.68} @{" 4.3.69. MODEMINIT modem-init-string " link 4.3.69} @{" 4.3.70. MODEMRESETINTERVAL minutes " link 4.3.70} @{" 4.3.71. NAME board's name " link 4.3.71} @{" 4.3.72. NODE zone:net/node.point " link 4.3.72} @{" 4.3.73. NODELIST nodelist-directory " link 4.3.73} @{" 4.3.74. OUTBOUND outbound-mail-directory " link 4.3.74} @{" 4.3.75. PASSWORD password " link 4.3.75} @{" 4.3.76. PICKUP what " link 4.3.76} @{" 4.3.77. PUBSCREENNAME name " link 4.3.77} @{" 4.3.78. QUIT " link 4.3.78} @{" 4.3.79. (NO)QUIET " link 4.3.79} @{" 4.3.80. REDIALDELAY seconds " link 4.3.80} @{" 4.3.81. RESET " link 4.3.81} @{" 4.3.82. RETRIES count " link 4.3.82} @{" 4.3.83. REXXNAME portname " link 4.3.83} @{" 4.3.84. RINGCOMMAND commandline " link 4.3.84} @{" 4.3.85. RINGINGS number " link 4.3.85} @{" 4.3.86. RINGS number " link 4.3.86} @{" 4.3.87. RUN command-string " link 4.3.87} @{" 4.3.88. SCLEAR " link 4.3.88} @{" 4.3.89. SCREENMODE mode " link 4.3.89} @{" 4.3.90. SCREENTOBACK " link 4.3.90} @{" 4.3.91. SCREENTOFRONT " link 4.3.91} @{" 4.3.92. SERIALBUFSIZE size-in-bytes " link 4.3.92} @{" 4.3.93. SERIALFLAGS serial-flags " link 4.3.93} @{" 4.3.94. SERIALNAME serial-device-name " link 4.3.94} @{" 4.3.95. SERIALUNIT serial-unit-number " link 4.3.95} @{" 4.3.96. (NO)SHARED " link 4.3.96} @{" 4.3.97. (NO)SHOWREXX " link 4.3.97} @{" 4.3.98. SLINE " link 4.3.98} @{" 4.3.99. SLOWMODEM modem-command-delay " link 4.3.99} @{" 4.3.100. SMODEM modem-command " link 4.3.100} @{" 4.3.101. (NO)SNIFFARQ " link 4.3.101} @{" 4.3.102. SPAWN command-string " link 4.3.102} @{" 4.3.103. STARTSESSION " link 4.3.103} @{" 4.3.104. STATUS what " link 4.3.104} @{" 4.3.105. STATWINDOW window-specification " link 4.3.105} @{" 4.3.106. STIMEOUT timeout " link 4.3.106} @{" 4.3.107. (NO)STRIPDASHES " link 4.3.107} @{" 4.3.108. SWAIT string " link 4.3.108} @{" 4.3.109. (NO)SWEPULSE " link 4.3.109} @{" 4.3.110. SWRITE string " link 4.3.110} @{" 4.3.111. SYSOP sysop's-name " link 4.3.111} @{" 4.3.112. TASKPRI priority " link 4.3.112} @{" 4.3.113. TESTFREQ " link 4.3.113} @{" 4.3.114. (NO)TIMESTAMP " link 4.3.114} @{" 4.3.115. (NO)TRAPZAP " link 4.3.115} @{" 4.3.116. TURNAROUND command-string " link 4.3.116} @{" 4.3.117. (NO)(UN)LISTEN " link 4.3.117} @{" 4.3.118. (NO)USESYSFONT " link 4.3.118} @{" 4.3.119. (NO)USEUSERSHELL " link 4.3.119} @{" 4.3.120. VOICECOMMAND commandline " link 4.3.120} @{" 4.3.121. VOICESTRING string " link 4.3.121} @{" 4.3.122. (NO)WAZOO " link 4.3.122} @{" 4.3.123. (NO)WRAPLINES " link 4.3.123} @{" 4.3.124. VERSION " link 4.3.124} @{" 4.3.125. (NO)XMAIL " link 4.3.125} @{" 4.3.126. (NO)ZEDZAP " link 4.3.126} @{" 4.3.127. (NO)ZEDZIP " link 4.3.127} @{" 4.3.128. (NO)ZOOMFULLSIZE " link 4.3.128} @{" 5. Example Setup " link 5} @{" 6. The Outbound Directory " link 6} @{" 6.1. 2-dimensional Filenames " link 6.1} @{" 6.2. 4-dimensional Filenames " link 6.2} @{" 6.3. Extensions " link 6.3} @{" 6.4. Packet files " link 6.4} @{" 6.5. Flow files " link 6.5} @{" 6.6. Compressed Mail files " link 6.6} @{" 6.7. Request files " link 6.7} @{" 6.8. Examples " link 6.8} @{" 6.9. Outbound File Tagging " link 6.9} @{" 7. The Inbound Directory " link 7} @{" 7.1. Bumping Filenames " link 7.1} @{" 8. Bugs? Poof! They're all features! " link 8} @{" 8.1. Real Bugs " link 8.1} @{" 9. Past & Future " link 9} @{" 10. Registration " link 10} @{" 11. Politics " link 11} @{" 11.1. Distribution " link 11.1} @{" 11.2. Support " link 11.2} @{" 11.3. Licence " link 11.3} @{" 11.4. No Warranty " link 11.4} @{" 11.5. Disclaimer " link 11.5} @{" 12. Acknowledgements " link 12} @{" 13. Index " link index} @ENDNODE MAIN TrapDoor® The Real Amiga Pleasure Version 1.84 Copyright (c) 1989-1994 Maximilian Hantsch and Martin Laubach All rights reserved TrapDoor's Fifth Manual Saturday 28-May-94 00:31:28 Copyright (c) 1989-1994 Maximilian Hantsch and Martin Laubach All rights reserved This manual is intended to be read from front to back for more convenience. @NODE 1 "Introduction " 1. @{B}Introduction@{UB} This manual is a description of TrapDoor Amiga, explaining how to set up the software in order to send and receive mail and attached files. Please refer to the documentation of other Fidonet packages, for example oMMM, ConfMail, Foozle or even better, the manual for TrapToss, for additional information on file attaches, netmail routing, echomail and other topics you are missing in here. If you are new to Fidonet, we recommend to read TrapDoor's Fidonet Manual (@{"FidoNet" link 3.1}.Man) first. Please read the @{B}entire@{UB} manual before using TrapDoor. TrapDoor is a @{"FidoNet" link 3.1}-compatible front mailer for Amiga systems. It transfers mail from/to other @{"FidoNet" link 3.1}-compatible systems using WaZoo DietIfna and ZedZap technique as well as the lowest common @{"FidoNet" link 3.1} protocol, FTS-0001 (Lotek). It also features the latest @{"EMSI" link 4.3.38} (Electronic Mail Standard Identification) handshake that allows two mailers to exchange lots of interesting information at session startup, for example @{"AKA" link 4.3.8} addresses. TrapDoor handles both sending and receiving of files and mail packets and is fairly easy to set up and use. It works well with high speed modems, and includes all the features found on standard @{"FidoNet" link 3.1} mailers, such as making and processing of filerequests, password-protected mail sessions, automatic nodelist lookup and much more. @ENDNODE 1 @NODE 2 "Installation " 2. @{B}Installation@{UB} TrapDoor is a CLI based application; it can't be run from Workbench. It accepts a wide range of keywords that allow an easy and accurate configuration. Upon invocation, TrapDoor will try to find a file "TrapDoor.cfg" in the current directory or in "MAIL:". This file should contain your default configuration data for TrapDoor, like your system's name, your nodenumber etc. (The option of saving the configuration data within the program file, which was available in earlier versions of TrapDoor, has been removed.) You should set up at least the @{"NAME" link 4.3.71}, @{"NODE" link 4.3.72}, @{"SYSOP" link 4.3.111}, @{"BOSS" link 4.3.23}, and @{"CALL" link 4.3.24} parameters. If you wish to change any parameters from the settings in your configuration file, just list the appropriate configuration keywords on the command line when you invoke TrapDoor. Please note that the keywords are neither case nor position sensitive. @ENDNODE 2 @NODE 2.1 "The Keyfile " 2.1. @{B}The Keyfile@{UB} TrapDoor is a Shareware program. The unregistered version will pop up requesters at the start and end of the program, and you will have to click some buttons with your mouse, or press some keys. Also, a few other functions are disabled in the unregistered version: - it will exit after every call - it will not respond to file requests Once you register, you will receive a so-called keyfile (to "unlock" your TrapDoor), which will make these requesters go away and enable all features of TrapDoor. For more information about "Shareware", and the registration process, please see the "@{"Registration" link 10}" chapter. @ENDNODE 2.1 @NODE 2.2 "Point Setup " 2.2. @{B}Point Setup@{UB} In a typical Amiga point setup, the installation of TrapDoor will merely consist of a few steps. If you are not familiar with @{"FidoNet" link 3.1} and @{"FidoNet" link 3.1} Point Systems at all, please read TrapDoor's @{"FidoNet" link 3.1} Manual (@{"FidoNet" link 3.1}.Man) first. 1. Copy the executable "TrapDoor" to a directory where you store your executable files. Copy "traplist.library" to "LIBS:". 2. Create a new subdirectory, and assign "MAIL:" to it, if you do not already have one. Create subdirectories "MAIL:Inbound" and "MAIL:Outbound". 2a. If you have already registered TrapDoor, and you have a keyfile called "TrapDoor.key", copy this to your "MAIL:" directory. 3. Copy the default configuration file to MAIL:TrapDoor.cfg. There is an example Point configuration file in the @{"Examples" link 5}/ directory, called Point.cfg. 4. Use a text editor to edit MAIL:TrapDoor.cfg to suit your system. (You can use Ed or MicroEmacs for that purpose.) Most important, change the @{"NAME" link 4.3.71}, @{"NODE" link 4.3.72}, @{"BOSS" link 4.3.23}, @{"CALL" link 4.3.24} and @{"PASSWORD" link 4.3.75} parameters. 5. That's it, you're done. Type "TrapDoor Call Boss" to call your boss system. @ENDNODE 2.2 @NODE 2.3 "Node Setup " 2.3. @{B}Node Setup@{UB} A @{"FidoNet" link 3.1} node is more complicated to set up. First, follow the steps in the "@{"Point Setup" link 2.2}" section. In addition to the directories created there, you will also need to setup a directory for the @{"FidoNet" link 3.1} nodelist. Create it on any partition large enough for at least 3 Megabytes of additional disk space, and assign "@{"Nodelist" link 3.3}:" to it. Now study the manual for TrapList and compile the @{"FidoNet" link 3.1} nodelist. (If you do not have a nodelist yet, you should use TrapDoor or a terminal program to obtain one from another @{"FidoNet" link 3.1} node.) Next, you need to create a scheduling script in which you tell TrapDoor to call out on certain days or during certain hours and what systems to call. This is usually done with a cron-like utility. Cron is a tool which executes other programs at regularly scheduled times. There is a good cron from TelePro Technologies. It is called TPTCron and freely available from many bulletin boards. TPTCron has successfully been used in many installations with TrapDoor. The main idea in a node setup is to run TrapDoor in answer mode. It will accept incoming calls and wait for @{"ARexx" link 3.14} commands. Then, you use cron to run "TrapPoll" every so often. TrapPoll is a tool that will scan your outbound directory to see what mail has to be delivered to which nodes, and send @{"ARexx" link 3.14} commands to TrapDoor to cause these nodes to be called. If you have TrapPoll executed by cron every ten minutes, TrapDoor will make outgoing calls until all mail and files have been sent, or until an accounting limit was reached (see the "@{"Accounting" link 3.6}" chapter for a description of the accounting system). By properly setting up your crontab file, you are able to exactly specify at what times TrapDoor should place outgoing calls, and when it should just sit around and wait for incoming calls. Also, you can run other scripts from cron that change TrapDoor's settings (like switching to @{"BBSMODE" link 4.3.21} ZMH during the Zone Mail Hour). Please see the Scripts/ directory for many example scripts for running a node. @ENDNODE 2.3 @NODE 2.4 "The Modem " 2.4. @{B}The Modem@{UB} @{"The Modem" link 2.4} @{B}must@{UB} be Hayes compatible. Other modem command standards are currently not supported. A word about cabling: you will need a seven-wire RS232C cable, that is one that supports at least RxD, TxD, CTS, RTS, DTR, @{"DSR" link 4.3.37}, DCD and last but not least, Gnd. Anything less (or other connections) may not have the desired effect, although the strict requirements which TrapDoor poses on the @{"DSR" link 4.3.37} signal can be bypassed by use of the @{"NODSR" link 4.3.37} keyword. Also, seven wire handshake can be disabled with @{"NO7WIRE" link 4.3.1}. Be sure to set up your modem so that dropping DTR causes a hangup, and a return to command state -- even better a complete reset. If you don't do this, TrapDoor will be incapable of hanging up correctly! On almost all Hayes compatible modems this can be achieved with AT&D3, a few may require changes to their DIP switch settings or S-registers. Please consult the manual that comes with your modem if you feel unsure. Also, take care that your modem should respond to successful connects with a "CONNECT XXXX" message (where XXXX is the baudrate), not just "CONNECT" (except at 300 baud). If your modem returns only "CONNECT", TrapDoor assumes that the connection takes place at 300 baud. On most Hayes compatible modems you will have to use ATX1 or higher. If your modem returns "CONNECT FAST" (Trailblazer modems do), TrapDoor will continue to operate at the baudrate specified in the @{"BAUD" link 4.3.16} statement. When DTR is set high, @{"DSR" link 4.3.37} should follow. In case your modem is reacting too slowly, try adjusting the @{"SLOWMODEM" link 4.3.99} parameter. If your modem cannot properly handle @{"DSR" link 4.3.37} at all, use the @{"NODSR" link 4.3.37} setting. Some modems require a substantial delay between the "AT" prefix and the actual command string. If this is the case with your modem, put at least one tilde ("~") character between the "AT" prefix and the command. This will cause TrapDoor to wait a short time before sending the rest of the string. Fine tune the time with @{"SLOWMODEM" link 4.3.99}. Some modems also require a substantial delay after a reset (caused by DTR drop or ATZ) before they respond to commands again -- insert tilde characters where appropriate! @ENDNODE 2.4 @NODE 2.5 "Example Modem Settings " 2.5. @{B}Example Modem Settings@{UB} These example setups for widely-used modems should get you started quickly. @ENDNODE 2.5 @NODE 2.5.1 "Ordinary 2400 Baud Modems " 2.5.1. @{B}Ordinary 2400 Baud Modems@{UB} Set your modem to: E1 echo modem commands Q0 display result codes V1 verbose results X1 or higher &C1 DCD follows carrier detect &D3 reset on dtr drop &S0 @{"DSR" link 4.3.37} always on To setup your modem, enter a terminal program and set the baudrate to 2400 baud. Then type AT&FE1Q0V1X4&C1&D3&S0&W and press return. You modem is now set up for use with TrapDoor. In your TrapDoor.cfg file, use the lines @{"BAUD" link 4.3.16} 2400 @{"SLOWMODEM" link 4.3.99} 10 @{"MODEMINIT" link 4.3.69} "~~AT~Z|~" @{"MODEMHANGUP" link 4.3.68} "|^" @{"MODEMDIALPRE" link 4.3.66} "~~AT~DP" @{"MODEMDIALPOST" link 4.3.67} "|~" @{"MODEMANSWER" link 4.3.65} "~~AT~A|~" @ENDNODE 2.5.1 @NODE 2.5.2 "US Robotics Courier HST Modems " 2.5.2. @{B}US Robotics Courier HST Modems@{UB} These are the settings for a Dual Standard HST modem. If you have the HST only or V.32 only version of the Courier, just set the parameters that apply to your modem only. USRobotics Courier 14400 HST Dual Standard NRAM Settings... DIAL=PULSE B1 F1 M3 X7 @{"BAUD" link 4.3.16}=19200 PARITY=N WORDLEN=8 &A3 &B1 &G0 &H1 &I0 &J0 &K3 &L0 &M4 &N0 &P0 &R2 &S0 &X0 &Y1 S02=043 S03=013 S04=010 S05=008 S06=007 S07=060 S08=002 S09=006 S10=007 S11=070 S12=050 S13=001 S15=008 S19=002 S21=010 S22=017 S23=019 S24=150 S26=000 S27=000 S28=008 S38=000 STORED PHONE #0: #1: #2: #3: To setup your modem, enter a terminal program. Select the baudrate at which you want to "lock" your modem, usually 19200 baud. (Warning: the serial.device of the Amiga - up to AmigaOS 1.3.3 - can @{B}not@{UB} keep up with 38400 baud. Unless you have a faster processor, like a 68020 or 68030, you will get lots of transmission errors if you choose a higher baudrate than 19200.) Then type AT&FM3X7&A3&B1&H1&K3&R2S13=1S15=8&W and press return. Your modem is now set up for use with TrapDoor. In your TrapDoor.cfg file, use the lines @{"BAUD" link 4.3.16} 19200 @{"LOCK" link 4.3.55} @{"7WIRE" link 4.3.1} @{"SLOWMODEM" link 4.3.99} 10 @{"MODEMINIT" link 4.3.69} "~~ATZ|" @{"MODEMHANGUP" link 4.3.68} "|^" @{"MODEMDIALPRE" link 4.3.66} "~~ATB1DP" @{"MODEMDIALPOST" link 4.3.67} "|" @{"MODEMANSWER" link 4.3.65} "~~ATB0S7=30A|" @{"ARQSTRING" link 4.3.11} "ARQ" @{"SNIFFARQ" link 4.3.101} @ENDNODE 2.5.2 @NODE 2.5.3 "Internal Supra 2400zi Modems " 2.5.3. @{B}Internal Supra 2400zi Modems@{UB} Set your modem to: E1 L2 M1 Q0 V1 X4 B0 Y0 &C1 &D3 &G0 &J0 &L0 &M0 &P0 &S0 S0=0 S2=43 S3=13 S4=10 S5=8 S6=2 S7=20 S8=2 S9=6 S10=14 S12=50 S25=5 S26=1 To setup your modem, enter a terminal program that can talk to "modem0.device" and set the baudrate to 2400 baud. Then type AT&FE1Q0V1X4&C1&D3&S0&W and press return. You modem is now set up for use with TrapDoor. In your TrapDoor.cfg file, use the lines @{"SERIALNAME" link 4.3.94} "modem0.device" @{"BAUD" link 4.3.16} 2400 @{"SLOWMODEM" link 4.3.99} 10 @{"MODEMINIT" link 4.3.69} "~~AT~Z|~" @{"MODEMHANGUP" link 4.3.68} "|^" @{"MODEMDIALPRE" link 4.3.66} "~~AT~DP" @{"MODEMDIALPOST" link 4.3.67} "|~" @{"MODEMANSWER" link 4.3.65} "~~AT~A|~" @ENDNODE 2.5.3 @NODE 2.5.4 "Supra V.32bis " 2.5.4. @{B}Supra V.32bis@{UB} Users of this modem recommend to set ATS95=2W2. We have not tested this modem. @ENDNODE 2.5.4 @NODE 2.5.5 "ZyXEL Modems " 2.5.5. @{B}ZyXEL Modems@{UB} These are the settings for a ZyXEL 1496 E modem, ROMs 6.11a or higher. If you have one of the other models, the parameters are the same. Current Setting............. B0 E1 L1 M1 N1 Q0 V1 X7 &B1 &C1 &D3 &G0 &H3 &J0 &K4 &L0 &M0 &N0 &P0 &R1 &S0 &X0 &Y1 *B0 *C0 *D0 *E0 *F0 *G0 *I0 *L0 *M0 *P9 *Q2 *S0 S00=000 S01=000 S02=043 S03=013 S04=010 S05=008 S06=003 S07=060 S08=002 S09=006 S10=015 S11=050 S12=000 S13=000 S14=002 S15=002 S16=000 S17=018 S18=000 S19=000 S20=001 S21=242 S22=000 S23=121 S24=034 S25=000 S26=000 S27=156 S28=068 S29=000 S30=000 S31=017 S32=019 S33=000 S34=030 S35=000 S36=000 S37=000 S38=008 S39=000 S40=000 S41=000 S42=002 S43=000 S44=000 S45=000 S46=000 S47=000 S48=004 S49=000 To setup your modem, enter a terminal program. Select the baudrate at which you want to "lock" your modem, usually 19200 baud. (Warning: the serial.device of the Amiga - up to AmigaOS 1.3.3 - can @{B}not@{UB} keep up with 38400 baud. Unless you have a faster processor, like a 68020 or 68030, you will get lots of transmission errors if you choose a higher baudrate than 19200.) Then type AT&FX7&D3S42.1=1S48.2=1&W and press return. Your modem is now set up for use with TrapDoor. In your TrapDoor.cfg file, use the lines @{"BAUD" link 4.3.16} 19200 @{"LOCK" link 4.3.55} @{"7WIRE" link 4.3.1} @{"SLOWMODEM" link 4.3.99} 25 @{"MODEMINIT" link 4.3.69} "~~ATZ|" @{"MODEMHANGUP" link 4.3.68} "|^" @{"MODEMDIALPRE" link 4.3.66} "~~ATDP" @{"MODEMDIALPOST" link 4.3.67} "|" @{"MODEMANSWER" link 4.3.65} "~~ATA|" @{"ARQSTRING" link 4.3.11} "ARQ" @{"SNIFFARQ" link 4.3.101} @ENDNODE 2.5.5 @NODE 3 "Basics " 3. @{B}Basics@{UB} This chapter is intended to give you a quick overview about the operation of TrapDoor and certain selected topics. If you wish to look up a specific command keyword, please see the reference section "@{"Configuration Commands" link 4}". @ENDNODE 3 @NODE 3.1 "FidoNet " 3.1. @{B}FidoNet@{UB} @{"FidoNet" link 3.1} is a world-wide network of many "@{"FidoNet" link 3.1}-compatible" bulletin boards, which communicate with each other using "mailers". TrapDoor is one of these mailers, it allows you to send and receive @{"FidoNet" link 3.1} mail and files. If you are not familiar with @{"FidoNet" link 3.1}, or certain terms used in this manual, please see "TrapDoor's @{"FidoNet" link 3.1} Manual" (@{"FidoNet" link 3.1}.Man) and the glossary there. @ENDNODE 3.1 @NODE 3.2 "Mailer Operation " 3.2. @{B}Mailer Operation@{UB} A mailer transfers mail bundles and/or files to/from another @{"FidoNet" link 3.1} system. You (or other mail packing software) prepare the outgoing mail and files in a so-called "outbound directory". You then tell TrapDoor to call another @{"FidoNet" link 3.1} system. TrapDoor will use the modem to place a telephone call there, then proceed to transfer mail/files with built-in protocols. Also, TrapDoor will receive mail and files that are waiting at the other system for you. These incoming data will be stored in the "inbound directory", from where you (or the mail tossing software) can further process the mail and files. A more detailed description of this process and the interaction between TrapDoor and mail processing software is given in TrapDoor's @{"FidoNet" link 3.1} Manual. @ENDNODE 3.2 @NODE 3.3 "Nodelist " 3.3. @{B}Nodelist@{UB} A "nodelist" is a directory listing all (or parts of) the nodes in @{"FidoNet" link 3.1}. It stores the names of systems and sysops, the node numbers, and the telephone number for each node. TrapDoor can use the nodelist to look-up telephone numbers before placing an outgoing call. A separate program called "TrapList" is used to process the nodelist before TrapDoor can reference it. TrapList builds index files for the nodelist, which TrapDoor later uses. For more information on TrapList and how to compile/index nodelists, please see "TrapList's Faaaast Manual" (TrapList.Man). Point systems do not necessarily need a nodelist, as they only call one single "boss" system, the telephone number of which can be stored in TrapDoor's configuration file. @ENDNODE 3.3 @NODE 3.4 "Compatibility " 3.4. @{B}Compatibility@{UB} A sensitive point in every @{"FidoNet" link 3.1} mailer is "compatibility". @{"FidoNet" link 3.1} uses at least three different handshake methods and more than three different transfer protocols. Not every mailer implements all of them, and so it is very important that mailers automatically detect the capabilities of the other system and switch to the correct handshake and protocol. This detection phase is also one of the sources of most errors and failures to establish a proper connection between two @{"FidoNet" link 3.1} systems. TrapDoor has been extensively tested with other mailers, including various versions of BinkleyTerm, D'Bridge, FrontDoor, Paragon and TrapDoor itself. It should work fine with most systems. There are two additional notes about compatibility, however. The @{"EMSI" link 4.3.38} handshake method sometimes causes problems with some BBSs with an integrated mailer, such as some older versions of Opus or Paragon. Should you repeatedly experience strange hangups with such a system, you should disable @{"EMSI" link 4.3.38} using the @{"NOEMSI" link 4.3.38} keyword and try again. Especially older versions of Paragon are known to not work correctly with @{"EMSI" link 4.3.38}. If you regularly call such a system, you might want to set up a "custom configuration" for that system (see the next chapter). Second, the FTS-1 "Lotek" protocol is very often poorly implemented in other mailers. TrapDoor uses a very strict version of this protocol, and behaves exactly according to the specifications. Other mailers with errors in their FTS-1 protocol code fail with TrapDoor. Two known cases are Tabby, a Macintosh mailer, which fails completely, and old versions of TIMS, an MS-DOS mailer, which sometimes failed to transfer the names of inbound files. (Newer versions of TIMS are fine.) TrapDoor will name the files "Unnamed.File", "Unnamed.File,1", "Unnamed.File,2" etc. Also, in the case of unnamed files, the files themselves may have some Ctrl-Z (hex 1A) characters at the very end, padding their size to an even multiple of 128 bytes. @ENDNODE 3.4 @NODE 3.5 "Custom Configuration Entries " 3.5. @{B}Custom Configuration Entries@{UB} Sometimes it is desirable to use a special custom configuration when calling a certain node. For example, if you regularly connect to a Paragon system which cannot handle @{"EMSI" link 4.3.38}, you will want to disable @{"EMSI" link 4.3.38} when calling that node. TrapDoor allows you to set up such custom configuration entries. There is a utility called "setconfig" to store a configuration string for a certain node number. For example, to disable @{"EMSI" link 4.3.38} for 2:314/471, enter setconfig 2:314/471 "@{"NOEMSI" link 4.3.38}" Custom configurations are very flexible. For example, you might have to use special modem settings to call some node. Using the setconfig utility, you enter setconfig 3:504/132 "@{"BAUD" link 4.3.16} 7200 @{"MODEMDIALPRE" link 4.3.66} \\ on one ATS42.3=1X29S133=45DT" / line Or, to override a telephone number from the nodelist: setconfig 2:253/500 "@{"CALL" link 4.3.24} 0044-44-123-1234" Here is another trick: if a node has been marked as -Undialable- in the nodelist, TrapDoor will refuse to call it. It will instead display something like "The Mad House (2:310/6) is undialable". If you know the telephone number of that system, you can enter setconfig 2:310/6 "@{"CALL" link 4.3.24} 0043-1-556-7863 @{"COST" link 4.3.29} 833" It is important that you specify the @{"COST" link 4.3.29} parameter here. Give it the cost per minute for that call. If you lose track of your custom configuration entries, the listconfig utility will list them all: Node : Config ------------------------ 2:310/6.0 : call 12341234 cost 6700 2:512/17.0 : @{"MODEMDIALPRE" link 4.3.66} ATS7=60B0X7DP @{"NOEMSI" link 4.3.38} 1:125/111.0 : @{"NOEMSI" link 4.3.38} Total 3 nodes in database @ENDNODE 3.5 @NODE 3.6 "Accounting " 3.6. @{B}Accounting@{UB} TrapDoor can keep a count of all outgoing calls and incoming calls, on a per node basis, and the cost for those calls. When you have enabled accounting (see the @{"(NO)ACCOUNTING" link 4.3.4} keyword), TrapDoor will maintain a database of - the number of outgoing calls to a node - the number of incoming calls from a node - the number of successful sessions with a node - the number of failed sessions with a node - the number of BUSY signals when calling a node - the number of NO CARRIER signals when calling a node - the number of VOICE signals when calling a node - the total cost of all outgoing calls to a node - the TrxID (a timestamp) of the last successful connection with that node The "listacct" tool will display all the accounting information, and "clearacct" will reset it, either on an individual basis or for all nodes. By using the @{"ACCTMAX" link 4.3.5} keyword, you can specify maxima for all of the above accounting items. You can set limits, and TrapDoor will refuse to call a node when at least one of the limits is exceeded. For example, you could set the maximum for the number of failed sessions to 2, and TrapDoor will refuse to call a node again after two failed connects (where a connection was made, but the carrier was lost before the successful end of the session). @ENDNODE 3.6 @NODE 3.7 "Security " 3.7. @{B}Security@{UB} It is often important to make sure that a particular system is really who it claims to be. For that reason, TrapDoor can use passwords to protect mail sessions. You can set up a password for each node you regularly exchange mail with, and TrapDoor will check the password every time this node calls you. If the password which the other end sends and the password that is stored in the local database do not match, TrapDoor will hang up, or, if the password for an @{"AKA" link 4.3.8} address is wrong, it will simply "forget" that @{"AKA" link 4.3.8} and will continue the session without sending mail or files for the @{"AKA" link 4.3.8} address. The "setpasswd" tool allows you to set up or remove passwords. For example, to setup a password of "vienna" for 2:313/28, enter setpasswd 2:313/28 "vienna" TrapDoor will always compare passwords using a case-insignificant match. It will, however, send out passwords exactly as you typed them, in case the other end does not use a case-insensitive compare. To protect you from losing your password database in case of a system crash, you can also enter "Password" statements in your TrapList configuration file and have TrapList set up all your passwords. This is described in more detail in the manual for TrapList. If you are running a private system, and you do not want to receive calls from any other nodes except the ones with which you have established passwords, you can set up a secret password using the @{"PASSWORD" link 4.3.75} keyword. Other mailers will only be able to connect to your system if either (a) they know the secret password or (b) you have set up another password for them (using setpasswd) and they send the latter one. If you are running a public @{"FidoNet" link 3.1} node, do not use the @{"PASSWORD" link 4.3.75} configuration keyword. @ENDNODE 3.7 @NODE 3.8 "File Tagging " 3.8. @{B}File Tagging@{UB} Another security feature of TrapDoor is "file tagging". Each received file will be tagged with a "Secure" field in the filenote, if it was received either from a node listed in the nodelist or from a node with which a password was set up. The "Secure"-Tag will contain either "NL" or "PW" or both "NL,PW" depending on the particular security measures under which the file was received. This can be used by a mail tosser to toss only mail from password-protected sessions automatically, for example. Also, every file received will be tagged with the node number of the system from which it was received, in a "From" field. Every @{"FidoNet" link 3.1} session will be assigned a unique number. This number will be recorded in the log file, and all files received in this session will be tagged with a "Trx" field listing this unique "transaction id". If files were renamed during the receive operation (for example, because the file already existed), the original filename will be stored in another field in the filenote, tagged as "FileName". @ENDNODE 3.8 @NODE 3.9 "Refusing and Pickup Preferences " 3.9. @{B}Refusing and Pickup Preferences@{UB} The Emsi handshake allows for "Refusing" and "Pickup Preferences". These features work only when an Emsi handshake was chosen at the beginning of the session. Refusing means that a system may refuse to receive certain files or certain mail packets at specific times. A system may refuse - file requests - compressed mail - file attaches - all of the above TrapDoor will respect these wishes and not send the appropriate items, unless @{"NOALLOWREFUSING" link 4.3.9} is in effect. Pickup Preferences means that another system may choose what mail or files to pick up from TrapDoor. A system may want to pick up mail and files - for all presented addresses - for the primary address only (no AKAs) - no pickup at all TrapDoor will respect these preferences and only send the requested items. @{"(NO)ALLOWREFUSING" link 4.3.9} does not affect this behaviour. To set up your own Refusing or Pickup Preferences, use the FORBID and @{"PICKUP" link 4.3.76} keywords. The default is to pick up mail for all presented addresses, and to not refuse to receive anything. @ENDNODE 3.9 @NODE 3.10 "The Keyboard " 3.10. @{B}The Keyboard@{UB} TrapDoor features sophisticated keyboard handling, including the ability to assign arbitrary configuration commands to function keys. One of the most important keys is probably the ESC (Escape) key. Pressing this key during a session will abort it. TrapDoor will hangup as soon as possible and either return to answer mode, or, if the call was not initiated from answer mode, exit. When TrapDoor is idle and you press the ESC key, it will reset the modem. Next, TrapDoor makes use of the Alt (Alternate) key for system functions. When TrapDoor is idle and waiting in answer mode, you can activate a number of things via Alt-key sequences. The Alt key works like a shift key: you have to hold it down while pressing another key. These are the Alt key sequences that TrapDoor understands: Alt-A ... immediately Answer the phone. Alt-C ... reread the Config file "MAIL:TrapDoor.cfg". This is useful if you have changed the config file and want to reset TrapDoor to the new settings. Alt-Q ... Quit, same as Alt-X. Alt-R ... Reset modem. Alt-S ... toggle Showrexx mode (see @{"SHOWREXX" link 4.3.97} keyword). Alt-X ... eXit, same as Alt-Q. If you get stuck and cannot remember a certain key, just press @{"HELP" link 4.3.47} .... pop up the Help display. Please note that TrapDoor will wait for the Help window to close before it exits. From the main help window, you can select "Settings" or "Keys". "Settings" will give you a short summary of all the current settings of your TrapDoor, "Keys" will show you a summary of all standard key assignments of TrapDoor. Select "Done" when finished reading. From the "Keys" display, you can also choose "F-Keys" which will show you a summary of the current function key assignments. Function key assignments can be put on any of the function keys (reasonable, eh?). These are the keys in the topmost row of your Amiga keyboard, beside the ESC key. The @{"FKEY" link 4.3.43} keyword is used to assign function keys. When you press a function key, and there is an assignment for it, TrapDoor will send the string assigned to that key to its own @{"ARexx" link 3.14} port. From there, the assignment will be processed. That way, you can put things like "Call 2:310/6" or "@{"NOEMSI" link 4.3.38}" on your function keys, or you can start external programs with the "Run" and "Spawn" keywords. Always remember that hitting a function key will cause TrapDoor to send an @{"ARexx" link 3.14}-message to itself. Thus, it will only process that keystroke when it is idle in answer mode. (It will actually process the keypress immediately, but the @{"ARexx" link 3.14}-message will be waiting at the @{"ARexx" link 3.14}-port until TrapDoor reads it when it comes back to the "Waiting for call" state.) @ENDNODE 3.10 @NODE 3.11 "Return Values " 3.11. @{B}Return Values@{UB} When TrapDoor returns to the calling program, the following returncodes indicate its success or failure: 0 ... everything successfully completed. 5 ... some minor problem occurred Either no session could be established (BUSY, NO CARRIER, VOICE etc.) or something went wrong during a session (timeouts, too many retries, carrier lost etc.). This can only occur if you do not start TrapDoor in answer mode, but immediately tell it to make a call, i.e. TrapDoor Call 2:310/6. 20 ... some fatal error prohibited any further action. TrapDoor could not open its window, screen, serial device or timer device, allocate memory or other necessary items. More detailed result codes are available through the @{"ARexx" link 3.14} interface. See the @{"STATUS" link 4.3.104} command. @ENDNODE 3.11 @NODE 3.12 "Fax and Voice Support " 3.12. @{B}Fax and Voice Support@{UB} TrapDoor can detect special "fax connect" and "voice connect" messages from the modem and run some external software to receive incoming fax or voice calls. See the description of the @{"FAXSTRING" link 4.3.42}, @{"FAXCOMMAND" link 4.3.41}, @{"VOICESTRING" link 4.3.121} and @{"VOICECOMMAND" link 4.3.120} keywords. @ENDNODE 3.12 @NODE 3.13 "Automatic Buffer Sizing " 3.13. @{B}Automatic Buffer Sizing@{UB} Some people have been complaining about the CPU usage of TrapDoor. The new feature of @{"Automatic Buffer Sizing" link 3.13} (@{"ABS" link 4.3.3} for short), if enabled, will try to reduce the CPU load of TrapDoor during Zmodem receiving. @ENDNODE 3.13 @NODE 3.14 "ARexx " 3.14. @{B}ARexx@{UB} TrapDoor includes an @{"ARexx" link 3.14} port -- while in answer mode waiting for incoming calls, TrapDoor also accepts @{"ARexx" link 3.14} messages. The port name, which is also called the "host name" in @{"ARexx" link 3.14} parlance, is "TrapDoor", unless you change it with the @{"REXXNAME" link 4.3.83} keyword. Use this name in Rexx "Address ..." statements to select TrapDoor. All commands and keywords listed in the "Configuration @{"Keywords" link 4.3}" section can be sent to the @{"ARexx" link 3.14} port and will be understood, although some might not behave as expected. (For example, if you change @{"SERIALNAME" link 4.3.94} while in answer mode, TrapDoor will @{B}not@{UB} switch to the new device. Instead, you should terminate TrapDoor and run it again with a different setup.) Apart from that, almost everything that can be set up from the command line (or a config file) can also be done via the @{"ARexx" link 3.14} port. Some commands can @{B}only@{UB} be used from @{"ARexx" link 3.14} (or TrapTell). Those keywords are marked with (+) @{"ARexx" link 3.14} only command Attempts to use them from the CLI will cause nothing but an error message. Usually, @{"ARexx" link 3.14} commands will be executed whenever TrapDoor is idle and waiting for a call. Some @{"ARexx" link 3.14} commands can also be sent for immediate execution. In that case, the command will be executed immediately, no matter whether or not TrapDoor is just connected to another system and a mail session takes place. For immediate execution, the command must be prepended with an "at" character ("@"). Such keywords are marked with (@) asynchronous execution possible Here are a few examples: /* This is a Rexx script to call my boss. TrapDoor must already be running in Answer mode. */ options results address "TrapDoor" "Call Boss" "Status D" say "Modem returned" RESULT "from the last call." "Status X" say "The last call terminated with error" RESULT"." Should you happen not to have a copy of @{"ARexx" link 3.14} handy, no problem -- the tool TrapTell simulates an @{"ARexx" link 3.14} server, sending a message to TrapDoor and waiting for the results. Here is an example. It stops a running TrapDoor by sending it a "Quit" command. TrapTell "Quit" Here's another example. First, we start up TrapDoor in answer mode, but we do not want it to react to incoming calls, so we set the @{"RINGS" link 4.3.86} limit very high. Immediately after launching TrapDoor, we wait a few seconds so TrapDoor has time to initialize everything and open its @{"ARexx" link 3.14} port. run TrapDoor answer rings 50000 wait 5 secs Then, I'd like to call node 1:200/300 and get the connect result string: TrapTell "call 1:200/300" TrapTell "status d" Try it, you should soon become familiar with that method of controlling programs. There are some example AmigaDOS scripts that use the TrapTell command in the Scripts/ subdirectory on the distribution disk (or in the distribution archive) and there are some more @{"ARexx" link 3.14} programs that make use of TrapDoor's @{"ARexx" link 3.14} port in the rexx/ subdirectory. @ENDNODE 3.14 @NODE 3.15 "Dial Scripts " 3.15. @{B}Dial Scripts@{UB} Sometimes, the built-in modem dialer in TrapDoor is not sophisticated enough. It will do fine for a normal telephone link between two nodes, but in some cases, two nodes might be linked via a packet switched network, a private network exchange, PCP, Telnet, Datex-P or whatever else there is. In these networks, it is usually necessary to log onto the network, identify yourself, and then select the network address or data telephone number with which you'd like to connect. Then, the network system will connect you, and only after that you will be able to establish your normal @{"FidoNet" link 3.1} session. TrapDoor features a tiny script language to accommodate this method of communication. You will have to write @{"ARexx" link 3.14}-scripts for your specific data network using the @{"STIMEOUT" link 4.3.106}, @{"SWRITE" link 4.3.110}, @{"SMODEM" link 4.3.100}, @{"SLINE" link 4.3.98}, @{"SCLEAR" link 4.3.88} and @{"SWAIT" link 4.3.108} commands. As soon as you have connected to the other @{"FidoNet" link 3.1} system, you issue the @{"STARTSESSION" link 4.3.103} command. Then, TrapDoor will take over again and proceed with a normal @{"FidoNet" link 3.1} session. Here is a short example: /* This is a Rexx script to connect to some other system via a custom data network. TrapDoor should already be running in Answer mode. */ address "TrapDoor" @{"STIMEOUT" link 4.3.106} 10 @{"SMODEM" link 4.3.100} "~~ATZ|" /* initialize the modem */ @{"SWAIT" link 4.3.108} OK @{"STIMEOUT" link 4.3.106} 60 @{"SMODEM" link 4.3.100} "ATDP1234" /* call the data network */ @{"SWAIT" link 4.3.108} CONNECT @{"SWAIT" link 4.3.108} "login:" /* wait for login prompt */ @{"SWRITE" link 4.3.110} "mad max"||d2c(13) /* send username */ @{"SWAIT" link 4.3.108} "password:" @{"SWRITE" link 4.3.110} "secret"||d2c(13) @{"SWAIT" link 4.3.108} "*" /* wait for prompt */ @{"SWRITE" link 4.3.110} "c 345-17635132#"||d2c(13) @{"SWAIT" link 4.3.108} "connection ok" @{"STARTSESSION" link 4.3.103} /* begin the session */ @ENDNODE 3.15 @NODE 3.16 "Multiple Lines " 3.16. @{B}Multiple Lines@{UB} TrapDoor can be run on multiple telephone lines. In order to reduce memory usage, we recommend making TrapDoor resident. This is achieved with the AmigaDOS Resident command as in Resident Mail:bin/TrapDoor ; or wherever TrapDoor ; resides on your system Next, you have to start each invocation of TrapDoor with different parameters for @{"SERIALNAME" link 4.3.94} or at least @{"SERIALUNIT" link 4.3.95}, and @{"REXXNAME" link 4.3.83}. TrapDoor will refuse to open if the serial device or the @{"ARexx" link 3.14} portname is already in use. Let us assume your configuration file contains, among other things, the statements SerialName "serial.device" SerialUnit 0 Now, the commands Run TrapDoor SerialUnit 1 RexxName "TrapDoor-1" Run TrapDoor SerialUnit 2 RexxName "TrapDoor-2" Run TrapDoor SerialName other.device RexxName "TrapDoor-3" will start three copies of TrapDoor. The first one will use serial.device, unit 1, and its @{"ARexx" link 3.14}-port will be named "TrapDoor-1"; the second will use serial.device, unit 2, "TrapDoor-2"; and the third one will use a special serial device named other.device, unit 0, and an @{"ARexx" link 3.14}-port of "TrapDoor-3". It is often useful to have separate configuration files for multiple lines, and change not only the above parameters, but also things like the window positions and sizes (@{"LOGWINDOW" link 4.3.60}, @{"STATWINDOW" link 4.3.105}) etc. Also note that there is a special @{"SCREENMODE" link 4.3.89} TRAPDOOR, which is very much like @{"SCREENMODE" link 4.3.89} CUSTOM, the difference being only that all invocations of TrapDoor will open their windows on the same shared TrapDoor-screen. (The first invocation of TrapDoor will open the screen, and the screen will close only after the last copy of TrapDoor has been shut down.). If you are using Kickstart 2.04 or higher, you can also use the new @{"SCREENMODE" link 4.3.89} PUBLIC, which works identically to @{"SCREENMODE" link 4.3.89} TRAPDOOR, but takes advantage of the KS 2.04 "Public Screens". That means that other programs can also share the TrapDoor screen, or TrapDoor can be made to run on other public screens. To send @{"ARexx" link 3.14}-commands to a specific copy of TrapDoor, use the @{"ARexx" link 3.14} ADDRESS command to select the port name. Here is an example: /* This @{"ARexx" link 3.14}-script closes down TrapDoor on line 3 */ address "TrapDoor-3" "quit" If you use TrapTell or TrapPoll, use the -p switch to select the portname, for example: TrapTell -pTrapDoor-3 "quit" @ENDNODE 3.16 @NODE 3.17 "Logfile Buffering " 3.17. @{B}Logfile Buffering@{UB} Older versions of TrapDoor (up to 1.80) would flush the logfile after every single line of log. This would slow down the program, especially when the logfile grew large. Thus, TrapDoor now allows you to configure a maximum number of lines and a maximum number of seconds, during which the logfile will not be flushed. If any of the two values has been exceeded, and a new line is written to the logfile, the file will be closed and reopened, thus forcing all data to be written to the disk. This is a two-edged sword: on the one hand, your system will become speedier if you don't let your logfile be flushed so often; on the other hand, if your system crashes for any reason, part of the logfile might not have been updated on the disk and you might just miss the important information that lead to the crash. So, you should flush the logfile at least after 10 seconds or so or after 10 lines of information. The logfile will always be flushed before an external program is run, so that the external software can add data to the TrapDoor logfile. Also, the logfile will be kept flushed when TrapDoor is idle waiting in answer mode. @ENDNODE 3.17 @NODE 3.18 "OwnDevUnit.library Support " 3.18. @{B}OwnDevUnit.library Support@{UB} Since version 1.84, TrapDoor now features support for OwnDevUnit.library. This is a freeware library that goes in your LIBS: directory and manages access to the serial port between multiple programs. Imagine your TrapDoor is running in answer mode, idle, and waiting for a call. Now you want to make an outgoing uucp call. Fortunately, the AmigaUUCP package by Matt Dillon also supports OwnDevUnit.library, and so you simply have to start "uucico" to make the outgoing call. Through OwnDevUnit.library, uucico will automatically let TrapDoor know that it wants the serial port, and TrapDoor will close it and relinquish it to uucico until uucico is done. At that point, TrapDoor will reopen the serial port, reinitialize the modem, and will be ready to accept new incoming calls or place outgoing calls. @{"Support" link 11.2} for OwnDevUnit.library is automatic. If the library can be opened, TrapDoor will use it. Note a few details: While the serial device has been "taken away" from TrapDoor, it will be in a "sleeping" state and reject most @{"ARexx" link 3.14} messages. With the exception of the asynchroneous commands (those that start with an @ character), TrapDoor will return all @{"ARexx" link 3.14} messages with a result code of 50 in this mode. OwnDevUnit.library is not provided with TrapDoor. It can be found on Fish Disk 650, for instance. @ENDNODE 3.18 @NODE 4 "Configuration Commands " 4. @{B}Configuration Commands@{UB} All configuration keywords are listed in the section "@{"Keywords" link 4.3}". They can be used either in the configuration file or on the command line. The keywords are neither case nor position sensitive. The meanings of the special notes (+) @{"ARexx" link 3.14} only command (@) asynchronous execution possible are explained in the "@{"ARexx" link 3.14}" chapter. If you wish to include space characters (blanks) in a string parameter, you must surround the string with double-quote characters, as in @{"SYSOP" link 4.3.111} "Maximilian Hantsch" The backslash ('\\') is used as an escape-character. For example, if you want to include a double-quote within a string, you need to use @{"NAME" link 4.3.71} "The \\"quoted\\" node" Of course, if you need a single backslash in a string, you need to escape it too, so you have to double each occurrance: @{"BANNER" link 4.3.15} "A Slash / and a Backslash \\\\ ..." @ENDNODE 4 @NODE 4.1 "Embedded Percent-Commands " 4.1. @{B}Embedded Percent-Commands@{UB} The @{"AFTERSESSION" link 4.3.7}, @{"BBSCOMMAND" link 4.3.18}, @{"DIALER" link 4.3.31}, @{"FAXCOMMAND" link 4.3.41}, @{"FREQUEST" link 4.3.46}, @{"RINGCOMMAND" link 4.3.84} and @{"VOICECOMMAND" link 4.3.120} keywords allow you to specify a commmand-string that will be executed. In these command-strings, the following embedded %-commands are permitted. All of them are case-sensitive. %a ... aka of the remote system (one aka per %a) %A ... all akas of the remote system (space separated) %b ... baudrate (between computer and modem) %B ... baudrate (of the actual connection) %C ... full CONNECT message from the modem %s ... serial device name %u ... serial device unit number %f ... serial device flags %r ... unique random number (timestamp) %l ... name of logfile %Z ... zone number of the other system %N ... net number of the other system %F ... fido node number of the other system %P ... point number of the other system %n ... complete @{"FidoNet" link 3.1} address of the other system %S ... name of Sysop of other system %R ... name of the @{"ARexx" link 3.14} port of this TrapDoor %p ... name of the public screen %I ... name of inbound directory %O ... name of outbound directory %d ... direction: 1 if inbound call, -1 if outbound call %% ... % For the @{"FREQUEST" link 4.3.46} keyword, the following sequences are allowed in addition to the above: %i ... name of the .REQ file (input file) %o ... name of the .RLO file (output file) Please note that %b and %B are equivalent unless you use @{"LOCK" link 4.3.55}. In that case, %b will reflect the LOCKed baudrate, whereas %B will give you the baudrate of the actual connection (that was returned by the modem in a "CONNECT XXXX" message). @ENDNODE 4.1 @NODE 4.2 "Modem Commands " 4.2. @{B}Modem Commands@{UB} All the modem commands (@{"MODEMINIT" link 4.3.69}, @{"MODEMDIALPRE" link 4.3.66}, @{"MODEMDIALPOST" link 4.3.67}, @{"MODEMANSWER" link 4.3.65} and @{"MODEMHANGUP" link 4.3.68} -- all explained later on) accept a few special characters in the configuration string. These are: ~ ... short delay ^ ... drop DTR, wait a while, raise DTR again | ... send a carriage return character \\ ... escape character, send next character as is All other characters will be sent to the modem unchanged and without any further action. As with configuration keywords, the backslash ('\\') is used as an escape-character for the following character, which is then just sent out unchanged. For example, if you need to send AT~Z4 to your modem, use AT\\~Z4| If you put this command into the configuration file, beware that the backslash needs to be escaped there. So you would have to use @{"MODEMINIT" link 4.3.69} "AT\\\\~Z4|" which gets even worse if you need to send a backslash to the modem. For example, some modems know commands such as AT\\N0. In the configuration file, this needs to be written as: @{"MODEMINIT" link 4.3.69} "AT\\\\\\\\N0|" @ENDNODE 4.2 @NODE 4.3 "Keywords " 4.3. @{B}Keywords@{UB} This section lists each configuration keyword and @{"ARexx" link 3.14} command that TrapDoor understands and explains the parameters and function of each keyword. The keywords are listed in alphabetical order. Boolean keywords, which can be preceeded by "NO" are listed under their main name; for example @{"(NO)DIETIFNA" link 4.3.33} is listed under "D". @ENDNODE 4.3 @NODE 4.3.1 "(NO)7WIRE " 4.3.1. @{B}(NO)7WIRE@{UB} Enable/disable 7-wire cabling. This will instruct the serial device to use (or not to use) the CTS and RTS signals. If you are using high speed modems with data compression, such as a US Robotics Courier HST, you must use @{"7WIRE" link 4.3.1} handshake and you must set your modem to "hardware handshake" mode, otherwise various difficulties will arise. This keyword defaults to @{"7WIRE" link 4.3.1}. @{"Examples" link 5}: 7Wire No7Wire @ENDNODE 4.3.1 @NODE 4.3.2 "ABORT signals " 4.3.2. @{B}ABORT signals@{UB} Abort is the @{"ARexx" link 3.14} equivalent of ^C, ^D, ^E and ^F. To "simulate" such a keypress, just send an "@{"ABORT" link 4.3.2} k" message, where k can be any of C, D, E or F. Multiple signals are OK, i.e. "@{"ABORT" link 4.3.2} CDEF" works as intended. For example, to terminate a TrapDoor that runs in answer mode, use "@{"ABORT" link 4.3.2} F". (+) @{"ARexx" link 3.14} only command (@) asynchronous execution possible (@ABORT) @{"Example" link 5}: TrapTell "Abort F" @ENDNODE 4.3.2 @NODE 4.3.3 "(NO)ABS " 4.3.3. @{B}(NO)ABS@{UB} Enables/disables @{"Automatic Buffer Sizing" link 3.13}. If this is turned on, TrapDoor will try to reduce its CPU usage during Zmodem receiving. @{"ABS" link 4.3.3} has no effect whatsoever on Telink/DietIfna/Xmodem/FTS1 sessions, on the YooHoo or @{"EMSI" link 4.3.38} handshake or on Zmodem sending. It defaults to @{"NOABS" link 4.3.3}. @{"Examples" link 5}: @{"ABS" link 4.3.3} NoABS @ENDNODE 4.3.3 @NODE 4.3.4 "(NO)ACCOUNTING " 4.3.4. @{B}(NO)ACCOUNTING@{UB} Turn accounting on or off. When enabled, TrapDoor will keep track of the number of calls made to a node, the total cost of all outgoing calls to that node, the number of calls received from that node, the number of successful and failed sessions as well as the number of calls that failed because of BUSY, NO CONNECTION or VOICE modem result strings. This keyword defaults to @{"NOACCOUNTING" link 4.3.4}. @{"Example" link 5}: @{"Accounting" link 3.6} @ENDNODE 4.3.4 @NODE 4.3.5 "ACCTMAX limits " 4.3.5. @{B}ACCTMAX limits@{UB} When accounting is enabled, TrapDoor, when instructed to call a certain node, will check whether or not this node exceeds the accounting limits set by this keyword. The limits parameter, a single string enclosed in quotes, sets - the maximum costs, - the number of calls out, - number of failed sessions (where a connection could be established, but the carrier was lost before the successful end of the session), - number of "busy" results, - number of "no connection/no carrier/no dialtone" results, - number of "voice" results, in that order. To disable a certain limit, just set it to minus one. This keyword defaults to @{"ACCTMAX" link 4.3.5} "-1 -1 -1 -1 -1 -1". @{"Example" link 5}: AcctMax "100 50 10 -1 -1 0" sets the limits for further outgoing calls to - Total cost thus far <= 100. - Number of calls made <= 50. - Number of failed sessions <= 10. - Number of BUSY, NO CONNECTION doesn't matter. - Number of VOICE <= 0 (i.e. don't call when there was VOICE only once). @ENDNODE 4.3.5 @NODE 4.3.6 "ADJUST factor " 4.3.6. @{B}ADJUST factor@{UB} NOTE: the following explanation is only valid for AmigaOS up to 1.3. The serial device has been dramatically improved in AmigaOS 2.04. If you have AmigaOS 2.04 or higher, set @{"ADJUST" link 4.3.6} to zero or leave it out completely. The value defaults to AJUST 0. Unfortunately, the Amiga serial.device software has a small problem with baudrates: not only will it calculate the value to stuff into the baudrate register of the serial hardware incorrectly and therefore use baudrates that are a bit offset from the correct value, but also this behaviour is different on NTSC and PAL machines, which makes it even worse. Some modems will work fine with such slightly wrong baudrates, others will not tolerate this and give a lot of transmission errors. By the way, this - it seems - is the main reason why programs such as BinkleyTerm Amiga fail to work with high-speed modems. TrapDoor offers you a cure for such problems: @{"ADJUST" link 4.3.6} allows you to specify how much TrapDoor will vary any given baudrate before it passes it on to the serial.device. This value should be given in thousands (1/1000). An example: at a value of -11, a baudrate of 2400 will be adjusted to 2400-1.1% = 2400-26.4 = 2373.6 baud. This value will be rounded to an integer and passed to the serial.device, which will then miscalculate the values for the hardware registers and set the hardware to almost exactly 2400 baud. Normally, you should leave this parameter at the default value. If you are using AmigaOS 1.3 or lower, and you seem to have serial problems, try setting it to -11, or maybe even something else. Experiment! @{"Example" link 5}: Adjust -11 @ENDNODE 4.3.6 @NODE 4.3.7 "AFTERSESSION command-string " 4.3.7. @{B}AFTERSESSION command-string@{UB} As soon as TrapDoor finishes a @{"FidoNet" link 3.1} session with another mailer, and hangs up the modem, it will call the command you specify here. There may be embedded %-commands, which will be substituted by the parameters of the session that just ended; a list of them can be found in the chapter "Embedded Percent-Commands". To turn off the @{"AFTERSESSION" link 4.3.7} command, use @{"AFTERSESSION" link 4.3.7} "" or omit the statement completely. The default is to have no @{"AFTERSESSION" link 4.3.7} command. @{"Examples" link 5}: AfterSession "run Execute Script:CheckInbound" AfterSession "" @ENDNODE 4.3.7 @NODE 4.3.8 "AKA akalist " 4.3.8. @{B}AKA akalist@{UB} During the @{"EMSI" link 4.3.38} handshake, not only your main address, but also a list of other "also-known-as" addresses will be sent to the other system. Using the @{"AKA" link 4.3.8} keyword, you can specify all your @{"AKA" link 4.3.8} addresses. should be a single string, listing all your other addresses. There is a limit of 20 AKAs for your system. The default is to have no AKAs. @{"Example" link 5}: Aka "2:3160/0 2:31/0 27:47/11" @ENDNODE 4.3.8 @NODE 4.3.9 "(NO)ALLOWREFUSING " 4.3.9. @{B}(NO)ALLOWREFUSING@{UB} Enables (disables) AllowRefusing mode. Default is @{"ALLOWREFUSING" link 4.3.9}. When AllowRefusing is enabled, TrapDoor respects the other end's wishes in the @{"EMSI" link 4.3.38} handshake. When the other end states it does not want to receive any compressed mail, for example, TrapDoor won't send it. With NoAllowRefusing, TrapDoor will always send what has to be sent. This keyword defaults to @{"ALLOWREFUSING" link 4.3.9}. @{"Examples" link 5}: AllowRefusing NoAllowRefusing @ENDNODE 4.3.9 @NODE 4.3.10 "ANSWER " 4.3.10. @{B}ANSWER@{UB} Forces TrapDoor to operate in "answer mode". TD will then wait for a call, answer the phone and try to start a session with the remote system. While in answer mode, TrapDoor will accept commands via its @{"ARexx" link 3.14} interface. @{"Example" link 5}: Answer @ENDNODE 4.3.10 @NODE 4.3.11 "ARQSTRING string " 4.3.11. @{B}ARQSTRING string@{UB} Tells TrapDoor what string the modem returns when it connects to another modem under an error-control protocol. HST modems, for example, return the string "ARQ" as in "CONNECT 9600/ARQ/HST/HST". You must setup the correct @{"ARQSTRING" link 4.3.11} for your modem when you use @{"FLOATLOCK" link 4.3.44} and/or @{"SNIFFARQ" link 4.3.101}. @{"Example" link 5}: ArqString "ARQ" @ENDNODE 4.3.11 @NODE 4.3.12 "(NO)AUTOADJUST " 4.3.12. @{B}(NO)AUTOADJUST@{UB} When AutoAdjust is set, TrapDoor will try to move or resize its status and/or log window to make them fit on screen, should their position and/or size be inadequate for the screen on which TrapDoor opens. This works only under KS 2.04 and higher. The default is @{"NOAUTOADJUST" link 4.3.12}. @{"Examples" link 5}: AutoAdjust NoAutoAdjust @ENDNODE 4.3.12 @NODE 4.3.13 "(NO)AUTOOVERSCAN " 4.3.13. @{B}(NO)AUTOOVERSCAN@{UB} When using the @{"SCREENMODE" link 4.3.89} CUSTOM, @{"SCREENMODE" link 4.3.89} TRAPDOOR or @{"SCREENMODE" link 4.3.89} PUBLIC option, switching this on forces TrapDoor to open its screen not to the standard NTSC or PAL size, but to the maximum size of the Workbench screen. If you use a program like "MoreRows" to expand your Workbench screen (under Kickstart 1.2/1.3) or use extended Overscan settings under AmigaOS 2.04 (or higher), and you would like TrapDoor to use the same expanded screen size, use this parameter. This keyword defaults to @{"NOAUTOOVERSCAN" link 4.3.13}. @{"Examples" link 5}: AutoOverScan NoAutoOverScan @ENDNODE 4.3.13 @NODE 4.3.14 "(NO)BACKGROUND " 4.3.14. @{B}(NO)BACKGROUND@{UB} When @{"BACKGROUND" link 4.3.14} is turned on, TrapDoor will open its screen behind all other screens. Also, when the log and status window are opened, they will not be activated, so your currently activated window will stay activated. The default is @{"NOBACKGROUND" link 4.3.14}. @{"Examples" link 5}: NoBackGround BackGround @ENDNODE 4.3.14 @NODE 4.3.15 "BANNER bannerline " 4.3.15. @{B}BANNER bannerline@{UB} This line will be sent to the other side when TrapDoor answers a call. This typically identifies your system, says "hi", or tells human callers to hang up. Instead of a single line, TrapDoor can also send a text file. In that case, use ". Below are a few useful mode ids. Note that if you use @{"DISPLAYID" link 4.3.35}, the keywords @{"INTERLACE" link 4.3.50} and @{"AUTOOVERSCAN" link 4.3.13} have no effect. If you do not specify @{"DISPLAYID" link 4.3.35}, TrapDoor will use a Hires screen, either interlace or not depending on the @{"(NO)INTERLACE" link 4.3.50} keyword. @{"Examples" link 5}: DisplayID $19000 ; NTSC Hires DisplayID $29000 ; PAL Hires DisplayID $19020 ; NTSC Superhires DisplayID $29020 ; PAL Superhires DisplayID $19004 ; NTSC Hires Interlace DisplayID $29004 ; PAL Hires Interlace DisplayID $19024 ; NTSC Superhires Interlace DisplayID $29024 ; PAL Superhires Interlace DisplayID $39024 ; VGA Productivity DisplayID $39025 ; VGA Productivity Lace DisplayID $39020 ; VGA Productivity Dbl (AA) DisplayID $69024 ; Euro72 Productivity DisplayID $69025 ; Euro72 Productivity Lace DisplayID $99000 ; DblNtsc Hires (AA) DisplayID $99005 ; DblNtsc Hires Lace (AA) DisplayID $a9000 ; DblPal Hires (AA) DisplayID $a9005 ; DblPal Hires Lace (AA) DisplayID $41000 ; A2024 10 Hz DisplayID $49000 ; A2024 15 Hz @ENDNODE 4.3.35 @NODE 4.3.36 "DROPBBSSECS seconds " 4.3.36. @{B}DROPBBSSECS seconds@{UB} When TrapDoor cannot detect a Fidonet handshake after @{"DROPBBSSECS" link 4.3.36} seconds, it will assume the caller is a human and pass the call to the BBS just as if the human had pressed Escape twice. You may not set @{"DROPBBSSECS" link 4.3.36} to anything lower than 10 seconds. The value defaults to 20 seconds. @{"Example" link 5}: DropBBSSecs 45 @ENDNODE 4.3.36 @NODE 4.3.37 "(NO)DSR " 4.3.37. @{B}(NO)DSR@{UB} After TrapDoor opens the serial.device, it will wait a short while (depending on @{"SLOWMODEM" link 4.3.99}) and then sample the @{"DSR" link 4.3.37} line. This line should be activated when a valid data set (i.e. a functioning modem) is connected to the serial line. If TrapDoor doesn't find @{"DSR" link 4.3.37} activated, it will report "modem not ready" and abort. This is the default. There are a few modems that cannot properly handle @{"DSR" link 4.3.37}. For these modems, use the @{"NODSR" link 4.3.37} setting. Note that when using @{"NODSR" link 4.3.37}, TrapDoor can't tell whether the modem is powered-on, on-line and ready. Also note that if you have not connected @{"DSR" link 4.3.37} to the modem (if you have a wrong/bad cable), RTS/CTS handshake might not work correctly. This is due to the way the Amiga serial.device handles things. @{"Examples" link 5}: NoDsr Dsr @ENDNODE 4.3.37 @NODE 4.3.38 "(NO)EMSI " 4.3.38. @{B}(NO)EMSI@{UB} Turns the @{"EMSI" link 4.3.38} handshake on or off. The default is on. Note that the @{"EMSI" link 4.3.38} handshake is the newest of all Fidonet protocols. Although @{"EMSI" link 4.3.38} is designed to be backwards compatible to older mailers, some fail when presented an @{"EMSI" link 4.3.38} handshake packet. If you experience any session handshake failures with other mailers, try again with @{"EMSI" link 4.3.38} disabled (use the @{"NOEMSI" link 4.3.38} switch). If you regularly call a node that cannot handle @{"EMSI" link 4.3.38}, you can set up a custom configuration string for that node. See the chapter "@{"Custom Configuration Entries" link 3.5}". @{"Examples" link 5}: NoEmsi Emsi @ENDNODE 4.3.38 @NODE 4.3.39 "(NO)ESCAPERESETSMODEM " 4.3.39. @{B}(NO)ESCAPERESETSMODEM@{UB} When you press the Escape key during a session, TrapDoor will immediately stop the transfer and hang up the phone. With @{"ESCAPERESETSMODEM" link 4.3.39} set, it will also send the @{"MODEMINIT" link 4.3.69} command afterwards. With @{"NOESCAPERESETSMODEM" link 4.3.39} (the default), TrapDoor will only hang up and wait for further instruction; you will have to press Escape a second time to re-initialize the modem. @{"Example" link 5}: NoEscapeResetsModem @ENDNODE 4.3.39 @NODE 4.3.40 "(NO)FASTEMSI " 4.3.40. @{B}(NO)FASTEMSI@{UB} Per default, @{"FASTEMSI" link 4.3.40} is enabled and this is what TrapDoor has been doing all the time since it could do @{"EMSI" link 4.3.38}: immediately after the connect, it will try to detect whether the other system can do @{"EMSI" link 4.3.38}, and if the other end indicates this, it will immediately start the handshake. This "fast" variant of @{"EMSI" link 4.3.38} can however, under very rare circumstances, give problems. One of the things that might lead to problems are asterisks ('*') in banner texts. If you call a system and repeatedly experience @{"EMSI" link 4.3.38} handshake failures, try turning off "fast" emsi with the @{"NOFASTEMSI" link 4.3.40} switch. When fast @{"EMSI" link 4.3.38} is turned off, @{"EMSI" link 4.3.38} handshakes will be a little bit slower (about 1-2 secs). @{"Examples" link 5}: FastEmsi NoFastEmsi @ENDNODE 4.3.40 @NODE 4.3.41 "FAXCOMMAND commandline " 4.3.41. @{B}FAXCOMMAND commandline@{UB} When TrapDoor detects a fax connect (it looks for @{"FAXSTRING" link 4.3.42} in messages from the modem), it will spawn this external program. Using this technique you can run your fax software to accept incoming fax calls, while at the same time allowing ordinary modem callers to go to the bulletin board or to run a @{"FidoNet" link 3.1} session with your system. There may be embedded %-commands in the string, these are described in the chapter "Embedded Percent-Commands". This will also work on outgoing calls. You can use the embedded percent command "d" to tell your fax software if this is an outgoing or incoming call. @{"Example" link 5}: FaxCommand "Fax %d" @ENDNODE 4.3.41 @NODE 4.3.42 "FAXSTRING string " 4.3.42. @{B}FAXSTRING string@{UB} Tells TrapDoor what string the modem returns when it connects to a fax machine or another fax modem using the fax protocol. Some fax modems, for example, return the string "FAX" as in "CONNECT FAX"; others return "+FCON". You must setup the correct @{"FAXSTRING" link 4.3.42} for your modem when you use the @{"FAXCOMMAND" link 4.3.41} keyword. @{"Examples" link 5}: FaxString "FAX" FaxString "+FCON" @ENDNODE 4.3.42 @NODE 4.3.43 "FKEY function-key-assignment " 4.3.43. @{B}FKEY function-key-assignment@{UB} Assign a configuration command string to a function key. The keyword must be followed by a single string, starting with the number of the function key (F1=1, F2=2,...; Shift-F1=11, Shift-F2=12,...), followed by a colon (":"), followed by the assignment. If you wish to include spaces in the assignment, the argument must be enclosed in double-quotes; to include quotes within the quoted string, use the backslash ("\\") as an escape character. @{"Examples" link 5}: FKey "1:Emsi" FKey "11:NoEmsi" FKey "5:Call Boss" FKey "6:Run CE" FKey "7:Run \\"Execute Scripts:Import\\"" FKey "8:Run \\"TrapPoll +r\\"" @ENDNODE 4.3.43 @NODE 4.3.44 "(NO)FLOATLOCK " 4.3.44. @{B}(NO)FLOATLOCK@{UB} HST modems support a mode (&B2) in which they will drop the DTE baud rate (the baud rate used between modem and computer) when a connection is made without error-correction, but will keep the DTE baud rate locked on a connection with error-correction. @{"FLOATLOCK" link 4.3.44} allows you to use this mode. If you have @{"FLOATLOCK" link 4.3.44} enabled, whenever TrapDoor reads a CONNECT xxx string from the modem, it will try to find the @{"ARQSTRING" link 4.3.11} string in the CONNECT result. If it finds it, it will keep the baudrate locked, otherwise it will switch to the baudrate found in the CONNECT string. You have to have @{"LOCK" link 4.3.55} enabled when you wish to use @{"FLOATLOCK" link 4.3.44}. To turn off @{"FLOATLOCK" link 4.3.44} mode, use @{"NOFLOATLOCK" link 4.3.44} or omit the statement completely; it defaults to @{"NOFLOATLOCK" link 4.3.44}. NOTE: we do not recommend using @{"FLOATLOCK" link 4.3.44}. Instead, set your HST to &B1 and S15=8. This can provide slightly higher troughput on non-ARQ connections than using &B2 and @{"FLOATLOCK" link 4.3.44}. @{"Examples" link 5}: FloatLock NoFloatLock @ENDNODE 4.3.44 @NODE 4.3.45 "(NO)FORBID... " 4.3.45. @{B}(NO)FORBID...@{UB} Select what type of mail/files you do _not_ want to be sent. In an @{"EMSI" link 4.3.38} handshake, TrapDoor will ask the remote system to not send these files (the other end may override this with the @{"NOALLOWREFUSING" link 4.3.9} switch): - FORBIDXMAIL Compressed mail and file attaches - FORBIDFREQ File requests - FORBIDALL All of the above The default is to not forbid anything. @{"Examples" link 5}: ForbidXMail NoForbidFreq @ENDNODE 4.3.45 @NODE 4.3.46 "FREQUEST command-string " 4.3.46. @{B}FREQUEST command-string@{UB} Sets the command to be executed as a file-request server on received file requests from remote systems. There may be embedded %-commands, these are described in the chapter "@{"Embedded Percent-Commands" link 4.1}". The called command should then read the remote's request from the %i file, perform any action that it wants to do, and write a list of files that it wishes to send to the other side (including directory path) to the %o file. To turn off the file-request capability, use @{"FREQUEST" link 4.3.46} "". This is also the default. Please note that the answering of file-requests is disabled in unregistered versions of TrapDoor. The external file-request server will not be called. @{"Examples" link 5}: FRequest "rx frequest %i,%o,%l" FRequest "" @ENDNODE 4.3.46 @NODE 4.3.47 "HELP " 4.3.47. @{B}HELP@{UB} Output some descriptive text, explaining the usage and commandline syntax of TrapDoor. @{"Example" link 5}: Help @ENDNODE 4.3.47 @NODE 4.3.48 "(NO)IMMEDIATE " 4.3.48. @{B}(NO)IMMEDIATE@{UB} If you specify @{"IMMEDIATE" link 4.3.48}, TrapDoor will not care about modem commands, dialing, resetting the modem etc, but will go directly and immediately to the session handshake (@{"EMSI" link 4.3.38}, YooHoo or TSynch). So, if you have two Amigas connected via a serial cable, you can use TrapDoor to transfer files between them. On the first machine, start TrapDoor with TrapDoor @{"ANSWER" link 4.3.10} @{"IMMEDIATE" link 4.3.48} @{"NODSR" link 4.3.37} TrapDoor will start up, open the serial device, ignore the @{"DSR" link 4.3.37} line (which has not been set high at that time because the other computer has not opened its serial device yet) and wait for approximately 30 seconds for a session handshake. Now, on the other computer, run TrapDoor @{"CALL" link 4.3.24} @{"BOSS" link 4.3.23} @{"IMMEDIATE" link 4.3.48} TrapDoor will open its windows, and within a few seconds you should see the banner line of the other system appear in the status window. TrapDoor will then go on as usual with the session handshake and the actual file transfers. @{"IMMEDIATE" link 4.3.48} has another use: if you send @{"IMMEDIATE" link 4.3.48} to a TrapDoor which is waiting in answer mode, it will react just as if it had just detected a RING from the modem. TrapDoor will send out the @{"MODEMANSWER" link 4.3.65} command and take an incoming call. This keyword defaults to @{"NOIMMEDIATE" link 4.3.48}. @{"Example" link 5}: Immediate @ENDNODE 4.3.48 @NODE 4.3.49 "INBOUND inbound-mail-directory " 4.3.49. @{B}INBOUND inbound-mail-directory@{UB} This should point to the directory where incoming files will be put. The default is "Mail:Inbound". Make sure that the TrapDoor inbound directory is the same as the one for your mail tosser, or your attempts to import mail will fail miserably. Additionally, TrapDoor uses this directory for temporary files during receiving and for files that store information about aborted/interrupted file transfers, so that receiving these files can be resumed in the next ZedZap session. For more information, see the chapter "Inbound Directory". @{"Examples" link 5}: Inbound "Mail:Inbound" @ENDNODE 4.3.49 @NODE 4.3.50 "(NO)INTERLACE " 4.3.50. @{B}(NO)INTERLACE@{UB} Specify whether TrapDoor should open its screen in the interlace mode or not. It defaults to @{"NOINTERLACE" link 4.3.50}. @{"Examples" link 5}: NoInterlace Interlace @ENDNODE 4.3.50 @NODE 4.3.51 "(NO)KEEPALL " 4.3.51. @{B}(NO)KEEPALL@{UB} @ENDNODE 4.3.51 @NODE 4.3.52 "(NO)KEEPXMAIL " 4.3.52. @{B}(NO)KEEPXMAIL@{UB} These two keywords disallow (allow) the sending of files and mail to the other system on incoming calls. @{"KEEPALL" link 4.3.51} suppresses the sending of all kinds of mail and files, whereas @{"KEEPXMAIL" link 4.3.52} will allow the sending of mail packets (.PKT files), but no compressed mail or files will be sent. Please note the difference between the FORBID.. and the KEEP.. keywords. FORBID will ask the other system in the @{"EMSI" link 4.3.38} handshake not to send certain kinds of files, whereas KEEP will turn off the sending of these types of files on your own system, and only on incoming calls. Even with KEEP in effect, your system will deliver all mail and files on outgoing calls. Per default, everything will be send and nothing kept. Both keywords default to NO. @{"Examples" link 5}: KeepAll NoKeepXMail @ENDNODE 4.3.52 @NODE 4.3.53 "(NO)KIWIPULSE " 4.3.53. @{B}(NO)KIWIPULSE@{UB} Applies a special number translation to the dial string before sending it to the modem. Special feature for kiwi people with vanilla modems. Defaults to @{"NOKIWIPULSE" link 4.3.53}. @{"Examples" link 5}: NoKiwiPulse KiwiPulse @ENDNODE 4.3.53 @NODE 4.3.54 "(NO)LISTEN " 4.3.54. @{B}(NO)LISTEN@{UB} @{"LISTEN" link 4.3.54} is a synonym for @{"NOUNLISTEN" link 4.3.117} and @{"NOLISTEN" link 4.3.54} is a synonym for @{"UNLISTEN" link 4.3.117}. Please see the description of the (NO)@{"UNLISTEN" link 4.3.117} command for a detailed explanation of these keywords. @ENDNODE 4.3.54 @NODE 4.3.55 "(NO)LOCK " 4.3.55. @{B}(NO)LOCK@{UB} Lock (do not lock) the baudrate. If the baudrate is locked, and TrapDoor receives a "CONNECT XXXX" message from the modem, TrapDoor will @{B}not@{UB} adjust the baud rate to XXXX, but continue to operate at the rate specified with the @{"BAUD" link 4.3.16} keyword. Use this for buffered modems that convert the baud rates internally (for example, HST). Be sure to also configure the modem for a locked baudrate in that case (i.e. on HSTs, use &B1). This keyword defaults to @{"NOLOCK" link 4.3.55}. @{"Examples" link 5}: NoLock Lock @ENDNODE 4.3.55 @NODE 4.3.56 "LOG level:text " 4.3.56. @{B}LOG level:text@{UB} Upon receipt of this @{"ARexx" link 3.14} command, TrapDoor will write the specified text with the specified log level to the log file. (+) @{"ARexx" link 3.14} only command (@) asynchronous execution possible !!! not yet implemented !!! @{"Example" link 5}: Log "3:Filerequest TRAPDOOR -> files:TD_1_50.LZH" @ENDNODE 4.3.56 @NODE 4.3.57 "LOGCALLERID filename " 4.3.57. @{B}LOGCALLERID filename@{UB} When @{"LOGCALLERID" link 4.3.57} is in use, TrapDoor will log all strings that the modem sends between the first and the second RING into the given file. External software can then be used to parse the data in that file and act upon it. This allows BBS software to receive CallerID information, for example. Since the CallerID data is sent between the first and second RING, you will need to set at least @{"RINGS" link 4.3.86} 2. To switch off CallerID logging, specify an empty string for the filename (""). This is also the default. @{"Examples" link 5}: LogCallerID Mail:CallerID.log LogCallerID "" @ENDNODE 4.3.57 @NODE 4.3.58 "LOGFILE filename " 4.3.58. @{B}LOGFILE filename@{UB} Sets the name of the logfile. The default is "Mail:TrapDoor.Log". @{"Example" link 5}: Logfile "Mail:TrapDoor.Log" @ENDNODE 4.3.58 @NODE 4.3.59 "LOGLEVEL group:level " 4.3.59. @{B}LOGLEVEL group:level@{UB} Sets the amount of logging information to be put into the logfile. There are ten logging groups, each of which deals with a different part of messages (such as modem, outbound, session protection, file transfers, general messages, external messages etc.). Each group maintains its own loglevel, which ranges from 0 to 7. A list of all log messages together with their groups and levels can be found in the file "LogMsgs.doc". The groups: 0 Debugger ? debugging messages, internal errors 1 Link - line is too bad, baudrate too low 2 Transfer | receiving xyz.txt, cps rates 3 System ! deleting file xyz.txt, user break, out of mem 4 Modem ~ NO CARRIER, BUSY, RING, VOICE 5 Session = Begin of session, picking up mail, session aborted, giving mail to, session connect time, cost 6 @{"Security" link 3.7} * bad password, unlisted system, node is undialable 7 Outside x spawning dialer, executing aftersession, spawning bbs 8 Information : sysop, name, aka, place, flags, using, trxid 9 Scheduler + waiting for call, incoming call detected, calling node The levels: 0 Silent minimum logging 1 Terse terse logging 2 Discreet normal logging 3 Verbose detailed logging 4 Talkative extensive logging 5 Excessive very much logging 6 Annoying even more logging 7 Monologue maximum logging Two (Discreet) seems to be a rather nice logging level and is the default for all groups. You might want to turn on more detailed logging in the @{"Security" link 3.7} and Information groups. @{"Examples" link 5}: Loglevel 5:3 Loglevel 4:4 @ENDNODE 4.3.59 @NODE 4.3.60 "LOGWINDOW window-specification " 4.3.60. @{B}LOGWINDOW window-specification@{UB} Use this keyword to change the position and size of the log window that TrapDoor opens. The window specification looks rather similar to a normal AmigaDOS CON:, RAW: or NEWCON: specification, but omit the device name and the window name. The correct format is: LeftEdge/TopEdge/Width/Height i.e. something like 0/20/640/150 @{"Example" link 5}: LogWindow 0/20/640/150 @ENDNODE 4.3.60 @NODE 4.3.61 "(NO)MAXBAUD " 4.3.61. @{B}(NO)MAXBAUD@{UB} If turned on, the @{"MINBAUD" link 4.3.64} parameter will automatically be set to the baudrate of the called system (found in the nodelist) or the own baudrate (set with @{"BAUD" link 4.3.16}) on outgoing calls, whichever is lower. The default is @{"NOMAXBAUD" link 4.3.61}. What is this good for? Let us assume you have a 2400 baud modem, and you wish to call a node that is also capable of 2400 baud. His nodelist entry also says he can do 2400 baud. Now, if you call him, sometimes, when line noise appears just when the modems negotiate the connect speed, this may cause a connection only at 1200 baud, or even worse, at 300 baud. If you have @{"MAXBAUD" link 4.3.61} enable, TrapDoor will immediately hang up in such a case. On the other hand, if you are using an HST modem, and you are calling a system with a Trailblazer PEP modem, you might have problems when you use @{"MAXBAUD" link 4.3.61}: if the nodelist entry for the PEP modem specifies 9600 baud, TrapDoor will hang up if the connect speed is lower than 9600 baud. But: HST modems and PEP modems use a different high speed protocol and can only talk at 2400 baud to each other. So, TrapDoor will hang up every time you call such a system. You have to decide whether the usage of @{"MAXBAUD" link 4.3.61} is appropriate for you or not. You can also set up custom configuration entries to select specific @{"MINBAUD" link 4.3.64} values for selected nodes. See the chapter "@{"Custom Configuration Entries" link 3.5}" for more details. Note: setconfig @{"NOMAXBAUD" link 4.3.61} won't work. See the chapter "@{"Bugs? Poof! They're all features!" link 8}". @{"Examples" link 5}: NoMaxBaud MaxBaud @ENDNODE 4.3.61 @NODE 4.3.62 "MAXLOGLINES number " 4.3.62. @{B}MAXLOGLINES number@{UB} This allows you to specify the number of log-lines that will be buffered, i.e. after so many lines have been written to the logfile, the file will be flushed (closed and reopened, in order to force all the data to disk). If you set this to 0, the behaviour is as in TrapDoor 1.80 and earlier (and this is also the default): the logfile will be flushed after every single line. @{"Example" link 5}: MaxLogLines 5 @ENDNODE 4.3.62 @NODE 4.3.63 "MAXLOGSECS seconds " 4.3.63. @{B}MAXLOGSECS seconds@{UB} This specifies the number of seconds that may expire before TrapDoor will flush the logfile. It will actually flush it when the next line is written to the logfile. If you set this to 0, the behaviour is as in TrapDoor 1.80 and earlier (and this is also the default): the logfile will be flushed after every single line. @{"Example" link 5}: MaxLogSecs 7 @ENDNODE 4.3.63 @NODE 4.3.64 "MINBAUD baudrate " 4.3.64. @{B}MINBAUD baudrate@{UB} Minimal baudrate to establish a connection. Connections at baud rates below this limit will not be allowed, no matter if incoming or outgoing. TrapDoor will hang up immediately if the baud rate is lower than the value specified. Defaults to 300. @{"Example" link 5}: MinBaud 1200 @ENDNODE 4.3.64 @NODE 4.3.65 "MODEMANSWER modem-answer-string " 4.3.65. @{B}MODEMANSWER modem-answer-string@{UB} Modem answer string like "AT~A|". For special characters like "~", "^" and "|" that are allowed in the string, see chapter "@{"Modem Commands" link 4.2}". The total length of the string may not exceed 100 characters. This string is sent to the modem whenever TrapDoor detects a "RING" and wants to answer the phone. The default is @{"MODEMANSWER" link 4.3.65} "~~AT~A|~". @{"Example" link 5}: ModemAnswer "ATA|" @ENDNODE 4.3.65 @NODE 4.3.66 "MODEMDIALPRE modem-pre-dial-string " 4.3.66. @{B}MODEMDIALPRE modem-pre-dial-string@{UB} Modem dial string such as "AT~DP" or "AT~DT". For special characters like "~", "^" or "|" that are allowed in the string, see chapter "@{"Modem Commands" link 4.2}". The total length of the string is limited to 100 characters. This string is sent to the modem whenever TrapDoor wants to dial a number. After sending this string, TrapDoor will send the telephone number to dial, followed by the @{"MODEMDIALPOST" link 4.3.67} string. The default is @{"MODEMDIALPRE" link 4.3.66} "~~AT~DP". @{"Example" link 5}: ModemDialPre "ATDP" @ENDNODE 4.3.66 @NODE 4.3.67 "MODEMDIALPOST modem-post-dial-string " 4.3.67. @{B}MODEMDIALPOST modem-post-dial-string@{UB} Final part of the modem dial string such as "|". For special characters like "~", "^" and "|" that are allowed in the string, see chapter "@{"Modem Commands" link 4.2}". The total length of the string is limited to 20 characters. This string is sent to the modem after the telephone number, when TrapDoor wants to dial a number. Also see the description of @{"MODEMDIALPRE" link 4.3.66}. The default is @{"MODEMDIALPOST" link 4.3.67} "|~". @{"Example" link 5}: ModemDialPost "|" @ENDNODE 4.3.67 @NODE 4.3.68 "MODEMHANGUP modem-hangup-string " 4.3.68. @{B}MODEMHANGUP modem-hangup-string@{UB} This string will be sent to the modem whenever TrapDoor wants to hang up the line. There are many methods to accomplish this, including the strange "~~~+++~~~ATH|" method. We do not recommend this. If you have configured your modem according to the descriptions in the chapter "@{"The Modem" link 2.4}", it should hang up as soon as DTR is lowered. So, the recommended hangup string is "|^|". This is also the default. For special characters like "~", "^" and "|" that are allowed in the string, see chapter "@{"Modem Commands" link 4.2}". The total length of the string is limited to 40 characters. @{"Example" link 5}: ModemHangup "|^|" @ENDNODE 4.3.68 @NODE 4.3.69 "MODEMINIT modem-init-string " 4.3.69. @{B}MODEMINIT modem-init-string@{UB} This string will be sent to the modem during the initialization phase of TrapDoor. Things like "AT~S7=20|" can be done here. For special characters like "~", "^" and "|" that are allowed in the string, see chapter "@{"Modem Commands" link 4.2}". The total length of the string is limited to 160 characters. TrapDoor will also check if it gets any response from the modem after sending this init string. The modem should at least send something like "OK". In fact, any carriage-return terminated string from the modem will suffice. If TrapDoor is unable to detect a response from the modem, it will report "Initializing modem failed" and exit. The default is @{"MODEMINIT" link 4.3.69} "~~AT~Z|~". @{"Example" link 5}: ModemInit "ATZ|" @ENDNODE 4.3.69 @NODE 4.3.70 "MODEMRESETINTERVAL minutes " 4.3.70. @{B}MODEMRESETINTERVAL minutes@{UB} Per default, TrapDoor resets the modem by sending the @{"MODEMINIT" link 4.3.69} command every 15 minutes if it has nothing else to do. Using this switch, you can set the time in minutes between automatic modem resets. Specifying a very large number (-1 for example), will yield no automatic resets. @{"Example" link 5}: ModemResetInterval 15 @ENDNODE 4.3.70 @NODE 4.3.71 "NAME board's name " 4.3.71. @{B}NAME board's name@{UB} Name of this system -- to be sent to the other system during the beginning of a mail session. The length of the string is limited to 60 characters. @{"Example" link 5}: Name "The Mad House -- TrapDoor Development" @ENDNODE 4.3.71 @NODE 4.3.72 "NODE zone:net/node.point " 4.3.72. @{B}NODE zone:net/node.point@{UB} Sets your own @{"FidoNet" link 3.1} address. For points: If your boss uses a mailer that is not point smart, be sure to insert your private pointnet number here and not your full address. In this case, you should not use your complete four dimensional address (2:310/3.24), but rather the fake pointnet addressing method "2:3000/24". FrontDoor, D'Bridge and newer versions of BinkleyTerm on the other hand do already support the four dimensional addressing method. Use your full address then. For nodes: Just set this to your own address. @{"Examples" link 5}: Node 2:310/3.14 Node 2:310/6 @ENDNODE 4.3.72 @NODE 4.3.73 "NODELIST nodelist-directory " 4.3.73. @{B}NODELIST nodelist-directory@{UB} Set this to the directory where you keep your nodelist files. TrapDoor understands only nodelist files generated by its own nodelist processor, @{B}TrapList.@{UB} TrapDoor needs the library "traplist.library" to access the nodelist, so make sure it is in your LIBS: directory. To disable the nodelist support in TrapDoor, use @{"NODELIST" link 4.3.73} "". This is also the default. @{"Examples" link 5}: @{"Nodelist" link 3.3} "Mail:@{"Nodelist" link 3.3}" @{"Nodelist" link 3.3} "" @ENDNODE 4.3.73 @NODE 4.3.74 "OUTBOUND outbound-mail-directory " 4.3.74. @{B}OUTBOUND outbound-mail-directory@{UB} This should point to the directory where outgoing files are kept. It should contain all the necessary #?.REQ, #?.FLO, #?.HLO and #?.CLO files and the associated mail bundles. TrapDoor will automatically maintain and delete these files as they get sent out. The default is "Mail:Outbound". For more information, see chapter "Outbound directory". @{"Example" link 5}: OutBound "Mail:Outbound" @ENDNODE 4.3.74 @NODE 4.3.75 "PASSWORD password " 4.3.75. @{B}PASSWORD password@{UB} Specifies the password to be used for mail sessions. The default is no password. On an outgoing call, if your password does not match the password that the other system has set up for you, you will be disconnected at the session handshake. On incoming calls, if the password of the remote system does not match the password you specified here, this will be detected during the session handshake, recorded in the log file and the caller/callee will politely be shown the way out (i.e. disconnected). If @{"Nodelist" link 3.3} support has been enabled by setting the @{"NODELIST" link 4.3.73} parameter, passwords will be fetched from there, unless the other system is not found in the nodelist. @{"Example" link 5}: Password "secret" @ENDNODE 4.3.75 @NODE 4.3.76 "PICKUP what " 4.3.76. @{B}PICKUP what@{UB} Select what mail and files to pickup (receive) from the remote system. These "Pickup Preferences" will only work if an @{"EMSI" link 4.3.38} handshake was used at the beginning of the session. There are three possible pickup values. The default is @{"PICKUP" link 4.3.76} ALL. - ALL Pick up mail and files for all of my addresses (primary address + AKAs) - PRIMARY Pick up mail and files for the primary address only - NONE Do not pick up mail or files at all @{"Examples" link 5}: Pickup Primary Pickup All Pickup None @ENDNODE 4.3.76 @NODE 4.3.77 "PUBSCREENNAME name " 4.3.77. @{B}PUBSCREENNAME name@{UB} If you use @{"SCREENMODE" link 4.3.89} PUBLIC, this keyword allows you to specify the name of the public screen that TrapDoor should use. If a public screen with this name already exists, TrapDoor will open its windows there. If it does not exist, TrapDoor will open one. Expert Notice: when TrapDoor opens the public screen, it will AllocVec() a buffer for the screen title. If any other program than TrapDoor closes the public screen, a few bytes of memory will be lost. If you are confused now and don't quite understand what I mean, just ignore it. :-) @{"PUBSCREENNAME" link 4.3.77} defaults to "TrapDoor". @{"Example" link 5}: PubScreenName "Hugo" @ENDNODE 4.3.77 @NODE 4.3.78 "QUIT " 4.3.78. @{B}QUIT@{UB} This tells TrapDoor to exit (when waiting in answer mode) and is exactly the same as "@{"ABORT" link 4.3.2} F" or pressing Alt-X or Alt-Q. (+) @{"ARexx" link 3.14} only command (@) asynchronous execution possible @{"Examples" link 5}: Quit @Quit @ENDNODE 4.3.78 @NODE 4.3.79 "(NO)QUIET " 4.3.79. @{B}(NO)QUIET@{UB} If enabled, TrapDoor will run quietly in the background without opening any windows, screens etc. The logfile will still be written and you can still send @{"ARexx" link 3.14} commands to a TrapDoor running in @{"QUIET" link 4.3.79} mode. The default is @{"NOQUIET" link 4.3.79}. @{"Examples" link 5}: NoQuiet Quiet @ENDNODE 4.3.79 @NODE 4.3.80 "REDIALDELAY seconds " 4.3.80. @{B}REDIALDELAY seconds@{UB} This specifies the amount of time TrapDoor spends idling between calls to a system. Note that TrapDoor will not accept incoming calls while in "redial" state, so this option is only suited for points and will only work if you start TrapDoor with "TrapDoor Call ..." (i.e. you do not start it in answer mode). The default is 123 seconds. @{"Example" link 5}: RedialDelay 120 @ENDNODE 4.3.80 @NODE 4.3.81 "RESET " 4.3.81. @{B}RESET@{UB} This forces TrapDoor to reset/reinitialize the modem. (+) @{"ARexx" link 3.14} only command @{"Example" link 5}: Reset @ENDNODE 4.3.81 @NODE 4.3.82 "RETRIES count " 4.3.82. @{B}RETRIES count@{UB} When calling a system, this instructs TrapDoor not to exit on a failed call (eg. line is busy), but to try it thus often again. Between the calls, TrapDoor will spend @{"REDIALDELAY" link 4.3.80} seconds waiting. Note that this automatic redialing does _not_ apply if you place the call from within @{"ANSWER" link 4.3.10} mode. You have to start TrapDoor directly with the @{"CALL" link 4.3.24} parameter. The default is to not retry. @{"Example" link 5}: Retries 5 @ENDNODE 4.3.82 @NODE 4.3.83 "REXXNAME portname " 4.3.83. @{B}REXXNAME portname@{UB} Using this configuration keyword, you can select the @{"ARexx" link 3.14} port name (the "host address" in @{"ARexx" link 3.14} terminology) of TrapDoor. If you run TrapDoor on multiple lines, be sure to set up a different @{"REXXNAME" link 4.3.83} for every invocation. TrapDoor will not start up if the port name is already in use. The default rexx port name is "TrapDoor". @{"Example" link 5}: RexxName "TrapDoor" @ENDNODE 4.3.83 @NODE 4.3.84 "RINGCOMMAND commandline " 4.3.84. @{B}RINGCOMMAND commandline@{UB} This command will be spawned whenever TrapDoor detects a "RING" from the modem. When it returns, TrapDoor will answer the call (if @{"RINGS" link 4.3.86} "RING"s have passed). You can use it to trigger some sound effects, if you like. The default is @{"RINGCOMMAND" link 4.3.84} "", i.e. to not spawn any command. @{"Example" link 5}: RingCommand "rx \\"address upd play 12\\"" @ENDNODE 4.3.84 @NODE 4.3.85 "RINGINGS number " 4.3.85. @{B}RINGINGS number@{UB} This is the number of times TrapDoor will allow another system to keep the phone "ringing" on an outgoing call. TrapDoor increments a counter every time it receives the string "RINGING" or "RRING" from your modem. When the counter exceeds the number specified with @{"RINGINGS" link 4.3.85}, TrapDoor will hang up, report the call as "NO @{"ANSWER" link 4.3.10}", and account it as an unanswered call (similar to "NO CARRIER"). Per default, TrapDoor will never abort a call because of the @{"RINGINGS" link 4.3.85} count. Please note that not all modems support this feature. @{"Example" link 5}: Ringings 3 @ENDNODE 4.3.85 @NODE 4.3.86 "RINGS number " 4.3.86. @{B}RINGS number@{UB} Number of rings to wait before answering an incoming call. To turn off the answering feature, you can set this to any high-enough value (@{"RINGS" link 4.3.86} 5000 will probably never answer the phone). This keyword defaults to @{"RINGS" link 4.3.86} 1. @{"Example" link 5}: Rings 1 @ENDNODE 4.3.86 @NODE 4.3.87 "RUN command-string " 4.3.87. @{B}RUN command-string@{UB} Causes TrapDoor to execute the given command asynchronously. If the command includes spaces, it must be enclosed in double-quotes; to include quotes within the quoted string, use the backslash ("\\") as an escape character. Embedded Percent Commands can also be used here. TrapDoor will not wait until the command returns, but merely continue to process @{"ARexx" link 3.14} messages and answer incoming calls. This is the big difference to the @{"SPAWN" link 4.3.102} keyword. In fact, "Run XXX" is exactly the same as "@{"SPAWN" link 4.3.102} \\"Run XXX\\"". (+) @{"ARexx" link 3.14} only command @{"Examples" link 5}: Run "ed mail:TrapDoor.cfg" Run "echo \\"This command was started from TrapDoor.\\"" @ENDNODE 4.3.87 @NODE 4.3.88 "SCLEAR " 4.3.88. @{B}SCLEAR@{UB} This command will clear the serial (receive) buffer. (+) @{"ARexx" link 3.14} only command @{"Example" link 5}: SClear @ENDNODE 4.3.88 @NODE 4.3.89 "SCREENMODE mode " 4.3.89. @{B}SCREENMODE mode@{UB} This allows you to specify the screen where TrapDoor opens its windows. There are five possible modes; the default is @{"SCREENMODE" link 4.3.89} WORKBENCH. WORKBENCH -- TrapDoor will open its windows on the workbench screen. CUSTOM -- TrapDoor will open its own screen and place the windows there. TRAPDOOR -- Similar to CUSTOMSCREEN, TrapDoor will open its windows on its own screen. However, if you have multiple TrapDoors running at the same time, all invocations of TrapDoor will share the same "TrapDoor" screen. The screen will only close when the last copy of TrapDoor quits running. PUBLIC -- Similar to TRAPDOOR, but will use a Kickstart 2.04 Public Screen instead of the proprietary and undocumented method that @{"SCREENMODE" link 4.3.89} TRAPDOOR uses. Thus, other programs can open their windows on the public TrapDoor screen, too. Or you can also make TrapDoor open its windows on a foreign public screen if you use @{"SCREENMODE" link 4.3.89} PUBLIC in conjunction with @{"PUBSCREENNAME" link 4.3.77} (to define the name of the public screen that TrapDoor should use). ACTIVE -- TrapDoor will use the screen with the currently active window and open its windows there. Note that this is rather dangerous as TrapDoor cannot control when the other program will close the screen. If this happens, TrapDoor will try to write to a screen that no longer exists and this will in most cases immediately crash the machine. In spite of these restrictions, @{"SCREENMODE" link 4.3.89} ACTIVE looks very nice in conjunction with Chameleon, a wonderful message editor written by Jürgen Hermann. Try sticking the following command into your 'CE.CFG' file: External CustomScreen "Call Boss" \\ "TrapDoor call boss screenmode active" Now start Chameleon, pull down the "External" menu, select this item and see for yourself ... @{"Examples" link 5}: ScreenMode Workbench ScreenMode TrapDoor @ENDNODE 4.3.89 @NODE 4.3.90 "SCREENTOBACK " 4.3.90. @{B}SCREENTOBACK@{UB} Will cause the TrapDoor screen to move behind all other screens. (+) @{"ARexx" link 3.14} only command (@) asynchronous execution possible @{"Example" link 5}: ScreenToFront @ENDNODE 4.3.90 @NODE 4.3.91 "SCREENTOFRONT " 4.3.91. @{B}SCREENTOFRONT@{UB} Will cause the TrapDoor screen to move to the front of all other screens. (+) @{"ARexx" link 3.14} only command (@) asynchronous execution possible @{"Example" link 5}: ScreenToFront @ENDNODE 4.3.91 @NODE 4.3.92 "SERIALBUFSIZE size-in-bytes " 4.3.92. @{B}SERIALBUFSIZE size-in-bytes@{UB} This keyword can be used to set the serial receive buffer. It defaults to 8192 bytes. @{"Example" link 5}: SerialBufSize 4096 @ENDNODE 4.3.92 @NODE 4.3.93 "SERIALFLAGS serial-flags " 4.3.93. @{B}SERIALFLAGS serial-flags@{UB} If you use some other device than "serial.device", you might need to change this, too. Consult the documentation that came with your other device or use the default of zero. @{"Example" link 5}: SerialFlags 0 @ENDNODE 4.3.93 @NODE 4.3.94 "SERIALNAME serial-device-name " 4.3.94. @{B}SERIALNAME serial-device-name@{UB} If you happen to have a modem connected to some other device than the standard Amiga "serial.device", you can use this parameter to set up the correct device name. Usually, the default of "serial.device" will just be about perfect. For Supra 2400zi modems, use @{"SERIALNAME" link 4.3.94} "modem0.device". @{"Example" link 5}: SerialName "serial.device" @ENDNODE 4.3.94 @NODE 4.3.95 "SERIALUNIT serial-unit-number " 4.3.95. @{B}SERIALUNIT serial-unit-number@{UB} If your modem is connected to some other unit number than zero (on the device you set with @{"SERIALNAME" link 4.3.94}), change this appropriately. @{"Example" link 5}: SerialUnit 0 @ENDNODE 4.3.95 @NODE 4.3.96 "(NO)SHARED " 4.3.96. @{B}(NO)SHARED@{UB} (Don't) Open the serial device in shared mode. If you are running TrapDoor in conjunction with a BBS program or similar, you need to switch the serial device to @{"SHARED" link 4.3.96} mode, so that both programs can have it open at the same time. The default is @{"NOSHARED" link 4.3.96}. @{"Examples" link 5}: NoShared Shared @ENDNODE 4.3.96 @NODE 4.3.97 "(NO)SHOWREXX " 4.3.97. @{B}(NO)SHOWREXX@{UB} In @{"SHOWREXX" link 4.3.97} mode, TrapDoor will display all @{"ARexx" link 3.14} commands that it processes in the status window. The default is @{"NOSHOWREXX" link 4.3.97}. You can toggle showrexx mode from the keyboard using Alt-S. @{"Examples" link 5}: NoShowRexx ShowRexx @ENDNODE 4.3.97 @NODE 4.3.98 "SLINE " 4.3.98. @{B}SLINE@{UB} This command will receive one line of text from the serial port and return it in the @{"ARexx" link 3.14} RESULT variable. The timeout specified with @{"STIMEOUT" link 4.3.106} will be used. (+) @{"ARexx" link 3.14} only command @{"Example" link 5}: SLine @ENDNODE 4.3.98 @NODE 4.3.99 "SLOWMODEM modem-command-delay " 4.3.99. @{B}SLOWMODEM modem-command-delay@{UB} Some modems won't understand incoming data at full speed while in command mode. Others take some time after a reset (ATZ or DTR dropped) until they will react to incoming commands again. If your modem doesn't seem to understand the commands TrapDoor is trying to send, feel free to change (increase) this parameter. Also see chapter "@{"The Modem" link 2.4}" for some suggested values. @{"SLOWMODEM" link 4.3.99} defaults to 10. @{"SLOWMODEM" link 4.3.99} changes a number of timings in TrapDoor, the most important being: (a) the time that TrapDoor waits between lowering and raising of DTR when it tries to reset the modem or hang up, (b) the time that TrapDoor waits when it encounters a tilde ("~") character in a modem command string (@{"MODEMINIT" link 4.3.69}, MODEMDIAL, @{"MODEMANSWER" link 4.3.65}). @{"Example" link 5}: SlowModem 7 @ENDNODE 4.3.99 @NODE 4.3.100 "SMODEM modem-command " 4.3.100. @{B}SMODEM modem-command@{UB} This @{"ARexx" link 3.14}-only command will send a command to the modem. It is similar to @{"SWRITE" link 4.3.110}, but the specified string will be run through the modem command processor first, allowing the use of "~", "^" and "|" special characters. For more information about these characters, see chapter "@{"Modem Commands" link 4.2}". (+) @{"ARexx" link 3.14} only command @{"Example" link 5}: SModem "~~AT~H1|~~" @ENDNODE 4.3.100 @NODE 4.3.101 "(NO)SNIFFARQ " 4.3.101. @{B}(NO)SNIFFARQ@{UB} If you have a modem that will detect MNP, LAP-M, V42 and similar error-correction protocols, you can enable @{"SNIFFARQ" link 4.3.101}. With @{"SNIFFARQ" link 4.3.101}, TrapDoor will minimize session-startup delays. The default is @{"NOSNIFFARQ" link 4.3.101}. You should _not_ use @{"SNIFFARQ" link 4.3.101} with modems that have no error correction. You must specify the correct @{"ARQSTRING" link 4.3.11} for your modem if you use @{"SNIFFARQ" link 4.3.101}. @{"Examples" link 5}: NoSniffArq SniffArq @ENDNODE 4.3.101 @NODE 4.3.102 "SPAWN command-string " 4.3.102. @{B}SPAWN command-string@{UB} Causes TrapDoor to execute the given command. If the command includes spaces, it must be enclosed in double-quotes; to include quotes within the quoted string, use the backslash ("\\") as an escape character. Embedded Percent Commands can also be used here. TrapDoor will wait until the command returns. It will not execute any other @{"ARexx" link 3.14} commands, nor will it answer incoming calls while the command is executing. (+) @{"ARexx" link 3.14} only command @{"Examples" link 5}: Spawn "ed mail:TrapDoor.cfg" Spawn "echo \\"Spawned from TrapDoor!\\"" @ENDNODE 4.3.102 @NODE 4.3.103 "STARTSESSION " 4.3.103. @{B}STARTSESSION@{UB} When TrapDoor receives this command, it will immediately start waiting for a banner line from the remote system, then begin with the session handshake. This command is intended to be used in outdialing scripts as the final command, giving control to TrapDoor to begin a session. (+) @{"ARexx" link 3.14} only command @{"Example" link 5}: StartSession @ENDNODE 4.3.103 @NODE 4.3.104 "STATUS what " 4.3.104. @{B}STATUS what@{UB} Depending on the argument, this command will return various information about the state TrapDoor is in, the result of previous calls etc. The following status specifiers are recognized: C ... Returns the cost of the last call made. D ... Reports the result string of the dial (or call), such as BUSY, NO DIALTONE, CONNECT 2400. F ... Reports the number of files that have been sent and received during the last session, separated by a slash ('/'). N ... Reports the node number that the last session was had with. S ... Reports the serial status of TrapDoor, which indicates whether TrapDoor is currently waiting for a call, answering a call, making an outgoing call, waiting for an external program to return or whether it has the serial port closed. Valid return values are: IDLE: TrapDoor is idle, waiting for a call. OUTGOING: TrapDoor is making an outgoing call. INCOMING: TrapDoor is answering an incoming call. CLOSED: TrapDoor has closed its serial port; another program is using it. SPAWNING: TrapDoor is currently spawning an external program and waiting for it to return. U ... Reports the "deafness" status of TrapDoor. It will return either @{"UNLISTEN" link 4.3.117} or @{"LISTEN" link 4.3.54} depending on the current status of TrapDoor (set with (NO)@{"UNLISTEN" link 4.3.117}). X ... Queries the status of the last call. It returns an integer number, where: 0: everything okay 1: (internal) unused 2: protocol error (too many retries) 3: (internal) end-of-transmission, Telink complete 4: (internal) file skipped 5: user break (Ctrl-C or ESC) 6: carrier lost 7: disk i/o error 8: remote canceled transmission 9: internal program error 10: human caller (BBS user) detected 11: remote didn't answer 12: (internal) object in use, can't send 13: node not found in nodelist 14: accounting limit reached 15: node is undialable 16: no response from modem while dialing 17: baudrate too low 18: BUSY 19: VOICE 20: NO DIALTONE 21: NO CARRIER 22: RINGING limit (NO ANSWER) 23: RING (incoming call detected while dialing) 24: ERROR (+) @{"ARexx" link 3.14} only command (@) asynchronous execution possible @{"Examples" link 5}: Status D @Status S @ENDNODE 4.3.104 @NODE 4.3.105 "STATWINDOW window-specification " 4.3.105. @{B}STATWINDOW window-specification@{UB} Similar to @{"LOGWINDOW" link 4.3.60}, this changes the position and size of the status window. @{"Example" link 5}: StatWindow 30/155/580/37 @ENDNODE 4.3.105 @NODE 4.3.106 "STIMEOUT timeout " 4.3.106. @{B}STIMEOUT timeout@{UB} Sets the timeout, in seconds, for the @{"SWAIT" link 4.3.108} and @{"SLINE" link 4.3.98} commands. @{"Example" link 5}: STimeout 3 @ENDNODE 4.3.106 @NODE 4.3.107 "(NO)STRIPDASHES " 4.3.107. @{B}(NO)STRIPDASHES@{UB} A few modems do not allow dashes ("-") in dial strings. The Fidonet nodelist, however, contains dashes. Specifying @{"STRIPDASHES" link 4.3.107} will tell TrapDoor to remove all dashes from dial strings before sending them to the modem. @{"Example" link 5}: StripDashes @ENDNODE 4.3.107 @NODE 4.3.108 "SWAIT string " 4.3.108. @{B}SWAIT string@{UB} Waits until the given string is received on the serial line, or until the timeout set with @{"STIMEOUT" link 4.3.106} has expired. @{"Example" link 5}: SWait "login:" @ENDNODE 4.3.108 @NODE 4.3.109 "(NO)SWEPULSE " 4.3.109. @{B}(NO)SWEPULSE@{UB} Applies a special number translation to the dial string before sending it to the modem. Special feature for swedish people with non-swedish modems. The default is @{"NOSWEPULSE" link 4.3.109}. @{"Examples" link 5}: NoSwePulse SwePulse @ENDNODE 4.3.109 @NODE 4.3.110 "SWRITE string " 4.3.110. @{B}SWRITE string@{UB} Sends the given string to the modem. The string will be sent as given, without any modification. @{"Example" link 5}: SWrite "Mad Max" @ENDNODE 4.3.110 @NODE 4.3.111 "SYSOP sysop's-name " 4.3.111. @{B}SYSOP sysop's-name@{UB} Sysop's name, will be sent to the other system during session negotiation. The length of this string is limited to 20 characters in the YooHoo/WaZoo handshake and to 30 characters when using @{"EMSI" link 4.3.38}. @{"Example" link 5}: Sysop "Maximilian Hantsch" @ENDNODE 4.3.111 @NODE 4.3.112 "TASKPRI priority " 4.3.112. @{B}TASKPRI priority@{UB} Use this to select the AmigaDOS/Exec task priority of TrapDoor. Normal tasks operate at priority 0. It is often advisable to set the priority of TrapDoor to 1 or 2, so that mail sessions are not slowed down by other activity such as mail importing/exporting. If the keyword is not used, TrapDoor will run at the priority of the invoking process. @{"Example" link 5}: TaskPri 1 @ENDNODE 4.3.112 @NODE 4.3.113 "TESTFREQ " 4.3.113. @{B}TESTFREQ@{UB} To be able to test your file request server programs and scripts, call TrapDoor with "TrapDoor testfreq". This will cause TrapDoor to look for a TrapDoor.FReq file in the inbound directory and, if one is found, call the file request server (specified with the @{"FREQUEST" link 4.3.46} keyword). The result of the file request server should be a .RLO file in your outbound directory, which you can check to see whether everything works all right. Please note that the request file should be called "TrapDoor.FReq", or to be more exact, ".FReq". @{"Example" link 5}: TestFreq @ENDNODE 4.3.113 @NODE 4.3.114 "(NO)TIMESTAMP " 4.3.114. @{B}(NO)TIMESTAMP@{UB} If @{"TIMESTAMP" link 4.3.114} is switched on, TrapDoor will @{B}always@{UB} use timestamps for converting 4D echomail bundle names to 2D for sending. Note: this might be incompatible with some old Echomail tossers when they are switched to "check security" mode. If @{"NOTIMESTAMP" link 4.3.114} is in effect (the default), TrapDoor will try to use the standard hex net/node difference naming, unless: - either system has a point address. - the main addresses of the two systems are in different zones, but have the same net and node numbers. "Fidonet peculiarities? Don't worry, we got them all under control... ;-)" @{"Examples" link 5}: NoTimeStamp TimeStamp @ENDNODE 4.3.114 @NODE 4.3.115 "(NO)TRAPZAP " 4.3.115. @{B}(NO)TRAPZAP@{UB} Enable (disable) TrapZap mode. TrapZap is a slight variant of the DirectZap transfer protocol, which is a slight variant of ZedZap/Zmodem -- on large files, TrapZap is the fastest protocol TrapDoor has to offer. Like ZedZap and DirectZap, TrapZap will automatically switch block sizes depending on modem speed and quality of the line. It will also resume an interrupted transfer if possible. TrapZap also has an improved control flow to make error recovery easier and hopefully more successful in the session turnaround phase. TrapZap also keeps the upper/lowercase spelling of the names of files being transferred and has a slightly faster protocol startup time when receiving. TrapZap only works in @{"EMSI" link 4.3.38} mode and only if the other side also supports it. Also - like DirectZap - TrapZap only works on 8-bit transparent lines. You should disable it (use @{"NOTRAPZAP" link 4.3.115}) if you are working over a non-transparent line like a packet-switching network. The keyword defaults to @{"NOTRAPZAP" link 4.3.115}. @{"Examples" link 5}: NoTrapZap TrapZap @ENDNODE 4.3.115 @NODE 4.3.116 "TURNAROUND command-string " 4.3.116. @{B}TURNAROUND command-string@{UB} TrapDoor will execute the given commandline when the session "turnaround" is about to take place. Session turnaround is when the sender and the receiver change sides, and files are transferred in the other direction afterwards. Since TrapDoor waits for the external command to complete before continuing with the session, it should return quickly. The default is to not execute any external command in the turnaround phase. @{"Examples" link 5}: Turnaround "run Execute Scripts:TossMail" Turnaround "" @ENDNODE 4.3.116 @NODE 4.3.117 "(NO)(UN)LISTEN " 4.3.117. @{B}(NO)(UN)LISTEN@{UB} Per default, TrapDoor will be in the "listen" state and keep waiting for messages from the modem (RING etc.). If you send TrapDoor a @{"NOLISTEN" link 4.3.54} or @{"UNLISTEN" link 4.3.117} @{"ARexx" link 3.14} message, you will make it terminate all its serial I/O. It will still keep the serial device open, but not send any I/O requests to it. In this mode, TrapDoor will keep hanging around idle until you send it a @{"NOUNLISTEN" link 4.3.117} or @{"LISTEN" link 4.3.54} @{"ARexx" link 3.14} message. If you tell TrapDoor to make an outgoing call, it will do so, but return to its silent @{"UNLISTEN" link 4.3.117} state as soon as the call is over. Please note that @{"NOUNLISTEN" link 4.3.117} is a synonym for @{"LISTEN" link 4.3.54} and @{"NOLISTEN" link 4.3.54} is a synonym for @{"UNLISTEN" link 4.3.117}. @{"Examples" link 5}: UnListen NoUnListen Listen NoListen @ENDNODE 4.3.117 @NODE 4.3.118 "(NO)USESYSFONT " 4.3.118. @{B}(NO)USESYSFONT@{UB} If enabled, TrapDoor will use the system screen font (proportional) for the TrapDoor screen instead of the default monospaced (non-proportional) system font. It defaults to @{"NOUSESYSFONT" link 4.3.118}. @{"Examples" link 5}: UseSysFont NoUseSysFont @ENDNODE 4.3.118 @NODE 4.3.119 "(NO)USEUSERSHELL " 4.3.119. @{B}(NO)USEUSERSHELL@{UB} This command will select whether TrapDoor passes external commands (such as @{"FREQUEST" link 4.3.46}, @{"RINGCOMMAND" link 4.3.84}, @{"BBSCOMMAND" link 4.3.18}, TURNAROUND and the like) to the standard AmigaOS system shell or to a user-selectable "UserShell" (such as WShell for instance). It defaults to @{"NOUSEUSERSHELL" link 4.3.119}. @ENDNODE 4.3.119 @NODE 4.3.120 "VOICECOMMAND commandline " 4.3.120. @{B}VOICECOMMAND commandline@{UB} When TrapDoor detects a voice connect (it looks for @{"VOICESTRING" link 4.3.121} in messages from the modem), it will spawn this external program. Using this technique you can run your voice software to accept incoming voice calls while at the same time allowing ordinary modem callers to go to the bulletin board or to run a @{"FidoNet" link 3.1} session with your system. There may be embedded %-commands in the string; these are described in the chapter "@{"Embedded Percent-Commands" link 4.1}". This will also work on outgoing calls. You can use the embedded percent command "d" to tell your voice software if this is an outgoing or incoming call. @{"Example" link 5}: VoiceCommand "VoiceAnswer %d" @ENDNODE 4.3.120 @NODE 4.3.121 "VOICESTRING string " 4.3.121. @{B}VOICESTRING string@{UB} Tells TrapDoor what string the modem returns when it senses a voice connect. You must setup the correct @{"VOICESTRING" link 4.3.121} for your modem when you use the @{"VOICECOMMAND" link 4.3.120} keyword. @{"Example" link 5}: VoiceString "+VCON" @ENDNODE 4.3.121 @NODE 4.3.122 "(NO)WAZOO " 4.3.122. @{B}(NO)WAZOO@{UB} Enable (disable) WaZoo mode. With WaZoo disabled, TrapDoor will only attempt to connect using the FTS-0001 (Lotek) protocol or @{"EMSI" link 4.3.38} handshake. No YooHoo will be done. It defaults to @{"WAZOO" link 4.3.122}. @{"Examples" link 5}: NoWaZOO WaZOO @ENDNODE 4.3.122 @NODE 4.3.123 "(NO)WRAPLINES " 4.3.123. @{B}(NO)WRAPLINES@{UB} With WrapLines enabled, TrapDoor will try to wrap lines that are sent to the log window and continue them in the next line, if they are too long to be displayed on a single line. The logfile will be unaffected by the setting of this switch. Only the output in the window is reformatted. It defaults to @{"NOWRAPLINES" link 4.3.123}. @{"Examples" link 5}: WrapLines NoWrapLines @ENDNODE 4.3.123 @NODE 4.3.124 "VERSION " 4.3.124. @{B}VERSION@{UB} This @{"ARexx" link 3.14}-only command will return the version identifier of TrapDoor, e.g. "1.84". (+) @{"ARexx" link 3.14} only command (@) asynchronous execution possible @{"Example" link 5}: Version @ENDNODE 4.3.124 @NODE 4.3.125 "(NO)XMAIL " 4.3.125. @{B}(NO)XMAIL@{UB} Enable (disable) eXtended Mail, whatever that is. There is a flag in the @{"EMSI" link 4.3.38} handshake packet called "XMA". The @{"EMSI" link 4.3.38} documentation is very unclear about what it means. Anyway, you got the choice now :-) This keyword defaults to @{"XMAIL" link 4.3.125}, as this was the behaviour of TrapDoor 1.80. @{"Examples" link 5}: NoXMail XMail @ENDNODE 4.3.125 @NODE 4.3.126 "(NO)ZEDZAP " 4.3.126. @{B}(NO)ZEDZAP@{UB} Enable (disable) ZedZap mode. ZedZap is a slight variant of the ZModem transfer protocol -- on large files, this is one of the fastest protocols around. ZedZap will automatically switch block sizes depending on modem speed and quality of the line. It will also resume an interrupted transfer if possible. ZedZap only works in WaZoo or @{"EMSI" link 4.3.38} mode and only if the other side also supports it. This keyword defaults to @{"ZEDZAP" link 4.3.126}. @{"Examples" link 5}: NoZedZap ZedZap @ENDNODE 4.3.126 @NODE 4.3.127 "(NO)ZEDZIP " 4.3.127. @{B}(NO)ZEDZIP@{UB} Enable (disable) ZedZip mode. ZedZip is the ZModem transfer protocol -- it will not switch block sizes, but use a fixed block size of 1kb. It will resume an interrupted transfer if possible. ZedZip only works in WaZoo or @{"EMSI" link 4.3.38} mode and only if the other side also supports it. This keyword defaults to @{"ZEDZIP" link 4.3.127}. @{"Examples" link 5}: NoZedZip ZedZip @ENDNODE 4.3.127 @NODE 4.3.128 "(NO)ZOOMFULLSIZE " 4.3.128. @{B}(NO)ZOOMFULLSIZE@{UB} Select whether using the Zoom/Zip-Gadgets on TrapDoor's windows will cause them to become full-sized windows or shrink to a very small size. The keyword defaults to @{"NOZOOMFULLSIZE" link 4.3.128}, because this is what the behaviour of all TrapDoors up to version 1.83 was. Please note that @{"ZOOMFULLSIZE" link 4.3.128} will @{B}not@{UB} work when using @{"SCREENMODE" link 4.3.89} WORKBENCH. If you have AmigaOS 2.04 or higher, you can use @{"SCREENMODE" link 4.3.89} PUBLIC @{"PUBSCREENNAME" link 4.3.77} "" or @{"SCREENMODE" link 4.3.89} PUBLIC @{"PUBSCREENNAME" link 4.3.77} "Workbench" instead and @{"ZOOMFULLSIZE" link 4.3.128} will work again. @{"Examples" link 5}: NoZoomFullSize ZoomFullSize @ENDNODE 4.3.128 @NODE 5 "Example Setup " 5. @{B}Example Setup@{UB} ; **************************************************** ; ** ** ; ** TrapDoor 1.83 @{"Example" link 5} Configuration File ** ; ** ** ; **************************************************** ; This is my @{"FidoNet" link 3.1} node number @{"NODE" link 4.3.72} 2:310/6.0 ; here are my AKAs @{"AKA" link 4.3.8} "2:3160/0 7:123/456 13:13/42" ; This is my node's name @{"NAME" link 4.3.71} "The Mad House -- TrapDoor Development" ; This is the sysop's name @{"SYSOP" link 4.3.111} "Maximilian Hantsch" ; Point setup: set up the password for your boss node here. ; Leave this unset ("") to operate a node or set it to ; something else to not accept calls from unlisted nodes. @{"PASSWORD" link 4.3.75} "" ; Here I set up the baudrate that TrapDoor should use to ; talk to the modem @{"BAUD" link 4.3.16} 19200 ; For modems that can lock the baudrate, use @{"LOCK" link 4.3.55}. @{"LOCK" link 4.3.55} ; This is the minimum baudrate at which TrapDoor will ; keep a connection. If the modem responds with a ; "CONNECT xxx" message where xxx is lower than ; the @{"MINBAUD" link 4.3.64} value, TrapDoor will hang up. @{"MINBAUD" link 4.3.64} 300 ; Point setup: set this to your boss' @{"FidoNet" link 3.1} address. ; Set this to your own address when running a node. @{"BOSS" link 4.3.23} 2:310/6.0 ; Point setup: set this to the telephone number of your ; boss. When operating with a nodelist, you can also put ; the @{"FidoNet" link 3.1} address of your boss here and TrapDoor will ; consult the nodelist to find out the phone number. ; Note that TrapDoor uses the colon (":") in the @{"FidoNet" link 3.1} ; node number ot distinguish it from a telephone number, ; so always specify the zone if you want to give it a ; nodenumber. @{"CALL" link 4.3.24} 2:310/6 ; The path to your outbound directory where .FLO, .OUT ; and such stuff is. @{"OUTBOUND" link 4.3.74} "Mail:Outbound" ; The path to your inbound directory where incoming files ; are put. @{"INBOUND" link 4.3.49} "Mail:Inbound" ; If you specify a path here, TrapDoor will use this ; directory to find nodelist index/extra files. ; To disable nodelist support, use @{"NODELIST" link 4.3.73} "". @{"NODELIST" link 4.3.73} "NodeList:" ; Use @{"MAXBAUD" link 4.3.61} to automatically adjust @{"MINBAUD" link 4.3.64} to the ; highest possible baudrate. @{"MAXBAUD" link 4.3.61} ; This is the number of rings that TrapDoor will wait ; before answering the phone. If you don't want TrapDoor ; to answer the phone, just set this to @{"RINGS" link 4.3.86} 9999. @{"RINGS" link 4.3.86} 1 ; A banner line that will be displayed to human callers. ; Instead of specifying a string, you could also send out ; a complete banner file here. The second line gives you ; an example of that. @{"BANNER" link 4.3.15} "TrapDoor Development, online Mon-Sun 00:00-06:00" ; @{"BANNER" link 4.3.15} " := '!.' '.' := '.' '.' '.' := integer := integer := integer := integer := ... := ' ' '; ' := anything_except_space := anything_except_semicolon Currently defined tags are: FileName From Length Secure Time Trx When a file comes in, it is received under a temporary filename. When the file has been received successfully, it is renamed to the final filename. Should a file with this name already exist, TrapDoor does the usual filename bumping (see "@{"Bumping Filenames" link 7.1}"), but stores the original filename in the filenote in a "FileName" field. Additionally, each inbound file is tagged with a "From" field in the filenote. When a file transfer fails (carrier lost etc.), the temporary file is renamed to "!.filename.zz.nnn.ooo.pp", where is the original filename, and is the @{"FidoNet" link 3.1} address of the sender. These files are also tagged with a "FileName" field in the FileNote. Additionally, TrapDoor adds a "Length" field to the FileNote, which specifies how long the file should be. When TrapDoor begins to receive a new file, it tries to find a "!.filename.zz.nnn.ooo.pp" file that matches the incoming file. If such a file exists, and the filesize compares successfully (remember: "Length" tag in the filenote!), TrapDoor will resume transfer (ZedZap sessions) at the end of the file. FTS-1 and DietIfna can't resume transfer, but you can abort such a file transfer and later on resume with ZedZap. When TrapDoor resumes receiving a file, it will first rename it to a temporary filename again and clear the filenote. Further actions are taken as described above. The "Secure" tag stores the security measures under which a file was received. Files received from systems listed in the nodelist get the "NL" flag, and files received during password-protected sessions are marked "PW". Both flags can be set if a file was received from a listed system in a password-protection session, in which case they will be separated by a comma (","). The "Trx" tag is used to store the Transaction ID of the session in which the file was received. Every session, or "transaction" with another system is associated with a unique identifier, the "transaction id". This identifier is also listed in the logfile as "TrxID". A transaction id consists of one single hexadecimal number, plus possibly a slash and another hexadecimal number giving the transaction id which the remote system associated with this particular transaction. The latter is only shown if the other end sent us their transaction id, which can only happen in an @{"EMSI" link 4.3.38} handshake. When a file is received with Zmodem (or any of its derivatives), the original date and time of the file is also transferred and will be stored in a "Time" tag by TrapDoor. The number behind the "Time" tag is a hexadecimal unix timestamp (seconds since 1.1.1970, midnight). Please note that the order of the filenote fields is insignificant. Examples: Normal inbound file, received from a known node with password-protection: ffeb0034.mo1 : From 2:310/3; Secure NL,PW; Trx 27b23ba7; Bumped inbound file: ffeb0034.mo1,1 : From 2:310/3; FileName ffeb0034.mo1; Trx 27c138f7/27c138fb; Aborted transfer: !.ffeb0034.mo1.2.310.3.0 : FileName ffeb0034.mo1; Length 23862; Trx 27c139ae; This format should be rather flexible if future extensions have to be added (limit is 80 chars for all the filenote fields), but still remains totally compatible with ConfMail & other utilities that assume MS-Dos style filenames. @ENDNODE 7 @NODE 7.1 "Bumping Filenames " 7.1. @{B}Bumping Filenames@{UB} TrapDoor does not overwrite inbound files. Instead, the incoming filename is "bumped", i.e. a unique name is created by cautiously modifying the original filename until a new, unique name is found. Bumping proceeds like this: (a) If the filename matches "#?.?UT", it is renamed to a random "#?.PKT" file. This is necessary, as some MS-Dos software does not rename .OUT files into .PKT when transmitting them with the DietIfna protocol. Therefore, TrapDoor tries to correct this mistake. After this step, bumping continues at (b). [00bf13f4.OUT -> 27bc34f5.PKT] The following steps will only be performed as long as the name is not unique, i.e. as long as there exists already a file with that name. (b) If the filename matches "#?.PKT", it is given some random hexadecimal number plus the ".PKT" extension again. Thus, packet files stay packet files, even when bumped. Only if a unique name cannot be found within ten tries, method (d) is used for renaming the file. [27bc34f5.PKT -> 28c39d7f.PKT] (c) If the filename matches "#?.(MO|TU|WE|TH|FR|SA|SU)([0-9])", the very last digit of the filename is modified. If a unique name cannot be found by changing the last digit, method (d) is used. [00bf3f55.mo0 -> 00bf3f55.mo1] (d) If the filename is not unique, TrapDoor will append a comma (",") and a number. The number will be incremented as long as the name is not unique. [test.txt -> test.txt,1 -> test.txt,2 -> etc.] (e) continue at (d) until a unique name is found. @ENDNODE 7.1 @NODE 8 "Bugs? Poof! They're all features! " 8. @{B}Bugs? Poof! They're all features!@{UB} Most problems we have encountered are caused by wrong or incomplete RS232 cabling, modem settings, and last, but not least, people @{B}not@{UB} reading the documentation. Be sure to especially examine the chapter about the modem carefully if you encounter problems. Please also read the frequently asked questions in file "TrapDoor.FAQ". There is a minor inconvenience for people using NTSC Amigas: You have to change the default setting of @{"STATWINDOW" link 4.3.105}, as this window won't open on a standard non-interlaced NTSC screen. If you find that you have trouble communicating with another Fidonet system, you might try using different protocols. Experiment with the @{"(NO)EMSI" link 4.3.38}, @{"(NO)WAZOO" link 4.3.122}, @{"(NO)TRAPZAP" link 4.3.115}, @{"(NO)DIRECTZAP" link 4.3.34}, @{"(NO)ZEDZAP" link 4.3.126}, @{"(NO)ZEDZIP" link 4.3.127} and @{"(NO)WAZOO" link 4.3.122} keywords. @{"(NO)MAXBAUD" link 4.3.61} does not have any effect if used in custom configuration entries (set via setconfig). You need to set a @{"MINBAUD" link 4.3.64} value instead. So, instead of setconfig 2:310/6 "@{"NOMAXBAUD" link 4.3.61}" ; WRONG! use setconfig 2:310/6 "@{"MINBAUD" link 4.3.64} 2400" ; much better. TrapDoor usually runs with the standard 4000 bytes stack size. Should you experience strange hangups, crashes or Guru Meditations, try raising the stack size with the CLI command "Stack" before running TrapDoor. If you place a call using a telephone number (as opposed to calling via a nodelist), be sure to also set the @{"BOSS" link 4.3.23} parameter to the node number of the system you are calling, and @{"PASSWORD" link 4.3.75} to the correct password (or "") for that node. Here is an example: TrapDoor Call 02236-87178 Boss 2:310/48 Password "" "Remember, any minor imperfections in this product are just evidence of its hand crafted nature." @ENDNODE 8 @NODE 8.1 "Real Bugs " 8.1. @{B}Real Bugs@{UB} When sending in bug reports, please state exactly under what circumstances the bug occurred, what equipment was used and what happened. If possible, please give us a step-by-step description of how to reproduce the bug. Statements like "TrapDoor sometimes crashes on my system" don't help us to track down the problem. @ENDNODE 8.1 @NODE 9 "Past & Future " 9. @{B}Past & Future@{UB} TrapDoor started back in spring 1989, when our boss got his first dual standard HST modem. Suddenly, BinkleyTerm Amiga stopped working, it could not successfully send/receive files. So mjl and I sat down and started writing a new mailer that would overcome this and many other disadvantages of BinkleyTerm Amiga, at that time the only mailer available for the Amiga. First, we created a point version; simple to use, it allowed you to setup a state-of-the-art point system. The point version was released in October 1989, and no major bugs have been found. That was version is 1.11; Registered users were shipped 1.12, which was almost the same, except the ShareWare reminders, which always open when you start the unregistered version, had been removed in that version. After the enormous feedback we received from the first version, we decided we'd go ahead and make TrapDoor a fully node-capable mailer. We implemented the basic @{"FidoNet" link 3.1} protocol that all mailers must support, FTS-1, added @{"ARexx" link 3.14} capabilities, bbs spawning, nodelist support and all the other nice features noone wants to miss anymore. The first node capable version of TrapDoor 1.50, was followed by TrapDoor 1.80 a year later. This version enhanced the original node version with a couple of exciting new features: it offered new nodelist support via the traplist.library, improved @{"ARexx" link 3.14} commands, new bbs handling modes, special dialer and special node-dependent configuration options, @{"EMSI" link 4.3.38} session handshake, and lots more. As always, this node version could also be used in a point environment. As always, bugs creep into software, and neither TrapDoor 1.80 nor the next version, 1.83 were totally bug-free. So we had to sit down and look into these little problems, plus include some more features here and there as they came in handy. So this is our fifth release version, and this number is also the reason for the name of this TrapDoor's manual. Of course, development does not stop here. We will continue to improve TrapDoor and its related utilities to give you the hopefully most advanced mailer on the Amiga. Our future work will go especially in the direction of providing you with an integrated package which takes away a lot of the hassle currently involved in writing AmigaDOS or @{"ARexx" link 3.14} scripts to handle event scheduling and putting together the different tools necessary for a @{"FidoNet" link 3.1} system. Depending on your ShareWare registration efforts and our time permitting, one day there will hopefully be a much better and more beautiful TrapDoor II. When this new and majorly improved TrapDoor becomes ready, already registered users will receive the new version for a moderate update fee. @ENDNODE 9 @NODE 10 "Registration " 10. @{B}Registration@{UB} TrapDoor is a copyrighted product that has been made available to you under the concept of "Shareware". It has never been, nor will it ever be in the "Public Domain". You are granted a limited licence in order to evaluate these programs. If, after a 3 or 4 week period of evaluation, you find that TrapDoor suits your telecommunication needs, please register. By cooperating with this concept you help to ensure continued development of this product. Registered users will be shipped a disk with the latest release version of TrapDoor together with a keyfile. This keyfile, once copied to your system, will disable the ShareWare reminders that always open when you start or quit TrapDoor. Site licence information for commercial and government use as well as source code licences can be obtained directly from the authors. No person(s) or businesses other than the authors are authorized to accept any registration or distribution fees in any form whatsoever, except the official registration and support centers as specified by the authors. The only people who will be acknowledged as registered users are those who have sent ATS 350,- (plus another ATS 150,- if you send foreign cheques or money orders) to: TrapDoor Development Maximilian Hantsch Matzleinsdorfer Platz 3-4/3/10 A-1050 Wien Austria / Europe or registered at one of the registration and support centers as specified by the authors. A list of these can be found in the file "SupportCenters.txt". As one of the safest and possibly easiest ways to send in your registration fee from other countries, we would suggest an international postal money order -- your local post office will happily provide you with more information about this. It also has the advantage that the exchange of currencies is handled automatically and the surcharge is negligible. Alternatively, you can either send us a Eurocheque payable to Maximilian Hantsch in Austrian Schillings or have your bank transfer the registration fee to the "Österreichische Postsparkasse (PSK)" (BLZ 60000), account 6.777.234, "Maximilian Hantsch". Beware: international transfers via banks are rather expensive. Note: IF YOU SEND CHEQUES, PLEASE SEND ONLY EUROCHEQUES MADE OUT IN AUSTRIAN SCHILLINGS! We have to impose a surcharge of ATS 150,- on all other cheques, money orders or bank drafts. Until now, we have accepted other foreign cheques, money orders and bank drafts as well, but our bank has raised the charge for these by more than 50% over the past two years to more than ATS 100,- per cheque. We can no longer afford this and are thus forced to pass on this charge. Sorry. In any case, be sure to provide us with your name, address, fido-nodenumber and international phone number for our files. You can send this information via electronic mail, if you wish. If you don't mind, this data will be stored and processed in electronic form. There is also a sample registration form you can fill out in the file "@{"Registration" link 10}.txt". Please allow up to eight weeks for delivery. You, too, can have a receding hairline, suffer a nervous breakdown, and precipitate disputes with your spouse. Here is all you need. @ENDNODE 10 @NODE 11 "Politics " 11. @{B}Politics@{UB} This chapter tells you about the allowed methods of @{"Distribution" link 11.1} for TrapDoor, about where to find @{"Support" link 11.2}, lists the exact terms of the software @{"Licence" link 11.3}, under which you may use the software, and finally, there is an important @{"Disclaimer" link 11.5} in this chapter too. @ENDNODE 11 @NODE 11.1 "Distribution " 11.1. @{B}Distribution@{UB} In a nutshell, TrapDoor may be distributed freely as long as the following restrictions are met: The distributor may only charge a fee up to the costs of obtaining a public domain diskette from Fred Fish. The distributor agrees to cease distributing the programs and data involved if requested to do so by the authors. The distributor may only distribute an unmodified copy of the original program, with all the supplied documentation and copyright notices intact. For more details, see the chapter called "@{"Licence" link 11.3}". @ENDNODE 11.1 @NODE 11.2 "Support " 11.2. @{B}Support@{UB} The latest version of TrapDoor (with all its associated tools) is always available for filerequest from @{"FidoNet" link 3.1} node 2:310/6, "The Mad House" under the magic filename "TRAPDOOR". If you have any suggestions, bug reports etc., feel free to contact the authors of TrapDoor at the address given in the chapter "@{"Registration" link 10}". Additionally, you can reach us at: Maximilian Hantsch Martin Laubach @{"Fido" link 3.1}: 2:310/6 @{"Fido" link 3.1}: 2:310/3.14 Uucp: max@madvie.co.at Uucp: mjl@alison.co.at Also, there is a @{"FidoNet" link 3.1} Echomail conference called TRAPDOOR, which should be available at major backbones. This conference is in English and intended for the users of TrapDoor. There, you can freely exchange your experience with TrapDoor, discuss future enhancements you would like to see etc. Both authors will participate in the conference and try to assist you. The availability of new versions of TrapDoor will be announced there, too. @ENDNODE 11.2 @NODE 11.3 "Licence " 11.3. @{B}Licence@{UB} 1. This licence applies to the product called "TrapDoor", a set of programs for the Amiga computer, published by Maximilian Hantsch and Martin Laubach under the concepts of ShareWare, and the accompanying documentation, example files and anything else that comes with the original distribution. The terms "Programs" and "TrapDoor" below, refer to this product. The licencee is addressed as "you". 2. You may copy and distribute verbatim copies of the programs' executable code and documentation as you receive it, in any medium, provided that you conspicuously and appropriately publish only the original, unmodified programs, with all copyright notices and disclaimers of warranty intact and including all the accompanying documentation, example files and anything else that came with the original. 3. You may not copy and/or distribute these programs without the accompanying documentation and other additional files that came with the original. You may not copy and/or distribute modified versions of these programs. 4. You may not copy, modify, sublicence, distribute or transfer the programs except as expressly provided under this licence. Any attempt otherwise to copy, modify, sublicence, distribute or transfer the programs is void, and will automatically terminate your rights to use the programs under this licence. However, parties who have received copies, or rights to use copies, from you under this licence will not have their licences terminated so long as such parties remain in full compliance. 5. By copying, distributing and/or using the programs you indicate your acceptance of this licence to do so, and all its terms and conditions. 6. Each time you redistribute the programs, the recipient automatically receives a licence from the original licensor to copy, distribute and/or use the programs subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. 7. You may not disassemble, decompile, re-source or otherwise reverse engineer the programs. 8. You may use the programs for a period of up to 30 days for evaluation. After that, you have to register. 9. If you wish to incorporate parts of the programs into other programs, write to the authors to ask for permission. 10. You agree to cease distributing the programs and data involved if requested to do so by the authors. 11. You may charge a fee to recover distribution costs. The fee for diskette distribution may not be more than the cost to obtain a public domain diskette from Fred Fish. @ENDNODE 11.3 @NODE 11.4 "No Warranty " 11.4. @{B}No Warranty@{UB} THERE IS NO WARRANTY FOR THE PROGRAMS, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAMS "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAMS IS WITH YOU. SHOULD THE PROGRAMS PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY REDISTRIBUTE THE PROGRAMS AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAMS (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAMS TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. @ENDNODE 11.4 @NODE 11.5 "Disclaimer " 11.5. @{B}Disclaimer@{UB} No warranty, either express or implied, is made with respect to the fitness or merchantability of TrapDoor. Maximilian Hantsch and Martin Laubach (referred to as "the authors"), reserve the right to not develop any future versions of TrapDoor. The authors will try to make a good faith attempt at correcting any problems if any are discovered, but are in no way required, nor bound to correct them. The authors neither assume nor accept any responsibility for the use or misuse of these programs. They also will not be held liable for damages or any compensation beyond the original registration fee due to loss of profit or any other damages arising out of the use, or inability to use these programs. Neither Maximilian Hantsch nor Martin Laubach will be liable for any damage arising from the failure of these programs to perform as described, or any destruction of other programs or data residing on a system attempting to run the programs. While we know of no damaging errors, the user of these programs uses it at his or her own risk. @ENDNODE 11.5 @NODE 12 "Acknowledgements " 12. @{B}Acknowledgements@{UB} The following names are either trademarks or the efforts of the person and/or company listed: Amiga and AmigaDOS are trademarks of Commodore-Amiga, Inc. @{"ARexx" link 3.14} by William S. Hawes, Wishful Thinking Development Corp. BinkleyTerm Amiga by Jürgen Hermann. BinkleyTerm by Alan D. Applegate, Robert Hartman and Vincent Perriello. Chameleon Editor by Jürgen Hermann. ConfMail by Bob Hartman, Spark Software Inc. D'Bridge by Chris Irwin. Diamonds & Pearls by Prince. DLG Professional by TelePro Technologies. EchoMail by Jeff Rush. @{"EMSI" link 4.3.38} by the EMSC. Excelsior! BBS by Sycom Design. @{"feline" link 12} Helsingissä. @{"Fido" link 3.1} and @{"FidoNet" link 3.1} are trademarks of Tom Jennings, @{"Fido" link 3.1} Software. FrontDoor by Joaquim Homrighausen. "Hey, there's Another Feature!"-Award: Roger Nordin. Inspiration by US Robotics' Courier HST Dual Standard. Jessi, our TrapBunny ;) Kittens, Katze and @{"Yvonne" link 12}. @{"Licence" link 11.3} Agreement inspired by Jack Radigan and the GNU General Public License. Many Thanks to Alan Bland, Alexander Holy, Arnout Grootveld, Eric De Jong, Fredrik Kjellberg, Heiko Richter, Iljitsch van Beijnum, Johannes Mistelbauer, Lawrence Freeman, Manfred Schädler, Many Others, Marcus Kuba, Peer Hasselmeyer, Peter Deane, Roger Nordin, Tony Miller, Werner Schlagnitweit. Moral Support by MTNLION. More Moral Support from @{"Tasmania" link 12}. MS-DOS is a trademark of Microsoft Corporation. Neelie yekom. Opus by Wynn Wagner III. OwnDevUnit.library by Christopher A. Wichura. Paragon by Jon Radoff. Proofreading of this manual by Arnout Grootveld. SEAlink, SEAdog are trademarks of System Enhancement Associates. Spaces, Pigs, Ships and their Stars. Special Thanks to all our Registered Users. TrapDog by Peter Wlcek. TrapDoor is a registered trademark of Maximilian Hantsch and Martin Laubach. TrapList, TrapPoll, TrapTell and traplist.library by Maximilian Hantsch and Martin Laubach. TrapToss by René Hexel. Typesetting of this manual by proff. Warm Wet Circles by Marillion. YooHoo by Wynn Wagner III. ZModem by Chuck Forsberg. "And you try to tell that the young people of today and they won't believe you." @ENDNODE 12 @NODE index Index @{"(NO)(UN)LISTEN 4.3.117. " link 4.3.117} @{"(NO)7WIRE 4.3.1. " link 4.3.1} @{"(NO)ABS 4.3.3. " link 4.3.3} @{"(NO)ACCOUNTING 4.3.4. " link 4.3.4} @{"(NO)ALLOWREFUSING 4.3.9. " link 4.3.9} @{"(NO)AUTOADJUST 4.3.12. " link 4.3.12} @{"(NO)AUTOOVERSCAN 4.3.13. " link 4.3.13} @{"(NO)BACKGROUND 4.3.14. " link 4.3.14} @{"(NO)BEEPDISPLAY 4.3.22. " link 4.3.22} @{"(NO)DIETIFNA 4.3.33. " link 4.3.33} @{"(NO)DIRECTZAP 4.3.34. " link 4.3.34} @{"(NO)DSR 4.3.37. " link 4.3.37} @{"(NO)EMSI 4.3.38. " link 4.3.38} @{"(NO)ESCAPERESETSMODEM 4.3.39. " link 4.3.39} @{"(NO)FASTEMSI 4.3.40. " link 4.3.40} @{"(NO)FLOATLOCK 4.3.44. " link 4.3.44} @{"(NO)FORBID... 4.3.45. " link 4.3.45} @{"(NO)IMMEDIATE 4.3.48. " link 4.3.48} @{"(NO)INTERLACE 4.3.50. " link 4.3.50} @{"(NO)KEEPALL 4.3.51. " link 4.3.51} @{"(NO)KEEPXMAIL 4.3.52. " link 4.3.52} @{"(NO)KIWIPULSE 4.3.53. " link 4.3.53} @{"(NO)LISTEN 4.3.54. " link 4.3.54} @{"(NO)LOCK 4.3.55. " link 4.3.55} @{"(NO)MAXBAUD 4.3.61. " link 4.3.61} @{"(NO)QUIET 4.3.79. " link 4.3.79} @{"(NO)SHARED 4.3.96. " link 4.3.96} @{"(NO)SHOWREXX 4.3.97. " link 4.3.97} @{"(NO)SNIFFARQ 4.3.101. " link 4.3.101} @{"(NO)STRIPDASHES 4.3.107. " link 4.3.107} @{"(NO)SWEPULSE 4.3.109. " link 4.3.109} @{"(NO)TIMESTAMP 4.3.114. " link 4.3.114} @{"(NO)TRAPZAP 4.3.115. " link 4.3.115} @{"(NO)USESYSFONT 4.3.118. " link 4.3.118} @{"(NO)USEUSERSHELL 4.3.119. " link 4.3.119} @{"(NO)WAZOO 4.3.122. " link 4.3.122} @{"(NO)WRAPLINES 4.3.123. " link 4.3.123} @{"(NO)XMAIL 4.3.125. " link 4.3.125} @{"(NO)ZEDZAP 4.3.126. " link 4.3.126} @{"(NO)ZEDZIP 4.3.127. " link 4.3.127} @{"(NO)ZOOMFULLSIZE 4.3.128. " link 4.3.128} @{"(UN)LISTEN 4.3.117. " link 4.3.117} @{"2-dimensional Filenames 6.1. " link 6.1} @{"4-dimensional Filenames 6.2. " link 6.2} @{"7WIRE 4.3.1. " link 4.3.1} @{"ABORT signals 4.3.2. " link 4.3.2} @{"ABS 4.3.3. " link 4.3.3} @{"Accounting 3.6. " link 3.6} @{"ACCOUNTING 4.3.4. " link 4.3.4} @{"ACCTMAX limits 4.3.5. " link 4.3.5} @{"Acknowledgements 12. " link 12} @{"ADJUST factor 4.3.6. " link 4.3.6} @{"AFTERSESSION command-string 4.3.7. " link 4.3.7} @{"AKA akalist 4.3.8. " link 4.3.8} @{"ALLOWREFUSING 4.3.9. " link 4.3.9} @{"ANSWER 4.3.10. " link 4.3.10} @{"ARexx 3.14. " link 3.14} @{"ARQSTRING string 4.3.11. " link 4.3.11} @{"AUTOADJUST 4.3.12. " link 4.3.12} @{"Automatic Buffer Sizing 3.13. " link 3.13} @{"AUTOOVERSCAN 4.3.13. " link 4.3.13} @{"BACKGROUND 4.3.14. " link 4.3.14} @{"BANNER bannerline 4.3.15. " link 4.3.15} @{"Basics 3. " link 3} @{"BAUD baudrate 4.3.16. " link 4.3.16} @{"BBSCHAR character 4.3.17. " link 4.3.17} @{"BBSCOMMAND command-string 4.3.18. " link 4.3.18} @{"BBSINOUT device 4.3.19. " link 4.3.19} @{"BBSMESSAGE text 4.3.20. " link 4.3.20} @{"BBSMODE mode 4.3.21. " link 4.3.21} @{"BEEPDISPLAY 4.3.22. " link 4.3.22} @{"BOSS zone:net/node.point 4.3.23. " link 4.3.23} @{"Bugs? Poof! They're all features! 8. " link 8} @{"Bumping Filenames 7.1. " link 7.1} @{"CALL number | fido-address 4.3.24. " link 4.3.24} @{"COLORS palette-specification 4.3.25. " link 4.3.25} @{"COLOURS palette-specification 4.3.26. " link 4.3.26} @{"Compatibility 3.4. " link 3.4} @{"Compressed Mail files 6.6. " link 6.6} @{"CONCEPTS 4.3.27. " link 4.3.27} @{"Configuration Commands 4. " link 4} @{"CONFIG config-file 4.3.28. " link 4.3.28} @{"COST cost-value 4.3.29. " link 4.3.29} @{"CREDITS 4.3.30. " link 4.3.30} @{"Custom Configuration Entries 3.5. " link 3.5} @{"Dial Scripts 3.15. " link 3.15} @{"DIALER command-string 4.3.31. " link 4.3.31} @{"DIALTIMEOUT seconds 4.3.32. " link 4.3.32} @{"DIETIFNA 4.3.33. " link 4.3.33} @{"DIRECTZAP 4.3.34. " link 4.3.34} @{"Disclaimer 11.5. " link 11.5} @{"DISPLAYID integer 4.3.35. " link 4.3.35} @{"Distribution 11.1. " link 11.1} @{"DROPBBSSECS seconds 4.3.36. " link 4.3.36} @{"DSR 4.3.37. " link 4.3.37} @{"Embedded Percent-Commands 4.1. " link 4.1} @{"EMSI 4.3.38. " link 4.3.38} @{"ESCAPERESETSMODEM 4.3.39. " link 4.3.39} @{"Examples 6.8. " link 6.8} @{"Example Modem Settings 2.5. " link 2.5} @{"Example Setup 5. " link 5} @{"Extensions 6.3. " link 6.3} @{"FASTEMSI 4.3.40. " link 4.3.40} @{"Fax and Voice Support 3.12. " link 3.12} @{"FAXCOMMAND commandline 4.3.41. " link 4.3.41} @{"FAXSTRING string 4.3.42. " link 4.3.42} @{"FidoNet 3.1. " link 3.1} @{"File Tagging 3.8. " link 3.8} @{"FKEY function-key-assignment 4.3.43. " link 4.3.43} @{"FLOATLOCK 4.3.44. " link 4.3.44} @{"Flow files 6.5. " link 6.5} @{"FORBID... 4.3.45. " link 4.3.45} @{"FREQUEST command-string 4.3.46. " link 4.3.46} @{"HELP 4.3.47. " link 4.3.47} @{"IMMEDIATE 4.3.48. " link 4.3.48} @{"INBOUND inbound-mail-directory 4.3.49. " link 4.3.49} @{"Installation 2. " link 2} @{"INTERLACE 4.3.50. " link 4.3.50} @{"Internal Supra 2400zi Modems 2.5.3. " link 2.5.3} @{"Introduction 1. " link 1} @{"KEEPALL 4.3.51. " link 4.3.51} @{"KEEPXMAIL 4.3.52. " link 4.3.52} @{"Keywords 4.3. " link 4.3} @{"KIWIPULSE 4.3.53. " link 4.3.53} @{"Licence 11.3. " link 11.3} @{"LISTEN 4.3.54. " link 4.3.54} @{"LOCK 4.3.55. " link 4.3.55} @{"LOGCALLERID filename 4.3.57. " link 4.3.57} @{"Logfile Buffering 3.17. " link 3.17} @{"LOGFILE filename 4.3.58. " link 4.3.58} @{"LOGLEVEL group:level 4.3.59. " link 4.3.59} @{"LOGWINDOW window-specification 4.3.60. " link 4.3.60} @{"LOG level:text 4.3.56. " link 4.3.56} @{"Mailer Operation 3.2. " link 3.2} @{"MAXBAUD 4.3.61. " link 4.3.61} @{"MAXLOGLINES number 4.3.62. " link 4.3.62} @{"MAXLOGSECS seconds 4.3.63. " link 4.3.63} @{"MINBAUD baudrate 4.3.64. " link 4.3.64} @{"Modem Commands 4.2. " link 4.2} @{"MODEMANSWER modem-answer-string 4.3.65. " link 4.3.65} @{"MODEMDIALPOST modem-post-dial-string 4.3.67. " link 4.3.67} @{"MODEMDIALPRE modem-pre-dial-string 4.3.66. " link 4.3.66} @{"MODEMHANGUP modem-hangup-string 4.3.68. " link 4.3.68} @{"MODEMINIT modem-init-string 4.3.69. " link 4.3.69} @{"MODEMRESETINTERVAL minutes 4.3.70. " link 4.3.70} @{"Multiple Lines 3.16. " link 3.16} @{"NAME board's name 4.3.71. " link 4.3.71} @{"No Warranty 11.4. " link 11.4} @{"NO(UN)LISTEN 4.3.117. " link 4.3.117} @{"NO7WIRE 4.3.1. " link 4.3.1} @{"NOABS 4.3.3. " link 4.3.3} @{"NOACCOUNTING 4.3.4. " link 4.3.4} @{"NOALLOWREFUSING 4.3.9. " link 4.3.9} @{"NOAUTOADJUST 4.3.12. " link 4.3.12} @{"NOAUTOOVERSCAN 4.3.13. " link 4.3.13} @{"NOBACKGROUND 4.3.14. " link 4.3.14} @{"NOBEEPDISPLAY 4.3.22. " link 4.3.22} @{"Node Setup 2.3. " link 2.3} @{"Nodelist 3.3. " link 3.3} @{"NODELIST nodelist-directory 4.3.73. " link 4.3.73} @{"NODE zone:net/node.point 4.3.72. " link 4.3.72} @{"NODIETIFNA 4.3.33. " link 4.3.33} @{"NODIRECTZAP 4.3.34. " link 4.3.34} @{"NODSR 4.3.37. " link 4.3.37} @{"NOEMSI 4.3.38. " link 4.3.38} @{"NOESCAPERESETSMODEM 4.3.39. " link 4.3.39} @{"NOFASTEMSI 4.3.40. " link 4.3.40} @{"NOFLOATLOCK 4.3.44. " link 4.3.44} @{"NOFORBID... 4.3.45. " link 4.3.45} @{"NOIMMEDIATE 4.3.48. " link 4.3.48} @{"NOINTERLACE 4.3.50. " link 4.3.50} @{"NOKEEPALL 4.3.51. " link 4.3.51} @{"NOKEEPXMAIL 4.3.52. " link 4.3.52} @{"NOKIWIPULSE 4.3.53. " link 4.3.53} @{"NOLISTEN 4.3.54. " link 4.3.54} @{"NOLOCK 4.3.55. " link 4.3.55} @{"NOMAXBAUD 4.3.61. " link 4.3.61} @{"NOQUIET 4.3.79. " link 4.3.79} @{"NOSHARED 4.3.96. " link 4.3.96} @{"NOSHOWREXX 4.3.97. " link 4.3.97} @{"NOSNIFFARQ 4.3.101. " link 4.3.101} @{"NOSTRIPDASHES 4.3.107. " link 4.3.107} @{"NOSWEPULSE 4.3.109. " link 4.3.109} @{"NOTIMESTAMP 4.3.114. " link 4.3.114} @{"NOTRAPZAP 4.3.115. " link 4.3.115} @{"NOUSESYSFONT 4.3.118. " link 4.3.118} @{"NOUSEUSERSHELL 4.3.119. " link 4.3.119} @{"NOWAZOO 4.3.122. " link 4.3.122} @{"NOWRAPLINES 4.3.123. " link 4.3.123} @{"NOXMAIL 4.3.125. " link 4.3.125} @{"NOZEDZAP 4.3.126. " link 4.3.126} @{"NOZEDZIP 4.3.127. " link 4.3.127} @{"NOZOOMFULLSIZE 4.3.128. " link 4.3.128} @{"Ordinary 2400 Baud Modems 2.5.1. " link 2.5.1} @{"Outbound File Tagging 6.9. " link 6.9} @{"OUTBOUND outbound-mail-directory 4.3.74. " link 4.3.74} @{"OwnDevUnit.library Support 3.18. " link 3.18} @{"Packet files 6.4. " link 6.4} @{"PASSWORD password 4.3.75. " link 4.3.75} @{"Past & Future 9. " link 9} @{"PICKUP what 4.3.76. " link 4.3.76} @{"Point Setup 2.2. " link 2.2} @{"Politics 11. " link 11} @{"PUBSCREENNAME name 4.3.77. " link 4.3.77} @{"QUIET 4.3.79. " link 4.3.79} @{"QUIT 4.3.78. " link 4.3.78} @{"Real Bugs 8.1. " link 8.1} @{"REDIALDELAY seconds 4.3.80. " link 4.3.80} @{"Refusing and Pickup Preferences 3.9. " link 3.9} @{"Registration 10. " link 10} @{"Request files 6.7. " link 6.7} @{"RESET 4.3.81. " link 4.3.81} @{"RETRIES count 4.3.82. " link 4.3.82} @{"Return Values 3.11. " link 3.11} @{"REXXNAME portname 4.3.83. " link 4.3.83} @{"RINGCOMMAND commandline 4.3.84. " link 4.3.84} @{"RINGINGS number 4.3.85. " link 4.3.85} @{"RINGS number 4.3.86. " link 4.3.86} @{"RUN command-string 4.3.87. " link 4.3.87} @{"SCLEAR 4.3.88. " link 4.3.88} @{"SCREENMODE mode 4.3.89. " link 4.3.89} @{"SCREENTOBACK 4.3.90. " link 4.3.90} @{"SCREENTOFRONT 4.3.91. " link 4.3.91} @{"Security 3.7. " link 3.7} @{"SERIALBUFSIZE size-in-bytes 4.3.92. " link 4.3.92} @{"SERIALFLAGS serial-flags 4.3.93. " link 4.3.93} @{"SERIALNAME serial-device-name 4.3.94. " link 4.3.94} @{"SERIALUNIT serial-unit-number 4.3.95. " link 4.3.95} @{"SHARED 4.3.96. " link 4.3.96} @{"SHOWREXX 4.3.97. " link 4.3.97} @{"SLINE 4.3.98. " link 4.3.98} @{"SLOWMODEM modem-command-delay 4.3.99. " link 4.3.99} @{"SMODEM modem-command 4.3.100. " link 4.3.100} @{"SNIFFARQ 4.3.101. " link 4.3.101} @{"SPAWN command-string 4.3.102. " link 4.3.102} @{"STARTSESSION 4.3.103. " link 4.3.103} @{"STATUS what 4.3.104. " link 4.3.104} @{"STATWINDOW window-specification 4.3.105. " link 4.3.105} @{"STIMEOUT timeout 4.3.106. " link 4.3.106} @{"STRIPDASHES 4.3.107. " link 4.3.107} @{"Support 11.2. " link 11.2} @{"Supra V.32bis 2.5.4. " link 2.5.4} @{"SWAIT string 4.3.108. " link 4.3.108} @{"SWEPULSE 4.3.109. " link 4.3.109} @{"SWRITE string 4.3.110. " link 4.3.110} @{"SYSOP sysop's-name 4.3.111. " link 4.3.111} @{"TASKPRI priority 4.3.112. " link 4.3.112} @{"TESTFREQ 4.3.113. " link 4.3.113} @{"The Inbound Directory 7. " link 7} @{"The Keyboard 3.10. " link 3.10} @{"The Keyfile 2.1. " link 2.1} @{"The Modem 2.4. " link 2.4} @{"The Outbound Directory 6. " link 6} @{"TIMESTAMP 4.3.114. " link 4.3.114} @{"TRAPZAP 4.3.115. " link 4.3.115} @{"TURNAROUND command-string 4.3.116. " link 4.3.116} @{"US Robotics Courier HST Modems 2.5.2. " link 2.5.2} @{"USESYSFONT 4.3.118. " link 4.3.118} @{"USEUSERSHELL 4.3.119. " link 4.3.119} @{"VERSION 4.3.124. " link 4.3.124} @{"VOICECOMMAND commandline 4.3.120. " link 4.3.120} @{"VOICESTRING string 4.3.121. " link 4.3.121} @{"WAZOO 4.3.122. " link 4.3.122} @{"WRAPLINES 4.3.123. " link 4.3.123} @{"XMAIL 4.3.125. " link 4.3.125} @{"ZEDZAP 4.3.126. " link 4.3.126} @{"ZEDZIP 4.3.127. " link 4.3.127} @{"ZOOMFULLSIZE 4.3.128. " link 4.3.128} @{"ZyXEL Modems 2.5.5. " link 2.5.5} @ENDNODE index