515 lines
22 KiB
Plaintext
515 lines
22 KiB
Plaintext
\input tex
|
|
\twelvepointsanserif
|
|
\font\hl=bs0003 scaled\magstep3 % headline font
|
|
|
|
\def\declare{\begingroup\obeylines\parindent=1em\parskip=0pt}
|
|
\def\enddeclare{\endgroup} % end of ...
|
|
\def\program#1{{\bf #1}\quad} % PROGRAMs stand out
|
|
\def\section#1{\bigskip\goodbreak{\hl #1}\vskip4pt\nobreak}
|
|
\def\subheading#1{\medskip\goodbreak{\bf #1}\ }
|
|
\def\fido{Fido\slash FidoNet} % simplicity
|
|
\hyphenation{jennings fido fidonet data-base data-bases}
|
|
|
|
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
|
\vskip.25in
|
|
\declare
|
|
\leftskip=4.5in
|
|
Tom Jennings
|
|
Fido Software\hfill June 1991
|
|
Box 77731
|
|
San Francisco
|
|
CA 94107 USA
|
|
bbs: (415)-863-2739
|
|
FidoNet: 1:125/111
|
|
Internet: tom.jennings@fidosw.fidonet.org
|
|
\enddeclare
|
|
\vskip.25in
|
|
\bar
|
|
|
|
\fido\ is a software package for DOS based Personal Computers that�
|
|
contains a complete Bulletin Board System plus a fully automatic�
|
|
Electronic Mail system.
|
|
|
|
Fido is the most popular Bulletin Board system in the world because of�
|
|
its flexibility, reliability, and features; FidoNet is the software�
|
|
that defined the FidoNet protocol now in use around the world. The�
|
|
worlds largest privately-owned computer network is based upon the�
|
|
FidoNet communications protocol.
|
|
|
|
\bar
|
|
\begindoublecolumns
|
|
|
|
Fido\trademark\ Bulletin Board System:
|
|
|
|
\declare
|
|
\item{\blob}Absolute security
|
|
\item{\blob}Complete caller access controls
|
|
\item{\blob}Multiple-language and graphical interfaces
|
|
\item{\blob}200 independent message \& file areas
|
|
\item{\blob}Complete Email and message commands
|
|
\item{\blob}Fully error correcting file transfer protocols
|
|
\item{\blob}Supports all DOS/MSDOS Personal Computers
|
|
\enddeclare
|
|
|
|
Fido is a full-featured Computer Bulletin Board System. Callers,�
|
|
commands, message and file areas can all have separate privilege�
|
|
levels and Locks \& Keys applied to them; these let you limit callers'�
|
|
access to any part of the Fido system to fit your needs.
|
|
|
|
\goodbreak
|
|
FidoNet\trademark\ Electronic Mail Network:
|
|
|
|
\declare
|
|
\item{\blob}Completely automatic Electronic Mail
|
|
\item{\blob}Full error correction protocol
|
|
\item{\blob}Extensive time-of-day event scheduling
|
|
\item{\blob}Powerful message routing language
|
|
\item{\blob}Automatic message routing
|
|
\enddeclare
|
|
|
|
FidoNet is an automatic ``store-and-forward'' mail system that�
|
|
transfers messages and files with other Fido\-Net-equipped computers.�
|
|
It is completely integrated with Fido, and completely transparent in�
|
|
operation, and if you don't use it, you won't even know it's there.
|
|
|
|
\enddoublecolumns
|
|
\bar
|
|
|
|
\section{System Description}
|
|
\subheading{\fido} is extremely easy to use, and is compatible with�
|
|
just about any users terminal program or computer. The user interface�
|
|
does not get in the way of communicating; there are only two levels of�
|
|
menus. Users see only what they need; novices find an easy to�
|
|
understand selection of simple commands, and experts can choose a�
|
|
brief prompt. Context sensitive help is available at all decision�
|
|
points. You can have up to 16 different languages or graphical�
|
|
interfaces installed at once.
|
|
|
|
\subheading{Reliability:} \fido\ is designed first and foremost for�
|
|
reliability, meaning it will run 24 hours a day for months at a time�
|
|
with no human intervention. (Obviously this doesn't include responding�
|
|
to callers questions or other such things.) Tools are provided that�
|
|
handle all routine maintenance tasks automatically.
|
|
|
|
\subheading{Performance:} \fido\ makes excellent use of ordinary�
|
|
computers; with a high-performance modem such as a US Robotics Courier�
|
|
Dual Standard, you will get kilobyte/second throughput on a so-called�
|
|
``turbo'' PC XT.
|
|
|
|
\subheading{More than one modem:} While \fido\ supports only one�
|
|
modem, you can run more than one copy of \fido\ per computer using a�
|
|
multitasker program. \fido\ prevents file and message ``collisions''�
|
|
when more multiple users are accessing the same messages and files.�
|
|
Performance degradation is negligible. See ``Supported Operating�
|
|
Systems'' for the current list of supported multitaskers.
|
|
|
|
\subheading{Low disk space overhead:} A 20 Megabyte hard disk is�
|
|
essentially unlimited space; room for thousands of messages, files, a�
|
|
10,000+ node FidoNet network, with plenty of disk space left over.
|
|
|
|
For a sample ``small scale'' system, with only two 360K floppies and�
|
|
256K of memory, there is room for all of the basic \fido\ system�
|
|
utilities plus your text editor and other tools, over 200 messages,�
|
|
and close to 100K bytes free. The same system with a 1,600 node�
|
|
FidoNet Network can have approximately 80 messages, would be�
|
|
considered very ``tight''.
|
|
|
|
\subheading{Modem Handling:} \fido\ achieves extremely high�
|
|
reliability with ordinary modems. During idle periods, \fido\ ``talks�
|
|
to'' the modem to make sure it is ready and working. (While of course�
|
|
modems are not supposed to misbehave, in real life they can get�
|
|
confused by callers' strange and incompatible modems, improper�
|
|
operation, bad phone lines, and bad modem design, and newer-model�
|
|
modems frequently have firmware bugs. \fido\ takes care of these�
|
|
things automatically. Almost all problems reported are modem-related�
|
|
problems!)
|
|
|
|
Incoming callers' baud rate is determined automatically; callers do�
|
|
not have to hit the ``ENTER'' key to get the systems attention.�
|
|
Outgoing calls made by FidoNet (if so enabled) can take advantage of�
|
|
busy detect, no-dial-tone, and other features if provided by the�
|
|
modem.
|
|
|
|
\subheading{Caller DataBase:} Each caller to the system has a record�
|
|
in a database that maintains each callers name, password,
|
|
terminal-specific settings, language selection, privilege levels and�
|
|
controls, and various statistics. Tools provided manipulate these�
|
|
records both manually and automatically. There can be up to 65,535�
|
|
callers in the database.
|
|
|
|
\subheading{System Messages and Bulletins:} \fido\ uses ordinary text�
|
|
files for system messages and bulletins, which are meant to be�
|
|
customized by you. When displaying and entering text, the Fido takes�
|
|
into account each callers terminal settings, such as screen width and�
|
|
length, and performs on-screen formatting for a clean display.
|
|
|
|
\subheading{Access Controls:} There are six privilege levels that�
|
|
callers can be assigned. You can specify minimum privilege levels�
|
|
needed to access commands and message and file areas.
|
|
|
|
In addition to privilege levels, there are 32 ``locks'' with matching�
|
|
``keys''. Locks are be applied to things such as commands and message�
|
|
and file areas; callers may be given any number of keys. Callers can�
|
|
access only those things for which they have all of the matching keys,�
|
|
plus meet the privilege level requirements. For example, if the {\tt�
|
|
E)nter-Message} command has lock \#20 applied, only callers that have�
|
|
Key \#20, plus any necessary minimum privilege levels, can use, see or�
|
|
get help with that command.
|
|
|
|
Limits can be placed on each callers' connect-time on the system
|
|
per-call and per-24-hour period, and on file downloads.
|
|
|
|
\subheading{Context-Sensitive Help System:} Help is
|
|
context-sensitive, taking into account what commands the caller has�
|
|
access to because of privilege levels or locks and keys. Help is�
|
|
available on every command in the system. The Help files are text�
|
|
files that can be customized to fit your specific needs.
|
|
|
|
\subheading{Message Areas:} There can be up to 200 separate message�
|
|
areas, each with access controls as described above. There can be up�
|
|
to 65,535 messages in each area. Callers can enter new messages,�
|
|
modify existing saved messages, search for messages by keyword or as�
|
|
addressed to or from them, and perform many other operations upon�
|
|
messages. (Command availability depending on privilege levels and�
|
|
locks of course.) Help is available at all decision points.
|
|
|
|
\subheading{File Areas:} There can be up to 200 independent file�
|
|
areas, with access controls as described earlier. There are a number�
|
|
of ways in which to make files available (or not) to callers. Commands�
|
|
and functions have been added to make remote maintenance of file areas�
|
|
and other parts of the disk easier for the system operator. Files can�
|
|
be uploaded and downloaded in ASCII, ZMODEM, XMODEM, Telink, ``MODEM�
|
|
BATCH'' or Kermit protocols. XMODEM is nearly universal, and can�
|
|
handle binary files; ZMODEM has performance to match high-performance�
|
|
modems; Kermit and ASCII are used between otherwise-incompatible�
|
|
computers.
|
|
|
|
My ``FidoTerm'' program works well with \fido\ or any other modem�
|
|
based system.
|
|
|
|
\subheading{Programmed events:} There can be up to 100 ``Events'',�
|
|
scheduled to run at any time of the day and any day of the week.�
|
|
Events allow \fido\ to run FidoNet network mail, execute external�
|
|
programs via DOS Batch Files, and other events for various special�
|
|
purposes. The events system can handle simultaneous and/or overlapping�
|
|
events, special ``optional'' events, and combinations of events and�
|
|
special characteristics. (``Optional'' events can be used, for�
|
|
example, to execute ``background'' FidoNet network activity while no�
|
|
caller is otherwise occupying the system.)
|
|
|
|
\subheading{Other Features \& Enhancements:} You can sign in to the�
|
|
system from the local keyboard, as if you had called in remotely with�
|
|
a modem, without ``taking down'' the system. Upcoming events can be�
|
|
listed, and previously-run events can be reenabled from the local�
|
|
keyboard.
|
|
|
|
Fido works with external ``shell'' programs to allow programmers and�
|
|
``aftermarket'' add-on programs to work with \fido. Technical�
|
|
information is available in the manual. (External ``shell'' support�
|
|
programs are not supplied by me.)
|
|
|
|
\section{FidoNet}
|
|
Using Fido, you enter messages, choosing the destination computer(s)�
|
|
from a list; later, FidoNet automatically transfers those messages to�
|
|
the destination computers. You can ``attach'' files to a message to�
|
|
transfer files of any kind, and \fido\ will transfer hten along with�
|
|
the messages. \fido\ will inform you when the message (and files, if�
|
|
any) has been successfully sent. There can be any number of�
|
|
messages\slash files pending to any number of destination computers.�
|
|
FidoNet's routing language and other resources let you control exactly�
|
|
how and when FidoNet messages are sent. All transfers use error�
|
|
correction for absolute reliability\footnote*{Fido supports both the�
|
|
original and universal FidoNet protocol, as well as the WaZoo�
|
|
protocol, developed by Wynn Wagner.}.
|
|
|
|
FidoNet networks can be organized into ``Nets'' and�
|
|
``Regions''\footnote{**}{FidoNet also has ``Zones'', groups of Nets�
|
|
and Regions, that handle the problems of intercontinental traffic;�
|
|
differences in time zones, incompatible modems, outgoing ``gateways''�
|
|
for lowest cost, and so on.}, each of which can contain any number of�
|
|
computers running the \fido\ software, or compatibles, one of which is�
|
|
designated Host for the Net. A Host receives mail for the entire Net,�
|
|
and distributes the mail to its local FidoNet computers. FidoNet is�
|
|
intelligent enough to send all messages for a given net in one phone�
|
|
call; you can get further efficiency with the routing language.
|
|
|
|
FidoNet networks can be as small as two or three computers, or as�
|
|
large or larger than the hobbiest FidoNet network, which is up to�
|
|
10,000 systems as of March 1991.
|
|
|
|
\subheading{Incoming FidoNet mail at any time:} \fido\ can receive�
|
|
mail from other \fido\ systems at any time a caller is not occupying�
|
|
the system, not just during scheduled FidoNet events. Optionally,�
|
|
\fido\ can execute external programs via a DOS Batch File to do�
|
|
special processing of unscheduled Incoming Mail.
|
|
|
|
\section{Customization}
|
|
\fido\ parameters, lists of events, command names, and message and�
|
|
file area definitions are contained in text files you can change with�
|
|
your own text editor program. All message and file areas are defined�
|
|
in one text file; the \fido\ system takes care of creating and�
|
|
verifying the actual DOS subdirectories used. Commands are in their�
|
|
own text file, along with any privilege levels and locks. You can�
|
|
change command names to any single word you choose.
|
|
|
|
\subheading{Multiple Languages:} \fido\ supports up to 16 languages�
|
|
and/or graphical interfaces. Interfaces accomodate both ANSI/color�
|
|
variations of one language (eg. all english, but color, monochrome,�
|
|
standard Fido interface) or multiple languages (English, German,�
|
|
Dutch, Spanish, etc) or any combination.
|
|
|
|
When a caller selects a language, the any or all parts of the�
|
|
interface can be changed; all runtime messages, command names, help�
|
|
files, system bulletins. (For example, when running ANSI/color�
|
|
variations of one language, the command names should not change; when�
|
|
changing languages changing command names may be part of the goal.)
|
|
|
|
The following interfaces are available at this time:
|
|
\smallskip
|
|
|
|
\begindoublecolumns
|
|
\declare
|
|
\item{\blob} American English
|
|
\item{\blob} American English Color \#1
|
|
\item{\blob} American English Color \#2
|
|
\item{\blob} ANSI Monochrome
|
|
\item{\blob} Bahasa Malay
|
|
\item{\blob} Chinese BIG-5
|
|
\item{\blob} Danish
|
|
\item{\blob} Dutch
|
|
\item{\blob} Dutch color
|
|
\item{\blob} German
|
|
\item{\blob} German color
|
|
\item{\blob} Spanish
|
|
\enddeclare
|
|
\enddoublecolumns
|
|
|
|
Chinese BIG-5 requires a special BIG-5 CODE ROM and programs, not�
|
|
available from me. The master American language files are available�
|
|
for custom translations; please contact me for details.
|
|
|
|
\section{Programs Supplied with \fido}
|
|
The following are some of the programs supplied as part of the�
|
|
standard \fido\ system package. In addition, there are many�
|
|
``aftermarket'' programs from other authors that make using and�
|
|
maintaining \fido\ easier and more powerful.
|
|
|
|
You can schedule Events in \fido\ to execute these or other programs�
|
|
at any time, using an MSDOS Batch File you create to make your system�
|
|
completely or partially automatic.
|
|
|
|
\program{MSGMGR.EXE} (the Message Manager) performs routine�
|
|
maintenance on messages within \fido\ Message Areas, such as purging�
|
|
messages by age, and renumbering messages so they are sequential.�
|
|
MSGMGR has it's own text file of commands that tells it what to do.
|
|
|
|
\program{SYSOP.EXE} is a database-like tool for managing the caller�
|
|
database that contains the names, passwords and statistics and other�
|
|
information on each caller. You can enter new callers, delete existing�
|
|
callers one by one or by time since last logged in; set caller�
|
|
privilege level and assign Keys; force callers into specific message�
|
|
and file areas; and many more functions. There is also an ``undo''�
|
|
feature and context sensitive help.
|
|
|
|
\program{FIDOMAIL.EXE} lets you create FidoNet network messages with�
|
|
your own text editor or word processor. For example, during the day�
|
|
you can create text files destined for other FidoNet network nodes,�
|
|
and via an Event, have FidoMail put them into the FidoNet message�
|
|
system.
|
|
|
|
\program{TWIX.EXE} prints FidoNet network mail newly received on your�
|
|
printer or in a disk file you specify.
|
|
|
|
\newpage
|
|
|
|
\section{Requirements and Specifications}
|
|
\subheading{Computers:} \fido\ works on all�
|
|
IBM\trademark\footnote*{``IBM'' is a trademark of IBM Corp.} Personal�
|
|
Computers; PC, XT, AT, all PS/2 models, and all compatible ``clones'',�
|
|
whether 8088, 8086, 80286, 80386. (A ``FOSSIL'' version is available�
|
|
for other non-compatible MSDOS computers.)
|
|
|
|
\smallskip
|
|
Your computer must have at least the following:
|
|
|
|
\declare
|
|
\item{\blob}192K available memory
|
|
\item{\blob}At least 700K of disk storage
|
|
\item{\blob}One Serial Port (or internal modem)
|
|
\item{\blob}Modem as described below
|
|
\enddeclare
|
|
|
|
It is strongly recommended that you have a hard disk, and an internal�
|
|
clock.
|
|
|
|
\subheading{Modems:} The following are explicitly supported by \fido.�
|
|
Though models not listed below are not guaranteed to work, no one has�
|
|
come up with a Hayes-type modem that can't be made to work properly my�
|
|
simply entering the necessary initialization commands into Fido's�
|
|
initialization file.
|
|
|
|
\declare
|
|
\item{\blob}U.S. Robotics Courier HST and Dual Standard
|
|
\item{\blob}Telebit TrailBlazer series
|
|
\item{\blob}U.S. Robotics Courier 2400
|
|
\item{\blob}Hayes SmartModem V-series
|
|
\item{\blob}Hayes SmartModem 1200
|
|
\item{\blob}Everex Internal \& External models
|
|
\item{\blob}Multi-Tech 2400
|
|
\item{\blob}Nearly all ``Hayes compatible'' modems
|
|
\item{\blob}``Dumb'' modems$^*$
|
|
\item{\blob}Direct connect to PBX or special serial device$^*$
|
|
\enddeclare
|
|
|
|
%
|
|
% To avoid having the footnote take on characteristics if the \item
|
|
% above, we've fudged it.
|
|
\footnote{\ }{However, FidoNet cannot originate calls without an
|
|
auto-dial modem.}
|
|
|
|
\subheading{Operating Systems Supported:} MSDOS\slash PCDOS versions�
|
|
2.00 and up, with most Local Area Networks (ViaNet, Novell Netware,�
|
|
etc) most multitasker programs (DoubleDOS, DESQView, Multilink, etc)�
|
|
and multiprocessor hardware products (Alloy Computer Products' Slave�
|
|
Cards); please contact the manufacturers of those products for�
|
|
details.
|
|
|
|
\fido\ is specifically DoubleDOS and DESQView aware.
|
|
|
|
\newpage
|
|
|
|
\section{Software Policy}
|
|
|
|
This is the software policy for the \fido\ package. Please read it�
|
|
carefully.
|
|
|
|
First:
|
|
|
|
Hobbyists run Bulletin Boards for their own personal reasons. Their�
|
|
Bulletin Board is not associated with their employer or any business.�
|
|
How they run their Bulletin Board is none of my business, ie. private,�
|
|
public, subscription or chattel slavery.
|
|
|
|
Commercial users are companies, corporations, proprietorships or any�
|
|
other business entities that run a BBS, either publicly or privately,�
|
|
associated with their business. ``Non-profit'' and ``not for profit''�
|
|
organizations are included in this category.
|
|
|
|
And here's the deal:
|
|
|
|
\subheading{Hobbyists and Individuals:} \fido\ is shareware; the�
|
|
latest version of the software, minus documentation, can always be�
|
|
found on the Fido Software BBS. There is no downloadable�
|
|
documentation. (If you thought the version 11 docs were unwieldy\dots)�
|
|
You must register the software for \$39.95; in return you will receive�
|
|
the latest version on diskette plus printed and bound documentation.�
|
|
If you later desire updates via diskette instead of download, send�
|
|
\$15 plus the original diskettes or other proof of purchase.
|
|
|
|
\subheading{Commercial Users:} \fido\ is a usual licensable product;�
|
|
the license fee is \$199.95. You will receive the latest software�
|
|
version, complete documentation, and support via the Fido Software�
|
|
BBS. (This has proved to be more than adequate for over two years.)�
|
|
Updates can be obtained by downloading, or via diskette for \$25 plus�
|
|
the original Fido Software diskette or other proof of purchase.
|
|
|
|
\subheading{BBS System Operators:} Besides being a {\bf Hobbyist} as�
|
|
defined above, you may have the software available for download, as�
|
|
you would any other program. Please keep READ.MEs and POLICY files,�
|
|
along with the basic files as supplied by me, together as a unit to�
|
|
avoid confusion frustration for all of us.
|
|
|
|
\subheading{Shareware Distributors,} clubs, etc: Please order the�
|
|
complete package as a {\bf Commercial User}; for small hobbyist clubs,�
|
|
as a {\bf Hobbyist} or {\bf Individual}. This will assure you the�
|
|
latest correct and complete version, and the manual will help your�
|
|
club members get things going easily. Such a deal. Look, I'm not�
|
|
getting rich off this (or even breaking even!) so let's scratch each�
|
|
others backs, OK?
|
|
|
|
Special arrangements can always be made on a case by case basis. In�
|
|
all cases, bugs are fixed promptly, as they have been for six years.
|
|
|
|
\newpage
|
|
\section{Ordering}
|
|
\declare
|
|
\parindent=3.5in
|
|
Tom Jennings
|
|
Fido Software
|
|
Box 77731
|
|
San Francisco
|
|
CA 94107 USA
|
|
bbs: (415)-863-2739
|
|
FidoNet: 1:125/111
|
|
Internet: tom.jennings@fidosw.fidonet.org
|
|
\enddeclare
|
|
|
|
\medskip
|
|
\bar
|
|
|
|
\def\product#1#2{\medskip\line{{\bf #1} \leaderfill\ {\bf #2}}}
|
|
|
|
{\parskip=0pt
|
|
\product{\fido\ Version 12}{Commercial price: \$199.95}
|
|
\line{\hfill\bf Hobbyist price: \$39.95}
|
|
}
|
|
Complete \fido\ system license, including support programs, diskette,�
|
|
manuals, and access to the Fido Software customer support bulletin�
|
|
board.
|
|
|
|
\product{\fido\ Version 12 program update}{\$25}
|
|
\line{\hfill\bf Hobbyist price: \$15}
|
|
When enhancements to \fido\ version 12 are made (bugs fixed, features�
|
|
added) customers may upgrade their current licensed Version 12�
|
|
software to the latest revision. Errata sheets are provided as�
|
|
necessary.
|
|
|
|
\product{\fido\ upgrade from Version 11 (or earlier)}{\$50}
|
|
Customers who purchased any previous version of \fido\ can upgrade to�
|
|
version 12 for this price; proof of purchase must be returned. NOTE:�
|
|
This is not a normal ``program update'', as described above, because�
|
|
of the new materials that must be provided.
|
|
|
|
\product{FidoTerm Terminal Program}{\$12}
|
|
The FidoTerm program is a simple, powerful and easy to use terminal�
|
|
program. You can view the last few hundred lines that scrolled off the�
|
|
top of your screen; supports powerful file transfer protocols (ASCII,�
|
|
Xmodem, Zmodem), and has a true script language with true programming�
|
|
language constructs: a switch() statement, local variables,�
|
|
subroutining and recursion. Comes complete with printed manual.
|
|
|
|
FidoTerm is well integrated into \fido; it may be invoked from Fido's�
|
|
local console by a single keystroke, and will ``know'' about the�
|
|
installed modem type and port, and commands let you dial from a�
|
|
FidoNet nodelist.
|
|
|
|
\medskip
|
|
\boxit{1pt}{NOTE: Unless you say otherwise, the integral IBM Async�
|
|
driver version of \fido\ and FidoTerm will be shipped. A FOSSIL�
|
|
version is also available. FOSSIL drivers are not supplied by Fido�
|
|
Software.\vadjust{\vskip\baselineskip}}
|
|
\medskip
|
|
|
|
\vfill
|
|
|
|
\subheading{All orders:} The software is available directly from Fido�
|
|
Software or authorized distributors only. Terms are prepaid with�
|
|
order, or invoices accepted from rated companies, payment Net 30 days.�
|
|
No credit cards accepted.
|
|
|
|
\subheading{US/Canada:} All orders are shipped U.S. Postal Service�
|
|
First Class (Priority Mail). Prices listed include shipping and taxes,�
|
|
where applicable. For Federal Express next-day service add \$25.
|
|
|
|
\subheading{Outside US/Canada:} For checks written outside U.S., add�
|
|
\$20.00 per order; please, only checks ``drawn upon a US bank''. All�
|
|
orders shipped Air Mail.
|
|
|
|
\vfill
|
|
\vskip\parskip\tenpointsanserif
|
|
Fido\trademark, FidoNet\trademark, and the dog-with-diskette are�
|
|
registered U.S. trademarks of Tom Jennings. \fido\ and all support�
|
|
programs are copyright \copyright\ by Tom Jennings 1991
|
|
|
|
\supereject\end
|