Keeping in Touch
July 1992
SPITFIRE Monthly Support Newsletter for registered SPITFIRE Sysops
Compliments of Buffalo Creek Software
In this issue
- 1992 SPITFIRE SYSOP CONFERENCE
- SYSOP-OF-THE-MONTH
- NEWLY REGISTERED SPITFIRE SYSTEMS
Archival transcript
The text below is a faithful Unicode rendering of the original SF07-92.TXT. Its DOS line wrapping, spacing, capitalization, spelling and CP437 box art have been retained.
╔════════════════════════════════════════════╗
║ ╟─┐
║ K E E P I N G I N T O U C H ║ │
║ ═══════════════════════════════ ║ │
║ SPITFIRE Monthly Support Newsletter ║ │
║ for registered SPITFIRE Sysops! ║ │
║ July 1992 ║ │
║ Compliments of BUFFALO CREEK SOFTWARE ║ │
║ Buffalo Creek's BBS * 515-225-8496 ║ │
║ 38400/19200/9600/24400/1200 Baud ║ │
║ 2 Nodes ║ │
║ ║ │
╚═╤══════════════════════════════════════════╝ │
└────────────────────────────────────────────┘
Edited by Jacque Shipley
The Mother Board BBS - (515) 986-3464 - 19200 Baud
Sysop Of The Month by Walt Crede
Roam This Fertile Land - (515) 288-8755 - 2400 Baud
Newly Registered SPITFIRE BBS List by Ann Woltz
Other Contributions As Noted
╔═════════════════════════════════════════╗
║ Notes from the author of SPITFIRE! ╟─┐
╚═╤═══════════════════════════════════════╝ │
└─────────────────────────────────────────┘
SPITFIRE v3.2 QUESTIONS & ANSWERS
---------------------------------
QUESTION: When I boot SPITFIRE, I see the message which states
-------- '■ External protocol files path is C:\SF\EXTNOD1'
and then there is quite a pause before I see the
'■ Initializing system at 57600 baud.' prompt. Why
does SPITFIRE pause at this point?
ANSWER: SPITFIRE tests for a carrier detect immediately after
------ it sends the 'external protocol files path' message. When
a carrier is detected, SPITFIRE attempts to sever the
connection which causes the pause you are noticing. Most
likely, you have your modem configured to report a carrier
regardless of whether there is actually a carrier or not.
YOU DO NOT WANT YOUR MODEM CONFIGURED IN THIS MANNER for many
reasons. I take this opportunity to mention just a couple of
the problems this can cause. First, it can cause your modem
to choke on the init string sent by SPITFIRE. Second, if a
caller disconnects abnormally (not using <G>oodbye) SPITFIRE
will not realize that the caller is gone because your modem
will be reporting a carrier. YOU NEED TO CONFIGURE YOUR MODEM
TO FOLLOW THE STATE OF THE DATA CARRIER FROM THE REMOTE MODEM.
This is done by a couple of different ways. First, you modem
may have a dip switch which controls this. Second, the AT&C1
register normally controls this in most modems. I would suggest
that you boot your favorite terminal program (Procomm, Telix or
whatever) and at the OK prompt, enter AT&C1&W. You should then
see a second OK. I would also suggest that you have &C1 in your
SPITFIRE modem init string.
QUESTION: I keep getting 'SFCALLOG.DAT error' messages in my CALLERS.LOG
-------- file. I must have a buggy copy of SPITFIRE. Will you compile
me a new copy?
ANSWER: You do NOT have a 'buggy copy of SPITFIRE'. Rather, it would
------ appear that you did not follow the SPITFIRE v3.2 upgrade
instructions. You must put the file named SFCALLOG.DAT in your
WORK directory.
Buffalo Creek Software UTI
--------------------------
I have finally found the time to get the Buffalo Creek Software UTI
to a raw test stage this last week. It is not ready for release, however,
this is a giant toward release. Now, it is just a matter of testing and
fixing the problems found. It is currently being tested by a select few.
Once they are satisfied that it works, then I have a long list of Sysops
who have volunteered to beta test.
Until next time, may God bless you...
Mike, Ann & family
╒════════════════════════════════╕
│ 1992 SPITFIRE SYSOP CONFERENCE │
╘════════════════════════════════╛
1992 S P I T F I R E S Y S O P S C O N F E R E N C E
As has become the custom, the 1992 SPITFIRE Conference was kicked
off with a reception Friday night. Sysops mingled, conversed, enjoyed
refreshments and pizza. Saturday and Sunday were dedicated to presentations
on a number of topics that were of interest to the SPITFIRE Sysops.
Association Of Shareware Professionals
Presented By Don Hutson
--------------------------------------
As the Association of Shareware Professionals moderator on Circuitnet,
Don explained to the Sysops that only shareware authors can be voting
members of ASP. However, disk vendors and bulletin board operators may
become associative members. If you are interested, applications are
available on Linking Rings SPITFIRE BBS at 404-447-0036. By becoming
an associative member, the BBS assists in the promotion of shareware
products.
In order to become an associative ASP member and to become an ASP
BBS certain criteria must be satisfied. The BBS must have bulletins
available which explain the shareware concept and explain the function
of the ASP. Sample bulletins are sent to the Sysop when the BBS is
approved for ASP membership. The file listing on the BBS should use
the "<ASP>" logo to denote any programs by authors who are members
of the ASP.
ASP approved BBSs must not knowingly post for download programs
which would be illegally distributed if made available for download from
the BBS. This would include commercial products and/or shareware products
where distribution by the author is restricted. The contents of the
distribution package supplied by the author should not be altered in
any way without the author's permission. In addition, the BBS should
always strive to ensure that the latest version of ASP products are
available for distribution, removing outdated versions from the BBS.
To receive approval as an ASP BBS, the application must be filled
out an returned. If you wish to include your BBS in the ASP Approved
BBS listing a $40 certification fee is required. An ASP member will
log onto the BBS and determine if it satisfies the standards imposed
for ASP membership and notify the Sysop of their approval status.
Approved BBSs will enjoy the benefits of receiving the ASP newsletter,
receive the current version numbers of ASP member's programs free
from Compuserve or mailed to you for an annual fee of $30 a year,
the distinction of using the ASP Approved BBS on their BBS, approved
BBSs are listed in the ASP approved BBSs register, and ASP authors
are encouraged to send updated disks or uploads to the approved BBSs.
It should be noted that the any annual fees apply for the fiscal
year of January 1 to December 31. Therefore, any annual costs sent
now will again be applicable January 1st.
Backfire Call Back Door Verification
Presented By Steve Cox
------------------------------------
Steve Cox, from Live Systems Software, spoke on Backfire his call back
verification system. Many may recognize Steve and Live Systems Software
as the producer of Wildfire, a SPITFIRE door conversion program.
Backfire was first released at the SPITFIRE Sysop conference.
Today, more than ever, it is important for Sysops to protect ourselves.
Numerous reasons exist why we must know how is calling our BBS. The
opportunity exists for callers to upload virus infected programs, leave
"inappropriate" messages that we do not want made available on our BBS, and
those who in general produce a whole assortment of problems to us as Sysops.
The most effective way in terms of BBS control today is to screen
your calls through a call back verification program. A call back
verification program verifies that the caller is indeed calling from
the phone number that they entered when first logging onto your BBS.
The process involved in the call back verification is quite simple.
The caller is asked to verify the phone number which was entered is
in fact correct. The call back program then drops carrier and calls
the phone number back. The caller simply types in ATA from their
communications program and the connection is made. At that time,
the caller is prompted to enter their password. If the password is
entered correctly, the caller is considered to be verified.
It should be noted, that if the caller does make a correction to the
phone number during the verification process, Backfire will update
SPITFIRE caller's file, SFUSERS.DAT.
A number of detailed display screens are provided which give the caller
complete instructions through the verification process. Backfire requires
no special directories. It's display files use SPITFIRE's standard .CLR
and .BBS extensions and are placed in the SPITFIRE display file directory.
The screens which are included with Backfire, can be edited to your
specifications either with a text editor or with TheDraw.
In the configuration, Backfire gives the Sysop the opportunity to
configure whether Backfire will verify long distance callers. If you
elect not to call back long distance, you can specify whether the
long distance caller's security will be upgraded during this call
or you may return the caller to the BBS at their original log on
security.
There are three methods under which Backfire can be installed on your
BBS. The recommended method is the Sysop configurable command from the
Main Menu. It is also recommended that the Main Menu options available
for a new caller security level be limited to leaving a comment to the
Sysop, exiting the BBS or selecting the verification process. The
other options for installing Backfire are through the SFSEC<xx>.BAT file
or from the door menu.
Backfire goes to great lengths to prevent call back attempts to bogus
numbers. Internally Backfire will disallow verification for such numbers
that use area codes such as 800, 900, 911, etc. In addition, numbers
known to be bogus can be placed in Backfire's BADNUM.LST by the Sysop.
Backfire allows local logon testing by the Sysop. During local
testing Backfire will perform as if a new caller was being verified,
with the exception that it will not drop carrier and dial the respective
phone number. All other functions of Backfire can be tested in local
mode.
Other features of Backfire include full multi-node compatibility,
call back verification for up to 5 different security levels, optional
duplicate number checking, allows 3 attempts for the caller to enter
the correct password, attempts to call back the number 3 times if
there is no response from the dialed number or a voice result code is
received, works with either pulse or tone phone lines, works with comm
port 1 to 35, and allows full number ranging in the local number list
file.
Registration for Backfire is $20 for the single node version and
$25 for the multi-node version. Registration entitles you to full
support from the author and free upgrades in the future.
Steve mentioned that he has already begun work on the next version
of Backfire. The next version will include the ability to allow long
distance call back verification only during the times when calling rates
are lowest. Steve contributed two copies each of Backfire and Wildfire
as door prizes at the conference.
Midwestern Mail Network
Presented By John Miksich
---------------------------
John Miksich, Sysop of Midwest Horizons, spoke to his fellow SPITFIRE
Sysops on the Midwestern Mail Network. Midwestern Mail Network will
be the first public Firenet mail network. Firenet, SPITFIRE's own netmail
software is being co-authored by Mike Woltz and Bob Zimmerman. Firenet
will support netmail importing and exporting directly into SPITFIRE's
message base without requiring any conversion programs.
Applications are now being accepted for membership into Midwestern Mail
Network and they are anxiously awaiting the completion of Firenet to begin
the mail exchange. Applications are also available for anyone interested
in hosting a conference. The applications are available on Midwest Horizons
(515-225-6380) and Buffalo Creek's BBS.
The conference listing is now in the process of being formulated.
Anyone interested in Midwestern Mail Network and who would like to
request specific conferences is asked to contact John on his BBS.
Midwestern Mail Network will be supported by Regional Hubs, Statewide
Hubs and local nodes. John stressed the importance of local nodes
since it is the individual participation of the nodes that contribute
to making for a more interesting mail exchange.
Specific requirements are established for serving as a hub. Both
Regional and Statewide hubs must support a 38400 modem, have 10-15 megs
of disk space available which will be dedicated to the Midwest Mail
Network and be available for mail runs 24 hours a day. Nodes require
only a 1200 baud modem and enough disk space to handle the specific
conferences they are participating in.
A registration fee of $20 for a Regional Hub, $15 for a Statewide
Hub and $10 for the local node will be required. This is to offset
the cost of time spent setting up the network, long distance charges
and paperwork involved. After the initial registration a $5 per
year membership fee will be required by all participants.
Completed applications can be returned to John at the address on
the form. However, the registration fee should not be sent until you
are notified that Midwestern Mail Network is ready to begin the
mail transfers.
SPITFIRE For Fun And Profit!
Presented By Mike Thacker
----------------------------
Unlike most Sysops who operate their SPITFIRE bulletin board systems
as a hobby, Mike uses it to operate his business. Home Connections
BBS depicts a commercial application for SPITFIRE.
Mike has registered five copies of SPITFIRE, with more on the way.
Home Connections provides property listings which both buyer and
agent may access. For this application, Home Connections wanted a
bullet proof communications software. Mike reports that SPITFIRE
has more than met their needs.
The BBS has few messages and does not allow uploads. The files
that are downloadable are self extracting executable pictures of
the property listings. Customer and agent primarily access the
door section from which Home Connections operates.
Mike provided a demonstration of how the buyer can enter the
door and through multiple search criteria select properties that
are of interest. The multiple search criteria include price range,
features, whether the property is assumable, a specific school
district, number of bedrooms, number of bathrooms, etc. It is also
possible to exclude criteria from your selection. For instance,
in the demonstration condos were excluded.
Once the criteria is selected, Home Connections saves the caller
profile so the caller can easily search on the same criteria repeatedly
without having to rekey their selection. Of course, the option always
exist to change the criteria.
Properties listings which meet the criteria are then displayed to
the buyer. At the touch of a key, additional information is available
on each listing. The buyer can also signify whether he/she would like
a picture of the property and whether they would like to be contacted by
the agent in regard to the listing.
The agent uses Home Connections to list properties which are for sale
and is responsible for maintaining information for their property listing.
Maintenance might include price reduction, feature updates, and addition
of new listings. It is from Home Connections they can see which of their
properties have been accessed and receive receive leads (names and numbers)
of prospective buyers they can contact.
Home Connections serves as an advertising media for which the agent
pays for the service. Fees range from $75 to $95 for the one time
sale by owner listing to $95 a month for the real estate agent that
has multiple listings (usually 10-25 per month) on the service.
In response to questions, Mike explained Home Connections is a
franchise operation. The franchise is based on the population of the
area, costing $950 per 1000. The average franchise ranges from
$27,500 to $29,000.
Mike also noted that the software could handle accounting requirements;
invoicing and logging of receivables.
Because most of the BBS operators are sales personnel, they are not
always "computer literate". Therefore, Home Connections also offers
what it calls the Hero System. Hero System is the combined hardware
and integrated software package. The Hero System is designed to
simplify the computer use process.
The integrated package includes such programs as Carousel, Quicken,
Word Perfect, QModem and Contact. With Carousel, it is possible for users
to switch applications with one keystroke. Mike reports the applications
are quicker than under Desqview, since they are only running one
application at a time. QModem allows Home Connections the ability to
call into the customer's computer and offer support when problems arise.
Scripts are also provided so the user can call out to other systems
with little hands on required. Through the use of generic form letters,
the Hero System uses Word Perfect to print documents and envelopes with as
few as 3 keystrokes.
Contact Plus is designed for the sales person. Mike referred to Contact
as their "extended memory manager". It is a rolodex of names, addresses
and phone numbers with which the sales person comes in contact. It
has many indexing options which expedite the quick retrieval of
information. By entering a small character string, such as part of
the person's name, the information appears before you almost immediately.
It allows you to make one line notations or extended comments in
reference to the person (contact) with whom you are dealing. It also
includes a "tickler" section that will remind you of upcoming events
when the computer is turned on.
During the conference, Mike offered 2 copies of Contact Plus as door
prizes and reduced the cost to $199 for interested Sysops.
Circuitnet Netmail System
Presented By Steve Newman
-------------------------
Steve Newman, also known as "Mr. Circuitnet", began his presentation
by giving a brief history of Circuitnet. Originally written by Sean
Burbidge, the early days of Circuitnet began what Steve called a "stormy"
relationship with Mike Woltz. However, since that time Mike has worked
with the Circuitnet authors and even made changes in SPITFIRE to make it
Circuitnet compatible.
Circuitnet was first released a little over two years ago. There were
quite a number of problems with the original software program. Steve
became involved with Circuitnet about the time a purchase of the software
was negotiated by Clyde Brown and Harold Nemee. Together they worked
extensively to release a new generation of Circuitnet, version 3.04,
quite improved from the old Circuitnet.
Circuitnet now has approximately 240 registered BBSs participating in
its mail exchange. Steve reported Circuitnet is growing constantly and
has gained several international members. When first joining Circuitnet
Steve mentioned that he thought of Circuitnet as a message exchange among
the SPITFIRE Sysops but now finds Circuitnet is getting alot of participation
from the local BBS callers as well.
Those wishing to learn more about Circuitnet can download it from
from Buffalo Creek's BBS. The current version is CN311-SW.ZIP.
Recently, Circuitnet was sold to a young programmer, Dave Stahl, Sysop
of Quantum Leap's BBS. He too, is working on a new version of Circuitnet.
Steve shared a letter from Dave which outlined the future enhancements that
can be expected in version 4.0.
Dave began concentrating his efforts to correct past software design
flaws. The upcoming version will support message import/export compatibility
between version 3.11 and 4.0. Conference code names will be stored in
SFCONF.DAT to allow conference insertion and deletion. A third work
file MESSAGES.CNC will be added for sorting messages when exporting
packets and perform duplicate message checking. The dossier, which is
the list of available conferences, will be updated automatically by
the host, if it finds the date and time has changed. This will enable
all conference lists to be synchronized. All conferences will now have
a number which will allow for netwide addition and deletion of a conference.
Circuitnet has been updated to work with SPITFIRE 3.1 and 3.2 rather than
3.0 and 3.1. The future version of Circuitnet will provide corrupted
header message checking by blocking out specific ASCII code characters.
Dates and times are checked for validity and will be replaced with the
current date time if found to be invalid. To speed the process, the
primer no longer checks for old messages while priming. SPITFIRE control
codes are stripped from the messages. Sysop All messages are now
restricted to Sysops and only available in the registered version. EMS
and XMS memory is now utilized to increase the speed of Circuitnet.
A text file user filter will be used to prevent messages from being
received by persons who are listed in this file. There are also plans
to allow file transfers with the mail exchange.
As you can see Circuitnet V4.0 promises to offer significant improvements
over the existing program. It should be mentioned that Circuitnet offers
free upgrades. Dave Stahl contributed a copy of Circuitnet for a door
prize at the conference.
BETA TESTING
Presented By Ira Lichtenstein
-----------------------------
There are initially three stages which a software product normally
goes through before it is released to the general public. First, is
the program development, followed by alpha testing and finally beta
testing. Beta testing is defined as prior evaluation and scrutiny
of software in development by the author and select others for the
purpose of perfecting a program before it is released. Authors
and beta testers have a unique relationship and must be able to
rely on each other. Together the author and the beta testers strive
to achieve an error free product by the time it is released.
The author begins by determining a need for the software application.
Once a purpose for the software is established, coding is written to
accomplish the desired task. It is at during the development phase that
the author must make decisions regarding what language the program will be
written in, any shareware limitations if it is to be released as shareware,
what price will be charged for the finished product, etc.
Alpha testing usually consists of the author doing the initial
testing of the program. Often, the author will use debugging code
during this phase to track down any known problems which might exist.
As the alpha testing nears completion, the author will usually begin
a rough draft of the documentation to guide the beta testers through
use of the program and begin to consider the selection of beta
testers.
One might ask, why does an author need others to assist in testing
their product. Perhaps most significant is hardware configurations.
Selecting beta testers will allow the software to be run under conditions
which the author is unable to duplicate. In addition, beta testing allows
the author to gather feedback from testers regarding problems they are
having and which the author might not have considered when originally
writing the software. The beta testers can also give suggestions for
enhancements while the software is still under development.
The author must be selective in determining who will test the
software. Too few and possibly not all the problems will be found, too
many and the author might not be able to keep up with all the feedback.
Testers chosen inappropriately may provide no feedback to the author at all.
The author should carefully determine the criteria and the minimum
competency level for the testers and their operating systems, as well as
examine what the tester can contribute to the development of the program.
The author and the tester should develop and ensure a level of trust
between each other.
Some authors will require a non-disclosure agreement with the beta
testers. One reason this is done is to prevent the tester from discussing
or revealing information about the product. If other authors hear about
the program, they may duplicate the program and destroy the market for the
original author. Or the author might decide to remove a feature implemented
in the beta version. If word has already "leaked" on the new feature and
prospective users of the software are expecting it, the author might be
faced with ill feelings unnecessarily. Announcing problems that occur
during the testing phase could possibly damage the author's reputation.
Another reason for such agreements is to protect against pirating of the
software.
There are both pros and cons to being selected as a beta tester.
As a beta tester, you have the opportunity to contribute to the
development of the program. You should never elect to beta test a
product for the simple reason of being able to run the latest and
greatest version of the software. However, that is one of the benefits.
As a beta tester you gain "bragging rights" and having these enhanced
versions of the software makes your BBS more attractive to callers.
There is the opportunity to make new friends and most often, the author
will provide you with a complimentary copy of the software you are testing.
However, when you agree to beta test you are assuming a responsibility
to do just that, TEST, not just run the software! Beta testing can be
expensive. There can be numerous long distance phone bills as you
continue to download updates of the program and report the results of
your testing back to the author. Beta testing can require a great deal
of time, as you put the software through the extensive paces of testing.
Beta testing requires you to examine the program carefully, utilizing each
and every feature available in the software. And if problems are found,
you must be willing to work with the author to resolve the problems you
discover and report. It is even possible, beta testing can lead to
hardware failure, the system may hang or even crash.
When beta testing, you should BACK UP your system often! A tape drive
is an essential tool in the tester's arsenal. And you should always
keep a copy of the latest version which you know to have worked with
little or no problems! Know your system. If you have components that
could possibly fail, refrain from testing at this time. It is not fair
to the author if in the middle of testing you are forced to abandon
the project because of expected hardware failure. Report back to the
author. The author needs to know how the testing is progressing and
relies on your feedback. If you discover what you consider to be
"bugs" in the program, make sure the problem is with the software.
Eliminate the possibility of the "bugs" being generated from another
source. If the program does have a problem, you should be able to
duplicate it. Report the problems thoroughly to the author; giving a
full accounting of the circumstances under which the problem is encountered
and any errorcodes the program may generate. Be prepared to work with
the author until the problem is fixed. Offer to assist the author with
the documentation so his time can be devoted to the program.
Always remember you are running someone else's program and they set
the rules. It is not your job to advise the author how to write his
program. However, many authors will be receptive to valid suggestions.
If you do offer a suggestion, don't be offended if the author chooses not
to implement it. Keep in mind, it is always a good idea to limit beta
testing too many programs at one time. If something goes wrong, you want
to be able to identify what program is responsible for the problem. If
you are testing several programs at one time this can be difficult at best.
During testing, again, the important thing you can do for the author is
thoroughly test the program, not just run it, while the most important
thing you can do for yourself is make frequent backups!
As the tester has responsibilities to the author, the author also has
responsibilities to the testers. Thank the testers for their assistance.
Testers are providing the author with an important service. Authors
should be patient if a tester doesn't understand all the intricacies
of the software and possibly their own hardware. In the vast field of
computers we can all learn from each other. Testers are often the
best advertisers and endorsers for your product. Acknowledge the
testers in the documentation to show your appreciation for their efforts.
Even after the program is released, maintain contact with the testers.
They have been running the software longer than anyone else and can still
provide valuable feedback. In addition, they can serve as prospective
testers for future projects. When possible, offer a complimentary copy
of the program as a gesture for offsetting the expenses they have incurred
during the testing period.
In conclusion, the author/tester relationship is crucial in the
development of software products. If a program is tested inadequately,
problems will undoubtedly arise after the software is released. It is
always better to ensure the testing has been thoroughly completed, even
if it means detaining the final release.
RomPro - CD Rom Door
Presented By Steve Cox
----------------------
Steve usually makes it a standard practice not to preview his programs
until they are ready to be released. However, he is admittedly quite
excited with his newest product, RomPro, a CD Rom door. Therefore, he
made an exception and treated the Sysops attending the conference.
CD Roms are revolutionizing the world of BBSing. Most of us can
probably remember the massive file searches we underwent in order to
accumulate an adequate file assortment for the initial startup. Chances
are you downloaded thousands of files and paid some enormous long distance
charges in order to start the BBS. With CD Roms this is no longer
necessary. A Sysop starting out today, in a matter of minutes, can have
thousands of files available by adding a single CD Rom to their system.
And probably for less than the phone bills paid by us pioneers.
Today CD Rom drives and platters are cost effective and becoming
more and more economical. Just compare costs between a CD Rom and a
hard drive of equal storage capacity. There are other advantages too.
Virus protection for instance. Although, you can not be guaranteed 100%
that a CD Rom will be virus free, its producers are extremely careful
about selecting what will go on the disk.
After acquiring a CD Rom for his BBS, Flite Line, Steve began to
search for a CD Rom door. He did not want the CD Rom file listing to
be merged with his BBS file listing. Primarily he was concerned with
the maintenance that would be required. If the CD Rom platter was
ever changed, the amount of maintenance to the file listing, cutting
and pasting of the text files, would be a tremendous undertaking. So,
unable to find such a program, Steve came to the conclusion he would
write a CD Rom door.
So began RomPro. Although developed for his own use, Steve now
has a RomPro, currently in alpha testing, which will soon be available
to SPITFIRE Sysops. RomPro is designed to seamlessly integrate with
your BBS. It will allow the Sysop to change platters, make available
the database listing of files for the new platter, and have it online
and ready for your callers within a matter of minutes.
As part of the RomPro project, Steve is working with CD Rom
manufacturers to obtain file listings of existing CD Roms. These
"ready to go" file listings will be available for download to registered
users of RomPro. Plans also include that future versions of RomPro will
contain a compiler that will Sysops to create their own file listing from
the CD Rom. The database file listings are Isam driven for speed. Each
word in the description (with the exception of the, and, or, etc.) are
indexed as a keyword. RomPro's keyword search option allows callers to
quickly locate files matching their keyword criteria.
RomPro can be ran as a SPITFIRE door or from SPITFIRE's Sysop configurable
command option of the File Menu. RomPro comes with a complete menu system
which is totally configurable by the Sysop. RomPro is designed to work with
a single CD Rom drive or with up to four chained six pack CD Rom drives. In
other words, you may have from 1 to 24 CD Rom drives accessible through RomPro.
Options from RomPro's menu provide the capability of viewing and/or
downloading files contained within a ZIP file. Callers may elect to read
files online. If a multiple CD Rom system is available, callers can change
from one volume listing to another and even select files for download from
any of the available CD Roms at one time. RomPro supports file tagging
and allows files to be tagged individually or by specifying a range. File
transfer protocols, including ZModem, are built into RomPro, so all
CD Rom activity can actually be completed from the CD Rom door itself,
totally independent of SPITFIRE.
Although Steve admits you can not always trust an author's projected
release date, the target date for the release of RomPro is August 15th.
It will be available in single node version for $30 and multi-node version
for $45. In conclusion, whether interested in RomPro or not, Steve
noted every Sysop should consider adding a CD Rom drive to their system.
LEGALITIES OF BBSING
Presented By Bruce Wilson
-------------------------
Bruce Wilson, local Des Moines attorney and co-Sysop of Sirus BBS,
spoke to the Sysops on the legalities involved in BBSing. There are
a number of legal issues that relate to operating a bulletin board
system that, as Sysops, we should be aware of. It is only through
knowing our responsibilities that we can protect ourselves from
possible court actions.
In 1986 the ECPA (Electronic Communications Privacy Act) expanded
upon the existing federal law which made wire tapping illegal. Thus
the prohibition against interfering in private oral communication
between individuals was applied to electronic communication. And
more specifically to bulletin boards.
The most notorious litigation to arise from this act was Thompson
vs. Predaina. Linda Thompson, a Sysop and law student, sued Bob Predaina,
alledging multiple violations of the privacy act. Her accusations
included that private messages she had entered to others on Predaina's
BBS were made public, messages were deleted and then undeleted and made
public. Needless to say, this suit created quite a stir in the BBS community.
As a result, Predaina filed bankruptcy and the suit was stayed. Thompson made
not attempt to have the stay lifted and it was ultimately dismissed. Both
sides claimed victory despite the fact that no decision was ever reached.
In this arena there remains a lot more questions than there are
answers. It is through court decisions that answers are provided and
so far there just hasn't been any to speak of. Therefore, the
interpretation of the law is still debatable.
However, if you do not desire to become the precedent from which the
court decision will come, the best rule to follow is private means
private! Anything not public, including SPITFIRE's non-public message
conference, should be considered private. And any activity you perform
on a private message could lead to possible problems in regard to the
privacy act. Most importantly, NEVER disclose a private message which
is an exchange between two other individuals! Only, if you are the
sender or the intended recipient can you disclose the contents of a
private message, making it public.
What responsibility does the Sysop have in acting on a private
exchange between two individuals that are using the message base where
the contents of the exchange are libelous or profane? Can the Sysop
be held responsible for deleting messages before they reach the intended
recipient in a private exchange? What about netmail systems that will
sometimes strip the privacy flag on messages? These are just a few of
the questions raised during the presentation. The typical privacy act
disclaimer most boards post may not be enough to protect you. What Bruce
recommends to minimize potential problems is full disclosure. By that,
make sure the callers to your BBS knows what will happen and how it works.
If certain standards of behavior are expected, inform the callers and let
them know of the consequences; for instance, that you reserve the right
to delete "inappropriate" messages.
Is it enough to post a notice acknowledging the terms and conditions
under which the Sysop will act of messages? Bruce noted that the best
protection would be a signed affidavit from your callers agreeing to the
terms you define in regard to any action the Sysop might take while
monitoring the message base. Although BBS questionnaires could be used for
this purpose, it offers little or no protection. Bruce admitted, as a
lawyer, he would love to challenge the admission of BBS records as
evidence in a litigation. Data files are too easily altered and even
the time/date stamp can be changed with little effort. Therefore,
to prevent the possibility of any legal actions the Sysop should
either take a "hands off" approach or require their callers to mail
in a signed form in which they agree to the terms defined by the Sysop.
Bruce also noted a concern with the increase interest of including
within SPITFIRE the ability to edit messages. Editing messages creates
a new potential for running afoul of the privacy act. Rather than
edit the message, he recommends letting it go through "as is" or simply
deleting it.
Sysops should also make an effort to become informed of any state
laws that might affect the operation of their BBS.
Most Sysops are aware that having commercial programs available
for download is in violation of the law. A BBS can only make public
domain and/or shareware programs available for download. If commercial
programs (also known as "pirate" files) are available for download the
Sysop risks confiscation of their entire system. The forfeiture act allows
any property being used in illegal activities to be confiscated by
authorities.
Another area with which Sysops need to be concerned are GIF files.
GIF files have the potential of violating the law in two ways. The
first being if the GIF contained material which could be considered to
be pornographic. The other being that the GIF may be copyrighted material
which you are not authorized to distribute. Copyright law allows a person
who creates a work rights to that work and all derivative works that
are created from it. Examples of this might include GIFs of logos or
even more specifically Walt Disney cartoon characters which are trademarks
of Disney Productions.
The question was also posed as to whether Sysops have any liability
if a caller downloads a file from their BBS and it is found to contain
a virus. Again, Bruce echoed that Sysops should protect themselves
by posting or requiring a signed form that discloses the Sysop assumes
no responsibility for files downloaded from the BBS and the caller
downloads and uses them at their own risk. Lately, it has become a
common practice for Sysops to makes reference to the fact that files
uploaded to the BBS are checked for viruses or that all files available
for download are virus free. By doing this, the Sysop is assuming
responsibility. In relation to a Sysop's legal responsibility, it would
be best not post claims regarding virus checking.
Although much of the Sysop's realm of legal responsibility still remains
undefined, Bruce concluded by reiterating the fact that the best means the
Sysop has to protect his/herself is full disclosure. Bruce also added one
consoling fact for the Sysops; that being most litigations will involve the
big boards. Most of us would be considered "small potatoes" and rarely will
any actions be brought against the local BBS as long as the Sysop acts
responsible and makes the callers aware of the conditions under which the
Sysop will take action if the terms are not met.
Future Conferences, SPITFIRE Support and SPITFIRE 3.3
Presented by Mike Woltz
-----------------------------------------------------
Mike began by asking some general questions in regard to the SPITFIRE
Conference. How can it be improved? Was it worthwhile? Should it
continue to be hosted in Des Moines?
Two years ago, it was mentioned that perhaps the conference should be
held in other locations. The proposal was made with the intention of
freeing Mike and Ann from all the work that accompanies preparation and
hosting of the conference. If the conferences were hosted by groups of
Sysops in various locations, all anyone else would need to do would be to
just come and enjoy the conference. Initial plans were made to have a
SPITFIRE Sysop conference in another location. However, as it progressed
Mike found he was being relied on to assist in the preparation of the
conference and that it was quite difficult because it was in another city.
Mike mentioned that airfare to another city, as well as room rates
might be less expensive than in Des Moines. It was suggested that Mike
make available a reference guideline of what was involved in hosting a
conference so that it could be used by Sysops who wished to do this.
In response, Mike remarked quite honestly that he wasn't sure if he
know how and that is in essence what he was trying to determine. Is
what they are doing okay. Mike expressed a genuine concern that he
hoped that Sysops found it beneficial and enjoyable and that know one
found themselves thinking it a waste of time and money.
It was pointed out that the conversations and new friendships made
it worthwhile, anything beyond that was an added bonus. Steve Cox,
who has spoken at a number of BBS conferences, interjected that the
more well known the city the more Sysops who are likely to attend. But
as the conferences start to get bigger you loose the element of friendliness
that permeates the SPITFIRE conference. He also noted that it is a
common practice with other BBS software conferences that it be hosted
in the author's city. Other Sysops noted that larger cities create
more distractions and that it makes it more unique to come to the home of
SPITFIRE.
The general consensus was that they would like to see the conference
continue to be held in Des Moines. And if possible, the conference
should continue to be held during the Twin Rivers Festival. Quite by
accident, the last two SPITFIRE conferences were held at the same time
as the Twin Rivers Festival. The festival provided entertainment to
family members while the Sysops attended the conference.
Suggestions were made that the conference, in addition to the
general presentations, have workshops on various subjects. Sysops
could then break into smaller groups and attend "how to" workshops that
were of interest to them. Ideas for workshops and speakers at the next
conference included Circuitnet, Fidonet, MacAffee virus scans, file
compression, TheDraw, and modem manufacturers.
Another suggestion that was well received was that the traditional
Friday night reception be held outside. That a park be reserved and
include a cook out. A number of Sysops volunteered to help should
this be included in the agenda.
The next topic Mike discussed was support of SPITFIRE. Mike has
give alot of thought recently to the possibility that SPITFIRE is
outgrowing its existing means of support. He has contemplated contacting
various people in various locations to draft up some of their most
commonly asked questions. Mike would then answer the questions and
make it available in a text file or pamphlet. Regional support sites
would be selected and the question and answer booklet would be available
to these support sites. As new questions arose, these would be forwarded
to Mike and he would continue to add to the existing question and answer
file.
Sysops interjected that a number of them are basically doing that now,
helping others when they can. Mike agreed but also added meaning no
disrespect to anyone, he has seen a number of times in the netmail
conferences when someone who was genuinely attempting to help another
Sysop passed on incorrect information. By making the questions and
answers available and regional support sites, he hoped this would cease.
It was suggested that the questions and answers be made available to
everyone and that it might even be included in the distribution package.
Although everyone liked this idea, they also agreed that all too
often answers are contained in the documentation if one would just
read it, so what makes one think that another book would be referenced.
It was also suggested that a flowchart be created map anticipated
problems.
Mike voiced fears he has in relation to adopting a new means
for supporting SPITFIRE. One being that despite all efforts nothing
would change. If someone has to call long distance to obtain support
from either the regional support board or from Mike, most often, they
will want to speak directly to the author. The only advantage of the
support board, is that it might be more accessible. Mike is also
concerned that if regional support boards were organized, Sysops might
get the impression that he is unwilling to support SPITFIRE. Mike
currently receives approximately 40 to 50 messages each day from Sysops
which require his attention. This is a real concern that prompted
Mike to consider some alternatives because as SPITFIRE grows so will
the time he dedicates to offer support. Another fear is selecting the
right people to assist in offering support.
Mike asked the Sysops to continue to think of ways that might be
implemented to better support SPITFIRE in the future.
Next and final topic of discussion for Mike was upcoming plans for
SPITFIRE, possibly version 3.3. Mike has already added a filter
which would prohibit new callers being entered into the SFUSERS.DAT
with strange ASCII characters. More than likely you have had a new
caller log on and when prompted to enter their name, a burst of line
noise fills the screen and suddenly you have a new caller that you
can not identify. Mike now uses a filter to test for these strange
ASCII characters and if found, the caller is again prompted to enter
their name.
SPITFIRE version 3.2 included an option which would allow messages
to be copied or moved. However, moving a message from a non-netmail
conference to a netmail conference provides no opportunity for flagging
the message as a netmail message. A prompt will be included which will
ask if you want the message marked as netmail in the future.
The question was asked whether Mike had any plans to include a full
screen editor in SPITFIRE. Mike responded that he has approximately
two full years of plans for SPITFIRE and although he would not say it
would not happen, it is very low on the priority list. The trend today
is that more and more messages are handled by offline readers. Because
of this, Mike feels that at this time it would be a waste of code and that
his time would be better spent on other features he has in mind.
Mike continued by saying that in the future he plans to remove the
SPITFIRE door option from the Message and File Menus, so that the Door
Menu will only be accessible from the Main Menu. In the Message Menu,
plans are to replace this option with a 'door' in which the callers will
have the ability to download (import/export) messages in the QWK format.
This capability would not be handled by SPITFIRE but rather a separate
assembler program Mike would include in the SPITFIRE package. When
this option was selected, SPITFIRE would then shell to the accompanying
program and execute it. Plans may even include expanding this to
provide a complete mail system which would allow Sysops to exchange
mail with other bulletin boards.
Needless to say, this was well received by the attending Sysops!
The question was raised whether Mike had any plans that included
removing SPITFIRE from memory when the "K" (Sysop configurable) option
was selected. Mike responded that he certainly is not married to the way
this is handled presently but also remarked that he generally feels that
he is giving Sysops the best of both worlds now. If the extra memory is
required, the door option is available. When the Sysop configurable
command was included in SPITFIRE, his intention was that it should appear
to be an extension of SPITFIRE and the caller would think it to be a part
of SPITFIRE. If SPITFIRE is removed from memory, SPITFIRE then must be
rebooted and the overall affect is more cumbersome.
There was a suggestion that a RAM drive be used for node chats. Mike
agreed that this is a possibility worth exploring. Currently the text
files which contain the chat text are on the physical drive and using a
RAM drive would be quicker. He said that that information (path of the
files on the RAM drive) would need to be stored somewhere. He would need
to check the existing or even possibly revise SPITFIRE's record structure
to allow this information to be stored should this be implemented in SPITFIRE.
In regard to node chats, Mike noted that he has the capability of
adding a netbios node chat as well. But because of time limitations
there is only so much he can do. The question was posed to the Sysops
whether this is something they would like added to SPITFIRE or whether
they felt it was more important to add other features that might better
serve the vast majority of SPITFIRE Sysops. Overall, attending Sysops
agreed that they would much prefer the QWK mail feature over improvements
to the node chat.
Virtual Reality or Virtual Nightmare
Presented by Steve Cox
------------------------------------
Steve began by providing Sysops with some background information
on himself. Steve's BBS, Flite Line, and his programming of such
products as Backfire, Wildfire and RomPro started out as a hobby.
Since that time, they have become a part time business. However,
in his real career, Steve is the Director of Research and Development
of a large firm in Lincoln, Nebraska that develops commercial software
for college bookstores all around the world.
This career provides Steve with the opportunity to travel all over
the United States looking at new types of development in technology
that most people don't ever get a chance to see. In fact, Steve reports
he sees alot of things that most people are not even aware of.
Most people never give a thought to how what we are doing today is going
to affect society tomorrow. Steve admits he spends alot of time thinking
about the new technology he has witnessed in the laboratories and
wonders what is going to happen with 2, 5, 10, 15, 25, even 50 years
from now when what is in development today becomes an integral part
of our society. Sometimes the results of thinking of this becomes
really scarey. Which brings us to the topic of discussion today,
Virtual Reality or Virtual Nightmares?
Now, everyone has within the last year or two heard the expression
virtual reality. Virtual, defined in terms of a computer, simply means
making something to appear to be something that it really is not. Virtual
memory tricks the computer into acting as if it has more memory than it
really does. Believe it or not, we can do the same thing with our minds.
In the laboratory of Cal Tech today there exists a little device
called a neuro chip. This stands to have more impact on the human race
in the next 25 years than any single development in a laboratory that has
ever been invented. What the scientist of Cal Tech have done, is invented
on silicon the actual equivalent of a human brain neuron. The neuron is
what makes everything happen; it is the basic building block that determines
how you think, how you learn and how you remember to do the things you do.
The difference between the neuron chip and the memory chip is that the
memory chip is digital, having 2 stages, on and off. In comparison the
neuron chip is an analog chip which means that it has an infinite variable
number of states it can be in. Now we have "maybe" conditions in computers.
That has always been the basic separation between a computer and the human
mind. Until now, computers have never been able to make maybe decisions.
In addition to the neuron chip, IBM has created a micro pump, also
known as a micro motor. This is an actual electric motor on a tiny silicon
chip no larger than the head of a transistor. Most applications are
anticipated to relate to the medical field. The self-powered micro motor
could be embedded in the arteries and blood vessels to assist in pumping
blood through the body. Today the micro motor is the size of a head on a
transistor, tomorrow they will be the size of a head on a needle.
For the first time, we are developing electronic technology that is
implantable in the human body. Implantable electronics which are capable
of replacing parts within the human body and the human mind. Keeping
this in mind, we should move onto the topic of virtual reality.
Can anyone say that their life is unequivocally and without a doubt
100% the way they wanted it to be? All of us would like to make
improvements or do things differently if we could. Suppose you had
the opportunity to be everything you ever wanted to be. Would you do it?
How many have ever had dreams about being able to fly? Do you remember
how hard it was to get off the ground and how exhilarating and wonderful it
felt when you could actually fly? Remember how great this felt, the
ultimate achievement and nothing in the world could be better than how you
felt at that particular moment. If you could feel that way all the time,
would you do it?
Virtual reality is a mechanism which today is still in its infancy.
By virtual reality, we refer to tricking your mind either by computer or
some other technology into believing it is doing something that it is not.
Have you seen the television demonstrations on virtual reality where the
scene, as far as the brain could tell, appeared very real. The virtual
reality of today is crude at best. But imagine a future where virtual
reality creates illusions, so lifelike that what you are witnessing appears
to be real even when it is not. An example of what you might see virtual
reality develop into, say fifty years down the road, would by the Hollowdeck
on Star Trek. The Hollowdeck is a true manifestation of virtual reality,
where you can be anything, do anything, go anywhere. If virtual reality is
not controlled the Hollowdeck will become a reality.
Next you must ask yourselves, is this something we really truly want
to happen? One thing we, as human beings, have almost never been able
to do is to examine the long term affects of what we do on the future.
Human beings, as a race, hardly ever exercise caution. It is either full
speed ahead or a dead stop. An example of this, would be the affects
we have had on our environment. Only when it reaches a point where it
becomes dangerous do we do anything about it. But what if by then it is
too late?
There is no question virtual reality could be a great boon. Doctors
could use it for training. They could practice delicate surgeries until
they get it right. Far better mistakes be made in practice than on patients.
Airplane pilots could simulate various flying conditions to gain expertise
required to fly new aircrafts. These are only a few applications for which
virtual reality could be applied. But what happens when this kind of
technology goes out of control. Human beings are very lax at controlling
anything.
Now, think about the consequences of what we do. One of the things
typical of the human race is that we can become addicted to almost anything.
Why do we become addicted? Because it feels good. Now reconsider the
question that if offered the chance to become everything you ever wanted to
be with no consequences, if only for a few minutes, would you do it? It
might well begin as a weekly 15 minute session at the virtual reality machine.
But if the human mind is so addictive think what might happen. The once
weekly sessions increase to two, three, four times a week and so on. If
you can anytime you want, be anything you want through virtual reality it
is inevitable that a certain percentage of the population will become
addicted. They will continue to rely on virtual reality because they either
do not feel good or are unhappy when they are not in a state of virtual
reality. What happens when virtual reality is better than real reality
and you don't want to come back? If uncontrolled, certain elements of
society will spend their entire lives hooked up to a tubes and a computer,
flat on their backs in a mortuary like environment, living only in a state
of virtual reality.
The human mind is so addictive that technology can take over and make
you believe that you are something that you are not. And many, many
people will become addicted. The technology exists today electronically
to develop implant technology where actual computer interfaces can be
installed in the human body. By implant technology, we mean a little
device implanted in the brain. Suppose the implants become required by law,
perhaps at birth, like the immunization shots of today. And when you choose
or need to communicate with the computer the installed device is triggered.
Do you really think this will not happen when we are developing neuron chips
that react and think like a human mind and micro motors that fit inside
arteries? Do you really believe we will not develop implant technology?
Envision that if uncontrolled, people, at will, summoning a visit into
virtual reality. Click and you are in another world, another time, another
reality where you can be anywhere, do anything, be anybody at will. We are
developing the technology that could well lead to the extinction of the
human race. What happens when this is carried out to the logical conclusion
in which there is no one left that lives in the real world. The entire human
race is hooked up to a machine. That is how we talk to one another, how we
react to one another and if we don't like how we react to one another we can
simply recycle the program and make it anyway we want, anytime we want. How
long can the human race exist like that? In a condition where everyone is
hooked up to a machine and no one knows who is real and who is not real.
How do you know that what is happening is real? The human mind does not
have the capability to determine what is real and what is not. What happens
when no one knows who is real and who is not. What happens with the birth
rate? Virtual reality does not have the capability of producing offspring?
What happens when the day comes that everyone is hooked up to a machine and
there are no more babies being born because no one knows who is real and who
is not. One day, nothing exists but the machine that everyone else used to
be hooked up to.
And why? Because we did not control our own technology. We let it
run rampant. We did not control it, we did not examine the ramifications.
We did not think of anything except the immediate gratification of how good
it felt. And now it is all gone.
Why project what might happen in the future? Why think about this
kind of thing. Because, as Sysops, we make these kind of things happen.
It is all of us. We do not ask enough questions. We don't pay enough
attention to the things we are using, the things we are doing and we
don't care about what happens to the future generation of our society
because of what we do today.
The whole point of this presentation, is to ask you to do one thing,
every single time you use a computer, every single time you read an article
in the paper about the neuro chip, every time you read a book about a
micro pump. Your first reaction will be that this is great. But at the
same time, ask yourself what can happen if this goes out of control? Let
your mind go free while today your mind is still your own. Take a flight
of fantasy into the future and what might it be. Scare yourself. Develop
a sense of examining. And ask what you can do as an individual to ensure
that this scenario never happens. Examine whether this is something, which
if left uncontrolled, that you really want to happen?
ATTENDEES OF THE SPITFIRE SYSOP CONFERENCE
Sysop Board Name Board Number
------------------------------------------------------------------
Mike & Ann Woltz Buffalo Creek's BBS 515-225-8496
Mary & John Krone I.C.I.X. 815-459-0825
Tim Gibson Byron Connection 519-453-4686
Steven Frantz Hug-64 419-423-6648
Kevin Turk The Turkey's Roost 713-530-7505
Dave Clark Fremont Arsenal 913-266-0067
Seam Fahey Shenanigans BBS Private
Scott Reigle Farkem Asylum 913-273-2589
Armand Michaud Cambridge Micro 519-621-0561
Chuck Eisenmenger Inside Info 519-756-8079
James Jones Jr. N2EHM Remote BBS 609-894-4366
Jacque Shipley The Mother Board BBS 515-986-3464
John & Diane McConnell One Oh Wurst BBS 615-648-0021
Mike Thacker Home Connections 404-447-0036
Don Hutson Linking Rings SPITFIRE 318-442-5694
Linking Rings Christians 318-448-9264
Bob Wolf The Wolf Den BBS 513-791-9020
Pat Stenberg Chicago Megaphile 312-283-4035
Ira Lichtenstein Sing Sing Sing Studios 914-941-2246
Chris Kuchma Nite Chills BBS 402-934-4924
Josh Stortz The Backup BBS 712-323-0462
Jake Kirkpatrick The File Cabinet 402-498-9505
Dennis Kostora Seldom Seen Data Line Private
Brian Pressler The Dark Avenger 319-264-0013
Dale & Louise Focht Kachina BBS 602-247-5521
Alan Boelter The Photo Club BBS 515-224-2054
Brian Carlson The Chicken Coop BBS 708-658-1545
Jay Jackson Test Pattern BBS 416-890-2531
Mike & Valli Redman See-More BBS 417-738-4341
Steve Cox Flite Line BBS 402-421-2434
Jason Spong Viper 515-225-1773
Doug Vangorp Dutchman's Cove 515-255-6078
Carl Villasenoi Prudential BBS 612-553-5702
Matt Carlson The Chicken Coop BBS 708-658-1545
Frank Crispell The Rocking Chair Connection 408-244-4250
Randall Hubbard The Hub BBS 405-536-2616
Harry Aller Norwalk Highlands 515-961-0729
Rick Dearbeck The Animal Farm BBS 904-387-0709
Chuck & Gay Dearbeck The Bad Attitude BBS 814-864-1230
John & Mary Butler Twilight BBS 515-284-1418
Stan & Derek Motloch The Computer Room BBS 519-659-7921
LeJean Dennis Silent Whisper 507-454-7787
Dennis Haase CIS BBS 507-454-7386
Steve Newman Columbia SPITFIRE 503-397-6040
Curt White Abort, Retry, Fail? BBS! 402-292-8290
Bruce Wilson Sirus System 515-224-8947
Robin Thibodeau The Max! 203-793-0471
Don Mortenson The Dark Side 309-787-6943
Sparky Sheppard Sparky's BBS 402-332-4740
Dean Langholz Blastoff BBS 402-551-8587
Jeremy Frum NIAS 402-556-5253
John Miksich Midwest Horizons 515-225-6380
It is interesting to note that there have been ten Sysops which have
attended all three SPITFIRE conference; October 1989, June 1991 and
this year's June 1992. They include Mike and Ann Woltz, John and
Mary Butler, Armand Michaud, Mary and John Krone, Steve Cox, Jacque
Shipley and Ira Lichtenstein.
DOOR PRIZES THAT WERE GIVEN AWAY
AT THE SPITFIRE SYSOP CONFERENCE
June 12-14 Des Moines, Iowa
Door Prize Contributor Winner
---------- ----------- ------
2 SFTOPTEN.............Buffalo Creek Software ASP Author...Steven Frantz
Sean Fahey
2 SFLASTEN.............Buffalo Creek Software ASP Author...Rick Dearbeck
Dennis Kostora
SPITFIRE T Shirts......Michael Redman........................Frank Crispell
Dennis Haase
2 Hobbit Trivia........Mary Van Horn.........................Chuck Eisenmenger
2 Disney Trivia........Mary Van Horn.........................Matt Carlson
Steve Frantz
2 Sex Trivia...........Mary Van Horn.........................Jake Kirkpatrick
Chris Kushma
2 Potpourri Trivia.....Mary Van Horn.........................Ira Lichtenstein
Josh Stortz
2 Sports Trivia........Jacque Shipley........................Jay Jackson
Chris Kushma
2 Television Trivia....Jacque Shipley........................Gay Ann Dearbeck
Alan Boelter
SFMgr Registration.....BETATech Computer Consulting..........Chuck Eisenmenger
HSLDoor Registration...BETATech Computer Consulting..........Rick Dearbeck
DoorKnob Registration..BETATech Computer Consulting..........John Krone
SFVerify...............Doug Vangorp..........................John Butler
Jason Spong
SFHeader...............Russell Mikami........................Valli Redman
Callback/Verifier......Russell Mikami........................Larry Jones
2 WildFire.............Steve Cox.............................Jay Jackson
Alan Boelter
2 BackFire.............Steve Cox.............................Randall Hubbard
Bob Wolf
CircuitNet Software....Dave Stahl............................Gay Ann Dearbeck
SFExtend...............Dave Stahl............................Dean Langholz
Procomm Plus v2.0......Alan Boelter..........................Harry Aller
Procomm Plus (Windows).DataStorm Technologies, Inc...........Stan Matlock
Desqview 386 v2.4......Quarterdeck...........................Dave Clark
DVX v1.0...............Quarterdeck...........................Doug Vangorp
1 So Much Shareware
CD-ROM.................Power User Software...................Brian Pressler
3 So Much Screenware
CD-ROM.................Power User Software...................Chuck Eisenmenger
James Jones Jr.
Michael Redman
3 Bad Attitude T-Shirts
.............Power User Software...................Tim Gibson
Armand Michaud
Alan Boelter
CD-ROM.................Dave Clark............................Michael Redman
2 CATDISK v6.21........Rick Hillier - ASP Author.............Mary Krone
Bruce Wilson
2 Telix v3.15..........Exis, Inc.............................Jake Kirkpatrick
Josh Stortz
2 SPIT-CD/ROM..........Don Hutson............................Dale Focht
Steve Newman
1 STORM Door...........STORM Door Productions................Chris Kuchma
2 SFLSTGEN.............Brown Business Software...............James Jones Jr.
John Steinberg
5 Gateway 1200.........Fifth Column Asscoiates Software......John McConnell
Larry Jones
Derek Motloch
Steve Newman
Louise Focht
Letter Match...........Sunrise Doors.........................Mike Thacker
Crypto Gram............Sunrise Doors.........................Don Mortenson
Baseball Dice..........Sunrise Doors.........................Frank Crispell
5 $20.00 Secret Service
Door Coupons.........Mike Wilson...........................Steve Frum
Dave Clark
Ira Lichtenstein
Frank Crispell
Chuck Dearbeck
Scott Reigle
5 $10.00 Secret Service
Door Coupons.........Mike Wilson...........................John Butler
Dennis Haase
Mary Krone
Kevin Turk
Dave Clark
2 FireInfo.............Tim Maloney...........................Curt White
Mary Butler
2 Dogfight.............Chris Tyson...........................Don Hutson
Dennis Kostora
2 LastCall II..........Bill Arlofski.........................Jacque Shipley
Armand Michaud
2 SubSpit..............Bill Arlofski.........................Diane Jackson
Robin Thibodeau
2 Subscribe............Bill Arlofski.........................Pat Stenberg
Brian Carlson
2 Hub T-Shirts.........Randall Hubbard.......................Valli Redman
Bob Wolf
2 Contact Plus.........Mike Thacker..........................Kevin Turk
Diane McConnell
Turbo Pascal 6.0.......Don Hutson............................Jeremy Frum
2400 Baud External
Modem....... Don Hutson............................Carl Villasenoi
3 ARJ..................Robert K. Jung........................LeJean Dennis
Matt Carlson
Carl Villasenoi
Printer Cable..........Glenn Jarvis..........................Gay Ann Dearbeck
T-Shirt................Artisoft..............................Amanda Woltz
10 $80 Coupons For
Door Games.....Doug Peterson.........................Scott Reigle
Randall Hubbard
John Krone
Curt White
Josh Stortz
Sean Fahey
Brian Carlson
Brian Pressler
Robin Thibodeau
Mike Thacker
Jason Spong
2 Backup Demo Disks....Colorado Memory Systems...............Josh Stortz
Robin Thibodeau
Star Printer Ribbon....Glenn Jarvis..........................Rick Dearbeck
Windows Quick Ref......Glenn Jarvis..........................Pat Stenberg
5 1/4 Storage Boxes....Don Hutson............................LeJean Dennis
3 1/2 Storage Boxes....Don Hutson............................Louise Focht
╒════════════════════╕
│ SYSOP-OF-THE-MONTH │
╘════════════════════╛
Ron Hossack
The Solid Rock BBS
Riverside, California
A brave one, is Ron Hossack!
[I'll let him explain why. -Ed.] "I was introduced to computers
by a friend who had several at his church," Ron related. "I bought an
IBM jr from him and promptly began disassembling it and, using a
soldering iron, began to make improvements." [See what I mean? More
nerve than I have! Cheers, Ron! -Ed]
"The computer came with a 300 baud modem," he continued, "and I
found OPUS would run on it. But I soon discovered, although I had an 80
meg hard drive and an HST, I wanted more speed."
Wasn't long before he upgraded to a 286 and Wildcat103 BBS software
and for quite a while beta tested it. Frankly, he wasn't pleased with
that BBS's functioning, so he started looking at other software. He tried
GAP and ProDoor before running across SPITFIRE 2.5.
"I set SPITFIRE up," Ron said, "configured it and ran a test. More
than satisfied, I fired a check off to Mike Woltz and have been a happy
camper ever since. It's been a real pleasure to help beta test Version 3.2.
"I also edit our local Sysops on-line magazine called, `RONtalk,' and
one of the challenges facing me is to set up and report on any available
new BBS software. It's very difficult to be unbiased when you already
have the best.
"I'm 40 years old and work in the marketing division of my company.
This puts bread on the table for my wife of 24 years and one of our sons
still living with us. Our other son is attending the University of Washington.
"The Solid Rock BBS is unique in that it's an extension of our church,
where I also dabble as the pastor. We use the Rock to take the message that
Jesus loves them to all the modem junkies out there in the community."
Ron has enjoyed working with DJ Chuang to bring to SPITFIRE Sysops the
first QWK compatible MailDoor, called JetMail.
╒════════════════════════════════════╕
│ NEWLY REGISTERED SPITFIRE SYSTEMS │
╘════════════════════════════════════╛
A hearty welcome is extended to the following, who have
recently become public registered SPITFIRE Bulletin Board Systems:
The Midnight Express......................318-334-9924....2400 Baud
Kevin Leger, Sysop.................................Rayne, Louisiana
The Psycho Ward...........................515-981-5265....2400 Baud
Dave Copeland, Sysop..................................Norwalk, Iowa
Cybornetic Information Systems............519-658-5804....2400 Baud
Andy Weisler, Sysop......................Cambridge, Ontario, Canada
Den Of Perversion.........................713-779-4202....2400 Baud
Richard Davis, Sysop.................................Houston, Texas
SEARCH....................................206-253-5213....2400 Baud
Sawvel & Associates, Sysop....................Vancouver, Washington
The Grapevine.............................503-325-1854....2400 Baud
Roger Lykins, Sysop.................................Astoria, Oregon
The Backup BBS............................712-323-0462....2400 Baud
Josh Stortz, Sysop.............................Council Bluffs, Iowa
Viking BBS................................817-526-7087....2400 Baud
Donald Camfield, Sysop...............................Killeen, Texas
St. Nicholas BBS..........................Phone Unknown...2400 Baud
Father Anthony Falsarella, Sysop.................Garrison, New York
House Of Ilkazam..........................515-262-2471....2400 Baud
Randal Anderson, Sysop.............................Des Moines, Iowa
P.A.C.E. Library BBS......................606-886-8403....2400 Baud
P.A.C.E. Library BBS...............................Auxier, Kentucky
Pirates Hollow............................Phone Unknown...2400 Baud
Michael Kasprzak, Sysop...............Ameliasburgh, Ontario, Canada
State Planning Office.....................207-289-4017....9600 Baud
State of Maine.......................................Augusta, Maine
Barne's Graphics..........................208-365-5223...19200 Baud
D. Leroy Barnes, Sysop................................Emmett, Idaho
Silver Blue Experience....................804-247-7659....2400 Baud
Forester John Barker III, Sysop...................Hampton, Virginia
Apollo's Lyre BBS.........................507-425-0967....2400 Baud
Timothy Lind, Sysop..........................Shirley, Massachusetts
Baddog's Domain BBS.......................714-352-1905...38400 Baud
Skip Bertsch, Sysop...........................Riverside, California
Westar Systems............................718-638-2478...14400 Baud
William Sheffield, Sysop.........................Brooklyn, New York
Mission Control...........................601-329-0195....2400 Baud
Steve Miles, Sysop...............................Columbus, Missouri
ComputerGraphix BBS.......................315-463-8702....9600 Baud
ComputerGraphix..................................Syracuse, New York
TOTAL REGISTER............................501-648-9397...38400 Baud
L.J. Mann, Sysop................................Fort Smith, Arizona
The Place To Be...........................913-441-3885....2400 Baud
Larry House, Sysop...........................Bonner Springs, Kansas
M.T.I. College BBS........................714-424-0107....2400 Baud
M.T.I. College...................................Colton, California
The Court House BBS.......................Phone Unknown...2400 Baud
Grey Lancaster, Sysop...................Spartanburg, South Carolina
Viper.....................................515-225-1773....2400 Baud
Jason Spong, Sysop............................West Des Moines, Iowa
The Data Fortress.........................503-591-8803....2400 Baud
Steve Facker, Sysop...................................Aloha, Oregon
The Zoo - The Black Hill's Best Wildlife..605-341-3955....2400 Baud
Michael Majorowicz, Sysop..................Rapid City, South Dakota
Up Town's.................................206-572-2548....2400 Baud
Richard & Margarita Towns, Sysops...............Tacoma, Washington
Hardly Up BBS.............................215-464-3101...14400 Baud
Len Aulett, Sysop........................Philadelphia, Pennsylvania
The Real Estate Connection................303-933-3372....9600 Baud
Alisa Hagner, Sysop.............................Littleton, Colorado
ComPostuff................................Phone Unknown...2400 Baud
Ted Balog, Sysop......................................Rittman, Ohio
Real Life Ministries......................702-731-9634....2400 Baud
Chris Phillips, Sysop.............................Las Vegas, Nevada
Images, Inc...............................918-652-3975....9600 Baud
Mark Maddox, Sysop..............................Henryetta, Oklahoma
Orange Computers..........................809-424-4135....2400 Baud
Harrington R.S. Trotman, Sysop...St. Michael, Barbados, West Indies
The Unknown BBS...........................806-665-8640....2400 Baud
Dan Treadwell, Sysop...................................Pampa, Texas
Tacotel Baan.............................+31-2154-23266...2400 Baud
Jeanette Saarberg, Sysop.........................Baarn, Netherlands
SMOKIN' JOE'S BBS.........................504-271-9690...14400 Baud
Joseph Revolta, Sysop..........................Chalmette, Louisiana
The U.S.B.B. BBS..........................209-896-8647....2400 Baud
Robert Beck, Sysop................................Selma, California
In addition, there were 9 new private SPITFIRE BBS Systems
registered. These private SPITFIRE BBS's included registrations
from: Hemet, California; Lyman, South Carolina; Plymouth, Minnesota;
Cairns, Australia; Green Bay, Wisconsin; Ft. Thomas, Kentucky;
Des Moines, Iowa; Houston, Texas; and an FPO-AP address.
There were 22 registrations for whom registration information was
incomplete. These included BBS's in: Saco, Maine; Gainesville,
Florida; Fort Hood, Texas; Tallahassee, Florida; Orange Park, Florida;
2 boards in Cincinnati, Ohio; Wilmington, Delaware; Monroe, Louisiana;
Baton Rouge, Louisiana; Hampshire, United Kingdom; Singapore, Singapore;
Florence, Alabama; Redlands, California; Detroit, Michigan; Odessa,
Texas; Clovis, New Mexico; Hampton, New Jersey; Gravois, Missouri;
Macon, North Carolina; Spartanburg, South Carolina; and an APO-AP
address.
The increase in registrations where information is incomplete is
largely due to Buffalo Creek's Software's new policy of accepting
on-line Mastercard and Visa credit card registrations.
JUST A REMINDER...the newsletter is always looking for contributions!
Please forward any articles in ASCII text to either Buffalo Creek's BBS
or The Mother Board BBS.Source note
This reading edition was decoded from SF07-92.TXT in the original SF07-92.ZIP package. The page date records the preserved archive timestamp; it is not a newly inferred publication date.