home *** CD-ROM | disk | FTP | other *** search
- This file is the main telephone directory or %phones file. It
- includes telephone numbers, a couple of short scripts, function key
- macros, and a couple of support routines called by the PB.T, Q.T and
- other scripts.
-
- TELEPHONE NUMBERS
-
- The telephone numbers at the top are all systems in the Boston area
- (area code 617), except for Telegodzilla. These fine BBS systems are
- all waiting for you to call - try them out. The PCPursuit code for
- the Boston area is MABOS.
-
- Notice that most of the systems are listed twice. (example: bix and
- abix, chan and achan). The entry which starts with "a" is automatically
- linked with a script by the "dial" and "linkup" entries, the unadorned
- name is not. The :** after the second group of numbers displays them
- with a function key (find **\r %phones).
-
- THE DIAL MCOMMAND
-
- The "dial" entry is quite different from those in the %phones script
- Omen supplies with Zcomm. The section of the dial script beginning
- with the label "doit" is the dialing procedure itself. This is where
- you'll edit in special initialization strings, etc. you need for your
- particular setup. (The statliner string parameter introduced without
- fanfare a few versions back replaces the port and speed info on the
- real-time status line with a string of your choice, in this case -
- %remote).
-
- The top of the dial entry first checks to see if the directory entry
- name is preceded by the letter "a" (for "automatic" access). If not,
- we skip to "doit" and dial. A call command which does start with the
- letter a is subjected to further processing - the call command line is
- parsed for up to 9 possible modifiers. The modifiers are stored in
- string parameters %n1-%n9, and a count of modifiers is stored in %n0.
-
- For example: call ac,1,5,6,9,25,d
-
- will cause %n0-9 to be set as follows:
-
- n0 6 <- number of modifiers
- n1 1
- n2 5
- n3 6
- n4 9
- n5 25
- n6 d
- n7
- n8
- n9
-
- The PCBoard calling script (PB.T) supplied in the ZPBQNOW archive
- gives one example of how these modifiers can be used.
-
- Once the command line is parsed, the dial script calls the "linkup"
- subroutine to attach the proper script file to the system called using
- the mconnect facility. The name of the attached script is displayed,
- and the call is placed.
-
- The command-line parsing/linkup procedure adds a second or two of lag
- time between typing a call command and dialout when the NOW file is
- stored on a ramdisk on a particularly slow 4.77 mhz PC. On a faster
- computer, you may not notice it at all. Keeping the telephone numbers
- and dial entry at the top of the script speeds access.
-
- If the call fails, the nocon label cleans things up and returns the
- Zcomm command prompt.
-
- SUPPORT ROUTINES
-
- The setpass routine finds the %remote name in a file called PASS and
- grabs a line containing a password and whatever other info is there
- into the %z0 string parameter. The line is string split into tokens
- stored in %z0-%z9 (the %remote name is in %z0) and control is returned
- to the caller. The PB.T script gets door numbers for Prodoor and
- Quickmail (if needed) from the PASS file. A sample PASS file is
- included.
-
- The clsparms routine sets string parameters %n0-%n9, %s0-%s9, and
- %password to empty. It also sets %ifs (internal field separator for
- string splitting) to a smorgasboard of characters used by different
- scripts. All the scripts in the ZCPBQNOW archive use either a comma
- or a blank space as separators.
-
- The k1 routine sets function keys to a default status. It's handy
- to keep this as a separate routine so that scripts for a particular
- system can redefine fkeys for their own purposes and quickly reset
- them when the script is finished. The "bon" script (for calling BIX)
- and the Q.T script for the outcall queue both use this technique.
-
- The tedit routine speeds the script editing/tryout cycle. Called from
- a function key, it prompts for a filename and calls your editor to
- work on it. The filename is stored in the %menu string parameter.
- When editing is finished, the script can be tested by pressing just
- "m" at the Zcomm command prompt. A filename in the %menu parameter
- "sticks" until it's specifically overridden, so the second and further
- tryouts can be edited just by Shift-f7-Enter. The editor used in
- testing was the fine shareware product SLED.COM copyrighted 1987 by
- Sam Willmot of Ontario, Canada.
-
- The findname subroutine is almost unchanged from a routine posted in
- the Omen-tech conference on the Interlink BBS Network by a fellow
- named Barry Thorp. Pressing Shift f-10 will search the capture buffer
- for the last filename displayed and ask if it is the correct one. When
- the right filename is displayed, pressing Y will initiate an Xmodem or
- Xmodem-1K download. A default filename is created if none can be
- found. Thanks, Barry!
-
- The sparms subroutine provides a somewhat formatted display of the
- contents of string parameters %z0-%z9, %n0-%n9, and %s0-%s9. It looks
- nicer with "display overstrike" enabled.
-
- TINY SCRIPTS
-
- The "bon" subroutine (linked to system name "abix") calls the BIX
- time- sharing system (copyright McGraw-Hill). Tymnet-specific login
- stuff is not included because we're lucky enough to have a direct
- access node here in Boston. This script is here mostly to illustrate
- a trick I've used to cut my bix costs considerably -- don't struggle
- with those conference names, define them once and let Zcomm soft keys
- do the typing. If called from the outcall queue, this script just
- gets a listing of new messages and logs you off.
-
- The "omenscan" subroutine (linked to aomen) refreshes copies of the
- "answer" and "messages" files on the Telegodzilla system and gets a
- "dirt" listing of files so you can see if your favorite comm program
- has been updated recently. It uses the zmodem -Z parameter added in
- version 17.27 to speed download of the text files by about 10%.
-
-
- SETUP ENTRY
-
- The setup entry is pretty minimal and you'll want to edit in your
- favorite setup stuff to suit your environment. The colors chosen are
- for my green-screen composite monitor attached to a CGA equivalent --
- they give bright text on a light background for incoming data and user
- input and black text on the same background for program messages and
- script prompts. Be sure to set the %lib string parameter to the
- directory where you keep PB.T, Q.T and other scripts.
-
- The setup entry does two things specific to the enclosed Q.T script.
- First, it looks for an archive of *.q files specific to the day of the
- week (example: Sun.arc, Mon.arc, etc.) and uses the ARCE archive
- extract utility (available from System Enhancements Associates) to
- decompress it if present, allowing for a schedule of outgoing calls.
- It then calls Q.T to start the *.q file creation process. Q.T is not
- called if there are Zcomm commands on the DOS command line (example:
- C:> zcomm call dog). Striking the carriage return twice after the
- program name at the Dos prompt quickly bypasses Q.T.
-