Beijing Paradise BBS Backup

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

/ Beijing Paradise BBS Backup / PARADISE.ISO / software / BBSDOORW / RFW_V110.ZIP / RFW_V110.ARJ / RFWDOCEN.DOC < prev next >

Wrap

Text File | 1991-04-15 | 47.1 KB | 932 lines

╔══════════════════════════════ ┌─────────────────┐ ║ RFC/W Remote Access │ D.I.S.P. │────┐ ║ Windowed file-list │ │░░░░│ ╟────────────────────────────── │ │░░░░│ ║ (c) 1991 Robert W.van Hoeven │ Dutch │░░░░│ ╟────────────────────────────── │ Independent │░░░░│ ║ Release : 1.10 │ ShareWare │░░░░│ ║ Rel.Date: 14th April 1991 │ Programmer│░░░░│ ╠══════════════════════════════ └─────────────────┘░░░░│ ║ | │░░░░░░░░░░░░░░░░░│ ║ │ RFC.EXE / RFCCFG.EXE | └─────────────────┘ ║ │ RFW.EXE / RFWCFG.EXE | ┌─────┐ | ║ │ | │░░░░░│ | ║ │ | └──┬──┘ | ║ │ Lines starting with '│' are | ┌────┴────┐ | ║ │ changes from version 1.04 ! ------││││││ ═══│------- ║ └─────────┘ ╠═══════════════════════════════ ║ Address: Robert W. van Hoeven ║ PO. Box 131 ║ 1170 AC Badhoevedorp ║ Nederland / Holland ╚═══════════════════════════════ ┌───────┬─────────────────────────────────────────────────────────────┐ │ 0 │ Table of contents │ └───────┴─────────────────────────────────────────────────────────────┘ 1 ---- General information 1.1 Copyrights and License Agreement 1.2 Newer versions and contacting the author 2 ---- Package description and requirements 2.1 Preface 2.2 Requirements 2.3 Included files 2.4 History 2.5 Multitaskers 3 ---- Installation description 3.1 Installation 3.2 Install RFC 3.3 Install RFW 3.4 BBS menu options 4 ---- Runtime information 4.1 Calling RFW 4.2 FileDoor/DISP-compatible tag-file <tm> 5 ---- Version information and credits 5.1 The BETA-team 5.2 Credits 5.3 Version history 5.4 Copyright, Trademarks ┌───────┬─────────────────────────────────────────────────────────────┐ │ 1 │ General information │ └───────┴─────────────────────────────────────────────────────────────┘ │1.1 Copyrights and License Agreement │──────────────────────────────────── │- Users of the RFW-package must accept this disclaimer of warranty: │ │- The RFW-package is supplied as is. The author disclaims all │ warranties, expressed or implied, including, without limitation, │ the warranties of merchantability and of fitness for any purpose. │ The author assumes no liability for damages, direct or consequential, │ which may result from the use of the RFW-package; │ │- The RFW-package is a "shareware program" and is provided at no charge │ to the user for evaluation. Feel free to share it with your friends, │ but please do not give it away altered or as part of another system. │ The essence of "user-supported" software is to provide personal │ computer users with quality software without high prices, and yet to │ provide incentive for programmers to continue to develop new products. │ │- If you find this program useful and find that you are using and │ continue the use of the RFW-package after a 30 days trial period, │ you must register the RFW-package as described below; │ │- Non-commercial users will get a license for the usage of RFW by │ sending a postcard or letter as registration. Non-commercial users │ are FREE to use RFW on their system(s) without paying any fee. A │ 'closed BBS' (a BBS where users have to pay for using the BBS) is │ NOT a non-commercial user; │ │- Closed BBS's (a BBS where you have to pay to get access to the │ BBS) can get a Closed-BBS license for a small amount of money. │ All users that are registered before April 1th 1991 (postcards, │ letters or NetMail received by me before April 1th 1991) and that │ run a Closed BBS, get their license for free. See REGISTER.RFW │ for details; │ │- Commercial usage of RFW will cost somewhat more. A company using │ RFW needs a commercial license. See REGISTER.RFW for details; │ │- The registration of the RFW-package will license ONE copy for use on │ any computer at any one time, as long as the usage confirms to the │ type of registration you have done (so NON-commercial usage when you │ have a non-commercial license); │ │- Anyone distributing the RFW-package for any kind of remuneration must │ first contact the Author at the address above for authorization. │ │- You are encouraged to pass a copy of the RFW-package along to your │ friends for evaluation. Please encourage them to register their │ copy if they find that they can use it; │ │- Support on RFW, is available by means of written letters or by │ entering the international echomail area DISP; │ │- Problems and suggestions can be entered in the FidoNet <tm> Echomail │ conference <tm> called DISP (international). Entering this echo does │ not exclude you of the duty to register the RFW-package, though users │ who evaluate the product can enter the echo for questions; │ │- The RFW-package, all programs, the documentation and support-files is │ copyrighted 1991 by Robert W. van Hoeven, PO. Box 131, Badhoevedorp │ 1170AC, Holland. All rights are reserved. You may copy this package │ for backup purposes. Also you may copy and share unmodified copies of │ the whole package, providing that the copyright notice is reproduced │ and included on all copies. │ Excluded from this statement are the support-files written by other │ authors. Please refer to the documentation of these programs for │ copyrights and license agreements; │ │- It is forbidden to modify, adapt, translate, reverse engineer, de- │ compile and/or disassemble the software in the RFW-package. Patching │ the medium at places that carry the software is seen as a program │ change and is also forbidden; │ │- Performing any of the illegal actions as stated in the previous │ lines, is a theft and no fair play to the author and, more important, │ to the registered users; │ │- Bulletin Board Systems that distribute the RFW package can convert │ the WHOLE package to any archive-system they like but all original │ files must be included in the new archive. The RFW-package on the │ Bulletin Board can contain at the most 2 extra files. These files │ can only be a commercial for that Bulletin Board and/or validation │ data that is presented as a service to all users and shall have no │ other functions; │ │- After the normal trial period of 30 days, you must register the soft- │ ware (see REGISTER.RFW) or you must remove it from your PC; │ │- Comments, suggestions and bug reports are welcome and will be answered │ as soon I have the time to do so. You can send me a letter of leave a │ NetMail <tm> message named to Rob Van.hoeven (mind the point) on node │ 2:512/100 (RA Support, Monster, Holland, SysOp is Reinier de Groot). │ When you want to send me normal mail, address it to: │ Robert W. van Hoeven, PO. Box 131, 1171 AC Badhoevedorp, Holland; │ Also you can enter messages in the FidoNet <tm> DISP Echomail <tm> │ area; │ │ │1.2 Newer versions and contacting the author │──────────────────────────────────────────────────────────────────────── │The newest version of RFW is always available at the DISP-HQ on node │2:512/100. RFW is also distributed thru a number of DISP support nodes. │You can obtain RFW in four different ways: │ │- Logging on at DISP-HQ or a support node │ │ All zones : 2:512/100 (Multiline Paradise NL ) DISP-HQ │ (Sysop: Reinier de Groot) │ │ For zone 1: 1:203/988 (Amber Shadow USA ) Support & beta │ (Sysop: Dave Overton ) │ │ For zone 2: 2:280/216 (Sirex NL ) Support & beta │ (Sysop: Gerry Ulrich ) │ 2:242/4 (GOLEM Meerbusch FRG ) Support & beta │ (Sysop: Hanstheo Wolf ) │ 2:244/12 (FunBoard Felbert FRG ) Support & beta │ (Sysop: Dirk Astrath ) │ │ The BBS's above will always have the most current version of RFW │ available. Also, in some cases, it is possible to request the │ newest RFW with a standard file-request (ask the SysOp in question). │ On 2:512/100 you can use RFWNEW as magical name to Freq. the newest │ version. │ The actual DISP-HQ is point 2:512/100.5, but this is a closed system │ and can not be accessed from the 'outside'). You CAN address netmail │ to this point though ! │ │- Logging on to a SDS node │ MTA is distributed thru SDS/SDN, but only big minors (x.10, x.20 and │ so on) and majors (14.01, 15.01 and so on) are submitted to the SDS │ distribution point in Holland; │ │- Logging on to your own BBS; │ Chances are, that you will find an older version (international │ users) because it will take some time for the new version to │ 'bleed' thru the net; │ │- Update service; │ You can enter a special update service (read REGISTER.RFW). │ │ │If you think you have found problems in RFW, or in any other case, │you wish to contact the author, you can send me: │ │- A letter to the address you can find in the header of this file; │- A NetMail <tm> message to Rob Van.hoeven (please mind the point │ between Van and Hoeven) at 2:512/100 or (better) 2:512/100.5; │- A Message in the FidoNet <tm> DISP echomail <tm> area; ┌───────┬─────────────────────────────────────────────────────────────┐ │ 2 │ Package description and requirements │ └───────┴─────────────────────────────────────────────────────────────┘ 2.1 Preface ──────────────────────────────────────────────────────────────────────── This program is developed as a stand-alone file-lister with windowing (full screen) capacity. It does NOT depend on the QF series, like the │QFF program. It can only be used in a Remote Access <tm>, QuickBBS <tm> │or SBBS <tm> environment. RFW will be VERY effective in multi-tasking environments and on BBS's with a large number of files/file area's because RF will not (each time it is called) search in the area's itself, but uses a pre-com- piled list. Access to this list is at (almost) optimum speed. 2.2 Requirements ──────────────────────────────────────────────────────────────────────── RFW requires: - PC XT/AT/386/486 │ - At least 160K free memory; - DOS 3.xx and higher; (tested with 4Dos 3.02, should work with lower versions); - HDU optional - A Bulletin Board System. Directly supported are the QuickBBS, SBBS and Remote Access types; 2.3 Included files ──────────────────────────────────────────────────────────────────────── │The package includes : RFW.EXE The main lister program │ RFWCFG.EXE Configuration program for RFW │ RFC.EXE The main compiler program │ RFWCFG.EXE Configuration program for RFC │ RFWHLP.ANS Example help-file for ANSI users │ RFWHLP.ASC Example help-file for ASCII users 2.4 History ──────────────────────────────────────────────────────────────────────── My current file-lister (QFF) is only usable along with the complete QF-series programs (500K). Some people don't use the main programs on this series (a pitty) but only QFF. To download the whole QF-series only for a file-list is somewhat overdone. I have created a full-screen file-list in the QF-series (QFW) but this program can only execute at fast speed with QF's (2.xx) database struc- ture and this version is not released yet. On a normal FILES.BBS, QFW will give a very poor performance but this program (RFW) uses a pre- compiled database and selects the lines to be displayed from this file. I find this program a nice 'intermediate' program between QFF V 1.57 and the up comming QFD V 2.01. QFV/D V 2.01 will take some months to be released. RFC/W keeps up the FILES.BBS compatibility AND the extension that QFV and QFC can create (extra comment-lines on files). 2.5 Multitaskers ──────────────────────────────────────────────────────────────────────── RFW is aware of multitaskers. When SHARE is loaded (and even when it isn't), RFW will share the pre-compiled database with other (concur- rent) RFW tasks. RFC (the compiler) will use the database on an exclu- sive basis, so you need to run the compiler somewhere in an event. ┌───────┬─────────────────────────────────────────────────────────────┐ │ 3 │ Installation description │ └───────┴─────────────────────────────────────────────────────────────┘ 3.1 Installation ──────────────────────────────────────────────────────────────────────── Installation is made simple. You must use the two configuration pro- programs to make a patched version of the original programs. You can use the CFG-programs to alter the current version without having to │install options again and you can use the main programs to type-out │a new configuration when a new version is released. Installation is as follows: - Put RFC.EXE somewhere on your hard-disk; - Put RFCCFG.EXE in the same directory; - Change to this directory and run RFCCFG (see below); - Put RFW.EXE somewhere on your hard-disk; │- Put the RFWHLP.??? files somewhere on you harddisk, on the DOS-path │ or along with RFW.EXE in the same directory (access depends on the │ installation of RFW0; - Put RFWCFG.EXE in the same directory; - Change to this directory and run RFWCFG (see below); - Add RFC.EXE somewhere in your batch file that runs your BBS (an event) and/or behind the program that you use to alter the FILES.BBS files; - For fastest access you can put the compiled files somewhere on a RAM-disk, but make sure you created these files first on a fixed disk; - Put RFW.EXE in a type 7 at locations where you want to replace your current files-list with this program (so at files-list, new-files, keyword-search and file-search) as described be- low; RFC.EXE makes two files (a compiled file-list and a compiled area list). RFC can (optionally) create temporary files first and when ready, RFC will move these files over the old version. In this case you can run RFC almost any time, also when the BBS if active and users use the file-list. RFC will take the area-file and compiles a list with records to be dis- played later. All extra info (like security level, area name, flags and │so on) is imported into the compiled list. Also CD-ROM (alternate files │area's) are supported in RA 1.xx and RA 0.xx mode. When installing for the first time, you must run RFC from the command- line first to get a database. Later, in the event, a new list will be created from inside the batch-file or after you have altered the files in FILES.BBS. RFW takes the compiled lists and creates a sub-list (depending on the task-number) in memory, EMS, XMS or disk, depending on the resources and the length of the list. The creation of a sub-list is needed be- cause only at execution-time of RFW, RFW knows the security level and flags (and chosen option for that matter) and creates the sub-list with this information. BUT only the compiled list is accessed on a very fast speed and not all individual files each. It should be clear that RFW.EXE points to the same files as RFC.EXE has created, also ensure that the files are compiled at least every day otherwise your users won't see new files for a long, long time. 3.2 Install RFC ──────────────────────────────────────────────────────────────────────── Both RFC and RFW have to be installed first, because it is almost sure that you can not use the supplied defaults (except the colors). When you start RFCCFG.EXE, you will get the following questions: │╒══════════════════════════════════════════════════════════════════════════════╕ ││ You can now select the type of BBS you run RFC on. Currently there │ ││ are four types supported, QuickBBS <tm>, Remote Access 0.xx /1.xx │ ││ and SBBS. │ ││ NOTE : Use <ESC> to abort installation and read documentation !! │ ││ │ ││ You can enter the following types: 1 - QuickBBS <tm> │ ││ 2 - Remote Access <tm> Rel 0.xx │ ││ 3 - Remote Access <tm> Rel 1.xx │ ││ 4 - SBBS <tm> │ ││ │ ││ Type of BBS RFC will assume : 3 │ │╘══════════════════════════════════════════════════════════════════════════════╛ │RFC needs to know the type of BBS you are running. This information is │needed to read the proper area-file and it's layout (FILES.RA in two │flavours, FLSEARCH.BBS). It must be the same type you supply to RFWCFG. ╒══════════════════════════════════════════════════════════════════════════════╕ │ Drive, path and name for area-file to use : D:\BBS\RAX\FILES.RA │ ╘══════════════════════════════════════════════════════════════════════════════╛ This field must point to (one of your) area-files. RFC will take this │file to create the compiled list. In general, use the FILES.RA for a │Remote Access <tm> BBS or the FLSEARCH.CTL for both QuickBBS <tm> or │SBBS <tm>. │ │╒══════════════════════════════════════════════════════════════════════════════╕ ││ Drive, path to alternate FILES.x files (CD-ROM) : D:\BBS\RAX\FIL\ │ │╘══════════════════════════════════════════════════════════════════════════════╛ │This question will only be asked when you use a RA 1.xx (and higer) │type of BBS (not for RA 0.xx). This directory must point to the same │directory you have installed with RACONFIG and that point to the │directory where alternate FILES.n (where n is the file-area number) │are stored; ╒══════════════════════════════════════════════════════════════════════════════╕ │ Drive, path and name for compiled file (CMP): D:\BBS\RAX\RFC.CMP │ ╘══════════════════════════════════════════════════════════════════════════════╛ This field must contain the name of the compiled files-list. This field must point to the same file as supplied in RFW.EXE. You must supply the full drive, path and name otherwise RFCCFG.EXE will complain. ╒══════════════════════════════════════════════════════════════════════════════╕ │ Drive, path and name for compiled area-file (ARE): D:\BBS\RAX\RFC.ARE │ ╘══════════════════════════════════════════════════════════════════════════════╛ This field must contain the name of the compiled area-list. This field must point to the same file as supplied in RFW.EXE. You must supply the full drive, path and name otherwise RFCCFG.EXE will complain. ╒══════════════════════════════════════════════════════════════════════════════╕ │ Use original files only a short moment [Y/N] : Y │ ╘══════════════════════════════════════════════════════════════════════════════╛ If you supply a 'Y', RFC will compile $$$RC$$$.CMP and $$$RC$$$.ARE in the current directory first and after compilation is ready, it will delete the original files and move these files to the right place and with the right name. Make sure you have enough space on your hard-disk because you need the full amount of space the compiled files use,twice. 3.3 Install RFC ──────────────────────────────────────────────────────────────────────── Both RFC and RFW have to be installed first, because it is almost sure that you can not use the supplied defaults (except the colors). When you start RFWCFG.EXE, you will get the following questions: │╒══════════════════════════════════════════════════════════════════════════════╕ ││ You can now select the type of BBS you run RFW on. Currently there │ ││ are four types supported, QuickBBS <tm>, Remote Access 0.xx /1.xx │ ││ and SBBS. │ ││ NOTE : Use <ESC> to abort installation and read documentation !! │ ││ │ ││ You can enter the following types: 1 - QuickBBS <tm> │ ││ 2 - Remote Access <tm> Rel 0.xx │ ││ 3 - Remote Access <tm> Rel 1.xx │ ││ 4 - SBBS <tm> │ ││ │ ││ Type of BBS RFW will assume : 3 │ │╘══════════════════════════════════════════════════════════════════════════════╛ │The same question as with RFCCFG.EXE. Look into the previous chapter ! ╒══════════════════════════════════════════════════════════════════════════════╕ │ Drive, path and name for compiled file (CMP): D:\BBS\RAX\RFC.CMP │ ╘══════════════════════════════════════════════════════════════════════════════╛ Must be the same name as you supplied in RFCCFG.EXE. ╒══════════════════════════════════════════════════════════════════════════════╕ │ Drive, path and name for compiled area-file (ARE): D:\BBS\RAX\RFC.ARE │ ╘══════════════════════════════════════════════════════════════════════════════╛ Must be the same name as you supplied in RFCCFG.EXE. ╒══════════════════════════════════════════════════════════════════════════════╕ │ Drive, path and name for ANS help-file or EMPTY : │ ╘══════════════════════════════════════════════════════════════════════════════╛ │You must use your own HELP-files. This option must point to the name │location of the help-file for ANSI-users. If you leave this option │empty, RFW will search for RFWHLP.ANS (or RFWHLP.ASC) in one of the │following locations: │- Current directory; │- Directory where RFW.EXE is stored; │- Dos-path; │If an ANS-file is not present, RFW will try to search for an ASC-file. │ │╒══════════════════════════════════════════════════════════════════════════════╕ ││ Drive, path and name for ASC help-file or EMPTY : │ │╘══════════════════════════════════════════════════════════════════════════════╛ │See previous question. │ │╒══════════════════════════════════════════════════════════════════════════════╕ ││ Drive and path to location of tag-file or EMPTY : D:\BBS\RAX │ │╘══════════════════════════════════════════════════════════════════════════════╛ │With the release of FileDoor 2.xx a new type of file is introduced to │support the tag-function of FileDoor. This FileDoor/DISP-compatible │file must be created in a certain directory. This must be the same as │your FileDoor.CFG configuration points to. If you leave the entry empty │RFW will not use tagging at all. ╒══════════════════════════════════════════════════════════════════════════════╕ │ Do you want scrolling and no clear-screen [Y/N] : N │ ╘══════════════════════════════════════════════════════════════════════════════╛ You can choose from either two options: - The screen is will clear before the next screen is drawn. This is the fastest option and most SysOp's will use it I imagine. In this case you supply a 'N'; - The screen is redrawn OVER the current screen. This is the same as a normal DOS application but because of the low speed (2400 and less) this can look a bit messy. In this case you use a 'Y'; ╒══════════════════════════════════════════════════════════════════════════════╕ │ Do you want a top-ruler (start of list) [Y/N] : Y │ ╘══════════════════════════════════════════════════════════════════════════════╛ You can choose to display 'TOP OF LIST' as a ruler. If you don't want this, you must supply 'N'; ╒══════════════════════════════════════════════════════════════════════════════╕ │ Do you want a bottom-ruler (end of list) [Y/N] : Y │ ╘══════════════════════════════════════════════════════════════════════════════╛ You can choose to display 'BOTTOM OF LIST' as a ruler. If you don't want this, you must supply 'N'; ╒══════════════════════════════════════════════════════════════════════════════╕ │ Only use specified /A for search and new [Y/N] : N │ ╘══════════════════════════════════════════════════════════════════════════════╛ Normally you only have to supply /A when you use RFW as a multiple choice list ('do you want to list, search, list new files') or when you only want to list files. If you want the /A also to work WITHIN newfiles and the search, you must supply a 'Y'. In this case a search will only be conducted in the area you supplied with /A. The same goes for new-files. By default you should use 'N' in this option unless you know what you are doing. ╒══════════════════════════════════════════════════════════════════════════════╕ │ Date format to use (use d/D/m/M/y/Y and sep.char): mm/dd/yy │ ╘══════════════════════════════════════════════════════════════════════════════╛ You can supply the date-format in the files-list. Any combination (within 8 characters and using the supplied characters) is valid (yy/mm/dd, mm-dd-yy, yy:dd:mm and so on). Be sure to include 8 characters, otherwise the file-list can be somewhat shifted at several places (only when you use multiple line comments). A capital character means 'suppress leading zero' a lower-case character means 'display leading zero'. ╒══════════════════════════════════════════════════════════════════════════════╕ │ Color for headers ( low) : <TEST> Blink: N │ │ Color for headers (high) : <TEST> Blink: N │ │ Color for header-1 : <TEST> Blink: N │ │ Color for header-2 : <TEST> Blink: N │ │ Color for header-3 : <TEST> Blink: N │ │ Color for header-4 : <TEST> Blink: N │ │ Color for header-5 : <TEST> Blink: N │ │ Color for top-ruler : <TEST> Blink: N │ │ Color for bottom-ruler : <TEST> Blink: N │ │ Color for art-work/comments : <TEST> Blink: N │ │ Color for filename : <TEST> Blink: N │ │ Color for filesize : <TEST> Blink: N │ │ Color for filedate : <TEST> Blink: N │ │ Color for file-comment : <TEST> Blink: N │ │ Color for new files : <TEST> Blink: M │ │ Color for error messages : <TEST> Blink: N │ │ Color for area-separators : <TEST> Blink: N │ │ Color for help-line ( low) : <TEST> Blink: N │ │ Color for help-line (high) : <TEST> Blink: N │ ││ Color for tag-option letter : <TEST> Blink: N │ ││ Color for tagged file char : <TEST> Blink: Y │ ╘══════════════════════════════════════════════════════════════════════════════╛ You can alter ANY (except the local information window) color in the list. For every option you can select one of 128 different color combinations. Use N to see the next, P to see the previous and T to go to the first (black) color in the list. Use ENTER to select the color and then use 'Y' or 'N' to select if you want this field to blink ! 3.4 BBS menu options ──────────────────────────────────────────────────────────────────────── RFW needs to be installed in a type 7 (or 15) in the BBS menu(s). RFW needs some command-line options to do its work. These are: ╒══════════════════════════════════════════════════════════════════════════════╕ │ /A[area to display] │ ╘══════════════════════════════════════════════════════════════════════════════╛ /A is only needed with /LF but can always be supplied (if this makes it more transparent to you). Only when you select a special option in RFWCFG.EXE, /A has a meaning with all other options than /LF (see above). You must include the same path as you have supplied in the FILES.RA file. So if all your paths are without a drive-letter, you must also leave the drive-letter out overhere. It is better to use the standard RA <tm> option *0 because this is the same path/area as in FILES.RA. So by default, use /A*0 in your type 7 or 15 menu record. (*0 works only with RA 0.03 and up !). ╒══════════════════════════════════════════════════════════════════════════════╕ │ /N[line] │ ╘══════════════════════════════════════════════════════════════════════════════╛ This option is important when you run a multi-line BBS. Include /N*N in your type 7 or 15 if this is the case. If you forget this option, two concurrent RFW programs, could use the same EMS/Disk-space when they are running, causing a mess on the screen and a hangup of your machine. ╒══════════════════════════════════════════════════════════════════════════════╕ │ /LF (*) see below │ ╘══════════════════════════════════════════════════════════════════════════════╛ When you supply this option, RFW will get into 'list files' mode and needs a /A to perform its task. Only files in the supplied area are listed. ╒══════════════════════════════════════════════════════════════════════════════╕ │ /NF (*) see below │ ╘══════════════════════════════════════════════════════════════════════════════╛ When you supply this option, RFW will get into 'list new files' mode. /A is not needed unless in special cases (see RFWCFG.EXE). ╒══════════════════════════════════════════════════════════════════════════════╕ │ /KS (*) see below │ ╘══════════════════════════════════════════════════════════════════════════════╛ When you supply this option, RFW will get into 'search for keyword' mode. /A is not needed unless in special cases (see RFWCFG.EXE). ╒══════════════════════════════════════════════════════════════════════════════╕ │ /FS (*) see below │ ╘══════════════════════════════════════════════════════════════════════════════╛ When you supply this option, RFW will get into 'search for files' mode. /A is not needed unless in special cases (see RFWCFG.EXE). ╒══════════════════════════════════════════════════════════════════════════════╕ │ /KF (*) see below │ ╘══════════════════════════════════════════════════════════════════════════════╛ When you supply this option, RFW will ask a question to the user if she/he want to go into search-keyword or search-files mode. /A is not needed unless in special cases (see RFWCFG.EXE). │╒══════════════════════════════════════════════════════════════════════════════╕ ││ /ASC │ │╘══════════════════════════════════════════════════════════════════════════════╛ │You will force RFW to use ASCII displays when you insert this option ! │ │╒══════════════════════════════════════════════════════════════════════════════╕ ││ /CFG │ │╘══════════════════════════════════════════════════════════════════════════════╛ │When /CFG is used on either RFC or RFW, the program will write a │configuration-file. This file can be used by RFWCFG and RFCCFG to │add the old information to any new release. RFC or RFW will stop │after the .CFG file is written; ╒══════════════════════════════════════════════════════════════════════════════╕ │ (*) now for something special │ ╘══════════════════════════════════════════════════════════════════════════════╛ If you supply neither /LF, /NF, /KF, /KS or /FS, RFW will ask the user what to do. The user can now select from any of the option and RFW will perform this task. Because the user (at any time in the list) can force RFW to go back to the start (to ask a new mask or date for new-files), this is a powerful option. You only need one menu-item to do all file (list) access in one strike. Obvious, one of the following versions will also include a 'Change area option'. ┌───────┬─────────────────────────────────────────────────────────────┐ │ 4 │ Runtime information │ └───────┴─────────────────────────────────────────────────────────────┘ 4.1 Usage of RFW ──────────────────────────────────────────────────────────────────────── When RFW presents its list of files (if any), so after the questions that RFW (optionally asks to the user), the user can do several things. FIRST (and most important) is that the user must set his/hers NUM-LOCK to on (also when running locally). If she/he forgets this, nothing will happen unless 'Q', '?','N','T', [ENTER] or [ESC] is used. Next the user can use '7' (simulate of HOME) to go to the top of the list. '1' (simulate of END) to go to the bottom of the list. These two options can also be used to redraw the screen. '8' and '2' (simulate CRSR-UP and CRSR-DOWN) can be used to scroll one line up or down at the time. '9' and '3' (simulate PGUP and PGDN) can be used to scroll one page at up or down at the time. [ENTER] can also be used as a replacement of '3' (PGDN). [ESC] will terminate the execution. '?' or 'H' will force QFW to display its own help information or the file you supplied with RWFCFG.EXE. 'N' can be used to reset RFW without leaving the program. In all modes except /LF, this option can be used to let the user enter a new selection (new search-mask or new date for new-files). If RFW runs without /LF, /NF, /KS, /FS and /KF, 'N' will force RFW to go back to the first question to ask the user the mode to run in. │'T' can be used to tag or untag files. When RFW starts, it will test │for the presence of a FileDoor/DISP-compatible tag-file. If this file │belongs to the user and was previously edited by RFW, the information │will be displayed to the user and the user can reuse (add/delete files │to the list) or delete the tag-file. │If RFW was not the last program that edited the tag-file, the user │can choose to terminate RFW or to delete the file. │If tagging is not set (e.g. RFW does not point to a directory that │will contain the tag-file), the user is left in peace and no questions │are asked. │With tagging, the user can tag/untag files from the list. Tagged │files will be stored in a list that can be used by FileDoor <tm> or │other 3th party vendor programs. At the local side, you can also enter any of the above keys AND you can enter CTRL-T to toggle RFW's information window. If this window is set to ON, RFW will re-display this window (only at the local side) with every change of the screen. If you toggle this option OFF again, you must wait until the user changes the screen before the window is gone again. The user is able to enter any key while the screen is build. This hot-key support looks much like the build-in hot-key support of RA. RFW monitors the remaining time the user is allowed in the BBS, the carrier (if carrier is lost, RFW will terminate and the BBS will take over again) and if the user is not entering any key within 2 minutes. │If you want to have current user information, you must hit the CTRL-T │button. This button toggles the status-display ! │4.2 FileDoor/DISP-compatible tag-file <tm> │──────────────────────────────────────────────────────────────────────── │With release 1.10, RFW contains a full FileDoor/DISP-compatibel tag- │file <tm> implementation. What does this mean. │ │The user is able to tag (or untag for that matter) files that she/he │would like to select from the list that RFW presents. Tagging can be │done with the <T>-key. A file already tagged can be untagged, a file │that is not tagged can be tagged (so <T> works like a toggle). │ │When the user terminates RFW, RFW will write a special kind of file. │This file is called the FileDoor/DISP-compatible tag-file. This file │has a uniform format and can be read by most door-like DISP programs │and (its primary reason of being there) by FileDoor <tm>. When the │FileDoor <tm> program detects such a tag-file, it will test if the │file belongs to the current user (if not, it will be deleted) and │the file will (or can) be used as input for the file-selection in- │side FileDoor (download/Bidirectional). RFW creates a so called auto- │tag file. This means that FileDoor will start reading the tag-file │without asking the user. The user is still able though, to select │or reject the presented choice. │ │When RFW has created a tag-file and the user enters RFW again (while │there is still a tag-file from the same user), the user has the op- │tion to reuse the tag-file or to delete it. If the file is reused, │RFW will show all files already tagged before and will keep files │from other areas inside the tag-file. The user can now change the │tagging (set it to off) or add new files. Before termination, RFW │will merge the new results in the old tag-file. In this way, the │user can scroll thru various areas and can create a combined tag- │file that can be used with FileDoor (if autosearch is set to on). │Deleting the tag-file means that the old tag-file is flushed and │(optionally) a new one is created. │ │When FileDoor <tm> has used the RFW tag-file, the auto-tag switch │is set to off. If the user enters FileDoor again, the tag-file must │be selected by hand (/TAG). │ │A description of the FileDoor/DISP-compatible tag-file is included │in the supporting programs at the moment that the internal structure │is released for public usage. In this case a file called FDTAGSTR.xxx │(where xxx is the version of the used format, currently 201) is added │to the archive. │ │Programs that will support this kind of tag-file are, MTS, RFW and │FileDoor itself. Other products can choose to use the functions of │such a tag-file. │┌───────┬─────────────────────────────────────────────────────────────┐ ││ 5 │ Version information and credits │ │└───────┴─────────────────────────────────────────────────────────────┘ │ │5.1 The BETA-team │──────────────────────────────────────────────────────────────────────── │The following Sysop's and their CoSysop's (only if they use the same │BBS or a NON-user (closed) shadow BBS) are allowed to make use of the │BETA-releases on their own risk: │ │- Remote Access Multiline/Multiport Paradise 2:512/100 (*) │ Sysop: Reinier De Groot │ │- GOLEM Service BBS 2:242/4 │ Sysop: Hanstheo Wolf │ │- Sirex BBS 2:280/4 (HUB) │ Sysop: Gerry Ulrich 2:280/401 │ │- Funboard BBS │ Sysop: Dirk Astrath 2:244/12 │ │- Amber Shadow │ Sysop: Dave Overton 1:203/988 │ │The BBS marked with (*) will always test the newest version and is │also the main distribution node for the MT-series. Also mail to me │can be send to this system. The other BBS's are asked, if they like, │to test the new versions, but if there is no time, or if they find │the risk to high I don't mind. I would be pleased though, if these │BBS's would like to look into the new BETA version. │ │ │5.2 Credits │──────────────────────────────────────────────────────────────────────── │Thanks to the following people: │ │- All registered users. You make it possible to enhance RFW with nice │ features; │- All users who did write me a message and/or sent me a postcard; │- The BETA-team; │- A special 'thanks' to Reinier de Groot, Hanstheo Wolf and │ Dirk Astrath. They keep coming with nice suggestions; │- A big thanks to Dave Overton who is doing the USA support; 5.3 Version history ──────────────────────────────────────────────────────────────────────── ┌───────┬─────────────────────────────────────────────────────────────┐ │ 1.01 │ Beta release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ First non-public beta release; ┌───────┬─────────────────────────────────────────────────────────────┐ │ 1.02 │ Beta release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ First public beta release; ■ Changed the RFC.CMP into two files (RFC.CMP and RFC.ARE) to gain memory; ■ Changed access to RFC.CMP, thus creating a gain in speed. A benchmark with 5000 files in FILES.BBS under DesqView gave the following results: 1.01ß2 Stored in memory : 87.56 seconds 1.02ß4 Stored on DISK ! : 30.80 seconds A benchmark with 2000 files in FILES.BBS under DesqView gave the following results: 1.01ß2 Stored in memory : 37.67 seconds 1.02ß4 Stored in memory : 9.61 seconds ■ Fixed some extended ASCII traps, so ASCII (non ANSI) users can now look at a clean screen; Suggested by: Eddy Emck ■ Fixed name of program in program header (QFW was displayed and not RFW). ┌───────┬─────────────────────────────────────────────────────────────┐ │ 1.03 │ First public release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ Added Hot-key support Suggested by: Reinier de Groot, Eddy Emck, Gert Ensing and lots of other users I imagine; ■ RFW is now capable of displaying more than 24 lines if the user did set a larger number of lines in the user-setup of the BBS; Suggested by: Eddy Emck ■ It is now configurable to choose between clear-screen/display and scrollwindow/display; Reported by: Many users ■ It is now possible to let the 'TOF'/'BOF' rulers out of the list; Reported by: Eddy Emck ■ It is now possible to configure all colors (local and remote); ■ It is now possible to configure the format the date that RFW displays in the files-list; ■ You can replace the internal help-screen with your own files. While displaying this file, Hot-key support is NOT active; Suggested by: Eddy Emck ■ It is now possible (with a special configuration option, to keep downward compatibility) to combine the /A option with all other options to reduce the search/display to one area; Suggested by: Eddy Emck ■ With keyword/file search any long comment (displayed on a next line in a normal file-list) was not displayed and/or searched. This is now fixed (in a somewhat cruel way). Suggested by: Gert Ensing ■ The user can now force RFW to restart without loading itself again. Suggested by: Eddy Emck ■ Fixed some bugs and flaws; ■ Fixed time-slice problems in DV. In combination with X00 (DV option) there is no degradation in performance, even with 8 RFW's concurrent in the machine; ■ Changed the internal structure of the compiled files again. This gives you a gain of 3 bytes per line. You must run RFC again when upgrading to this version ! ┌───────┬─────────────────────────────────────────────────────────────┐ │ 1.04 │ Bug release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ Changed the hotkey-support somewhat. Overrun errors should be fixed now. Also several hits on ENTER or PGDN would result in a partial displayed screen. This is also fixed; Suggested by: Eddy Emck, Reinier de Groot ■ Fixed RFC to work OK on both the old structure of FILES.RA and the one introduced with RA 1.00beta8. Suggested by: Reinier de Groot ┌───────┬─────────────────────────────────────────────────────────────┐ │ 1.10 │ Minor release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ Changed the hot-key support. RFW was know to eatup many ticks. This was caused by the special routines that implemented the hot-keys. All keys will now ALWAYS redraw the screen, so CRSR-DOWN when the last line is on the screen will still cause a redraw of the screen. The same goes for CRSR-UP, END, HOME, PGUP and PGDN. Hot-keys should now work better and with a smaller number of cycles. Suggested by: Eddy Emck ■ Added support for QuickBBS and SBBS; Suggested by: Various users ■ Added support for CD-ROM drives in RFC; Suggested by: Various users ■ Added /CFG to RFW and RFC and /ASC to RFW; ■ Added tag-file support to create and use FileDoor/DISP-compatible tag-files; ■ Removed help information from RFW. This is now stored in a separate help-file (example included); ■ Changed the FOSSIL-access a bit and changed the input-routines to give back more time-slices to DesqView <tm>; │5.4 Copyright, Trademarks │──────────────────────────────────────────────────────────────────────── │CRA is a trademark of DISP and donated to public domain │Windows is a trademark of The Microsoft Corporation │4Dos is a trademark of J.P. Software / R.C. Conn and T. Rawson │FrontDoor is a trademark of J. Homrichhausen │QuickBBS is a trademark of the QuickBBS group Inc. │Remote Access is a trademark of Continental Software │DesqView is a trademark of QuarterDeck Office Systems. │X00 is a trademark of Ray Gwinn │ │RFW is written in Turbo Pascal 6.0, with help of the Turbo Debugger 2.0 │and makes extensive use of Object Professional 1.10 and OPCFI V 9.11. │ │Turbo Pascal is a trademark of Borland International │Turbo Debugger is a trademark of Borland International │Object Professional is a trademark of TurboPower Inc. │OPCFI is a trademark of Robert W. van Hoeven │ ==================== END OF DOCUMENT ==================================