Beijing Paradise BBS Backup

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

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

Wrap

Text File | 1995-05-01 | 41.1 KB | 1,449 lines

FrontDoor Manager 1.00.SW Gamma-1 User documentation Shareware version Table of contents 1 LICENCE AND DISCLAIMER . . . . . . . . . . . . . . . . . . . . . . . 1 2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2.1 Software requirements . . . . . . . . . . . . . . . . . . . . . 2 2.2 Hardware requirements . . . . . . . . . . . . . . . . . . . . . 2 2.3 Additional software . . . . . . . . . . . . . . . . . . . . . . 2 2.4 BBS Software . . . . . . . . . . . . . . . . . . . . . . . . . 2 3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.1 FrontDoor . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.1.1 FrontDoor 2.20 or above . . . . . . . . . . . . . . . . . 3 3.1.2 FrontDoor 2.11.SW or above . . . . . . . . . . . . . . . 3 3.2 RemoteAccess 2.0x . . . . . . . . . . . . . . . . . . . . . . . 3 3.3 Concord 0.01 . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.4 PCBoard 15.x . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.5 AUTOEXEC.BAT . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.6 CONFIG.SYS . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.7 Directories . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4 Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4.1 Environment variables . . . . . . . . . . . . . . . . . . . . . 5 4.2 System variables . . . . . . . . . . . . . . . . . . . . . . . 5 4.3 FDMSETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4.3.1 Command line parameters . . . . . . . . . . . . . . . . . 5 4.3.2 Compile . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.3.2 System data . . . . . . . . . . . . . . . . . . . . . . . 7 4.3.3 Miscellaneous . . . . . . . . . . . . . . . . . . . . . . 12 4.3.4 Event manager . . . . . . . . . . . . . . . . . . . . . . 13 4.3.5 Export data . . . . . . . . . . . . . . . . . . . . . . . 14 4.3.6 Information . . . . . . . . . . . . . . . . . . . . . . . 14 4.3.7 Exit to DOS . . . . . . . . . . . . . . . . . . . . . . . 14 5 Nodelist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 5.1 FDMNODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 6 Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 6.1 Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 6.2 Command line parameters . . . . . . . . . . . . . . . . . . . . 18 6.3 Errorlevels . . . . . . . . . . . . . . . . . . . . . . . . . . 18 8 Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 7 Shareware registration . . . . . . . . . . . . . . . . . . . . . . . 20 8 Commercial inquiries . . . . . . . . . . . . . . . . . . . . . . . . 21 9 Credits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 1 LICENCE AND DISCLAIMER FrontDoor Manager here after FDMGR is copyrighted material of Thomas Raehalme, FINCOMM SYSTEMS protected by the laws of Finland. THIS IS THE SHAREWARE VERSION OF FRONTDOOR MANAGER. THE SHAREWARE VERSION IS AVAILABLE ONLY FOR NON-COMMERCIAL USERS. ALL COMMERCIAL USERS MUST PURCHASE A COMMERCIAL COPY OF FRONTDOOR MANAGER FROM ONE OF THE AUTHORIZED DEALERS. IF YOU ARE A NON-COMMERCIAL USER YOU ARE ALLOWED TO TEST THIS SOFTWARE FOR A PERIOD OF TWENTY-ONE (21) DAYS. AFTER THE EVALUATION PERIOD YOU MUST DECIDE IF YOU WANT TO USE THE SOFTWARE IN THE FUTURE AND REGISTER IT. Although this software has been tested in different environments no guarantee or warranty of anykind is given by the author, Thomas Raehalme or FINCOMM SYSTEMS. The author is not responsible for damage of anykind including but not limited to financial lost of any kind caused by FDMGR. The Shareware version of FrontDoor Manager can be distributed freely as long as the following terms are agreed. FDMGR must be distributed in the original unmodified archive. No files may not be deleted and files may not be added. All the files must be distributed in an unmodified original format and no profit of any kind is made of the product. For CD-ROM distribution please contact the author, Thomas Raehalme. 1 2 Introduction FrontDoor Manager is an off-line product. It has been developed to allow electric bulletin board systems stay on-line 24 hours a day. FDMGR does nearly everything which takes expensive on-line time from the users without taking the BBS off-line. FDMGR takes care of external events, mail processing, nodelist updating, file echo processing, and more. Do not take your BBS off-line while packing messages, let FDMGR do the job for you! 2.1 Software requirements o MS or PC DOS 3.10 or 99% compatible operating system. o FrontDoor 2.11.SW, 2.20 or above. o RemoteAccess 2.0x, Concord 0.01 or PCBoard 15.x. 2.2 Hardware requirements o An IBM PC, AT, i386, i486, Pentium(tm), PS/2 or 100% BIOS compatible. o A hard disk with at least 300 KB of available disk space. o A monochrome or color monitor. o 234 KB of free system memory. 2.3 Additional software o Mail tosser/manager such as GEcho. o File echo processor such as Allfix. o Full screen mail reader such GoldEd. o Full screen file editor such as QEdit or GEdit. 2.4 BBS Software FrontDoor Manager supports RemoteAccess, Concord and PCBoard. 2 3 Installation FrontDoor Manager can be very easily set up with a setup maintenance provided with the software. FDMSETUP which is the setup maintenance utility gives a possibility to alter nearly every option available. 3.1 FrontDoor If you're running FrontDoor multiLine setting up FDMGR does not require many changes to be done in the FD configuration. Running under the Shareware version gives you just a little bit work but is not impossible. 3.1.1 FrontDoor 2.20 or above Disable exiting back to the OS after a mail session from Mailer.Miscellaneous and from Manager.Events.Behaviour. FrontDoor should only exit when passing a human caller to the BBS or when pressing <Alt-Q>. Edit the Global.Filenames.MailExit to point to the filename which FDMGR will recognize when new mail or files have been received and they need to be processed. Make FD to create the MailExit semaphore every time either files or mail packets have been received. This filename must be exactly the same as in FDMSETUP (System data.Semaphores.Received). 3.1.2 FrontDoor 2.11.SW or above As the Shareware version doesn't support the MailExit semaphore only the batch files need to be changed. After a mail session FD usually exists back to the OS and tosses the mail, etc. depending of the configuration. Replace everything which is done when FD exists to OS after a mail session with a command line which will create the MailExit semaphore manually. Semaphores can be created either with SEMAFORE.EXE provided with FDMGR or with a plain DOS command REM: REM>filename.ext eg. REM>C:\FD\FDRESCAN.NOW. FDMGR semaphore directory must point to the FD System directory where the Shareware version stores its semaphores. 3.2 RemoteAccess 2.0x FrontDoor Manager can be used with both Shareware and Professional versions of RemoteAccess. The path defined in RA environment variable will be used as common path and FDMGR will search USERON.BBS from that directory. RemoteAccess will also create RABUSY semaphores which should be defined in Semaphores.Task specific. 3.3 Concord 0.01 As Concord has a seperate node directory where it stores its node files and on-line messages it has to be defined in FDMSETUP. When using Concord it is not required to use the user on-line semaphore. 3.4 PCBoard 15.x 3 As the path to the USERNET.XXX file is user defined must the file be defined in FDMSETUP also. USERNET.XXX is the file which holds information about each node (who's on-line, etc). It is also possible to use PCBoard as a stand-alone software with FDMGR. 3.5 AUTOEXEC.BAT Add SET FDMGR=C:\FDMGR to the AUTOEXEC.BAT so that FDMGR can easily find it's main configuration files. When the environment variable FDMGR has been set correctly it is possible to execute FDMGR in another directory than the one where the executables are stored. 3.6 CONFIG.SYS Please make sure that the FILES setting is at least 50. 3.7 Directories First create the system directory where all the system files are stored. FrontDoor Manager doesn't require any other directories but it might be a good idea to store all the batch and script files in a separate directory to keep the system directory clean. Example: C:\FDMGR ├─BATCH └─SCRIPT 4 4 Setup The setup maintenance of FrontDoor Manager, FDMSETUP, is used to configure FDMGR. It gives you the possibility to change nearly every available feature. FDMGR also supports environment variables and special system variables to get access to the system information. 4.1 Environment variables It is possible to import environment variables to the FDMGR settings. When starting FrontDoor Manager it will scan all path and file names for possible environment variables. The environment variable can be anything within two $ (ASCII 36) characters. Please be aware that there are two internal variables which might get messed up with the environment variables. These variables are $TASK$ which indicates the current task number (node number minus one) and $NODE$ which indicates the current node number. $FD$ would import the data stored in the environment variable FD used by FrontDoor and $RA$ would import the data stored in the environment variable RA used by RemoteAccess for example C:\FD and C:\RA. 4.2 System variables FrontDoor Manager has a few system variables which are used in different situations. $TASK$ and $NODE$ described in the chapter Environment variables can be used to indicate the node and task number. When setting up status strings can some system variables be used to indicate node/task information. %USER% Name of the user on-line %LOCATION% Location of the user on-line %BPS% Connection speed of the user on-line %STATUS% Node status (Browsing, File xfer, Messages, etc) %LASTCALLER% Name of the last caller (any node) %REMOTE% The node address of the remote system The following variables can be used with the user definable reply file which is used when replying a message from another node. %USER% Name of the original writer %FIRST% First name of the original writer %LAST% Last name of the original writer %QUOTE% Quote the text written by the original writer %VERSION% FrontDoor Manager version %COOKIE% Pick a random cookie from COOKIE.MGR 4.3 FDMSETUP 4.3.1 Command line parameters The following parameters must be given as stated. Do not use a forward slash (/) or a dash (-) in the front of the command. PACK 5 Pack all the database files. This option will remove all deleted entries. IMPORT Import configuration from other software. FDMSETUP will automatically detect which software has been installed and import the configuration from the setup files. COMPILE Compile a configuration from an ASCII file to a BINARY format. Please note that before starting the compilation FDMSETUP will reset all the values and everything has to be defined in the input file. KEYS Enter the personal registration information. This parameter is available only in the registered version. The following command line parameters require the usage of a forward slash (/) or a dash (-) as the first character. CONFIG:<file> Forces FDMSETUP to use <file> as a configuration. The <file> must include a full path to the SETUP.MGR eg. C:\FDM\SETUP.MGR. NOSHADOW Disables box shadows. MONO Forces the usage of monochrome display (video segment B000h). NOCLOCK Disable the system clock from the right corner. If your system hangs when starting FDMSETUP better try this parameter. 4.3.2 Compile If you like more ASCII configuration files than using a setup maintenance utility you can use FDMGR.INI an ASCII file instead of the setup maintenance. Every time FDMGR.INI has been changed it has to be compiled with FDMSETUP using the command line parameter 'Compile'. FDMGR.INI consists of three different categories just as in FDMSETUP. [System data] [Miscellaneous] [Event manager] 6 In each category there are several commands included which are named just as in FDMSETUP with the only difference that all spaces are replaced with an underscore (ASCII 95). Commands and passwords are not case sensitive. A few examples: [System data] SYSTEM_USERS.1.NAME Thomas Raehalme SYSTEM_USERS.1.PASSWORD Password SYSTEM_USERS.1.STATUS Remote SYSTEM_USERS.2.NAME Toni Raehalme SYSTEM_USERS.2.PASSWORD Secret SYSTEM_USERS.2.STATUS Supervisor PATHNAMES.SYSTEM E:\FDMGR FILENAMES.LOG_FILE E:\LOG\FDMGR.LOG [Miscellaneous] GLOBAL_OPTIONS.BBS_SOFTWARE RemoteAccess GLOBAL_OPTIONS.SCREEN_SAVER 30 Configuring Event manager is not yet supported in 1.00.SW. 4.3.2 System data Site information Defines miscellaneous information about your system. System users It is possible to define up to 10 system users. Each user can have a password defined. Each password has to be different. Two users cannot use the same passwords as passwords are used to identify the person. FDMGR supports three different access levels: Normal, Supervisor and Remote. Users with the normal access level aren't allowed to use FDMSETUP but they're allowed to use FDMGR freely. Users with the remote status are allowed to alter settings remotely but not locally with FDMSETUP. Users with the status supervisor don't have any restrictions. Pathnames System Path to the directory where all the system files are stored. Netmail Path to the netmail directory as defined in FrontDoor. This 7 is the directory where all the netmail messages are stored. Nodelist Path to the nodelist directory. This is the directory where FDMGR searches the nodelist files. Inbound Path to the directory where all incoming file and mail packets are stored. This directory is important as this directory is checked for incoming file and mail packets before starting the external echomail/fileecho processor. SecInbound All the received files from secured sessions are stored in this directory. Packets Path to the directory where FrontDoor stores its temporary mail packets. Common If your BBS software uses a specific directory as a common directory for all the lines the directory must be defined here. By leaving this entry empty FDMGR will use the directory defined in the BBS environment variable. Temporary Full path to the directory where all the temporary files are stored. Swapping If swapping to disk has been enabled this directory will be used to store the temporary swap file. Semaphore This is one of the most important directories used by FDMGR. FDMGR will store all the semaphore file in this directory and if no directory for a file defined in Semaphores is specified FDMGR will search the file from this directory. Filenames Editor Full path to the full screen mail reader such as FM. MsgEditor Full path to the message/file editor such as QEdit or GEdit. 8 Nodelist Full path to the nodelist compiler/manager such as FDNC. Reply msg Full path to the template file which will be used when replying to an on-line message. To use the default reply leave this entry empty. The template file can contain certain system variables. %USER% User name %FIRST% User's first name %LAST% User's last name %QUOTE% Quote the original text %VERSION% FrontDoor Manager version number %COOKIE% Pick a random cookie from COOKIE.MGR Usernet If you're using PCBoard 15.x you must define the full path to the USERNET.XXX file eg. C:\PCBOARD\MAIN\USERNET.XXX. Log file Full path to the FDMGR log file. Please see Log options to control logging. Semaphores Task status Each task can have seperate status strings and semaphore definitions. It is possible to use $TASK$ and $NODE$ variables which will be replaced with the current task/node number. Mailer alive Full path to the file which indicates that mailer is alive and running. Usually this file is FDALIVE.$TASK$. Mailer frozen When this semaphore exists mailer is frozen. Usually this semaphore is FDFROZEN.$TASK$. Mail session The existence of this file indicates that the mailer is having a mail session. Usually FDINSESS.$TASK$ is used. User on-line This semaphore was required with RemoteAccess as it creates RABUSY.$NODE$ when user is in the BBS. But if 9 you're running PCBoard or Concord this file won't be created and therefore not required. Strings These are the strings which are displayed at the node status if that has been enabled. It is possible to use certain variables which indicate different information about the node. %NAME% User name %LOCATION% User location %BPS% Connect speed %STATUS% What is the user doing currently %REMOTE% The address of the remote system %LASTCALLER% The name of the last caller Logging in String which will be displayed when a user is logging in to the BBS. Task inactive String which will be displayed when the task is inactive. User on-line String which will be displayed when the task is having a user on-line in the BBS. There're certain variables which can be used with this string. %NAME% User name %LOCATION% User location %BPS% Connect speed %STATUS% What is the user doing currently The default value User: %NAME% from %LOCATION%, %BPS% (%STATUS%) could be displayed at User: Thomas Raehalme from FCS, 14400 BPS (Browsing) If you're using PCBoard 15.x FDMGR cannot display the speed of the connection as the speed cannot be found from USERNET.XXX. If %BPS% is still being used it is only removed and not replaced with anything. Waiting call This string is used when the mailer is waiting for a call or next event. It is also possible to display the name of the last caller with the variable %LASTCALLER%. Because the name of the last caller is always from any 10 node it is reasonable to use %LASTCALLER% only with one node. Otherwise every node would display the same name as a last caller. Task frozen String which will be displayed if the task is frozen. Session String which will be displayed if the task is having a mail session. It is possible to use %REMOTE% variable to indicate the remote's node address. The default value Mail session with %REMOTE% could be displayed at Mail session with 2:220/412 FDTerminal String which will be displayed when the FDTerminal has been loaded. External utilities Toss Full path to the filename which will be executed when new mail has to be processed. This could be the batch file TOSSMAIL.BAT which was provided with FDMGR. Scan Full path to the filename which will be executed when new local/net/echomail has been entered to the message base. FDMGR provides a batch file called SCANMAIL.BAT to do message base scanning with GEcho. Files Full path to the filename which will be executed when new files have been received and all the .TIC files have to be processed. TOSSFILE.BAT will handle the file echo processing with Allfix. Import Full path to the filename which will be executed when netmail has to be imported from the netmail directory. Nodelist Full path to the filename which will be executed when one of 11 the nodelists needs to be updated. Editor Full path to the external file editor used with FDMSETUP. The external file editor can be called by pressing either F3 or Alt-E. 4.3.3 Miscellaneous Global options Mailer type Only FrontDoor supported for obvious reasons. BBS software Type of the BBS software. This release of FDMGR supports RemoteAccess 2.0x, Concord 0.01 and PCBoard 15.x. If your BBS software is not one of the above you can use USERON.EXE and SEMAFORE.EXE to create files and use FDMGR. Then FDMGR will have the minimum support for your BBS software. Active nodes Number of nodes. Display info Display information about the active nodes (which node is doing what). Install on node FDMGR can be installed as a user to one of the nodes in the BBS. Then users are allowed to write on-line messages to FDMGR and FDMGR will reply to the messages if possible. This also enables the on-line Remote Maintenance option. Screen saver How many seconds to activate the internal screen saver. To enable the internal screen saver the value must be greater or equal to 5. Multitasker FDMGR currently supports only DESQview and OS/2. If FDMGR cannot detect the multitasker automatically it is possible to force FDMGR think it's running under one of the supported multitasker. Find destination If you're using the variable %REMOTE% with System data.Semaphores.Task status.Session you must indicate how to 12 search for the remote address. FDMGR can search the address either from PASSWORD.FD or it can use it's own index file NODELIST.MGX. If you have only secured mail sessions it is wise to use PASSWORD.FD as then you don't have to compile the whole nodelist. But if you want to cover all the addresses in the nodelist you must use NODELIST.MGX which can be created with FDMNODE. Multitasker options Function keys In this menu you can define all the function keys used with FDMGR. It is possible to load an external utility or to login locally to the BBS. If $TASK$ or $NODE$ has been used with the function keys FDMGR will ask the current node number before executing any external utility. Audio control Log options FDMSETUP colors 4.3.4 Event manager Tag FDMGR has three types of events: eXternal, Execute and Script. When an external event has to be executed FDMGR will exit back to the operating system with an errorlevel defined in the current event. It is also possible to execute external utilities (.EXE, .COM, .BAT, .BTM) in an event. The internal script language is not supported in this release. The @ event may not be deleted. It is active all the time when there is no other events. Days Days when the event will be displayed. Start time Defines the start time of an event. The start time must be in 24-hour format. Length time Defines the length of the event in 24-hour format. Errorlevel Defines the errorlevel used with eXternal events. The value may be between 31 and 255. Filename 13 Full path to the filename which will be executed with Execute and Script events. 4.3.5 Export data Export various data to any device. 4.3.6 Information Information about FDMSETUP. 4.3.7 Exit to DOS Return back to the operating system. If changes have been made you'll be prompted whether or not you want to save the changes. When starting FDMSETUP for the first time changes will be saved automatically. 14 5 Nodelist As you have probably used FrontDoor for some time I see no reason why to explain the structure of the nodelists used by FrontDoor. FrontDoor Manager cannot share the FD nodelist index files because the files have been created with the help of Turbo Database Toolkit which FDMGR doesn't include. FrontDoor Manager doesn't require the existence of the nodelist. It can be set up to use the nodelists as a source when searching for the destination address but then it will only use it's internal nodelist database index file which is created with the nodelist. 5.1 FDMNODE FDMNODE is a nodelist compiler which compiles all the nodelists defined in FDNODE.CTL to a single index file. Each node will take approx. 3 bytes. About 40000 nodes will then occupy disk space only a little more than 100 kilobytes. FDMNODE needs no special configuration. It uses SETUP.MGR to find out the nodelist directory and FDNODE.CTL to incorporate nodelists. 15 6 Manager FrontDoor Manager is the brains of the product. It will control the BBS, start the external utilities at an appropriate time, handle events and much more. All the other software provided with the product are just utilities made for FDMGR. 6.1 Menus Programs <Alt-P> Message editor <Alt-E> Load the user defined mail editor/reader. Configure <Alt-C> Start the setup maintenance (FDMSETUP). Nodelist <Alt-N> Start the nodelist compiler/manager. User keys <Alt-K> Display function keys. DOS shell <Alt-Z> Temporary shell to the operating system. Type "EXIT" to return back to FrontDoor Manager. Quit <Alt-Q> Return back to the operating system. Utilities <Alt-U> Recent activity <Alt-R> Shows you the last two days of general activity, failed sessions, file requests, number of files/bytes sent and received, etc. Inbound activity <Alt-I> Invokes the inbound call (mail) history management function. Send a message <Alt-O> Send an on-line message to one of the users on-line. Lock keyboard <Alt-L> Allows you to lock the keyboard against unauthorized use. FDMGR will still perform its duties. To unlock the computer just enter the correct password. The keyboard lock password is not case sensitive. 16 Restart event <Alt-F7> Force rescan on all tasks. Mail <Alt-M> Mail queue <Alt-B> Allows you to manipulate the current FD mail queue. Undialable <Alt-V> Allows you to manipulate systems marked as undialable. Forced poll <Alt-F> Creates a priority entry in the mail queue for the specified system. If an entry for the specified system already exists in the queue, its status is set to priority. Request files <Alt-G> Allows you to create a temporary file request to the specified system. Transmit files <Alt-T> Allows you to transmit files to the specified system. System <Alt-G> Answer Temporary disable/enable Manual answer. Printer Toggle printout of incoming messages. Human callers Temporarily prevent human callers passing through. Scan messages Temporarily prevent scanning the message base. Toss mail Toggle processing of incoming mail. Process files Toggle processing of incoming files. Update nodelists 17 Toggle processing of new nodelists and nodelist updates. 6.2 Command line parameters All of the following parameters must be preceded by either a forward slash (/) or a dash (-). Command line parameters are not case sensitive which means it doesn't matter whether or not you write the letters in capitals. LOCK:<pwd> Locks the keyboard with the specified password just like in FrontDoor. The keyboard can be locked from FrontDoor by pressing <Alt-L> or by choosing Lock keyboard from Utilities in FDMGR. NOSHADOW Disables box shadows. CONFIG:<file> Forces FDMGR to use <file> as a configuration. The <file> must include a full path to the SETUP.MGR eg. C:\FDM\SETUP.MGR. 6.3 Errorlevels FrontDoor Manager can return one of the following errorlevels. 1 Internal error 2 External error (file or path missing, etc) 3 Insufficient disk space (less than 32 kB) 8 FDMGR already loaded, enter EXIT to return 10 User break 31-255 User definable errorlevels 18 8 Scripts This version of FrontDoor Manager doesn't support the internal programming language. This feature will probably be seen in FDMGR in the next version. No promises given, no promises broken. 19 7 Shareware registration FrontDoor Manager has several registration sites all around the world. Please contact your local registration site if available. If one is not available please contact the worldwide registration site in Finland. The full list of the registration sites can be found from REGSITES.LST. The Evaluation version of FrontDoor Manager does not include all the features available in the Registered version. The Evaluation version also has some limitations. o Support available only for one node. The Registered version supports up-to 250 nodes and is capable of displaying node information of the first 10 nodes. o Installing FDMGR to a one node in the BBS has been disabled in the Evaluation version. This option can be toggled in the Registered version. o SessStart and SessEnd has been disabled. These features are available in the Registered version and be defined to be executed in the beginning and in the end of a mail session. o Automatical importing of netmail messages has been disabled. If system has received new mail but not new mail packets the Registered version will start a mail importer instead. 20 8 Commercial inquiries There are two different versions available of FDMGR. One of them is the commercial version which is developed for commercial users. Commercial users are not allowed to use the Shareware version of FrontDoor Manager. Commercial inquiries should be sent to the following company: FINCOMM SYSTEMS Telephone: +358 40 545 0605 Attn. Thomas Raehalme Modem: +358 14 724 293 P.O. Box 110 FIN-11101 RIIHIMÄKI 2:220/412@fidonet.org Finland 255:3358/1@fdnet 21 9 Credits FrontDoor Manager was written by Thomas Raehalme, FINCOMM SYSTEMS. This documentation was written using DOCUMENT 1.00 by Thomas Raehalme. I, the author, would like to thank following persons: ... the beta crew, Joaquim Homrighausen, Richard Hansen, Andrew Milner, Christian Homrighausen, Pasi Talliniemi, Jörg Haberstroh, Bo Bendtsen, Roland van der Put, Toni Raehalme and Jani Lillberg. The following trademarks and brand names are property of their respective owners. Allfix Harald Harms Concord Pasi Talliniemi, Softatalli Oy DESQview Quarterdeck Office Systems FrontDoor Joaquim Homrighausen, Absolute Solutions FrontDoor Manager Thomas Raehalme, FINCOMM SYSTEMS GEcho Gerard van der Land GEdit The Developers Network Inc. GoldEd Odinn Sorensen MS-DOS Microsoft Corp. Nodelist Updater Roland van der Put OS/2 WARP International Business Machines PCBoard Clark Development Company, Inc. QEdit SemWare Corp. RemoteAccess Andrew Milner, Wantree Development Turbo Pascal Borland International Inc. 22