Category : BBS Programs+Doors
Archive   : INFDOOR3.ZIP
Filename : INFODOOR.DOC

 
Output of file : INFODOOR.DOC contained in archive : INFDOOR3.ZIP




















InfoDoor

(C) Copyright 1987, 1988
by R. P. Byrne

Version 3.0
December 18, 1988




InfoDoor version 3.0 Documentation i

Licensing Information......................................1
Program Overview...........................................2
The InfoDoor Database......................................3
The InfoIndx Program.......................................7
Installation...............................................8
Configuration File(s) Setup............................8
Batch File Setup......................................11
Doors.Dat File Entry..................................12
Commands..................................................13
Sysop Commands........................................13
Display Toggle....................................13
Other Sysop Functions.............................13
Local Testing.....................................13
Main Menu Commands....................................13
Enter keyword for search..........................14
Mode (graphics)...................................15
Help..............................................15
Operator Page.....................................15
Xpert mode........................................15
View Statistics...................................15
Quit..............................................15
Goodbye (Hang up).................................16
Item Selection and Display Options....................16
Scan Item Headers.................................16
Display all items.................................16
Select item for display...........................17
Display next item.................................17
Acknowledgements..........................................18
Feedback..................................................19

InfoDoor Licensing Information Page 1


InfoDoor is provided for private, personal use. You may distribute
InfoDoor so long as the following conditions are satisfied:

The program is supplied in its original, unmodified form, including
this documentation.

No fee is charged for the distribution of InfoDoor.

The program may not be distributed as part of any other application
or service without the written consent of the author

InfoDoor is being distributed as a ShareWare product. If you like the
program and feel that it is useful, then send the author a check for
$25.00.

If you are running your bbs for profit, or as part of a business or
government operation, then you are required to remit $50.00 to the
author for each copy of PCBoard under which the InfoDoor program will
be run.

Send checks to: Mr. Richard P. Byrne
5 Twin Elm Terrace
Sparta, NJ 07871



* * * DISCLAIMER * * *


Unfortunately, I cannot and do not claim that the InfoDoor
program is good for anything! If YOU think it is, that's
great, but it is up to you to decide. If you lose a
million dollars because InfoDoor messes up, I refuse to be
held responsible...it is you that is out the million, not
me! In short, you the user must accept full
responsibility for any and all consequences resulting from
the use of this program.


InfoDoor Program Overview Page 2


InfoDoor is a program for use with PCBoard version 14.0 that searches
ASCII text files and displays the results of that search to the
caller. It is not perfect, but it is fast and effective.

InfoDoor utilizes an Index file for fast and efficient searches of
your text database. A companion program, InfoIndx, is used to create
and maintain this index.

Both InfoDoor and InfoIndx expect your database files to be structured
in a consistent manner. Each file contains an optional Header
followed by individual Items. Certain strings are used to identify
each part of a database file as well as the individual items within
the file. These strings are user configurable and are communicated to
InfoDoor via a configuration file.

To help you in setting up your own InfoDoor database, a working sample
is provided in the InfoDoor archive file (see the file README for more
details on the contents of your distribution archive). I would urge
you to become familiar with this sample application before attempting
to implement your own. Each of the database files, the configuration
file, and the index file in this sample application contain nothing
but straight, ASCII text and may be printed for easy reference while
reading through this document.


The InfoDoor Database Page 3

It is almost always easier to learn by example rather than by studying
a list of steps to be followed. This is especially true when it comes
to setting up and running the InfoDoor program where it is actually
easier by an order of magnitude.

Contained in your InfoDoor distribution archive is a sample
application based on the news digest Info-IBMPC. Included in this
application is a database consisting of two "item" files (Info006.065
and Info006.066), an "index" file (InfoIBM.Cfg), and an InfoDoor
configuration file.

Throughout this and succeeding sections of this manual, we will be
referring to this application as various points are introduced and
discussed. It would be a good idea to print out the files mentioned
above before proceeding. Having this "live" example in front of you
as you proceed will make learning to install and use InfoDoor that
much easier (after all, a picture IS worth a thousand words, isn't
it?).

Ok, so what is an InfoDoor database anyway? Simply put, an InfoDoor
database is one or more text files stored in a subdirectory of your
hard disk. These text files are referred to as "Item Files" in
InfoDoor terminology. Your database may contain any number of Item
Files.

An individual Item File may contain any number of "Items". An Item is
a single unit of information that, when selected via a keyword search,
may be displayed to the caller.

There is no limit on the size of your Item Files, however best results
can be expected when each is somewhere in the range of 30 to 50
kilobytes in size.

Before being used by the InfoDoor program, your database must be
indexed. What this means is that a file must be created which
contains one line for each Item in each Item File in the database.
These lines will contain information about where that Item is located
and what information it contains. InfoDoor's companion program
InfoIndx is used to perform this indexing function (we'll talk about
how this is actually accomplished a little later).

Take a look at the sample Item file shown below. It can be found in
its entirety in the sample Info-IBMPC application provided with
InfoDoor.

The component parts of this sample Item File are labeled on the left
with numbers in parenthesis and are described in detail below:


The InfoDoor Database Page 4

Sample Database Item File (Info006.065)

+===========================================================
+- |
| | Info-IBMPC Digest Thursday, 24 September 1987 Volume
| |
| | This Week's Editor: Billy Brackenridge
| |
| | Today's Topics:
| | Smalltalk on the PC/AT
| | Partitions on Z-248 Hard Disk
(1) -+ | CTS Modem Garbage
| | How to get MIT/CMU TCP/IP Package
| |
| | . . .
| | . . .
| | . . .
| |
| | etc.
+- |
(2) --- | ----------------------------------------------------------
+- |
| | Date: Mon, 21 Sep 87 17:19:30 PST
| | From: [email protected] (David Reisner @teleso
(4) --- | Subject: Smalltalk on the PC/AT
| |
| | Yep, Softsmarts is still around. Although mail to the old
| | still get to them, they've moved to
| |
(3) -+ | 299 California Ave, Suite 205
| | Palo Alto CA 94306
| | (415)327-8100 (same as before)
| |
| | . . .
| | . . .
| | . . .
| |
| | etc
+- |
(5) --- | ------------------------------
+- |
| | Date: Mon, 21 Sep 87 21:27:13 CDT
| | From: [email protected] (Mahan)
(4) --- | Subject: Partitions on Z-248 Hard Disk
| |
| | Jim,
| |
| | I have experienced this also with only installing one
(3) -+ | the military contract (Air Force and Dahlgren) Z-248's.
| | It seems that if you assign partitions manually (selected
| | Zenith reserves the drive letters c,d,e,f for drive partit
| |
| | . . .
| | . . .

The InfoDoor Database Page 5

| | . . .
| |
| | etc

+- |
(5) --- | ------------------------------
|
+===========================================================

(1) This section of the Item File is called the "File Header". The
File Header is never used by the InfoDoor and may therefore contain
any information desired. Typically, this part of the file is used to
store "memory jogger" information for the person(s) that will be
maintaining the database (e.g. date created, update information, terse
summary of contents, etc.).

(2) This line separates the File Header from the rest of the Item
File. It may contain any sequence of ASCII characters not found in
the header itself. The string chosen for this function must be the
first characters appearing on the line. It will be referred to in
this document as the "End of Header" string.

(3) These sections of our sample Item File are the actual Items that
are indexed and that may be displayed to the caller following a
successful keyword search of the index file.

(4) These lines determine the content of the Index File entry for each
Item. In InfoDoor terminology, they are referred to as Subject
Headers. A Subject Header contains the keywords by which the Item
will be referenced.

InfoDoor identifies Subject Headers via a unique string of characters
called the "Subject ID" string. This string must begin the line and
may contain any sequence of ASCII characters not found in the body of
any Item.

(5) To be able to display only the items that have been matched by a
keyword search, InfoDoor needs to be able to identify where each Item
in the file ends. This is accomplished by following each Item in the
file with a line called the "End of Item" string. This string must
appear on a line by itself and may contain any sequence of ASCII
characters that will not be found in the body of any Item.


InfoDoor "learns" about the setup of your system and the structure of
your database by reading a configuration file. Among other things,
the configuration file tells InfoDoor what you have chosen as your
"End of Header", "Subject ID", and "End of Item" strings.

Look at the sample configuration file shown below. It can also be
found as part of the sample Info-IBMPC application provided in your
InfoDoor distribution archive.

Since this section of the document concerns itself with the structure
of an InfoDoor database, a complete discussion of the contents of a

The InfoDoor Database Page 6

configuration file is postponed until later. For now, concentrate on
the last three lines of this file. These lines are labeled with
numbers corresponding to the sample Item file printed earlier.

Sample Configuration File (InfoIbm.Cfg)

+===========================================================
|
| c:\infoibm\infoibm.idx
| c:\infoibm\hello
| c:\infoibm\news
| c:\infoibm\goodbye
| c:\infoibm\help
| c:\infoibm.tmp
| c:\infoibm\
| c:\pcb\pcboard.sys
| c:\pcb\pcboard.dat
(5) --- | ------------------------------
(4) --- | Subject:
(2) --- | ----------------------------------------------------------
|
+===========================================================


The InfoIndx Program Page 7


The InfoIndx program is used to create and maintain an index for your
database. Like InfoDoor, InfoIndx needs to know about the structure
of your database and reads the InfoDoor configuration file to acquire
this information.

The syntax for invoking the InfoIndx program is as follows:

InfoIndx [d:][\path\]CfgFilename ItemFilespec

Where CfgFilename specifies the name of a valid InfoDoor configuration
file (as described in the next section of this document) and
ItemFilespec contains a valid DOS file specification for one or more
Item Files (this specification may include DOS wildcard characters).

The InfoIndx program sends its output to the DOS standard output
device. To capture this output to an Index File, use the redirection
facilities provided by DOS (ie. >filename or >>filename).



InfoDoor Installation Page 8


Installation of InfoDoor is a simple process. What little information
the program cannot obtain from PCBoard's own setup files (pcboard.dat,
cnames, etc.) is provided by the sysop in a configuration file.

Once a configuration file has been built, a batch file is created to
invoke the door program. This batch file serves to invoke the door
program, and return the caller to PCBoard after the door is terminated
by the caller.

Finally, entries are made into PCBoard's Doors.Dat file(s) to inform
the board software that a new door is available to callers.

Configuration File(s) Setup
===========================

The environment under which InfoDoor will operate must be described
in a configuration file. There is no magic associated with this
file, so you can use your favorite editor (Edlin?) to put one
together or to make changes to the samples provided. There are
only 2 rules to follow:

* Put each entry on a line by itself
* Precede any comment in the file with a semicolon

================================================================
NOTE: A separate configuration file needs to be created for each
node of a multi-node system.
================================================================

Several sample configuration files are provided in the InfoDoor
distribution archive. These should be used as templates for
creating your own configuration files.

InfoDoor.Cfg - Sample config. for single node system
InfoDoor1.Cfg - Sample config. for 1st node of a two-node system
InfoDoor2.Cfg - Sample config. for 2nd node of a two-node system

Pretty simple, eh? Ok, lets begin with a description of what is
specified on each line in the file.


Line 1: Full Path and Filename for the database Index File

This line specifies the name of the Index file for your
database. This file is created by the InfoIndx program
and contains information about each Item in your database.

Line 2: Full Path and Filename for an Opening Message File

This line specifies the "base" name of a text file that
will be shown to the caller when the door is first opened.


InfoDoor Installation Page 9

If the caller is NOT in graphics mode when the door is
opened, InfoDoor will look for a file with the same name
specified here. If the caller IS in graphics mode,
InfoDoor will append a 'G' to this filename and attempt to
display it. Should this fail, InfoDoor will fall back to
displaying the file with the exact name specified here.
If this too fails, no opening message will be displayed,
and processing will continue normally.

The contents of this file will NOT be paginated for the
caller, so keep it short.

Line 3: Full Path and Filename for a News File

This line specifies the base name of a text file that will
be displayed to the caller following the Opening Message
File.

As with the opening message file, a graphic version may be
created. Append a 'G' to the name of the graphic version
filename, and InfoDoor will automatically display it if
the caller is in Graphics mode. Similarly, if the graphic
version cannot be found by InfoDoor, the Non-Graphic news
file is displayed. If neither is found, processing
continues normally.

The contents of this file will be paginated, so feel free
to make it as long as you need it to be.

Line 4: Full Path and Filename for a Logoff Message File

This line specifies the name of a text file that will be
displayed to the caller after the G)oodbye command is
issued (before carrier is dropped).

As with the Opening Message and News files, a graphic
version may be created for callers in color graphics mode.

The contents of this file will NOT be paginated, so keep
it short.

Your existing Script0 file can be used, however the
semicolons are not parsed out prior to display. It is
suggested, therefore, that you copy Script0 to another
name and then edit out the semicolons.

Line 5: Full Path and Filename for a Help File

This line specifies the base name of a text file that will
be displayed to the caller if the H)elp command (or it's
synonym '?') is selected from one of InfoDoor's menus.

As with the Opening Message and News files, a graphic
version may be created for callers in color graphics mode.

InfoDoor Installation Page 10


The contents of this file will be paginated, so feel free
to make it as long as you need it to be.

==================================================================
NOTE: The first four lines of the configuration file MUST contain
valid DOS file specifications. The files do not need to
actually exist, but valid file specifications must be
provided.
==================================================================

Line 6: Full Path and Filename of the Main Menu file

This line tells the door where to find its main menu. The
rules for creating both graphic and non-graphic versions
of the main menu are the same as stated above for the
opening message, news, logoff, and help displays.

A sample main menu file, called IMenu, is provided in the
InfoDoor archive.

Line 7: Full Path and Filename of the Item Display menu file

This line tells the door where to find its Item Display
menu (see the description of InfoDoor commands in the next
section for more details on the contents of both InfoDoor
menus). The rules for creating both graphic and non-
graphic versions of this menu are the same as stated above
for the opening message, news, logoff, and help displays.

A sample Item Display menu (called IRMenu) is provided in
the InfoDoor archive.

Line 8: Full Path and Filename of a Search Results file

This line specifies the name of a temporary file that will
be used to hold the results of each database search.
InfoDoor will automatically delete this file before
exiting back to the board. It is recommended that this
file be located on a different physical drive (preferably
a ramdisk) than the one on which your database files are
located.

Line 9: Subdirectory containing the Item File(s) for your database

This line tells the door where to find your database of
Item Files. Specify the subdirectory in which you keep
all of your Item files. Make sure that the last character
of the subdirectory specification is a backslash (\).

Line 10: Full Path and Filename of the PCBoard.Sys file


InfoDoor Installation Page 11

This line tells the door where to find the PCBoard.Sys
file that is generated by PCBoard whenever a caller enters
a door.

Line 11: Full Path and Filename of the PCBoard.Dat file

This line tells the door where to find the PCBoard.Dat
file that contains the setup information for PCBoard.

Line 12: End-of-Item string

This line specifies the string you've chosen to separate
the Items in your Item files (see the section on "The
InfoDoor Database" earlier in this document for an
explanation of the significance of this string).

Line 13: Subject-ID string

This line specifies the string you've chosen to identify
the content of each Item in your database (see the section
on "The InfoDoor Database" earlier in this document for an
explanation of the significance of this string).

Line 14: End-of-Header string

This line specifies the string you've chosen to identify
the end of the Header section of each Item File in your
database (see the section on "The InfoDoor Database"
earlier in this document for an explanation of the
significance of this string).


Batch File Setup
================

A batch file needs to be created to invoke the InfoDoor program.
This batch file will be renamed to door.bat and executed by PCBoard
when the door is selected. The only difference between a "real"
batch file and a "door" batch file is the filename extension.
While DOS expects the extension to be '.BAT', PCBoard expects no
filename extension at all.

e.g. "InfoDoor.Bat" is no good, but "InfoDoor" is fine.

Assuming that all InfoDoor files are kept in C:\Doors, that
C:\Doors is part of your DOS Path, and that the name of the
InfoDoor configuration file is INFODOOR.CFG, then the following
door batch file should suffice:

INFODOOR C:\DOORS\INFODOOR.CFG
BOARD

(If C:\Doors were not part of your DOS Path, the batch file would
need to change subdirectories before running the InfoDoor program.)

InfoDoor Installation Page 12


If you run a multi-node system, then you will need separate batch
files for each node. For instance:

Node 1 Node 2
=============================== ===============================
INFODOOR C:\DOORS\INFODOOR1.CFG INFODOOR C:\DOORS\INFODOOR2.CFG
BOARD1 BOARD2

Some sample batch files are provided in the InfoDoor archive file.
These may be used as templates for building your own batch file(s).

InfoDoor - Batch file for use on single node system
InfoDoor1 - Batch file for node 1 of a two node system
InfoDoor2 - Batch file for node 2 of a two node system

NOTE: If your DOORS.DAT is shared between nodes, you would rename
both InfoDoor1 and InfoDoor2 to InfoDoor, but place the
appropriate one in the "\PCB" subdirectory for each node.

Doors.Dat File Entry
====================

The final step for installing InfoDoor is to create an entry in
your board's DOORS.DAT file (and possibly also in your conference
doors.dat file if your conferences do not use the one for the main
board area). This file describes all available doors to PCBoard
and instructs PCBoard as to the name of the batch file to be
invoked when a particular door is selected by the caller. Consult
your PCBoard documentation for setup instructions for this file.

A sample entry in DOORS.DAT might be:

InfoDoor,,43

which means no password is required, and any caller with a security
level of 43 or higher may open InfoDoor.


InfoDoor Commands Page 13


Sysop Commands
==============

When a remote caller has entered the door from PCBoard, both the
caller's keyboard and the sysop's keyboard may be used to enter
commands. In this way, a sysop can help a new user by actually
showing him how to use the door. This feature is only enabled when
the sysop's local display is enabled.

Display Toggle

The local display can be enabled or disabled by the sysop. When
disabled, nothing will be echoed to the screen by the door. The
F9 key on the sysop's keyboard toggles the display on/off.

On entry, the PCBOARD.SYS file is examined to determine if the
display was active prior to the door being invoked. If so, the
display is automatically enabled for the door. If the display
was disabled in PCBoard, it will remain disabled when the door
program is loaded.

The state of the display is maintained on return to PCBoard.
That is, if the display is on when InfoDoor terminates, then it
will be on when PCBoard reloads itself and visa-versa.

Other Sysop Functions

Many functions are available to the sysop via the local console.
When the display is enabled, a "PCBoard-like" status line will
be displayed. Press the HOME key to change this status line to
show the available sysop keys and the functions they provide.
The END key may also be used and will change the status line to
display the caller's registration information.

One function that is not displayed on the local status line when
the HOME key is pressed is the ability to dynamically alter the
caller's remaining time allowed. The UP ARROW key, when
pressed, will add 5 minutes to the time allowed for the current
call. Similarly, the DOWN ARROW key will reduce the caller's
time allowed for the current call by 5 minutes.

Local Testing

The InfoDoor may be run locally to test the configuration and
setup. Log onto the board locally, and invoke the InfoDoor just
as you would if you were calling from remote.

Main Menu Commands
==================

InfoDoor's menus are always shown to callers when they enter the
door. Expert callers can use the X)pert command to toggle the

InfoDoor Commands Page 14

display of menus off. This has no effect on the caller's Expert
status in PCBoard.

InfoDoor's menus, like those for PCBoard, reside on your disk as
normal text files (the names of these files are specified in the
InfoDoor configuration file). Both graphic and non-graphic
versions of the menus may be created (the names used for each
version follow PCBoard conventions).

A sample InfoDoor main menu appears below:

_________________________________________________________________________


Your Choices are:

E .... Enter keyword for search M .... Mode (Graphics)
H .... Help O .... Operator Page
X .... Expert mode on/off V .... View Statistics
Q .... Quit (Return to PCBoard) G .... Goodbye (Logoff)

_________________________________________________________________________

Each option from this menu is described below:

Enter keyword for search
------------------------

This command is used to initiate a search of the database. The
caller will be prompted to enter the keyword(s) that will be
searched for and, after entering a reply, will be asked to
verify the keyword(s) entered.

A keyword may be any string of ASCII characters (except | and +,
which have special meanings as described below). For instance,
if your database contains items relating to the Disk Operating
System, a caller might enter CHKDSK as his keyword. The
subsequent search would match all items in your database
containing "chkdsk" or "CHKDSK" or "ChkDsk" or ... in the
Subject Header. As you can see from this example, the searches
performed by InfoDoor are NOT sensitive to the case of the
keywords entered.

The special characters "|" and "+" are used as boolean
connectors and represent logical OR and logical AND
respectively. Thus, entering "CHKDSK | FORMAT" would match all
items containing either of the keywords "CHKDSK" or "FORMAT" in
the Subject Header. Similarly, the keyword entry "DOS + 3.2"
would match any Item containing both "DOS" and "3.2" in the
Subject Header.

Note that "+" has precedence over "|" so that an entry of "DOS +
3.2 | CHKDSK" will match any item with both "DOS" and "3.2" in

InfoDoor Commands Page 15

the Subject Header and will also match any Item containing
"CHKDSK" in the Subject Header.

Mode (graphics)
---------------

This command toggles the caller into and out of color graphics
mode.

Graphics mode will be denied to callers showing a connection
using anything other than 8 data bits and no parity.

Help
----

Choosing this option causes InfoDoor to display a help file to
the caller. The name of this file is specified in the InfoDoor
configuration file and may be customized to suit your particular
application or preferences.

Operator Page
-------------

This option allows the caller to page the sysop. The page bell
will be sounded at the local console only if it has been enabled
by the sysop.

The sysop may respond to a page with either the spacebar or with
the F10 key. Chat mode can be terminated using the ESCape key.

Xpert mode
----------

This option toggles the display of InfoDoor menus off/on.

View Statistics
---------------

This option allows the caller to obtain a display of various
PCBoard statistics relating to his board activity. Among the
statistics displayed are upload and download counts, security
level, last time on, last DIR scan date, and more. In addition
to historical information, the caller is also shown statistics
accumulated during the current call including bytes downloaded
and bytes still available for download.

Quit
----

Selecting this option returns the caller to PCBoard.


InfoDoor Commands Page 16

Goodbye (Hang up)
-----------------

Choosing this option causes InfoDoor to update all relevant
USERS file statistics for the caller, write logoff information
to the CALLER log, display the Logoff Message file, and drop
carrier on the caller.


Item Selection and Display Options
==================================

Following a successful search of the database (ie. a search that
results in one or more matches), InfoDoor displays its Item Display
menu. In addition to the commands described above for the Main
menu, several Item selection/display commands are available. A
sample Item Display menu appears below:


_________________________________________________________________________


Your Choices are:

E .... Enter keyword for search M .... Mode (Graphics)
H .... Help O .... Operator Page
X .... Expert mode on/off V .... View Statistics
Q .... Quit (Return to PCBoard) G .... Goodbye (Logoff)
====================( Item Display Options )====================
S .... Scan item headers A .... Display all items
# .... Select item for display ... Display next item

_________________________________________________________________________

Each Item selection/display option is described below:

Scan Item Headers
-----------------

This command displays the Subject Headers for all items matched
in the preceding keyword search. Each Subject Header in the
list is numbered so the caller may use this display to select
individual items (by number) for subsequent viewing.

Display all items
-----------------

This command each Item matched by the preceding keyword search
starting with the next sequential Item not already displayed
(e.g. if the caller has just displayed Item number 5, this
command's display will begin with Item number 6). If the last
item was just viewed, this command will start with the first
Item in the list (as shown by the Scan Item Headers command).


InfoDoor Commands Page 17

Select item for display
-----------------------

The caller can use this option to view an individual Item by
entering that Item's number (as shown by the Scan Item Headers
command). Item numbers may be stacked on the command line to
view several selected Items (e.g. entering '3 8 10 15' will
cause Items numbered 3, 8, 10, and 15 to be displayed).

Display next item
-----------------

Pressing the ENTER key will display the next sequential Item
(e.g. if the caller has just finished viewing Item number 6,
then pressing ENTER will cause Item number 7 to be displayed).



Acknowledgements Page 18


At this point in the documentation, I would normally list the names of
all of the people who helped in one way or another with the
development of the program. Unfortunately, a list such as that would
probably go on for several pages. Suffice it to say that I have
received assistance, advice, and support from many people. I would
like to thank all those involved in the development and testing of
InfoDoor and all who have contributed ideas, suggestions, and even
money to help make InfoDoor a useful and viable product. Without the
assistance of all of these dedicated people, I would have given up
long ago.

Special credit must, however, be given to a number of individuals who
have made major contributions to the development of this program.
My personal thanks go out to Paul Kopit, Dave Klein, and Robert
Blacher.

Thanks also to Phil Burns for publishing a wonderfully useful set of
communications routines, and to Fred Clark for creating the
environment under which InfoDoor executes.



Feedback Page 19


Please report any problems or difficulties in the use of this program
to me. I will attempt to resolve any and all trouble reports. I can
be reached on any of the fine bulletin boards listed below:

Software Society Sparta PCBoard
Sysop: Paul Kopit Sysop: Richard Driggers
(201) 729-7410 (201) 729-5377

Computer Connections PC-Rockland
Sysop: Robert Blacher Sysop: Charlie Innusa
(202) 547-2008 (914) 353-2176

Northern Lights Tamiami
Sysop: Jack Kilday Sysop: Gerhard Barth
(207) 766-2467 (813) 793-2392

Chuck's Attempt Software Society South
Sysop: Chuck Ammann Sysop: Dave Klein
(201) 729-2602 (201) 214-8896





rpb


  3 Responses to “Category : BBS Programs+Doors
Archive   : INFDOOR3.ZIP
Filename : INFODOOR.DOC

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/