ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º º º The Opus CBCS System Manager º º º º Version 1.13 * August 8, 1990 º º º º Copyright (C) 1986-1990 by Tom Kashuba º º º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º°°° C o n t e n t s °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ o Introduction o Packing List o Requirements o Configuration o Operation o Quick Start o Licensing agreement o Revision History o Credits o Usage Notes Oman 1.13 The Opus System Manager Page 2 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º°°° I n t r o d u c t i o n °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ Oman, which is an integral part of the Opus CBCS system, is a general purpose utility that an Opus system operator uses to maintain the various aspects of the system such as: o User database o User menus o System area definitionso o Event schedule o Outbound mail area o Global data items In addition, it can also view the system log file in an easy to read, compressed format and can make dynamic changes to the active, compiled nodelist data file. Oman needs to know many things about how your Opus CBCS system and computer are configured. To know about these things, Oman takes its operational information from a combination of the Opus parameter file (eg, Opus.Prm), its own optional configuration file (eg, Oman.Cfg), command line switches, and/or the DOS environment variable, "OMAN=". Beside its several video modes, Oman can also be run remotely via FOSSIL controlled modem access. When operated remotely, it can be optionally set to request a password for added security and has carrier detect logic that will immediately terminate the program when the carrier is lost. ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º°°°° Packing List °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ The official Oman utility consists of the following files. Any further distribution of this kit must include all of these files, as is, without modifications of any kind. README.1ST Brief unpacking instructions. OMAN.PRN Documentation (Printer format w/form feeds) SAMPLE.CFG Sample configuration file. OMAN.EXE Main program Oman 1.13 The Opus System Manager Page 3 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º°°° R e q u i r e m e n t s °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ MEMORY Approximately 275k, depending on the functions used. DISK SPACE Approximately 300k. No major operational requirements. Just enough to hold the component files of this package with a little safety margin. OPERATING SYSTEM Although this product makes use of the extended path specifications that were first supported by MSDOS 2.0, the supporting libraries used to create it assume MSDOS 3.0 or higher. MSDOS 3.0 or higher is recommended. OPERATOR In order to maximize your use and enjoyment of Oman, you should be suitably attired in jeans and a T-shirt. Oman is liable to act unpredictably when in the presence of those who bodies are unduly punished by tight collars, ties, or jackets. If you can't roll around in it, take it off. KEYBOARD Local mode: When running in local (non-remote) mode, the program accepts standard ASCII, WordStar Ctrl-Codes, and IBM PC key codes. Remote mode: When running in remote mode (via modem), the program accepts ASCII or IBM PC key codes (if they can be sent). A limited translation of ANSI or VT-100 cursor keys is employed at the menu prompts for HOME, END, LEFT, and RIGHT keys for moving through records. FOSSIL INTERFACE PROGRAMS For remote operation or when using consoles that are not fully compatible with the IBM PC, a "FOSSIL" interface is required (Version 5 or greater) to make use of the "Video FOSSIL" or remote options. X00 by Ray Gwinn and OpusComm by Bob Hartman are examples of compatible FOSSIL interfaces. Oman 1.13 The Opus System Manager Page 4 CARE and FEEDING Oman has no special nutritional requirements but likes to be operated in airy, indirectly lit, open areas with the New Age album of your choice playing in the background. FILE FORMATS Oman works with all Opus v1.13 data files such as USER.DAT, SYSTEMxx.DAT, SCHED.DAT, etc. The outbound area files are more generic and Oman's outbound manager can work with outbound areas that conform to the model used by Opus, BinkleyTerm, Ommm, et al. REMOTE MODE When running in remote mode (via modem), the program requires a FOSSIL interface, Version 5 or greater. VIDEO SYSTEM Character Set The program primarily uses the IBM Extended ASCII character set as implemented on the IBM PC but makes minimal use of its text graphics codes (128-255). For those systems that have trouble displaying IBM text graphics, you can optionally request that all IBM Extended Graphics be translated into their nearest ASCII equivalents. See the section on the configuration file for details. Video Monitor The screen presentations in both local and remote modes utilizes 24 lines of 80 columns each and can be presented in either monochrome or color. Video Interface - Hardware Any controller that is compatible with the text modes of the IBM MDA or IBM CGA video controllers or any later models that are downward compatible such as the EGA and VGA. controllers. As bit mapped graphics are not used, such modes are not required. Oman 1.13 The Opus System Manager Page 5 Video Interface - Software The program has different software support requirements based upon its selected video mode. It defaults to using very standard DOS supervisor calls (slowest but safest) but can be set to use IBM-BIOS (faster), FOSSIL (most generic), or Direct Ram Write (very fastest) video routines. The following table lists the requirements for each mode. Video Mode Requirements IBM IBM PC/XT/AT compatible BIOS DOS MSDOS 2.1 or higher with ANSI.SYS FOSSIL FOSSIL driver (Version 5 or superset) RAM IBM CGA or MDA video buffer compatibility Oman 1.13 The Opus System Manager Page 6 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º°°° C o n f i g u r a t i o n °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ Oman's operational parameters are taken from up to four different sources which can all work together in an increasing order of precedence (as listed below): o Opus parameter file (eg, Opus.Prm) Oman can take nearly all of its operational control information from your active Opus.Prm file. Oman only needs to know what its name is by entering it on the command line. For example, the command, "OMAN Opus", will cause Oman to use the information from "Opus.Prm". o Oman configuration file (eg, Oman.Cfg) You can use an optional Oman configuration file, "Oman.Cfg", to set additional operational data as well as to override any of the item values it would otherwise use from the Opus parameter file given on the command line. o Oman Environment Variable "OMAN=" You can set a DOS environment variable, "OMAN=", which can specify the same values as those that can be entered on the command line (see command line, next). o DOS command line You usually just specific the name of the Opus parameter file on the DOS command line when you run Oman but you can also set certain parameters such as the video mode. Actually, the scanning order is a little more complex to allow for a wide range of control variations. The exact order in which these configuration sources are scanned is as follows: 1. Environment string "OMAN=" only for -C or -N parameters. 2. DOS Command line only for any -C parameter. 3. Default Configuration File (or as given by -Cpath). 4. Environment string "OMAN=" (all settings EXCEPT -C, -N) 5. DOS Command line (all settings EXCEPT -C or -N) As these sources are scanned in the above order, an option set in one overrides any like option set at a previous level. Please note that both the environment and the command line are scanned before and after the configuration file to allow you to give an alternate configuration file path. Oman 1.13 The Opus System Manager Page 7 Also note that although the -N switch looks like a command line switch, it is only meant to be used in the environment string and turns off command line scanning. This is the primary reason for environment string being scanned before the command line. That is, by setting the -N switch in the environment string, the command line will not be scanned. This feature is needed in some cases where a host program might unconditionally pass some command line parameters which are not compatible with Oman. However, as of Oman v1.13, there is no conflict between the parameters passed by Opus and those used by Oman. Oman will sense that it is being spawned from Opus and will interpret the command line correctly. ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ Configuration File ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ The configuration file, "OMAN.CFG", is optional and, if used, must be placed in the same directory in which Oman is located unless its path is explicitly defined on the command line or in the OMAN environment variable. It is a plain ASCII text file that contains configuration commands, one per line. Each command starts with a verb and is followed by a number of option settings as required for the particular verb. Blank lines and any portion of a line following a semi-colon are skipped completely. Therefor, prefix all comments with a ';'. Currently supported configuration commands: Command Syntax Description CMDline {ON|off} Scan command line options (or not) COLOR {ON|off} Force use of color (or not) HELP {path} Alternate path to the OMAN.HLP file OPUSSys {path} Opus "System" directory OPUSRoot {path} Directory where Opus resides GLOBAL {path\file.ext} Global (COMMON) data file DEFOCD {integer} Default Outbound Call Delay used when creating new events SYMBOLS {IBM|ASCII} Allow IBM graphics or convert them to their nearest ASCII equivalent. NETMSG {path} Netmail directory (future use) INFILE {path} Inbound files path (future use) Oman 1.13 The Opus System Manager Page 8 EXEC {OUTBOUND | NODELIST | USER | AREA | EVENTS | LOGVIEW } Start up with given function NETID {net addr} Prime address Zone:District/Node NETINFO {path} Nodelist directory path OUTbound {path} Outbound mail (Hold) path PARM {path\file} Opus parmfile path\file (no ext) SYSOP "{name}" Sysop's Name (use quotes) SYSTEM "{title}" System Name (use quotes) USERfile {path\file} User file path\name SYSOPIDX {path\file} Sysop Index a la FIDOUSER.LST ULIST {path\file.ext} Default user list device or file ALIST {path\file.ext} Default area list device or file SCHEDule {path\file.ext} Opus Schedule File VIDEO {IBM|DOS|FOSSIL|RAM [VideoSegment]} Video Method. If RAM, an optional second argument (4 hex digits) can be given to set the video buffer's segment address, eg, A000. LOGfile {path\file} Opus log file path\file FOSSIL {Active} Leave FOSSIL active on exit PORT {1|2} Remote operation via comm port. SPEED {baud rate} Remote baud rate, eg, 2400 REMPWD {password} Remote password NAKEDREQ Don't make POLL with File Requests XLTOUT {path\file.ext}[DUMP] 256 byte Output translate file with 1 byte per code. If a byte is a binary zero, the original character is send, as is. If the DUMP verb is present, the internal translate table is dumped to the given file name so only use it once to generate a starting translate file that you can then binary edit for custom translations. Oman 1.13 The Opus System Manager Page 9 OHMFMT {FILES|ZMODS|ZARCS|NOCALL|ALL} Sets outbound display detail. Sample configuration files ... The following configuration is for 100% compatible IBM PC or compatible and enables direct video RAM screen write for maximum video response. It also disables the use of color. Although the program automatically matches the color mode indicated by the BIOS flags they do not always reflect the desired mode. With this setup, the program can be run without any arguments. ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ ; ³ ³ ; Standard local PC configuration ³ ³ ; ³ ³ PARM C:\OPUS ; Use "C:\Opus.Prm" ³ ³ COLOR Off ; Forces monochrome ³ ³ VIDEO Ibm ; Video uses IBM BIOS ³ ³ ; ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ The following configuration autostarts the Outbound Manager whenever it runs and is for a machine whose BIOS does not match IBM's so the FOSSIL interface is requested for video operation. With this setup, the program can be run without any arguments. ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ ; ³ ³ ; Autorun Outbound, Use FOSSIL video ³ ³ ; ³ ³ PARM C:\OPUS ; Use "C:\Opus.Prm" ³ ³ EXEC Outbound ; Run OutBound Manager ³ ³ VIDEO Fossil ; Video uses FOSSIL calls ³ ³ ; ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ The following configuration sets up a forced remote operation at 2400 baud using the COM1: port and enables password control for the password "ABC". Since programs other then Opus might add command line arguments that are incompatible with Opus and Oman, the "CMD off" is used to suppress the scanning of the command line, avoiding incorrect or ambiguous reactions to it. Please note: the manual setting of the baud rate and communications port is not normally necessary when running Oman as a child of Opus because Opus will add the necessary command line switches. Instead, this example might be used in special cases where Oman needs to be run remotely outside of an Opus scenario. Oman 1.13 The Opus System Manager Page 10 Also note: the "VIDEO Fossil" command is actually redundant since the "Port" command will force the use of the FOSSIL interface. ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ ; ³ ³ ; Example OMAN configuration file (remote) ³ ³ ; ³ ³ PARM C:\OPUS ; Use "C:\Opus.Prm" ³ ³ EXEC Outbound ; Jump to NED ³ ³ VIDEO fossil ; Use FOSSIL ³ ³ PORT 1 ; Use COM1: ³ ³ SPEED 2400 ; Run at 2400 baud ³ ³ REMPWD ABC ; Ask/Verify password "ABC" ³ ³ ; ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ Other, Opus related environments? ... It is quite possible that OMAN can be used for related Opus environments such as Binkley, SeaDog, and Dutchie with judicious use of the configuration parameters. In such cases, though, Opus specific functions such as the user file, area, and menu managers would not be applicable. If running Oman as a child from a BBS, host, or netmail program stuffs the command line with arguments different than those of Opus or which do not use an Opus.Prm file, you will need to use the "CMDLINE OFF" configuration command to suppress OMAN' processing of the command line. Likewise, you probably should NOT have an "OMAN=" environmental string set as that is simply an alternative to command-line style processing. Keep in mind that the data files accessed must be compatible with Opus 1.13. Eg, NodeList.Dat, not NodeList.Sys. ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ DOS Environment ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ You can alter Oman's basic configuration using the DOS environment variable called "OMAN=" using exactly the same format and command set as for the command line. See the section on "Command Line Switches", for details on the available options. For example, to run with the Opus parameter file OPUS.PRM, an alternate configuration file "C:\OMAN2.CFG", with color forced OFF, and autostarting the Outbound Manager, you could place the following command in your AUTOEXEC.BAT file or execute it directly from DOS at some time prior to running the program: SET OMAN=OPUS -CC:\OMAN2.CFG -L0 -XO Then you need only run the DOS command "OMAN" to have all those options in effect. Note, however, that anything you might then enter on the command line will override the above settings. Oman 1.13 The Opus System Manager Page 11 ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ Environment String and Command Line Switches ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ The environmental string and command line switch format is as follows. Not that the [] enclose optional items and the {} enclose mandatory ones. In both cases, the brackets are not meant to entered and are only for descriptive clarity: OMAN [parmfile] [-opt1] [-opt2] ... [-optn] [parmfile] Opus parameter file path (w/o ext) -N Don't use command line (environment only) -Ccfgpath Alternate configuration file path. -L{0|1} Force color OFF (-L0) or ON (-L1) -V{I|D|F|R} Video mode: I)BM D)OS F)OSSIL R)AM -X{U|A|E|O|N|L|M|G} AutoRun USER, AREA, EVENTS, OUTBOUND, NODE, LOG, MENU, or GLOBAL managers -A{helppath} Alternate help file path -O{path} Outbound mail path -S Naked (starkers) Requests, ie, w/o POLL -O{path} Alternate outbound mail path -H List command line options to screen -W{pass} Remote password 'pass' -Z Leave FOSSIL active on exit These command switches are sent by Opus when it shells to an external program, such as Oman, but can also be entered, manually: -P{1|2} Remote COMM port 'n' (1 or 2) -B{baud} Remote baud rate of 'n' (1200,2400,etc) -K Local mode (from Sysop keyboard) -Fn User's current file area 'n' -Mn User's current message area 'n' -Rn User's remaining minutes 'n' -Tn Current Opus task no 'n' Oman 1.13 The Opus System Manager Page 12 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º°°° O p e r a t i o n °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ Invocation ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ The program is initially started by running it as a DOS command with any desired command line options to override the basic set up as defined in it's configuration file and/or the environment variable, "OMAN=". Oman will attempt to find its configuration file (if any) and its help file in the same directory where it resides unless these paths are specifically overridden. When executed in remote mode, it automatically enables carrier detect sensing and will instantly terminate upon loss of carrier to return to the parent program. Remote mode is typically only used when it is spawned as a 'child' of Opus or some other telecomm program. ÚÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ Main Menu ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÙ When the program is run without any autostart option, it displays a status screen with its operating parameters. Pressing {Enter} will bring you to the main menu which has the following options: U)ser Manager Manages the user file A)rea Manager Manages the area definitions M)enu Manager Manages the Opus Menu File(s) E)vent Manager Event Schedule Manager L)og Surveyor Pre-scans, displays, searches log file O)utbound Manager Manages the outbound mail area G)lobal Data Mgr Manages global data (eg: call count) N)odelist Manager Nodelist Display and Editor P)arameters Screen Return to opening parameter screen Q)uit Return to DOS (or parent program). From this menu, you request the other program functions and return to it when you exit from them. The Quit option exits the program and will return to DOS if the program was from the DOS command line or the host program if it was run as a "child" from it. Oman 1.13 The Opus System Manager Page 13 ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ Text field editing ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ The program has a fairly complete input text field editor that allows editing of new or old fields. Whenever you are asked for a text input line or to update an existing field, this editor takes over. Much like DOS-EDIT or other command line editors, it gives you the following line editing controls: Action Ctl-Keys Keypad Move left 1 char pos ^S [Left] Move right 1 char pos ^D [Right] Move to field start ^X [Home] Move to field end ^E [End] Move left 1 word ^A ^[Left] Move right 1 word ^F ^[Right] Delete curr char ^G [Del] Delete left char ^H [BS] Delete to end ^Y ^[Home] Delete to home ^T ^[End] End input/edit ^M [Return] Cancel Input (Clear field) ^[ [Escape] ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º°°° F u n c t i o n N o t e s °°°°°°°°°°°°°°°°°°°°°°°°°°°°°º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ This section contains brief notes on each of the major functions within Oman. Since most functions are screen oriented and relatively easy to use, detailled operational explanations have been left out of this section. You should use Oman's built-in Online Help System which is available on nearly all function menus via the help command (?). It offers specific, context sensitive help on each function. Oman 1.13 The Opus System Manager Page 14 ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ User Manager ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ SUMMARY: This function maintains the user file. It operates on the user file as defined in the active Opus.Prm file or in the Oman.Cfg file, if overridden therein. The operation of the User Manager is quite straight forward. Upon entry, you are shown the record of the first user which is typically the Sysop. You use the cursor keys to move about the records, making changes to the fields, as needed. To change any field of any one record, you use the highlighted keys that preface the field name. The Oman screen and Online Help system are your prime sources of information on the operation of any given function. Please use them. FEATURES: - Lists users by all, name, or location fields - Marks users as KILL for later removal by PACK - Packs users, removing records marked as KILL - Sorts users into any of several different orders - Finds user by name, location, marking, or with suspect data - Clears user's 24 hr time & DL limits - Resets a record to default values (ZAP) - Creates, tracks, and maintains Custom Welcome Files - Renumbers Custom Welcome Files during sorting and packing - Powerful GLOBAL editor for changes 'en masse' - Fully supports and maintains User Expiration Control data. - Automatically creates and maintains the user index NOTES: W)rite and R)estore: When any changes are made to a record, the "*UPD*" indicator lights up to remind you that you of that and that need to use the "W)rite" command to write the record back to the user file. It is done this way so that, should you inadvertently mangle a record, you still have a chance to use the "R)estore" command to reload the data from the user file. Oman 1.13 The Opus System Manager Page 15 Removing Records: To remove a record from the user file, you need to first mark it as KILL with the K)ILL command and then pack the file using the P)ACK command. The K)ILL command only sets a flag on the user record. It is the P)ACK command that physically recreates the file, dropping all records which have the KILL flag set. It is done this way so that you can take your time, mark records to be killed, review them, and, sometime later, physically remove them. In multitasking scenarios, this method allows you to do some routine maintenance while there is an Opus running in another partition or on another network CPU. It is only when using the P)ACK command that you need to have all Opera inactive. Oman tries to check that this is the case but common sense is always the best protection. REMEMBER: Never pack the user file when an Opus is using it. Doing so may destroy your user file. Viewing Filter The VIEW command allows you to limit the user records that the NEXT, PREVIOUS, and some LIST commands will display based on one or more criteria that you set on the full-screen VIEW setting screen. Any setting you make is stored on disk so that the next time you use the command, the previous settings will be retained so you can reuse them, as is, if applicable. The User Manager starts up with the view filter turned off. When you press (V)IEW, you can simply active the previous view settings with the (O)N command or you can edit the view criteria with the (D)EFINE command. When VIEW mode is turned ON, you can see records that are not in the view by jumping directly to them. When a displayed record is not in the view, the VIEW indicator also shows the words "OutOf". As soon as you use the NEXT or PREVIOUS movements commands, you will go to the next or previous record that is within the view. Global Edits The GLOBAL edit command is very powerful in that it works with the VIEW filter and allows you to make one or more changes to each and every record in the user file that matches the current view. Because of this relationship, the GLOBAL command first invokes the VIEW filter edit screen so you can verify or change the current VIEW settings. After that, you are then presented with an almost identical screen that lists the fields that you can globally change. Don't be confused by this. Although similar in appearance, they are quite different in function. Use the Online Help for more details. Oman 1.13 The Opus System Manager Page 16 ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ Area Manager ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ SUMMARY: The Area Manager maintains the System Area definition files, allowing you to make dynamic changes to the system areas. With it, you can change the paths, titles, privileges, keys, or other attributes of each area. It basically operates in a full screen, one area per screen, edit mode. Since any changes made dynamically will *not* be reflected in any existing control file definitions, you should run PEPPER after you make any changes so that your SALT control file will be kept up-to- date. The Oman screen and Online Help system are your prime sources of information on the operation of any given function. Please use them. NOTES: Default Record When first entering this function, a special DEFAULTS area is displayed. It behaves as if it were numerical area -1. That is, the lowest possible area that occurs BEFORE Area 0 and AFTER the highest allowable one. When you run the Area Manager for the very first time, a few of the DEFAULT fields, such as the HELP path, are set to those of System Area 0 and saved in a special defaults file called, "System.Def". Any subsequent saves of this special record will update that file for future use of the Area Manager. The C)opy command: The C)opy command is interesting in that it will copy all of an area's definitions to a new area. If the new area is already in use, you are asked to confirm your wish as it will obviously destroy any definitions that area currently has. W)rite and R)estore: When any changes are made to a record, the "*UPD*" indicator lights up to remind you that you of that and that need to use the "W)rite" command to write the record back to the area definition file. It is done this way so that, should you inadvertently mangle a record, you still have a chance to use the "R)estore" command to reload the data from the area definition file. Oman 1.13 The Opus System Manager Page 17 ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ Outbound Manager ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ SUMMARY: This function starts up by scanning the outbound mail area, storing in memory information about the items found, sorts them into address order, and displays them in a visually coordinated fashion similar to a spread-sheet program. FEATURES: - Supports OMMM and Binkley style zoned directories - Lists outbound area in Lotus-like format - Lists the files within Attached file lists (FLO's). - Lists empty, zero-length ARCmail entries. - Lists incomplete Zmodem transfer file markers. - Lists From/To/Subj of messages in unarced packets. - Readdresses pending outbound mail objects - Changes bundle priority (Hold, Direct, Normal, Crash) - Deletes bundles, file lists, ArcMail, and others. - Creates POLLs using Null FidoNet Packets ("Bundles") - Creates File Requests (with matching POLL object) - Creates File Attaches (directly creates .?LO file) - Built-in DOS directory command - Merges bundles when needed due to address changes. - Merges file lists when needed due to address changes. - Deletes null archives, "no call" and Zmodem markers. - Runs DOS command from outbound menu. - Full Screen File Request and Send editor. The tabular display shows several selectable levels of detail: - Mail bundles, archives, file lists and bad call markers. - Archived mail bundles and file attach list contents. - Spent mail archives of zero length All objects are sequentially numbered for the ease of subsequent activities which one might group as: - Readdressing - Priority changing - House keeping - Inspection - File Request and File Sends Oman 1.13 The Opus System Manager Page 18 NOTES: The Outbound Manager's options are fairly self-explanatory and a help key is available that invokes the Oman Online Help system. Please use it for more details on specific functions and fields. In addition to modifying the characteristics of existing objects, you can create proper, zero-length, POLL packets, WaZoo (.REQ) File Requests, or File Send lists (.FLO). With the Re-prioritizing commands of Norm, Crash, Hold, Direct, and Leave, you can create subtle routing and sending variations for the most situations. For example, if your bundler program is set to HOLD all mail to a particular address but you wish to allow one particular message bundle to go out right away, you could set that one message bundle to something like LEAVE, DIRECT, or CRASH (something that will escape the bundler's HOLD), then run your normal bundling procedure, then reset that special bundle back to NORMAL or leave it as CRASH. Zoned Operation When multiple, zone-specific outbound directories are used as with zoned operation of the BinkleyTerm and Ommm mail packing programs, then the directory for the default zone is the one that is first scanned and displayed. After that, the Z)one command can be used to switch between zones. Any changes to the zone segment of an object's address will "toss" the object into zone-specific directory for that zone. If the no directory has been created for the object, then a rename error will be reported and the address change will fail, safely. Please note that Opus does not directly support zoned directories. However, with a little batch file magic, you can easily emulate zoned outbound mail operations by running several netmail events, one for each zone that you support. During each of those event periods, you run Opus with separate parameter files, each of which specifies a different (zoned) outbound directory. Entering Addresses When readdressing an mail object, you can enter any or all address components. Only those that are given will be changed while those that are not will default to corresponding part of the original address. For example: 3: Change zone to 3 (tosses object) /111 Change node to 111 123/ Change district to 123 2:/12 Change zone to 2, node to 12 (tosses object) Oman 1.13 The Opus System Manager Page 19 ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ Nodelist Editor ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ SUMMARY: The Nodelist Editor, allows the Sysop to directly edit the actual Nodelist Data and Index files. Like the User and Area Managers, it displays one record (Node) per screen. You can edit, search, jump to, insert, or delete nodes in the current, compiled nodelist data. FEATURES: The EDIT function changes the current record's: o System Name o User & Call cost o System Password o Hub node o Miscellaneous Info o All user bit flags o Telephone number o Modem type & speed The INSERT and DELETE functions are handy for those times in between official nodelist updates when you wish to add a new node or remove one that has left the net. Note, this does not change the original nodelist.### file but DOES directly modify the working files. The LIST mode, lists for each node, one per line, ... o Nodelist position o Miscellaneous Info o Network address o Telephone number o System Name o Continuous mail flag. o Zone, Region, Host, Hub nodes are high-lighted NOTES: It is important to note that all work is done on the compiled nodelist file and its index. Should anything go wrong or you find yourself edited into a corner, you can simply recompile your original, distribution nodelist. Please remember that the prime use of Nodelist Editor is to make TEMPORARY updates to your nodelist while waiting for subsequent updates of the distributed nodelist. More elaborate updating is not recommended since the next nodelist compilation will erase what you've done. Due to the size of the current nodelist, the nodelist data file is now in excess of 800k. For this reason, as well as for speed, all INSERTS and DELETES of nodes are done IN PLACE in the live nodelist without virtue of a back up. When INSERTING a new node, all records above the insert point are shifted up by one, the new one is added where it belongs and the index is rewritten. When DELETING a node, all records are shifted down to the deletion point, the be deleted is overwritten by the shift, DOS is asked to resize the file, and the updated index is rewritten to disk. Oman 1.13 The Opus System Manager Page 20 Sysop Name Search The Sysop Name search is invoked by the F)ind O)perator command and will search the sysop index for a sysop's name and display the corresponding node and then ask whether you want to seek out any next or previous name that also matches the given text. Normally, the text you enter is taken to be (at least) the beginning portion of the sysop's last name. If you enter two words, then the program assumes you have entered a *full* name and reverse the words, with a comma, into phone book format. Because of this, you should only enter two words when it is a full name. Eg, a partial, two word name, like "Tom K", would end up as "K, Tom". If you were looking for me, you might enter "Tom Kashuba", "Kashuba", or, maybe, "Kash". When entering names in the above manner, a binary search is performed on the sysop index. It is very fast but relies on your input being last name based. If you are not sure of the name and only recollect a text fragment of it, you can request a linear search that will search each and every record for any name that contains the given text. To request this kind of search, you prefix your text with a question mark (?). When requesting a linear search (?text), you should only enter a single, small piece of text without spaces. Spaces trigger an attempt to reverse the text into the reverse name order that the sysop index is stored in and would probably result in a search text that is not what you intended. Regardless of method, whenever a match is found, you are asked whether you want to find the next or previous match. This allows you to choose among several nodes whose sysop names match the the search text. When a binary search is requested (without '?') but no match is found, you are asked if you want to try again using the linear (or "W)ild") search. If you request it, then the same text you entered for the binary search is used, again, for a linear search. This is adequate if you entered a short, single piece of text but will probably do no better if you entered what you thought was a full, correct name. When unsure of a sysop's name, use the linear search with just a short name fragment that you are sure exists within the desired name. Eg, if you know he or she was Irish and had "Mc" in their name, you would enter "?mc". Likewise, if the sysop's first name was John, then use "?John". By reverse, if you entered "John", then only those whose last name starts with "John" would be found such as "Johns", "Johnston", and so on. Oman 1.13 The Opus System Manager Page 21 ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ Event Manager ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ SUMMARY: The Event Manager is a full screen, tabular editor that allows the complete editing of all events that comprise an Opus schedule. With the editor, you can add, delete, activate, deactivate, or modify events of all types. Use the Event Manager's Online Help for detailled information on all of the various event types and fields. ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ Menu Manager ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ SUMMARY: The Menu Manager allows the editing of the Menu file that contains all of the Opus menus that are available to callers. It allows the addition, deletion, and modification all menu commands on all menus. For each command on every menu, you can edit the command's: - Command's Title - Minimum Privilege to access the command - Minimum user keys required to access the command - Internal Opus command to execute - Optional data required by some commands Oman 1.13 The Opus System Manager Page 22 ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ Global Manager ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ SUMMARY: This function manages those items that are of a global nature, ie, applicable to all running Opus systems, regardless of their task. For now, that means just the Quote Pointer, System Call Count, and the Maximum Task Number (future use). NOTES: The Quote Pointer and Call Count are initially stored in the predefined Schedule File. But, if a COMMON DATA file is defined, then these fields are stored in that file and updated there, instead. When a COMMON DATA file is defined, Opus continues to update the Call Count in the Schedule Fie, as well. Since most multi-line Sysops define separate schedules for each line's task, the Call Count in the COMMON DATA file will then reflect the total calls to the system across all lines and the Call Count in each individual schedule file will reflect the total calls to each line. The Global Manager displays the fields from both the currently defined schedule as well as from the COMMON DATA file for editing and viewing convenience. ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ Log Surveyor ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ SUMMARY: The Log Surveyor prescans the Opus log and displays it in a tabular, compressed, and highlighted manner that makes it easy to review all logged activity. For very large logs, it asks you choose what 1/10 of the log you want to review. NOTES: When requesting this function, Oman prescans the log then jumps to the last page of log entries. From then on, you can jump, by page, forward or backward in the log file. Each log session has the first applicable entry for that session highlighted so that sessions are clearly delineated. Log session are broken into the three classes of Opus, User, and NetMail, each being displayed with different screen attributes. Oman 1.13 The Opus System Manager Page 23 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º°°° Q u i c k S t a r t °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ If you are masochistic and have found your way to this section without reading the rest of the notes, then here's how to get the program up and running, quickly (at your own risk). 1) Place the Oman files in the directory where you put your commonly used Opus utilities. The Opus home directory is most often used. 2) If desired, create a configuration file using one of the simple examples in the configuration section of this document. You usually won't need to do this if you are willing to put up with the absolute slowest video display method that it defaults to (DOS). 3) Run the program, specifying the Opus parameter file name (without extension) on the command line. Eg, if your Opus parameter file is called Opus.Prm, then you would start Oman with the DOS command: "OMAN Opus". If you have a 100% CGA or MDA compatible video adaptor, then you can use Oman's fastest video mode (RAM) by adding the command line switch "-vr" as in "OMAN OPUS -VR". However, once you set up your Oman configuration file, you can set this mode there and won't have to use the above switch. The program will start up and display the parameters screen. Any key will bring you to the main menu and you're off and running. As stated elsewhere, however, there are several run-time options to better customize it to your individual needs but to properly use them, you'll just have to read the documentation. ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º°°°° Licensing Agreement °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ This product is an integral part of the Opus CBCS system and is copyrighted by Tom Kashuba. There is no charge for it use and it may distributed, copied, or used by any person or group as long as all of the terms and conditions associated with the Opus CBCS system are adhered to. This product may only be distributed in its full, unadulterated form with all the files listed under "Packing List". All queries concerning this, or any other part of the Opus CBCS system should be directed toward the nearest OpusInfo system. Oman 1.13 The Opus System Manager Page 24 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º°°° R e v i s i o n H i s t o r y °°°°°°°°°°°°°°°°°°°°°°°°°º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ Version 1.13, 90/08/01 (Changes since Oman v1.10b) ______________________________________________________________ User Manager - Recolorized the UserMgr's color palette to tone it down a bit. This only affects color CRT users. - Due to some long standing confusion over the way records were "marked" for removal or (long ago obsolete) for reuse by Opus and also to reduce the required keystrokes, I have changed the way you mark records for later removal. Previously, the (M)ark command was just a prefacing command to then set the PURGE or GROUP marks. Because of that, you had to press (M)ark (P)urge (W)rite to mark a record for removal. The (M)ark step is no longer needed as the (K)ill command now directly sets the flag to mark records for later removal. As a spin-off of this segregation, the new (T)ag command now prefaces any Group letter you want to attach. See next two items for more detail. - The PURGE mark is now called KILL and is set with the (K)ill command. This was done to give it its own key (K) in all functions that use it, without having to use the, now obsolete, (M)ark command, first. So, PURGE no longer exists in any way, shape, or form. It's KILL, with a (K). - As part of the above command re-alignment, a record's GROUP marks are now set by first using the (T)ag command. That is, you "tag" a record with a GROUP letter (A-H). Eg, to tag a record as being part of Group 'B', you would enter (T)(B). - Stomped several more mites to do with the updating of CWF indicator when in the CWF Manager sub-menu and when APPEND'ing a virgin user record. - Fixed problem with CWF flag updating while in the CWF Manager. - F)ind [Name or Locale] now accepts leading/trailing spaces - F)ind [Name or Locale] now matches any field text - L)ist [Name or Locale] now accepts leading/trailing spaces - L)ist [Name or Locale] now matches text anywhere in the field - O)utput: Fixed mite that scrolled screen w/ESC at Output Path - V)iew: Now allows -days (expired) in last call age range Oman 1.13 The Opus System Manager Page 25 ______________________________________________________________ Nodelist Editor - Recolorized the screen - Added Sysop Index search which will search a sysop index of the FIDOUSER.LST variety for a sysop name and display the corresponding node. See "Function Notes" pertaining to the NodeList Editor for more details. - For the above feature, the statement "SysopIdx (filepath)" has been added to the configuration file. If present in the CFG file, the given path is taken to be the Sysop Index to use. Whatever its name, it must exactly conform to the 62 byte, ASCII record format, of the FIDOUSER.LST file used by Opus and many other systems. If no SysopIdx statement is used, the file and path default to "FIDOUSER.LST" in the Opus 'NetInfo' directory. - Added "SysopIdx" path to parameter screen. - The "Write or Restore First" message one gets when trying to move to another record while important changes have been made now directly accepts the (W) or (R) to execute those functions rather than having to hit return, first. Saves a keypress. - Added access to help facility (?) from Nodelist Editor Menu. - Entry of any digit (0-9) now triggers prompting for the rest of the record number to jump to, superseding the purpose of previous (J)umpTo command which has been removed. Saves a keystroke. - All F)ind functions should now work as advertised. ______________________________________________________________ Area Manager - Recolorized screen - Added Z)ap command to clear an area record back to defaults. - Added Echo.Ctl skeleton maker which will create an Echo.Ctl file skeleton from Area Record Data for special cases only. Oman 1.13 The Opus System Manager Page 26 ______________________________________________________________ Outbound Manager - Recolorized screen - Alter code to allow start-up into empty outbound areas. - Due to changes in the MSC 6.0 memory allocation libraries, there should now be less problems with the handling of cases where all outbound objects are deleted. Previously, there had been some reports of the zero object case causing problems. I tested multiple cases and haven't been able to generate any further anomalies of that nature. If any of those who had such problems in the past continue to, let me know. Thanks. - Changed header title to 'OutboundMgr' from 'MailMgr' to avoid being mistaken for a message edit function. ______________________________________________________________ Global Data Editor - Tweaked some of the field edit code - Redesigned screen layout and coloring. - Added concurrent display and edit of COMMON and EVENT DATA. - Added edit access to the Maximum Task field of the COMMON DATA record. This is mostly for future use. - Added access to the OnLine System via the (?) command. ______________________________________________________________ Events Manager - Recolorized screen - Added support for the FileReqLimit field in Behavior Records. Use of the 'R' command while on a Behavior Event line will now asks whether you want to set the "E)rrorOffset" or the F)ileReqLimit". If FileRequest Limit is chosen, then the ErrorLevel field is used to display the FileRequest Limit. - Added "DEFOCD n" CFG statement to set the default Outbound Call Delay that is used for new schedules or new events inserted within existing schedules. Oman 1.13 The Opus System Manager Page 27 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º°°° C r e d i t s °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ The credits for those who have contributed to existence of Oman and Opus could fill volumes. As with all things in the PC BBS world as we now know it, there are many pioneers and contributors without whose help we would not have what we have now. Here's a partial list of those who have most affected my work in one way or another: ... Ward Christensen ... Ward has to get top billing for creating and donating X-Modem, the first reliable and well documented method of exchanging binary files using those new fangled things called modems. To this day, despite its age and due to its simplicity, it is the most commonly found file exchange protocol in the world. ... Tom Jennings ... It almost goes without saying that the entire Opus project, and the world of FidoNet electronic mail, is based almost exclusively upon the original online PC communications system model created by Tom Jennings, as first manifested in his Fido Bulletin Board Software. The Fido BBS model, first exemplified the monolithic control program, BBS electronic mail, and the use of the C language in PC telecommunications. ... Wynn Wagner III ... Wynn's Opus CBCS model advanced the Fido model, further still, with more advanced and efficient telecommunications methods, the inclusion of Z-Modem file exchanges, the WaZoo netmail protocol, and a host of other innovations. It is Wynn who created the Opus world that this product lives within and the Opus team that I am part of. ... Vince Perriello and Bob Hartman ... Like two robust peas on a New England pod, Vince and Bob, contributed, enormously, to the advancement of the overall netmail and Opus environments. The ConfMail, Ommm, and Renum programs created by Bob, the BinklyTerm electronic mail program by both of them, and Vince's Opus telecommunications contributions share very prominent roles on the Opus stage. ... and ... George Stanislav ... For Opus, Avatar and OEC advancements. Doug Boone ......... For keeping the ball rolling. Bob "Scribe" Davis.. For his tremendous support and cool head. Mike Elkins ........ For introducing me to the Opus gang. Chuck Forsberg ..... For creating Z-Modem. Rick Huebner ....... For fitting Z-Modem into Opus. Colin Sampaleanu ... For giving Z-Modem to the callers. Oman 1.13 The Opus System Manager Page 28 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º°°° U s a g e N o t e s °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ MEMORY USAGE Oman can use up to 300k of memory when heavily used with very active systems and DOS doesn't handle running out of memory very gracefully. Oman tries its best to catch memory run out conditions but, still, under extreme load in tight memory layouts, it is possible to crash it if you try hard enough. MULTITASKING When using utilities like Oman that significantly alter the Opus operating environment in a multi-tasking scenario, you are playing with fire. You have to use your head and have to take into consideration the vagaries and peculiarities of the multi-tasker that you are using. For instance, when running out of memory in an M/T environment (easy to do when splitting up memory between multiple tasks) not only will DOS be ungracious, so will most multitasking software. More importantly, though, when you are running Oman in one partition while one or more Opus programs are running in another, you MUST carefully contemplate the consequences. For instance, sorting or packing the user file while a user is online will, most likely, destroy your user files for obvious reasons. Modifying the outbound hold area while a mail operation is taking place can cause equal damage. Likewise, altering Area data while an Opus is running can cause destructive synchronization problems. Just keep in mind that a multi-tasker will allow all partitions to do anything they want with the disk without any arbitration between the partitions. Merging of File Lists Whenever a merge of file attach lists is triggered by such things as address or handling changes, there is no check on duplicate files that may result when the original list and the merged list both contain the same file name. The resulting file will then contain the exact sum of the original two file lists, one after the other. For the time being if you see that happen, you can correct the listed "xxxxxxxx.?LO" file with your text editor. =Kash=