**************************************************************************
*OnLineOnLineOnLineOnLineOnLineOnlineOnLineOnLineOnLineOnLineOnLineOnLine*
*Online                                                            OnLine*
*OnLine                  TeleTalk OnLine Magazine                  OnLine*
*OnLine                  """"""""""""""""""""""""                  OnLine*
*OnLine                The BBSer and SysOp Resource!               OnLine*
*OnLine                                                            OnLine*
*OnLine  (C)opyright 1988                           Public Domain  OnLine*
*OnLine                        Vol.3, Issue 28                     OnLine*
*OnLine                                                            OnLine*
*OnLineOnLineOnLineOnLineOnLineOnlineOnLineOnLineOnLineOnLineOnLineOnLine*
**************************************************************************
*                    "An AUTHORIZED T/TalkNET BOARD!"                    *
*                     ''''''''''''''''''''''''''''''                     *
*  WILDCAT! Orphanage 3/12/24    Colorado Springs, CO      (719)392-6631 *
*  Autoline!          3/12/24    Covino, CA          [CAGLE]818/339-2085 *
*  Eight Bit Tar Pits 300/1200   Atlanta, GA         [GAATL]404/388-7482 *
*  The Graphics Dump  3/12/24    Newark, NJ          [NJNEW]201/469-0049 *
*  The Vault          300/1200   Denver, CO          [CODEN]303/796-0539 *
*  Lost Paradise      3/12/24    Washington DC       [DCWAS]   /370-7795 *
*  Modern Pastimes    300/1200   Milwaukee, WI       [WIMIL]414/384-1701 *
*  Nick At Nite       3/12/24    Salt Lake City, UT  [UTSLC]801/964-1889 *
*  North Shore        300/1200   Boston, MA          [MABOS]617/595-0211 *
*  SJAS III           3/12/24    San Jose, CA        [CASJO]408/448-7527 *
*  The Maverick       3/12/24/96 Los Angeles, CA     [CALAN]213/609-2176 *
*  ProTech            3/12/24    Everett, WA         [WASEA]206/745-4694 *
*  Bull City BBS      3/12/24    Durham, NC          [NCRTP]919/383-8707 *
*  W.C.S. BBS         3/12/24    Oakland, CA         [CAOAK]415/825-2952 *
*  Sorman's Info Exchange        Sweden                1-11-46-470-22183 *
*  Crow's Nest BBS               England              010-044-793-813633 *
*  TVS BBS                       Peru                    011-5114-479305 *
*                                                                        *
*       Publisher / Editor ......................... John Peters         *
*        Associate Editor ......................... Bob Connors          *
**************************************************************************
IN THIS ISSUE                                               DECEMBER 1988
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
  TELEBITS ................ [BIT]      SYSOPS FABLES ............. [SYS]
   T/TalkNET Newswire                   BBS Law & Copyrights

  ASK DOCTOR BOB .......... [ASK]      MESSAGE OF THE MONTH ...... [MSG]
   DOS In Rom - A Good Idea?            Cryptic Thoughts

  MISTER FIX-IT ........... [FIX]      WANDERING WANDERER ........ [WAN]
   Phone Line Noise?                    More ARC and Apples

  HOT PURSUIT! ............ [PCP]      UNDERSTANDING MS/PC-DOS ... [DOS]
   Talk'n The TeleNet Blues             The Plain Vanilla Guide, Pt. 2
    Bulletins and Updates                 (MUST Read For Beginners!)

  PROGRAMMING CHALLENGE ... [PGR]      LOG OFF ................... [OFF]
   WILDCAT! Doors Contest!              Using and Reprinting of
                                         TeleTalk OnLine

                                 [*][*][*]

[BIT]**************************
                     TELEBITS *
*******************************
An Open Letter To Our Readers
"""""""""""""""""""""""""""""

Dear TeleTalk OnLine Readers,

TeleTalk OnLine Magazine is currently undergoing a few format changes  many  of
which  are obvious,  others are subtle.  Some affect you,  our readers,  others
affect our T/TalkNET SysOps.

No, we're not disbanding T/TalkNET, just streamlining it,  making it faster and
more efficient for us and you.  In fact, we are making these changes so that we
can  add  several new cities to our circuit.  Some of the changes we are making
are:

    1)  Each issue is now just one file instead of two or three.  The  size  of
each  issue in the former format has averaged a low of 40K and a high of around
70K.  That will not change.  If a single file that large is is too big  to  fit
in your word processor buffer,  there are several utilities out for the various
computers that will divide the file into the size you need.

    2)  We will no longer require our SysOps  to  have  TeleTalk  OnLine  as  a
readable  text  file  and  a  file available for downloading.  Either method is
satisfactory.

    3)  We're asking the SysOps to,  (at  their  option)  remove  the  TeleTalk
message  bases  from  their BBS's.  They have been instructed to pass along any
files and/or messages that you want to send to us.  Just leave a message to the
SysOp stating so.

    4)  Issues are now available in 80 column format only.  98 percent  of  the
boards carrying TeleTalk OnLine are 80 columns.  Most 40 column boards are able
to wordwrap so formatting should not be a problem.  As always,  you are free to
re-arrange and/or re-format the issue to fit your needs.

    5)  We  will  continue to offer each issue with the special carriage return
characters.  The carriage return formats available are  ^M^J  for  the  MS-DOS,
IBM,  Atari ST,  CP/M, and Amiga boards, ^M for the Apple and TRS-80 boards and
the ACSII 155 character for the Atari 8-bit boards.

    6)  To  speed  up  the process of transferring files,  the file will now be
uploaded in ARC format.  Bulletins, updates etc., will also be included in this
package.  (Exceptions will be made for the Apple  and  Macintosh  boards  which
have inadequate or non-existing ARC utilities.)

                              [*][*][*]

The reasoning behind these changes is easily explained.  Frankly, we are trying
to make our work  easier.   Unlike  most  other  online  magazines,  we  upload
TeleTalk  OnLine  to  each and every T/TalkNET node.  The disadvantages to this
method are many.  PC Pursuit, (which is our primary means of staying in contact
with the T/TalkNET boards,) is at many times fickle when it comes to transfers.
Occasionally,  boards are offline or they have gone down without notifying  us.
At  times,  Telenet drops carrier for seemingly no reason.  If we were to add a
dozen or more new T/TalkNET boards to the list,  the whole process  of  getting
the issue from us to you becomes unmanageable.  The point is, all of this takes
up valuable time and adds another notch to our 'frustration level.'

But then uploading TeleTalk OnLine to the T/TalkNET boards every month has it's
advantages  too.   Our readers don't have to search several boards all over the
country hoping to stumble across the latest issue and since these boards can be
called via PC Pursuit,  the cost of receiving TeleTalk OnLine is  minimal.   If
you  call any of the T/TalkNET boards listed at the top of each issue,  you can
be assured that  you  are  receiving  TeleTalk  OnLine,  "Hot  of  the  press."
Likewise, do you need to upload an article for us to review?  Or maybe you have
a  question  for  Doctor Bob or a comment you would like to make?  We log on to
these boards at least once per month which makes it easy for us to make  direct
contact with our readers.

We  want  to keep the T/TalkNET circuit intact.  Other changes are in the works
and will be implemented in the near future.  By making these  changes,  we  are
able to concentrate more on putting together each issue,  (the enjoyable part!)
and will be spending much less time on distributing it, (the not-so-fun part).

                                           Sincerely,

                                           John Peters
                                           Bob Connors
[EOA]

[SYS]**************************
                 SYSOP FABLES *
*******************************
BBS LAW-COPYRIGHT INFRINGEMENT
"""""""""""""""""""""""""""""""
Brian Oliva
North Shore BBS
[MABOS] 617/595-0211 [T/TN]

The following message was left on "THE VAULT BBS" - The Authorized TeleTalk BBS
for the Denver area.  TSR, for those unfamiliar with them,  is the company that
developed  and  markets  the  roll  playing  game ADVANCED DUNGEONS AND DRAGONS
(AD&D).  Many bulletin boards have online AD&D games,  and this  is  apparently
what happened to one that got too good for TSR's comfort.

Msg #21678 * TeleTalk Online *
Date: 9-30-88   Time:  9:35'21 pm.
Subj: Tsr Closes Bbs
 To : All
From: Bruce Berna (Modern Pastimes/SysOp)

September 28,1988.  Milwaukee, Wisconsin.

The  City of Aldimar BBS was ordered by TSR's lawyers to close down and destroy
all software pertaining to the BBS.  Aldimar was based on AD&D rules and had  a
active  user  base.   This  may  have contributed to it's downfall as the Sysop
mimic the rules a almost completely,  though  what  may  have  been  it's  true
downfall was that they charged a small fee to join.

More  to  follow  as it occurs.  At this time the Sysop of the BBS doesn't have
the funds to fight TSR,  so 3 years of work will soon be  deleted  without  TSR
even looking at the product.

**Commentary**

Here's that old Knee jerk principle going again, if you don't understand it sue
it.  TSR may be losing a lot of money because this was a finely written BBS, it
used Datamedia 1500 emulation to produce a online map,  everything was per AD&D
rules.

                                [*][*][*]

BBSs mentioned in article:

Modern Pastimes  [WIMIL] 414/384-1701 [T/TN]
The Vault BBS    [CODEN] 303/796-0539 [T/TN]
North Shore BBS  [MABOS] 617/595-0211 [T/TN]
[EOA]

[ASK]**************************
               ASK DOCTOR BOB *
*******************************
Bob Connors
Wildcat! Orphanage BBS  (719)392-6631

From   : CHRIS HOPPING
To     : DOCTOR BOB
Subject: MS-DOS In ROM
Folder : Ask Doctor Bob

Dr. Bob,

I am looking at gobs of Ms-Dos clones trying to decide  what  to  buy.   I  was
wondering  if  you  knew  if  the Tandy computers with MS-DOS in ROM are a good
thing to get?  In a way it sounds good to have it and in another,  I'm leary of
it.

What  are  advantages  and the disadvantages?  Buying a clone is like trying to
choose what to have for supper.  Any help would be appreciated.

                                              Thanks,
                                              Chris
From   : DOCTOR BOB
To     : CHRIS HOPPING
Subject: (R) MS-DOS in ROM
Folder : Ask Doctor Bob

The only disadvantage I know of with the Tandy machines having DOS  in  ROM  is
the  version of DOS being used.  They use version 2.10 while the latest version
is 3.x (not counting the new DOS 4.x).   The  newer  version  gives  much  more
capability.

[Dr. Bob Notes: Since writing this reply, it has come to my attention that some
of the Tandy Computers now have MS-DOS 3.3 in ROM.]

The  advantages  are numerous!  First of all,  the DOS is designed specifically
for the Tandy machines,  ensuring compatibility.  DOS loads immediately.  There
is  no  chance of accidentally erasing the DOS.  Upgrading (when available)  is
only a matter of popping out the old  ROM  and  putting  in  the  new  ROM.   I
personally believe that ALL computers should have their DOS version imbedded in
ROM (and even some of the DOS utilities too).

For more information about the Tandy 1000 series and their DOS in ROM,  see the
article "ROM With a View"  by Stewart Alsop,  PC World magazine,  October  1988
issue (page 47).
[EOA]

[MSG]**************************
         MESSAGE OF THE MONTH *
*******************************
Cryptic Thoughts
""""""""""""""""
From   : GHARNET STOHNE
To     : SUZANNE PALANUK
Folder : B, "The Writer's Club"

G,  I  never  thought of it that way.  O,  maybe it X'ed my mind once or twice,
but....  We'll have to 86 this soon,  or we'll run out of goon #  puns to make.
We should exercise some CONTROL, find an ALTERNATE subject, SHIFT the emphasis,
before  we  ENTER  a  state  of  confusion.  We need to step BACK SPACE out our
thoughts a little more.  Find a good |  and get \'ed,  or is that smashed?  END
UP in a , .  Well, that last was < I'd expected....
[EOA]

[FIX]**************************
                MISTER FIX-IT *
*******************************
Modem Noise Killer
""""""""""""""""""
Captured on Nick-At-Nite
[UTSLC] 801/964-1889 [T/TN]

[Addition to original file by Mike McCauley
CIS 71505,1173 - 2/29/88]

First,  a  personal  recommendation.  _THIS WORKS!!!_  I have been plagued with
noise at 2400 for some time.  I went round and round with Ma Bell  on  it,  and
after they sent out several "repair persons"  who were,  to be kind, of limited
help in the matter, I threw in the towel.  I saw this file on a board up east a
few days ago,  and thought I'd bite.  Threw the  gismo  together  in  about  10
minutes,  took  another  five  to  adjust  the pot for best results on my worst
connection, and guess what?  No more worst connection!

                                 [*][*][*]
Modem Noise Killer
""""""""""""""""""
 (alpha version)

With this circuit diagram,  some basic tools including a  soldering  iron,  and
four  or  five  components  from  Radio  Shack,  you  should be able to cut the
noise/garbage that appears on your computer's screen.

I started this project out of frustration at using  a  US  Robotics  2400  baud
modem and getting a fare amount of junk when connecting at that speed.  Knowing
that capacitors make good noise filters, I threw this together.

This  is  very easy to build,  however conditions may be different due to modem
type, amount of line noise,  old or new switching equipment (Bell's equipment),
and  on  and on.  So it may not work as well for you in every case.  If it does
work,  or if you've managed to tweek it to your computer/modem setup I'  d like
to hear from you.

I'd  also  appreciate  any of you electronic wizards out there wanting to offer
any improvements.  Let's make this work for everyone!

Please read this entire message and see if you understand it before you begin.

OK, what you'll need from Radio Shack:

1 #279-374 Modular line cord if you don't already have one.  You won't need one
if your phone has a modular plug in its base.  $4.95

1 #279-420 Modular surface mount jack (4 or 6 conductor) $4.49

1 #271-1720 Potentiometer.  This is a 5k audio taper variable resistor.  $1.09

1 #272-1055 Capacitor.  Any non-polarized 1.0 to 1.5 uf cap should do.   Paper,
Mylar,  or metal film caps should be used,  although #272-996 may work as well.
(272-996 is a non-polarized electrolytic cap) $.79

1 100 ohm resistor - quarter or half watt.  $.19

1 #279-357 Y-type or duplex modular connector.  Don't  buy  this  until  you've
read the section on connecting the Noise Killer below.  (A, B,or C) $4.95

First off, open the modular block. You normally just pry them open with a
screwdriver. Inside you'll find up to 6 wires. Very carefully cut out all but
the green and red wires. The ones you'll be removing should be black, yellow,
white, and blue. These wires won't be needed and may be in the way. So cut them
as close to where they enter the plug as possible. The other end of these wires
have a spade lug connector that is screwed into the plastic. Unscrew and remove
that end of the wires as well. Now, you should have two wires left. Green and
red. Solder one end of the capacitor to the green wire. Solder the other end of
the capacitor to the center lug of the potentiometer (there are three lugs on
this critter). Solder one end of the resistor to the red wire. You may want to
shorten the leads of the resistor first. Solder the other end of the resistor
to either one of the remaining outside lugs of the potentiometer. Doesn't
matter which. Now to wrap it up, make a hole in the lid of the mod block to
stick the shaft of the potentiometer through. Don't make this hole dead center
as the other parts may not fit into the body of the mod block if you do. See
how things will fit in order to find where the hole will go. Well, now that
you've got it built you'll need to test it. First twist the shaft on the
potentiometer until it stops. You won't know which way to turn it until later.
It doesn't matter which way now. You also need to determine where to plug the
Noise Killer onto the telephone line. It can be done by one of several ways:

    A.  If your  modem has two modular plugs in back,  connect the Noise Killer
into one of them using a line cord.  (a line  cord  is  a  straight  cord  that
connects a phone to the wall outlet.  Usually silver in color)

    B.  If your phone is modular,  you can unplug the cord  from the back of it
after you're on-line and plug the cord into the Noise Killer.

    C.  You may have to buy a Y-type modular adaptor.  Plug the adaptor into  a
wall outlet,  plug the modem into one side and the Noise Killer into the other.
Call a BBS that has known noise problems.  After you've connected  and  garbage
begins to appear, plug the Noise Killer into the phone line as described above.
If you have turned the shaft on the potentiometer the wrong way you'll find out
now.  You may get a lot of garbage or even disconnected.  If this happens, turn
the shaft the other way until it stops and try again.  If you don't notice much
difference when you plug the Noise Killer in, that may be a good sign.  Type in
a  few  commands and look for garbage characters on the screen.  If there still
is, turn the shaft slowly until most of it is gone.  If nothing seems to happen
at all,  turn the shaft slowly from one side to  the  other.   You  should  get
plenty  of  garbage  or disconnected at some point.  If you don't,  reread this
message to make sure you've connected it right.

                                 [*][*][*]

***END OF ORIGINAL FILE***

A few pointers:

1) The pot need  not be either 5K or audio taper.  I used a 10K  15  turn  trim
   pot.  Suggest you use what is handy.

2) I used 2MFD's of capacitance (two 1MFD's in parallel) Two R.S.  p/n 272-1055
   work  fine.  Remember that about 90 Volts will appear across red &  green at
   ring, so the caps should be rated at 100VDC+.

3) I ended up with a final series resistance value (100 ohm + pot) of 2.75K.  I
   speculate that one could probably use 2MFD and a fixed 2.7K resistor and  do
   the  job  90%  of the time.  The adjustment of the pot is not very critical.
   Changes of +/- 1K made little difference in the performance of the circuit.

Hope it works as well for you as it did for me.

Mike McCauley
[EOA]

[WAN]**************************
           WANDERING WANDERER *
*******************************
More Arc and Apples
"""""""""""""""""""
By Wandering Wanderer

Had to smile...  Last month's article  dealt  with  ARC  and  Apples,  or  more
specifically,  Apple's  *lack*  of  an ARC utility.  I knew that if the article
generated any response,  more than likely it would come from the  Graphic  Dump
BBS,  a  Apple BBS in Newark,  New Jersey.  Although it supports all computers,
the system is a popular meeting place for the Apple users in the area.

Apparently I was wrong.  Well, actually half wrong.  The Apple system does have
an ARC utility.  However,  the Macintosh,  due to some technical reasons  (???)
does not.  I'll let the Graphic Dump SysOp, Bob Lindabury explain it:

Subj ->ARC programs for the Apple
From ->Bob Lindabury [#1]
Date ->10/25/88 05:45:08 PM

There  ARE a couple of deARCing programs for the Apple //  John.  Although they
haven't been received very well, they do work.

For the //e the program is called DEARC2E.  I have it up in  my  file  transfer
section  here.   It  is  a  clumsy program but it WILL unARC an ARCed file.  In
fact, I just used it to unARC a file someone sent me..text of course.

For the //gs there also is a program called DEARCGS.  I  don't  currently  have
this  one  but  I imagine it is faster than the 2E version but probably just as
clumsy to use.  At least there are a couple for us to use.

The MAC on the other hand is a whole 'nother  story.   There  is  an  ARCHIVING
program  for  the Mac called Stuffit which basically does the same thing as ARC
but with Mac specific files.  The Mac's file structure is  such  that  I  don't
even  know  if it would be possible to unARC an ARC file from another computer.
The Mac stores files in 2 separate sections called  Forks.   One  fork  is  the
Resource fork -  contains file info,  icon info, data addresses and a whole lot
of other info on the file.  Then the other fork  is  called  the  Data  fork  -
contains all the file data to run the program or to display a picture whatever.

Since  the  Mac  has  this specialized file format,  regular ARCed files may be
unrecognizable to the Mac system thus  preventing  the  ability  to  unARC  the
typical ARC files.

I'm not a programmer so I couldn't tell you exactly what the problem is,  but I
would think that if it were possible to do the UnARCing of these files, someone
would have figured it out by now.

                              [*][*][*]

So....  the Mac won't and the Apple can,  but not efficiently enough to warrant
widespread  use.   So  whose  fault  is that?  An ARC utility has recently been
released for the Atari 8bit computer that actually outperforms the ST  computer
in  terms  of  speed.   In light of all this,  I have to come to the conclusion
that, 1) Apple users don't know what they're missing, 2)  If I were using a Mac
to publish TeleTalk OnLine,  I'd be in serious trouble and 3)  I'm the only one
who cares, (and I don't even own an Apple!).

Till next month, this is Wandering Wanderer logging off...

BBSs mentioned in article:
Graphic Dump BBS [NJNEW] 201/469-0049
[EOA]

[DOS]*******************************
           UNDERSTANDING MS/PC-DOS *
************************************
The Plain Vanilla Guide, Part 2

Copyright (c) 1988 by Robert M. Connors
Permission to Reprint is granted provided
Copyright Notice is included in reprint.

------------------------
In  my  first  column,  we  discussed the CONFIG.SYS file and I alluded to such
things as an AUTOEXEC.BAT,  root directories,  and paths.  This month,  we will
look   at  all  of  these  things  which  will  hopefully  give  you  a  better
understanding of what they are and how to use them.

Before  going  any  further,  we must define and explain the use of directories
since everything we do in MS-DOS (from now on,  I will just say DOS which  will
mean MS-DOS or PC-DOS --  and don't forget,  we are discussing version 3.x, and
below, of these DOS's, not the new version 4.x)  depends on paths for efficient
operation.   If  your  computer  does  not have a hard drive,  paths are not as
important to you so you might want to skip past this part in that case.

A directory is a file on your disk(ette).  It contains a list of all the  files
that are currently active and visible on the disk.  You can see the contents of
a directory by typing "DIR<ENTER>" while at the DOS prompt (the DOS prompt will
be  a  drive  letter followed by a greater than (>)  symbol).  If you have more
files than will fit on a screen,  the list will scroll up off  of  the  screen.
Typing "DIR /P<ENTER>" (the space is not needed; "DIR/P<ENTER>" works the same)
will cause the display to pause when the screen becomes full.  You continue the
display  by  pressing <ENTER>  again,  repeating as necessary.  So think of the
"/P"  as the "pause"  command.  Here is a sample of  how  a  typical  DIRectory
listing looks:


 Volume in drive C is PC-DOS-32
 Directory of  C:\

PCD-UTIL     <DIR>      3-15-88   8:50p
AUTOEXEC BAT     1078  10-18-88   8:35a
.
.        (other files listed here)
.
NANSI    SYS     2500  10-20-86
Strike a key when ready . . .
SETCLK   COM      116   1-01-87  12:00a
.
.        (other files listed here)
.
       26 File(s)    405504 bytes free

The  first  line of the directory is the volume name or label we have given the
directory (if any)  using the LABEL command.  If there is no name assigned,  it
would  say  "Volume  in Drive C has no label."  Labels,  or names,  can also be
assigned using a parameter with the FORMAT command (/V for volume label)  which
we will discuss in a future column.

The second line,  "Directory of C:\", tells us that we are looking at the "root
directory"  of disk drive C.  Remember last month I stated that all drives  are
referenced by letters,  usually followed by a colon (:).  The slash (\) in this
line is the key to what directory we are looking at.  Since nothing follows it,
we know we are at the root directory.  Below this line is  the  list  of  files
that are contained in the directory.  The first column is the name of the file.
It  can  be  from  1  to  8  alphameric  (alphabetical,  numerical,  or special
characters) characters.

The filename is followed by one or more spaces and then a  1  to  3  alphameric
file  extension.   File  extensions  are  handy  ways to group similar files by
categories.  When the filename and file extension are put  together,  they  are
seperated  by a period (.)  and called a file specification.  For example,  the
file specification for the filename,  AUTOEXEC with the file extension  of  BAT
would  be AUTOEXEC.BAT while SETCLK COM would be SETCLK.COM (notice the removal
of any blank spaces in the filename).  The only restriction for a file name  or
extension is that they cannot begin with a blank space.

Next we have the size,  in bytes,  of the file followed by the date and time of
day the file was created or last written to.  With only a few files on a  disk,
file  maintenance  is not a problem.  However,  putting all your files into one
directory can get very cumbersome to deal with very quickly.  That  is  why  we
have  what  is  called "subdirectories."  Looking again at the sample directory
listing, we see a line that says, "PCD-UTIL"  followed by "<DIR>"  and the date
and time.  This a subdirectory (subdir), or a directory within a directory.  We
could  list  this  subdir by typing the command,  "DIR PCD-UTIL/P,"  at the DOS
prompt.  All the files that are contained in the subdir would be listed just as
the files in our root directory were.

We can use subdirs to put files together that are similar.  For example,  let's
say  I  have  Turbo  Pascal.   All the files for Turbo Pascal could be put in a
subdir entitled "TURBO"  in order to keep them together.  Likewise,  the  TURBO
subdir  could  contain other subdirs to group the source listings of programs I
write,  the .EXE(cutable)  files created by the compiler,  etc.  So as you  can
see,  directories  can  contain  subdirs  which  can  contain subdirs which can
contain subdirs which....  well,  you get the idea.  Each of these subdirs then
could  be  used  to  group  together  files of a similar nature.  The following
diagram is typical of the organization of directories:

D:\-+-BATCH
    |
    +-CVCS--------+-CATALOG
    |             |
    |             +-CM------------DATA
    |             |
    |             +-G&J
    |             |
    |             +-QUARTET
    +-DOSUTIL
    |
    +-KITTY
    |
    +-WC------------REMOVED
    |
    +-WILDCAT-----+-BULLETIN
    |             |
    |             +-DISPLAY
    |             |
    |             +-DOORS-------+-TW200
    |             |             |
    |             |             +-TW500
    |             +-HELP
    |             |
    |             +-LIVECAT
    |             |
    |             +-MENU
    |             |
    |             +-PROTOCOL
    |
    +-WORKAREA----+-ARC
                  |
                  +-TESTDOOR

This diagram is commonly referred to as a "tree"  and is  used  to  graphically
illustrate  the  structure  of  disk  directories.  I am sure,  based on how it
looks,  you can see where it got the "tree"  name.  We start at the root  (D:\)
and "branch" out from there.  Our root directory contains seven subdirs, BATCH,
CVCS,  DOSUTIL,  KITTY,  WC,  WILDCAT,  and WORKAREA.  Some of the subdirs have
other subdirs and some of the subdirs have more subdirs.  Okay,  here it comes,
so pay attention here.  What you are looking at are "paths" which are not to be
confused with the DOS command known as "PATH" (although they are related).

A  path  is nothing more than the way to get to a specific directory or subdir.
For example,  let's say we want to list the files in the TESTDOOR  subdir.   We
already have covered the DIR command (partially; more will be covered later) so
we  have the basics on how to do it.  There are different ways we could examine
that subdir's directory listing.  The easiest, at least at this point, would be
to type "DIR WORKAREA\TESTDOOR" at the DOS prompt.  Here is what we would see:

 Volume in drive D is DATADRIVE-D
 Directory of  D:\WORKAREA\TESTDOOR

.            <DIR>      6-28-88   9:07p
..           <DIR>      6-28-88   9:07p
        2 File(s)   4632576 bytes free

Hmm, looks a little different than the last directory display, doesn't it?  The
familiar volume name is there in the first line.  Our second line looks  almost
the  same but now contains information after the "D:\"  which tells us the name
of the directory (or subdir)  we are looking at.  However,  there are no  files
listed  even  though  the last line says that two files are there.  What gives?
Notice that there are two lines with <DIR>  shown.  The first line  contains  a
single  dot  in the directory/file name column and the second line contains two
dots.  These two lines (with different dates and times) will appear anytime you
get a directory listing of a  subdir.   In  the  first  line,  the  single  dot
represents  the  "current"  directory  or,  as  in  this  case,  the  directory
D:\WORKAREA\TESTDOOR.  The two dots in  the  second  line  represent  the  next
higher,  or parent,  directory or, as in this case, D:\WORKAREA.  Note that DOS
considers these dots to represent files, thus, 2 File(s)  are contained in this
subdir.  Later on,  we will discuss how to use these shorthand dots when moving
from directory to directory.   The  main  point  of  this  discussion  is  that
"D:\WORKAREA\TESTDOOR" represents a "path" to the directory we want displayed.

Paths are used by many DOS commands, one of which (DIR) we just covered.  As we
continue this column about DOS,  you will see how important paths can be.  This
month,  I will cover just the PATH command itself as we go over the second file
that DOS looks for when it initializes, AUTOEXEC.BAT.

What  is  a  .BAT  file anyway?  The extension BAT stands for BATCH file.  This
file is a pure text file that contains a series of commands that are  performed
by DOS just as if you typed the commands from the keyboard one at a time.  When
you  type  a  command,  DOS  will  check  to see if that command is part of its
built-in library of commands.  If not,  it will next see if the  command  is  a
command  (.COM)  file.  Again,  if not,  DOS checks to see if the command is an
executable (.EXE)  file.  Finally,  failing all else,  DOS will check to see if
the command is a .BAT file (if not,  then it issues an error message, "File not
found").  Assuming it is a .BAT file,  DOS will open the  file  and  read  each
line,  one  at  a time,  acting on each before going to the next.  The file can
contain DOS library commands or lines  that  contain  the  .COM  or  .EXE  file
commands, and can even jump to another .BAT file if need be.  More detail about
how  to  create  and use batch files will be covered in a future column but for
now, let's just concentrate on the AUTOEXEC.BAT file.

The purpose of the AUTOEXEC.BAT file is to  relieve  you  of  the  drudgery  of
typing various commands over each time you boot-up (or reset) your computer.  I
will  use the AUTOEXEC.BAT file I use to initialize my BBS system as an example
for this discussion and in the process,  you will see some new DOS commands.  I
won't  go  into a lot of detail about these commands since most will be covered
in later columns.  I will tell you,  however,  what the commands are  doing  in
this  batch  file.   Each line of the batch file will be numbered for reference
purposes only.  The numbers should not be included in the batch file.  Here  it
is:

 1 ECHO OFF
 2 REM set DOS path
 3 PATH C:\;C:\PCD-UTIL;D:\BATCH;D:\DOSUTIL
 4 REM Get battery backed-up DATE and TIME
 5 GETCLK
 6 MODE MONO
 7 MODE COM1: 9600,N,8,1
 8 PROMPT $P$G
 9 REM Define EDIT Configuration file
10 SET EDCONFIG=D:\DOSUTIL
11 REM Force system into TURBO (8 Mhz) Mode
12 FAST
13 REM Activate DOS PRINT utility, with 1K buffer and 20 entries allowed
14 PRINT /D:PRN /Q:20
15 SPS > NIL
16 BRK ON
17 ECHO.
18 ECHO Press ^C to ABORT batch file at this point if desired
19 REM Pause for 3 seconds before continuing in case ^C desired
20 WAIT! 3
21 REM Execute CAT.BAT to load and execute WILDCAT! BBS
22 CAT.BAT

In line 1,  we see the ECHO command followed by the parameter,  OFF.  Normally,
as a batch file is executing,  all the commands are echoed to the display.  The
command,  ECHO  OFF,  tells DOS we do not want to see all these commands.  This
makes the display look a bit nicer.  Things tend to  move  pretty  fast  during
batch execution and sometimes you won't even be able to read what is happening,
so  you  might  as  well  turn the ECHO OFF.  Besides,  echoing commands to the
screen does slow down the batch execution.  You can turn the ECHO  back  on  by
just putting the word "ECHO" or "ECHO ON" in a seperate line.

Line  2  starts  with  the REM command.  REM is short for REMark and is used to
document your batch file.  Anything following REM is ignored by DOS.   If  ECHO
is ON,  REM lines will appear on your video display.  By the way, both ECHO and
REM are commands used _ONLY_  in batch files.  Typing them from the DOS  prompt
has  no effect.  In our REM line,  we indicate that we are going to set the DOS
PATH (finally, useful path information!).

Line 3 is the PATH command which is used by DOS to determine where to look  for
a  file  if  it  can  not  be  found  in the current directory or subdirectory.
Remember a few lines ago my talking about how DOS  searches  for  a  file  (the
.COM, the .EXE, or the .BAT files)?  If no path is set, DOS issues the File not
found error message if the file is not in the current directory/subdir.  If the
path is set, DOS will search for the file in each directory/subdir specified by
the  command before issuing the error message (assuming the file isn't found in
any of them).  To see what your path is set to, just type PATH<ENTER>  from the
DOS  prompt.  If you see "PATH ="  with nothing following it,  then there is no
path for DOS to use.

Let's look at line 3 and see exactly what is there.  Of  course,  we  have  the
word,  "PATH."  Following  that  command,  there are a series of "paths,"  each
seperated by a semicolon.  Each "path"  is the drive and directory we want  DOS
to  search  when  looking  for  files.   Since my C:  drive has DOS in the root
directory,  I specified a path of "C:\."  I put all the utilities for DOS (such
as format,  backup, chkdsk, etc.) in a subdir on drive C: called PCD-UTIL, so I
included that subdir in the path line.  Almost all of my  batch  files  are  on
drive  D:  in a subdir called BATCH,  so that is the next path I have included.
The subdir of DOSUTIL contains many utilities that I have accumulated over  the
years  and  that  is  the  final  entry  on  the line.  Note that each of these
directories is seperated by the semicolon except for the last one.  The end  of
line  characters  (a  carriage  return followd by a line feed),  which does not
display, ends the PATH command.  Once executed, DOS will search, in order,  the
current  directory,  and then the directories specified in the PATH command and
either execute the file if  found  or  issued  the  error  message.   To  reset
(delete)  the PATH command, the command, "PATH=<ENTER>" at the DOS prompt or in
a batch file will remove the path and DOS will only check the current directory
once again.  One final note about PATH.  DOS uses it to find  executable  files
only,  not data files.  Data files should always be in the current directory or
the application program must be given the path in which the files can be found.

Line 4 is another remark while line 5 contains a command,  GETCLK.   GETCLK  is
not  a DOS command.  It is the name of a .COM file that came on a diskette with
my multi-I/O (input/output) board that has a battery backed-up clock on it.  It
causes the clock date and time to be used as the system (DOS) date and time and
eliminates the need to manually set the date and time each boot-up.  Note  that
I  did  not  include  the  .COM designation since it is not needed (DOS adds it
automatically,  as it will the .EXE and .BAT designations if the  .COM  is  not
found).

Lines 6 and 7 use the DOS MODE command.  MODE is used to set values for various
devices  that  you  may  have  connected to your computer.  Among these are the
printer,  a modem,  and the video display.  The first MODE command informs  DOS
that  my  system  uses a monographic display (as opposed to color).  The second
MODE command initializes my communications port to use port 1 at 9600 baud with
no parity, an 8-bit word,  and one stop bit.  What all these mean is beyond the
scope  of  this  article  but if you use a modem with a communications program,
your documentation covers them.

The next line,  Line 8,  has a command called PROMPT.  When you  first  boot-up
DOS,  the  prompt line for DOS is the letter of the drive followed by the colon
and a "greater than"  symbol.  For example,  if you boot-up on  drive  C,  your
prompt is "C>".  No matter what directory on your C drive you are in,  you will
see the same DOS prompt.  I for one, like to know what directory (or path) I am
currently in which is what my command, "PROMPT $P$G," does.  If I am on drive D
in subdir MENU, my DOS prompt shows: D:\WILDCAT\MENU>.  If I change drives, the
drive letter, as well as the path,  also changes.  This way,  I am always aware
of  where I am at regardless of the drive or directory I currently have active.
The PROMPT command has other options you can use to set colors and  other  neat
things.  We will cover them later.

Line 10 contains the SET command.  If you type "SET<ENTER>"  at the DOS prompt,
you will see such things as the location of the  COMMAND.COM  file,  what  your
path  is  set to,  what your PROMPT variables are (if any),  and other SETtings
that you have specified.  In my batch file,  I tell DOS that EDCONFIG should be
set  to the D:\DOSUTIL path.  This setting is stored in reserved memory in what
is called the DOS environment.  DOS does not use this particular  SETting,  but
another  file I have does.  The file is a text editor which will search the DOS
environment for the term,  "EDCONFIG=",  and when found,  extracts the path  so
that  it  knows where to place its configuration files.  Many programs use this
feature which acts almost like the PATH command.  If a program  you  use  takes
advantage of the feature,  it will be in the documentation for that program and
it will tell you exactly what the SET parameters should be.  Be aware that  you
can  issue  a  SET  command over and over again,  each one containing different
parameters (similar to the DEVICE command in  the  CONFIG.SYS  file  we  talked
about last month).

Next  is  the  FAST  command  in  line  12.  Again,  this is not a DOS command.
Rather,  it is the name of a .COM file that switches my computer into the TURBO
mode, changing the operating speed from 4.77 mhz to 8 mhz.

In line 14,  I tell DOS to setup the printer spooler for 'future' use; that is,
reserve space for it without actually printing  anything  at  this  time.   The
/D:PRN  parameter  tells  the PRINT command that I want DOS to use the standard
PRiNter device.  I could have also stated LPT1 (line printer 1) since it is the
same as the PRN device.  Alternatively, I could have used LPT2 if, for example,
I have 2 printers and want to use the second one for the spooler (or  only  one
printer  but  it is connected to the second printer port).  The /Q:20 parameter
tells DOS that I want to specify up to a maximum of 20 files to be  printed  at
one time (higher or lower numbers can be used).  PRINT has many more parameters
than  the two specified here (which we will cover later)  but I find that these
two are sufficient for most purposes.  Now whenever I want to print a  file,  I
type  (at  the  DOS prompt)  "PRINT filespec"  and DOS will put the file into a
queue (pronounced cue)  for printing.  I can issue up to 20 such  commands  and
each  file  will  be  printed  one  at  a  time in the order I issued the PRINT
commands.  DOS will send a form feed (page eject)  after each file is  printed.
Anytime  I  want  to  see  the  current status of the queue,  I issue the PRINT
command without any parameters.  The current file being printed is shown  along
with  a  list  of all other files waiting in the queue to be printed.  If there
are no files being printed,  DOS will display  the  message,  "PRINT  queue  is
empty."  By the way, a queue is a term that describes a line (yes, even when in
line at the bank,  you are in a queue waiting for your turn).   Queues  can  be
based on 'first in,  first out'  (FIFO)  or 'last in,  first out'  (LIFO).  Our
PRINT queue is a FIFO queue.

DOS gives us the capability of sending to the printer anything that is  on  the
screen.   If,  at the DOS prompt,  we type Shift-PrtSc (hold down the Shift key
and press the PrtSc key),  whatever is currently on the screen is sent  to  the
printer.  If we type Ctrl-PrtSc, this process is continuous until Ctrl-PrtSc is
typed  again.  Sometimes I don't want the entire screen sent to the printer but
would rather have only a portion of the screen printed.  That is the purpose of
line 15.  SPS is a .COM file that is called a TSR  (terminate,  stay  resident)
program.  It loads itself into memory,  hooks into DOS, and then returns to the
DOS prompt (or back to  the  batch  file).   It  sits  there  waiting  for  the
Shift-PrtSc  combination.   When  that  combination  is  seen,  it allows me to
specify the starting and stopping point of the screen dump  to  printer.   That
way, I don't need the entire screen printed each time.  The portion of the line
that says ">  NIL" tells DOS that this program will generate screen output when
it is first run and that I don't want to see the output.  So DOS  sends  it  to
NIL  which  means,  nowhere.  Actually,  NIL is a file that DOS uses to reroute
things of no practical value.  Since there is no pratical reason for me to  see
the ouput from SPS.COM each time,  I route it to NIL (by the way,  rerouting is
also called "piping").  Remember, ECHO OFF only works with batch commands,  not
the output from an application program.

The  "BRK ON"  in line 16 is similar to SPS.  However,  it does not load itself
into memory;  in fact,  it is not even a .COM file.  It is a command  that  has
been   added  to  DOS  by  a  DEVICE  driver  I  have  in  my  CONFIG.SYS  file
(DEVICE=BRK.DRV).  This driver permits me to allow or  disallow  processing  of
^C/^Break  keystrokes.  Since my BBS uses live programs where the BBS is exited
and a batch file is executed (which ^C or ^Break  can  terminate),  having  the
ability  to  turn  off  ^C/^Break  processing  by DOS is essential.  Otherwise,
callers could break out of the executing batch  file  and  cause  havoc  to  my
system  (they would go to the DOS prompt).  In this line,  I turn the ^C/^Break
processing on because of lines 17-20.

In line 17, we see a variant of the ECHO command; it is followed immediately by
a period (.)  which causes a blank line to be  displayed.   It  is  useful  for
spacing.   In  line  18,  we  tell  DOS  to  ECHO the phrase following the ECHO
command.  This turns ECHO on *only* for this one line; it turns OFF again right
after the line is displayed.  This is how you can send prompts  for  particular
actions  you may want to accomplish.  In this case,  I use it as a way to break
out of the batch file if I do not want the BBS to activate.   It  tells  me  to
press  ^C  to  ABORT  the  batch  file if I desire.  Line 20 uses the WAIT!.EXE
program (from Mustang Software, the authors of my BBS software)  to countdown 3
seconds  while  waiting for the ^C.  If I do not type ^C during that time,  the
batch file continues.  If I do type it,  DOS will ask me if I want to terminate
the batch file.  If I answer yes, the batch file is exited.  If I answer no, it
continues as if I never pressed ^C.

If  I do not press ^C or answer no to the termination prompt,  line 22 executes
the CAT.BATch file that initializes the BBS (turns it on)  and this batch  file
(AUTOEXEC.BAT) is done.

Let's summarize what we have learned in this month's column.  AUTOEXEC.BAT is a
text  file  that contains a series of commands,  each on a seperate line,  that
emulate  (and  eliminates)   typing  of  the  commands  at  the   DOS   prompt.
AUTOEXEC.BAT  is always looked for by DOS at boot-up or reset and if found,  is
executed.   The  file  can  contain  any  DOS  command,  .COMmand  file  names,
.EXEcutable  file names,  or .BATch file names.  Parameters for these files can
be included in each batch line.  We  can  document  a  AUTOEXEC.BAT  using  the
special  batch  REM  command  and  can turn on or off screen displays using the
batch ECHO command.  We can even direct the DOS send screen displays  from  any
of  the  files  to  a  special  NIL file,  resulting in cleaner displays (or no
display at all).  Finally, we can jump from our AUTOEXEC.BAT to any other batch
file.  We can change AUTOEXEC.BAT at any time simply  by  editing  it  to  add,
change,  or  delete lines using any text editor or word processor that does not
imbed any type of formatting control codes in the file.

By  thinking  through  and  planning  your  AUTOEXEC.BAT  file,  very  powerful
sequences can be put together.  The best way to determine what you will need in
your  batch  file  is to keep track of all the things you now type from the DOS
prompt (such as setting the date and time, establishing your prompt, etc.)  and
including those things in the batch file.  It is a great time saver.

I  know  that  I  promised  you  all  last month that I would discuss the VDISK
ramdisk utility, but I simply have no room for it this month.  It will be first
on our agenda next month.  See you then.  TTFN!

------------------------
Have a question about DOS?  Have a comment about this column?  Just post it  on
any  authorized  T/TalkNET  BBS  or  call Wildcat Orphanage (719-392-6631)  and
Doctor Bob will be glad to answer/publish it in TeleTalk OnLine.  See your name
in print!
[EOA]

[PCP]**************************
                  HOT PURSUIT *
*******************************
Talk'n the Telenet Blues
""""""""""""""""""""""""
John Peters

Has anybody else noticed?  All of a sudden,  transferring files on  PC  Pursuit
has become a nightmare.  (Especially uploads.)  Sometimes it works,  many times
it doesn't.  Zmodem,  once considered to be the optimum  protocol  for  maximum
speed  and  efficiency  on packet systems,  now doesn't work at all.  Strangely
enough,  all of this  occurred  when  the  new  indial  nodes  were  installed.
Coincidence?

                               [*][*][*]

[NET EXCHANGE BBS]

From: Jim Howard                  To: Mark Earle

Good  luck  in  getting  an  answer..   No one has yet explained how it is that
uploads are never more than 50 percent efficient, whereas downloads are usually
95 percent.  They also don't bother to tell why it WAS NOT this way two  months
ago.  All they say is "we're looking into it".

Here's  my  theory....   On  regular  telenet,  during  prime time,  there is a
"kilopacket"  limit per hour.  I believe the limit is 3.5 kilopackets per hour,
and there is a .75 extra charge after that per extra packet...  A kilopacket is
roughly 75k.  Now,  apparently outdials can send data as fast as they want, but
when you are calling through your local telenet and trying to  upload,  if  you
use an efficient protocol such as Zmodem, you instantly hit the "cutoff" point,
where  your  speed of data sending is calculated to be more than the set limit.
This results in a "possible  data  loss"  error.   This  is  based  on  various
information  I  have  gleamed  from  a few sources,  and is,  to the best of my
knowledge,  the reason for the problems.  OF course,  it  could  be  completely
wrong, but thats just what I have heard.

                               [*][*][*]

From: Hank Oxford                 To: Vann Hall

Since  I  have not the had opportunity to study communications systems in great
detail,  I can't argue with your appraisal of Zmodem's design.  However,  if it
is so bad and what you say is true,  why did it function so well for so long on
Telenet?  I see it like this :

    1)  Zmodem is supposedly designed to work well  over  Telenet  (or  so  the
author says).

    2) It did work extremely well for quite some time.

    3) Without being changed, it suddenly quit working

    4) Other protocols began to suffer a decrease in performance.

The  facts pretty much point in the direction of something being changed in the
makeup of Telenet, don't they?

                               [*][*][*]

From: Christopher Miller          To: David Purks

I don't want to belabor the point, but I am a Field Engineer for a natl service
organization, and if I came up with a report like that after a problem had been
in effect for 5 months,  I don't think I would have a chance to write a  second
opinion.   First  off,  my  companies equipment would be out the door due to an
extremely upset customer.  I don't like the delays in correcting  the  problem,
but  I  also  realize  that  PCP  is basically the only game in town other than
direct dial, so I suppose I'll have to live with it...

                                [*][*][*]

I can deal with the BUSYies and the quirks and even the slowness of  transfers.
However, uploading and downloading are critical areas or me.  Unfortunately, PC
Pursuit IS the only game in town.

Telenet has promised some answers.
To be continued...

PC PURSUIT BULLETINS AND UPDATES
""""""""""""""""""""""""""""""""
Net Exchange BBS

The following 2400 bps outdial rotories are currently operational:

          Philadelphia             Atlanta
          Washington, DC           Seattle
          Newark                   Houston
          Boston                   Chicago
          Denver                   Detroit
          New York                 Los Angeles
          Dallas

The following 2400 bps outdial is expected up as soon as possible:

          San Francisco

    The following new sites are operational:

          San Diego       Kansas City
          Colton          St Louis
          Palo Alto       Hartford
          Santa Ana       Oakland

The  following  site was originally announced (in January)  in error and is not
expected up with the rest of the new sites: Sacramento.

FREE DAYS
"""""""""

The following holidays are considered as "free" days for use of Pursuit:

          New Year's Day
          July 4th
          Thanksgiving Day
          Labor Day
          Christmas Day


NEWARK UPDATE
"""""""""""""
The decision was made this morning to postpone  implementation  of  the  Newark
exchange  restrictions  pending development of a proposal to open new cities in
northern NJ to cover a significant portion of  the  exchanges  which  would  be
lost.  This proposal is not expected for at least several months.

Your  comments here have convinced the marketing management that northern NJ is
an important PC Pursuit destination!
[EOA]

[PGR]**************************
        PROGRAMMING CHALLENGE *
*******************************
Programming Challenge Contest
"""""""""""""""""""""""""""""
By Norman Morgan

Captured on Nick-At-Nite
[UTSLC] 801/964-1889 [T/TN]

[NOTE:  The following article pertains to the versatile "Door"  option found on
WILDCAT!  boards.  Ed.]

The Eagle's Nest BBS announces a FIRST .....
The DOOR Programming Challenge Contest!

Here's how it works.  We challenge you to write a door program for our BBS.  We
will supply the special code to do the "hard parts"  of the job, like the modem
I-O routines.  You supply the creativity.

1.  Download either ALLEYCAT.ARC or CATPCH13.ARC from The Eagle's  Nest  to  do
    the special I-O routines.  Both of these programs are very well-written and
    easy to work with.

2.  Write your door using Microsoft QuickBASIC.  It may be a game or other type
    program  of  general interest to BBS users.  (You may use another language,
    but you will have to come up with your own "door patch"  code and  we  will
    not be able to help you debug.  There are door code modules available for C
    and Turbo Pascal.  Ask us about where to get these.)

3.  Upload  the  finished  program to the SysOp or Private  area of The Eagle's
    Nest along with documentation.  Source code must be included  but  will  be
    kept  confidential  unless  you tell us it is OK to release it.  You retain
    ALL rights to your program.  The deadline for entries is January 31, 1989.

4.  We will establish a special menu for our Programming Challenge doors.   Our
    callers  will have the opportunity to try your creations beginning February
    7,  1989 and they will  decide  the  winner  starting  February  28,  1989!
    Winners  will  be determined solely from the caller vote totals as of March
    14,  1989.  The winners will be announced on March 18,  1989  to  mark  the
    first anniversary of The Eagle's Nest BBS.

5.  Now  the  GOOD  part!  A cash prize of $50 dollars will  be offered for the
    first-place winner and $20 for the second-place.  This will  be  contingent
    upon the number of entries received.  If only two people enter,  there will
    only be one prize of $50.  Contest is void if fewer than  two  entries  are
    received.  If a commercial sponsor can be found, we may be able to increase
    these prizes.

Let's  see  what kind of programmers we have out there!  Put your thinking-caps
on and sharpen your pencils!  There is also the chance to  make  a  buck  here.
SysOps  across  the country are always looking for good door programs.  We will
help  you  market  your  program  as  Shareware  by  making  it  available  for
downloading  on  The  Eagle's  Nest and by uploading it to any distant BBSs and
on-line services that we call.

So...get started today.  Call The Eagle's Nest BBS and get either the  ALLEYCAT
or CATPCH13 module so you can start writing.

                        The Eagle's Nest BBS
                 The First BBS in the US dedicated
               to supporting the principles, programs
              and members of The Boy Scouts of America
              (812) 425-6950 - 300/1200/2400 - 24 hours
                    8/N/1 please!  A Wildcat! BBS
                        Norman Morgan - SysOp
                        (812) 425-6940 voice
[EOA]

[OFF]*******************************
                           LOG OFF *
************************************

Articles  and  advertising contained in TeleTalk OnLine do not necessarily mean
endorsement.  Signed articles are the  opinion  of  the  authors  and  are  not
necessarily the opinion of the publisher or the SysOp(s) of this BBS system.

                              [*][*][*]

Every  effort  is  made to verify phone numbers which appear in TeleTalk OnLine
Magazine.   However,   due  to  the  constant  changes  within  the  field   of
telecommunications, accuracy is not guaranteed.

                              [*][*][*]

No copyrighted material will be acceptable for publication without the express,
written  permission  of the copyright holder.  We reserve the right to edit the
letters and copy.

Computer clubs, user groups,  and Electronic Bulletin Board Systems are free to
reprint  or  republish  information  in  TeleTalk  OnLine  without  limitations
provided the following is printed at the top of the article:

                     Courtesy of TeleTalk OnLine Magazine
                       WILDCAT! Orphanage (719)392-6631
                            Reprinted by permission.

[EOF]
