Beijing Paradise BBS Backup

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

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

Wrap

Text File | 1995-08-01 | 36.2 KB | 871 lines

/▀▀▀▀▀▀ /▀▀▀▀▀ /▀▀▀ /▀▀ /▀▀▀▀▀▀ /▀▀▀▀▀ /▀▀ /▀▀ /▀▀ /▀▀ /▀▀▀▀ /▀▀ /▀▀ /▀▀ /▀▀ /▀▀ /▀▀▀▀▀▀ /▀▀▀▀▀▀▀ /▀▀/▀▀/▀▀ /▀▀ /▀▀▀ /▀▀▀▀▀▀▀ /▀▀ /▀▀ /▀▀ /▀▀ /▀▀▀▀ /▀▀ /▀▀ /▀▀ /▀▀ /▀▀ /▀▀ /▀▀ /▀▀ /▀▀▀ /▀▀▀▀▀▀ /▀▀ /▀▀ (tm) /▀▀▀▀▀▀ /▀▀▀▀▀▀ /▀▀▀▀▀ /▀▀ /▀▀ /▀▀ /▀▀ /▀▀ /▀▀▀▀▀▀ /▀▀▀▀▀▀ /▀▀▀▀▀ /▀▀ /▀▀ /▀▀ /▀▀ /▀▀ /▀▀▀▀▀▀ /▀▀▀▀▀▀ /▀▀▀▀▀▀ /▀▀▀▀▀▀▀ /▀▀▀▀▀▀ /▀▀▀▀▀▀▀ /▀▀▀▀▀ /▀▀ /▀▀ /▀▀ /▀▀ /▀▀ /▀▀ /▀▀▀▀▀ /▀▀▀▀▀▀ /▀▀▀▀▀ /▀▀▀ /▀▀▀ /▀▀ /▀▀ /▀▀ /▀▀ /▀▀/▀/▀▀ /▀▀ /▀▀ /▀▀ /▀▀▀▀▀▀▀ /▀▀▀▀/▀ PBBSFreq(tm) ─ File Request Door V1.01 Copyright (C) 1995 Bing Wu & International Meridian Company (IMC). All Rights Reserved ┌──────────────────────────────────────────────────────────────────┐ │ ▓▓▓ Features ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ │ └──────────────────────────────────────────────────────────────────┘ ■ Easy to setup. Takes less than 15 minutes ■ Reads your configuration file from InterMail and FrontDoor ■ Full screen Setup program using Pulldown menus ■ Multi-Line aware ■ Major multi-taskers supported ■ Co-SysOp with SysOp access ■ Built in User Editor {+} ■ Support of upto 50 definable File Request Systems {+} ■ File password protection {+} ■ Sends an online message in a RemoteAccess environment when the file request has been received if the user is still online. {+} ■ Sends the users a message when there file request has arrived supporting Hudson, Squish, Fido (*.MSG), EzyCom, and JAM ■ Uses it's own database file for speed searches ■ Direct support for RemoteAccess's File Data Base (FDB) ■ The ability to set message attributes of CRASH and HOLD so your routing file will only the call when you want it to ■ Non-Fossil BBS Supported ■ Internal carrier detection ■ Optional customized Main Menu {+} ■ Full detailed logging ■ Plus much more {+} Registered Only Features ┌──────────────────────────────────────────────────────────────────┐ │▓▓ OverView & System Requirements ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ └──────────────────────────────────────────────────────────────────┘ From the Features Listed above you can see that this program has all the features of a regular Online BBS Lister door but with much much more. Features marked with {+} or + is registered only feature. To run this program online on your BBS, you need to run either one of the following BBS systems or one of the compatible systems. ■ RemoteAccess 1.xx & 2.xx ■ WildCat ■ QuickBBS ■ PCBoard ■ SpitFire ■ RBBS─PC ■ Telegard ■ WWIV ■ SuperBBS ■ ProBoard ■ Any software supports either door.sys or dirinfo#.def drop file. This program fully supports and has been tested under DV, Windows, DOS, Win95 beta, OS/2. ┌──────────────────────────────────────────────────────────────────┐ │ ▓▓▓ Licensing Information ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ │ └──────────────────────────────────────────────────────────────────┘ PBBSFreq refers to all executables and text files contained in the PBBSFreq archive released by Bing Wu and International Meridian Company of Minneapolis, MN (IMC). PBBSFreq is the copyrighted material of Bing Wu and IMC. It may only be used in accordance with the following licensing conditions. 1. You may use PBBSFreq for period of three (3) weeks on a trial basis in order to determine its suitability for your system. After this period, you must register PBBSFreq or discontinue its use. 2. Commercial sites (Schools, business, or any site that conducts commercial activities) must register this program first before it can be used. 3. Registration entitles you to use PBBSFreq and any future versions of it without any future registration. 4. The products are provided as is. Neither the author nor any representative distributing this software is responsible for any damage incurred during the operation of the program. All that is promised is that it will utilize some disk space. 5. The Author (Bing Wu) and/or IMC can discontinue support and development of PBBSFreq without notice and at anytime. 6. You may not modify or otherwise reverse─engineer PBBSFreq. 7. You may not use PBBSFreq in any unlawful and/or illegal manner. 8. You are welcome to distribute PBBSFreq as long as you don't charge more than $5 for it, modify the program in anyway, or delete or add files from the original distribution archives. Distributing on CD-ROMs is welcome. 9. A Registered Version of PBBSFreq MUST not be distributed with or without the authors and/or IMC's Permission. 10. File Networks are FORBIDDEN from adding any files to the archive or change the archive type. The file must remain in ZIP format. ┌──────────────────────────────────────────────────────────────────┐ │ ▓▓▓ Registration & Support ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ │ └──────────────────────────────────────────────────────────────────┘ This program is distributed as shareware. You are granted 21 days a three (3) week trail period, after that you must either send in $25.00 registration fee or discontinue using it. All Commercial sites MUST register this program first before it can be used. Otherwise legal action may be brought against you. The $25.00 registration fee grants you to use to all future versions of this program without any additional registration fees. Your registration will be either sent to you via crash netmail or conventional mail at no extra charge within CANADA and USA. $5 charge applies for orders outside the USA and CANADA. See REGISTER.REG for more registration information. -=[ Support ]=- Echo Areas: FidoNet: RA_UTIL, SYSOP, PROBOARD, PCBOARD Official Echo: PS_SUPPORT (Available on all Panda Software support sites) Support/Distribution Site: ■ When Sending request/help to following support sites, specify how that support site should reply to your message. (ROUTE/HOLD) Author/Support: Registrations: Bing Wu @ Panda BBS! Mike Brusletten Data: 1-612-378-7783 (28,800 V34) Data : 1-612-938-3206 (28,800 V.FC) FidoNet : 1:282/1027.1 1-612-938-0558 (14,400) InterNet: wuxx0037@gold.tc.umn.edu FidoNet : 1:282/1027 InterNet: mike.brusletten@scifi.mmbbs.com Snail: Scientifica/IMC 342 18th Ave N. Hopkins, MN 55343-6909 Support Site/Beta Site: Mike McGrane Data: 1-612-537-0449 (28,800 V34) 1-612-536-9218 (14,400) FidoNet: 1:282/1024 ┌──────────────────────────────────────────────────────────────────┐ │ ▓▓▓ Files In The Package ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ │ └──────────────────────────────────────────────────────────────────┘ PBBSFREQ.EXE The main program PBFSETUP.EXE The setup program for PBBSFreq PBFMAINT.EXE The Maintenance Utility program for PBBSFreq PBFSCAN .EXE Program used to read and move inbound file(s) requests PBFIMPRT.EXE A support program to import messages. PBBSFREQ.DOC You're reading it PBFMENU.A?? Customizable menus in ASCII, ANS, AVATAR {+} PBBSFREQ.A?? PBBSFreq logon screen BADFILE.PBF Definable filelist of files you DON'T want imported {+} PBFHELP.A?? PBBSFREQ help file BETATEST.APP Application form for joining Panda Software BETA test team REGISTRA.REG Registration Form REGSITE.ZIP Non-North American Registration site application packet TABSREG.INF Information on how to use TABS to register doors HISTORY.DOC Development history of PBBSFreq ┌──────────────────────────────────────────────────────────────────┐ │ ▓▓▓ Configuring PBBSFreq ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ │ └──────────────────────────────────────────────────────────────────┘ The door will run in local mode with as little as 128k of memory. However when using the door within a BBS environment it is recommended that you have atleast 384k of free memory for door execution. You need to create a sub-directory to put the program files in. This can be accomplished by doing the following. C: CD\BBS MD\BBS\FREQ Substitute your actual directory name in place of the BBS. Many systems differ and no 2 are alike. Once that is done, UnZip the archive into the directory that you just created by doing the following. pkunzip pbbsfreq c:\bbs\freq Now it is best to set the ENVIRONMENT variable to where the door files are to be located. Place the following command in your autoexec.bat file. SET PBBSF=C:\<BBS DIR>\<Door Path>\ Substitute your actual bbs directory for the <BBS DIR> and your actual directory to the door <Door Path>. You will have to reboot your system for the new environment to take effect. Once that is completed you're ready to start the configuration of the File Request Door (PBBSFREQ). You will need a copy of the filelists you wish to allow FREQ's from. So make sure you have them before you start. You should be able to get a file list from most systems by FREQing FILES from the system(s) you wish to FREQ to. Note 1: You need a copy of POLYXARC.EXE to be able to extract the file_id.diz from inside the archive to import into your FDB or FILES.BBS. Which is found on most reputable BBS systems. Note 2: Do to the built in overlay files within the door you need to make the PBBSFREQ.EXE a read-only file. This can be accomplished using DOS's ATTRIB.EXE program. Change to your PBBSFREQ directory and type " attrib +r pbbsfreq.exe". This will mark the file as read-only. If you have any troubles with this please refer to your DOS documentation. PBFSetup: Configuring the door to your needs. SYSTEM SETUP: Paths: Here is where you setup all the paths that PBBSFreq will use during door runtime. It should be noted that PBFSETUP will search for an existing configuration file for both InterMail and FrontDoor and set most of the vital paths automatically for you. Hudson: The full path to your Hudson Message base. JAM : The full path and name of your JAM base you wish to use without any extension. Net-Mail: The full path to your Net-Mail directory. Door: The full path to the DOORs working directory. Swapping: The full path where to door should place it's swap file if needed during runtime. Logfile: Full path and logfile name with extension. If you use the percent sign " % " this will be translated the the node number for the node during runtime. Inbound: The full path to your Un-Secure mail directory. Sec. Inbd: The full path to your Secured mail directory. Freq File: The full path where the incoming file(s) should be moved to. Semephore: The full path and filename of your mailers semephore directory for rescaning the net-mail directory. Local Dir: The full path and filename of your dupe database. This must be in PBBSFREQ format. Note: DO NOT use PBBSFREQ.DAT as the file name. It is reserved for the request file database. It is suggested you use your node number for this. ie.. 282_1024. No extension needed. Using your own filelisting for this. *** NOTE *** In a RemoteAccess v2.xx environment this should point to the <Drive>:<Directory> of your FDB. RA Semaphore: The Semaphore path for RemoteAccess. This is used to send an online message to the user if s/he is still online when the requested file is received. Site Information: This is the basic information that the door needs. When a File Request (FREQ) is generated it will get the HOST system information for here. It should noted again that some of this vital information will be taken from your mailers configuration. System Name: Your BBS system NAME. SysOp Name : Your NAME goes here. Phone Number: Your PHONE number. Net Address: Your Network address in Z:XXX/NNNN.PP Z : is your Zone number X : is your Network number N : is your Node number. P : is your Point number Security: Reserved for future expansion. OPTIONS: System options is where you can fine tune the door to your system. Message Base Type: Valid message base types are Hudson, JAM, EzyCom and Fido (*.MSG) System Type: This is what type of file system you are using. You can choose from either RemoteAccess, ProBoard or Others. Maximum File Requests: The MAX file requests a user is allowed to make within a 24 hour period. Message Area: Area number you wish to have PBBSFREQ post a message to your user letting them know when a file has been received. (HUDSON/EyzCom) File Area: Area # in the RemoteAccess FDB you wish the description to be imported. (RA v2.xx Only) Allow Logoff: You may disallow users to logoff from within the door. Allow Paging: If you wish to chat with people in the door you may. Co-SysOp: The security of your Co-SysOp if you wish for Her/Him to override any of the setup options. Uses Fossil: If you use a Fossil driver. (Recommended) Locked Rate: The locked rate at which your fossil is locked. Valid settings are. 19200, 38400, 57600, and 115200 Time Allowed in Door: You can limit how long a person can be in the door. If you only want people allowed in the door for say 20 minutes enter 20 here. Inactivity Timer: How long a user can wait at a prompt before they are dis-connected from the system for inactivity. Days Old: How many days before PBBFMaint will delete any unsent requests. (Default = 2) {+} Cost of Request: You can charge users in kilobytes (K) how much it will cost them to request a file. Just enter the proper amount in K for this. Whenever a credit option is in use and under RA a password is generated to protect that file from being download by someone else other than the one who requested the file and paid for with his/her credits. For a Proboard system, however, the file is simply updated in PVTFILES.PRO, as for other file base (FILES.BBS) systems. If credit option is in use, a hidden feature of PBBSFreq should appear by pressing 't' key at the main menu. This will allow the user to transfer credits from his/her BBS account to the door account. Protect FREQs : The author really believes that the password and private file protection of the requested file is a fair play situation to the requester who paid with his/her credits. However you may disable this by toggling this option. {+} Colors: Here is where you can customize the colors that you and your users will see when the door is running. Choose colors that are easy to read during both day/night time hours. Paging: This is where you can define how the paging hours can be utilized. You choose the hours you wish to use. Duration: How long you wish the page bell to sound when you are paged. Paging Times: Here is where the timing can be confusing to alot of people. So we'll take a little time to show you some simple steps on using this feature to it's fullest extent. Note that the day starts at MIDNIGHT. For example: to allow paging all day on Weekends until 6am on Monday Morning, and between 8pm and 6am Monday through Friday would require the following settings : Start End Sunday : 00:00 00:00 Monday : 20:00 06:00 Tuesday : 20:00 06:00 Wednesday : 20:00 06:00 Thursday : 20:00 06:00 Friday : 20:00 06:00 Saturday : 00:00 00:00 Notice Monday, we Start at 8pm, but also notice that we had to Stop at 6am, this Stop is to stop the paging we had enabled Sunday. It's important that you understand this! MANAGER: Freq SYSTEMS: This is where we will define what system(s) we wish to make a File Request(s) from. In the unregistered version you may only have 2 systems listed as FREQable. The registered version allows upto 50 systems to be configured as FREQable. System Name: The name of the System you will allow File Requests (FREQs) to. Net Address: This system network address. List Files: The master file listing that is used to search for files. Without any extension. Hold Mail: If you wish to hold the file request until a certain time of the day or night use this option to hold the request until you wish it to go out. Valid options are Y or N. Crash Mail: If you wish to have the FREQ sent out as soon as possible set this option to yes. Valid options are Y or N. NOTE: Most mailers use a routing file and it'll be most cost advantageous to use that routing scheme instead of changing message attributes here. Hence your routing file will know what to do. Freq Filelist: The name of this systems filelist. This will allow you to FREQ an updated filelist weekly if needed. This is used in conjunction with Freq Days noted below. Security: The security level a user must have to access this systems filelist. Freq Days: The day of the week you wish to get an updated file list for this system. If the system is local every day would be a logical option. However if the system is Long Distance call once a week, bi-weekly or monthly may be enough to suit your systems needs. {+} FREQ FILES: Here is where you can do maintenance on the door queue if you haven't run PBFMAINT.EXE yet to pack the request queue. So we'll take a look at how the system works. ╔═══════════════════════════[ FREQ File Queue ]╗ ║ FILENAME.EXT SYSTEM NODE STATS DAY ║ ║ RA_202.ARJ 1:282/1024 [NEW] 045 ║ ║ PBBSFREQ.ZIP 1:282/1027.1 [REC] 045 ║ ║ FE141G1.ZIP 1:282/1027 [NEW] 048 ║ ║ SMENUS.ZIP 1:282/1024 [SEN] 045 ║ ║ MC_CBV30.ZIP 1:360/1024 [DEL] 050 ║ ╚══════════════════════════════════════════════╝ The above is a sample of FREQs pending or that have been sent, or deleted. If you need to make any changes to any of the FREQs in the queue you just move the highlight bar to that entry. From there you can press the ENTER key and toggle the status of that particular request. Valid status messages are SEN(SENT), NEW, DEL (DELETED), and REC (RECEIVED). The DAY is actually the day of the year using the Julian calander to calculate the day that the request was made. USER LIMITS: If you need to make any adjustments to the user accounts that have been using the door. In this setup portion you can make some advanced adjustments to there profile. Security : The security level for which you're going to allow users from your host program. A - D Flags : The proper flags that are used from your host program that ensures the user has access to the systems you allow File Requests to. # Freqs : The number of requests that can be made by this level. This overrides the setting used under OPTIONS>>SYSTEM Chk Flags : Check flags to make certain the user using the door has the proper access to the system you are allowing her/him to FREQ to. Cost : The cost of requesting the files for this access level. This overrides the cost setting under OPTIONS>>SYSTEM. Below is a cross reference chart on how the flags from RA convert to ProBoard and vise-versa. ┌──────────────────────────────────────────────────────────────────┐ │ ▓▓▓ Flag Cross-Reference Chart ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ │ └──────────────────────────────────────────────────────────────────┘ The following cross-reference chart will help you to easily determine which flags to use for your user records and menus using the ProBoard style (A-Z and 1-6) of flags. Note: The flag structures in ProBoard are actually no different than those in QuickBBS or RA, they are just expressed in a more "user friendly" format. ╔═══╦═══╤═══╤═══╤═══╤═══╤═══╤═══╤═══╕ ║ ║ 1 │ 2 │ 3 │ 4 │ 5 │ 6 │ 7 │ 8 │ ╠═══╬═══╧═══╧═══╧═══╧═══╧═══╧═══╧═══╛ ║ A ║ A B C D E F G H ╟───╢ ║ B ║ I J K L M N O P ╟───╢ ║ C ║ Q R S T U V W X ╟───╢ ║ D ║ Y Z 1 2 3 4 5 6 ╙───╜ A few flag examples follow: QuickBBS/RA ProBoard ─────────── ──────── A1 A C3 S D7 5 C8 X USER EDITOR: {+} If you need to make some adjustments to a users account, you can make some minor changes here. Name : The name of the user. Freqed : How many files the user has requested. On Day : What day of the year the last request was made. The format used here is using the Julian calander so the day can be converted using the following formula. day 97 would be April 7th 1995 day 200 would be July 19th 1995 day 359 would be December 25th 1995 Credit : Number of credits required for 100kb of file requests. PBBSFREQ: Installing the File Request Door. You need to set the environment variable so the door will know where it will be able to find its data files. This is accomplished by doing the following to your autoexec.bat file that was shown at the begining of this document. We will accommodate those that skipped it earlier. SET PBBSF=<drive>:\<path> If you wish to invoke the door via a type 7 batch file you should use the following as a general guideline. For RemoteAccess: Display : ; Action : Execute sub-program (Type 7) OptData : *c /c c:\bbs\freq.bat *N *M *UFreq_Door HotKey : F AutoExec : No For ProBoard: 1 2 3 4 5 1234567890123456789012345678901234567890123456789012345 ; Color : Your option HotKey : F Or your choice Function : 7 - Shell Data : *Z c:\bbs\freq.bat *# *Q *X The batch file should look similar to this for both of the above systems. D: SET PBBSF=<DRIVE>:\<PATH> ; If not set in your autoexec.bat CD\BBS\FREQ ; Change to your proper directory. PBBSFREQ /SD:\BBS\LINE%1 ; Call the door with appropriate command line. CD\BBS\LINE%1 ; Change back to the proper directory. NOTE: Do NOT put EXIT in your batch file if your using DESQView. You may close the window down and your system will end up sitting at the DOS prompt. If you wish to run from a command line type 7 you should use the following as a general rule. Make sure you have the environment variable set else the door will not know where it's files are. For RemoteAccess: Display : ; Action : Execute sub-program (Type 7) OptData : c:\bbs\freq\pbbsfreq.exe /NOOFF /sc:\bbs\node*N *M *UFreq_Door HotKey : F AutoExec : No For ProBoard: 1 2 3 4 5 01234567890123456789012345678901234567890123456789012345 ; Color : Your option HotKey : F Or your choice Function : 7 - Shell Data : c:\bbs\freq\pbbsfreq.exe /NOOFF /sc:\bbs\node*# *Q *X These are all of the command line options that can be used when loading up PBBSFreq for runtime execution. /NOOFF - No Logoff /NOPAGE - No Paging /NODATE - Do not display the compilation date of the database. /C[#] - Co-SysOp access /U[#] - Number of Credits User have in hand when entering the door. /LOCAL - Local Mode /S[PathName] - Points to the directory where the door drop file is created (i.e. /SC:\BBS\LINE1) /D[PathName] - Where PBBSFreq.EXE and its files are located. Overrides the PBBSF environment parameter if set.(i.e. /DC:\BBS\FREQ) Note: The /U parameter is used for BBS software that can pass the daily download credit via control codes. Hence using %2 in your command line configuration you should be able to pass the credits to the door. However the System Operator must make any adjustments to the users account by hand. PBFMAINT: Maintenance of the door and configuring your database. Here we need to make our databases of the systems we will allow File Requesting (FREQs) to. It should be noted here that when using the door that you try to let each System Operator (SysOp) know that you'll be allowing file requests by your users to his or her system. It's not mandatory but a courtesy. PBFMAINT CONVERT LISTNAME.EXT OUTNAME [switches] CONVERT: This will convert your file listing in ASCII format to the database format used within the door. All file listings MUST be in this format. It is a quick scan format and takes less time for the door to verify if the file is available. Here are the following command line parameters for it. LISTNAME.EXT - FULL Name of the input TEXT all file listing OUTFNAME - Name of the output file without extension /APPEND - Append current covert list to existing one /SHOW - Show file description of the converted filelist /NOHIGH - Omit High ASCII characters /C[#] - Column # of Description, 0 for 2nd line /L[#] - Line # to start importing file list /K[#] - Exclude file with size over #kb /B[#] - Read file list until line # /F[#] - Start reading file name on column # /12 - Read full 12 characters of Filename.Ext /D[+] - Treat the line starting with the character + as part of the description. The following 4 types are example formats can be used to read your file listing. PBFMAINT CONVERT PANDA.LST PANDA The above format should work with most systems. As it's pretty much a default for RA and files.bbs type systems. PBFMAINT CONVERT PANDA.LST PANDA /C31 The format above tells PBFMAINT that the description starts on column 31 of the file listing. You can tell PBFMAINT what column your listing starts on for any file list that you have. PBFMAINT COVERT PANDA.LST PANDA /L13 This format is of concern to filelist that have a header in them. It tells the program how many lines to look down before finding the first file. It starts importing from that line number in the list. PBFMAINT CONVERT PANDA.LST PANDA /C0 The last format used here says that our description starts on the 2nd line of our file list. This is due to the way PBFMAINT parses out any erroneous characters that may be used in your list format. Also, the /SHOW switch which will show you the descriptions as they are being imported into the database. It should be noted that only the first 4 lines of a description will be imported into the database. All high ASCII characters will be removed from the descriptions. You can also append one file list to another using the /APPEND switch. This will merge 2 file lists into one. Do NOT mix file lists of 2 different systems as your file requests will more then likely fail. Freq: PBFMAINT FREQ Running PBFMAINT FREQ will FORCE send filelist requests to the systems you have defined. This will ensure that you have an updated list weekly if you allow FREQs to a vary active system. It will create a file request to that system for you. If you wish to send out a file request on a defined day of week and you're registered user, you may want to define it the setup, and run PBFMAINT PACK instead. Pack: PBFMAINT PACK This option is usually used when you do your nightly maintenance on your system. It will delete all old file request that meets the criteria of DAYS OLD. It will also remove file request that have been sent and received. When registered, it will also create Filelist Requests to the systems you have defined on the day of the week or month you have defined. Also, it'll post any messages to your users whose request have not been honored letting them know that the request has failed, letting them know that they may try again. PBFIMPRT: This is the utility used by PBFSCAN and PBFMAINT to write the messages into the appropriate message base type. ie.. JAM, Hudson, EZYCom, Squish, and Fido (*.MSG). PBFSCAN: Scans your inbound directories for any received FREQs moving these file(s) to the defined directory that you will allow the user to download this file from. Place this command somewhere in the batch either before or after you process your incoming mail. It creates FILES.BBS if it doesn't exist so, then it updates the RemoteAccess FDB if using RA. In order to use the correct description for the file PBFSCAN will spawn POLYXARC and extract file_id.diz or desc.sdi and use the contents from one of these files for the file description. POLYXARC can be found on most reputable BBS systems. Notifies the user if her/his file request (FREQs) have been received by sending them a message. In RA an online message will be sent to the user notifying them that they have mail waiting, and that the file has been received. {+} ┌──────────────────────────────────────────────────────────────────┐ │ ▓▓▓ Support Files ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ │ └──────────────────────────────────────────────────────────────────┘ PBBSFREQ.???: The main title screen that is displayed when entering the door. PBFMENU.??? : With these you can create customizable screens that you can taylor to your system. Valid screens are .ASC, ANS, AVT. {+} BADFILE.PBF : If you wish to disallow certain files from being imported into your database just place them inside this file. It is read when you start PBFMAINT.EXE COVERT. You can use wildcards to cover a wider area also. Here is a sample ------- SNIP ------ *.GIF *.JPG *.A?? money.txt ------- SNIP ------ PBFHELP.??? : Information on how to use the door to it's fullest. Valid screens are ASC, ANS, AVT. ┌──────────────────────────────────────────────────────────────────┐ │ ▓▓▓ Credits ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ │ └──────────────────────────────────────────────────────────────────┘ RemoteAccess Wantree Development & Andrew Milner ProBoard Philippe Leybaert InterMail Copyright 1988-199 Scandinavian PC Systems AB & InterZone Software, Inc. Borland International Borland International, Inc. OpenDoors v5.00 Brian Pirie Borland C++, Turbo C++ Borland International, Inc. DESQview, QEMM Quarterdeck Office Systems FidoNet Tom Jennings IBM PC/XT/AT International Business Machines, Inc. MS-DOS , Microsoft C Microsoft, Inc. Squish Scott J. Dudley Turbo Assembler/Debugger Borland International, Inc. FrontDoor Joaquim H. Homrighausen "JAM(mbp)" Copyright 1993 Joaquim Homrighausen, Andrew Milner, Mats Birch, Mats Wallin. "ALL RIGHTS RESERVED." Flag conversion documentation used with permission from the ProBoard documentation. ┌──────────────────────────────────────────────────────────────────┐ │ ▓▓▓ The Beta Testers ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ │ └──────────────────────────────────────────────────────────────────┘ The following people deserve the credit for running this program to the ground on making sure all the bugs are out of it, and asking for additions when I thought there was nothing else that could be crammed into the code. In no particular order they are: Mike Brusletten, Mike McCabe, Mike Chamberlain, Kim Kha, Greg Schlagel Chris Reicks, Wade Martin, Paul Butler, Ric Schwandt, Tom Stoltz Mike McGrane, Rico Randle, Dave Ammerman