2543 lines
106 KiB
Plaintext
2543 lines
106 KiB
Plaintext
F I D O N E W S -- Volume 14, Number 3 20 January 1997
|
||
+----------------------------+-----------------------------------------+
|
||
| The newsletter of the | ISSN 1198-4589 Published by: |
|
||
| FidoNet community | "FidoNews" |
|
||
| _ | 1-904-409-7040 [1:1/23] |
|
||
| / \ | |
|
||
| /|oo \ | |
|
||
| (_| /_) | |
|
||
| _`@/_ \ _ | |
|
||
| | | \ \\ | Editor: |
|
||
| | (*) | \ )) | Christopher Baker 1:18/14 |
|
||
| |__U__| / \// | |
|
||
| _//|| _\ / | |
|
||
| (_/(_|(____/ | |
|
||
| (jm) | Newspapers should have no friends. |
|
||
| | -- JOSEPH PULITZER |
|
||
+----------------------------+-----------------------------------------+
|
||
| Submission address: FidoNews Editor 1:1/23 |
|
||
+----------------------------------------------------------------------+
|
||
| MORE addresses: |
|
||
| |
|
||
| submissions=> cbaker84@digital.net |
|
||
+----------------------------------------------------------------------+
|
||
| For information, copyrights, article submissions, |
|
||
| obtaining copies of FidoNews or the internet gateway FAQ |
|
||
| please refer to the end of this file. |
|
||
+----------------------------------------------------------------------+
|
||
|
||
|
||
PRESIDENT CLINTON GETS REINAUGURATED!
|
||
|
||
|
||
Table of Contents
|
||
1. EDITORIAL ................................................ 1
|
||
The WebRing server is down et al ......................... 1
|
||
2. ARTICLES ................................................. 2
|
||
ELIST.EXE - Eudora Mailbox/Message Extraction utility .... 2
|
||
3. GETTING TECHNICAL ........................................ 6
|
||
FSC-0020 - Alternate Nodelist Flag Proposal .............. 6
|
||
FSC-0021 - VFOSSIL - An OS/2-Subset ...................... 9
|
||
FSC-0023 - Bundle Name Format ............................ 22
|
||
4. COORDINATORS CORNER ...................................... 26
|
||
Nodelist-statistics as seen from Zone-2 for day 017 ...... 26
|
||
5. WE GET EMAIL ............................................. 27
|
||
A NEW way to get FidoNews! ............................... 27
|
||
Is this the Good News about Good Times? .................. 28
|
||
Open letter to ZC1 ....................................... 30
|
||
6. NET HUMOR ................................................ 31
|
||
ET phone home? ........................................... 31
|
||
7. WANTED ................................................... 33
|
||
Looking for Mr. Surveyed equipment? ...................... 33
|
||
8. NOTICES .................................................. 34
|
||
Future History ........................................... 34
|
||
9. FIDONET SOFTWARE LISTING ................................. 35
|
||
Latest Greatest Software Versions ........................ 35
|
||
10. FIDONEWS PUBLIC-KEY ..................................... 42
|
||
FidoNews PGP public-key listing .......................... 42
|
||
And more!
|
||
FIDONEWS 14-03 Page 1 20 Jan 1997
|
||
|
||
|
||
=================================================================
|
||
EDITORIAL
|
||
=================================================================
|
||
|
||
|
||
Lots of folks are trying to get their Webpages linked to the new
|
||
FidoNet WebRing but are hitting a wall.
|
||
|
||
The WebRing [reported in 1402], in operation for two years, has lost
|
||
their server and is in search of another. Timing is everything. [grin]
|
||
|
||
I received email from the WebRing owner and he advises that they will
|
||
be back in business on another server by next week at the latest. So,
|
||
if you get a server timeout or not located notice when you try to sign
|
||
up on the FidoNet World Wide WebRing, please keep trying or wait until
|
||
late next week. These things happen.
|
||
|
||
Also in this Issue is a message from jim barchuk about a new way to
|
||
get your weekly FidoNews via an Internet email subscription. Please
|
||
note the list name change in the second part of the message extract.
|
||
|
||
Other than that, FidoNet seems about the same as usual. Nothing has
|
||
been heard here about the status of ZCs or an IC lately. What gives
|
||
guys?
|
||
|
||
SEND MORE ASCII ART!! Thanks.
|
||
|
||
SEND MORE .BIOs!! Thanks.
|
||
|
||
C.B.
|
||
|
||
-----------------------------------------------------------------
|
||
|
||
FIDONEWS 14-03 Page 2 20 Jan 1997
|
||
|
||
|
||
=================================================================
|
||
ARTICLES
|
||
=================================================================
|
||
|
||
|
||
ELIST.EXE - Eudora Mailbox/Message Extraction utility
|
||
Written by Fredric L. Rice, January 1997
|
||
The Skeptic Tank, 1:218/890.0 (818) 335-9601
|
||
|
||
Overview
|
||
|
||
The ELIST utility displays a list of Eudora mailbox titles
|
||
and allows the operator to select any of them for extraction.
|
||
|
||
Upon selection the program displays the subjects of all of
|
||
the messages within the selected mailbox and allows the
|
||
operator to select any number of messages for exporting to
|
||
a straight ASCII file.
|
||
|
||
In this way messages received and sent using Eudora may be
|
||
easily extracted from the Eudora mailboxes to an external
|
||
file which can then be manipulated in any way the operator
|
||
needs (imported into Word documents, sent to a FidoNet echo,
|
||
anything you need; use your imagination.)
|
||
|
||
Who Could Use This Program
|
||
|
||
Anyone who uses Eudora for sending and receiving mail will
|
||
most likely employ the "(S)ave-As" menu option to export a
|
||
single message. This utility allows easier selection and
|
||
export-to-file of multiple messages from all mailboxes
|
||
quickly and easily. All of the messages selected are
|
||
exported to the same file allowing all messages for a specific
|
||
subject to be selected and then exported to a single file.
|
||
|
||
When Will This Program Die?
|
||
|
||
If versions of Eudora come out which allow multiple message
|
||
selection for export to a file, this program will become
|
||
obsolete. Further enhancements might be performed in the
|
||
future which would keep this project alive -- for example,
|
||
the program could create FidoNet *.MSG type message packets
|
||
out of selected messages in a future version.
|
||
|
||
What Is This Program?
|
||
|
||
This is a DOS program. There was some intention of making it
|
||
a Windows or OS/2 program but I wanted it to be DOS only.
|
||
|
||
How To Get The Program
|
||
|
||
You can FileRequest ELIST.ZIP from 1:218/890.0 24 hours a
|
||
day or call direct at (818) 335-9601 and download it from
|
||
(A)rea 1 -- General Files.
|
||
|
||
If you send a message to frice@stbbs.com or frice@linkline.com
|
||
FIDONEWS 14-03 Page 3 20 Jan 1997
|
||
|
||
|
||
and place ELIST.ZIP anywhere within your message text, the
|
||
file will be automatically sent to you (unless you have an
|
||
invalid return address in which case the program doesn't
|
||
even try to send it.)
|
||
|
||
MagicFile name ELIST will also return the program.
|
||
|
||
What Limitations Are There?
|
||
|
||
Currently the program displays the first 40 mailboxes on the
|
||
screen and asks the operator to select which one to use. If
|
||
there are more than 40 Eudora mailboxes, the program will
|
||
refuse to run. Usually if you have that many mailboxes
|
||
anyway you should create subdirectory folders and logically
|
||
group your mailboxes within them. ELIST would manipulate
|
||
only the current folder specified by the ELIST environment
|
||
variable path.
|
||
|
||
Another constraint is memory. When a mailbox is selected
|
||
the program extracts header information from every message
|
||
in the mailbox if the program hasn't already extracted the
|
||
information from it. If multiple mailboxes are selected the
|
||
header information for all mailboxes is maintained in
|
||
memory. I haven't seen a problem yet however in the event
|
||
an out-of-memory problem occurs, the operator would need to
|
||
simply restart the program and work with one mailbox at a
|
||
time instead of multiple mailboxes.
|
||
|
||
If it's a problem, contact me and I'll make a version which
|
||
will discard a mailbox's header information from memory if
|
||
the memory starts to get full. It's easy; no problem. I
|
||
should probably do it anyway but I'm a speed maven; if I read
|
||
something into memory once, I don't like doing it again if
|
||
I don't need to. I don't _think_ I need to at this time.
|
||
|
||
Environment Variable
|
||
|
||
The program looks for the ELIST environment variable. This
|
||
points to where the *.TOC and *.MBS Eudora mailboxes can be
|
||
found. Usually this is either the main mailbox folder or a
|
||
subdirectory containing mailboxes for a secondary folder.
|
||
|
||
Usually, if it's the main folder, it would look something
|
||
like this:
|
||
|
||
set ELIST=C:\EUDORA
|
||
|
||
A secondary folder containing mailboxes holding mail from
|
||
a variety of crackpots (I get a LOT of crackpot mail) would
|
||
probably look something like this:
|
||
|
||
set ELIST=C:\EUDORA\CRACKPOT
|
||
|
||
If there is a trailing backslash that's okay, too.
|
||
|
||
If there is no environment variable set, the program looks
|
||
FIDONEWS 14-03 Page 4 20 Jan 1997
|
||
|
||
|
||
in the current default directory for the Eudora mailbox
|
||
files.
|
||
|
||
ErrorLevel Values
|
||
|
||
The program will terminate with an errorlevel value which
|
||
offers some indication as to why the program failed to run
|
||
properly. There is a descriptive error message offered by
|
||
the program yet historically FidoNetters and Internetters
|
||
have enjoyed batch-file processing even when an application
|
||
requires operator input.
|
||
|
||
Toward that end, the following errorlevel values will be
|
||
issued in the event a problem occurs:
|
||
|
||
#define EL_No_Problem 0
|
||
#define EL_No_Eudora_Files_Found 10
|
||
#define EL_Cant_Open_TOC_File 11
|
||
#define EL_Ran_Out_Of_Memory 12
|
||
#define EL_Programming_Error_Point_One 13
|
||
#define EL_Cant_Find_MBX_File_Now 14
|
||
#define EL_Programming_Error_Point_Two 15
|
||
#define EL_Programming_Error_Point_Three 16
|
||
#define EL_Cant_Create_Report_File 17
|
||
|
||
Output of Selected Messages
|
||
|
||
After selecting messages to export to a file, the operator is
|
||
asked to enter the file name of where to put them. If the
|
||
operator hits [ENTER] without offering a file name, they are
|
||
exported to ELIST.OUT as the default.
|
||
|
||
Operational Details
|
||
|
||
The operator may select all messages in a mailbox for export
|
||
as well as toggle individual messages. (There's an option
|
||
for deselecting all messages if desired.) Selecting all of
|
||
the messages in a mailbox and exporting them to an ASCII
|
||
file is quite useful for people who maintain mailboxes for
|
||
specific subjects (such as having a specific mailbox for
|
||
company business, another for tax information, one for
|
||
messages from a mailing list, and another for personal
|
||
business.)
|
||
|
||
Selecting and exporting all messages from a mailbox would be
|
||
an easy way to transfer messages received from a mailling
|
||
list to a single file which could be bundled-up and sent on
|
||
to someone else.
|
||
|
||
What Does This Cost?
|
||
|
||
The program is being distributed freely at no cost provided
|
||
it is not used for any commercial venture and is not sold for
|
||
any reason (or under any pretense.) "Companies" which "sell
|
||
floppies" with software pulled from what they believe to be
|
||
the public domain are _not_ allowed to distribute this program
|
||
FIDONEWS 14-03 Page 5 20 Jan 1997
|
||
|
||
|
||
(either at swap meets or through the mails or person-to-
|
||
person.)
|
||
|
||
If I see this program being distributed at a swap meet, I will
|
||
take names and start fucking everyone responsible until all
|
||
the nasty criminals bleed horribly to death.
|
||
|
||
I'm serious. I've been screwed by these mock "companies"
|
||
before and Goat help me it's time to screw back some.
|
||
|
||
Source Code Availability:
|
||
|
||
The source code for this project is available but costs. The
|
||
code consists of a single Turbo C++ module and a single
|
||
header module. The code format and variable naming conventions
|
||
used conform to IBM's in-house standards. Additionally it
|
||
should LINT-out cleanly enough.
|
||
|
||
The cost of the source code is $10.00 George Bush United States
|
||
Dollars (foreign currency is also okay provided it's around the
|
||
same ballpark.) The source code is shipped on a 3.5inch
|
||
floppy, zipped-up, with multiple copies for safety. Checks
|
||
okay. Will also take any kind of books in trade for the source
|
||
code.
|
||
|
||
Fredric L. Rice (frice@stbbs.com or frice@linkline.com)
|
||
StarGoat Industries
|
||
Care Of E. I. USA.
|
||
13000 Pierce Street
|
||
Pacoima, California.
|
||
91331
|
||
|
||
-----------------------------------------------------------------
|
||
|
||
FIDONEWS 14-03 Page 6 20 Jan 1997
|
||
|
||
|
||
=================================================================
|
||
GETTING TECHNICAL
|
||
=================================================================
|
||
|
||
|
||
[This is part of a continuing series publishing FidoNet Technical
|
||
Standards and Proposals as part of our FidoNet History. They have
|
||
been reformatted to meet the 70 column limit where necessary.] Ed.
|
||
|
||
FSC-0020
|
||
|
||
Alternate Nodelist Flag Proposal
|
||
|
||
by Marshall Presnell
|
||
(109/639.106)
|
||
|
||
November 13, 1987
|
||
|
||
Permission to reprint and distribute this document is
|
||
granted so long as no payments are incurred for the use and
|
||
distribution of this document and the author is credited.
|
||
|
||
$Revision: 1.1 $
|
||
|
||
$Log: E:/SRC/NLPROC/PROJFILE/NODELIST.PRV $
|
||
|
||
Rev 1.1 13 Nov 1987 15:50:56 M. Presnell
|
||
Added Update log into document body
|
||
|
||
------------------------------------------------------------
|
||
|
||
NODELIST FLAGS
|
||
A Proposal
|
||
|
||
In order to properly code a function to read and interpret
|
||
the nodelist flags, several vexing problems arise. The most
|
||
significant problem is simply figuring out the capabilities
|
||
of the software running at a particular node. In order to
|
||
solve this confusion, I propose the following standards to
|
||
be accepted by the FTSC, IFNA, and any other anciliary
|
||
organizations which contribute to the content and
|
||
maintenance of the nodelist.
|
||
|
||
First, a code needs to be established for each piece of
|
||
NETMAIL PROTOCOL CAPABLE software. This defines exactly WHAT
|
||
will answer the phone and transfer mail according to FTSC
|
||
netmail protocol standards. For the current arena of
|
||
software, I propose the flag and operand approach as
|
||
follows:
|
||
|
||
ST: <- the FLAG, ST meaning System Type
|
||
|
||
Operands:
|
||
|
||
FD1 - Fido Version 11?
|
||
FD2 - Fido Version 12?
|
||
FIDONEWS 14-03 Page 7 20 Jan 1997
|
||
|
||
|
||
SD? - SEAdog version ?
|
||
OP1 - Opus version 1.?
|
||
BT? - BinkleyTerm version ?
|
||
TY? - Tabby version ?
|
||
DT? - Dutchie version ?
|
||
(and others as needed, apologies to those I omitted)
|
||
|
||
Therefore, the complete type flag would read:
|
||
|
||
ST:FD2 for Fido v12x
|
||
ST:OP1 for Opus version 1.xx
|
||
ST:SD4 for SEAdog version 4.x
|
||
|
||
This gives the nodelist processor (and we illogical
|
||
humans) a much easier time in interpreting the
|
||
nodelist. I also recommend that the operands be of a
|
||
set length (in the above example, 3 characters).
|
||
|
||
Second, a PROTOCOL code needs to be established, using the
|
||
same FLAG:OPERAND approach as the system type flag. In this
|
||
case:
|
||
|
||
PR: <- The FLAG, meaning PRotocol
|
||
|
||
and the operands:
|
||
|
||
TS - TSYNC (Fido v11 and v12)
|
||
SL - SEAdog Link (SEAdog)
|
||
WZ - WaZoo (Opus)
|
||
others as the technology progresses.
|
||
|
||
The operand field may contain multiple operands, as
|
||
follows:
|
||
|
||
PR:WZ/TS <- to indicate an Opus system
|
||
|
||
In the event of multiple operands, the most desired
|
||
protocol for network communications should be first in
|
||
the list of operands.
|
||
|
||
Third, the operation hours, as before in a FLAG:OPERAND
|
||
combination as follows:
|
||
|
||
OH: <- Operation Hours
|
||
|
||
This flag is followed by the operation hours of the
|
||
system regarding inbound MAIL only. The operation hours
|
||
are in a fixed format as follows:
|
||
|
||
D.HHMM-D.HHMM
|
||
|
||
where D is the day number (Sunday being 1), HH is the
|
||
24 hour military hour, and MM is the minute. A special
|
||
case of the day being 0 means all days 1 through 7. ALL
|
||
times are EST (purely arbitrary, but ALL times in the
|
||
nodelist should have a common base reference time).
|
||
FIDONEWS 14-03 Page 8 20 Jan 1997
|
||
|
||
|
||
Therefore, a system which runs national mail time only
|
||
would be as follows:
|
||
|
||
OH:0.0400-0.0500
|
||
|
||
Multiple operational hours may be specified by
|
||
separating the separate time specifiers with a slash
|
||
as follows:
|
||
|
||
OH:D.HHMM-D.HHMM/D.HHMM-D.HHMM/D.HHMM-D.HHMM
|
||
|
||
Continuous inbound mail would be indicated as follows:
|
||
|
||
OH:1.0000-7.2359
|
||
|
||
It is important to note that these times are when the
|
||
system is able to RECEIVE mail. These are NOT the
|
||
actual operation hours of the BBS (if one exists at
|
||
that node).
|
||
|
||
The time known as National Mail Hour (04:00 to 05:00
|
||
EST) is automatically ASSUMED and need not be
|
||
incorporated into the FLAGS field. Since it is one of
|
||
the baseline requirements for being listed in the
|
||
nodelist, this assumption is a relatively safe one.
|
||
|
||
Also, this method should also be used to indicate the
|
||
time(s) when File Requests are accepted. The suggested
|
||
flag for File Requests is "FR:" and follows the same
|
||
time specification logic as the OH: flag.
|
||
|
||
Fourth, modem flags need to be standardized (until the
|
||
modems themselves can be standardized), for a hopefully
|
||
"stop gap" measure, we could use the following:
|
||
|
||
MDM: for the flag,
|
||
|
||
TLB for Telebit Trailblazer
|
||
HST for USR Courier HST
|
||
H96 for Hayes 9600
|
||
(and others as needed)
|
||
|
||
Only ONE of these modem types can appear per node, and
|
||
it has no relavence unless the baud rate is greater
|
||
than or equal to 9600.
|
||
|
||
(This is one of those flags we can get rid of once the
|
||
modem manufacturors establish a standard.)
|
||
|
||
Fifth, the Mail Only flag. Basically, it need to be changed
|
||
to "#MO" instead of "MO:". All flags which do not have
|
||
operands should not contain the colon (:) character.
|
||
|
||
Flags occur following the seventh comma in a nodelist line
|
||
and continue to the end of the physical line. All flags and
|
||
flag:operand combinations are separated by commas, with the
|
||
FIDONEWS 14-03 Page 9 20 Jan 1997
|
||
|
||
|
||
last flag on the line terminated by the end of line
|
||
character. Order of the flags is not critical.
|
||
|
||
------------------------------------------------------------
|
||
|
||
I hope this proposal will serve to elicit ideas and comment.
|
||
Please direct any inaccuracies, suggestions for improvement,
|
||
comments, and constructive criticism to Marshall Presnell
|
||
at Fido node 109/639.106
|
||
|
||
Thank you.
|
||
|
||
-30-
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
-----------------------------------------------------------------
|
||
|
||
|
||
VFOSSIL - An OS/2-Subset Video FOSSIL Appendage
|
||
|
||
Version 1.00, May 23, 1988
|
||
|
||
Rick Moore, Solar Wind Computing
|
||
FidoNet Address: 1:115/333
|
||
|
||
FidoNet Standards Committee index: FSC-0021
|
||
|
||
Copyright (C) 1988, Rick Moore, Homewood, IL, 60430. All rights
|
||
reserved.
|
||
|
||
This document may be distributed freely as long as it is distributed
|
||
FIDONEWS 14-03 Page 10 20 Jan 1997
|
||
|
||
|
||
in its original, unmodified form.
|
||
|
||
VFOSSIL design criteria:
|
||
|
||
The VFOSSIL appendage proposed here is designed to be an compatible
|
||
subset of the OS/2 VIO subsystem. All services are proper subsets of
|
||
the equivalent OS/2 VIO API's, and if you stick to the services
|
||
defined in this document, you will be able to compile and run your
|
||
programs with very minor changes in an OS/2 environment.
|
||
|
||
VFOSSIL (and OS/2 VIO at this time) only supports text modes. It is
|
||
possible to use the "set mode" service to set a graphics mode, but
|
||
that is the only support for pixel-oriented graphics functions
|
||
provided by VFOSSIL. The minimum environment supported by VFOSSIL is
|
||
a 80 by 24 monochrome text screen, and any program using VFOSSIL
|
||
calls should be capable of operating within this level of support. By
|
||
querying the VFOSSIL, the full capabilities of a specific
|
||
implementation may be determined and used, but all programs using
|
||
VFOSSIL should be capable of operating with the 80 by 24 monochrome
|
||
text environment.
|
||
|
||
|
||
The organization of the video screen:
|
||
|
||
The virtual screen is organized in rows of columns of
|
||
character/attribute pairs, hereafter referred to as cells. The
|
||
characters actually displayed are located on the even addresses, the
|
||
attribute for each character is located at character+1.
|
||
|
||
Regardless of the manner in which the video screen is actually
|
||
organized, the programmer will view it as a a contiguous area of
|
||
memory, referred to as the "logical video buffer" (LVB). The LVB is
|
||
(NumRow * NumCol) cells in length.
|
||
|
||
VFOSSIL installation:
|
||
|
||
The VFOSSIL appendage is installed via the standard FOSSIL external
|
||
application function. The FOSSIL interrupt (14h) is issued with the
|
||
following parameters:
|
||
|
||
AH = 7Eh Install appendage
|
||
AL = 81h VFOSSIL application code
|
||
DX = offset of VFOSSIL entry point
|
||
ES = segment of VFOSSIL entry point
|
||
|
||
Upon return from the FOSSIL interrupt, the following registers are
|
||
modified:
|
||
|
||
AX = 1954h FOSSIL signature
|
||
BL = 81h VFOSSIL application code
|
||
BH = 01h - Installation was successful
|
||
00h - Installation was unsuccessful
|
||
|
||
VFOSSIL removal:
|
||
|
||
The VFOSSIL appendage is removed via the standard FOSSIL external
|
||
FIDONEWS 14-03 Page 11 20 Jan 1997
|
||
|
||
|
||
application function. The FOSSIL interrupt (14h) is issued with the
|
||
following parameters:
|
||
|
||
AH = 7Fh Remove appendage
|
||
AL = 81h VFOSSIL application code
|
||
DX = offset of VFOSSIL entry point
|
||
ES = segment of VFOSSIL entry point
|
||
|
||
Upon return from the FOSSIL interrupt, the following registers are
|
||
modified:
|
||
|
||
AX = 1954h FOSSIL signature
|
||
BL = 81h VFOSSIL identification code
|
||
BH = 01h - Removal was successful
|
||
00h - Removal was unsuccessful
|
||
|
||
VFOSSIL functions called via the standard FOSSIL interrupt (14h):
|
||
|
||
The following three functions are called via the standard FOSSIL
|
||
interrupt, int 14h. All other VFOSSIL functions are called via the
|
||
OS/2 compatible direct call interface.
|
||
|
||
Subfunction 00h - Return VFOSSIL information
|
||
|
||
Entry: AH = 81h VFOSSIL application code
|
||
AL = 00h VFOSSIL subfunction
|
||
ES:DI = Far pointer to VFOSSIL information structure
|
||
|
||
Exit: AX = 1954h FOSSIL signature
|
||
|
||
This function is used before calling the open function (sub-
|
||
function 01h) to determine the characteristics of the VFOSSIL. Such
|
||
things returned in the structure are current version level and number
|
||
of functions supported.
|
||
|
||
The format of the information structure filled in by this call is
|
||
as follows:
|
||
|
||
DW Size of this structure, in bytes, including this
|
||
field
|
||
DW VFOSSIL major version
|
||
DW VFOSSIL revision level
|
||
DW Highest VFOSSIL application function supported
|
||
|
||
Subfunction 01h - Open VFOSSIL
|
||
|
||
Entry: AH = 81h VFOSSIL application code
|
||
AL = 01h VFOSSIL subfunction
|
||
CX = Length of application function table (in bytes)
|
||
ES:DI = Far pointer to application function table
|
||
|
||
Exit: BH = Highest VFOSSIL application function supported
|
||
AX = 1954h FOSSIL signature
|
||
|
||
This VFOSSIL subfunction will initialize the table pointed to
|
||
by ES:DI with far pointers to the VFOSSIL application services.
|
||
FIDONEWS 14-03 Page 12 20 Jan 1997
|
||
|
||
|
||
The number of far pointers initialized is equal to the value
|
||
returned in register BH + 1. Under no circumstances will the number
|
||
of far pointers initialized exceed the value passed in register
|
||
CX / 4. All other processing necessary to ready the VFOSSIL for use
|
||
by the application program should be performed at this time.
|
||
|
||
Subfunction 02h - Close VFOSSIL
|
||
|
||
Entry: AH = 81h VFOSSIL application code
|
||
AL = 02h VFOSSIL subfunction
|
||
|
||
Exit: AX = 1954h FOSSIL signature
|
||
|
||
This VFOSSIL function terminates all VFOSSIL operations, and
|
||
leaves the VFOSSIL in a state that allows for it to be removed from
|
||
memory, or to be reinitialized via VFOSSIL function 01h.
|
||
|
||
VFOSSIL application services:
|
||
|
||
All calls to VFOSSIL services are made in a manner identical to the
|
||
OS/2 API protocol. All services are entered via a far call, with
|
||
parameters passed via the stack. All services return an error code in
|
||
register AX. The parameters are pushed onto the stack Pascal-style,
|
||
from left to right. The parameters are passed on the stack in one of
|
||
the three following ways:
|
||
|
||
WORD A one-word value pushed directly onto the stack
|
||
|
||
DWRD A double-word value pushed directly onto the stack
|
||
(low word first, followed by the high word)
|
||
|
||
PTR A far pointer to a memory area. Far pointers are passed
|
||
as double-word values, segment followed by offset.
|
||
|
||
Single-word and double-word input parameters are always passed as WORD
|
||
and DWRD. If the service returns information in the parameter field
|
||
itself, then it is pushed as a PTR, even if the object is a WORD or a
|
||
DWRD. Variable length parameters, such as data structures or ASCIIZ
|
||
strings, are always passed as PTR objects.
|
||
|
||
All cursor coordinates are expressed as zero (0) based numbers.
|
||
|
||
Each VFOSSIL service requires a "handle" parameter as the last
|
||
parameter passed to the service. At this time, zero (0) is the only
|
||
valid handle.
|
||
|
||
The actual addresses used to call the application services are
|
||
contained in the address table filled in by the VFOSSIL initialization
|
||
call described above. All addresses are in far (segment/offset)
|
||
format. Here is the format of the application service address table:
|
||
|
||
Table +00h VioGetMode Query current video mode
|
||
+04h VioSetMode Set video mode
|
||
+08h VioGetConfig Query video hardware
|
||
configuration
|
||
+0Ch VioWrtTTY Write data in TTY mode
|
||
FIDONEWS 14-03 Page 13 20 Jan 1997
|
||
|
||
|
||
+10h VioGetANSI Query current ANSI state
|
||
+14h VioSetANSI Set ANSI state
|
||
+18h VioGetCurPos Query current cursor position
|
||
+1Ch VioSetCurPos Set cursor position
|
||
+20h VioGetCurType Query current cursor
|
||
parameters
|
||
+24h VioSetCurType Set cursor parameters
|
||
+28h VioScrollUp Scroll screen up
|
||
+2Ch VioScrollDn Scroll screen down
|
||
+30h VioReadCellStr Read cell string from display
|
||
+34h VioReadCharStr Read char string from display
|
||
+38h VioWrtCellStr Write cell string
|
||
+3Ch VioWrtCharStr Write char string (existing
|
||
attributes)
|
||
+40h VioWrtCharStrAtt Write char string (constant
|
||
attributes)
|
||
+44h VioWrtNAttr Replicate attribute
|
||
+48h VioWrtNCell Replicate cell
|
||
+4Ch VioWrtNChar Replicate char
|
||
|
||
VioGetMode - Query current video mode
|
||
|
||
Parameters:
|
||
|
||
PTR Pointer to a video mode data structure
|
||
WORD VIO handle (must be 0)
|
||
|
||
|
||
Video mode data structure:
|
||
|
||
DW Structure length (including this field)
|
||
DB Mode characteristics
|
||
-------0 Monochrome/printer adapter
|
||
-------1 Other adapter
|
||
------0- Text mode
|
||
------1- Graphics mode
|
||
-----0-- Enable color
|
||
-----1-- Disable color (black and white)
|
||
DB Number of colors supported by the display
|
||
1 = 2 colors
|
||
2 = 4 colors
|
||
4 = 16 colors
|
||
DW Number of text columns
|
||
DW Number of text rows
|
||
DW Reserved
|
||
DW Reserved
|
||
DD Reserved
|
||
|
||
|
||
A partial video mode buffer may be specified. VFOSSIL returns only
|
||
the data that will fit into the buffer. The minimum buffer length is
|
||
3, and the maximum buffer length is 12. Partial fields are not
|
||
returned.
|
||
|
||
|
||
Error codes returned:
|
||
FIDONEWS 14-03 Page 14 20 Jan 1997
|
||
|
||
|
||
0 - Successful completion
|
||
116 - Internal VIO failure
|
||
382 - Buffer too small
|
||
436 - Invalid VIO handle
|
||
|
||
VioSetMode - Set video mode
|
||
|
||
Parameters:
|
||
|
||
PTR Pointer to a video mode data structure (see
|
||
VioGetMode)
|
||
WORD VIO handle (must be 0)
|
||
|
||
|
||
A partial video mode buffer may be specified. The minimum buffer
|
||
length is 3, and the maximum buffer length is 12. Partial fields are
|
||
not supported. The remaining fields are set to default values.
|
||
|
||
|
||
Error codes returned:
|
||
|
||
0 - Successful completion
|
||
116 - Internal VIO failure
|
||
355 - Unsupported mode
|
||
382 - Buffer too small
|
||
421 - Invalid VIO parameter
|
||
436 - Invalid VIO handle
|
||
|
||
VioGetConfig - Query video hardware configuration
|
||
|
||
Parameters:
|
||
|
||
PTR Pointer to a video configuration data area
|
||
WORD VIO handle (must be 0)
|
||
|
||
|
||
Video configuration data area:
|
||
|
||
DW Structure length (includes this field)
|
||
DW Adapter type
|
||
0 = Monochrome/printer
|
||
1 = CGA
|
||
2 = EGA
|
||
3 = VGA
|
||
7 = 8514A
|
||
DW Display type
|
||
0 = Monochrome
|
||
1 = Color
|
||
2 = Enhanced color
|
||
9 = 8514
|
||
DD Adapter memory size
|
||
|
||
|
||
Error codes returned:
|
||
|
||
0 - Successful completion
|
||
FIDONEWS 14-03 Page 15 20 Jan 1997
|
||
|
||
|
||
116 - Internal VIO failure
|
||
382 - Buffer too small
|
||
436 - Invalid VIO handle
|
||
|
||
VioWriteTTY - Write data in TTY mode
|
||
|
||
Parameters:
|
||
|
||
WORD Pointer to a character string that VFOSSIL will write
|
||
to the screen
|
||
WORD String length
|
||
WORD VIO handle (must be 0)
|
||
|
||
|
||
This service writes a string to the video screen in TTY mode. The
|
||
characters CR, LF, BS, TAB, and BELL are interpreted as control
|
||
values rather than being display as values. If ANSI mode has been
|
||
enabled (see VioGetANSI, VioSetANSI), then ANSI control sequences are
|
||
also interpreted as control strings. In ANSI mode, this service is
|
||
not required to be reentrant, and should not be called when a MS/DOS
|
||
function is in progress. When in non-ANSI mode, this service is
|
||
required to be reentrant, and may be called from within a MS/DOS
|
||
function. If the write goes beyond the end of a line, it continues at
|
||
the start of the next line. The write terminates at the end of the
|
||
screen. The cursor is left positioned at the next character position
|
||
to be written.
|
||
|
||
|
||
Error codes returned:
|
||
|
||
0 - Successful completion
|
||
116 - Internal VIO failure
|
||
436 - Invalid VIO handle
|
||
|
||
VioGetANSI - Query current ANSI state
|
||
|
||
Parameters:
|
||
|
||
PTR Pointer to a one-word field in which VFOSSIL will
|
||
return the current ANSI state:
|
||
0 = Off
|
||
1 = On
|
||
WORD VIO handle (must be 0)
|
||
|
||
|
||
Error codes returned:
|
||
|
||
0 - Successful completion
|
||
116 - Internal VIO failure
|
||
436 - Invalid VIO handle
|
||
|
||
VioSetANSI - Set ANSI state
|
||
|
||
Parameters:
|
||
|
||
PTR Pointer to a one-word field indicating how ANSI
|
||
FIDONEWS 14-03 Page 16 20 Jan 1997
|
||
|
||
|
||
processing is to be set:
|
||
0 = Off
|
||
1 = On
|
||
WORD VIO handle (must be 0)
|
||
|
||
|
||
Error codes returned:
|
||
|
||
0 - Successful completion
|
||
116 - Internal VIO failure
|
||
421 - Invalid VIO parameter
|
||
436 - Invalid VIO handle
|
||
|
||
VioGetCurPos - Query current cursor position
|
||
|
||
Parameters:
|
||
|
||
PTR Pointer to a one word field in which VFOSSIL will
|
||
return the current cursor row
|
||
PTR Pointer to a one word field in which VFOSSIL will
|
||
return the current cursor column
|
||
WORD VIO handle (must be 0)
|
||
|
||
|
||
This service returns the current cursor position. Cursor coordinates
|
||
are zero based.
|
||
|
||
|
||
Error codes returned:
|
||
|
||
0 - Successful completion
|
||
116 - Internal VIO failure
|
||
436 - Invalid VIO handle
|
||
|
||
VioSetCurPos - Set cursor position
|
||
|
||
Parameters:
|
||
|
||
WORD Desired cursor row
|
||
WORD Desired cursor column
|
||
WORD VIO handle (must be 0)
|
||
|
||
|
||
This service sets the cursor position to the zero based coordinates
|
||
specified by the parameters. If either of the parameters is invalid,
|
||
the cursor position is left unchanged.
|
||
|
||
|
||
Error codes returned:
|
||
|
||
0 - Successful completion
|
||
116 - Internal VIO failure
|
||
358 - Invalid row value
|
||
359 - Invalid column value
|
||
436 - Invalid VIO handle
|
||
|
||
FIDONEWS 14-03 Page 17 20 Jan 1997
|
||
|
||
|
||
VioGetCurType - Query current cursor parameters
|
||
|
||
|
||
Parameters:
|
||
|
||
PTR Pointer to a cursor type data area
|
||
WORD VIO handle (must be 0)
|
||
|
||
|
||
Cursor type data area:
|
||
|
||
DW Cursor start line
|
||
DW Cursor end line
|
||
DW Cursor width (always 1)
|
||
DW Cursor attribute (-1 = hidden)
|
||
|
||
|
||
Error codes returned:
|
||
|
||
0 - Successful completion
|
||
116 - Internal VIO failure
|
||
436 - Invalid VIO handle
|
||
|
||
VioSetCurType - Set cursor parameters
|
||
|
||
Parameters:
|
||
|
||
PTR Pointer to a cursor type data area (see VioGetCurType)
|
||
WORD VIO handle (must be 0)
|
||
|
||
|
||
Error codes returned:
|
||
|
||
0 - Successful completion
|
||
116 - Internal VIO failure
|
||
421 - Invalid VIO parameter
|
||
436 - Invalid VIO handle
|
||
|
||
VioScrollUp - Scroll screen up
|
||
|
||
Parameters:
|
||
|
||
WORD Top row of the scroll area
|
||
WORD Left column of the scroll area
|
||
WORD Bottom row of the scroll area
|
||
WORD Right column of the scroll area
|
||
WORD Number of rows to scroll. A value of -1 causes the
|
||
scroll area to be cleared.
|
||
PTR Pointer to a char/attr cell that is used to fill the
|
||
scroll area.
|
||
WORD VIO handle (always 0)
|
||
|
||
|
||
Error codes returned:
|
||
|
||
0 - Successful completion
|
||
FIDONEWS 14-03 Page 18 20 Jan 1997
|
||
|
||
|
||
116 - Internal VIO failure
|
||
358 - Invalid row value
|
||
359 - Invalid column value
|
||
436 - Invalid VIO handle
|
||
|
||
VioScrollDn - Scroll screen down
|
||
|
||
Parameters:
|
||
|
||
WORD Top row of the scroll area
|
||
WORD Left column of the scroll area
|
||
WORD Bottom row of the scroll area
|
||
WORD Right column of the scroll area
|
||
WORD Number of rows to scroll. A value of -1 causes the
|
||
scroll area to be cleared.
|
||
PTR A pointer to a char/attr cell that is used to fill the
|
||
scroll area.
|
||
WORD VIO handle (always 0)
|
||
|
||
|
||
Error codes returned:
|
||
|
||
0 - Successful completion
|
||
116 - Internal VIO failure
|
||
358 - Invalid row value
|
||
359 - Invalid column value
|
||
436 - Invalid VIO handle
|
||
|
||
VioReadCellStr - Read cell string from display
|
||
|
||
Parameters:
|
||
|
||
PTR Pointer to a buffer into which the cell string is to
|
||
be placed
|
||
PTR Pointer to a one-word field which, upon entry,
|
||
specifies the length of the cell buffer (in bytes),
|
||
and, on return, contains the number of bytes actually
|
||
read. Each cell occupies two bytes, so the number of
|
||
cells read is equal to half of the buffer length
|
||
specified.
|
||
WORD Row where the read is to start
|
||
WORD Column where the read is to start
|
||
WORD VIO handle (always 0)
|
||
|
||
|
||
If the read request extends beyond the end of the line, it continues
|
||
at the first column of the next line. If an attempt is made to read
|
||
past the end of the screen, the read operation terminates and the
|
||
length field is set to the actual number of bytes read.
|
||
|
||
|
||
Error codes returned:
|
||
|
||
0 - Successful completion
|
||
116 - Internal VIO failure
|
||
358 - Invalid row value
|
||
FIDONEWS 14-03 Page 19 20 Jan 1997
|
||
|
||
|
||
359 - Invalid column value
|
||
436 - Invalid VIO handle
|
||
|
||
VioReadCharStr - Read character string from display
|
||
|
||
Parameters:
|
||
|
||
PTR Pointer to a buffer into which the character string is
|
||
to be placed
|
||
PTR Pointer to a one-word field which, upon entry,
|
||
specifies how many characters are to be read, and,
|
||
on return, contains the number of characters actually
|
||
read.
|
||
WORD Row where the read is to start
|
||
WORD Column where the read is to start
|
||
WORD VIO handle (always 0)
|
||
|
||
|
||
If the read request extends beyond the end of the line, it continues
|
||
at the first column of the next line. If an attempt is made to read
|
||
past the end of the screen, the read operation terminates and the
|
||
length field is set to the actual number of characters read.
|
||
|
||
|
||
Error codes returned:
|
||
|
||
0 - Successful completion
|
||
116 - Internal VIO failure
|
||
358 - Invalid row value
|
||
359 - Invalid column value
|
||
436 - Invalid VIO handle
|
||
|
||
VioWrtCellStr - Write a cell string
|
||
|
||
Parameters:
|
||
|
||
PTR Pointer to the cell string to be written
|
||
WORD Cell string length. Since each cell occupies two
|
||
bytes, this number is twice the number of cells to be
|
||
written.
|
||
WORD Row at which write is to begin
|
||
WORD Column at which write is to begin
|
||
WORD Vio handle (must be 0)
|
||
|
||
|
||
If the write request extends beyond the end of the line, it continues
|
||
at the first column of the next line. If an attempt is made to write
|
||
past the end of the screen, the write operation terminates.
|
||
|
||
|
||
Error codes returned:
|
||
|
||
0 - Successful completion
|
||
116 - Internal VIO failure
|
||
358 - Invalid row value
|
||
359 - Invalid column value
|
||
FIDONEWS 14-03 Page 20 20 Jan 1997
|
||
|
||
|
||
436 - Invalid VIO handle
|
||
|
||
VioWrtCharStr - Write a character string, using existing attributes
|
||
|
||
Parameters:
|
||
|
||
PTR Pointer to the character string to be written
|
||
WORD Character string length
|
||
WORD Row at which write is to begin
|
||
WORD Column at which write is to begin
|
||
WORD Vio handle (must be 0)
|
||
|
||
|
||
The attributes of the display cells whose characters are replaced are
|
||
not modified. If the write request extends beyond the end of the
|
||
line, it continues at the first column of the next line. If an
|
||
attempt is made to write past the end of the screen, the write
|
||
operation terminates.
|
||
|
||
|
||
Error codes returned:
|
||
|
||
0 - Successful completion
|
||
116 - Internal VIO failure
|
||
358 - Invalid row value
|
||
359 - Invalid column value
|
||
436 - Invalid VIO handle
|
||
|
||
VioWrtCharStrAtt - Write a character string, using constant attribute
|
||
|
||
Parameters:
|
||
|
||
PTR Pointer to the character string to be written
|
||
WORD Character string length
|
||
WORD Row at which write is to begin
|
||
WORD Column at which write is to begin
|
||
PTR Pointer to the display attribute to be used with each
|
||
character written
|
||
WORD Vio handle (must be 0)
|
||
|
||
|
||
If the write request extends beyond the end of the line, it continues
|
||
at the first column of the next line. If an attempt is made to write
|
||
past the end of the screen, the write operation terminates.
|
||
|
||
|
||
Error codes returned:
|
||
|
||
0 - Successful completion
|
||
116 - Internal VIO failure
|
||
358 - Invalid row value
|
||
359 - Invalid column value
|
||
436 - Invalid VIO handle
|
||
|
||
VioWrtNAttr - Replicate an attribute byte, leaving characters
|
||
unchanged
|
||
FIDONEWS 14-03 Page 21 20 Jan 1997
|
||
|
||
|
||
Parameters:
|
||
|
||
PTR Pointer to the display attribute to be replicated
|
||
WORD Replication count
|
||
WORD Row at which write is to begin
|
||
WORD Column at which write is to begin
|
||
WORD Vio handle (must be 0)
|
||
|
||
|
||
The characters contained in the display cells whose attributes are
|
||
replaced are not modified. If the write request extends beyond the
|
||
end of the line, it continues at the first column of the next line.
|
||
If an attempt is made to write past the end of the screen, the write
|
||
operation terminates.
|
||
|
||
|
||
Error codes returned:
|
||
|
||
0 - Successful completion
|
||
116 - Internal VIO failure
|
||
358 - Invalid row value
|
||
359 - Invalid column value
|
||
436 - Invalid VIO handle
|
||
|
||
VioWrtNCell - Replicate a cell
|
||
|
||
Parameters:
|
||
|
||
PTR Pointer to the cell to be replicated
|
||
WORD Replication count
|
||
WORD Row at which write is to begin
|
||
WORD Column at which write is to begin
|
||
WORD Vio handle (must be 0)
|
||
|
||
|
||
If the write request extends beyond the end of the line, it continues
|
||
at the first column of the next line. If an attempt is made to write
|
||
past the end of the screen, the write operation terminates.
|
||
|
||
|
||
Error codes returned:
|
||
|
||
0 - Successful completion
|
||
116 - Internal VIO failure
|
||
358 - Invalid row value
|
||
359 - Invalid column value
|
||
436 - Invalid VIO handle
|
||
|
||
VioWrtNChar - Replicate an character, leaving attributes unchanged
|
||
|
||
Parameters:
|
||
|
||
PTR Pointer to the character to be replicated
|
||
WORD Replication count
|
||
WORD Row at which write is to begin
|
||
WORD Column at which write is to begin
|
||
FIDONEWS 14-03 Page 22 20 Jan 1997
|
||
|
||
|
||
WORD Vio handle (must be 0)
|
||
|
||
|
||
The attributes contained in the display cells whose characters are
|
||
replaced are not modified. If the write request extends beyond the
|
||
end of the line, it continues at the first column of the next line.
|
||
If an attempt is made to write past the end of the screen, the write
|
||
operation terminates.
|
||
|
||
|
||
Error codes returned:
|
||
|
||
0 - Successful completion
|
||
116 - Internal VIO failure
|
||
358 - Invalid row value
|
||
359 - Invalid column value
|
||
436 - Invalid VIO handle
|
||
|
||
-30-
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
-----------------------------------------------------------------
|
||
|
||
|
||
Date: 11 Jul 88 00:30:18
|
||
From: Roeland Meyer on 132/101, BBS Source Ar of New England-N, Nashua
|
||
NH
|
||
To: Randy Bush on 105/6, DawgGone Disg of VanPort Net, Portland OR
|
||
Subj: Bundle name format
|
||
|
||
I thought I'd bring back something we discussed a few months ago for
|
||
your enjoyment. I am doing a router and thought I might try to add
|
||
this capability as an option.
|
||
|
||
As you can see, this is already part of a .H file. The router will
|
||
only build this type of bundle if specifically told to do so.
|
||
Otherwise, it will build a standard Opus style bundle. It will be able
|
||
to process a mix of both types.
|
||
|
||
Oh yeah, the router will also "peek" at the Inbound area for any
|
||
PassThru bundles. The router is specifically designed to work with
|
||
Binkley as the mailer. There is no nonsense about delta addresses and
|
||
such. The name of the bundle is the address of where it has to go. If
|
||
this is not the current system then the router will tell Binkley to
|
||
send it.
|
||
|
||
If there exists a bundle of the same name and sequence number on the
|
||
target machine then Binkley will automatically increment the sequence
|
||
number. This is a current feature of Binkley.
|
||
|
||
Notice the special Flags for Files and EchoMail. The router will allow
|
||
FIDONEWS 14-03 Page 23 20 Jan 1997
|
||
|
||
|
||
routing for both, if desired. There is also full Zone and Point
|
||
support, something which oMMM is desparately lacking.
|
||
|
||
There are three major routing goals:
|
||
1) least cost routing.
|
||
2) Conservation of disk space.
|
||
3) Zone and Point support.
|
||
|
||
How do I propose this nameing convention to the FTSC?
|
||
|
||
/*********************************************************************
|
||
|
||
New address specifier
|
||
This is designed for the new bundle nameing convention of
|
||
|
||
ZNNNOOPP.Fxx
|
||
| | | | ||
|
||
| | | | |`--> Incrementing sequence number, base 10, max =
|
||
99d
|
||
| | | | | Starts at 0 and counts to '99' then
|
||
wraps
|
||
| | | | | back to 0. No "Day-of-week" bullshit.
|
||
| | | | | This is strictly to avoid bundle
|
||
collisions.
|
||
| | | | | An 'empty' version of the bundle is kept
|
||
| | | | | around to help the router remember what
|
||
the
|
||
| | | | | last sequence number was.
|
||
| | | | |
|
||
| | | | `-----> Flag to indicate bundle type
|
||
| | | | Allowed values:
|
||
| | | | '1' to 'V' are not allowed here.
|
||
| | | | 'W' - <Reserved>
|
||
| | | | 'X' - File bundle
|
||
| | | | 'Y' - Echo Mail bundle
|
||
| | | | 'Z' - Normal mail bundle
|
||
| | | |
|
||
| | | `--------> Point address, base 32, max = 1,024d
|
||
| | | Allowed values: '00' to 'VV'
|
||
| | | This is the Point part of the
|
||
destination
|
||
| | | address of the bundle.
|
||
| | | Special values:
|
||
| | | '00' - Destination is the Node given by
|
||
| | | ZNNNOO, not forwarded to any
|
||
Points.
|
||
| | | 'VV' - This a broadcast bundle to ALL
|
||
Points
|
||
| | | under the Node given by ZNNNOO,
|
||
as
|
||
| | | well as, the Node given by same.
|
||
| | |
|
||
| | `----------> Node address, base 32, max = 1,024d
|
||
| | Allowed values: '00' to 'VV'
|
||
| | This is the Node part of the destination
|
||
| | address of the bundle.
|
||
FIDONEWS 14-03 Page 24 20 Jan 1997
|
||
|
||
|
||
| | Special values:
|
||
| | '00' - Destination is the Net Host
|
||
given by
|
||
| | ZNNN, not forwarded to any
|
||
Nodes.
|
||
| | 'VV' - This a broadcast bundle to ALL
|
||
Nodes
|
||
| | in the Net given by ZNNN, as
|
||
| | well as, the Net Host given by
|
||
same.
|
||
| |
|
||
| `------------> Net address, base 32, max = 33,824d
|
||
| Allowed values: '000' to 'VVV'
|
||
| This is the Net part of the destination
|
||
| address of the bundle.
|
||
| Special values:
|
||
| '000' - Destination is the ZoneGate
|
||
given by
|
||
| Z, not forwarded to any Nets.
|
||
| 'VVV' - This a broadcast bundle to ALL
|
||
Nets
|
||
| in the Zone given by Z, as well
|
||
as,
|
||
| the ZoneGate given by same.
|
||
|
|
||
`--------------> Zone address, base 32, max = 32d
|
||
Allowed values: '0' to 'V'
|
||
This is the Zone part of the destination
|
||
address of the bundle.
|
||
Special values:
|
||
'0' - Destination is the current
|
||
ZoneGate.
|
||
'V' - This a broadcast bundle to ALL
|
||
ZoneGates given by the NodeList,
|
||
as well as, the ZoneGate given by
|
||
same.
|
||
EXAMPLES:
|
||
|
||
10020304.Z01 - Destination = 1:2/3.4 Point 4 under 1:2/3
|
||
10020300.Z01 - Destination = 1:2/3.0 Node address Zone 1 Net 2 Node 3
|
||
10020000.Z01 - Destination = 1:2/0.0 Net Host of Zone 1 Net 2
|
||
10000000.Z01 - Destination = 1:0/0.0 ZoneGate of Zone 1
|
||
00000000.Z01 - Destination = 0:0/0.0 ZoneGate of current Zone
|
||
100203VV.Z01 - Destination = ALL Points under 1:2/3
|
||
1002VV00.Z01 - Destination = ALL Nodes under 1:2/0, no Points.
|
||
1VVV0000.Z01 - Destination = ALL Net Hosts in Zone 1 only, no one
|
||
else.
|
||
V0000000.Z01 - Destination = ALL ZoneGates in the Nodelist.
|
||
1002VVVV.Z01 - Destination = ALL Nodes and Points in Zone 1 Net 2.
|
||
1VVVVVVV.Z01 - Destination = ALL Points, Nodes, and Nets in Zone 1.
|
||
VVVVVVVV.Z01 - Destination = All Points, Nodes, and Nets in all
|
||
Zones.
|
||
VVVV0000.Z01 - Destination = All Net Hosts and ZoneGates in all Zones
|
||
only.
|
||
1002VVVV.Z01 - Destination = All Nodes and Points in Zone 1 Net 2.
|
||
1VVV00VV.Z01 - Destination = All Points on all NetHosts in Zone 1
|
||
FIDONEWS 14-03 Page 25 20 Jan 1997
|
||
|
||
|
||
0VVVVV00.Z01 - Destination = All Nets and Nodes in the current Zone
|
||
|
||
|
||
*********************************************************************/
|
||
|
||
typedef struct
|
||
{
|
||
Byte Zone ; /* Binary 00 to 32 Zone address */
|
||
Word Net ; /* Binary 00 to 33824 Net address */
|
||
Word Node ; /* Binary 00 to 1024 Node address */
|
||
Byte Point ; /* Binary 00 to 1024 Point address */
|
||
} NetAddr, *NetAddrPtr;
|
||
|
||
The router will only generate this type of bundle if it is told that a
|
||
particular target Node can accept it. If it receives this type of
|
||
bundle, and the router has not been told that the Node it is sending
|
||
to can process it, than the router will transform the bundle into the
|
||
current style of bundle acceptable by Opus. This means more
|
||
processing, but, should allow for a smoother transition.
|
||
|
||
--- ConfMail V3.31
|
||
* Origin: Computer Linguistics,Huntington Beach,CA (1:103/507.2)
|
||
|
||
-30-
|
||
|
||
-----------------------------------------------------------------
|
||
|
||
FIDONEWS 14-03 Page 26 20 Jan 1997
|
||
|
||
|
||
=================================================================
|
||
COORDINATORS CORNER
|
||
=================================================================
|
||
|
||
|
||
Nodelist-statistics as seen from Zone-2 for day 017
|
||
By Ward Dossche, 2:292/854
|
||
ZC/2
|
||
|
||
+----+------+------------+------------+------------+------------+--+
|
||
|Zone|Nl-355|Nodelist-362|Nodelist-003|Nodelist-010|Nodelist-017|%%|
|
||
+----+------+------------+------------+------------+------------+--+
|
||
| 1 | 10564|10452 -112 |10370 -82 |10370 0 |10177 -193 |35|
|
||
| 2 | 16127|16104 -23 |16056 -48 |15979 -77 |15936 -43 |55|
|
||
| 3 | 878| 876 -2 | 869 -7 | 868 -1 | 865 -3 | 3|
|
||
| 4 | 413| 556 143 | 552 -4 | 554 2 | 553 -1 | 2|
|
||
| 5 | 93| 93 0 | 93 0 | 93 0 | 93 0 | 0|
|
||
| 6 | 1003| 1075 72 | 1073 -2 | 1073 0 | 1073 0 | 4|
|
||
+----+------+------------+------------+------------+------------+--+
|
||
| 29078|29156 78 |29013 -143 |28937 -76 |28697 -240 |
|
||
+------+------------+------------+------------+------------+
|
||
|
||
-----------------------------------------------------------------
|
||
|
||
FIDONEWS 14-03 Page 27 20 Jan 1997
|
||
|
||
|
||
=================================================================
|
||
WE GET EMAIL
|
||
=================================================================
|
||
|
||
|
||
Here's a new way to get FidoNews via an email subscribe:
|
||
|
||
--- Following message extracted from FIDONEWS @ 1:18/14 ---
|
||
By Christopher Baker on Sun Jan 19 17:42:52 1997
|
||
|
||
From: jim barchuk
|
||
To: all
|
||
Date: 16 Jan 97 17:14:17
|
||
Subj: FidoDist - FidoNews via email
|
||
|
||
Hello, all, I'd like you to meet my friend, Harvey...
|
||
|
||
jb>> Chris, if you like, I could easily set up a 'subscribable'
|
||
jb>> distribution list to do that.
|
||
|
||
CB> great! keep us advised and thanks.
|
||
|
||
Okee doke. To subscribe to FidoDist - the FidoNews email distribution
|
||
list, send an email msg:
|
||
|
||
=======
|
||
|
||
To: jbarchuk@worldnet.att.net
|
||
Subject: subscribe fidodist
|
||
|
||
=======
|
||
|
||
That's it, nothing in the msg body.
|
||
|
||
To unsubscribe from the distribution list, send an email msg:
|
||
|
||
=======
|
||
|
||
To: jbarchuk@worldnet.att.net
|
||
Subject: unsubscribe fidodist
|
||
|
||
=======
|
||
|
||
That's it. Painless, eh? :)
|
||
|
||
:-)
|
||
|
||
jB-)
|
||
|
||
---
|
||
Origin: woc'in the path in the fifth age (1:141/355)
|
||
|
||
--- Following message extracted from FIDONEWS @ 1:18/14 ---
|
||
By Christopher Baker on Sun Jan 19 17:43:09 1997
|
||
|
||
From: jim barchuk
|
||
FIDONEWS 14-03 Page 28 20 Jan 1997
|
||
|
||
|
||
To: all
|
||
Date: 16 Jan 97 20:59:00
|
||
Subj: FidoDist - FidoNews via email
|
||
|
||
Hello, jim barchuk, I'd like you to meet my friend, Harvey...
|
||
|
||
jb> To: jbarchuk@worldnet.att.net
|
||
jb> Subject: subscribe fidodist
|
||
|
||
I have changed my mind about that name, not clear enough, should be:
|
||
|
||
fnews-edist
|
||
|
||
Subject: subscribe fnews-edist
|
||
|
||
:-)
|
||
|
||
jB-)
|
||
|
||
---
|
||
Origin: woc'in the path in the fifth age (1:141/355)
|
||
|
||
-30-
|
||
|
||
|
||
-----------------------------------------------------------------
|
||
|
||
|
||
--- Following message extracted from NETMAIL @ 1:18/14 ---
|
||
By Christopher Baker on Thu Jan 16 01:13:53 1997
|
||
|
||
From: Brian Patterson @ 1:317/103
|
||
To: Christopher Baker @ 1:18/14
|
||
Date: 15 Jan 97 22:20:02
|
||
Subj: Last of Good Times
|
||
|
||
Hello, Chris!
|
||
|
||
I saw this last night in the VIRUS echo. In the spirit of technical
|
||
cooperation so common to Fidonet, I thought I'd forward it to you for
|
||
inclusion in the next Fidonews. It contains the latest information on
|
||
that scourge of the e-mail system, the "Good Times" virus. The
|
||
latest research, quoted below, demonstrates that this virus is FAR
|
||
MORE dangerous then people had been led to believe!
|
||
|
||
* Forwarded from "VIRUS"
|
||
* Originally by Vic Von Abo, 5:7104/10
|
||
* Originally to All
|
||
* Originally dated 10 Jan 1997, 22:24
|
||
|
||
Hi Guys,
|
||
|
||
I know that this isn't a humor conf and neither do I think viruses are
|
||
funny, but after a spate of Good Times Virus Warnings I thought I
|
||
might share this with you. No hate mail pleez - Just enjoy.
|
||
|
||
FIDONEWS 14-03 Page 29 20 Jan 1997
|
||
|
||
|
||
"Goodtimes will re-write your hard drive. Not only that, but
|
||
it will scramble any disks that are even close to your computer. It
|
||
will recalibrate your refrigerator's coolness setting so all your
|
||
ice cream goes melty. It will demagnetize the strips on all your
|
||
credit cards, screw up the tracking on your television and use
|
||
subspace field harmonics to scratch any CD's you try to play.
|
||
|
||
It will give your ex-girlfriend your new phone number. It will mix
|
||
Kool-aid into your fishtank. It will drink all your beer and leave its
|
||
socks out on the coffee table when there's company coming over. It
|
||
will put a dead kitten in the back pocket of your good suit pants and
|
||
hide your car keys when you are late for work.
|
||
|
||
Goodtimes will make you fall in love with a penguin. It will give
|
||
you nightmares about circus midgets. It will pour sugar in your gas
|
||
tank and shave off both your eyebrows while dating your girlfriend
|
||
behind your back and billing the dinner and hotel room to your
|
||
Discover card..
|
||
|
||
It will seduce your grandmother. It does not matter if she is
|
||
dead, such is the power of Goodtimes, it reaches out beyond the grave
|
||
to sully those things we hold most dear.
|
||
|
||
It moves your car randomly around parking lots so you can't find
|
||
it. It will kick your dog. It will leave libidinous messages on your
|
||
boss's voice mail in your voice! It is insidious and subtle. It is
|
||
dangerous and terrifying to behold. It is also a rather interesting
|
||
shade of mauve.
|
||
|
||
Goodtimes will give you Dutch Elm disease. It will leave the
|
||
toilet seat up. It will make a batch of Methamphetamine in your
|
||
bathtub and then leave bacon cooking on the stove while it goes out to
|
||
chase gradeschoolers with your new snowblower.
|
||
|
||
Listen to me. Goodtimes does not exist.
|
||
|
||
It cannot do anything to you. But I can. I am sending this message
|
||
to everyone in the world. Tell your friends, tell your family. If
|
||
anyone else sends me another E-mail about this fake Goodtimes Virus,
|
||
I will turn hating them into a religion. I will do things to them that
|
||
would make a horsehead in your bed look like Easter Sunday brunch.
|
||
|
||
thanx: seth mall < small@mail.spiritusa.net >
|
||
written by: joe littrell < agent13@accessus.net >"
|
||
|
||
Have a great day
|
||
Lekker dag verder
|
||
|
||
+---------------------------------------------------+
|
||
+ Vic von Abo - King William's Town, South Africa +
|
||
+ E-Mail : vic@fc.co.za or vic@kwt1.ecape.gov.za +
|
||
+---------------------------------------------------+
|
||
|
||
... 10.0 times 0.1 is hardly ever 1.0.
|
||
***
|
||
|
||
FIDONEWS 14-03 Page 30 20 Jan 1997
|
||
|
||
|
||
* Origin: Friendly City BBS - Port Elizabeth, RSA (5:7104/10.0)
|
||
|
||
-----------------------------------------------------------------
|
||
|
||
|
||
--- Following message extracted from NETMAIL @ 1:18/14 ---
|
||
By Christopher Baker on Mon Jan 13 14:10:54 1997
|
||
|
||
From: Bob Moravsik @ 1:2606/583
|
||
To: Fidonews @ 1:1/23
|
||
Date: 13 Jan 97 06:46:03
|
||
Subj: Please
|
||
|
||
* Original to Bob Satti of 1:1/0@fidonet.org
|
||
|
||
cc: Fidonews 1/23
|
||
|
||
|
||
Bob:
|
||
|
||
Do you think you can give us all in Z1 a "State of the Zone " message.
|
||
|
||
At least let us know what you intend to do in the next year concerning
|
||
the coordination of Zone 1.
|
||
|
||
Thanks Bob
|
||
|
||
-----------------------------------------------------------------
|
||
|
||
FIDONEWS 14-03 Page 31 20 Jan 1997
|
||
|
||
|
||
=================================================================
|
||
NET HUMOR
|
||
=================================================================
|
||
|
||
|
||
From: "Mike Riddle" <mriddle@novia.net>
|
||
To: "Baker, Christopher" <cbaker84@digital.net (Christopher Baker)>
|
||
Date: Sat, 18 Jan 97 11:55:43 -0600
|
||
Reply-To: "Mike Riddle" <mriddle@novia.net>
|
||
Subject: Fwd: What To Do If . . .
|
||
|
||
==================BEGIN FORWARDED MESSAGE==================
|
||
>Return-Path: mriddle
|
||
>From: Rich.Arnold@fbbs.omahug.org (Rich Arnold)
|
||
>Date: 17 Jan 97 10:16:00
|
||
>Newsgroups: oma.general
|
||
>Subject: What To Do If . . .
|
||
|
||
WHAT TO DO...
|
||
|
||
...if you get a phone call from Mars.
|
||
|
||
Speak slowly and be sure to enunciate your words properly. Limit
|
||
your vocabulary to simple words. Try to determine if you are
|
||
speaking to someone in a leadership capacity, or an ordinary
|
||
citizen.
|
||
|
||
...if he or she doesn't speak English?
|
||
|
||
Hang up. There's no sense in trying to learn Martian over the
|
||
phone. If your Martian really had something important to say to
|
||
you, he or she would have taken the trouble to learn the language
|
||
before calling.
|
||
|
||
...if you get a phone call from Jupiter?
|
||
|
||
Explain to your caller, politely but firmly, that being from
|
||
Jupiter, he or she is not `life as we know it'. Try to terminate
|
||
the conversation as soon as possible. It will not profit you.
|
||
|
||
...if a starship, equipped with an FTL hyperdrive, lands in your
|
||
backyard?
|
||
|
||
First of all, do not run after your camera. You will not have
|
||
any film. Be polite. Remember, if they have an FTL hyperdrive,
|
||
they can probably vaporize you, should they find you to be rude.
|
||
Direct them to the White House lawn, which is where they probably
|
||
wanted to land, anyway. A good road map should help.
|
||
|
||
...if you wake up in the middle of the night, and discover that your
|
||
closet contains an alternate dimension?
|
||
|
||
Don't go in. You almost certainly will not be able to get back,
|
||
and alternate dimensions are almost never any fun. Remain calm
|
||
and go back to bed. Check your closet in the morning. If it
|
||
still contains an alternate dimension, nail it shut.
|
||
FIDONEWS 14-03 Page 32 20 Jan 1997
|
||
|
||
|
||
...if reality disappears?
|
||
|
||
Hope this one doesn't happen to you. There is not much you can
|
||
do about it. It can be quite unpleasant.
|
||
|
||
...if you meet an older version of yourself who has invented a time
|
||
traveling machine, and has come from the future to meet you?
|
||
|
||
Follow the books on this one. Ask about the stock market and
|
||
cash in. Don't forget to invent a time traveling machine and
|
||
visit your younger self before you die, or you will create a
|
||
paradox.
|
||
|
||
SLMR 2.1a * Age and treachery will always overcome youth and skill.
|
||
|
||
===================END FORWARDED MESSAGE===================
|
||
|
||
-----------------------------------------------------------------
|
||
|
||
FIDONEWS 14-03 Page 33 20 Jan 1997
|
||
|
||
|
||
=================================================================
|
||
WANTED
|
||
=================================================================
|
||
|
||
|
||
Christopher Baker
|
||
Rights On!, 1:18/14
|
||
Edgewater_FL_USA
|
||
|
||
Wanted: old electronics parts.
|
||
|
||
I'm looking for control panels from old 2" video tape mastering
|
||
equipment. They don't have to be working as long as they are intact
|
||
externally with knobs and VUs in place. These panels are about 3.5
|
||
feet long and six inches top to bottom.
|
||
|
||
I'm also looking for old Commodore 64 keyboards. They don't need to
|
||
be operational either.
|
||
|
||
I would prefer them to be free but reasonable costs are acceptable.
|
||
|
||
If you have or know where such items may be obtained, please send
|
||
Netmail to the address above or email to me at:
|
||
|
||
cbaker84@digital.net
|
||
|
||
with details.
|
||
|
||
Thanks.
|
||
|
||
QOFM.
|
||
Chris
|
||
|
||
-----------------------------------------------------------------
|
||
|
||
FIDONEWS 14-03 Page 34 20 Jan 1997
|
||
|
||
|
||
=================================================================
|
||
NOTICES
|
||
=================================================================
|
||
|
||
Future History
|
||
|
||
26 Jan 1997
|
||
Australia Day, Australia.
|
||
|
||
6 Feb 1997
|
||
Waitangi Day, New Zealand.
|
||
|
||
16 Feb 1997
|
||
Eleventh Anniversary of invention of Echomail by Jeff Rush.
|
||
|
||
29 Feb 1997
|
||
Nothing will happen on this day.
|
||
|
||
25 May 1997
|
||
Independence Day, Argentina
|
||
|
||
11 Jun 1997
|
||
Independence Day, Russia
|
||
|
||
1 Jul 1997
|
||
Canada Day - Happy Birthday Canada
|
||
|
||
13 Oct 1997
|
||
Thanksgiving Day, Canada
|
||
|
||
22 May 1998
|
||
Expo '98 World Exposition in Lisbon (Portugal) opens.
|
||
|
||
1 Dec 1998
|
||
Fifteenth Anniversary of release of Fido version 1 by
|
||
Tom Jennings.
|
||
|
||
31 Dec 1999
|
||
Hogmanay, Scotland. The New Year that can't be missed.
|
||
|
||
1 Jan 2000
|
||
The 20th Century, C.E., is still taking place thru 31 Dec.
|
||
|
||
15 Sep 2000
|
||
Sydney (Australia) Summer Olympiad opens.
|
||
|
||
1 Jan 2001
|
||
This is the actual start of the new millennium, C.E.
|
||
|
||
-- If YOU have something which you would like to see in this
|
||
Future History, please send a note to the FidoNews Editor.
|
||
|
||
-----------------------------------------------------------------
|
||
|
||
FIDONEWS 14-03 Page 35 20 Jan 1997
|
||
|
||
|
||
=================================================================
|
||
FIDONET SOFTWARE LISTING
|
||
=================================================================
|
||
|
||
|
||
Latest Greatest Software Versions
|
||
by Peter E. Popovich, 1:363/264
|
||
|
||
The backlog is actually getting winnowed down to something
|
||
manageable. I guess I'm actually starting to get caught up... ;-)
|
||
|
||
I added my first Atari entry this week and have a couple of others
|
||
pending. I also finally got enough info about GoldED to get it added.
|
||
|
||
Given that my "todo" queue is almost empty, I'm going to encourage
|
||
everyone to check to make sure every package they use is listed and
|
||
for each package that isn't listed, netmail me with the names of the
|
||
package and contact info for the author or a support site. I actually
|
||
got caught up enough to twiddle my thumbs, so I think I can handle
|
||
a few extra suggestions... ;-)
|
||
|
||
Also, since I've fallen way behind my original estimates for phasing
|
||
out the old info section, I've reformatted it a little to reduce the
|
||
space it takes.
|
||
|
||
Phased out this week: SuperComm 0.99 and TAG 2.5g
|
||
|
||
Phase-out highlights:
|
||
This week: Telegard 2.7 and TPBoard 6.1
|
||
Deadline for info: 31 Jan 1997.
|
||
Last week: TBBS 2.1 and TComm/TCommNet 3.4
|
||
Deadline for info: 24 Jan 1997.
|
||
|
||
-=- Snip -=-
|
||
|
||
Submission form for the Latest Greatest Software Versions column
|
||
|
||
OS Platform :
|
||
Software package name :
|
||
Version :
|
||
Function(s) - BBS, Mailer, Tosser, etc. :
|
||
Freeware / Shareware / Commercial? :
|
||
Author / Support staff contact name :
|
||
Author / Support staff contact node :
|
||
Magic name (at the above-listed node) :
|
||
|
||
Please include a sentence describing what the package does.
|
||
|
||
Please send updates and suggestions to: Peter Popovich, 1:363/264
|
||
|
||
-=- Snip -=-
|
||
|
||
MS-DOS:
|
||
Program Name Version F C Contact Name Node Magic Name
|
||
----------------------------------------------------------------------
|
||
Act-Up 4.6 G D Chris Gunn 1:15/55 ACT-UP
|
||
FIDONEWS 14-03 Page 36 20 Jan 1997
|
||
|
||
|
||
ALLFIX 4.40 T S Harald Harms 2:281/415 ALLFIX
|
||
Announcer 1.1 O S Peter Karlsson 2:206/221 ANNOUNCE
|
||
BGFAX 1.60 O S B.J. Guillot 1:106/400 BGFAX
|
||
Binkley Docs 2.60 M F Bob Juge 1:1/102 BDOC_260.ZIP
|
||
BinkleyTerm 2.60 M F Bob Juge 1:1/102 BDOS_260.ZIP
|
||
BinkleyTerm-XE XR4 M F Thomas Waldmann 2:2474/400 BTXE_DOS
|
||
CFRoute 0.92 O G C. Fernandez Sanz 2:341/70 CFR
|
||
CheckPnt 1.0 O G Michiel van der Vlist
|
||
2:500/9 CHECKPNT
|
||
FastEcho 1.45a T S Tobias Burchhardt 2:2448/400 FASTECHO
|
||
FastEcho/16 1.45a T S Tobias Burchhardt 2:2448/400 FE16
|
||
FidoBBS (tm) 12u B S Ray Brown 1:1/117 FILES
|
||
FrontDoor 2.12 M S JoHo 2:201/330 FD
|
||
FrontDoor 2.20c M C JoHo 2:201/330 FDINFO
|
||
GIGO 07-14-96 G S Jason Fesler 1:1/141 INFO
|
||
GoldED 2.50 O S Len Morgan 1:203/730 GED
|
||
GoldED Docs 2.50 O S Len Morgan 1:203/730 GEM
|
||
GoldNODE 2.50 O S Len Morgan 1:203/730 GEN
|
||
Imail 1.75 T S Michael McCabe 1:1/121 IMAIL
|
||
ImCrypt 1.04 O G Michiel van der Vlist
|
||
2:500/9 IMCRYPT
|
||
InfoMail 1.11 O F Damian Walker 2:2502/666 INFOMAIL
|
||
InfoMail/386 1.20 O F Damian Walker 2:2502/666 INFO386
|
||
InterEcho 1.19 T C Peter Stewart 1:369/35 IEDEMO
|
||
InterMail 2.29k M C Peter Stewart 1:369/35 IMDEMO
|
||
InterPCB 1.52 O S Peter Stewart 1:369/35 INTERPCB
|
||
IPNet 1.11 O S Michele Stewart 1:369/21 IPNET
|
||
JD's CBV 1.4 O S John Dailey 1:363/277 CBV
|
||
Jelly-Bean 1.01 T S Rowan Crowe 3:635/727 JELLY
|
||
Jelly-Bean/386 1.01 T S Rowan Crowe 3:635/727 JELLY386
|
||
JMail-Hudson 2.81 T S Jason Steck 1:285/424 JMAIL-H
|
||
JMail-Goldbase 2.81 T S Jason Steck 1:285/424 JMAIL-G
|
||
MakePl 1.9 N G Michiel van der Vlist
|
||
2:500/9 MAKEPL
|
||
Marena 1.1 beta O G Michiel van der Vlist
|
||
2:500/9 MARENA
|
||
Maximus 3.01 B P Tech 1:249/106 MAX
|
||
McMail 1.0 M S Michael McCabe 1:1/148 MCMAIL
|
||
MDNDP 1.18 N S Bill Doyle 1:388/7 MDNDP
|
||
Msged 4.00 O G Paul Edwards 3:711/934 MSGED
|
||
Opus CBCS 1.73a B P Christopher Baker 1:374/14 OPUS
|
||
O/T-Track 2.63a O S Peter Hampf 2:241/1090 OT
|
||
PcMerge 2.7 N G Michiel van der Vlist
|
||
2:500/9 PCMERGE
|
||
PlatinumXpress 1.3 M C Gary Petersen 1:290/111 PX13TD.ZIP
|
||
RAR 2.00 C S Ron Dwight 2:220/22 RAR
|
||
RemoteAccess 2.50 B S Mark Lewis 1:3634/12 RA
|
||
Silver Xpress
|
||
Door 5.4 O S Gary Petersen 1:290/111 FILES
|
||
Reader 4.4 O S Gary Petersen 1:290/111 SXR44.ZIP
|
||
Spitfire 3.51 B S Mike Weaver 1:3670/3 SPITFIRE
|
||
Squish 1.11 T P Tech 1:249/106 SQUISH
|
||
StealTag UK 1.c... O F Fred Schenk 2:284/412 STEAL_UK
|
||
StealTag NL 1.c... O F Fred Schenk 2:284/412 STEAL_NL
|
||
T-Mail 2.599I M S Ron Dwight 2:220/22 TMAIL
|
||
Terminate 4.00 O S Bo Bendtsen 2:254/261 TERMINATE
|
||
FIDONEWS 14-03 Page 37 20 Jan 1997
|
||
|
||
|
||
Tobruk 0.33 T G Paul Edwards 3:711/934 TOBRUK
|
||
TriBBS 10.0 B S Patrick Driscoll 1:372/19 TRIBBS
|
||
TriDog 10.0 M S Patrick Driscoll 1:372/19 TRIDOG
|
||
TriToss 10.0 T S Patrick Driscoll 1:372/19 TRITOSS
|
||
WaterGate 0.92 G S Robert Szarka 1:320/42 WTRGATE
|
||
WWIV 4.24a B S Craig Dooley 1:376/126 WWIV
|
||
WWIVTOSS 1.30 T S Craig Dooley 1:376/126 WWIVTOSS
|
||
xMail 2.00 T S Thorsten Franke 2:2448/53 XMAIL
|
||
XRobot 3.01 O S JoHo 2:201/330 XRDOS
|
||
|
||
OS/2:
|
||
Program Name Version F C Contact Name Node Magic Name
|
||
----------------------------------------------------------------------
|
||
ALLFIX/2 1.10 T S Harald Harms 2:281/415 AFIXOS2
|
||
BGFAX 1.60 O S B.J. Guillot 1:106/400 BGFAX
|
||
Binkley Docs 2.60 M F Bob Juge 1:1/102 BDOC_260.ZIP
|
||
BinkleyTerm 2.60 M F Bob Juge 1:1/102 BOS2_260.ZIP
|
||
BinkleyTerm-XE XR4 M F Thomas Waldmann 2:2474/400 BTXE_OS2
|
||
CFRoute 0.92 O G C. Fernandez Sanz 2:341/70 CFR
|
||
FastEcho 1.45a T S Tobias Burchhardt 2:2448/400 FE2
|
||
FleetStreet 1.18 O S Michael Hohner 2:2490/2520 FLEET
|
||
GIGO 07-14-96 G S Jason Fesler 1:1/141 INFO
|
||
GoldED 2.50 O S Len Morgan 1:203/730 GEO
|
||
GoldED Docs 2.50 O S Len Morgan 1:203/730 GEM
|
||
GoldNODE 2.50 O S Len Morgan 1:203/730 GEN
|
||
ImCrypt 1.04 O G Michiel van der Vlist
|
||
2:500/9 IMCRYPT
|
||
Maximus 3.01 B P Tech 1:249/106 MAXP
|
||
Msged 4.00 O G Paul Edwards 3:711/934 MSGED
|
||
PcMerge 2.3 N G Michiel van der Vlist
|
||
2:500/9 PCMERGE
|
||
RAR 2.00 C S Ron Dwight 2:220/22 RAR2
|
||
Squish 1.11 T P Tech 1:249/106 SQUISHP
|
||
T-Mail 2.599I M S Ron Dwight 2:220/22 TMAIL2
|
||
Tobruk 0.33 T G Paul Edwards 3:711/934 TOBRUK
|
||
XRobot 3.01 O S JoHo 2:201/330 XROS2
|
||
|
||
Windows (16-bit apps):
|
||
Program Name Version F C Contact Name Node Magic Name
|
||
----------------------------------------------------------------------
|
||
BeeMail 1.0 M C Andrius Cepaitis 2:470/1 BEEMAIL
|
||
FrontDoor APX 1.10 P S Mats Wallin 2:201/329 FDAPXW
|
||
|
||
Windows (32-bit apps):
|
||
Program Name Version F C Contact Name Node Magic Name
|
||
----------------------------------------------------------------------
|
||
BeeMail 1.0 M C Andrius Cepaitis 2:470/1 BEEMAIL
|
||
Binkley Docs 2.60 M F Bob Juge 1:1/102 BDOC_260.ZIP
|
||
BinkleyTerm 2.60 M F Bob Juge 1:1/102 BW32_260.ZIP
|
||
CFRoute 0.92 O G C. Fernandez Sanz 2:341/70 CFR
|
||
GoldED 2.50 O S Len Morgan 1:203/730 GEO
|
||
GoldED Docs 2.50 O S Len Morgan 1:203/730 GEM
|
||
Maximus 3.01 B P Tech 1:249/106 MAXN
|
||
Msged/NT 4.00 O G Andrew Clarke 3:635/728 MSGNT400.ZIP
|
||
PlatinumXpress 2.00 M C Gary Petersen 1:290/111 PXW-INFO
|
||
T-Mail 2.599I M S Ron Dwight 2:220/22 TMAILNT
|
||
FIDONEWS 14-03 Page 38 20 Jan 1997
|
||
|
||
|
||
WinFOSSIL/95 1.12 r4 F S Bryan Woodruff 1:343/294 WNFOSSIL.ZIP
|
||
WinFOSSIL/NT 1.0 beta F S Bryan Woodruff 1:343/294 NTFOSSIL.ZIP
|
||
|
||
Unix:
|
||
Program Name Version F C Contact Name Node Magic Name
|
||
----------------------------------------------------------------------
|
||
ifmail 2.8g M G Eugene Crosser 2:293/2219 IFMAIL
|
||
ifmail-tx ...tx7.8 M G Pablo Saratxaga 2:293/2219 IFMAILTX
|
||
Msged 4.00 O G Paul Edwards 3:711/934 MSGED
|
||
Tobruk 0.33 T G Paul Edwards 3:711/934 TOBRUK
|
||
|
||
Amiga:
|
||
Program Name Version F C Contact Name Node Magic Name
|
||
----------------------------------------------------------------------
|
||
CrashMail 1.23 T X Fredrik Bennison 2:205/324 CRASHMAIL
|
||
CrashTick 1.1 O F Fredrik Bennison 2:205/324 CRASHTICK
|
||
DLG Pro BBOS 1.15 B C Holly Sullivan 1:202/720 DLGDEMO
|
||
GMS 1.1.85 M S Mirko Viviani 2:331/213 GMS
|
||
Msged 4.00 O G Paul Edwards 3:711/934 MSGED
|
||
Tobruk 0.33 T G Paul Edwards 3:711/934 TOBRUK
|
||
|
||
Atari:
|
||
Program Name Version F C Contact Name Node Magic Name
|
||
----------------------------------------------------------------------
|
||
BinkleyTerm/ST 3.18pl1 M F Bill Scull 1:363/112 BINKLEY
|
||
|
||
Function: B-BBS, P-Point, M-Mailer, N-Nodelist, G-Gateway, T-Tosser,
|
||
C-Compression, F-Fossil, O-Other. Note: Multifunction will
|
||
be listed by the first match.
|
||
|
||
Cost: P-Free for personal use, F-Freeware, S-Shareware, C-Commercial,
|
||
X-Crippleware, D-Demoware, G-Free w/ Source
|
||
|
||
|
||
Old info from: 01/27/92
|
||
---------------------------------------------------------------------
|
||
|
||
BBS Software MS-DOS Systems
|
||
Name Version --------------
|
||
--------------------
|
||
TBBS 2.1 Other Utilities Other Utilities
|
||
TComm/TCommNet 3.4 Name Version Name Version
|
||
Telegard 2.7* -------------------- --------------------
|
||
TPBoard 6.1 2DAPoint 1.50* Netsex 2.00b
|
||
WildCat! 3.02* 4Dog/4DMatrix 1.18 OFFLINE 1.35
|
||
XBBS 1.77 ARCAsim 2.31 Oliver 1.0a
|
||
ARCmail 3.00* OSIRIS CBIS 3.02
|
||
Network Mailers Areafix 1.20 PKInsert 7.10
|
||
Name Version ConfMail 4.00 PolyXarc 2.1a
|
||
-------------------- Crossnet 1.5 QM 1.00a
|
||
D'Bridge 1.30 DOMAIN 1.42 QSort 4.04
|
||
Dreamer 1.06 DEMM 1.06 RAD Plus 2.11
|
||
Dutchie 2.90c DGMM 1.06 Raid 1.00
|
||
Milqtoast 1.00 DOMAIN 1.42 RBBSMail 18.0
|
||
PreNM 1.48 EEngine 0.32 ScanToss 1.28
|
||
SEAdog 4.60 EMM 2.11* ScMail 1.00
|
||
FIDONEWS 14-03 Page 39 20 Jan 1997
|
||
|
||
|
||
SEAmail 1.01 EZPoint 2.1 ScEdit 1.12
|
||
TIMS 1.0(mod8) FGroup 1.00 Sirius 1.0x
|
||
FidoPCB 1.0s@ SLMail 2.15C
|
||
Compression FNPGate 2.70 StarLink 1.01
|
||
Utilities GateWorks 3.06e TagMail 2.41
|
||
Name Version GMail 2.05 TCOMMail 2.2
|
||
-------------------- GMD 3.10 Telemail 1.5*
|
||
ARC 7.12 GMM 1.21 TGroup 1.13
|
||
ARJ 2.20 GROUP 2.23 TIRES 3.11
|
||
LHA 2.13 GUS 1.40 TMail 1.21
|
||
PAK 2.51 Harvey's Robot 4.10 TosScan 1.00
|
||
PKPak 3.61 HeadEdit 1.18 UFGATE 1.03
|
||
PKZip 1.10 HLIST 1.09 VPurge 4.09e
|
||
ISIS 5.12@ WEdit 2.0@
|
||
NodeList Utilities Lola 1.01d WildMail 2.00
|
||
Name Version Mosaic 1.00b WMail 2.2
|
||
-------------------- MailBase 4.11a@ WNode 2.1
|
||
EditNL 4.00 MSG 4.5* XRS 4.99
|
||
FDND 1.10 MsgLnk 1.0c XST 2.3e
|
||
MakeNL 2.31 MsgMstr 2.03a YUPPIE! 2.00
|
||
Parselst 1.33 MsgNum 4.16d ZmailH 1.25
|
||
Prune 1.40 MSGTOSS 1.3 ZSX 2.40
|
||
SysNL 3.14
|
||
XlatList 2.90
|
||
XlaxNode/Diff 2.53
|
||
|
||
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
|
||
|
||
OS/2 Systems
|
||
------------
|
||
Other Utilities Other Utilities
|
||
BBS Software Name Version Name Version
|
||
Name Version -------------------- --------------------
|
||
-------------------- ARC 7.12 oMMM 1.52
|
||
Kitten 1.01 ARC2 6.01 Omail 3.1
|
||
SimplexBBS 1.04.02+ ConfMail 4.00 Parselst 1.33
|
||
EchoStat 6.0 PKZip 1.02
|
||
Network Mailers EZPoint 2.1 PMSnoop 1.30
|
||
Name Version FGroup 1.00 PolyXOS2 2.1a
|
||
-------------------- GROUP 2.23 QSort 2.1
|
||
BinkleyTerm(S) 2.50 LH2 2.11 Raid 1.0
|
||
BinkleyTerm/2-MT MSG 4.2 Remapper 1.2
|
||
1.40.02 MsgLink 1.0c Tick 2.0
|
||
SEAmail 1.01 MsgNum 4.16d VPurge 4.09e
|
||
|
||
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
|
||
|
||
Xenix/Unix 386 Other Utilities
|
||
-------------- Name Version
|
||
--------------------
|
||
BBS Software Network Mailers ARC 5.21
|
||
Name Version Name Version C-LHARC 1.00
|
||
-------------------- -------------------- MSGLINK 1.01
|
||
oMMM 1.42
|
||
Omail 1.00
|
||
|Contact: Willy Paine 1:343/15,| ParseLst 1.32
|
||
FIDONEWS 14-03 Page 40 20 Jan 1997
|
||
|
||
|
||
|or Eddy van Loo 2:285/406 | Unzip 3.10
|
||
VPurge 4.08
|
||
Zoo 2.01
|
||
|
||
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
|
||
|
||
BBS Software Macintosh Other Software
|
||
Name Version --------- Name Version
|
||
-------------------- --------------------
|
||
FBBS 0.91 Network Mailers MacArd 0.04
|
||
Hermes 1.6.1 Name Version Mantissa 3.21
|
||
Mansion 7.15 -------------------- Mehitable 2.0
|
||
Precision Sys. 0.95b Copernicus 1.0 OriginatorII 2.0
|
||
Red Ryder Host 2.1 Tabby 2.2 PreStamp 3.2
|
||
Telefinder Host StuffIt Classic 1.6
|
||
2.12T10 Other Software SunDial 3.2
|
||
Name Version TExport 1.92
|
||
-------------------- TimeStamp 1.6
|
||
Point System ArcMac 1.3 TImport 1.92
|
||
Software AreaFix 1.6 Tset 1.3
|
||
Name Version Compact Pro 1.30 TSort 1.0
|
||
-------------------- EventMeister 1.0 UNZIP 1.02c
|
||
Copernicus 1.00 Export 3.21 Zenith 1.5
|
||
CounterPoint 1.09 Import 3.2 Zip Extract 0.10
|
||
MacWoof 1.1 LHARC 0.41
|
||
|
||
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
|
||
|
||
Amiga Network Mailers Other Software
|
||
----- Name Version Name Version
|
||
-------------------- --------------------
|
||
BBS Software BinkleyTerm 1.00 Areafix 1.48
|
||
Name Version TrapDoor 1.80 AReceipt 1.5
|
||
-------------------- WelMat 0.44 ChameleonEdit 0.11
|
||
4D-BBS 1.65 ConfMail 1.12
|
||
Falcon CBCS 1.00 ElectricHerald 1.66
|
||
Starnet 1.0q@ Compression FFRS 1.0@
|
||
TransAmiga 1.07 Utilities FileMgr 2.08
|
||
XenoLink 1.0 Name Version Fozzle 1.0@
|
||
-------------------- Login 0.18
|
||
AmigArc 0.23 MessageFilter 1.52
|
||
NodeList Utilities booz 1.01 Message View 1.12
|
||
Name Version LHARC 1.30 oMMM 1.50
|
||
-------------------- LhA 1.10 PolyXAmy 2.02
|
||
ParseLst 1.66 LZ 1.92 RMB 1.30
|
||
Skyparse 2.30 PkAX 1.00 Roof 46.15
|
||
TrapList 1.40 UnZip 4.1 RoboWriter 1.02
|
||
Zippy (Unzip) 1.25 Rsh 4.07a
|
||
Zoo 2.01 Tick 0.75
|
||
TrapToss 1.20
|
||
|Contact: Maximilian Hantsch 2:310/6| Yuck! 2.02
|
||
|
||
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
|
||
|
||
BBS Software Atari ST/TT
|
||
Name Version -----------
|
||
FIDONEWS 14-03 Page 41 20 Jan 1997
|
||
|
||
|
||
--------------------
|
||
FIDOdoor/ST 2.5.1 Network Mailers Other Utilities
|
||
FiFo 2.1v Name Version Name Version
|
||
LED ST 1.00 -------------------- --------------------
|
||
QuickBBS/ST 1.06* The Box 1.95* ApplyList 1.00@
|
||
Burep 1.1
|
||
Compression ComScan 1.04
|
||
Utilities NodeList Utilities ConfMail 4.10
|
||
Name Version Name Version Echoscan 1.10
|
||
-------------------- -------------------- FDrenum 2.5.2
|
||
ARC 6.02 ParseList 1.30 FastPack 1.20
|
||
LHARC 2.01i EchoFix 1.20 Import 1.14
|
||
PackConvert sTICK/Hatch 5.50 oMMM 1.40
|
||
STZip 1.1* Pack 1.00
|
||
UnJARST 2.00 Trenum 0.10
|
||
WhatArc 2.02
|
||
|
||
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
|
||
|
||
Tandy Color Computer 3 (OS-9 Level II) Other Utilities
|
||
-------------------------------------- Name Version
|
||
--------------------
|
||
BBS Software Compression Utility Ascan 1.2
|
||
Name Version Name Version AutoFRL 2.0
|
||
-------------------- -------------------- Bundle 2.2
|
||
RiBBS 2.02+ Ar 1.3 CKARC 1.1
|
||
DeArc 5.12 EchoCheck 1.01
|
||
OS9Arc 1.0 FReq 2.5a
|
||
UnZip 3.10 LookNode 2.00
|
||
UnLZH 3.0 ParseLST
|
||
PReq 2.2
|
||
RList 1.03
|
||
RTick 2.00
|
||
UnBundle 1.4
|
||
UnSeen 1.1
|
||
|
||
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
|
||
Key to old info:
|
||
+ - Netmail Capable (Doesn't Require Additional Mailer Software)
|
||
* - Recently Updated Version
|
||
@ - New Addition
|
||
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
|
||
|
||
Please send updates and suggestions to: Peter Popovich, 1:363/264
|
||
|
||
-----------------------------------------------------------------
|
||
|
||
FIDONEWS 14-03 Page 42 20 Jan 1997
|
||
|
||
|
||
=================================================================
|
||
FIDONEWS PUBLIC-KEY
|
||
=================================================================
|
||
|
||
|
||
[this must be copied out to a file starting at column 1 or
|
||
it won't process under PGP as a valid public-key]
|
||
|
||
|
||
-----BEGIN PGP PUBLIC KEY BLOCK-----
|
||
Version: 2.6.2
|
||
Comment: Clear-signing is Electronic Digital Authenticity!
|
||
|
||
mQCNAzINVLcAAAEEAM5dZN6t6j5Yc0kl7qegVFfiBeVoteuhDg4ay8h43u38Q4kO
|
||
eJ9Mm7J89wXFb9vgouBVb4biIN6bTWCwcXTbGhBe5OIceLvluuxuEKsaIs/UwXNe
|
||
Ogx5azIPhRfC7MJDe41Z8tMEBuHY/NE88cuxQ8yXWO126IRttavu6L/U5BwRAAUR
|
||
tCRGaWRvTmV3cyBFZGl0b3IgPDE6MS8yM0BmaWRvbmV0Lm9yZz6JAJUDBRAyGwFS
|
||
JZMgw7eCKz0BAZl0A/9xrfhpsEOqGiPfjy2qd9dv6tvSVPPVFu+Wy1lGTHYtuTtg
|
||
FIN3fQ47AM3XzqHxWRWvp/xZYgR6sRICL7UFx94ShYBQc7CyqBBZKA0IvIWqXP/g
|
||
c4Br+gQJR6CLiQK7TUyjUbqNbs6QAxuNUi4xFQM+O2Gene5/iTjHFmmSDj2C9YkB
|
||
FQMFEDIOmHDTQ6/52IG1SQEBQ78H/Rz/mleIrtZwFIOhzy3JH4Z6FUTfZuM9nPcs
|
||
1ZLjZCPptHvY7wEYJWGr03lPPJ6tj1VBXwTrWJTf/hOLsoi00GKV8t1thjqGDo23
|
||
O91/bSQ+Vn0vBQ2vOEJys8ftxdoLJAyI5YLzHVT+RsMTQLIXVuPyrNcKs1vC2ql+
|
||
UDHpU1R+9cG9JUEHpGI6z0DPnQ74SKbQH3fiVBpHhYx4BmvcBC4gWQzKMkDWFiq3
|
||
8AssIZ7b9lWl3OBgQ4UM1OIDKoJyjRewIdKyl7zboKSt6Qu8LrcsXO3kb81YshOW
|
||
ZpSS3QDIqfZC4+EElnB15l4RcVwnPHBaQY0FxUr4Vl4UWM36jbuJAJUDBRAyDpgY
|
||
q+7ov9TkHBEBAQGoA/sFfN07IFQcir456tJfBfB9R5Z6e6UKmexaFhWOsLHqbCq6
|
||
3FGXDLeivNn6NTz81QeqLIHglTuM3NP1mu8sw215klAG8G3M1NA2xLw7Eqhspze2
|
||
raGvNeEwxl8e+PY9aZwBj4UWU+CmIm6QNiP0MtvR7QYDIKn5mZCDc3CLmr942IkB
|
||
FQMFEDIOh0O8AhTPqRipPQEB4EYH/1gkDmdHL6lbEkFuQLrylF+weBl0XQ+kv7ER
|
||
vWXYrvIrkppxtc4VAge6CXXEbOGJnvkFHgyNZzO9Q9O64QsmZvjip+4lhDLeNrdH
|
||
X9DizS4YKXxkSKr9Yltmn2/AlBCx6jwcDIfkqy/P1tNWcikxZZMd6KryK0Wsres9
|
||
Ik12OmVmJjQSxb5bS6Q8aYUbV3qwosGXTqy+BzYh/UYAX/XJIWa5kxFVSPKFSZ+5
|
||
toiSzANd9SpHPEogGvQDHJlJ23lmsMx/6uHsR1LTsQ8su8zIk92XyqePJTjlMx2j
|
||
D7KJWNR7Zzu4QHCXBkga5W8l2FfPk7D3+o7bXTLRuR1yTYGdNoiJAJUCBRAyDhwt
|
||
SlKLwP4OFW0BAdaMA/9rcWQlSq44K9JuJ7fZUgt9fwxGreTud9fC8DvlbUW79+CA
|
||
AHLTLLagcEF1OKsWzVBWcA2JEAp+TUTqktRN0oD8vnaw3uNJd1G5KK59hw0WR8x1
|
||
v4ivypbSjiq95Y3gBunb7WjpyiFRWDlm0PrKrWHtbWzjnpPIpetln1UuqsSfbokB
|
||
FQIFEDIOG9C3N61ZQ4Dr/QEBIzMH/1VxxztmBPBszbjZLDO8Svcax9Ng8IcWpcDy
|
||
WqHCAA2Hoe5VtMD0v6w31ZgVqTPIvCark2Y/aTR1GofiuN9NUqbVV534AgAYLzYk
|
||
DMT1swsPvqDTpOYgQl6PCGh6A5JGAbWJfKkX9XCUHJAAmiTsEVRNnjOgL+p6qjoh
|
||
EfIG8CGehghWSRKl5eGeDAtbXupZKNjFI1t2XV+ks0RFQ/RPuTH7pF7pk7WO6Cyg
|
||
+Dk2ZMgua0HRL1fXvHKb5Xzr3MVgsbAl5gP8ooIiD9MI/x5Irh3oo58VyoEZNBs/
|
||
Kz+drGFDPljcS6fdiVCFtYIzMrshY6YsfLi0aB8fwOvFtxgBqli0J0NocmlzdG9w
|
||
aGVyIEJha2VyIDwxOjE4LzE0QGZpZG9uZXQub3JnPrQoQ2hyaXN0b3BoZXIgQmFr
|
||
ZXIgPGNiYWtlcjg0QGRpZ2l0YWwubmV0Pg==
|
||
=61OQ
|
||
-----END PGP PUBLIC KEY BLOCK-----
|
||
|
||
|
||
File-request FNEWSKEY from 1:1/23 [1:18/14] or download it from the
|
||
Rights On! BBS at 1-904-409-7040 anytime except 0100-0130 ET and Zone
|
||
1 ZMH at 1200-9600+ HST/V32B. The FidoNews key is also available on
|
||
the FidoNews homepage listed in the Masthead information.
|
||
|
||
-----------------------------------------------------------------
|
||
FIDONEWS 14-03 Page 43 20 Jan 1997
|
||
|
||
|
||
=================================================================
|
||
FIDONET BY INTERNET
|
||
=================================================================
|
||
|
||
This is a list of all FidoNet-related sites reported to the Editor as
|
||
of this appearance.
|
||
|
||
============
|
||
|
||
FidoNet:
|
||
|
||
Homepage http://www.fidonet.org
|
||
FidoNews http://ddi.digital.net/~cbaker84/fidonews.html
|
||
HTML FNews http://www.geocities.com/Athens/6894/
|
||
WWW sources http://www.scms.rgu.ac.uk/students/cs_yr94/lk/fido.html
|
||
FTSC page http://www2.blaze.net.au/ftsc.html
|
||
Echomail http://www.portal.ca/~awalker/index.html
|
||
WebRing http://ddi.digital.net/~cbaker84/fnetring.html
|
||
|
||
============
|
||
|
||
Zone 1: http://www.z1.fidonet.org
|
||
|
||
Region 10:
|
||
http://www.psnw.com/~net205/region10.html
|
||
http://www.dharmanet.org/BDO/net125.html
|
||
|
||
Region 15:
|
||
http://www.smrtsys.com/region15/
|
||
|
||
Region 17:
|
||
http://www.portal.ca/~awalker/region17.htm
|
||
|
||
Region 18:
|
||
http://www.citicom.com/fido.html
|
||
|
||
Region 19:
|
||
http://ccove.n-link.com/
|
||
|
||
============
|
||
|
||
Zone 2: http://www.z2.fidonet.org
|
||
ZEC2 http://fidoftp.paralex.co.uk/zec.htm
|
||
|
||
Region 36: http://www.geocities.com/SiliconValley/7207/
|
||
|
||
============
|
||
|
||
Zone 3: http://www.z3.fidonet.org
|
||
|
||
============
|
||
|
||
Zone 4:
|
||
|
||
============
|
||
|
||
FIDONEWS 14-03 Page 44 20 Jan 1997
|
||
|
||
|
||
Zone 5:
|
||
|
||
============
|
||
|
||
Zone 6: http://www.z6.fidonet.org
|
||
|
||
============
|
||
|
||
-----------------------------------------------------------------
|
||
|
||
FIDONEWS 14-03 Page 45 20 Jan 1997
|
||
|
||
|
||
=================================================================
|
||
FIDONEWS INFORMATION
|
||
=================================================================
|
||
|
||
------- FIDONEWS MASTHEAD AND CONTACT INFORMATION -------
|
||
|
||
Editor: Christopher Baker
|
||
|
||
Editors Emeritii: Thom Henderson, Dale Lovell,
|
||
Vince Perriello, Tim Pozar,
|
||
Tom Jennings, Sylvia Maxwell,
|
||
Donald Tees
|
||
|
||
"FidoNews Editor"
|
||
FidoNet 1:1/23
|
||
BBS 1-904-409-7040, 300/1200/2400/14400/V.32bis/HST(ds)
|
||
|
||
more addresses:
|
||
Christopher Baker -- 1:18/14, cbaker84@digital.net
|
||
cbaker84@aol.com
|
||
cbaker84@msn.com
|
||
cbak.rights@opus.global.org
|
||
|
||
(Postal Service mailing address)
|
||
FidoNews Editor
|
||
P.O. Box 471
|
||
Edgewater, FL 32132-0471
|
||
U.S.A.
|
||
|
||
|
||
voice: 1-904-409-3040 [1400-2100 ET only, please]
|
||
[1800-0100 UTC/GMT]
|
||
|
||
------------------------------------------------------
|
||
|
||
FidoNews is published weekly by and for the members of the FIDONET
|
||
INTERNATIONAL AMATEUR ELECTRONIC MAIL system. It is a compilation
|
||
of individual articles contributed by their authors or their
|
||
authorized agents. The contribution of articles to this compilation
|
||
does not diminish the rights of the authors. OPINIONS EXPRESSED in
|
||
these articles ARE THOSE OF THE AUTHORS and not necessarily those of
|
||
FidoNews.
|
||
|
||
Authors retain copyright on individual works; otherwise FidoNews is
|
||
Copyright 1996 Christopher Baker. All rights reserved. Duplication
|
||
and/or distribution permitted for noncommercial purposes only. For
|
||
use in other circumstances, please contact the original authors, or
|
||
the Editor.
|
||
|
||
=*=*=*=*=*=*=*=*=
|
||
|
||
OBTAINING COPIES: The most recent issue of FidoNews in electronic
|
||
form may be obtained from the FidoNews Editor via manual download or
|
||
file-request, or from various sites in the FidoNet and Internet.
|
||
PRINTED COPIES may be obtained by sending SASE to the above postal
|
||
address. File-request FIDONEWS for the current Issue. File-request
|
||
FIDONEWS 14-03 Page 46 20 Jan 1997
|
||
|
||
|
||
FNEWS for the current month in one archive. Or file-request specific
|
||
back Issue filenames in distribution format [FNEWSDnn.LZH] for a
|
||
particular Issue. Monthly Volumes are available as FNWSmmmy.ZIP
|
||
where mmm = three letter month [JAN - DEC] and y = last digit of the
|
||
current year [6], i.e., FNWSMAY6.ZIP for all the Issues from May 96.
|
||
|
||
Annual volumes are available as FNEWSn.ZIP where n = the Volume number
|
||
1 - 12 for 1984 - 1995, respectively. Annual Volume archives range in
|
||
size from 48K to 1.2M.
|
||
|
||
|
||
INTERNET USERS: FidoNews is available via:
|
||
|
||
http://www.fidonet.org/fidonews.htm
|
||
ftp://ftp.fidonet.org/pub/fidonet/fidonews/
|
||
ftp://ftp.aminet.org/pub/aminet/comm/fido/
|
||
|
||
You can read the current FidoNews Issue in HTML format at:
|
||
|
||
http://www.geocities.com/Athens/6894/
|
||
|
||
STAR SOURCE for ALL Past Issues via FTP and file-request -
|
||
Available for FReq from 1:396/1 or by anonymous FTP from:
|
||
|
||
ftp://ftp.sstar.com/fidonet/fnews/
|
||
|
||
Each yearly archive also contains a listing of the Table-of-Contents
|
||
for that year's issues. The total set is currently about 11 Megs.
|
||
|
||
=*=*=*=
|
||
|
||
The current week's FidoNews and the FidoNews public-key are now also
|
||
available almost immediately after publication on the Editor's new
|
||
homepage on the World Wide Web at:
|
||
|
||
http://ddi.digital.net/~cbaker84/fidonews.html
|
||
|
||
There are also links there to jim barchuk's HTML FidoNews source and
|
||
to John Souvestre's FTP site for the archives. There is also an email
|
||
link for sending in an article as message text. Drop on over.
|
||
|
||
=*=*=*=*=*=*=*=*=
|
||
|
||
A PGP generated public-key is available for the FidoNews Editor from
|
||
1:1/23 [1:18/14] by file-request for FNEWSKEY or by download from
|
||
Rights On! BBS at 1-904-409-7040 as FIDONEWS.ASC in File Area 18. It
|
||
is also posted twice a month into the PKEY_DROP Echo available on the
|
||
Zone 1 Echomail Backbone.
|
||
|
||
*=*=*=*=*
|
||
|
||
SUBMISSIONS: You are encouraged to submit articles for publication in
|
||
FidoNews. Article submission requirements are contained in the file
|
||
ARTSPEC.DOC, available from the FidoNews Editor, or file-requestable
|
||
from 1:1/23 [1:18/14] as file "ARTSPEC.DOC". ALL Zone Coordinators
|
||
also have copies of ARTSPEC.DOC. Please read it.
|
||
FIDONEWS 14-03 Page 47 20 Jan 1997
|
||
|
||
|
||
"Fido", "FidoNet" and the dog-with-diskette are U.S. registered
|
||
trademarks of Tom Jennings, P.O. Box 410923, San Francisco, CA 94141,
|
||
and are used with permission.
|
||
|
||
"Disagreement is actually necessary,
|
||
or we'd all have to get in fights
|
||
or something to amuse ourselves
|
||
and create the requisite chaos."
|
||
-Tom Jennings
|
||
|
||
-30-
|
||
|
||
|
||
-----------------------------------------------------------------
|
||
|
||
|