Magnum BBS 6.00C Announcement

June - 1992

* * * * * A N N O U N C E M E N T  * * * * *

Gilmore Systems is proud to annouce version 6.00C of our OS/2 BBS package:

Magnum BBS (r) for OS/2 - the first of it's kind. -

Available in seven configurations:

2-node: - 1 dialup + console 3-node: - 2 dialup + console 4-node: - 3 dialup + console 5-node: - 4 dialup + console 9-node: - 8 dialup + console 13-node: - 12 dialup + console 17-node: - 16 dialup + console

A DEMO version (2-node: - 1 dialup + console) is also available, restricted to 128 users, 128 files, 128 messages, Magnum-to-Magnum remote mail is deactivated.

NOTE: IBM PS/2's can address COM1, COM2 and COM3 with OS/2 1.2 or 1.3 or COM1, COM2, COM3 and COM4 with OS/2 2.0 Non PS/2's can address COM1 and COM2 only.

To go beyond the limitations of the OS/2 COM device driver's            capability for your machines, you'll need:

- IBM Artic communications add-on card and Quadron Service Corp's OS/2 communications driver (QCOM).

- Alternately, you can use a Digiboard communications add-on card + driver software.

Both of the above cards are available for MicroChannel or AT.

Requirements:

IBM PS/2 computer with a minimum of: Intel 80286 (for OS/2 1.2 or 1.3) Intel 80386 or 80486 CPU (for OS/2 1.2, 1.3 or 2.0) IBM OS/2 version 1.2 or 1.3 (SE or EE) or OS/2 version 2.0. 4.5 Mb RAM for 1 node (allowing other uses for your computer) 500 Kb RAM for each additional node. NOTE: The preferred system should have at least 6 Mb RAM.

-or-

Any 80286, 80386 or 80486 based computer capable of running OS/2 ver 1.2, 1.3 or 2.0.

At least 5 Mb RAM is recommended to run 2 nodes. Up to 500 Kb RAM is needed for each additional node. The number of nodes is currently limited  by the number of communications ports supported by the OS/2  communications device driver supplied with OS/2. These memory requirements will vary depending on what the BBS will  be used  for. If running many Child  (door) processes and/or RJE programs, the memory requirements will increase.

Special communications drivers and communications add-on card(s) are needed to address communications ports beyond the support of the COM device driver supplied with OS/2 (Artic,  QCOM, Digiboard). There may be  other device drivers available  which  will  support  additional comports on your system without the need for specialized add-on  cards, however, we  do not provide these drivers or the support for them.

Modem requirements are: CTS/RTS signals must be supported by your modem and modem cable. Your modem must  report Carrier-Detect  signal in a realtime fashion (not forced on), and be able to respond to the DTR signal. MAGNUM BBS can communicate with your modem at speeds  of up to 19.2  KiloBaud with the OS/2 COM driver, or 38.4 KiloBaud with  the QCOM or Digiboard  drivers. Your modem should have the ability  to either ignore  or pass the  Xon/Xoff signals through to the computer.

Background: --

MAGNUM BBS for OS/2 was designed and developed by Gilmore Systems. It was in the works since 1988. MAGNUM BBS was running in beta  test mode since July of 1989, and has been released for commercial resale in January 1990.

You can  log  on  to  MAGNUM  BBS  at  the "Gilmore Systems BBS of Southern California" at (818) 706-9805. Just by logging on, you are actually demoing MAGNUM BBS. If this number is busy, your call will automatically be routed to the next available node. All nodes are running v.32 modems (9600 baud). Any 9600 baud modem following V.32 standards can connect at 9600 baud. All other modems can connect at any lower speed as expected.

MAGNUM BBS was designed  with specific  purposes in  mind, the most notable being able to run the BBS without dedicating the machine for that  purpose. Now you can have  more than  one user  online, plus  a virtual comport (the console) logon while your  machine is working on  other things such as  Word Processing, Accouting, Payroll, Compiling, Games or whatever. You can even be running DOS program(s) or Windows program(s) (OS/2 2.0 required)!

To take things a step further, Magnum BBS  offers an RJE section  (RJE is a term used on IBM mainframe systems, meaning "Remote Job Entry"). With RJE, users can start jobs (ie:   a job is  a "task" or  "program") which run  as background tasks. The user needn't  stay online  to wait  for the  job to finish. Once a remote user starts a job, the  user is free to use  the BBS for other things (ie: file xfer, e-mail, doors, etc) or log off.

Overview/Features: -

MAGNUM BBS has many features which are built in! Features that just cannot exist on DOS-based BBS systems. For Starters:

I) SECURITY

i)   Up to 9,999 different user security levels      ii)   Allow/Disallow Private Messages iii) Different Configuration File for Each node can configure            the BBS as a multiple-line single BBS, or actually a different            BBS for each node.      iv)   Users are not "locked" to their security level - the SYSOP can tailor *any* user's priveleges at *any* security level without necessarily changing their user level. v)   Up to 26 Message Conferences offering Read/Write/List            capabilities on an individual basis or according to security            level. For example, a subscription BBS might let users Read            messages in a certain message area but disallow them from            responding - message areas (conferences) are all separate.         -> NOTE: Optional 'Extended MessageBase' module available to                  expand to 256 MesageBases of 26 areas each for a total                  of up to 6,656 message conference areas.      vi)   Up to 26 File Xfer areas offering Upload/Download/List capabilities on an individual basis or according to security level. For example, a subscription BBS might let users list certain or all file sections in an effort to entice the user to "join", while only allowing downloads from certain areas. -> NOTE: Optional 'Extended FileBase' module available to expand to 256 FileBases of 26 areas each for a total of up to                 6,656 file areas. vii) Automatic security checks on File Uploads and Message Entry            scans for any harmful ANSI escape sequences capable of            redefining keyboard keys for destructive purposes. Any user            who enters a message or uploads a file containing keyboard key            redefinition in the form of ANSI escape sequences will be            locked out of the system (and the file or message deleted).      viii) User's time allotments are highly configurable. There are 4 period types: Daily, weekly, monthly, annually. Any individual user can have a daily, weekly, monthly, or annual time allowance. If the time is used up before the period (day, week,           month or year) ends, the user cannot gain access to the system again until the next period begins. There is also a pro-rate option which prorates users who log on in the middle of a           period: For example, a weekly user who is granted 7 hours/week of connect time can use the time all up in one day or a couple of days. As an option, if a weekly period is from Sunday to           Saturday, then a user logging on for the first time within the period on Wednesday will be pro-rated to 4 hours since they did not use Sunday, Monday, or Tuesday's time. ix)  Maximum time limit per call disallows weekly, monthly or annual            users to use up their entire time allotment in one call - they            can, however call back immediately.      x)    Upload/Download Ratios are optionally enforced and optionally configured on a security-level or individual user basis. In           addition, Download Kbytes/period can be enforced. xi)  Any file area(s) can be designated as "free", meaning files            downloaded from those areas will not apply to the user's            upload/download count.      xii)  Message section offers optional "Carbon Copy", "Receipt", and message "Forwarding" capabilities. xiii) Messages can contain imbedded commands to interact with those           reading the messages (sysop option).      xiv)  Communications ports can be configured to be opened as Exclusive or Shared. Support for redirected serial ports (on a LAN) are also supported. xv) Any node(s) can be "announce-only", "mail only" or regular BBS.      xvi)  With our optional "pipe module(s)", any dialup node(s) can be            configured as "port" (modem) or "pipe". "Pipe" nodes will allow OS/2 or DOS 5 workstations to log onto the BBS (no modems). xvii) User passwords are stored in encrypted form for security.

II) FEATURES

A) MESSAGE SECTION        i)   Both a line-editor and an ANSI editor are built into the system. Both offer automatic wordwrap. The ANSI editor allows for re-reading of a message being replied to during message entry. The ANSI editor has editing capabilities similar to that of most text editors. Both editors allow message entry of up to 150 text lines. Message Quoting is supported in the ANSI editor when replying to a message. Portions of your message can be stored to any of your 100 personal NotePads. ii) Any message can have an "Expiration Date" - no more tying              up of disk space with old, cluttered messages announcing              things such as meetings which already took place!         iii) "Carbon Copy", "Receipt" and "Forwarding" capabilities. iv) Thread capabilities allows following a thread forward or              backwards, finding the origin (beginning) of a thread, and              non-stop scrolling of threads or other messages.         v)   Private Messages and Deletion of messages are configurable by the Sysop to allow/disallow private messages, and to             allow/disallow users ability to kill messages. All messages entered via "Comment to Sysop" menu selection are always private regardless of private message settings. vi) Can search for messages in any conference by date, subject,              or user.         vii) User's can edit (modify) their message(s) at a later date even though they've already been saved. This capability is only available if the addressee of the message has NOT received the message yet. If the message is addressed to ALL, this capability only exists if the message has not yet been read by anyone. viii)Each message header shows subject nature, whether it was             received (if not to ALL) along with date and time of receipt,              date and time of message, how many times it was read,              expiration date (if any), whether there has been a reply, and              if it's part of a thread.         ix)  MAGNUM OS/2 BBS can be configured by the Sysop to compensate users with "time" for entering public messages. Compensation can range anywhere from 0 to 255 seconds per word. x)  Messages can contain special, embedded MAGNUM "MILC" commands.              MILC is "MAGNUM Interpreted Language Commands". There are              hundreds of commands, such as commands for color which will              emit the proper ANSI escape sequence for color when a user              with their color settings set to ON is reading a message. If a              user who is reading a message has their color settings set to              OFF, no escape sequences are emitted - the command is simply              removed and ignored when sent to the reader. This eliminates              the "garbage" display for users reading messages containing              ANSI escape sequences entered by the sender of the message.              There are many other commands in MILC which can make a general              message appear "personalized" to the reader. MILC also has the              capability of asking the reader questions and logging their answers to a file. Among some of MILC's advanced features are the ability to perform arithmetic and logical expressions, string logic, IF logic, conditional/unconditional branching, etc. MILC's command set is configurable by the sysop as to             which of MILC's commands users (or a particular user) can have access to, or it can be disabled for any particular user. Among the most powerful of MILC commands is the ability to             start an external program or RJE program. xi) If new mail arrives for a logged-on user at anytime during              their online session, Magnum will notify them that "New mail              has arrived".        xii)  Optional Message Encryption where security is an issue for those running on a LAN (network). [Included]

B) MAGNUM-TO-MAGNUM REMOTE MAIL        i)   All features of the mail section (above) are also supported in Magnum-to-Magnum Remote Mail (ie: CC's, receipts, message             forwarding, expiration date, etc). ii) Direct (point-to-point) mail support for targeting ALL or              specific users on another system.         iii) InDirect (store-and-forward) mail support for targeting ALL or              specific users on another system; routed through other systems. iv) Echo (store-post-and-forward) mail support for targeting ALL or              specific users on another system; but allowing the systems in              which the message is routed through to 'post' the message.         v)   Broadcast capability to ALL. A message entered as 'broadcast' to ALL, sends the message to all systems on your mail network. vi) Broadcast capability to SYSOPs. A message entered as              'broadcast' to SYSOPs, sends the message to all Sysops on              all systems on your mail network.         vii) For busy systems, modem node(s) can be set as "mail only" nodes (automatically, and at any given time via the event             handler), or open to all callers (user accounts and mail              accounts). viii) Message 'Groups' are configurable by the Sysop (requires 'Extended Msgbase Module'). Groups define which message bases             users (or mail accounts) are allowed to access, regardless              of their security level.         ix)  Although Magnum-to-Magnum Remote Mail capabilities are built in, the optional 'Extended MessageBase Module' is highly recommended.

C) FILE SECTION        i)   Any file can have an "Expiration Date" - no more tying up              of disk space with old, cluttered files. Once the expiration date is reached, the file is no longer available. ii) Any file can have a description of up to 150 lines of text              in the form of a message which is permanently associated with              that file. A 1-line description is required, the message              description is optional.         iii) Configurable by the Sysop, users can modify fields of any file(s) they uploaded themselves. For example, they can delete or rename the file, change or assign an expiration date, move it to a different file area, change the 1-line description or add/change the message description (up to             150 lines of text). They can also password protect the file (make it private), or un-password protect it (make it             public). iv) Password protected (private) files are optionally              configurable by the Sysop. Also, whether or not private files              are "list-able" are also at the Sysop's descretion.         v)   ARC and ZIP compressed file formats are both supported. Not only can users view the contents of compressed files, but they can also read any ASCII (readable) members, and download any member(s) of the compressed file without having to             download the entire compressed file. -> NOTE: ANY external file compression program(s) can be                    supported by Magnum. The Sysop need only define the syntax of these programs to Magnum, and Magnum will maintain the same features with those external file compression programs as it does with ARC and ZIP. An example of external file compression programs might be LZH or ZOO formats. vi) XMODEM, XMODEM-CRC, XMODEM-1K are the standard single-file              protocols supported. YMODEM, YMODEM-G and ZMODEM are the              standard batch (multiple-file) download protocols supported.         vii) During the Files Listing, the following are displayed (2 text              lines per file):  Whether an additional message (up to 150              text lines) describing the file exists, the filename, the filesize, date & time of upload, number of times downloaded, expiration date (if any) and 1-line description. Additional, extended Information on the file including upload method, date of last access and message description are available through the file menu selection. -> File NUMBERS also exist. In response to ANY prompt requiring a file name, the user may optionally supply the file number. During listings (at the -More- prompt), users can choose to             Mark files for download, examine or inspect them, download members from them, etc, without losing their place in the file listing. viii)MAGNUM OS/2 BBS can be configured by the Sysop to compensate             users with "time" spent during uploads. Compensation can range              anywhere from 0 to 255 times the time spent uploading. Uploads              of ".ARC" or ".ZIP" files (or externally-defined file compression formats) are automatically integrity checked.        ix)  MAGNUM OS/2 BBS can be tailored to a group of users or to              individual users to list, download, and/or upload to/from any file area(s). x)  MAGNUM OS/2 BBS eliminates the need for creating a compressed              file or series of files containing the list of available files              on the board. MAGNUM OS/2 BBS users simply choose a file menu              option, choose which areas they want, and MAGNUM OS/2 BBS              creates an .ARC or .ZIP file containing the listing the users              want. It's available for immediate download, and expires the              following day. The file will be deleted immediately upon              successful completion of download.         xi)  Any file section(s) can be designated as "free". If the Sysop is using an upload/download ratio, files downloaded from "free" sections will not count toward their ratio. xii) File 'Groups' are configurable by the Sysop (requires 'Extended Filebase Module'). Groups define which File bases             users are allowed to access, regardless of security level.

D) BULLETIN SECTION, QUESTIONAIRRES, NEWSLETTER via INTERPRETED LANGUAGE        i)   Unique "file-display" routine incorporates an all-new interpreted language (MILC or MAGNUM Interpreted Language             Commands)which can optionally be imbedded within any ASCII text file. Literally hundreds of commands are available within any file. ANSI escape sequences are no longer needed for color - the interpreted language processes color or ignores it depending on             whether the remote user has their color settings on or off. ii) The interpreted language is capable of creating multi-layered              menus, and can "include" files within files for display. 100              numeric and 100 string variables provide String and Mathematics              logic. All basic math and logical operations are supported              including IF processing, conditional and unconditional              branching, labels, etc. Many options for "Included" files such              as privacy of variables (inherited or not) from parent file.         iii) The interpreted language is capable of I/O to/from comport, screen and disk. Powerful and colorful questionairres can be             created with just a regular text editor. Answers to             questionairres are logged to a disk file, complete with User Information including date and time of questionairre completion. iv) At logon, the user is notified if any Bulletins or Newsletters              have been changed since the time of last logon.         v)   Any Bulletin, Newsletter, or Questionairre can be layered to              make sophisticated menuing systems. vi) All display files including Help files can contain imbedded              commands.         vii) With the power of MILC, the BBS can even be made to appear differently to different users. You could even make a public announcement to all users except say, a handfull of users you wish to exclude from seeing it. viii)MILC commands even include the ability to start an external             program or RJE task (including the passing of parameters and the setting of priority of execution).        ix)  MILC commands are capable of non-BBS related file transfer. The Sysop can use this feature to attach a file to a message.

E) RJE SECTION        i)   Remote Job Entry (RJE) allows users to start jobs (programs) which run concurrently to their session which will continue to             run after the user has logged off. These jobs run until their completion. The next time the user logs on, the user can check the status of thier job and download any resultant files. If             the user is still online when the job finishes, Magnum will notify the user of job completion. Job status can be checked at any time by the user. ii) Magnum is supplied with an RJE program which "ZIPs" (or "ARCs") all messages on the system (with options) for later             download. Also supplied is POWER (Personal Offline Writer Editor Reader) which your remote users can download and use             which runs under OS/2 or DOS). Another RJE program is supplied which accepts an upload of the remote user's offline responses or new messages which it processes in the background and adds to the message database.

F) SYSOP SECTION        i)   Sysop section allows the Sysop to modify any field of any record in the user, message, and file databases. ii) Can view the activity log, print the user database, pack              the databases, and generate mailing labels by security level.         iii) Can gain control of the entire system via remotely (or              locally) executing CMD.EXE (equivalent in DOS is COMMAND.COM). iv) "Remote Snoop" and the ability to remotely perform any sysop              task as though sitting at the console.

G) CHILD SECTION        i)   Known as DOORS on DOS-based BBS's. Games and other programs which run under OS/2 using STDIN, STDOUT, and STDERR can all be run as a Child Process. An example is the original adventure game which has been converted to OS/2. ii) Door (child) programs do not have to worry about              communications ports, Carrier Detect, Baud Rates or any other              communications considerations. MAGNUM BBS constantly monitors              this while the door (child) program is in progress. The door              (child) process merely reads and writes to/from the console              (very simple for any programmer to write) while MAGNUM BBS              handles all redirection both to and from the console and              communications ports, as well as to/from files and the child.         iii) Magnum is supplied with a door (child) program which provides useful charts on system utilization on a per-node or combined basis. Offers 'year and month-at-a-glance', and a breakdown of any 'day' in the year for an hourly chart of that day.

H) SYSOP CONSOLE        i)   The Sysop can monitor any node in realtime status from the console, or can "snoop" on any of the nodes in a fullscreen or windowed session, seeing everything the remote user sees and types. ii) The Sysop can invoke a CHAT session with a user on any node,              or send a message to a user on any or all nodes.         iii) The Sysop can FORCE a user off, LOCK them out of the system, change their security level up or down, change a user's time remaining up or down, etc.        iv)  The Sysop can specify a Shutdown Time of any or all nodes in              HH:MM format. Within 30 minutes of shutdown, MAGNUM BBS will              send the remote user(s) messages in the format of "System              Going Down In xx Minutes". These messages will be sent to the              remote user(s) at 30, 20, 15, 10, 5, 4, 3, 2, and 1 minutes              from shutdown time.         v)   The Sysop can shut down a node immediately (even with a caller              on that node), or have MAGNUM BBS shut down a node after the current caller logs off. vi) The Sysop can control the printer, pager and beeps by              activating or deactivating them.         vii) The Sysop can log on to the "sysop node" from the console without using a modem or telephone lines. viii)Any CHAT between Sysop and Remote User (or group chat) is             logged to a file including Time and Date of chat. During Chat,              if the remote user has their color settings on, both Sysop and              remote user type in different colors to help distiguish who              typed what.

I) GROUP CHAT        i)   Group Chat is available on all nodes, whether it's the local Sysop (modemless) node, or an active comport node. Any user on a node with their color settings ON, will see all typed material from other nodes in different colors depending on             which node is doing the typing. ii) Any User on any node can "page" a user on any other node.         iii) Any User on any node can set their "privacy" switch ON in              order to refuse any "paging" requests from other nodes. iv) Although Group Chat is public to all nodes, a user on any              node can send private lines of text to a user on any other              node.         v)   Automatic word wrap is active during group chat, as it is              in the message entry and Sysop Chat sections.

J) MENUS and HELP SCREENS        i)   Menus are defined by the Sysop in the Configuration file for each node. Menus are then built dynamically by MAGNUM BBS, eliminating selections not available to lower security level users. ii) Menus can also be external files (for color and other fancy things). Since external files (created with your text editor)             can contain imbedded interpreted commands, the sysop can              prepare the menus such that certain menu selections are              visible only to certain security levels.         iii) Help Screens can also be spiffed up by taking advantage of              the imbedded interpreted commands. For Instance, the help file for the File Section might contain a Menu of choices which help narrow down exactly what part of the File Section they need help on. "Other" BBS's make users read through an             entire "Help" Screen - MAGNUM BBS can offer you a choice - right down to a Menu offering Help for each actual menu selection - not just whole menus.

K) MAINTENACNE AND "EVENTS"        i)   Although MAGNUM BBS virtually runs itself, deleting expired files, etc, scheduled "events" are handled by MAGNUM BBS's             ACE (Automatic Command Execution) event handler. This event handler can execute any MAGNUM BBS "internal command", or             execute any external command (such as any OS/2 program, or              OS/2 .CMD file). Up to 300 events can be queued for execution at days/times predetermined by the Sysop. External OS/2 programs or .CMD files can be run as a WAIT, NOWAIT or             DETACHed process. Magnum-to-Magnum Remote Mail is handled as an 'event' and can be set up to exchange mail with other systems at any given day and time with any frequency. ii) MAGNUM's EXECUTIVE maintenance utility (included) allows the              Sysop to perform ANY kind of maintenance s/he can dream of.              This utility is actually an interpreted C-like language              processor which makes maintenance a snap! For example, to              delete all users who've not called within the past 90 days,              the following statements would perform the task:

IF(LASTCALL < TODAY - 90) DELETED = TRUE

While the above would be performed for every user in the database, you might have need to perform statements on only a single user. For example, If you're running a subscription BBS, you might have some of the following statements to             increase a user's security level and set a subscription expiration date:

LEVEL = 50 MEMODATE1 = TODAY + 365

The above would change a user's security level to 50 and set an expiration date to 365 days from today. To check expiration dates and lower the level, the following might be used:

IF(MEMODATE1 < TODAY) LEVEL = 25

Of course, in actuality, you would want to specify the different file and message areas you would allow/disallow the user to access in the above examples.

How about deleting all files which have had less than 10 downloads in the past 100 days? Simply:

IF(DOWNLOADS >= 10) GOTO(SKIP) IF(TODAY > FILEDATE + 100) DELETED = TRUE SKIP:

The above examples are a minute fraction of the capabilities of the executive maintenance program. The last example demonstrates the use of GOTO and a label. IF statements, if             true, can process a group of statements enclosed in { and } braces (as with C). Also available is nested IF, ELSE, WHILE and function declarations. You can access/manipulate any field in the USER, FILE, MESSAGE, RJE and UTILIZ databases. Because one of the fields of the USER database is "User Interests", you could create a list (or mailing labels or a form letter) to all users with an interest in music, for example. iii) The EXECUTIVE maintenance utility provides powerful             capabilities such as generating form letters and providing              statistics.

L) MAGNUM BBS IS "LAN-aware" and can accommodate ADDITIONAL INCOMING        DIAL-IN LINES VIA A NETWORK         i)   Magnum BBS will run on a LAN (local area network) by              purchasing additional copies of Magnum BBS for more DIAL-IN lines. ii) Each node can use unique databases or share the same              databases. In other words, each node can be a unique,              separate BBS if so desired.         iii) Magnum observes file sharing and record locking conventions to preserve integrity of the databases.

M) MAGNUM BBS IS "LAN-aware" and can operate as a "LAN BBS" with        our PIPE MODULEs.         i)   Optional OS/2 pipe module can be used to log on to Magnum BBS from any workstation via "named pipe". Similar to a             terminal program, workstations can "connect" to the BBS by              knowing the pipe name of the node they wish to access. ii) Optional DOS pipe module can be used to log on to Magnum              BBS from any workstation via "named pipe". Identical to              the OS/2 pipe module described in i) above, but for DOS 5 workstations. iii) Optional OS/2 and DOS 5 pipe modules will run on any LAN             software capable of supporting "named pipes" (ie: LanServer, LanManager, Banyan, Novell, etc).         iv) Optional pipe modules allow any DIAL-IN node(s) to be              configured as "port" (modem) or "pipe". v) A rotary (ie: hunt group) can be simulated with the pipe             modules.       -> vi) Pipe modules maintain system security in that they require no read/write access to anything on the server - they are treated the same way any "modem" caller is handled. vii) Proprietary error-correcting "pipe xfer protocol" is built             in and invoked when performing file uploads or downloads.

N) Optional CALLBACK feature available separately.          i) Any DIAL-IN node can be used as a CALLBACK node, although a dedicated CALLBACK node is recommended. ii) CALLBACK can be mandatory and/or courtesy (or none).        iii) In the event one or more CALLBACK nodes are "busy" (in use), Magnum will queue up to 100 callers for CALLBACK.

O) NOTEPAD facility (built-in)          i) A NotePad facility is built into the BBS which allows online users the capability of creating up to 100 personal notes. ii) Any of the user's 100 NotePads can contain a pre-defined             list of User ID's for CC's (Carbon Copies) in which they              can simply supply the NotePad number in response to a CC              prompt when entering a message. CC's of the message will              be generated to every user id found in that NotePad.              CC's lists can contain both local and/or remote user addresses              for Magnum-to-Magnum remote mail.         iii) NotePads can be used as a 'cut & paste' tool between messages.

P) SUPPORT & SERVICES          i) Technical support is free to all who are running the current 'ship-level' version. ii) Six months of "Sysop Download Plan" included with purchase.             Entitles Sysops to download new (commercial) and beta releases              of Magnum. Subscription service to our LARGE OS/2 file              sections is included.



This has been a condensed listing of features for the Gilmore System's MAGNUM BBS software for OS/2.

If you're using a 9600 baud modem (v.32), you can download a DEMO version of Magnum BBS from our Bulletin Board. If you're using a modem less than 9600 baud, you won't have enough time to download the DEMO unless you're a subscriber to our BBS. Alternately, you may order a copy of the DEMO version online with Visa, MasterCard or AmEx for $12. Call the BBS for details.

---

Our BBS, "Gilmore Systems BBS of Southern California", besides dealing with "Magnum BBS" software, offers the following file and message sections:

Our OS/2 File collection is large and growing faster and faster every month (available via subscription service only). Call up and join in on the latest in software technology for BBS systems. Pricing and ordering information is available via our system [N]ewsletter.

BBS: (818) 706-9805. Voice: (818) 706-9800. FAX: (818) 706-2785

For further information, call, FAX, or write to us at:

Gilmore Systems 1285 Falling Star Ave.                           Thousand Oaks, CA 91362 USA

Thank you for taking the time to read through this document.

The following page is an order form for your convenience. The pricing scheme is competitive and agressive. Prices are current as of June, 1992 and are guaranteed through December 31, 1992.

Gilmore Systems "Magnum BBS (r) for OS/2" order form Complete the form, and mail it with your remittance to:

Gilmore Systems 1285 Falling Star Ave. Thousand Oaks, California, 91362 - U.S.A.                                   - OR - Fax the form with credit card information to: (818) 706-2785 - OR - Place your order with us by phone at: (818) 706-9800 - OR - Place your order via credit card ONLINE on our BBS at: (818) 706-9805 -  The heading 'S' below is "shipping/handling" category: ^    ^  a = $ 5.00 U.S. Destinations, $ 12.00 non-U.S.   Charge is PER UNIT ^ b = $ 3.00 U.S. Destinations, $  6.00 non-U.S.   Charge is once/order ^    ^   SPECIAL: Items in category 'a' come with printed, bound user manual. ^           If you don't want the manual (print your own) take 10% off ^           of those items and change the category to 'b' instead! ^           Simply fill in a 10% less price in the 'Total' column for ^           that item and place a check mark here: _______ ^ Qty S      Description                                       Price      Total --- -     --- ___  a   2-node  (1 dialup + console node) Magnum BBS....... $ 99.00  _______ ___  a   3-node  (2 dialup + console node) Magnum BBS....... $ 175.00 _______ ___  a   4-node  (3 dialup + console node) Magnum BBS....... $ 250.00 _______ ___  a   5-node  (4 dialup + console node) Magnum BBS....... $ 300.00 _______ ___  a   9-node  (8 dialup + console node) Magnum BBS....... $ 400.00 _______ ___  a  13-node (12 dialup + console node) Magnum BBS....... $ 500.00 _______ ___  a  17-node (16 dialup + console node) Magnum BBS....... $ 600.00 _______ ___  b  Extended MsgBase (expand to 6,656 conferences)...... $ 29.95  _______ ___  b  Extended FileBase (expand to 6,656 file areas)...... $ 29.95  _______ ___  b  CallBack Module (ultimate in security).............. $ 29.95  _______ ___  b  OS/2 Pipe Module (1 time license fee/serial#)....... $ 79.95  _______ ___  b  DOS 5 Pipe Module (1 time license fee/serial#)...... $ 79.95  _______ ___  -  1-yr Sysop Download Plan after 1st free 6-months.... $ 60.00  _______

SubTotal: $ _________ California Destinations, Add Sales Tax: $ _________ Shipping/Handling: $ _________

=
============================================= Total: $ _________ Ship To:                                                < < Be certain to fill < in the "Ship To" < Information!! <                                                        < PURCHASE ORDERS

=
============================================= REQUIRE PRE-APPROVAL

Telephone Number: ______________________________ For Credit Card Orders Only:

Check One:  ____ VISA    ____ MASTERCARD    ____ AMERICAN EXPRESS

Card Number: __________________________________ Expiration Date: ____________

Your (CardHolder) Name: ___________________________Today's Date: ____________

Signature of CardHolder: ____________________________________________________