home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Black Box 4
/
BlackBox.cdr
/
bbs_mail
/
lstfmt22.arj
/
LSTFMT22.DOC
< prev
next >
Wrap
Text File
|
1991-09-28
|
39KB
|
1,172 lines
28-SEP-1991
LSTFMT Version 2.20
A NodeList Output Formatting Utility for FTSC Compliant NodeLists
Author: Steven K. Shapiro
SysOp LoneStar CBCS
FidoNet 1:382/35
Program and Documentation
Copyright (C) 1989, 1990, 1991 SKS Computer Consulting, Inc.
All Rights Reserved
LSTFMT IS NOT PUBLIC DOMAIN SOFTWARE!
LSTFMT IS COPYRIGHTED SOFTWARE.
YOU ARE ENTITLED TO USE AND DISTRIBUTE THE
LSTFMT PACKAGE ONLY IN ACCORDANCE WITH THE LICENSE
AGREEMENT CONTAINED HEREIN.
28-SEP-1991
LICENSE AGREEMENT, WARRANTY AND STATEMENT OF LIABILITY
The term "the package" refers to the LSTFMT software and
documentation, individually and collectively. The term "the author"
shall be construed to mean Steven K. Shapiro. The term "FTSC" refers
to the FidoNet Technical Standards Committee.
The package is the exclusive property of the author, and is protected
by copyright laws. By obtaining a copy of the package, you do not
"own" a copy...all property rights are retained by the author. You
are merely licensed to USE it.
This License grants limited rights to use and distribute the package
in accordance with the terms listed herein. Any other use constitutes
a violation of the author's rights under United States Copyright Law,
and applicable treaties.
You may use the package and/or give copies of the package to others,
but only in a form that permits inclusion of all files as found in the
original, archived form in which the package is distributed by the
author. You are not permitted to modify any portion of the package in
any way, including, but not limited to adding files to or removing
files from the distribution package, changing or editing the
documentation, and/or changing or modifying the executable
program(s).
If you find the package to be of use, and feel that a monetary
contribution is in order, you are encouraged to forward it to the
author.
The package is not provided with any warranty of any kind, including,
but not limited to fitness for any particular purpose.
IMPORTANT NOTE: If this License or any portion thereof is not legally
valid in your geographical area or jurisdiction, THIS LICENSE IS
WITHDRAWN and YOU ARE NOT LICENSED TO USE OR DISTRIBUTE THE PACKAGE!
WARNING! YOU USE THIS PACKAGE ENTIRELY AT YOUR OWN RISK! The author
will NOT be responsible for any loss of data, loss of business, loss
of monies or any other damages resulting from the use of, or inability
to use this program. By operating the program, you accept and
acknowledge responsibility IN FULL for all occurrences related to your
use of the program. In any jurisdiction where such limitation of
liability is restricted or forbidden, this program IS NOT licensed for
legal use.
2
28-SEP-1991
OTHER USES (NON-LICENSED USES)
Use and distribution outside the scope of the License Agreement above
is strictly prohibited, unless prior, written permission is obtained
from the author. Inquiries may be directed to: SKS Computer
Consulting, Inc., P.O. Box 202350, Austin, TX, 78720, USA. Include a
self-addressed, stamped envelope for replies.
DISTRIBUTION NOTICE
The package may be posted for download or file request by any FTSC
compliant system in archived form, and in adherence to the terms of
the License above. No profit may be realized directly or indirectly
from such distribution, although the package may be provided for
download on 'pay systems'.
ARCHIVES
The regular distribution version of the package is archived using
PKZIP from PKWare, Inc. This is NOT a political statement, it's a
matter of personal preference.
If you feel it necessary to re-archive the package in a format other
than the format it's delivered in, go ahead, but you should read the
License Agreement carefully. Any distribution of the package requires
that ALL the files AS ORIGINALLY DISTRIBUTED must be included.
Prior to distribution, make certain that you have a full, original
version, and make sure all the files in the package make it into your
new archive. Addition of files to the distribution is prohibited.
PURCHASING COPIES OF THE PACKAGE
The package is also available on diskette within the USA and Canada.
Send check or money order in US dollars to: SKS Computer Consulting,
Inc., P.O. Box 202350, Austin, TX, 78720, USA.
SOURCE CODE
Source code to the package will not be available. I do not feel that
I need to justify my reasoning.
3
28-SEP-1991
PROGRAM OPERATION
LSTFMT provides 2 functions. 1). The extraction of comments and 2).
Formatted extraction of node information from FTSC compliant
nodelists.
The format for using LSTFMT is:
LSTFMT /I<Input_file>
/O<Output_file>
/N<Net_number>
/S<System_info>
/Pazrtenscypbf
/K<zone>,<region>,<net>
/C[SUFAE]
/E<echo_area>,<host_zone>,<host_net>,<host_node>,
<your_zone>,<your_net>,<your_node>
/D
/R
/A
/T
/L
Where all arguments are entered on the same line interactively or via
a batch file.
/I<Input_file>
This is the nodelist file from which to extract the information.
If you fail to specify the filename extension, LSTFMT will
calculate the day number of the current nodelist and will attempt
to open the file with the nodelist day as the file name
extension. If you do not use this switch, LSTFMT will attempt to
use the current expected NODELIST.### file. In either of these
last 2 cases, if LSTFMT doesn't find a list for the current
expected julian date for the nodelist, it will look for the
previous weeks list.
You may specify any valid Drive:\directory\path\filename.ext.
Either one or both of these switches must be specified:
/N<Net_number>
This is the Zone, Region, or Host net from which to extract and
format the information. LSTFMT will find the first match which
corresponds to the specified information. So, if you specify
/N1, it will format all of the information for the first match
which will be all of the Zone 1 independent nodes. If you
specify /N10 you will receive a listing for all of the Region 10
independent nodes, etc. Bear in mind that some Regions/Hosts may
be duplicated between Zones. If you want to extract specific
information for a particular net in a particular region in a
particular zone, you should probably use the /K switch.
4
28-SEP-1991
If an '*' is specified as the net_number, then all nets in the
input nodelist will be formatted. This parameter will supercede
the /S switch.
5
28-SEP-1991
/C[sufae]
This indicates that comments should be extracted from the
nodelist input file. Only comments with text following them will
be extracted. If no arguments are specified, all comments will
be extracted. The valid comment types are S,U,F,A and E. You
may specify any combination of these comment types for
extraction.
/O<Output_file>
Is the file to which the extracted information is to be written.
This file does not have to exist, but it will be created in the
same directory as LSTFMT if it does not exist.
You may specify any valid Drive:\directory\path\filename.ext.
If this switch is not specified, the output will be sent to the
system terminal (console).
If the <Output_file> cannot be opened, or if none is specified,
then the output will be sent to the system terminal (console).
*WARNING* If the file <Output_file> exists, it will be deleted
and the current output from LSTFMT will be directed to the new
file. Refer to the use of the /A switch for appending output to
existing files.
/S<System_info>
This is specific system information that LSTFMT is to search for
and extract to the output file. This may be any text string.
Each system found which contains this information in the
input_file will be formatted and written to the output file.
This may be system name, sysop name, baud rate, etc.
If no /N net number is specified, all Zones, Regions and Hosts in
the input file will be searched. If a /N net number is
specified, only that net will be searched for this information.
*NOTES* The actual <System_info> string searched for is case
insensitive. That means you can use any combination of upper or
lower case letters and you will get the same results.
Also, using the /T switch may cause the output to be formatted in
such a way so that the text searched for may not be written to
the output file.
/T
This indicates that the /Net output should be formatted for 80
columns. This is handy if you wish to use the output file for
display via a B)ulletins Menu item.
6
28-SEP-1991
/L
This indicates that the output should be formatted for labels.
The output is directed to the device/file specified. This is
really a 'down and dirty' label program. All that it does is
output 3 lines to the output device/file. Each line is preceded
with the Epson double wide character (hex) 0E, and each line is
separated by a blank line. The spacing is designed for the
labels which are 3-1/2 x 15/16 in size. The 3 lines generated
are: 1). SysOp name, 2). System name and 3). Node number.
The 3 lines are centered, based on this label size. Note, that
these labels can only handle about 18 double wide characters
across. So any lines which would be greater than 18 lines will
run off the end of the label. If you direct the output to a file
rather than the printer, you will have an opportunity to manually
edit these lines. This will give you the opportunity to
abbreviate the spelling if you wish. A sample label is as
follows:
Steve Shapiro
LoneStar CBCS
382/35
(of course, on the label they would be double wide). This
functionality is handy if you wish to use the output file for
display via a B)ulletins Menu item. The purpose for which I
developed this functionality is so that we had some simple name
tags for our Net382 pizza parties. It simplified the
introductions as well as automated the generation of the list.
Our NPC (Net Pizza Coordinator) used to have to type it in
manually.
/A
This switch indicates that the output is to be appended to the
output file if it exists, rather than deleting the existing file
first. If the file specified does not exist, it will be
created.
/R
This switch allows for RAW nodelist output. If specified, the
output will not be formatted for display purposes. This switch
overrides the /T switch.
/D
This switch will result in a comma delimited list being produced
which may be used for input into the CVTFON program (written by
Steve Linhart). CVTFON is a program which will produce a
telephone dialing directory for most of the popular comm
programs. For example, the commands:
7
28-SEP-1991
lstfmt /inodelist /ofidonet.cvl /k1,19 /d
if exist fidonet.cvl cvtfon fidonet.cvl=comma fidonet.fon=telix
will produce a comma delimited list for all of Zone 1, Region 19
and place it in the file FIDONET.CVL. CVTFON is then run using
FIDONET.CVL as input, and FIDONET.FON as output. The FIDONET.FON
file produced is for use with the Telix Communications program
produced by Exis, Inc.
Additional FON file support:
There is a program written by Henry Clark of 1:124/6120 in
Dallas, Tx. called FONDIR. FONDIR is a BBS List conversion
utility which uses textual BBS lists as input and produces .FON
files for comm programs. However, FONDIR does NOT support comma
delimited files as input for conversion. So, to use LSTFMT with
FONDIR this is what you do:
First create a text file named FONDIR.TPL containing the text:
+-------------column 1
| +--------column 28
| | +---column 43
| | |
V V V
|n25 |#14 |p4
Then create a batch file:
LSTFMT /INODELIST /OTEXTLIST.TXT /N382 /PSPB
copy fondir.tpl+textlist.txt textlist.inp
fondir textlist.inp /o:t
Then when you run the batch file you will get a TELIX.FON file.
8
28-SEP-1991
/E<echo_area>,<host_zone>,<host_net>,<host_node>,
<your_zone>,<your_net>,<your_node>
Note: while I have split this into 2 lines, it is neccessary that it
all appear on the same line
This switch will cause LSTFMT to create an output file which
conforms to the FTSC definition for a mail packet. A packet and
message header are created, and the message, which is the
extracted output, is appended.
All arguments are required.
The MAXIMUM length of the net/node number is 5 characters. FTSC
only requires up to 4 characters for these numbers, but I have
noticed that some people use special net/node numbers when
dealing with their point systems. If you use numbers longer than
5 characters, the results will be inconsistent and you get what
you deserve.
The echo_area is the echo area in which the message is to be
tossed. This area name may be in upper or lowercase as LSTFMT
will convert it to uppercase. If the area specified does not
exist, the message will be handled based on the mailer program
you are using. ie: Confmail and Qmail will toss it into your
bad_messages area.
The host_zone, host_net and host_node is the zone, net and node
number of your 'parent' node, ie: if you are a node, it would be
your hub, if you are a hub, it would be your host, etc. If you
only want the message sent to your subordinate nodes, then enter
your node number.
The your_zone, your_net and your_node is your zone, net and node
number.
LSTFMT will automatically calculate the filename for the packet.
However, LSTFMT also needs to know where your inbound mail
directory is located. To do this it uses the /O specification.
If the /O switch is blank or omitted, it will place the packet in
the current directory. If the /O switch does specify a
drive:directory\path string, it must be terminated with a final
backslash '\', ie: c:\inbound\.
/K<zone>,<region>,<net>
This switch will cause LSTFMT to produce a shrunK, or pruned
NODELIST file which may be used as input to such programs as
Parselst or Xlatlst. LSTFMT does not attempt to provide the same
kind of versatility as is available with programs such as
ShrinkNl or Prune. The intended purpose of this feature is to
produce a list for the SysOp who only wishes to have a nodelist
which is comprised of his local net, or a small number of
specific nets. This switch overrides the /P, /T and /R
switches.
9
28-SEP-1991
This switch supports 3 required parameters. They are:
1. Zone - Your zone of interest, ie: 1,2,3,99, etc.
2. Region - Your region of interest, ie: 10,11,19, etc.
3. Net - Your net of interest, ie: 142,256,382,9100, etc.
These parameters must be in the order indicated. LSTFMT will
attempt to do some minor error checking, but the burden is on
YOU. It will merely make sure that before it encounters the NET,
it has found the REGION, and before it finds the REGION, that it
has found the ZONE. It will print an error message on the
terminal if these conditions are not satisfied, or if it does not
find the NET.
Each parameter is optional. If you do not specify any Zones,
Regions or Nets, then LSTFMT will ignore this switch. If you
omit the Region and Net number, then LSTFMT will produce a list
containing ALL nodes in ALL Nets in ALL Regions in the Zone
specified. If you omit the Net number, then LSTFMT will produce
a list containing ALL nodes in ALL Nets in the Region specified.
A note on regional independent nodes. If the number you specify
as the HOST is actually a regional independent node, then you
will receive a listing for just that node, rather than an entire
list of nodes under a host.
Bear in mind, even if you specify valid Zones, Regions and Nets,
it may still be wrong. For example, if you specify Zone 1,
Region 20 and Net 632, these are all valid parameters, and they
are in the proper sequence in the nodelist, but Region 20 is in
zone 2 and Net 632 is in Zone 3.
By combining various switches, you can produce a multizone /
multinet nodelist with only the nets of your choice. For
example, if you are a member of FidoNet, EggNet and AlterNet, you
could produce a file which contains information with all 3 of
your local nets included into a single nodelist.
One special note, depending on the nodelist processor you use,
you may have to use the Version 5 nodelist switch when you
process the nodelist and/or when you use your BBS software. ie:
Binkley has a NewNodelist parameter so you would not use it.
This switch supercedes the /N, /S, /P, /T and /R switches.
10
28-SEP-1991
/Pazrtenscypbf
This switch allows for POSITIONAL nodelist output. If specified,
the output will be positionally formatted for display purposes.
This switch overrides the /T switch and the /R switch.
The fields to be output are specified via the argument list.
These are:
1. A - Address. This is a fully qualified network address of
the form zone:net/node. The field width is 14 characters
wide.
2. Z - Zone. The field width is 4 characters wide.
3. R - Region. The field width is 6 characters wide.
4. T - Net. The field width is 7 characters wide.
5. E - Type, ie: any information such as HOST, HUB, etc. The
field width is 7 characters wide.
6. N - Node number. The field width is 5 characters wide.
7. S - System name. The field width is 25 characters wide.
8. C - City. The field width is 25 characters wide.
9. Y - sYsop name. The field width is 21 characters wide.
10. P - Phone. The field width is 16 characters wide.
11. B - Baud. The field width is 5 characters wide.
12. F - Flags. The field width is 25 characters wide.
If the data for any field is larger than the field width, the
data is truncated so that the information may be formatted in the
specified widths.
The output is formatted in the order in which it appears in the
list. So, if you specify /Pnyp, LSTFMT will format the output
as: Node number, SysOp name and Phone number. If you specify
/Pycpb, LSTFMT will format the output as: SysOp name, City,
Phone number and Baud rate.
It is possible to use each field qualifier more than once, but no
more than 7 total may be used.
These switches may be in any order and may be in either upper or lower
case. They must be separated by a space.
11
28-SEP-1991
EXAMPLES:
1). LSTFMT /inodelist.307 /oadmin1.lst /n1
LSTFMT would use the file NODELIST.307 as input. It will create the
output file ADMIN1.LST. It will search NODELIST.307 for the Zone,1
administrative information and format the output for each node in the
net and write it to the file ADMIN1.LST.
2). LSTFMT /N382 /Inodelist /Onet382.lst /T
LSTFMT would determine that the file NODELIST does not exist. It
would then calculate the expected day of the current nodelist. For
our examples, this would be day 307. It would then use the file
NODELIST.307 as input. It will then create the output file
NET382.LST. It will search NODELIST.307 for Host,382 and format the
output for each node in the net and write it to the file NET382.LST.
The text will be written in 80 column format.
3). LSTFMT /oLIST307.CMT /iNODELIST.307 /c
LSTFMT would use the file NODELIST.307 as input. It will copy every
comment line from the input file into the output file.
4). LSTFMT /N2 /Inodelist.307 /csa /Onetz2.lst /T
LSTFMT would use the file NODELIST.307 as input. It will create the
output file NETZ2.LST. It will search NODELIST.307 for Zone,2 and
format the output for each administrative node in the zone and write
it to the file NETZ2.LST. The text will be written in 80 column
format. Only the ;S and ;A comments from the input nodelist will be
witten to the output file.
*NOTE* The comments section is ALWAYS written to the output file prior
to its writing the net information section to the output file.
5). LSTFMT /N9100 /IEGGlist.LST /c /OEGG9100.lst /s9600
LSTFMT would use the file EGGLIST.LST as input. It will create the
output file EGG9100.LST. It will then search the input file for all
of the comments. Once done, it will search all of the nodes in
NET9100 for the text string 9600 and write each node which qualifies
to the output file.
6). LSTFMT /N* /IEGGlist.LST /c /OALLEGG.lst /s9600
LSTFMT would use the file EGGLIST.LST as input. It will create the
output file ALLEGG.LST. It will then search the input file for all of
the comments and write them to the output file. Once done, it will
format and write the information for each node in the nodelist to the
output file. The /s9600 switch is ignored since it is already
formatting the output for every node in the list. The output will be
in 132 column format since the /T switch is not specified.
12
28-SEP-1991
7). LSTFMT /IEGGlist.LST /c /Ob:\EGG9100.lst /s9600
LSTFMT would use the file EGGLIST.LST in the current directory as
input. It will create the output file EGG9100.LST in the root
directory of drive B:. It will then search the input file for all of
the comments. Once done, it will search all of the nodes in ALL of
the nets for the text string 9600 and write each node which qualifies
to the output file.
8). LSTFMT /N382 /Inodelist /c /Oallnet.lst /T
LSTFMT /IEGGlist.LST /c /oallnet.lst /n9100 /a
LSTFMT would use the file NODELIST.307 as input (it would calculate
the 307 automatically). It will then create the output file
ALLNET.LST. It will then search the input file for all of the
comments. Once done, it will search for all of the nodes in net382.
It will format the node information for 80 column output.
With the execution of the second command, LSTFMT would use the file
EGGLIST.LST as input. Upon finding the file ALLNET.LST to exist, it
would append all of the comments found in the EGGLIST.LST file to the
output file. It would then search for all of the nodes in net9100 and
write it to the output file formatted for 132 column output.
9). LSTFMT /N382 /Inodelist.307 /c /O /T
LSTFMT will use the file NODELIST.307 as input. It will send the
output to the system terminal (console). It will produce a list of
the comments and a list of all nodes in NET 382. The output will be
formatted for 80 columns.
10). LSTFMT /N382 /Ia:\list\nodelist.307 /c /O /T /R
LSTFMT will use the file NODELIST.307 on drive A: in the LIST
subdirectory as input. It will send the output to the system terminal
(console). It will produce a list of the comments and a list of all
nodes in NET 382. The output will look just like it does in the raw
nodelist.
11). LSTFMT /N382 /Ilist\nodelist.307 /c
LSTFMT will use the file NODELIST.307 which is in the LIST
subdirectory as input. It will send the output to the system terminal
(console). It will produce a list of the comments and a list of all
nodes in NET 382. The output will be formatted for 132 columns.
12). LSTFMT /N382 /PNSCY
LSTFMT will choose NODELIST.307 for the input file. The /P switch
activates the positional output formatting. The output will be
formatted as: Node number, System name, City and SysOp name.
13
28-SEP-1991
13). LSTFMT /inodelist /oshrnklst.lst /k1,19,382
LSTFMT will choose the current nodelist. It will create a shrunk list
file for Zone 1, Region 19, Net 382. The output will be placed into
the file SHRNKLST.LST in the current directory.
14). LSTFMT /onodelist.lst /k1,19,382 /t /n383 /psny
LSTFMT will choose the current nodelist. It will create a shrunk list
file for Zone 1, Region 19, Net 382. The output will be placed into
the file SHRNKLST.LST in the current directory. The /T, /N and /P
information is ignored.
15). LSTFMT /inodelist /omultilst.lst /k1,19,382
LSTFMT /iegglist.lst /omultilst.lst /k99,912,9100 /a
LSTFMT /inetlist.lst /omultilst.lst /k8,71,7102 /a
LSTFMT will use the current NODELIST to produce a shrunk list for all
of the nodes in FidoNet Net382. It will then use EGGLIST.LST to
produce a shrunk list for all of the nodes in EggNet Net9100 and
append it to that of Net382. It will then use NETLIST.LST to produce
a shrunk list of all of the nodes in NetWork Net7102, and append it to
that of Net382 and Net9100.
The output file can then be used for multizone processing for all of
the nets you belong to in your local area.
16). LSTFMT /Inodelist /onetslist.lst /k1,19
LSTFMT will use the current NODELIST to produce a shrunk list for all
of the nodes in all of the Nets in all of the Regions in FidoNet
Region 19.
17). LSTFMT /Inodelist /N382 /t /Elocal-sysop,1,382,1,1,382,35
LSTFMT will use the current NODELIST to produce an echomail packet
file of all the nodes in Net382 in an 80 column format. It will place
this packet file in the current directory.
18). LSTFMT /N382 /t /Elocal-sysop,1,382,1,1,382,35 /Oc:\inbound\
LSTFMT will use the current NODELIST to produce an echomail packet
file of all the nodes in Net382 in an 80 column format. It will place
this packet file in the c:\inbound directory. When processed, it will
be tossed into the LOCAL-SYSOP echo and sent upwards to the host at
382/1 as well as to any nodes who I feed this echo to.
19). Lstfmt /inodelist /ofidonet.cvl /k1,19 /d
LSTFMT will use the current NODELIST to produce a comma delimited list
for all of Zone 1, Region 19 and place it in the file FIDONET.CVL.
If you have the program CVTFON by Steve Linhart, then you may use this
command:
if exist fidonet.cvl cvtfon fidonet.cvl=comma fidonet.fon=telix
14
28-SEP-1991
CVTFON is then run using FIDONET.CVL as input, and FIDONET.FON as
output. The FIDONET.FON file produced is for use with the Telix
Communications program produced by Exis, Inc.
20). LSTFMT /inodelist /onet382.lab /l /n382
LSTFMT will use the current NODELIST to produce an output file in
Epson label format for all nodes in Net 382.
That's all there is to it.
If you have any ideas for enhancements, modifications, improvements,
etc. feel free and encouraged to contact me. You won't receive any
monetary remuneration, but you may find yourself receiving credit in
the documentation.
15
28-SEP-1991
HISTORY
v1.00 11/06/1989
This is the initial release of LSTFMT.
v1.10 11/12/1989
Thanks to Jim Westbrook of 1:382/29 for this suggestion. You can now
specify a Zone or Region number in addition to a Host number.
v1.20 11/15/1989
Thanks again to Jim Westbrook for his suggestions. Thanks also to
Larry Mundy of 1:170/400 and Bruce Bodger of 1:124/1003 for their
ideas.
Features added to this version:
1. Each input parameter is specified by individual switches.
2. Some parameters are optional. Some features can be combined.
3. Support for 80 column output as well as 132 column output.
4. The ability to search for user specified text strings.
5. The ability to determine the day of the current nodelist for use
with input filename specifications.
6. Only comments with S,U,F,A or E encoding is supported.
7. Added the capability to append output to an existing file.
v1.30 11/18/1989
First rampant bug. The default nodelist date algorithm had a bug
which didn't give the correct nodelist day if you attempted to run it
on Saturday or Sunday. I guess it didn't like working weekends any
more than I do.
v1.40 12/15/1989
1. Eliminated any ability for users to specify an alternate
dir:\path string or wildcards in the input or output filename
specification.
2. Added /N* option for specifying ability to format list for all
nodes in the nodelist.
3. Thanks to Charles Falconer of 1:141/209.1 for his suggestion
regarding the /O switch. LSTFMT will now default to terminal
(console) output if the output file is not specified, or if it
cannot open the output file.
16
28-SEP-1991
v1.50 01/28/1990
1. Added the /R switch for raw output capability. Thanks to William
Collins for this suggestion.
2. Fixed minor bug. If the user created an excerpted version of the
nodelist and ran LSTFMT, there were some circumstances where it
would output a duplicate of the last line in the file. Thanks to
William Collins of for finding this bringing it to my attention.
v1.60 02/18/1990
1. Added the /P switch for positional output capability. Thanks to
William Collins for this suggestion.
2. Eliminated the need for the /I flag. If no input file is
specified, then LSTFMT will look for the current NODELIST.###
file in the current directory.
3. Added Drive and Path support for both the Input and Output
files. Thanks to almost everyone in the net who wanted this
feature.
4. Added capability to produce a ShrunK nodelist. Thanks to Jim
Westbrook of 1:382/29 for this suggestion.
v1.70 04/02/1990
1. Modified the /C switch. Now the user may specify which of the
comments to include into the output.
2. Added the /E switch to allow the user to toss the output into an
echo area for netwide distribution. Special thanks to Kelly
Drown who provided some data structures for the packet
description.
3. Added the /D switch to allow the user to produce a comma
delimited file which may be used as input to the CVTFON program
by Steve Linhart.
4. Modified the /K switch so that independent regional nodes may be
explicitly extracted.
v1.80 11/01/1990
1. Added the /L switch. Now you may produce name labels for those
Net Togethers and pizza parties. Thanks to Bill Degnan of 382/39
for this suggestion.
17
28-SEP-1991
v1.90 07/14/1991
Maintenance release.
1. Updated the docs for greater clarity.
2. Added ability to specify the zone number for the /E parameter.
v2.00 07/24/1991
1. Revised the way in which <FF> form-feeds are utilized. Thanks to
Richard Holler of 1:231/290 for this suggestion.
v2.10 09/10/1991
1. Revised some internal algorithms to speed things up a bit.
2. Compressed .EXE file with PKLite v1.12 and gained a 50% size
reduction. If you experience problems or difficutlties, contact
me ASAP so that I can determine if PKLite caused the problem.
v2.20 09/21/1991
1. Added the AZRTE positional qualifiers for the /P switch.
2. If a node is the net host, the node number is converted from the
net number itself to a zero for printing. ie: a line of the
form:
Host,382,,,,etc.
Would be displayed as 1:382/0 in the formatted output.
3. All formatted listings now display the full network address in
the form of zone:net/node.
4. Added functionality so that if LSTFMT cannot find the nodelist
for the current week, it will try to find the one for the
previous week.
18