home *** CD-ROM | disk | FTP | other *** search
-
-
-
-
-
-
- ▓▓▓▓▓┐ ▓▓▓▓▓┐ ▓▓▓▓┐ ▓▓┐ ▓▓┐ ▓▓▓▓┐ ▓▓▓▓▓▓┐
- ▓▓┌─▓▓┐ ▓▓┌─▓▓┐ ▓▓┌─▓▓┐ ▓▓▓┐▓▓│ ▓▓┌──┘ └▓▓┌─┘
- ▓▓│ ▓▓│ ▓▓│ ▓▓│ ▓▓│ ▓▓│ ▓▓┌▓▓▓│ ▓▓▓┐ ▓▓│
- ▓▓│ ▓▓│ ▓▓▓▓▓┌┘ ▓▓▓▓▓▓│ ▓▓│ ▓▓│ └▓▓┐ ▓▓│
- ▓▓▓▓▓┌┘ ▓▓┌─▓▓┐ ▓▓┌─▓▓│ ▓▓│ ▓▓│ ▓▓▓▓┌┘ ▓▓▓▓▓▓┐
- └───┘ └┘ └┘ └┘ └┘ └┘ └┘ └──┘ └────┘
-
-
- v1.2
-
- An ANSI screen viewing door
-
- (C) Copyright 1993
-
-
-
-
- ╓────────────────────────────────────────────────────────────────────────────╖
- ║ ░░░░░░░ DR ANSI v1.2 ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
- ╙────────────────────────────────────────────────────────────────────────────╜
-
- Documentation and programming by Dan Roseen
-
-
- ╓────────────────────────────────────────────────────────────────────────────╖
- ║ ░░░░░░░ TABLE OF CONTENTS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
- ╙────────────────────────────────────────────────────────────────────────────╜
-
- INTRODUCTION
-
- 1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2
- 1.2 Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
- 1.3 Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
- 1.4 Options and Features . . . . . . . . . . . . . . . . . . . . . . 3
-
- DR ANSI SETUP & OPERATION
-
- 2.1 Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
- 2.2 Configuration File . . . . . . . . . . . . . . . . . . . . . . . 7
- 2.3 ANSI Category Screen . . . . . . . . . . . . . . . . . . . . . . 9
- 2.4 Help Screen . . . . . . . . . . . . . . . . . . . . . . . . . . 9
- 2.5 Viewing ANSI Screens . . . . . . . . . . . . . . . . . . . . . . 11
- 2.6 Baud Rate/ANSI Size Filter . . . . . . . . . . . . . . . . . . . 11
- 2.7 Download Option . . . . . . . . . . . . . . . . . . . . . . . . 12
- 2.8 Errorlevels . . . . . . . . . . . . . . . . . . . . . . . . . . 12
-
- CLOSING
-
- 3.1 Registration . . . . . . . . . . . . . . . . . . . . . . . . . . 13
- 3.2 Support and Distribution . . . . . . . . . . . . . . . . . . . . 14
- 3.3 Thank You To: . . . . . . . . . . . . . . . . . . . . . . . . . 15
- 3.4 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 15
-
- Page 1
-
-
-
-
-
-
-
-
-
-
-
- ╓────────────────────────────────────────────────────────────────────────────╖
- ║ 1.1 INTRODUCTION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
- ╙────────────────────────────────────────────────────────────────────────────╜
-
- DR ANSI was developed for several reasons:
-
- ■ I wanted to replace the ANSI door currently on my system since it
- was missing some features that are important for my BBS.
- ■ I discovered OpenDoors, a 'C' door writing library that is fantastic!
-
- DR ANSI was written using Borland's C++ v3.1 and OpenDoors v4.1. It
- requires an IBM PC, AT, or 100% compatible computer. This version has been
- tested with RemoteAccess v1.11 & v2.00Γ, Wildcat! 3.6M, under MS-DOS v5.0,
- and DESQview v2.42, and QEMM v6.02. DR ANSI was tested remotely with Telix
- and Qmodem communications software. DR ANSI requires a fossil driver, and
- has been tested with BNU v1.70 and X00 v1.24.
-
-
- ╓────────────────────────────────────────────────────────────────────────────╖
- ║ 1.2 DISCLAIMER ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
- ╙────────────────────────────────────────────────────────────────────────────╜
-
- DR ANSI is provided AS IS. I give no warranty of any kind, nor am I
- responsible for the results of use or misuse of the program.
-
-
-
- ╓────────────────────────────────────────────────────────────────────────────╖
- ║ 1.3 FILES ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
- ╙────────────────────────────────────────────────────────────────────────────╜
-
- DRANSI.CFG . . . . . . . . . Sample of a DR ANSI configuration file
- DRANSI.DOC . . . . . . . . . This documentation text file
- DRANSI.EXE . . . . . . . . . DR ANSI program
- DRANSI.HIS . . . . . . . . . DR ANSI history of changes
- DRANSI.HLP . . . . . . . . . DR ANSI help file
- DRANSI.REG . . . . . . . . . DR ANSI registration form
-
-
-
-
-
-
-
-
-
-
-
-
-
- Page 2
-
-
-
-
-
-
-
-
- ╓────────────────────────────────────────────────────────────────────────────╖
- ║ 1.4 OPTIONS AND FEATURES ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
- ╙────────────────────────────────────────────────────────────────────────────╜
-
- ■ Fully functional shareware.
-
- ■ Vertically sorted ANSIs.
-
- The list of ANSI screens will automatically format itself to give
- a pleasing appearance with different amounts of ANSI screens. For
- example: 100 ANSI screens will be 5 columns of 20 length, while
- a much lower number of ANSI screens may be 4 (or even 3) columns
- of lesser length.
-
- ■ 4,000 ANSI screen maximum (40 categories X 100 screens/category).
- Each selection screen can contain up to 100 ANSI screens. The
- documentation describes how you can make use of more than 100 ANSI
- screens per selection screen, but user selection is still limited
- to 100 per screen.
-
- ■ Simultaneous multi-node use does not require a batch file.
-
- ■ 'Slide-show' of ANSI screens because of multiple selection
- capability. The user has the ability to select and add individual
- screens as well as ranges of screens to a slide-show.
-
- ■ "Baud rate/ANSI size" filter. The sysop can set the maximum ANSI
- file size for specified baud rates. This is an optional feature
- that will permit the sysop to have DR ANSI not even list big ANSIs
- (such as long-playing animations) for callers at low speeds. This
- will help prevent users from feeling like they have to drop-
- carrier in order to get out of viewing an ANSI that takes a long,
- long time for their baud rate. It will also prevent users from
- greatly exceeding their time left on the BBS.
-
- ■ Built-in ANSI emulator lets you use DR ANSI locally without even
- using DOS's ANSI.SYS or DESQview's DVANSI.COM.
-
- ■ "Already seen" filter. The user's previously selected keys will
- almost dissappear from the selections available. However, the
- user will be able to view the same ANSI again if they desire.
-
-
-
-
- Page 3
-
-
-
-
-
-
- ╓────────────────────────────────────────────────────────────────────────────╖
- ║ 1.4 OPTIONS AND FEATURES (continued) ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
- ╙────────────────────────────────────────────────────────────────────────────╜
-
- ■ Download capability.
- ■ Optional configuration variables for DSZ/GSZ and download
- capability. If download capability is turned on, and the DSZ
- config. variable is not defined, then DR ANSI will search the
- BBS system's path to find DSZ/GSZ.
- ■ DSZ/GSZ support.
- ■ DSZ.COM, DSZ.EXE, or GSZ.EXE.
- ■ Xmodem, Ymodem, and Zmodem support.
- ■ DR ANSI uses return errorlevels to distinguish between
- successful and unsuccessful transfers.
- ■ "Already-downloaded" filter shows user what ANSIs have already
- been downloaded.
- ■ Complete file info given (file size, estimated transfer time,
- etc.)
-
- ■ Attention to details to keep it looking clean and easy to use (e.g.
- extra attention given to sysop break for chat and shell to DOS. User
- also has capability to 'S'top/Skip or 'P'ause ANSI viewing, help, or
- selection screen).
-
- ■ Error levels upon door exit for those who wish to monitor things like
- drop-carriers, keyboard inactivity timeout, etc.
-
- ■ DESQview-aware. It will use BIOS screen writes and share CPU time
- slices with other processes when in DESQview.
-
- ■ Sysop shell to DOS uses EMS memory if available.
-
- ■ Online help. Can be customized by sysop.
-
- ■ No maintenance (just dump more ANSI screens into the directory).
-
- ■ Supports up to 38.4K baud.
-
- ■ Automatic support for many BBS types. Supports user drop files
- as listed:
- DORINFO?.DEF CALLINFO.BBS
- * EXITINFO.BBS (Normal) DOOR.SYS (GAP/PC-Board)
- CHAIN.TXT DOOR.SYS (Doorway style)
- SFDOORS.DAT DOOR.SYS (WildCat standard)
-
- * Support for RA and QuickBBS's extended EXITINFO.BBS
- formats has been disabled so that this program can be
- used as intended with other drop files supported by RA
- and QuickBBS. This will prevent this program from
- possible damage of user records if the BBS authors
- change their extended EXITINFO.BBS files in the future.
-
- Page 4
-
-
-
-
-
-
-
-
-
-
-
- ╓────────────────────────────────────────────────────────────────────────────╖
- ║ 2.1 SETUP ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
- ╙────────────────────────────────────────────────────────────────────────────╜
-
- By default, DR ANSI will allow display of *.ANS files in it's directory, so
- you may want to make a directory just for DR ANSI.
-
- Also by default, DR ANSI will look in the current working directory for the
- BBS's user drop file. If DR ANSI is in a directory other than the user drop
- files, you can specify the directory pathname to the user info files as an
- argument to DRANSI.EXE as shown:
-
- pathname_to_dransi_directoryDRANSI
-
- or
-
- DRANSI door_drop_files_directory(user_info_files)
-
- Suggested setup for single or multi-node:
- ─────────────────────────────────────────
-
- DR ANSI will find related files in the directory of the pathname of
- DRANSI.EXE itself. For example: \RA\DOORS\DRANSI\DRANSI.EXE
- will run DRANSI.EXE using the ANSI files and optional files of the
- \RA\DOORS\DRANSI\ directory. This makes it very easy to run
- DR ANSI multi-node since it can be executed from the drop directory
- and will read the user drop files in that directory. Therefore
- no batch file is ever needed for single or multi-node. On my BBS
- I simply have the command \RA\DOORS\DRANSI\DRANSI.EXE execute from
- the BBS menu and it lets people use the door simultaneously from
- any existing line or line that I add in the future with no batch file.
-
- Example: C:\RA\DOORS\DRANSI\DRANSI.EXE
-
- (This is my setup. I run it directly from the user's menu.
- In my case, this is a RemoteAccess menu and the above example
- is inserted in the optional data field of a Type 7 menu item.)
-
-
-
-
-
-
-
-
-
-
-
- Page 5
-
-
-
-
-
-
-
-
-
-
- ╓────────────────────────────────────────────────────────────────────────────╖
- ║ 2.1 SETUP (continued) ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
- ╙────────────────────────────────────────────────────────────────────────────╜
-
- Alternative (considered normal) multi-node setup:
- ─────────────────────────────────────────────────
-
- Suppose you have a multiple line RemoteAccess BBS that has directories
- \RA\LINE1, \RA\LINE2, ... You also have a directory for DR ANSI called
- \RA\DOORS\DRANSI and a batch file in your \RA directory similiar to the
- file shown below:
-
- :: DRANSI.BAT - This batch file will use the DORINFO1.DEF file for each
- :: particular BBS line. It will move the user to the DR ANSI
- :: directory, run the program, then move him back to the
- :: Line directory that he came from before returning back to
- :: the BBS.
- ::
- :: DR ANSI's menu selection is a Type 7 with the following
- :: optional data: *C /C \RA\DRANSI.BAT *N
- ::
- :: The "*N" argument to the batch file is the node number of
- :: the BBS line and is used to locate the correct user info
- :: files on a multi-node system because the batch file's
- :: "%1" variable becomes the value of "*N".
-
- CD \RA\DOORS\DRANSI
- DRANSI \RA\LINE%1
- CD \RA\LINE%1
-
-
- Local (local without BBS user drop files):
- ──────────────────────────────────────────
-
- You can run DR ANSI locally with any of the following formats:
-
- DRANSI LOCAL
- DRANSI /LOCAL
- DRANSI -LOCAL
-
-
-
-
-
-
-
-
-
-
- Page 6
-
-
-
-
-
-
-
- ╓────────────────────────────────────────────────────────────────────────────╖
- ║ 2.2 CONFIGURATION FILE ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
- ╙────────────────────────────────────────────────────────────────────────────╜
-
- The remainder of this section is an actual configuration file (filled with
- comments) for the configuration file:
-
- ## DRANSI.CFG - Existence of this configuration file is optional. However,
- ## to find out the benefits of having this file, please read on.
- ##
- ## The format of this file is simple. Any line that doesn't start out with
- ## keywords are considered a comment. Keywords can appear in any order in
- ## this configuration file. They are as described:
- ##
- ## REG - Add your registration number when you get it.
- ## SYSOP - Add your sysop name after this keyword.
- ## EXT/CAT - Add the file extention for each category, followed by
- ## a '/' character, followed by a description of 30 characters
- ## or less (longer descriptions are truncated).
- ## BAUD/SIZE - Add a baud rate, followed by a '/' character, followed by
- ## the maximum size of ANSI that a caller at that baud rate
- ## or lower can view. The order of how the baud rate is listed
- ## in this configuration file is not important. Any baud rate
- ## can be specified. You can control 0 baud (local mode) by
- ## including it in this file, otherwise 0 baud has no limit.
- ## DSZ - DSZ/GSZ file_pathname (DR ANSI searches path by default if
- ## file_pathname is not specified and DOWNLOAD ON is specified).
- ## DOWNLOAD - Download option for users? Specify DOWNLOAD ON or OFF
- ## (default is OFF).
- ## PROMPT - Visually prompt user to press Enter after viewing an ANSI?
- ## Specify PROMPT ON or OFF (default is ON).
-
- ## In order to show DR ANSI as registered software, this configuration file
- ## must exist in the same directory as DRANSI.EXE and the sysop name and
- ## correct registration number must be filled in.
-
- REG 00000
- SYSOP Dan Roseen
-
- ## The following "EXT/CAT" keyword example (commented so it won't be used
- ## by default when first setting up this door) will enable an ANSI category
- ## selection menu when DR ANSI is run. Up to 40 categories can be created.
- ## DR ANSI will select the first 100 files with the filename extension
- ## specified for a particular category. This example will cause DR ANSI to
- ## use the first 100 *.ANS files for the "General ANSI" category. The
- ## Categories will be displayed in the order that they are read from this
- ## configuration file. *.ANS files are used if no categories are defined.
-
- #EXT/CAT ANS/General ANSI
-
-
-
- Page 7
-
-
-
-
-
-
-
-
- ╓────────────────────────────────────────────────────────────────────────────╖
- ║ 2.2 CONFIGURATION FILE (continued) ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
- ╙────────────────────────────────────────────────────────────────────────────╜
-
- ## The purpose of "BAUD/SIZE" configurations is to prevent low speed callers
- ## from selecting very large ANSI screens in DR ANSI. ANSIs larger than
- ## permitted won't appear in a listing. "BAUD/SIZE" settings are optional.
- ##
- ## With the settings shown below, viewing of ANSIs will be as follows:
- ##
- ## CALLER (baud) ANSI SIZE (bytes)
- ## ───────────── ─────────────────────────────────────────
- ## 0 No Limit (no limit for 0 baud unless specified)
- ## 300 1500
- ## 1200 6000
- ## 2400 50000 (uses next highest since commented)
- ## 9600 No Limit (nothing was specified over 4800)
- ##
- ## Note: You can set 0 baud's maximum file size to match another baud rate
- ## to see the ANSI selections available for the other baud rate.
-
- BAUD/SIZE 300/1500
- BAUD/SIZE 1200/6000
- #BAUD/SIZE 2400/35000
- BAUD/SIZE 4800/50000
-
- ## An "[Enter]" prompt can be displayed to the user after an ANSI screen has
- ## been viewed. This is turned on by default, but you can turn it off (the
- ## user is still prompted to press Enter or Space but is not asked visually).
- ## Use either "PROMPT OFF" or "PROMPT ON".
-
- #PROMPT OFF
-
- ## Do you want your users to be able to download your ANSI screens? You can
- ## use "DOWNLOAD OFF" or "DOWNLOAD ON" (default is off). You can also
- ## specify the file pathname of DSZ or GSZ (default is to search the path)
- ## with the DSZ configuration variable. For example: DSZ C:\DSZ\DSZ.COM
- ## Note: DR ANSI will only show download capability at baud rates greater
- ## than 0.
-
- DOWNLOAD OFF
- #DSZ C:\DSZ\DSZ.COM
-
-
-
-
-
-
-
-
-
- Page 8
-
-
-
-
-
-
-
-
-
- ╓────────────────────────────────────────────────────────────────────────────╖
- ║ 2.3 ANSI CATEGORY SCREEN ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
- ╙────────────────────────────────────────────────────────────────────────────╜
-
- DR ANSI will support up to 4,000 ANSI screens by using the ANSI Category
- feature. Up to 40 categories can be created. DR ANSI will select the first
- 100 files with the filename extension specified for a particular category.
- Use of ANSI Categories is optional. Please see the "Configuration File"
- section for information on using this feature.
-
-
- ╓────────────────────────────────────────────────────────────────────────────╖
- ║ 2.4 HELP SCREEN ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
- ╙────────────────────────────────────────────────────────────────────────────╜
-
- Help for DR ANSI is available as a selection in the category and ANSI
- selection screens. The help is in the form of a standard text file (not
- ANSI) to ensure that DR ANSI will have full control of line count, screen
- clear, screen redraw, and 'More?' prompting, in the event of a sysop chat,
- shell to DOS, etc.
-
- Use of an ANSI screen for this purpose was rejected due to the likelihood
- of many people saving their help file with ANSI drawing utilities in an ANSI
- format that doesn't represent each displayed line as a separate line in the
- help file.
-
-
- I don't expect there will be many who feel a real need to colorize their
- help file, but here's a way to do just that:
-
- Color code capability was added for those sysops who want to customize and
- spice up their help text file with color.
-
- The color code is just placed in the text file with the format:
- ~X (where 'X' is the number of the color attribute + 40,
- and the + 40 is added in to ensure that a single character can
- easily be used to avoid things like the tab character, etc.)
-
- The color attribute is computed from the IBM-style screen attribute.
- Hence, you can set the color of text to be displayed by a single
- character that is derived from the hexidecimal value.
-
- ┌───────────── Background color
- │
- 0x7f
- │
- └──────────── Foreground color
-
-
-
- Page 9
-
-
-
-
-
-
-
-
- ╓────────────────────────────────────────────────────────────────────────────╖
- ║ 2.4 HELP SCREEN (continued) ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
- ╙────────────────────────────────────────────────────────────────────────────╜
-
- Where the left digit of the hexidecimal number represents the background
- color, and the right digit represents the foreground color. Possible
- colors, along with their corresponding hexidecimal values, are listed
- in the charts, below.
-
- ╒═══════════════════════╕ ╒═══════════════╤══════════╕
- │ Foreground colors │ │ Background │ Flashing │
- ├─────┬─────────────────┤ ├─────┬─────────┼──────────┤
- │ 0 │ Black │ │ 0 │ Black │ Off │
- │ 1 │ Blue │ │ 1 │ Blue │ Off │
- │ 2 │ Green │ │ 2 │ Green │ Off │
- │ 3 │ Cyan │ │ 3 │ Cyan │ Off │
- │ 4 │ Red │ │ 4 │ Red │ Off │
- │ 5 │ Magenta │ │ 5 │ Magenta │ Off │
- │ 6 │ Brown │ │ 6 │ Brown │ Off │
- │ 7 │ White (grey) │ │ 7 │ White │ Off │
- │ 8 │ Bright Black │ ╘═════╧═════════╧══════════╛
- │ 9 │ Bright Blue │
- │ a │ Bright Green │
- │ b │ Bright Cyan │
- │ c │ Bright Red │
- │ d │ Bright Magenta │
- │ e │ Yellow │
- │ f │ White (bright) │
- ╘═════╧═════════════════╛
-
- Example color codes:
-
- Yellow on a black background would be:
- ~6 (since 0x0e = 14, and 14 + 40 is character '6' in the ASCII table)
-
- Black on a white (grey) background would be:
- ~ÿ (since 0x70 = 112, and 112 + 40 is character 'ÿ' in the ASCII table)
-
- If you are unsure of what character represents a decimal number in the
- ASCII table, just press and hold ALT, then enter the number in the numeric
- keypad, then release ALT. For example: ÿ is obtained from ALT-152
-
-
-
-
-
-
-
-
-
-
- Page 10
-
-
-
-
-
-
- ╓────────────────────────────────────────────────────────────────────────────╖
- ║ 2.5 VIEWING ANSI SCREENS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
- ╙────────────────────────────────────────────────────────────────────────────╜
-
- Select an ANSI screen by entering the number of the screen you want
- displayed. When the screen is done drawing, press Enter or Space to
- continue. When you return to the list of screens, you will notice that the
- selection numbers for screens you have viewed will have almost disappeared
- to remind you of which screens you have already viewed (this is what is
- referred to as the "already-seen filter").
-
- A 'slide-show' can be made by entering multiple screen numbers. Screens will
- be displayed in the same order as they are entered. Separate the screen
- numbers by a space, comma, or semi-colon. You can select a range of screens
- to view by using the minus '-' character. Here's an example slide-show
- selection: 1 5 10 20-30 40
-
- You can escape out of a slide-show by pressing the ESC key. When the
- current screen has finished you will be brought back to the screen selection
- menu without finishing the slide-show.
-
- While you are using DR ANSI, you can stop/skip or pause any selection or
- ANSI screen by pressing 'S'top/skip or 'P'ause. If you are using DR ANSI
- remotely, keep in mind that the BBS may be ahead of you and you will still
- see what has already been displayed on the BBS's screen. In other words,
- the slower your BBS connection, the more delayed the response will be to
- the 'S' and 'P' keys.
-
- If you are viewing ANSI music remotely, chances are that there is not any
- way to stop or skip the remainder of the music on that screen from playing
- because the buffer in the terminal package (e.g. Qmodem) has to play out.
- The only way I know of for getting out of a long ANSI music screen is for
- people who are multi-tasking (e.g. DESQview). They can usually close their
- current window, open up a new one and load up their terminal package again
- using the same baud rate connection and they should still be on the BBS and
- in DR ANSI, but out of the long ANSI music screen.
-
-
- ╓────────────────────────────────────────────────────────────────────────────╖
- ║ 2.6 BAUD RATE/ANSI SIZE FILTER ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
- ╙────────────────────────────────────────────────────────────────────────────╜
-
- The purpose of the Baud Rate/ANSI Size Filter is to prevent low speed
- callers from selecting very large ANSI screens in DR ANSI. ANSIs larger
- than permitted won't appear in the ANSI selection screen and are impossible
- to select. Use of this filter is optional. Please see the "Configuration
- File" section for more information on using this feature.
-
- Personally, my rule of thumb is to set the maximum screen size to 10 times
- the baud rate. I also don't set a maximum screen size for my highest baud
- rate.
-
-
- Page 11
-
-
-
-
-
-
-
-
-
-
- ╓────────────────────────────────────────────────────────────────────────────╖
- ║ 2.7 DOWNLOAD OPTION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
- ╙────────────────────────────────────────────────────────────────────────────╜
-
- You can set up DR ANSI so users on your system can download your ANSI
- screens. DR ANSI has built-in support for an external DSZ or GSZ, and their
- Xmodem, Ymodem, and Zmodem protocols. You can specify the file pathname of
- DSZ or GSZ, or have DR ANSI search your computer's PATH environment variable
- for DSZ or GSZ.
-
- When an ANSI screen is downloaded successfully, DR ANSI will show that ANSI
- as having been downloaded by changing the color of the '-' character in the
- ANSI screen selection menu from bright red to dark grey (this is what is
- referred to as the "already-downloaded filter"). This should become
- apparent to the downloader in a very short time, and they will be aware of
- it from then on. This is to show the user (and sysop) what the user has
- already downloaded during that session with DR ANSI.
-
- Note: DR ANSI will only show download capability at baud rates greater
- than 0.
-
- GSZ tip: Set a GSZWINDOW environment variable so GSZ doesn't take up your
- whole screen when a user is downloading. If you set your
- enviroment variable to GSZWINDOW=23 you will still be able
- to see DR ANSI's status bar on the bottom of your screen when
- a person is downloading an ANSI. The status bar will be updated
- again after the download has finished.
-
- Please see the "Configuration File" section for more information on using
- this feature.
-
-
- ╓────────────────────────────────────────────────────────────────────────────╖
- ║ 2.8 ERRORLEVELS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
- ╙────────────────────────────────────────────────────────────────────────────╜
-
- DR ANSI's errorlevels are as follows:
-
- 0 - A critical error has occurred
- 1 - Carrier lost, user off-line
- 2 - Sysop terminated call, user off-line
- 3 - User time used up, user STILL ON-LINE
- 4 - Keyboard inactivity timeout, user off-line
- 10 - User requested exit
-
-
-
-
-
- Page 12
-
-
-
-
-
-
-
-
-
-
- ╓────────────────────────────────────────────────────────────────────────────╖
- ║ 3.1 REGISTRATION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
- ╙────────────────────────────────────────────────────────────────────────────╜
-
- Please support shareware!
-
- You are granted permission to evaluate DR ANSI for a period of 30 days.
- After this evaluation period a $10.00 (US funds) registration fee is
- required. If you do not plan to register, then remove DR ANSI and it's
- associated files from use.
-
- Upon receipt of your registration fee, a registration number will be sent to
- you. Put this registration number in DRANSI.CFG (as shown in the
- "Configuration File" section) to register your copy of DR ANSI.
-
- DR ANSI, as an unregistered copy, is not crippled in any way. Registered
- owners will receive their registration number that will do the following:
-
- ■ Replace "UNREGISTERED" in the title screen to your name.
-
-
- Your registration is valid for all future versions of DR ANSI.
-
- Please use the file DRANSI.REG to send in your registration information.
- Send your DRANSI.REG information, plus a $10 check or money order (US funds)
- to:
- Dan Roseen
- P.O. Box 5695
- Kent, WA 98064-5695
-
- Please make the check or money order payable to Dan Roseen.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Page 13
-
-
-
-
-
-
-
-
- ╓────────────────────────────────────────────────────────────────────────────╖
- ║ 3.2 SUPPORT AND DISTRIBUTION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
- ╙────────────────────────────────────────────────────────────────────────────╜
-
- Updates and/or new releases of DR ANSI can be downloaded or file-requested
- from my BBS, The Night Owl (shown below). If you are logging in, you will
- have to fill out a newuser questionnaire. Once you have done this you will
- have enough access to download DR ANSI without complete user verification.
- You may leave your comments, questions, and suggestions to Dan Roseen
- (or Sysop) if I'm not available for chat.
-
- If you are experiencing problems, call The Night Owl BBS or write me and
- include the following information:
-
- ■ Explanation of the problem. ■ DRANSI.CFG file.
- ■ BBS type and version number. ■ AUTOEXEC.BAT and CONFIG.SYS files.
-
-
- You may contact the following systems:
-
- Support and Distribution
- ────────────────────────
- Sysop: Dan Roseen
- BBS: The Night Owl (a RemoteAccess BBS)
- Fidonet: 1:343/102
-
- Login: (206)631-4949 24 Hrs. Kent, WA - USA
- Max baud: 2400 (expected to be HST/14.4K on June 1, 1993)
-
- Mail/FREQ: 1:343/102 (this node is not for login)
- 2400 to HST/14.4K
-
- Comment: For downloading latest version: Download DRANSI*.ZIP
- For file-requesting: Request the magic name "DRANSI"
- or request DRANSI*.ZIP
-
- Distribution (also Beta-Site)
- ─────────────────────────────
- Sysop: Andy Nachbaur
- BBS: Wild Bee's BBS (a Wildcat! BBS)
-
- Login: (209)826-8107 24 Hrs. Los Banos, CA - USA
- Max baud: 14.4K
-
-
- Both of the support systems listed above will have a DR ANSI support file
- area containing the latest DR ANSI, fossil driver set up example(s), and
- even some whole sets of ANSI screens that you can use to quickly set up
- different ANSI categories on your own BBS.
-
-
- Page 14
-
-
-
-
-
-
-
- ╓────────────────────────────────────────────────────────────────────────────╖
- ║ 3.3 THANK YOU TO: ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
- ╙────────────────────────────────────────────────────────────────────────────╜
-
- Denise Roseen, my wife, for her encouragement and for helping me set aside
- time to work on these projects.
-
- David and DeAnne Roseen, my children, for going to bed by 10 PM so I could
- do some late-night programming.
-
- Andy Nachbaur, sysop of Wild Bee's BBS, for his willingness to beta test
- DR ANSI v1.2 and his comments and suggestions.
-
- Albin Gersich for finding a bug when the conditions were high transfer rates
- and slow CPUs. He also did the testing on v1.2's fix for this bug.
-
- Jerry Harris, sysop of After 10:00 BBS, for testing DR ANSI v1.1, and all
- the help he has given to other Wildcat! sysops who weren't familiar with
- setting up a fossil driver (needed to run DR ANSI).
-
-
- ╓────────────────────────────────────────────────────────────────────────────╖
- ║ 3.4 ACKNOWLEDGEMENTS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
- ╙────────────────────────────────────────────────────────────────────────────╜
-
- Borland C++ . . . . . . . Borland International Inc.
- DESQview . . . . . . . . . Quarterdeck Office Systems
- DSZ . . . . . . . . . . . Omen Technology Inc.
- GSZ . . . . . . . . . . . Omen Technology Inc.
- OpenDoors . . . . . . . . Brian Pirie
- Qmodem . . . . . . . . . . Mustang Software Inc.
- RemoteAccess . . . . . . . Continental Software
- QEMM . . . . . . . . . . . Quarterdeck Office Systems
- Telix . . . . . . . . . . Exis Inc.
- Wildcat! . . . . . . . . . Mustang Software Inc.
-
-
-
-
-
-
- Page 15
-