Magnum One

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

/ Magnum One / Magnum One (Mid-American Digital) (Disc Manufacturing).iso / d19 / pcbnet01.arc / NETMAL50.ARC / NETDOR50.ARC / NETDOOR.DOC < prev next >

Wrap

Text File | 1990-12-30 | 22.5 KB | 598 lines

NetDoor Version 5.0 HUB Door System for NetMail by Mark J. Findlay Home Dba BBS (206) 789-9302 HST 19.2 (WASEA) Copyright (c) 1989, 90 All Rights Reserved Disclaimer. The author makes no warranties expressed or implied as to the quality or performance of this program. The author will not be held liable for any direct, indirect, incidental, or consequential damages resulting from the use of this program. Your use of the program constitutes your agreement to this disclaimer and your release of the author from any form of liability or litigation. We are continuing our full support of the NetMail system and are constantly working to improve our product to suit the needs of the users. Many of the upgrades to NetMail since its original release are due to user's comments and suggestions for improvement. We also provide FREE 24 hour support to ALL Home Dba Software users regardless of their registration status via our support board (Home Dba BBS) as well as the HOMEDBA conference carried by systems throughout the United States. Table of Contents. NETDOOR.ZIP Contents ............................... 1.0 Files Included with NETDOOR.ZIP ............... 1.1 Files Created By NetDoor ...................... 1.2 Multi-Node Processing and NetDoor ............. 1.3 Setup .............................................. 2.0 HUB Responsibility : Assigning Conf Names ..... 2.1 Directories ................................... 2.2 Updating DOORS.DAT ............................ 2.3 Adjusting the NETDOOR batch file .............. 2.4 Other Required Programs ....................... 2.5 Before Running NetDoor ........................ 2.6 Running NetDoor .................................... 3.0 When a NODE calls ............................. 3.1 Security : BBS.NET ............................ 3.2 PCBoard Caller Log ............................ 3.3 When a NODE Changes Configuration ............. 3.4 Deleting a NODE from the Network .............. 3.5 Unattended Logging of NetDoor Operation ....... 3.6 PCBoard Events ................................ 3.7 How to Get Additional Help ......................... 4.0 Help in Finding/Joining a NetMail Network .......... 5.0 Other Programs From Home Dba Software .............. 6.0 Acknowledgements ................................... 7.0 Page 1 1.0 NETDOOR.ZIP Contents. 1.1 Files Included with NETDOOR.ZIP. The following files should be contained in your NETDOOR.ZIP file: NETDOOR.EXE - NetDoor executable file. NETDOOR.CNF - NetDoor config file. NETDOOR.DOC - This document. NETDOOR - NetDoor batch file. If your NETDOOR.ZIP file is missing any of these files, please contact Home Dba BBS at (206) 789-9302 (WASEA). You may always download the most recent version of NetMail from the support conference there. 1.2 Files Created by NetDoor. NetDoor will create new files not included with the original NetMail/NetDoor package, in order to help in the processing of calling nodes. <BBSCODE>.HST : NetDoor will create this file and maintain it for each calling node. <BBSCODE> represents the 1 - 8 character unique identifier for the calling node. This file contains a history of the calling node's last successful mail transfer, in the form of last message numbers processed for each conference carried by the calling node at the time of the last successful call. With this information, NetDoor can prompt calling nodes as to whether they wish to re-receive their previously received mail packet. You should not alter this file or attempt to move this file from its directory. 1.3 Multi Node processing and NetDoor. You may make this door available to as many nodes simultaneously as you wish. This door can be run concurrently by any number of callers. Remember that you must create a work directory for each of your PCBoard nodes. Each work directory will have a name equal to the work directory specified in your NetMail GLOBAL configuration, with an added number corresponding to the node number of each PCBoard node. For example: If your WORK DIRECTORY = C:\NETMAIL\WORK and you are operating 3 nodes, you will need to create 3 NetDoor work directories: C:\NETMAIL\WORK1 C:\NETMAIL\WORK2 C:\NETMAIL\WORK3 NetDoor will use the work directory corresponding to the node number the caller is currently on. If a NetMail node calls on your PCBoard node 2, then C:\NETMAIL\WORK2 would be the work directory NetDoor uses for that call. NOTE: IT IS ABSOLUTELY VITAL THAT YOU CREATE A SEPARATE WORK DIRECTORY FOR EACH PCBOARD NODE YOU OPERATE! 2.0 Setup. 2.1 HUB Responsibility : Assigning Conference Names. As stated in the NetMail documentation, you, as the HUB sysop must assign a unique conference name for each conference that will be networked through your HUB. This applies to ALL conferences networked through you regardless of whether or not you intend to actually carry the conferences on your BBS! Never alter or reuse these names once networking begins unless deleting the conference from your network or your nodes will not recieve their mail from that conference and you will not receive theirs. 2.2 Directories. The first step in setting up NetDoor is creating the directory in which NetDoor will reside. For the sake of order, the author recommends the creation of a separate subdirectory to house NetDoor: Example: C:\Netdoor\ Next, copy the files NETDOOR.EXE and NETDOOR.CNF into this directory or subdirectory. Place the NETDOOR file in your main PCBoard directory. See section 1.3 above to properly set up your NetDoor work directories. 2.3 Updating DOORS.DAT You will need to update your PCBoard DOORS.DAT file with the appropriate entry. If you have never configured a door before you should re-read the PCBoard documentation on the subject to completely familiarize yourself with the entire process, but as an aid in Setup configuration we will brief you on the details. Using PCBSETUP, enter the screen containing the DOORS.DAT file specification and press F2 to edit the DOORS.DAT file. Add an entry for NetDoor by adding the name of the NetDoor batch file: NETDOOR. Next, assign a security level to which the user (NODE system Sysop) will need in order to enter the door from PCBoard. NOTE: NetDoor is not designed to be a Door security system. Please specify an adequate security level to insure that only the NODE system sysops are granted access to the door. 2.4 Adjusting the NETDOOR batch file. NetDoor comes with a pre-written NETDOOR batch file which you are to place in your PCBoard executable directory. (Do not add the extention of ".BAT" to the NETDOOR file, PCBoard will take care of this when the door is entered). You may need to update the NETDOOR file depending on your configuration. Update this file accordingly based on the following example: NETDOOR file statement comment ---------------------- ---------------------------------------- echo off Do not echo to screen. cd \Netdoor Change directory to the directory housing Netdoor. SET DSZLOG=C:\PCB\DSZ.LOG Tells DSZ to create DSZ.LOG in this directory. IMPORTANT: The file MUST be called DSZ.LOG and MUST be in the same directory as parameter #2 in the following line! Since parameter #2 changes with each PCBoard node you run, each NETDOOR batch file must reflect the unique and proper location of the DSZ.LOG file. Netdoor netdoor.cnf c:\pcb c:\hubmail c:\utils c:\nodemail The above line illustrates the startup command for NetDoor. Netdoor = Startup Netdoor.exe Netdoor.cnf = Config file for NetDoor c:\pcb = This is where your PCBOARD.DAT, PCBOARD.SYS reside. NetDoor will scan these node specific files when first entered by the calling node. c:\hubmail = HUB's Main NETMAIL directory. c:\utils = PATH of your PKZIP.EXE file. NetDoor was re-written to execute PKZIP WITHOUT loading a copy of COMMAND.COM in order to save approximately 24K of memory at compression time. This 4th parameter tells NetDoor the directory that PKZIP.EXE resides in. c:\nodemail = NODE's Main NetMail Directory. cd \pcb return to the main PCBoard directory. board restart PCBoard. You must enter the parameters in EXACTLY the order presented above. NetDoor uses the HUB's NetMail directory specified to load both the HUB GLOBAL.NET file and BBS.NET files and the NODE's NetMail directory to maintain the network-wide nodelist. SPECIAL NOTE: Please be certain you make the proper distinction between the HUB`s NetMail directory and the NODE's NetMail directory. If you are operating SOLELY as a HUB (In other words, you are the National Hub and you make NO calls to any other system to transfer mail), then specify the directory where NETDOOR.EXE resides as your 5th parameter. Please note that with release 2.0 of NetMail, the HUB system no longer performs manual IMPORT or EXPORT. These functions are now written into the NetDoor and are performed automatically each time a node calls. 2.5 Other Required Programs. HUB systems MUST have PKZIP, PKUNZIP and DSZ in one of the directories included in the DOS PATH specification. NetMail and NetDoor use PKZIP and PKUNZIP at various points and NetDoor calls DSZ to receive and transmit mail packets. YOU MUST HAVE A REGISTERED VERSION OF DSZ IN ORDER FOR THE DOOR TO FUNCTION PROPERLY! NOTE: Please make an effort to coordinate similar versions of DSZ between the HUB and NODE systems. This has been found to be a problem when DSZ versions were too far apart between some HUB and NODE systems. 2.6 Before Running NetDoor. Prior to running NetDoor for the first time, you must insure that you have completed the HUB configuration process through NETMAIL and that all GLOBAL.NET and CONF.NET information (created by the global and conference configuration process) is complete. This includes the creation and verification of directories and the assignment of a unique conference names to every conference that will be processed through your HUB regardless of whether you intend on carrying the conference or not. 3.0 Running NetDoor. You are now ready to receive NODE callers. As an initial test of your NetDoor configuration, you should attempt entering the door locally from PCBoard. If your configuration is correct, you will enter the door, and, because there are at present no local functions available, be returned to PCBoard. If this happens as described, you are ready to receive calling NODES. 3.1 When a NODE calls. NetDoor provides several prompts to the NODE caller, either helping to direct operations or simply notifying the NODE of the current activity. All messages are echoed to the local HUB screen as well. One of the most important prompts your caller will receive is "Do You Wish to Re-Receive your Previous Mail Packet?". This is NetDoor's way of allowing a node to re-receive mail which might have already been successfully received during the last call. If the user answers the prompt with "N", or simply waits the ten seconds the prompt takes to time out, then mail processing will continue as normal, with the user receiving any new messages. If the user types "Y", then any mail successfully received during the previous call, as well as new awaiting the user for the current call, are packed up for the user. Another feature of NetDoor (which the caller has no direct control over) is Netdoor's ability to determine if a caller's session is abnormally terminated (loss of carrier etc.) or if a file transfer (either upload or download) was successful or not. In the case of any problems mentioned above, the caller is returned to PCBoard and no message pointers on the BBS.NET file are updated. This allows the user to call again and attempt a transfer. NetDoor is able to recognize errors in file transfers through the use of the DSZ LOG file which is defined through the use of the SET statement in each NETDOOR batch file. (See sample NETDOOR batch file below). 3.2 Security : BBS.NET NetDoor provides security through the use of the NetDoor Verification of Callers option from the NetMail Configuration Menu. (Global Information). If the HUB sysop specifies "Y" in the "Verify NetDoor Callers" option of the Global Configuration, NetDoor will, after determining the identity of a NODE calling for the first time, verify that NODEs authority by scanning BBS.NET in the main NetMail executable directory. BBS.NET is created when the HUB system is first configured through NetMail. If the security option is on and NetDoor does not find the NODE's BBS-Code in BBS.NET, the calling NODE will be notified and will not be permitted to carry on the mail transfer process within NetDoor and will be returned to PCBoard. Appropriate entries will also be made in the PCBoard Caller Log. On the other hand, the HUB system could conceiveably be configured to allow ANY AND ALL new NODE callers immediate access to the NetMail system by specifiying "N" in the "Verify NetDoor Callers" entry. When this occurs, NetDoor scans BBS.NET for the NODE entry, but if not found, automatically adds the new NODE's configuration information to BBS.NET for subsequent use. If the HUB sysop maintains a bulletin listing all conferences in the network and their conference number, and specifies a security allowing ANYONE into the NetDoor through PCBSetup, AND specifies "N" in the "Verify NetDoor Callers" field, AND configures the NETDOOR batch file for automatic non-attended HUB operation (See Sample Batch File), the HUB system could actually operate a network allowing new NODES to enter and participate in the network, without ever having made contact with the new NODE or ever needing to! While this scenario is not necessarily an ideal or suggested one, it does illustrate NetMail's power and gives you some idea for the flexibility and options you have as a HUB sysop. 3.3 PCBoard Caller Log. NetDoor reports to you on the activity of the calling NODE, not only on screen while the caller is online, but also to the PCBoard caller log for your review at a later time. Included in each entry in the caller log is: Time and Date of entry to NetDoor Calling BBS identity File transfer completions Various Error Messages Time and Date of NetDoor termination. 3.4 When a NODE changes configuration. When the NODE system calls and transfers its mail, BBS.NET is automatically updated by NetDoor with the current NODE configuration. (Which conferences the NODE is networking). This allows the NODE system to freely change the conferences it carries at any time and be insured of receiving only the conferences it is currently carrying. At no time does the HUB sysop need to make any alterations to NetDoor. 3.5 Deleting a NODE from the Network. When a NODE system is no longer part of the network run by the HUB, the HUB sysop must delete the NODE information record from the BBS.NET information file to stop any further holding or creation of that NODE's mail. This is accomplished by executing the ALT-D function from the BBS Maintenance function from within the NetMail Configuration program. After entering the BBS Maintenance screen, page through the available entries until you come to the bbs you wish to delete. Press ALT-D and confirm. A backup of the BBS.NET file will be maintained by NetMail each time you perform a DELETE of a NODE. 3.8 Unattended Logging of NetDoor Operations. Incorporated into NetMail are many ProKit routines. This means that as a HUB, you may log all NetDoor screen display activity to a collection file for later review. This can be useful if you wish to review to message activity of a node over a period of time, or wish to review the NetDoor activity which occurred while you were away from the terminal. Everything that is normally displayed by NetDoor will be written to the collection file in the NetDoor directory. The collection filename will be DEBUG1.OUT. In order to turn this function on, you must set the ENVIRONMENT variable "PRODEBUG" on by using the following command either from the DOS prompt or in your autoexec.bat: SET PRODEBUG=ON Keep in mind that with prodebug set to on, ALL programs written with ProKit routines will begin the detailed logging process. This could have a profound effect on your disk space, as well as the overall performance of your system, which is now writing to disk, nearly everthing that scrolls across the user's screen. WITH PRODEBUG SET TO ON, ALL PROGRAMS WRITTEN WITH PROKIT ROUTINES WILL BEGIN THE DETAILED LOGGING PROCESS. THIS COULD HAVE A PROFOUND EFFECT ON YOUR DISK SPACE, AS WELL AS OVERALL SYSTEM PERFORMANCE. In order to counter the effects of the disk utilization of the various ProKit program logging, you should periodically enter the subdirectories that the programs using ProKit reside, and delete the DEBUG1.OUT files that are created. By far the greatest impact will be seen by the ProDoor program. All screens displayed to the user by ProDoor will also be logged to disk! Therefore, a user browsing 100K of messages during a session would also result in an additional 100K being added to your log file. Multiply this by several callers and you can easily see the impact this environment variable can have. In order to remove the PRODEBUG=ON variable, you must either remove the SET PRODEBUG=ON command from your autoexec.bat and reboot your system, or, you may turn the variable off from the DOS command line: SET PRODEBUG= Keep in mind that just turning the prodebug variable off from the DOS command line will be ineffective if you still have the PRODEBUG=ON command in your autoexec.bat file. The next time you booted your system, the prodebug variable would be reset to ON and you would again be logging all ProKit program activity. 3.9 PCBoard Events. If a calling Node attempts to enter the NetDoor within 15 minutes of a scheduled PCBoard event, NetDoor will first check to see if the event can "slide" (that is, if the upcoming event has been defined as being able to wait until the caller logs off before starting) and if so, will let the calling Node proceed with the mail transfer. if an event is scheduled and the slide indicator has been set to "N" and the caller is within 15 mintutes of the upcoming event, the caller will be informed of this by NetDoor and will be returned to PCBoard. 4.0 How to Get Additional Help. If at any time you happen to run into problems you cannot solve or need additional information on any of NetMail's functions or simply wish to learn more about NetMail or any other Home Dba Software program, you may call our Support Board - HOME DBA BBS at (206) 789-9302 (WASEA). PLEASE MAKE ALL INQUIRIES IN THE SUPPORT CONFERENCE! When calling with problems, please upload as many NetMail files related to the problem as possible; (CONF.NET, BBS.NET etc), as well as CONFIG.SYS and AUTOEXEC.BAT 5.0 Help in Finding/Joining a NetMail Network. The support conference on Home Dba will maintain a bulletin listing all known bulletin boards networking with NetMail. You may browse and/or download this list and contact the BBS most conveniently located, for more information in joining that BBS's network. If you are already a member of a NetMail network, you may fill out the support conference questionnaire and your BBS will be added to the Nationwide NetMail Users List. 6.0 Other Programs Available from Home Dba Software. NetMail - This is the counterpart to NetDoor. This program provides both HUB and node with everthing required for complete setup and configuration into a NetMail Network. TuDoor - This DOOR allows users to view ansi/ascii tutorials forward and backwards. It was put together to get information to users who never seemed to get around to reading bulletins... know any users like that?... AnsiView - Interactive Ansi Viewing Door that allows users to view ansi screen creations interactively without having to download them first. Comes with a starter set of ansi screens.... WallyBil - Calculates and maintains shared expenses among groups of people like roommates in college etc. Maintains individual entries, allows update of entries, calculates each person's debt to the other etc. Assorted tutorials for TuDoor Door. 7.0 Acknowledgements. Special thanks and program dedication to Yani, whose patience and encouragement are outdone only by her Indian cooking! I also wish to thank all those who have helped to make NetMail the program it is today, through their many comments and suggestions for improvement.