FIDO-FAM Version 5 FIDO-FAM FIDO BBS File Area Maintenance Utility User Manual - also supp

Master Index Current Directory Index Go to SkepticTank Go to Human Rights activist Keith Henson Go to Scientology cult

Skeptic Tank!

FIDO-FAM Version 5 FIDO-FAM FIDO BBS File Area Maintenance Utility User Manual - also supports OPUS and QuikBBS - Copyright (c) 1988 Dennis Glaeser All rights reserved. 3016 Country Knoll Dr. MDC - RCC BBS St. Charles, MO 63303 Fido 100/10 (314) 928-3525 (voice) (314) 232-6881 FIDO is a registered trademark of Tom Jennings FIDO-FAM Version 5 Table of Contents 1 Overview and Syntax 1 2 System Requirements 3 2.1 Operation on the Host machine 3 2.2 Remote Operation 3 2.3 Colors 3 2.4 Host Serial Driver 4 2.5 Required Files and Paths 5 2.5.1 Location of System Files 5 2.5.2 Text File Format for Area Definitions 6 2.5.3 Path Checks 6 3 Command Line Parameters 8 3.1 Single Character Parameters 8 3.2 Multi-Character Commands 9 3.3 The FAMOPT environment variable 9 4 SEND Files 10 4.1 Types of SEND Files 10 4.1.1 Single Send File 10 4.1.2 Multiple Send Files 11 4.2 Batch SEND 11 4.3 Interractive SEND 12 5 FIDO-FAM.CFG File 13 6 File Area Selection Screen 14 6.0.1 Dynamically Added File Areas 14 7 File Area Editor Operation 15 7.1 Cursor and Function Keys 16 7.2 Cursor and Screen Movement 16 7.3 Commands to Mark/Unmark Lines 17 7.4 File Area Editing Commands 18 7.4.1 - A - Abandon/Adopt the file(s) 18 7.4.2 - C - Send a Command to DOS 19 7.4.3 - E - Line Editor 20 7.4.4 - F - Find 21 7.4.5 - G - Regenerate the Display 22 7.4.6 - I, Ins, 0 - Insert a comment 22 7.4.7 - J - Jump 22 FIDO-FAM Version 5 7.4.8 - K, Del, . - Kill/Delete Line(s) 22 7.4.9 - M - Move/Copy lines 23 7.4.10 - O - Overwrite this Comment 23 7.4.11 - Q - Quit the Editor 24 7.4.12 - R - Rename the File 24 7.4.13 - S - Sort files 24 7.4.14 - T - Date the file description 25 7.4.15 - V - View a File 25 7.4.16 - # - Move line to another area 25 7.4.17 - ? - Display a 'help' screen 26 7.4.18 CTRL-A - Adopt all orphans 26 7.4.19 CTRL-D - unDate the Comment(s) 26 7.4.20 CTRL-E - Edit DIR.BBS 26 7.4.21 CTRL-T - Touch (File Date/Time) 26 8 Backup of .BBS Files 27 9 Shareware Registration 27 10 Change History 28 10.1 Version 2.0 28 10.2 Version 3.0 28 10.2.1 Version 3.01 28 10.3 Version 4.0 29 10.4 Version 5.0 29 10.4.1 Version 5.01 30 10.4.2 Version 5.02 30 FIDO-FAM Version 5 1 Overview and Syntax FIDO-FAM is designed to be a FIDO BBS File Area Maintenance utility. It allows the user to quickly and easily review, modify, and coordinate the files in any File area with the appropriate FILES.BBS file. This utility is designed to work with either version 11 or 12 of FIDO, and also has features to support OPUS and QuikBBS . FIDO-FAM uses FIDO.SYS, SYSTEMnn.BBS files, or a text file to define File Area Paths. Syntax : FIDO-FAM [a] [b] [c] [d] [h] [i] [l] [n] [z] [path to system files | text filename] [SEND nn [nn..[nn]] TO filename] Note: any command line parameter may be prefixed with either '-' or '/' if desired. For example, the following command line parameters are equivalent: d -d /d Environment string FAMOPT may also be used in place of, or in conjunction with the command line to specify parameters. The FAMOPT string can contain any command line option EXCEPT the SEND command. A configuration file named FIDO-FAM.CFG may also be used to invoke parameters. A sample file named DEFAULT.CFG is distributed with FIDO-FAM and is commented sufficiently to be self-explanatory. FIDO-FAM operates on any MSDOS system. It may be run remotely, as long as the remote terminal/computer responds to ANSI terminal commands for color and cursor positioning. All screens are designed to work with either color or monochrome displays. Page 1 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 FIDO-FAM provides two modes of operation: REMOTE and LOCAL. The basic difference between them is that REMOTE uses DOS for I/O, whereas LOCAL mode does direct screen writes for fast displays. REMOTE mode is the default configuration because it allows operation through the communication ports, if the Console device is redirected appropriately (usually with the CTTY=COMx command). You do not need to be operating remotely to use REMOTE mode! The 'L' parameter puts the program in LOCAL mode which writes directly to display memory for very fast screen displays. LOCAL MODE WORKS ONLY ON THE HOST MACHINE AND REQUIRES AN IBM-PC OR COMPATIBLE. Local mode is NOT required if you are using the host machine, it is simply a display speedup. If for any reason your display is messed up using Local mode, be sure to try running without the 'L' command. Page 2 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 2 System Requirements 2.1 Operation on the Host machine FIDO-FAM can be run on any computer running MSDOS or PCDOS 2.x or higher, and which has an ANSI terminal or ANSI device driver installed. For example, an IBM PC (or compatible) may be used as long as an ANSI device driver (ANSI.SYS, or FANSI- CONSOLE) is installed. Any computer whose terminal emulates a VT100/102, such as the DEC Rainbow, may also be used. If FIDO-FAM is run on an IBM PC (or clone) ONLY in LOCAL mode the ANSI driver is not required. Without the ANSI driver FIDO-FAM cannot be run in REMOTE mode. 2.2 Remote Operation FIDO-FAM can be run remotely. This allows authorized users, typically the Sysop or File Area Managers (assistant Sysops), to do file area maintenance from home. The remote terminal, or modem program, being used MUST respond to the ANSI terminal control strings for: - Cursor Positioning - Clear Screen - Clear to End of Line - Colors - Note: all displays are designed to work even if color is ignored. An 80 x 24 display is used, to support remote users who don't have 25 line screens. 2.3 Colors FIDO-FAM normally uses color in all of its displays. A command line switch ('N') will totally disable the issuance of color commands. A configuration file named FIDO-FAM.CFG may be used to configure the colors used in all FIDO-FAM displays. A file named DEFAULT.CFG, distributed with FIDO-FAM, shows the default colors used by the various FIDO-FAM displays. If different colors are desired, copy the appropriate lines from DEFAULT.CFG to a file Page 3 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 named FIDO-FAM.CFG and change the values to your liking. The configuration file is discussed in depth later in this document. screens. Some users have complained that FIDO-FAM does not restore colors to their original settings when it exits. If you have that concern, read on. The ANSI device specification does not provide a means to querry the system about 'current' colors. Therefore it is impossible to generically restore the original colors upon exit from any program using the ANSI device driver for color control. FIDO-FAM will restore colors on an IBM-PC or compatible through the use of BIOS calls, if the 'L' command line parameter is used. Remember that this can only work on a local machine. It has no effect on the remote user's terminal. There is a better way! Since any (non-local) system using FIDO-FAM must have an ANSI device installed, there is a powerful, easy, and safe way to restore your favorite colors after ANY program has run. Furthermore it works ALL THE TIME, running local or remote! The secret: put color control commands in the DOS PROMPT. Refer to your DOS documentation on the Prompt Command, and ANSI.SYS for more details. 2.4 Host Serial Driver In order to allow remote programs to be run, the Host machine must allow the program to do its I/O through the Communications port, instead of the local Console and Keyboard. There are basically two ways to do this: 1) the CTTY command, or 2) use redirection on the command line when calling the program. In either case the redirection goes through a Serial Device driver. In order to work without limitations, FIDO-FAM requires a Serial Device driver which responds correctly to an Input Status request (is a char waiting to be read). Generally, only drivers which buffer input will respond as needed. In plainer English: During the execution of many commands, FIDO-FAM checks with DOS to see if a keypress is waiting to be read. This is done to support local Function Keys (on IBM compatibles) and to allow repetative cursor movements before updating the screen display. Some device drivers respond to a keypress check with a 'yes', and then proceed to wait until a key is pressed!! This makes using FIDO-FAM very difficult. The symptoms of this problem are: FIDO-FAM does not immediately respond to a single keypress while in the File Area Editor; but a subsequent keypress invokes the Page 4 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 previously pressed key! In other words FIDO-FAM reacts one keypress out of synch, or appears to require two keystrokes when one should do. If this occurs try to invoke redirection from the command line as follows: FIDO-FAM >com1 This identifies individual Send-Files and provides a convenient header for each Area in a multiple-area Send-File. The current SEND File file itself cannot appear in the file listing, because it has not been created/closed! If a previous version of the SEND File file existed, that old file size (and date) will appear in the new file. 4.1.1 Single Send File A single file will be created if the file name (including path if desired) of the SEND file is a legal DOS name. If more than one Area is specified, the Areas will appear in the file in the same order they were entered in the SEND command. Page 10 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 4.1.2 Multiple Send Files If the filename specified for the SEND file is in the form: *\filename (Note the wildcard 'path' which is an illegal DOS format.) FIDO-FAM will put a SEND file in EACH AREA specified in the SEND command. Existing files are overwritten. If the Auto-Adopt mode (command line option) is in effect, Orphan files will be Adopted for this operation. However, if the file contains an end-of-file comment, the Adopted Orphans will not appear in the SEND file because they are appended to the end of the data - past the eof-comment. FILES.BBS is never changed by a SEND operation (even if the SEND file contains Auto-Adopted Orphans). 4.2 Batch SEND If the keyword SEND is found on the command line, FIDO-FAM operates in a Batch SEND mode, rather than interractively. The general form of the Batch Send command is: SEND nn [nn ...[nn]] TO filename The keywords SEND and TO are required (case is not significant, used here for emphasis). The 'nn's represent area numbers, separated by spaces or any non-numeric character (1 2 3 or 1,2,3 for example). The filename will determine if one or multiple SEND files are to be created, as defined above. Other options may be used in conjunction with this command (Show File Dates, Auto Adopt, System Path, etc) however THIS COMMAND MUST BE THE LAST ONE ON THE COMMAND LINE. FIDO-FAM terminates following the completion of the SEND operation, with ERRORLEVEL set as follows: 0 - successful completion 3 - 'to' keyword not found, or no filename found 4 - unable to open 'to' file(s) 5 - no area numbers found between 'send' and 'to' Page 11 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 Messages are displayed on the screen as well. If invalid area numbers are found, a warning message is displayed and no action is taken. This is not considered an error. ERRORLEVEL will be 0 even if no valid area numbers are found. If no valid area numbers are found and the SEND TO file is a single file (a legal DOS file name) the SEND TO file will be empty (length will be 1 because the file is always terminated with a ^Z char). 4.3 Interractive SEND FIDO-FAM's first screen displays the lowest level subdirectory names of the available file areas, and the prompt: to edit,xpanded info,end to a file or uit Entering the 'S' command invokes the interractive SEND operation. You will first be prompted for the Area Numbers to SEND. Don't forget that if you intend to create a single file the areas will appear in the order specified here. Next is a prompt for the file name (which determines single or multiple SEND files as described above). If a legal DOS filename was input and that file exists, you will be given the option to: ppend, ewrite or uit If multiple SEND files are requested (*\filename) any existing files are overwritten in their respective directories. Page 12 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 5 FIDO-FAM.CFG File If a file named FIDO-FAM.CFG is found in the same directory where the system files are found, it will be processed to allow a number of user-defineable configurations: - Colors. If you want to paint mustaches on my Mona Lisa, here's your chance. The defaults are the colors FIDO-FAM has been using. - The char used to replace the ESC char while editing comments. The default is the Tilde (~). - The number of additional Areas which can be dynamically added when using FIDO.SYS. The default is 5. - Any of the command line options. NOTE: the .CFG file is processed FIRST, the FAM-OPT environment variable is processed SECOND, and the arguments on the command line are processed LAST. The file DEFAULT.CFG is provided to show you how the FIDO-FAM.CFG file must look. The comments make the file self explanatory (hopefully). Use any text editor to modify as desired. The name of an item (on the left side of the '=') must remain exactly as shown to be recognized (caps and spacing). Invalid data is ignored. The order of items is immaterial. If you want the default for any item you may remove it from the .CFG file if you like (saves processing time). Page 13 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 6 File Area Selection Screen FIDO-FAM's first screen displays the lowest level subdirectory names of the available file areas, and the prompt: to edit,xpanded info,end to a file or uit Entering a valid area number will invoke the File Area Editor for that area (described below). The 'E' command (Expanded Info) will prompt for the Area Number, and then display the full path name for that area and its description (if available). The 'S' command is discussed above (Interractive SEND). The 'Q' command exits FIDO-FAM. If the 'L' option was invoked on the command line, the screen colors will be restored, and the screen cleared to those colors before exiting. 6.0.1 Dynamically Added File Areas FIDO-FAM allows a you to dynamically add a new Area by simply entering an Area number which does not already exist. If you are using SYSTEMnn.BBS files to define Area Paths, a non-existent Area number is any number in the valid range (0 to 99 normally, or 0 to 255 if the 'H' parameter is in effect). If you are using FIDO.SYS to define Area Paths, FIDO-FAM allows for five (5) additional Areas. This number can be changed by using a FIDO-FAM.CFG file (discussed below). When you enter a non-existent Area number, you will be prompted to keyin the path to use for that area. If you specify a non-existent directory, you will be given the opportunity to have it created. You can, of course, ESC from this process at any point. Added Areas are displayed differently in an Areas Display, to remind you that they were dynamically added. Other than that, they operate the same as any other Area. Any invalid input is ignored. No funny messages, just no action (except to erase the bad input from the screen). Page 14 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 NOTE: if you add Areas under the Move or # command within the Area Editor (discussed below), those Areas only exist while editing that Area. When you Quit the editor they will NOT appear in the Areas list. 7 File Area Editor Operation The file area editor starts by reading the directory of the selected area. It then reads FILES.BBS, if it is there. A working array of information is displayed for manipulation. Each line is numbered on the screen, with the current line in reverse video (and an asterisk in case color is not available). If a comment or description is too long to fit on the screen (because of the line number), its display is truncated, but no data is lost. The entire string is available for editing (discussed below). If there is no FILES.BBS, and the Area Directory is empty, the display states: 'New FILES.BBS, no files found'. The only actions available are to Insert comments, or Edit the one line that is displayed. If no Inserts or Editing is done, a FILES.BBS is NOT created. ANY modifications will cause a FILES.BBS to be created in that subdirectory. Per FIDO specs, any line in FILES.BBS is either a File Name and optional Description, or a Comment. If the first character of the line is a space, dash, '%', the Esc char, or '@', the line is a comment, otherwise it is a file. (The '% ' char is used by Fido 12 for display control, the Esc char is used by OPUS for colors and display control.) If FILES.BBS is found, its contents are displayed. Files named in FILES.BBS which are found in the directory are displayed with their file size and description. If Showing File Dates, they are displayed between the file size and comment, with two spaces between file date and the comment (just like OPUS). File names which are not found are tagged 'Missing' in place of file size. If the 'A' command line parameter was NOT used, any files in the area directory, not named in FILES.BBS are appended to the working display array, with their size [date] and a description of 'Orphan'. Using the 'A' parameter automatically adopts these files, and they appear no different than the files already in FILES.BBS. The bottom two or three lines of the screen display the available commands, and prompts. The capital letter shown in each mnemonic is the character which will invoke that command. Page 15 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 Character commands do not require a terminating carriage return. Numeric input requires a terminating carriage return. The bottom line changes to show the valid commands for the current line. In general the ESC key will abort any input or operation in the Area Editor. Most displays show ESC as an input option. 7.1 Cursor and Function Keys When running the program locally on an IBM PC (or compatible) the Arrow Keys, PgUp, PgDn, Ins, Del, and some Functon keys, may be used, as noted below, in place of the appropriate character command. This assumes, of course, that the response generated by those keys has not been modified through the use of ANSI commands, 'Smart Key' programs, or Command Line Editor programs, etc. During remote operation from a machine which has a PC style keyboard, the numeric equivalent of the Cursor keys perform the same function. Therefore, you may be able to toggle NumLock On and use the 'Cursor Keys'. This mechanism will work either Local or Remote. The Numeric keys which are not on the Cursor Key Pad act the same as those on the Cursor Keys. No warranties expressed or implied about the use of Cursor or Function keys on any non PC-clone. Try them, if they work, fine. If they don't, use the character commands. Note that the Local HOME/7 and END/1 keys have been implemented but no character command has been defined for these functions. 7.2 Cursor and Screen Movement Command Description ----------------------------------------------------------------- 7, Home jump to top of data 1, End jump to end of data U, 9, PgUp page up a full screen or to the top of the data D, 3, PgDn page down a full screen or to the bottom of the data P, 8, UpArrow move to the previous line N, 2, DnArrow move to the next line Page 16 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 [, F5 move cursor to top of display ], F6 move cursor to bottom of display CTRL-P, F1 scroll window and cursor UP one line (cursor appears stationary on screen, display scrolls 'behind' it) CTRL-N, F2 scroll window and cursor DOWN one line (cursor appears stationary on screen) ALT-P, F3 scroll window DOWN one line - cursor remains on same line (cursor moves UP, but is on same line number) ALT-N, F4 scroll window UP one line - cursor remains on same line (cursor moves DOWN, but is on same line number) 7.3 Commands to Mark/Unmark Lines Marked Lines are highlighted and have the '<' char following the line number (for non-color displays). If the current line is Marked, its '*' is changed to a '#'. Command Description ----------------------------------------------------------------- B - Mark a Block of lines You are prompted to enter the range of lines: Mark line [..line] xx (xx is the current line number) You may respond with a single number, two numbers, or simply hit RETURN. If the input is a single number, or RETURN, you will be prompted for the last number in the desired range. If the input was two numbers (separated by any non-numeric characters) that range is used. You may enter a large number for the high end (ie: 9999) and the actual max value will be used. Invalid input (ie: first > last) is ignored and the operation is aborted. X - UnMark a block of lines Works the same as the 'B' command. CTRL-B - Mark ALL lines Page 17 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 as described. CTRL-X - Unmark ALL lines as described. * - Mark/UnMark the current line This toggles the current line only. Editing Commands (described below) which work with Marked Lines operate in this manner: If there ARE marked lines, the prompt is: Marked entries or line [..line] x Esc Where x represents the current line number. The possible responses are: 'M' - to use the marked entries - to use the current line n1 - to use line n1 (n1 is a valid line number) n1 n2 - to use the block n1 to n2 (where n1 and n2 are valid line numbers) In this mode a value of n2 greater than the max valid line number (ie. 999) may be used. The two numbers may be separated by any non numeric char (space, commma, dot, ...). Any response except 'M' ignores marks, and processes the line(s) indicated. If the key-in response does not make sense (no numbers found, n1 > n2, n1 not valid, ???) the command is aborted. If NO marked entries are detected, the 'Marked entries' prompt does not appear, and the 'M' response is not available. All other responses are treated as described above. Marks are not removed by any commands except '*', 'X', and '^X' (discussed above). Marked Entries which are re-located within the current area (due to Moves or Sorts, or Inserts) remain Marked in their new position. 7.4 File Area Editing Commands 7.4.1 - A - Abandon/Adopt the file(s) This command works with Marked Lines. If the [marked/n1..n2] line Page 18 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 is an Orphan file, it becomes an Existing file, and this line will be added to FILES.BBS. Note that a file must be Adopted before its description or file name may be edited. If the [marked/n1..n2] line is an Existing file, this command will make it an Orphan. This means it will not appear in FILES.BBS, and any description which existed is lost. The description 'Orphan' is displayed to identify such files. Marked Lines can be a mixture of Existing and Orphan files. This operation toggles each files' respective status. Comment lines are not affected. 7.4.2 - C - Send a Command to DOS A prompt will instruct you to enter a DOS command and then invoke the line editor (see E above). If the current line has a file name (existing, missing, or orphan), that name is placed in the buffer for convenience. If the line entered is a single asterisk, "*", the operation is aborted. Otherwise, before invoking COMMAND.COM, the current directory is set to be the Area Path. A blank line will simply invoke a secondary version of COMMAND.COM and a normal DOS prompt will appear. To return to FIDO-FAM, enter the EXIT command. A non-blank command line will be executed by the secondary copy of COMMAND.COM and then return directly to FIDO-FAM. When control returns to FIDO-FAM it pauses until the user presses a key. This allows the user to view the last display generated by the subtask. The current directory is restored to its original value (before the 'C' command was issued). If the Area Path referred to another drive, that drive's current path is restored to its previous value also. NOTE: if running FIDO-FAM remotely, remember that not all programs will run correctly in that environment! FIDO-FAM is compiled to take aprox 160K, and release the rest back to DOS. The remaining available memory must be sufficient to hold the secondary COMMAND.COM and the program(s) to be run. If a DOS command fails to work, it is likely that insufficient memory is the problem. Unfortunately COMMAND.COM always returns with ERRORLEVEL set to 0, even if a problem occured, so it is impossible to detect errors, much less provide error messages! NOTE: any changes to the current area's directory will NOT automatically appear in the FILES.BBS display. See the G command. Page 19 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 7.4.3 - E - Line Editor The appropriate line is displayed in full at the bottom of the screen. This string may now be edited as desired. The line editing commands are displayed above the line being edited: CTRL-V, Ins - toggles the mode between INSERT and OVERWRITE OVERWRITE is the default mode when the line editor is invoked. This can be changed by the 'I' command line parameter. TAB - insert spaces to align comment with file description (see below) Cursor Movement Commands: CTRL-W, Home - beginning of line CTRL-A - left one word CTRL-S, LtArrow - left one char (NOTE: was CTRL-D !!!) CTRL-D, RtArrow - right one char (NOTE: was CTRL-F !!!) CTRL-F - right one word CTRL-R - end of line CTRL-G, Del - delete char under cursor CTRL-H, BackSp - destructive cursor backward Comment Lines may be up to 127 characters long. If the first character of a comment is not a space, dash, '@', Esc, or '%', a space is inserted as the first character. File descriptions may be up to 56 characters long (44 if Showing File Dates). The cursor will not advance beyond the appropriate point. NOTE: this routine is used to get input for some other commands (Find, dosCmd, renAme). The line editor does not strip leading or trailing blanks from the input string. Such blanks may be significant to the command being invoked. If you do not get the desired results, check to see if trailing blanks are the culprit. The TAB key (the one between CTRL and ESC on a PC keyboard) provides a convenient way to align additional comment lines with a file description. It inserts sufficient blanks at the beginning of the comment string so that the comment will fall exactly under a File Description. When Showing File Dates, remember the File Date is NOT part of the description. The INSERT mode has been given a new twist: When INSERTING chars, if the current string exceeds the defined max allowed for that string: - the bell rings - the last char of the string 'disappears' off the end - the new char is inserted Subsequent char deletes will 'recover' the last chars which were Page 20 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 pushed off the end of the string. When the string is accepted (by hitting RETURN) only the valid (visible) chars are kept. Comment lines containing ANSI ESC sequences may be edited. The ESC char is temporarily replaced by a Tilde (~) for editing. Tildes may be entered in editing, and will be translated back to ESC when editing is complete. The char which replaces the ESC may be changed by using a FIDO-FAM.CFG file - discussed below. NOTE: the replacement char must be a displayable ANSI character (!..~) and one that you don't use in your comments (since it will be replaced). If a comment does NOT contain the ESC char, FIDO-FAM truncates the comment to 79 chars to avoid wrap around on the BBS display. If the comment contains the ESC char it will not be truncated by FIDO-FAM and the user is responsible to avoid wrap arounds in the BBS display. FIDO-FAM always truncates the display of comments, so you cannot use the FIDO-FAM display to determine if wrap around will occur. NOTE: when in REMOTE mode a 'full width' comment which contains ESC sequences will not display the full width across the screen. This is because FIDO-FAM does not attempt to eliminate ESC sequences from its count of chars to be displayed. If, for example, a comment contains a 5 char ESC sequence (ESC[33m) and the comment is actually the full width of the screen, FIDO-FAM will display it 5 chars narrower than the width of the screen. The full comment may be seen by using the line editor. 7.4.4 - F - Find The user is prompted to enter the string of characters to find. If the characters "*" and "?" (DOS wildcards) appear in the string they are treated as DOS wildcards and only file names are searched. If the search string has no wildcards, then everything (file names, file descriptions, and comments) are searched. If a match is found, it becomes the current line. Subsequent Find commands display the last search string. A carriage return will search for the next occurrance of the string. If a new string is entered on a subsequent Find, the search is started from the beginning of the data, not the current line. Searches always stop at the bottom of the data. Subsequent searches will not automatically wrap around and start searching from the beginning of data. Page 21 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 7.4.5 - G - Regenerate the Display This command is a shortcut way of Quitting, then re-entering the same area. The most practical use of this command is after exiting to DOS and modifying the files in the current area subdirectory (expanding an ARC, unsqueezing a file, etc). Unless this command is invoked, or you manually Quit and re-enter the area, the FILES.BBS data may not be in synch with the actual subdirectory contents. 7.4.6 - I, Ins, 0 - Insert a comment The user is prompted to indicate: Before or After the current line Either a 'B' or 'A' must pressed. A blank line is inserted as requested. Note: only comments can be inserted. The only way to add a file to an area is with the Move (Copy) or '#' commands. 7.4.7 - J - Jump The jump command can be direct or relative. The following prompt appears: Jump (+n, -n, n) Entering an unsigned number will make that line the current line. Entering a signed number will move the marker up (+) or down (-) the number indicated. Jump to 1 takes you to the top of the file. Jump to 999 (or any number >= lines in the file) will take you to the last item in the file. If possible, the display will present the requested line in the center of the screen. 7.4.8 - K, Del, . - Kill/Delete Line(s) This command works with Marked Lines. A secondary prompt verifies that you really want to continue the operation. The appropriate Existing or Orphan files are physically delete from the Page 22 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 directory. The line is removed from FILES.BBS and the display is updated. 7.4.9 - M - Move/Copy lines This command works with Marked Lines. Subsequent prompts are: move [Marked/n1 [..n2]] to BEFORE line or area(#) (A)bort If the last input is a '#', the prompt becomes: Move [Marked/n1 [..n2]] Lines to Area _ Only valid area numbers will be accepted. If a keyin is not detected within a few seconds, a list of available areas is displayed temporarily at the top of the screen. Of course, if Esc is input as the response to any prompt, the move is immediately aborted. If a valid Area Number is entered, the next prompt is: keep original? (y/n) If the response is Y (or y) the Move becomes a Copy! All leading comments (those prior to the first line with a filename) are Moved/Copied to the new area. Once a filename is encountered, all subsequent comment lines are considered to be comments about that file. If a file already exists in the destination area, the user will be notified and must indicate whether or not to overwrite it. NOTE: if a file is NOT moved, any trailing comment lines are not moved either! Any Orphan files moved to another area become existing files in the new area. ----------- Controlling locatation of data moved into a FILES.BBS: ----------- When moving files to the destination FILES.BBS, that file is searched for a Comment Line beginning with the chars: '-*' (dash-asterisk). If found, the new lines are inserted immediately after that comment line, otherwise they are appended to the end of the file. (Note: This feature has always been in FIDO-FAM, but inadvertently not documented when the original version was released!). 7.4.10 - O - Overwrite this Comment Page 23 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 The current line's comment or description is replaced with one from another line. Comments and descriptions are treated interchangeably by this command. If an existing, or missing file's description is being overwritten, leading blanks are removed from the incoming data. 7.4.11 - Q - Quit the Editor This command returns the user to the File Area Selection screen. See the discussion about backups below. 7.4.12 - R - Rename the File This command is only valid on Existing or Missing file lines. The line editor (see the 'E' command) is used to edit the name. The name must be a valid DOS file name, or the input is ignored. If the file exists, the file is renamed. If an existing file is renamed to another existing file name, the following prompt appears: already exists, rename the entry anyway? (y/n) If the user enters 'Y' (or 'y'), the entry in FILES.BBS is renamed, and the area is automatically regenerated (see the G command). The file whose entry was renamed should then show up as an Orphan. Missing files may be renamed, but no actual directory checks are made. 7.4.13 - S - Sort files The user is prompted for the range to sort (first and last line numbers). This command DOES NOT work on Marked Lines, only the range explicitly entered in response to the prompts. Next, the user must select: sort by: Name Ext File-date Descr-date and then: Ascending or Descending order The sort by Descr-date looks only at the desciption on the same Page 24 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 line as the file name, not any trailing comments. Descriptions without dates, by default, are placed AFTER dated descriptions. The sort routine treats Existing, Missing, and Orphan lines as file lines. Comment lines are treated as follows: - Comment lines which precede the first file line are ignored. - Comment lines which follow a file line are treated as a continuation of the file line during sorting. Thus a file and all following comment lines stay together. 7.4.14 - T - Date the file description This command works with Marked or specified line(s), but is only valid for existing files. The user is prompted to select: File date or System date Either an 'F' or 'S' must be input. The appropriate date is inserted at the beginning of the description. The description is truncated if necessary. If the description was already dated, the new date replaces the old date. This replacement will only take place if the date is at the very beginning of the description. 7.4.15 - V - View a File This command is only valid for Existing or Orphan files. The file is analyzed to determine whether or not it is an ASCII text file. Text files are listed to the screen. Any lines longer than 79 chars are truncated to prevent wrap around. A non-ASCII file is displayed in a Hex Dump type of display. Either mode displays data a screen at a time. Any key but 'Q' will continue to display the file. 7.4.16 - # - Move line to another area This command is only valid if the current line contains an existing or orphan file. A prompt requests the user to enter the destination area number or Esc. After a few seconds, unless a key is struck, a list of available areas is displayed. If a file Page 25 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 with the same name already exists in the destination area, the user will be notified and must indicate whether or not to overwrite it. If the response is NO, the move is aborted and the file is not removed from the current area. 7.4.17 - ? - Display a 'help' screen This screen contains commands not shown on the normal command summary at the bottom of the editor screen: 7.4.18 CTRL-A - Adopt all orphans If you have entered FIDO-FAM with the 'A' parameter, this will happen automatically. However if you want to be selective about which areas have the Orphans adopted (so you didn't use the A parameter) this command makes it easy to grab all Orphans for this area. 7.4.19 CTRL-D - unDate the Comment(s) This command works with Marked lines. It is provided as a convenience for those who are switching to an OPUS system. (This is the inverse of the 'T' command.) 7.4.20 CTRL-E - Edit DIR.BBS Only a one line DIR.BBS is supported. The top line of the Area display shows the current contents of DIR.BBS. The Line Editor is used to modify the data. 7.4.21 CTRL-T - Touch (File Date/Time) This command works with Marked Lines. The appropriate files are updated with the current System Date and Time. No action is taken on Comment lines which are Marked. The file description is NOT modified by this command (even if it contained the file date). Therefore if NOT Showing File Dates there will be no visual indication that the file date/time has Page 26 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 been modified. Note however that immediately invoking the 'T' command WILL update (or add) the date to descriptions of the same file(s). If File Dates ARE being shown, the displayed file date is modified to reflect the change. 8 Backup of .BBS Files The 'B' command line parameter tells FIDO-FAM not to create .BAK files for either FILES.BBS or DIR.BBS. If this command is NOT used: The first time a change is made to any area's FILES.BBS, the original FILES.BBS becomes FILES.BAK, then the new FILES.BBS is written. Subsequent modifications to an area's FILES.BBS updates that file, but FILES.BAK is not modified. In other words, regardless of how many times you change the FILES.BBS data, FILES.BAK is always the FILES.BBS you started with (for that session). FILES.BBS is always the latest data. If changes are made to DIR.BBS (using the CTRL-E command), the current DIR.BAK is deleted (if it exists), and DIR.BBS is renamed to DIR.BAK. This process occurs each time you enter an Area and change DIR.BBS (the original DIR.BBS is NOT kept in the same manner as the original FILES.BBS). 9 Shareware Registration FIDO-FAM is now being distributed as SHAREWARE. This means that following a reasonable (ie: 2-4 week) trial period you decide to keep and use this program a $25 registration fee is requested. Please send checks to: Dennis Glaeser 3016 Country Knoll Dr. St. Charles, MO 63303 User support will continue to be provided through Fido 100/10, or by calling or writing me directly. Page 27 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 10 Change History 10.1 Version 2.0 Initial Release. 10.2 Version 3.0 Bugs Fixed: - Memory Allocation for the MOVE command. If available memory is tight, Version 2.0 may crash during a MOVE which requires physically copying files. - The input to the Jump command may now be 'edited' by backspacing. - Line numbers > 255 are now valid as input. - The FILES.BBS file is now prettier - comments always line up regardless of file-name length. Added Features and/or Commands: - MARKED Lines - OPUS Support (Show File Dates, Remove Dates from Comments) - Color on/off control - Editing of DIR.BBS - Auto Adopt of Orphans, - Control of .BAKs - New String Editing commands - Control of default mode in String Editor - Sort enhancement, - New Screen Scrolling Commands - Program is now overlayed. - Implemented a SEND option with both interractive and batch modes. - Environment strings FAMOPT and FAMOVR may be used to specify options and overlay files path 10.2.1 Version 3.01 Version 3.01 fixes a bug in the 'C' command (dosCmd): When the 'C' (dosCmd) command is used: If the current Area Path refers to a different drive than the System files use, the 'current directory' on the other drive was not preserved in versions 2.0 and 3.0. Version 3.01 restores the original 'current directory' on the other drive correctly. Page 28 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 10.3 Version 4.0 This version was very short lived. It was version 3.01 modified to work with Fido 12 with no other improvements. It was only distributed locally (St. Louis area) and was almost immediately replaced with version 5. 10.4 Version 5.0 - The program was upgraded to Turbo Pascal version 4.0. - FIDO-FAM now uses either FIDO.SYS (Fido Ver 12) or SYSTEMnn.BBS (Fido Ver 11 and Opus) for file area path information. - A new command line parameter: 'L' may be used when running FIDO-FAM locally. The 'R' parameter has been replaced with the 'L' parameter (was: estore original colors - now: ocal mode). - A new 'Z' parameter supresses EOF chars in FILES.BBS (and DIR.BBS if applicable). The default is to end those files with the EOF char - ^Z. - A new 'H' parameter supports OPUS 1.1 which uses HEX values for the 'nn' in 'SYSTEMnn.BBS'. - The 'K' parameter is no longer supported. - Hitting ESC will abort any input or operation in the Area Editor. - The input to the Mark/Unmark and Sort (B, X, S) commands of the Area Editor has been modified a bit. - Comment lines may begin with the ESC char (for ANSI strings) or the '%' char (for some new FIDO 12 display commands). - Comment lines containing ANSI ESC sequences may now be edited. - The limitation that Comments containing ANSI ESC sequences be less than 79 chars long has been eliminated. The line editor will allow you to create a comment up to 127 characters long. - If a comment does NOT contain the ESC char, FIDO-FAM truncates the comment to 79 chars to avoid wrap around on the BBS display. - If the comment contains the ESC char it will not be truncated by FIDO-FAM and the user is responsible to avoid wrap arounds in the BBS display. - An improperly terminated DOS Environment no longer causes FIDO-FAM a problem. OPUS users no longer have to 'game the system' with unneeded environment strings. - The FAMOVL environment string is not used in version 5. - FIDO-FAM allows a you to dynamically add a new Area by simply entering an Area number which does not already exist. - If a file named FIDO-FAM.CFG is found in the same directory where the system files are found, it will be processed to allow a number of user-defineable configurations. Page 29 (c) 1988 Dennis Glaeser FIDO-FAM Version 5 - The 'C' command line parameter for FIDO Version 12 users: Control the File Areas 'visible' to File Area Managers (Assistant Sysops) who are authorized to use the Outside or Exit commands of FIDO. This is the Check Caller feature. - FIDO-FAM is now being distributed as SHAREWARE. 10.4.1 Version 5.01 FIDO-FAM will use a text file to define the paths for the file areas instead of FIDO.SYS or SYSTEMnn.BBS. 10.4.2 Version 5.02 Fixes a bug in 5.0 and 5.01 where continuous use of the Area Move command ('#') will eventually cause a fatal error. This was due to an error in memory allocation/deallocation logic. Page 30 (c) 1988 Dennis Glaeser


E-Mail Fredric L. Rice / The Skeptic Tank