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

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

/ ProfitPress Mega CDROM2 …eeware (MSDOS)(1992)(Eng) / ProfitPress-MegaCDROM2.B6I / BBS / MISC / ROS403.ZIP / ROSSYS.DOC < prev next >

Wrap

Text File | 1991-03-31 | 67.8 KB | 1,700 lines

System Operator's Guide to ROS Copyright (c) 1990 Steven Fox All Rights Reserved Associated Information Services P.O. Box 13711 Albuquerque, NM 87192-3711 USA TABLE OF CONTENTS INTRODUCTION.................................................. 1 DISTRIBUTION.................................................. 3 Shareware................................................ 3 Included Files........................................... 4 SECURITY...................................................... 5 INSTALLATION.................................................. 7 Configuring DOS.......................................... 7 Preliminary Startup...................................... 7 Editing the Display Files................................ 7 Connecting the Modem..................................... 7 The Setup Program........................................ 9 Building a New File Catalog.............................. 10 Upgrading from ROS 3.8x.................................. 12 OPERATION..................................................... 13 Logging in the first time................................ 13 Status line.............................................. 13 Local console commands while idling...................... 14 Local console commands during remote operation........... 15 Using ROS on a Network................................... 16 Command Line Options..................................... 16 MAINTENANCE................................................... 19 Sysop Menu............................................... 19 Command Enhancements..................................... 27 EXTENDED DISPLAY CODES........................................ 29 WARNING AND ERROR MESSAGES.................................... 33 TECHNICAL SUPPORT............................................. 37 INDEX......................................................... 39 INTRODUCTION ROS is a fast, multi-user Bulletin Board System designed to operate on an IBM PC, or very compatible computer, with at least 512 k-bytes of memory. DOS version 3.3 or later is required. To maximize the flexibility the sysop has to install new capabilities as they are developed, ROS uses a FOSSIL driver to handle the serial port, external file transfer programs to exchange files with the remote user, and external programs to display directories and text from archives. In addition, ROS allows other external programs to be installed and accessible to the user through "doors." Users of ROS must accept this disclaimer of warranty: ROS 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 ROS. DISTRIBUTION Shareware Shareware distribution gives users a chance to try software before buying it. If you try a Shareware program and continue using it, you are expected to register. Individual programs differ on details -- some request registration while others require it, some specify a maximum trial period. With registration, you get anything from the simple right to continue using the software to an updated program with printed manual. Copyright laws apply to both Shareware and commercial software, and the copyright holder retains all rights, with a few specific exceptions as stated below. Shareware authors are accomplished programmers, just like commercial authors, and the programs are of comparable quality (in both cases, there are good programs and bad ones!). The main difference is in the method of distribution. The author specifically grants the right to copy and distribute the software, either to all and sundry or to a specific group. For example, some authors require written permission before a commercial disk vendor may copy their Shareware. Shareware is a distribution method, not a type of software. You should find software that suits your needs and pocketbook, whether it's commercial or Shareware. The Shareware system makes fitting your needs easier, because you can try before you buy. And because the overhead is low, prices are low also. Shareware has the ultimate money-back guarantee -- if you don't use the product, you don't pay for it. This program is produced by a ┌─────────┐ member of the Association of ┌─────┴───┐ │ (tm) Shareware Professionals (ASP). The ──│ │o │────────────────── ASP wants to make sure that the │ ┌─────┴╨──┐ │ Association of shareware principle works for you. │ │ │─┘ Shareware If you are unable to resolve a └───│ o │ Professionals shareware-related problem with an ──────│ ║ │──────────────────── ASP member by contacting the member └────╨────┘ MEMBER directly, the ASP may be able to help. The ASP Ombudsman can help you resolve a dispute or problem with an ASP member, but does not provide technical support for members' products. Please write to the ASP Ombudsman at P.O. Box 5786, Bellevue, WA 98006 or send a Compuserve message via easyplex to ASP Ombudsman 70007,3536. As Shareware, ROS is provided at no charge to you 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 ROS and continue to use ROS after a reasonable trial period, you must make the registration payment to Associated Information Services. The registration fee will license one copy for use on any one computer at any one time. You must treat this software just like a book. An example is that this software may be used by any number of people and may be freely moved from one computer location to another, so long as there is no possibility of it being used at one location while it's being used at another. Just as a book cannot be read by two different persons at the same time. Commercial users of ROS must register and pay for their copies of ROS within 30 days of first use or their license is withdrawn. Site-License arrangements may be made by contacting Associated Information Services. Anyone distributing ROS for any kind of remuneration must first contact Associated Information Services for authorization. This authorization will be automatically granted to distributors recognized by the ASP as adhering to its guidelines for shareware distributors, and such distributors may begin offering ROS immediately. Associated Information Services must still be advised so that the distributor can be kept up-to-date with the latest version of ROS. You are encouraged to pass a copy of ROS along to your friends for evaluation. Please encourage them to register their copy if they find that they can use it. All registered users will receive a copy of the latest version of ROS. Included Files The following files are included with this version of ROS: !READ.ME If present, describes last minute changes and updates to documentation CAT-NORM.EXE Catalog "normalizer" DISPLAY.ZIP Sample menus and text display files RESPONSE.FRM Please tell us what you think of ROS ROS.EXE Main executable code for ROS ROS-MAC.DAT Sample macro file ROS38-40.EXE File conversion utility ROSSETUP.EXE Setup program ROSSYS.DOC System Operator's Guide (this file) ROSUSER.DB Paradox database format for the user file ROSUSER.DBF dBaseIV database format for the user file ROSUSR.DOC User's Guide SECURITY The security of a computer system is of paramount importance when that system is readily available through the telephone system. To make ROS robust enough to withstand both incorrect entries and malicious attacks, a simple but effective method is used: an access level, ranging from 0 to 255, is assigned to each user. System privileges are based upon this number. In general, the higher the number, the greater the privileges the user has. The following access levels are recommended (use ROSSETUP to change): 0-9 Twit - will be logged off immediately 10-19 Unvalidated user - limited message and files access 11 Registered user - has not yet been validated 20-249 Normal user - full message and files access 250-254 Alternate sysops 255 Primary sysop This access level structure allows sysops to review and edit all user records in the system, including their own, but no one may change or even display the record of a user with a higher access level. CAUTION: Take care not to accidentally lower your own access level. ROS encrypts passwords to increase security. This encryption uses a "one-way" algorithm that has no simple inverse, i.e. the encrypted password cannot be readily converted into the un-encrypted password. Nonetheless, the author recommends that the ROS-USER.DAT file and all passwords be carefully protected. INSTALLATION ROS works well with monochrome or color displays and will use direct screen writes whenever possible to improve performance. ROS recognizes most multi-tasking executives such as DESQview and will either write to the screen buffer or, if necessary, use BIOS calls. Configuring DOS ROS needs 25 file handles when running. Since DOS provides only 20 unless told otherwise, you should include the statement "FILES=25" in your CONFIG.SYS file. This will allow ROS to open all the files it needs to operate. If you already have a "FILES" statement with a value greater than 25, you do not need to change it. Please refer to your DOS manual for more information about the CONFIG.SYS file and remember that after making changes to CONFIG.SYS, DOS must be rebooted. ROS uses a FOSSIL driver for its interrupt driven interface to the communication port. This driver is a memory resident utility that needs to be run only once after the computer is booted, regardless of how many times ROS is run. The simplest approach is to include the FOSSIL driver in your CONFIG.SYS or AUTOEXEC.BAT. If you plan to run ROS under a multi-tasking executive such as DESQview, then SHARE.EXE must be loaded. Again, the simplest way to ensure SHARE.EXE is always loaded is to install it using your CONFIG.SYS or AUTOEXEC.BAT. Preliminary Startup ROS should be installed in its own subdirectory, e.g. "C:\ROS". Once this directory has been created, copy all the files (see section 3) to this directory. Then type the following command: ROS /D This will run ROS in the "direct" or "no modem" mode. If this is a new installation, ROS will create a couple of sub-directories and then automatically run the setup program. Editing the Display Files Before putting ROS online for the users, the text display files contained in DISPLAY.ZIP and extracted to the subdirectory ROS-SYSM should be edited. Most of these files contain embedded descriptions of how the file is to be used -- information you probably do not want to display to your users. In addition, you will probably want to create color images of many of these files for use by your users with ANSI enabled. Connecting the Modem The ROSSETUP program has several commonly available modems already configured for ROS. Simply select the modem that matches your setup or, if you have a different modem, select the one that most closely matches and then use the following paragraphs as a guideline for "Customizing" the settings. The single most common problem sysops have had with setting up a new ROS installation has been with the modem, for example: "my computer works fine with Procomm, but hangs when I run ROS." Since the rest of the system hardware (disks, memory, etc.) is compatible at the DOS level, ROS can count on what will be available. But, since DOS does not support interrupt driven communication port input- output (I/O), ROS has to bypass DOS and even the BIOS, to get to the modem. In addition, "compatible" modems almost never are. Even models made by the same manufacturer may respond differently to commands. Sometimes these differences are significant, such as "NO DIAL TONE" instead of "DIAL TONE." More often the differences are subtle, such as whether or not the modem returns a CR/LF before and after verbal responses. One modem does on some responses and not on others. Another modem even changes baud rate while it is sending the connect response to the computer! ROS is designed to be robust in the way it handles the modem and "hooks" are provided to be able to get to almost everything the modem and ROS need. Nonetheless, experimentation may be required to get a new modem operational. Start with the simplest command string that works and add to it if necessary. Usually, the initialization string will require the most work. Most terminal emulation programs use open-loop control, i.e. they assume that the modem understood the command it was sent, although they do monitor the modem for some command responses, such as "BUSY" or "CONNECT." ROS on the other hand, is expected to operate for long periods of time without attention, and thus drives the modem in closed-loop mode, i.e. all characters sent to the modem are expected to be echoed by the modem back to the computer. Then, ROS waits for the modem to respond to the command with a result code. For example, when ROS commands the modem to go off-hook (answer an incoming call), the modem should eventually tell ROS at what baud rate the connection was made or that the connection failed. When attaching a modem to ROS, then, be sure that the modem is set to allow "modem echo" and "result code display." In addition, set the modem to use "verbal (word) messages" since this matches the setup that is included with ROS. You may, of course, modify this configuration and then set the modem to return "numeric result codes." The only exception to the need for a character by character echo is during the modem reset string. Some modems do not have a switch for "modem echo" and must be set into this mode through a command. If the modem requires a time delay after it is reset until it will accept another command, use pauses as necessary. ROS interprets a tilde character ("~") as a one-half second pause. For example, to reset a modem, wait for two seconds, and set the echo mode, the following reset string could be used: ATZ^M~~~~ATE1^M Two other common switch settings should be considered. The RS-232C Data Carrier Detect (DCD) is used by ROS to determine whether or not a connection is still valid. In other words, ROS monitors DCD and will terminate a session if it determines that DCD has been lost. Most modems have a switch setting that allows the modem to control DCD, based on the condition of the connection, or to force DCD always on. The modem should be set to control DCD. Another switch determines in what way the modem will respond to Data Terminal Ready (DTR). This signal, coming from the computer and controlled by ROS, may be used to enable or disable the modem. For example, when a user completes a session and ROS tries to hang-up the modem, it first drops DTR. If the modem is set to disconnect when DTR is dropped, ROS will immediately see the loss of DCD and will recycle between callers very quickly. If after a few seconds, DCD is still present, ROS will send the local mode escape sequence and then the hang-up sequence to disconnect the caller. These steps take a little longer than simply dropping DTR. Some modems control DTR response through commands. These commands may be included in the reset or initialization strings sent to the modem instead of, or in addition to, the switch settings. Finally, some modems can be set to automatically answer the phone when a ring is detected. This function should be disabled since ROS will tell the modem when to answer the phone. In fact, ROS expects the modem to never answer the phone unless told to do so. One reason for doing this is to ensure the modem will not answer the phone until (and unless) the computer is ready for it to do so. For example, if for some reason the computer "dies," long distance callers will not be charged for a call to a down system. To monitor the modem commands and responses, append "/M" to the command line when starting ROS. When you are satisfied that ROS and the modem are communicating properly, just start ROS without the "/M" to improve the local display appearance. In modem command strings, a "^M" is used to send a carriage return to the modem. A tilde ("~") causes a delay for 1/2 second before continuing. For example, "~~~+++" delays for 1 1/2 seconds, and then sends "+++" to the modem. Command strings may be up to 50 characters long (although most modems only allow 40 characters not including the prefix "AT," spaces, or the carriage return); responses may be as long as 16 characters. The following modem initialization string works well with most Hayes compatible modems: |get the modem's attention | |the modem should echo characters when off-line | | |ensure the phone is hung up | | | |return result codes | | | | |disable auto answer | | | | | |wait 30 seconds for carrier | | | | | | |verbose (word) result codes | | | | | | | |enable extended command set | | | | | | | | |turn off the speaker | | | | | | | | | |command terminator AT E1 H0 Q0 S0=0 S7=30 V1 X4 M0 ^M Sample Modem Initialization Command String The Setup Program ROSSETUP is the program used to setup message and file areas, doors, modems, and most other configurable resources used by ROS. Since the program is menu driven with help messages throughout, these instructions will be succinct. The Command Line The command line used by ROSSETUP is similar to that used by ROS itself. Please refer to the Command Line section for details. The Line Editor Many of the entries to be made in ROSSETUP require more than one character to be entered, e.g. the full sub-directory specification for a door. The following commands are available for editing: <Left>, <CtrlS> Move cursor left one character <Right>, <CtrlD> Move cursor right one character <CtrlLeft>, <CtrlA> Move cursor left one word <CtrlRight>, <CtrlF> Move cursor right one word <Home>, <CtrlQ><S> Move cursor to beginning of line <End>, <CtrlQ><D> Move cursor to end of line <Del>, <CtrlG> Delete character at cursor <Bksp>, <CtrlH> Delete character to left of cursor <CtrlY> Clear entire field or line <CtrlEnd>, <CtrlQ><Y> Delete to end of field or end of line <CtrlHome> Delete from beginning of field to cursor <CtrlT> Delete word to right of cursor <CtrlP> Insert literal, e.g. <CtrlP><CtrlM> inserts a <CtrlM> (Carriage return) in the text <Ins>, <CtrlV> Toggle insert mode on and off <Enter>, <CtrlM>, <ClickCenter> Accept contents of field <CtrlEnter>, <CtrlJ> Accept contents of field and record <CtrlR>, <CtrlQ><L> Restore original contents of line <Esc>, <CtrlBreak>, <ClickRight> Quit editing Menus The following menu will be displayed when ROSSETUP is first started. As each entry is selected by pressing the <Enter> key, additional menus will be displayed. When all changes have been made, select "Exit." ┌────────────────────────────────────────────────────────────────┐ │ System User Comm Modem Retention Access Control Exit │ └────────────────────────────────────────────────────────────────┘ Building a New File Catalog Using the tools provided with ROS, building a new file catalog is not at all difficult. Six steps are required: 1. Collect file descriptions from other sources, such as other bulletin boards willing to share. 2. Use CAT-NORM to "normalize" these catalogs. 3. Edit the normalized description file (CAT-NORM.OUT) as required. 4. Use the <S>ysop <C>atalog <R>econcile command to create the basic catalog. 5. Use the <S>ysop <C>atalog <D>escribe command to incorporate the descriptions built in steps 1 through 3. 6. Use the <S>ysop <C>atalog uild command to build the new CATALOG file for users to download. Using CAT-NORM Syntax: CAT-NORM [d:][path]filename[.ext] [n] [e] [d:][path]filename[.ext] specifies the input file(s) to be processed. If the input drive or path are not specified, the current default directory will be assumed. Wildcards are allowed, e.g. "*.CAT". [n] specifies the starting column of the description in the input file(s). If this value is less than 13 or not specified, CAT-NORM will assume column 13. [e] specifies the number of catalog entries to be sorted. If not included, a value of 30,000 will be assumed. This value should be large enough to accomodate the number of elements to be sorted, but not so large as to cause the sort to fail for lack of resources. Examples: CAT-NORM *.DIR 34 This processes all files with an extent of "DIR". The descriptions in these files will be found starting in column 34. CAT-NORM C:\LOGIN\CATALOG This processes the file "CATALOG" in the "LOGIN" subdirectory of drive "C". The descriptions will be found in column 13. Limitations The number of entries that can be processed is limited to about 2 billion. Practically, the real limit will be the disk space available for the sort phase. Output File The file CAT-NORM.OUT will be created. If no lines are output to this file, it will be empty. If it already exists, all data in the old file will be lost. Operations Performed The following operations are performed to normalize input files: Tabs are expanded into spaces File names are normalized thus: file name and file extent are separated by "." embedded blanks are removed all characters are forced to upper case Entries with file names containing invalid characters are removed Leading and trailing blanks are trimmed from the description Entries with empty descriptions are removed The entries are sorted in ascending order by file name and description Duplicate entries are removed As a result, ROS can handle catalogs with file names in the format "NAME EXT" as well as the more conventional "NAME.EXT". Since duplicate entries will be removed, it is possible to merge catalogs from many sources without getting an output file that is too large to work with. ANY difference in two entries will cause both entries to be included, including differences in case. Since entries with filenames containing invalid characters (as defined by DOS) are removed, headers such as the following will not be included in the output file and do not have to be manually removed: +-------------------------------------------------------+ | ACCOUNTING Bookkeeping, taxes, inventory, etc. | +-------------------------------------------------------+ Upgrading from ROS 3.8x CAUTION: A backup of your current ROS 3.8x database should be made before performing the procedure described in this section. The ROS file update utility, ROS38-40.EXE, converts version 3.8x data files into the format expected by version 4.0. To use this program, copy it into the subdirectory containing your version 3.8x files and enter the following command: ROS38-40 After verifying the program will be run on version 3.8x files, all operations are automatic and require no additional inputs. The program may take several minutes to complete its conversions, depending on the size of the existing database. NOTE: ROS38-40.EXE will only operate correctly on version 3.8x files. Attempts to run the program using files from other versions of ROS will produce unpredictable results. OPERATION ROS maintains its support files in the sub-directory in which it starts. You can protect access to these files by not including this area in your setup or - if you need remote access - ensuring the access level of this area is set sufficiently high (250-255). Logging in the first time When you run ROS the first time, it will create the files it needs. ROS will signon and let you know what files it is making and then get the modem ready. When the status line appears, ROS is in an idling state and is ready for one of four actions: 1. a signal from the modem indicating an incoming call, or 2. a time initiated macro to start, or 3. a command from the console to shutdown, or 4. a command from the console indicating a local user. To log in locally, press the <Enter> key. After the "Name>" prompt appears, enter "SYSOP" as your full name and press <Enter>. This is a special name that ROS recognizes. Since this is the first time you have been on the system, ROS will prompt for a password - enter one of your choice. You are now logged into the system. As the sysop, you are automatically assigned an access level of 255. CAUTION: It is very important that you login as "sysop" and set your password before making the system available for others to use, otherwise they may get sysop privileges on your system! Status line A single line of information will be displayed on the bottom line of the local console screen at all times, even when the display is blanked. Two formats are used, one while ROS is waiting for a call and another when a user is actually logged into the system. When waiting for a call When ROS is waiting for a call, a status line with the following information will be displayed: Node | Memory | Time where Node the node number Memory the amount of working memory available to ROS (in bytes) Time the current time of day If a time initiated macro has been defined, an addition field will be displayed showing the date and time when this macro will start. When a user is logged in When a user is logged into ROS, a status line of the following form will be displayed: Node | Memory | Time | Icons | Speed | Access | Name | Phone | City, State where Node the node number Memory the amount of working memory available to ROS (in bytes) Time the time remaining to the current user Icons system status information: chat signal on remote online delayed shutdown enabled Speed the speed of the current remote user or the word "Internal" or "Local" Access the access level of the current user Name the name of the current user Phone the phone number of the current user City, State the city and state of the current user Local console commands while idling ┌───────────────────────────────────────────────┐ │F1: Help F2: Macro Start │ │F3: F4: │ │F5: Toggle Chat Signal F6: │ │F7: F8: │ │F9: F10: │ │Alt-X: Shutdown ROS Enter: Local Login │ └───────────────────────────────────────────────┘ F1: Help This command displays the help menu as shown above. F2: Macro Start If a time initiated macro has been installed, this key will start the macro as if the timer had expired. F5: Toggle Chat Signal This key will alternately disable and re-enable the chat signal. If a user requests chat during the chat period, this key may be used to turn off the console bell. Alt-X: Shutdown ROS This key will shutdown the system and return to the DOS prompt. Enter: Local Login Pressing the <Enter> key will take the modem off hook and allow you to proceed as if you were a remote caller. All operations except file transfer are available. Local console commands during remote operation The local console has several commands that may be used while the system is connected to a remote user: ┌───────────────────────────────────────────────┐ │F1: Help F2: │ │F3: F4: │ │F5: Toggle Chat Signal F6: Chat │ │F7: Toggle Remote F8: Validate User │ │F9: F10: │ │ : 5 Minute Increment : 5 Minute Decrement│ │ ^End: Immediately Logoff Current User │ │ Alt-X: Shutdown ROS after Current User │ │Alt-Fn: List ALTFn File │ └───────────────────────────────────────────────┘ F1: Help This command displays the help menu as shown above. F5: Toggle Chat Signal This key will alternately disable and re-enable the chat signal. If a user requests chat during the chat period, this key may be used to turn off the console bell. F6: Chat This key may be used by the sysop to initiate a chat or to answer a chat request from the user. F7: Toggle Remote This command alternately disables and re-enables the output to the remote system. Disabling the remote I/O is useful since local operations can proceed at full speed without waiting for the relatively slow modem. F8: Validate User This command may be used to validate a user while they are logged in. It is equivalent to using the Sysop <V>alidate command. : 5 Minute Increment This command will add five minutes to the user's time for the current session. : 5 Minute Decrement This command will subtract five minutes from the user's time for the current session. ^End: Immediately Logoff Current User This command will immediately disconnect the current user. No reason will be given. Alt-X: Shutdown ROS after Current User This command will cause ROS to shutdown after the current user logs out. Alt-Fn: List ALTFn File When any function key is pressed while the <Alt> key is held down, ROS will immediately display the contents of the associated ALTFn.xxx file. "n" is a number from 1 to 10 indicating the function key and "xxx" is either "ASC" or "ANS" depending on the operating mode of the current user. Using ROS on a Network ROS explicitly recognizes the following networks (other networks which emulate one or more of these may be compatible): 1. Novell's NetWare (ELS, Advanced, SFT) 2. MS-Net or compatible (SHARE must be loaded) 3. MS-Net compatible with NetBIOS machine name support 4. CBIS' Network-OS 5. Software Link's PC-MOS 386 6. Banyan's Vines 7. Alloy's NTNX In addition, ROS works well on a non-networked, single-user system. To specify the network, use the command line parameter "/Tx" where "x" is a number from "1" to "7" as shown in the above list. If this parameter is not included or if an invalid number is entered, ROS will assume no network is being used. When operating on a network, the parameter "/Ny" - where "y" is a number from "1" to "9" to specify the node - must be included. This number must be unique for each node. For example, to run ROS on a NetWare system, use a command line similar to the following: ROS /T1 /N3 When using ROS on a Novell NetWare system, NetWare specific calls to mark files as shareable are used; this service returns an error when the file is not on a server drive. This means that on a NetWare system, your files MUST reside on a net drive and cannot be located on a local drive. ROS is "DESQview aware" and, in addition to confining its video output to its own portion of the screen, will relinquish any unneeded time to tasks running in other windows. A DESQview window of approximately 440 k-bytes of memory is required. Command Line Options Several command line options are recognized by ROS: /d direct connect - ignore modem responses /i information on FOSSIL driver should be displayed locally /m modem information display /n node number /r reorganize user and catalog files /t type of network These options may be used in any order, with or without spaces separating them. Option /d This option causes ROS to ignore the modem. It is useful in two situations. First, there may be situations when you do not have a modem connected to the serial port or the modem is already off-hook and you do not want to hang up. Since modem commands and modem responses are inhibited with this command, it may also be used when there is no modem connected at all. In fact, the system may be connected to another computer. Option /i When this command line option is included, ROS will display additional information about the FOSSIL driver when it starts and as the FOSSIL driver is opened and closed. Option /m To assist in setting up your modem, the command line parameter "/m" may be used to display commands sent to the modem and responses from the modem. A left pointing triangle ("") indicates a carriage return, and a down pointing arrow ("") indicates a line feed. Option /r ROS can recover from many types of damage to the user and catalog files, and it can recover from corrupted or even missing index files (in fact, if you suspect that your index files may have become corrupted, simply delete them. ROS will rebuild them as necessary. This includes all ROS files with the ".IX" extension. To reorganize the user and catalog data files and subsequently rebuild the index files, you may add a "/r" to the command line. Normally, this option is not needed, but there may be times when it can improve or even restore system operation. For example, while ROS re-uses deleted records to keep the user and catalog databases as compact as possible, you may wish to use this option to physically remove the deleted records from the file. One situation in which you may need to recover your data and index files should never occur, but a disk failure or other serious system problem could cause damage to the data or index files. If you suspect that any of these files may be damaged, use this option. ROS commits to disk all system files frequently to minimize data loss. You can even reset or power down the computer while ROS is running without serious consequences, although this is not recommended. During execution, ROS will display counts of records processed and the supported data files on which it is working. Option /t This option tells ROS what type of network is being used. Please refer to the section titled "Using ROS on a Network" for more information. Option /n This option is for network use. Please refer to the section titles "Using ROS on a Network" for more information. MAINTENANCE As the sysop, you should regularly use ROS to read mail, validate new users, and release (or not) the new files uploaded to the system. A check may also be made of other messages and mail to ensure that they are appropriate to the philosophy of the system. Beware of messages and mail which contain credit card numbers, computer access codes, or other sensitive information. Sysop Menu The sysop command system is accessed by typing <X> at a message or file menu prompt. This command is not available to users below the alternate sysop access level. The following figure lists the commands available to the sysop. This menu may be displayed at any time by entering <?>. Subsequent sections describe each command in detail. Sysop Menu Exchange List Style Viewpoint ------------------------------------------------------------------ <C>atalog <L>ist files <S>etup <D>own at logout sers <V>ersions <X>pert toggle <F>iles <K>ey macros <A>udit trail <M>essages urge <G>oodbye (logout) <C>atalog This command provides access to the file catalog system. Refer to Section 13 for more information about setting up a new catalog. The following commands, described in the following sections, are available: Build Describe Edit Post Reconcile Global Quit Build This command builds two files, "CATALOG" and "LEADERS". The first is the contents of the catalog. The second is a list of the most frequently downloaded files. Both files will be built into the LOGIN file area. Describe Many sources are currently available for the descriptions that are to be included in your catalog. These sources include other bulletin board systems, catalog files you may be currently maintaining by hand, and other catalog systems. ROS provides this command to make use of these sources to speed the development of your catalog. When this command is executed, ROS will prompt for a file name (a full path name including drive may be entered) that contains file names and descriptions in the following format: name.ext description where "name.ext" is the file name and extension of a file which may be in your catalog and "description" is the description of that file. Up to 50 characters of description are allowed. After accepting the file name (a null name will exit this function), ROS will prompt for the column in which the description starts. ROS will then ask whether or not it should update existing descriptions. If the default "no" response is entered, only blank descriptions will be updated. If ROS finds the file name in the current catalog, and its description is currently blank, the description from the specified text file will be added. Existing descriptions will not be overwritten nor will files which are not in the catalog be added. If you answer "yes", existing descriptions will be changed. This option is useful if you want to edit your existing CATALOG with your favorite word processor and then feed this catalog back into ROS. NOTE: duplicate file names in different file areas may produce unexpected results since only the first entry will be changed. Use this option with care. This command may even be used to restore a completely destroyed catalog if the text file "CATALOG" is still available. Simply specify "CATALOG" for the input text file and column 29 for the column in which the description starts. For example, call another local BBS or two and download their descriptions. These descriptions do not have to be in any special order, nor does ROS care if there are blank lines or lines with special characters. What it is looking for is an exact match of the file name in columns 1-12 of the file. If this is found and the current catalog description is blank, the text description will be added to the catalog. Edit This command allows you to display and edit catalog entries. If the command has not been previously executed in the current session, the first record in the default file area will be displayed. Subsequent uses of this command will redisplay record displayed the last time the command was used. The following commands are available during editing: Area Forward Backward Select Next Previous Edit Delete Release Quit Area This command is used to change the file area currently being accessed. Forward This command changes the current file area to the next area alphabetically. ROS will then display the first record in that file area. File areas "wrap around," i.e. when the last file area is current, using this command will cause the first file area to become current. Backward This command changes the current file area to the previous area alphabetically. ROS will then display the first record in that file area. File areas "wrap around," i.e. when the first file area is current, using this command will cause the last file area to become current. Select This command allows you to select a specific file to be displayed from the current file area. Next The next alphabetical catalog entry will be displayed. If there are no more entries in the current file area, the next file area will be made current and the first record in that area will be displayed. Previous The previous alphabetical catalog entry will be displayed. If there are no more entries in the current file area, the previous file area will be made current and the last record in that area will be displayed. Edit This command positions the cursor at the first field of the record, ready to edit. As the <Enter> key is pressed, subsequent fields will be edited. The catalog fields are as follow: Home area This is the file area in which the file will spend most of its time. When a file is added to the system, by an upload or directly, this field should be set to reflect the file area most appropriate to the content of the file. For example, a new file, MYCB.ARC is uploaded to the system. The current area (see below) will be set to "UPLOAD" automatically. Upon determining the file is another checkbook balancing program, you may decide that the file belongs in the ACCOUNTING file area. The home area should be set to "ACCOUNTING." After the file has been in the NEWIN area for a time, it will be moved to the "ACCOUNTING" area when the ost command is executed. Current area This is the file area where the file can presently be found. If this field is changed, the file will be automatically relocated to its new area. Name The name of the file Description The textual description of the file Size The file size in bytes Accesses The number of times the file has been downloaded Upload date The date the file was uploaded to the system Uploaded by The user that performed the upload Last download The date and time of the last download Normal editing commands are available on all fields except the last two, "Uploaded by" and "Last download." Please refer to the ROS User's Guide for more information on the editor. Delete This command will delete the current catalog entry and its associated file. Both actions are verified before taking place. Release This command is used to release a file into the NEWIN file area, thus making it available to users. Quit This command exits the catalog entry editor. Post This command automatically performs most of the housekeeping that a large file repository, such as a BBS, needs. For example, new versions of files are added to the system, old versions must be purged, changes to the file area structure may have to be made, etc. The name of file and its description are entered by the user and the other fields are set by the system when the file is uploaded. The sysop then sets the "Home area" and releases the file to the NEWIN area. The "Upload date" and the "Last access" field are used to determine when a posting action should take place. After a file has been in the NEWIN area for "Newin" days, it will be moved to its Home Area. After a file has been in its Home Area for "Other" days without being accessed, it will be moved to the DUSTY area. This area indicates to users that after "Dusty" days without access, the file will be removed from the system. From DUSTY, the file is moved to the ARCHIVE file area (which should not available to users). Files in this area then may be copied to a backup media such as floppy disk or tape and then deleted. The migration of files through the system can be displayed thus: NEWIN --> home area --> DUSTY --> ARCHIVE --> deleted ROS will not actually delete any files from the system. This is left to the sysop. Note the difference in the way ROS determines expiration for the NEWIN area compared to all other file areas: in NEWIN, "Upload date" is used, while "Last access" is used elsewhere. Reconcile This command is used to ensure the physical directory and the catalog maintained by ROS are in agreement. If a change in the file size is made, this command will detect this change and update the catalog. If files are listed in the catalog, but not found in the disk directory, ROS will mark them as missing. If files are found in the disk directory, but not in the catalog, ROS will add them. Since pictures are such a popular item, ROS can even automatically add the size (in pixels) of .GIF files to the file description. Global This command changes the "home" and "current" area fields from one value to another. For example, you have decided that "TOOLS" is a better file area name than "PROGRAMS." After making the change in ROSSETUP, you start ROS and enter this command to effect the change for all the catalog entries. No files are moved, only the catalog and its associated index files are updated. NOTE: If the ROSSETUP is changed and the catalog entries are not, users will not have access to the files. Quit This command terminates the catalog edit session. sers This command allows the sysop to display and edit user records. The first time this command is used in a session, the first record in the user file will be displayed. Subsequent uses of this command will redisplay the last record edited. The following commands, described in subsequent sections, are available to move around the user file: Registered Select Next Previous Edit Delete Insert Validate Force Quit Registered This command will search for a user that has registered for validation. If the displayed record does not change, there are no more registered users. Select When this command is entered, ROS will prompt for a new user name and then display that user for edit. Access level restrictions similar to those described for the next record command apply. Next When this command is entered, ROS will find the next user record (alphabetically by last name and then first name) and display it for edit. Only records with access levels equal or less than the user will be displayed, e.g. alternate sysops cannot modify or even view the primary sysop record. Previous When this command is entered, ROS will find the previous user record (alphabetically by last name and then first name) and display it for edit. Access level restrictions similar to those described for the next record apply. Edit The cursor will be positioned at the "Name" field for editing using commands identical to those used for messages (refer to the ROS User's Guide). All fields except the time of last access can be edited. ROS does not require precise entry of the user name to find a record for editing. It will find the record which is equal to or greater than the entered name. For example, if you cannot remember how John Smith spells his last name, enter "John" for the first name and "Smith" for the last name. ROS will find the record even if John spells his last name "Smithe." While this is a useful feature, similar names can result in the display of a record other than the one desired. Ensure the desired record is actually displayed before making changes. Delete ROS will prompt to verify that this is the action desired. If so, it will delete the user and any messages addressed to or from that user. Insert This command may be used to add a new user to the system. ROS will verify that the name does not already exist. If not, it will prompt for the new password and then display the record for further edits. This command is especially useful for closed systems where new users are not allowed to register on-line. Validate This command changes the access level and time allowance for the user being edited to the values defined by ROSSETUP. It is more convenient than editing the user and can be performed easily from a remote site. Force Since passwords cannot be viewed, this command is available to enter a new password for a user. The new password will echo as it is typed. Quit When all user records have been edited, enter this command and ROS will return to the sysop menu. <K>ey Macros In addition to being able to read characters from either the keyboard or the remote channel, ROS can read from internal character strings called "macros." These strings can be used to execute any sequence of operations as defined by the sysop. Since some of the system maintenance commands can take some time to complete, macros are very useful. In addition to the text editing commands described in the ROS User's Guide, pressing for "Begin" will cause ROS to prompt for the macro number to execute. Since the macro file is a standard text file, most text editors and word processors that can operate in a pure ASCII mode can also be used to edit the ROS-MAC.DAT file. ROS is still monitoring both the local and remote keyboards while processing a macro so the sysop can pause (^S) or cancel (^C) a command. Since a carriage return is used to terminate the entry of a new macro string, a slash (/) may be entered into the macro. When encountered, ROS will convert this character into a carriage return. As shown in the example, control characters may be entered by prefixing a standard letter with a carat ("^"). For example, CTRL-G may be inserted into a macro with the two character string "^G". Time Initiated Macro If the macro starts with a colon and a time of day, e.g. ":00:15", ROS will use this time to automatically start the macro execution. Only one time initiated macro is allowed. Macro Example The sample macro file included with ROS performs the following: :4 00:01,sysop/nnnodaily1/xapaycpbqmodaily2/xcrlogin/yqagy :4 node to run the macro 00:01, macro start time and separator sysop/ user name terminated with a carriage return nnn answer "no" three times to clear any questions o open a door daily1/ name of door x enter the sysop system a turn on the audit trail p purge... a ...all files y yes, really do it c start the catalog processor p post the files b build a new text catalog and leaders list q quit the catalog processor m back to the messages system o open another door daily2/ name of door x back to sysop system c catalog r reconcile... login/ ...the LOGIN file area (ensures the two files we just built are up to date) n no, don't update any .GIF files q quit the catalog processor a turn off the audit trail g goodbye y yes, really urge This command purges selected files of outdated entries. It processes three different files, each selectable by a single command, or all three files together. All commands are verified before continuing. All This command purges all three files, i.e. it automatically performs a purge of the catlalog, log, and user files. Catalog This command purges the file catalog system of any entries that are currently marked as "Missing." Log This command removes entries from the log file that are more than seven days old. Users This command deletes all users that have not logged in within the times specified in ROSSETUP. When a user is purged with this command, any messages sent to or from that user will also be deleted. <L>ist system files When this command is entered, two secondary commands may be entered to select which file should be listed. Log ROS maintains a time and date tagged list of most system operations. This command will display this list. From the information contained in this file, you can determine what kind of activity the system is being used for, what users seem to be having problems, what users are abusing their privileges, etc. Messages All messages after the specified date will be displayed in chronological order. <V>ersions This command displays the version numbers of DOS, DESQview (if installed), and ROS. <S>etup This command starts ROSSETUP for the current mode, if logged in locally. Remote operation of this command is not currently allowed. <X>pert mode toggle In the sysop sub-system, pressing <X> will alternate between Expert and Novice help levels, similar to the results normal users see when pressing <X> at either the Files or Messages menu. <A>udit trail This command allows you to create a standard ASCII text file from any system output. The audit trail file name is "ROS-AUDT.x" where "x" is the number of the node. If this file already exists, it will be appended to. If it does not, it will be created. <D>own at logout This command is equivalent to pressing the <Alt-X> key from the local console. When the current user logs out, ROS will shutdown and return to DOS. <F>iles This command causes ROS to exit the sysop menu and enter the file menu. <M>essages This command causes ROS to exit the sysop menu and enter the message menu. <G>oodbye (logout) This command terminates the session. Command Enhancements Naturally, all the user commands are available to the sysop. In addition, several commands are enhanced when used by the sysop. Changing a Message Status or Message Area After reading a message, the sysop will be given the option of altering the message area or status of the message. The options are as follow: <M>ove move the message to another message area ndividual mark the message as private <O>pen make the message an open letter, i.e. "Public" <D>elete delete the message, even if not the sender or reciever Note that all of these commands are available for any message that can be displayed by the sysop, even one addressed to someone else. Setting the System Time and Date After The nfo <S>ystem command displays the PSTAT file, you will be given the option of changing the current system time and date. User List Additions When the user list is requested, ROS will allow the sysop to enter one of four parameters: <A>ll List all the fields in the user records. The sysop may select either <C>olumnar (fixed field length) or <D>elimited (comma separated) format. When captured using the <A>dit command, the output from this command is suitable for import into many database management systems. Two files, "ROSUSER.DB" and "ROSUSER.DBF" are included for use with Paradox and dBaseIV respectively. <E>xceptional List users with an access level or time limit greater than that set for validated users. nvalidated List unvalidated, unregistered users. <Q>uick List user names only (this is the same listing normal users get). EXTENDED DISPLAY CODES When ROS is displaying text, it checks for an embedded ^B (control-B). If it finds one, it replaces the number following with a value retrieved from the system, at that time. This means, for example, that you can include the user's name and birthday right in their login screen. Many values are available (see the table below). In addition, several codes are used to control system operation. The syntax of an Extended Display Code (EDC) is as follows: nnn["x"] The smiley face above is a ^B. The "nnn" indicates a three digit number from 0-999 as described in the table below. ["x"] indicates an optional parameter that must be enclosed in quotation marks if included. When used to define a numeric field, the following values may be entered: # A digit position. Unused digits are printed as blanks. * A digit position. Unused digits are printed as asterisks instead of blanks. Needs occur only once to activate this effect. @ A digit position. Unused digits are printed as zeros instead of blanks. Needs occur only once to activate this effect. $ A digit position. A floating dollar sign is returned in front of the number. Needs occur only once to activate this effect. Other characters (including commas and periods) will be inserted literally. For example, the following are valid fields: "##,###,###" "*$###,###" When used to define a time-of-day field, the following values may be entered: h or H Hours m or M Minutes s or S Seconds : Colon character t Displays "a" or "p" e Displays "m" Lowercase formatting characters cause numbers to be padded with "0". Uppercase formatting characters cause numbers to be padded with spaces. For example, if the time of day is 1:15 in the afternoon, a mask of "Hh:mm te" would produce " 1:15 pm". A special case exists for date formatting. If the parameter field is "1", then displayed dates will be in the format "mm/dd/yy". Otherwise, dates will be displayed as "dd mmm yyyy". A second special case exists for codes 4-6 where the parameter field is used to specify the width of the string field for text justification. See the accompanying .ASC and .ANS files for more examples. The file TEST.ASC activates all possible codes (though not all possible numeric formats). To use, append it to one of your menus such as MNUSYSOP.ASC and use the menu display command (<?>) to bring it up or rename the file to a bulletin, such as "BULLET.ASC" and select bulletin "ET" from the bulletin menu. Invalid EDC's will be ignored by ROS (and displayed to the user unchanged), but future versions of ROS may use any numbers from 0-999. While the message editor will not allow the entry of ^B characters, the sysop can use the <L>oad command to send personalized messages to users that contain EDC's. See the accompanying .MSG files for examples. NOTE: when using EDC's in files with ANSI sequences (.ANS), ensure the ^B is not separated from the numeric code. For example, in the file LOGOUT1.ANS, the user's session duration (login time) is shown in a different color. It is imperative that this color change take place before the ^B, not between the ^B and the EDC number. Miscellaneous System Controls 000: Turn off break (^C) checking 001: Turn off line count checking ("More..." prompts) 002: Immediate "More..." prompt 003: Delay for period specified in miliseconds (1000 = 1 second) 004: Left justification - width specified in param 005: Center justification - width specified in param 006: Right justificiation - width specified in param 007: Turn off justification System Values 100: Current time and date 101: Current version of ROS 110: Node id 111: System name 112: Sysop name 113: Max tries allowed for password 114: Daily download count limit 115: Daily download size limit 116: Chat start time 117: Chat end time 120: System startup date/time 121: Caller number User's Personal Information 200: First name 201: Last name 202: Address 203: City 204: State 205: ZIP 206: Phone #1 207: Phone #2 208: Birthday 209: User's system description User's Settings 220: Message area 221: File area 222: Transfer protocol 223: Columns 224: Lines 225: Color User's General Statistics 240: Login date/time 241: Time on 242: Time left 243: Times on 244: Last login date/time 245: Time allowed 246: Total time used 247: Extra time 248: Last high message number User's File Transfer Stats 260: Download count today 261: Download size today 262: Download count total 263: Download size total 264: Upload count today 265: Upload size today 266: Upload count total 267: Upload size total 268: Download count / Upload count 269: Download size / Upload size User's Authorizations 280: Access level 281: Time limit 282: Expiration date Messages Menu Values 300: Messages in database 301: Next message number Files Menu Values 400: Files in database WARNING AND ERROR MESSAGES ROS has three categories of messages: "Warning," "Error," and "Fatal error." The first two categories indicate situations or problems you should be aware of but that have been handled by the system. Fatal Errors are those errors that are so severe that ROS cannot recover and has done its best to close all open files and shutdown. The following lists errors that may be encountered: DOS errors 0001:Invalid DOS function code 0002:File not found 0003:Path not found 0004:Too many open files 0005:Access denied 0006:Invalid handle 0008:Not enough memory 0010:Invalid environment 0011:Invalid format 0012:Invalid file access code 0015:Invalid drive 0016:Cannot remove current directory 0017:Cannot rename across drives 0018:No more files I/O errors 0100:Disk read error 0101:Disk write error 0102:File not assigned 0103:File not open 0104:File not open for input 0105:File not open for output 0106:Invalid numeric format Critical errors 0150:Disk is write-protected 0151:Unknown unit 0152:Drive not ready 0153:Unknown command 0154:CRC error in data 0155:Bad request structure length 0156:Seek error 0157:Unknown media type 0158:Sector not found 0159:Printer out of paper 0160:Device write fault 0161:Device read fault 0162:Hardware failure Miscellaneous errors 0200:Division by zero 0201:Range check error 0202:Stack overflow error 0203:Heap overflow error 0204:Invalid pointer operation 0205:Floating point overflow 0206:Floating point underflow 0207:Invalid floating point operation 0208:Overlay manager not installed 0209:Overlay file read error Sort errors 1103:Not enough memory available for sorting 1108:Illegal item length 1109:Too many records to sort 1110:Write error during sort (disk full?) 1111:Read error during sort 1112:Could not create sort work file (directory full?) FOSSIL driver and modem errors 2000:FOSSIL driver not found 2001:FOSSIL version incompatible 2100:Modem not responding 2101:Modem returned an error File maintenance errors 3000:Source area not found 3001:Destination area not found 3002:Source file not found 3003:Destination file already exists 3004:Could not create destination file 3005:Could not delete source file 3006:Could not update catalog System errors 4000:System date not set 4001:Invalid system name File access errors 10500:Record modified by another user Note: this message may appear when editing a catalog record if the "Current area" is changed at the same time as another field in the record. To avoid this problem, edit only the "Current area" field during one pass. 10501:Record deleted by another user TECHNICAL SUPPORT AIS maintains a 24 hour, multi-line, bulletin board (running ROS, of course) as the best way to get answers to your questions. Message and file areas called "ROS" are available in which questions, comments, suggestions, and problems concerning ROS will be found. Public and private messages addressed to "Sysop" will be answered as quickly as possible. Regular updates to ROS will be found in the "ROS" file area. The BBS number is (505) 299-5974, 300-2400 bps, no parity, eight bit words, one stop bit (N-8-1). Technical support is also available through the mail at this address: ROS Technical Support Associated Information Services P.O. Box 13711 Albuquerque, NM 87112-3711 USA Your comments and suggestions are important and welcome. Please use the User Response Form to let us know what you think of ROS. INDEX address.........................31, 37 Albuquerque......................i, 37 ANSI.............................7, 30 answer................8, 9, 15, 20, 25 archive.............................22 areas.....................9, 20-22, 37 ASCII...........................24, 27 board........................1, 19, 37 bulletin.............1, 11, 19, 30, 37 change............5, 7, 20, 22, 23, 30 chat........................14, 15, 30 color........................7, 30, 31 comments............................37 connect..........................8, 17 connection...........................8 default.........................11, 20 deleted.................17, 22, 26, 35 directory....7, 10, 11, 13, 22, 33, 34 door............................10, 25 doors.............................1, 9 download.............11, 20, 22, 30-32 execute.............................24 goodbye.............................25 help..................3, 9, 14, 15, 27 license...........................3, 4 mail............................19, 37 newin...........................21, 22 others........................3, 8, 13 password.................5, 13, 24, 30 pause............................8, 25 pauses...............................8 program.............3, 4, 7, 9, 12, 21 prompt......13, 14, 19, 20, 23, 24, 30 prompts.............................30 protocol............................31 questions.......................25, 37 quit.................10, 19, 20, 22-25 read.................4, 19, 24, 33, 34 reading.............................27 ready....................9, 13, 21, 33 receive..............................4 refer............7, 10, 18, 19, 22, 24 registered....................4, 5, 23 related..............................3 release.....................19, 20, 22 remaining...........................14 remote.................1, 13-15, 24-26 replaces............................29 require...............3, 8, 10, 12, 24 respond...........................8, 9 responses.....................8, 9, 17 return........8-10, 14, 17, 24, 25, 27 returned........................29, 34 subsequent...................19-21, 23 toggle..............10, 14, 15, 19, 27 upload..................21, 22, 31, 32 wildcards...........................11