ProfitPress Mega CDROM2 Shareware Freeware (MSDOS)(1992)(Eng)

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

/ ProfitPress Mega CDROM2 …eeware (MSDOS)(1992)(Eng) / ProfitPress-MegaCDROM2.B6I / BBS / RBBS_PC / SX227R1.ZIP / XPCFG.HLP < prev next >

Wrap

Text File | 1990-07-30 | 23.2 KB | 693 lines

[ REGISTRATION ] If you like and use this program, you are required to register your copy. Upon registration, Santronics Software will issue you an special registration code. If you are not registered, please leave this field as is. If you start to become devious by entering a false code, Xpress will begin to scratch it's head and start wondering about you. So trying to play the random game will not help. If you want to register, please see the order form. [ BOARD NAME ] The reader requires a short title of your board. It is used as a header for some of the Xpress Reader menus. Enter something like; Pitt Xpress, Pittsburgh PA. The Spring Board, 7 Springs, PA. [ SYSOP NAME ] Your name fella! Just make sure it's the same name you use on the registration form and on the board. [ OPX FILE NAME ] This is the name of your Xpress mail packet. Xpress will put the extension OPX on it. It is an identification for the BOARD using the Silver Xpress system. You may choose your own ID. 8 characters MAX. Choose a ID that is similar or familar to your board title. ie. Pitt Xpress ==> PITTX Software Connection ==> SOFTCONN Doctor's Inn ==> DOCSINN The Cat's Meow ==> CATMEOW Enchanted Forest ==> FOREST Registration of Silver Xpress makes the ID an official Xpress Board ID. Your ID will be reserved on a first come first serve basis. [ OPUS VERSION ] Use 1.10 ALWAYS!!!! OPUS 1.10 is now fully supported. This version of Xpress does not support OPUS 1.03. [ ORIGIN LINE ] Enter the origin line for your system. Xpress will append it to mail (echo only). If you leave this line blank, Xpress will ignore this line and will nothing to the mail. This allows external mail processors such as confmail to add the origin line. If you do use the origin line, please include your Fido Net number at the tail end of the line. This is for echo mail processors to handle the mail correctly. Xpress will not force the number in the line. You have to put it in. [ FIDONET NUMBER ] ZONE - Enter 1 - North America 2 - Europe 3 - Asia NET - Your FidoNet net number NODE - Your FidoNet node # within your net. You must have one to register Xpress. [ REPORT LOG ] Enter the name of a file where Xpress will record/log major happenings with Xpress. Default is xpress.log. You may wish to define the same log file as OPUS.LOG. However, keep in mind the format is not the same. [ LASTUSER FILE ] *** IMPORTANT TO THE PROPER OPERATION OF XPRESS *** Enter the full path location of the lastus??.DATs file OPUS creates when it goes outside to run an external program. The file tells Xpress all there is to know about the current user. If you run OPUS task modes, then just declare the proper lastuse01.DATs or lastuse02.DAT file., and you should set up multiple configuration files, xpmail1.ctl and xpmail2.ctl. Example; c:\OPUS\lastuse02.dat NOTE: Xpress not rewrites user last read pointer information back into this file. You must configure OPUS to reload this file. See the OPUS control file, option 165. [ SYSTEM BBS FILES ] *** IMPORTANT TO THE PROPER OPERATION OF XPRESS *** Enter the directory location where OPUS keeps the entire SYSTEM??.DAT files. These files are required by Xpress. In other words, if you use Binkley as a front end, you still need these files. This directory location is typically c:\OPUS. But then again, are you a typical kind of guy? [ WORK DIRECTORY ] This is where Xpress will place all temporary files when creating a packet or where the reply packet is uncompressed. Xpress will create this directory if it does not exist. Note: Do not place any files in this work directory. Xpress erases this directory with each usage. [ DOWNLOAD DIRECTORY ] This is where Xpress will create the OPX file or mail packet. The compression process will create the OPX here and the download process will grab the OPX from this directory. In local mode, this is where you will find the OPX file. Xpress will create this directory if it does not exist. [ UPLOAD DIRECTORY ] This is where Xpress will receive any reply mail from the user. The upload process will place the REP file here, and the expansion process will decompress the file to the work directory. In local mode, place your REP file here! Xpress will create this directory if it does not exist. [ ECHO TOSS FILE ] Enter the full path name of the ECHO TOSS file. When a user uploads a reply packet, and Xpress begins to distribute the mail to the apppropriate echo areas, it will append to the echotoss file the echotoss name. See section 3.1 of the documentation discussing the echo toss names for echo message areas. Option C of this configuration will allow you to enter the echo toss name for each echo area. If you are using CONFMAIL or some other processor, you can use the echotoss file for your mail processing. NOTE: You can also use this file as an INDICATOR to trigger OPUS scanning. See Section 2.4. [ STATISTICS FILE ] This is an optional feature. Input the full path name of a statistical file Xpress will create to record the DOWNLOAD and UPLOAD file sizes. With the Xpress utility program called XPSTATS.EXE, you can modify the user's download and upload statistics in the user.bbs file. Since this file can not be modified while a user is on, it can only be updated after he logs off. An Xpress utility called XPSTATS.ZIP is optionally available. When 1.10 support arrives, this will not be required. [ SCHEDULE FILE ] This is another feature to determine the time remaining. Xpress is designed to read two types of schedule or event formats; OPUS's SCHED.BBS (barebones) or the Xpress event format defined in the configuration program. If you choose to use OPUS's sched.bbs file, then input the full path name to this file. If you use any other frontend system, then you may use the xpress format. In this case, leave this field blank. If you do use a frontend system and want xpress to read the OPUS sched.bbs, then you must maintain it separately. If you choose the latter method, it will eliminate the need to recompile the control file every time you modify or add events. When 1.10 support arrives, this will not be required. [ DUMP PATH ] Define the directory where XPRESS will "DUMP" all messages it fails to distibute to proper mail areas. This may occur when you make drastic changes to your mail area setup and the user is not upto par with the changes. ie, he uploads a reply packet that corresponds to your old setup. This will happen only after the first time he sends his replies using the new set up. After that, his next download packet will contain the proper information. Xpress will create this directory if it does not exist. [ DUPE FILE PATH ] Define the directory where XPRESS will store it's XPDUPES.DAT file. This file will contain CRC calculations on uploaded messages by the user. If the user unknownly tries to uploaded already process replies, hopefully the dupe checker will trap the messages. In section D, the key word MAX DUPES must be defined to determine the amount of DUPE checking you want. It's Default is 1000. This NUMBER SHOULD BE MORE THAN 16K. NEVER! [ MAXIMUM DUPE CHECK ] Define the recording amount of message dupe checking. It's Default is 1000. This NUMBER SHOULD BE NO MORE THAN 8000. !NEVER! 1000 - 4000 very good for xpress. (Opus stores 4000) [ ACCEPTABLE READER VERSION ] The Xpress Reader 2.20 is compatible with this version of Xpress, however, this option will allow you to STOP users with version reader 2.20 from using your Mail System. A FUTURE version of the reader will include more features which will make it more tightly coupled with the door. Some examples of futures reader changes: o Reader will include echo tag (area names) information. o Reader will include encryption methods to stop users from screwing around with mail headers. If these changes was important to you, then you can inforce the reader upgrade on your users with this option. As of reader v2.24, this is not very important so keep it at 2.20 or 2.24 to force users to upgrade. [ NODE LIST VERSION ] Define the node list version # 5 or 6, you are using for NETMAIL processing. Xpress will use then node list to get cost information. It will put this cost in the file XPSTATS.DAT where the program XPSTATS.EXE will read and update the opus user record during post processing mode. Use version 5 or 6: 5 - OPUS 1.03 6 - any bbs with BINKLEY configured to use version 6. If for some reason during a upload process of a netmail, xpress seems to be a long search process. More than likely, you have defined the wrong number. The search should be as FAST as OPUS or Binkley searches net/node numbers or faster. [ NODE LIST PATH ] Define the node list version # 5 or 6, you are using for NETMAIL processing. Xpress will use then node list to get cost information. It will put this cost in the file XPSTATS.DAT where the program XPSTATS.EXE will read and update the opus user record during post processing mode. [ USER BASE FILE ] Define the directory where XPRESS will look for the user database file called XPUSER.DAT. This is normally the same directory as your Xpress directory. [ MAIL TRANSFER PATH ] This is the directory location of the following batch files: SENDOPX.BAT RECOPX.BAT These batch files are used for starting up the appropriate Xpress mail packet download or upload process. In these batch files, there is logic for calling any of the defined mail transfer programs such as DSZ, CLink, PCKERMIT, etc. The mail transfer definition option will allow you to define the transfer protocols you wish to have on your Xpress system. Make sure the definitions match those in the batch files. [ ARCHIVER PATH ] This is the directory location of the following bacth files: COMPRESS.BAT EXPAND.BAT These batch files are used for starting up the appropriate Xpress compression or expansion process. In these batch files, the logic for calling any of the defined archiver programs such as ARC, PKware, LH, etc. is available. The Archiver Definition option in this config program will allow you to define the archivers you wish to have on your Xpress system. Make sure the definitions match those in the batch files. [ MAIL AREA SELECTION ] Select or deselect the message area by hitting the SPACE bar. Once selected Xpress will include this area as part of the Xpress list of xpressable message areas the user may have access to. However, the area selection is not complete until you fill in area information. o Area Short Title o Xpress Access Override o Area Long Title o Area Password o Echo Name, if any o Seen-By YES/NO When you hit the <CR>, a data entry screen will appear. It is important you read section 3.1 of the Xpress sysop manual to fully understand area definitions and area security logic. [ AREA TITLE ] Define the Area titles, short and long. The short title is used for Xpress in various areas. The long title should be used for more detail. Xpress will automatically center the short title. Sample look of area titles as presented to the user. ( Local Msg ) - General Local Messages (Pri/Pub). ( Xpress Echo ) - Intl Xpress echo for Xpress users. Do not include the parenthesis around the short title. Xpress will do it for you. [ ECHO AREA? ] If the area is an echo, define the echo name for this area. Xpress will automatically append the echo name to the ECHO TOSS file for uploaded echo messages. By the way, did your know there is two echos for Xpress? OPUS_XPRESS - International User's Xpress Echo XPRESS_SYSOP - International Sysop only Xpress echo Look for them in the back bone. [ ACCESS OVERRIDE ] Use the Function keys to get the the OPUS defined access priv(s) and area title(s). Use the Xpress access override to let Xpress decide how a user will gain access to the area. A typical use for this control feature is when you don't want users to use xpress for a particular area but only thru OPUS. You do this by setting the Xpress access higher than the OPUS setting. You can do the reverse which will have the net effect as locking users using the mail areas thru OPUS, but not thru xpress. On a USER to USER priv basis, see the SYSOP-SELECTED feature in the XPUSER user maintenance program, section 4.0 option A, and Section 3.1 for area security logic. It is very important the control file is compiled if you make changes to OPUS area privs via OPUS or other system??.bbs editors. [ AREA PASSWORD ] This PASSWORD partially emulates the OPUS barricade password feature. When a user selects the area thru the Xpress door program, Xpress will prompt the user for this password. Any area can have a password. This password is not case sensitive. Do not confuse this password system with OPUS barricards. You can use the Xpress passwords for any OPUS area. Not just area 51 and above. However, You can match a true OPUS barricard password with the Xpress password to have the same overall effect for area access. [ SEEN-BY TRUNCATION ] When Xpress packs echo mail, it packs the entire message including the seen-by lines. You can have Xpress ignore the seen-by lines to reduce the size the Xpress mail packets. This is done on a per-area basis so you may select to view the seen-bys in certain echo conferences. Seen-by truncation speeds up the total download process since less mail is copied and compressed. [ NETMAIL USER ACCESS ] After given the user access to NETMAIL, you can further provide extra security by limiting some netmail features such as: Crash Mail - Immediately send mail to node File Attach - Attach a file to be sent with netmail File Request - Request a file from another system. By default, since it was never defined and this feature is new in XPCFG 2.23, it was set at DISGRACE.. CHANGE IT NOW!! [ MESSAGE LIMIT ] Enter the maximum number of new messages that can be downloaded. The limit is set to protect your hard disk from being consumed. Use these approximations to size your limit. Given: Average 1.5k per message including seen-bys. Using PKZIP with a 50% compression. 240 Xpress msgs correspond to 540K of disk space required. 480 Xpress msgs correspond to 1080K " " " 720 Xpress msgs correspond to 1620K " " " Example: if you wish to allow 600 msgs as the limit, then (600*1500) + (600*1500*.50) = 1,350,000 bundle compressed should be reserved for Xpress mail bundling and compression. [ RESPONSE TIMEOUT ] This feature allows a timeout for users who do not respond to the system between key strokes. A response time of 0 secs will disable the response timeout feature. [ PROMPT TIME ] This parameter will set the delay for 'timed' prompts in Xpress. This is used in the download sessions to give the user a second chance to avoid the download. Setting this value to 0 will not provide a timed prompt and will immediately jump to the download session. [ NEW MESSAGES ] This parameter is the total number of messages a user is allowed to create with his reader. Unregistered users are allowed only to enter 10 messages. Setting it to 0 will not set a limit for registered users. [ FILE REQUEST ] This parameter is the maximum number of file requests a user can make using the reader program. Setting it to 0 will not allow file requesting. The maximum is 10 during a given Xpress session. [ SNOOPING ] This parameter allows the SYSOP to see what is going on your console. YES - turns on the snooper. NO - turns off the snooper. Note: The @ sign can be used by the sysop to toggle the snooper on-line. [ ABORT ON ^C ] ABORT when ON allows the user to ^C out of the program. I recommend keeping this OFF. [ SIGNATURES ] This parameter is an option to allow users to define SIGNATURES for the tear line. This feature is so political that I leave it up to the sysop to make the decision to use it or not. BTW, only registered users are allowed signatures. [ CARRIER DETECT ] Carrier Detect allows the program to exit if carrier detect is dropped. ON - turn on carrier detection. OFF - turn off carrier detection. (Default for local usage) Combine this with REBOOT to complete the "WATCH DOG" security. It is recommended you keep this ON and turn off the REBOOT option so that Xpress can exit gracefully to OPUS and not reboot the machine. Opus does a fine job of realizing a carrier drop and will reset itself. [ BELLS ] BELLS ON or OFF will toggle that nasty bell sound locally. ON - bells sound. OFF - bells disabled. [ REBOOT ] REBOOT allows the program to reboot the system if REBOOT is ON. ON - enables system reboot if CARRIER DETECT on. OFF - disables reboot. If CARRIER DETECT is ON, then program will just exit to the main board when the carrier drops. [ TIME LIMIT ] Set the Time Limit for each type of ACCESS priv. This should match the time limit set in your OPUS CTL file. These values are used to calculate the time remaining in Xpress. When OPUS 1.10 arrive, this will not be required. [ BULLETIN ] Input the name of the files which will be displayed to the user when he/she starts up the Xpress Reader. Think of these as welcome screens. They will be shown one by one to the user. Two types of files are supported. o Ascii/ANSI Screens These are text oriented screens that you can create with your favorite editor. The files may include ANSI commands and/or Xpress screen control dot commands. o Binary Dump Screens These are 'bloadable' or BSAVE dump screens that you may create with a program such as TheDraw or AnsiPaint. Make sure the extension for the file starts with a B like BSV. The difference between ANSI vs Binary is SPEED of display. See Section 3.2 for more detail on creating bulletins. [ PROTOCOL DESCRIPTION ] Enter a Short Decription for the Transfer Protocol. This description will be used in the design of the transfer protocol selection menu in the Xpress door user configuration section. Enter a description and hot key that users are familar with. Example: description hot key ------------------- --------- Zmodem Z Xmodem CRC X Ymodem (Xmodem 1k) Y SeaLink S [ PROTOCOL HOT KEY ] Enter the HOT KEY or LETTER that the user will HIT to select this protocol. Make sure it is UNIQUE from the other protocol definitions. Also make sure that this protocol hot key is used correctly in the SENDOPX.BAT and RECREP.BAT batch files. [ ARCHIVER DESCRIPTION ] Enter a Short Decription for the Archiver Program. This description will be used in the design of the archiver selection menu in the Xpress door user configuration section. Enter a description and hot key that users are familar with. Example: description hot key ------------------- --------- Pkzip/pkunzip Z PAK K LHARC L [ ARCHIVER HOT KEY ] Enter the HOT KEY or LETTER that the user will HIT to select this archiver. Make sure it is UNIQUE from the other archiver definitions. Also make sure that this archiver hot key is used correctly in the COMPRESS.BAT and EXPAND.BAT batch files. [ SCHEDULED EVENTS ] Schedule events. Match this with your own schedule. Fill in this information when you are not using the barebone SCHED.BBS file. Consider these events as your Z or X types, events which will force your user OUT!!! field 1 - F forced event. N - Not forced (event ignored) field 2 - day of week. (0-sunday, 6-saturday, 7-all week) field 3 - Military time for the start of the event. field 4 - rest of line is a comment example; F 7 04:58 !house cleaning F 7 05:00 !netmail hub poll F 7 07:01 !shutdown. N 6 18:01 !saturday hub poll. F 0 18:00 !sunday hub poll [ FILE DOWNLOAD AREAS ] Toggle the file areas you wish to allow users to download or file request files from. Please note Xpress will respect the access security levels based on those used in OPUS. NOTE: If the parameter FILE REQUEST LIMIT is set to ZERO, no file requesting will be allowed for the user. [ UPLOAD ERROR LEVELS ] Use these error codes for new mail scanning. There are three types of mail scanning, but only two make any sense: echo and matrix mail. Input the error levels for each type. These are cumulative depending on how mail is distributed. Example using the following numbers. LOCAL = 0 ECHO = 1 MATRIX = 2 To check for the errorlevel, you have to consider the possible combinations of ERRORLEVEL checks in your batch file. ie; IF ERRORLEVEL 3 THEN ECHO,MATRIX IF ERRORLEVEL 2 THEN MATRIX IF ERRORLEVEL 1 THEN ECHO See Section 3.0 on using this errorlevels in the XPRESS.BAT file.