home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
MISC
/
MN324LNX.ZIP
/
old_docs
/
history.txt.bak
< prev
next >
Wrap
Text File
|
2004-07-09
|
20KB
|
499 lines
MakeNL Revision History
V2.53.14 -- July 4th, 2004 -- Several Changes by MakeNL: NG Team
Changes Linelength to a define and set it from 160 characters
to 512. Should alleviate limitations for future nodelist
expansion.
Untied Pvt & -Unpublished- It is now possible to have a non
Pvt node to use -Unpublished- if they are ION.
This version should not be used on a production system.
[YOU HAVE BEEN WARNED] <g>
V2.52 -- April 16, 1998 -- Y2k patch (Björn Felten -- 2:203/0)
Patched the year written in attach and reciept mail.
Removed the check for Hi ASCII and "erroneous" baud rates.
Reformatted PRN files into TXT files.
V2.51 -- June 15, 1992 -- Maintenance release
To check for erroneous duplicate numbers, MakeNL maintains a
stack of zone numbers, region/net numbers within the current
zone, and node numbers within the current region/net.
FidoNet Zone 1 was about to overflow this stack. This
release changes the stack implementation. It is now limited
only by available memory.
The entire program was recompiled with MS C V7.0 and several
minor changes were made to eliminate new warnings.
V2.50 -- February 12, 1991 -- New features
By default, the first line of distribution lists from
earlier versions contained "FidoNet Nodelist for. . ."
FidoNet is a registered trademark of Tom Jennings. While
Tom hasn't complained about this behavior, he has every
right to, so now the default is " Nodelist for. . ." (no
name at all).
Since version 2.00, the /N command line switch would insert
a name other than "FidoNet" in the first line, and it still
does. A new configuration verb, NAMe, has been added to do
the same. The difference is that now, if you really want it
to say "FidoNet Nodelist for. . ." you have to explicitly
tell MakeNL the name is "FidoNet" by one of these methods.
I am told that some mailers require all out-going messages
to contain the ^AINTL extended address kludge. With a lot
of grimacing and head-shaking, I have added the capability
to force MakeNL to do this. See the SUBmit verb in
MAKENL.PRN.
V2.41 -- January 25, 1991 -- Code bug, documentation bug
There are only two ways MakeNL can know your zone number.
You explicitly tell it in your NETADDR statement, or, if you
are making a zone list, MakeNL can guess it. Failing either
of these methods, your zone number is set to zero. Usually
this doesn't matter, but. . .
If MakeNL generates a message to a zone-qualified address,
and he doesn't know your zone (i.e. your address is set to
zone 0), MakeNL failed to notice and both the message header
and the INTL kludge were generated malformed. This has now
been fixed. Under the stated condition, MakeNL will issue a
warning and NOT generate the message.
Last time I added the PUBlish verb to the code. This time I
added it to the documentation!
V2.40 -- December 1, 1990 -- New features.
Version 7 of ARC uses considerably more memory than earlier
versions. MakeNL now checks free memory, and if there is
less that 256K, it swaps itself out of memory before execut-
ing ARC. If there is an expanded memory driver loaded, and
enough expanded memory available, MakeNL will use it for
swap space. Otherwise it swaps to a temporary disk file.
When swapped out, only about one kilobyte plus your environ-
ment space remain in memory. This behavior is transparent
to users, and requires no action on their part.
A new configuration verb, BAUdrate, was added to permit
redefinition of MakeNL's baud rate validity table. This
allows for future growth without continual recompilation.
See section 6.1.6 on page 24 of the documentation for
complete details.
Added a second configuration verb, PUBlish, to define a
publication day other than Friday.
V2.31 -- August 8, 1990 -- New feature, bug Corrected.
Added ARC <n> control verb, where <n> may be either 5 or 6.
It is used to force ARC version 6 or 7 to create level-5 or
level-6 compatible archives. Note that it will cause errors
if <n> is greater than or equal to your ARC version number.
MakeNL had another string length error. A 12-character
array was having a string of up to 12 characters scanned
into it. That doesn't leave much room for the null termi-
nator. The size of the array was increased.
V2.30 -- June 3, 1990 -- New feature, bug Corrected.
Added MINPHONE control verb. If causes MakeNL to reject
phone numbers with fewer than a defined minimum number of
parts. (See documentation.)
A file entry in the FILES section of a control file may in-
clude an alternate notification address. MakeNL was limit-
ing the length of this address to seven characters -- a bit
confining. The string has now been extended to 17 charac-
ters. This will permit an alternate address with a 5-digit
zone, a 5-digit net, and a 5-digit node number.
FTS-0005.TXT was added to the distribution. It is the re-
placement document for FSC002-3.
2
The documentation was updated to reflect these changes, how-
ever the sample control files were not changed to include
any instances of MINPHONE.
Recompiled the entire program using MSC 6.00, which resulted
in about 10% reduction in size of .EXE file.
V2.20 -- 10/06/89 -- Significant Bug Corrected.
Why this one wasn't reported before now is beyond me! When
MakeNL received more than one new submittal difference file
at once, all but the first would fail to apply because the
CRC was not being reinitialized. RCs probably don't get
many difference files, but how could DD go a year and a half
without noticing this problem?
The program salutation and the documentation title page were
changed to reflect the new release level.
The obsolete "FSC002-3" was dropped from the distribution
archive.
No other changes were made.
V2.12 -- 05/31/88 -- Bug(?) Corrected.
For some reason (as yet unidentified), memory allocation in
the difference analyzer (changed in V2.11) behaves badly
when MakeNL is executed on an 8088 machine. This release
modifies the routine to get around the problem, and should
work in the most adverse conditions (I hope).
V2.11 -- 05/15/88 -- New behavior.
The FidoNet nodelist has become larger than earlier versions
could produce difference files for. The current version's
difference analyzer has been modified to segment long files
and analyze the segments. After a segment is analyzed, the
differences are output, then processing proceeds to the next
segment.
Some time ago, Tom Marshall, IFNA Council, pointed out that
any copyright contained in the original document should also
be contained in any published difference file. The program
at that time was forcing about four lines of the notice into
the difference file. Since I was modifying the routine that
does it anyway, the difference analyzer was also modified to
force any copyright notice in full into the difference file.
The changes made do not affect documentation, and it was not
changed.
V2.10 -- 04/12/88 -- New feature, docs updated, minor bug fixed.
3
A new control file statement, "PRIvate," was added to the
repertoire to control the processing of private nodes in
networks which discourage or do not permit them.
The documentation received many cosmetic changes. Some of
the change bars merely reflect the movement of figures to
produce better pagination. The substantive changes are doc-
umentation of the /NAMe command line switch and the PRIvate
control file statement.
The /NAMe command line switch was added in version 2.00, but
seems to have been overlooked in the documentation, includ-
ing this file. It provides the capability of changing the
network name placed on the first line of a composite list.
One minor bug was discovered which could cause problems only
with a rare combination of events. Since I have had no re-
ports on it, I guess no one ever noticed it, but I fixed it
anyway!
V2.03 -- 03/12/88 -- Bug fixed
A bug was introduced in 2.02 which caused the PVT and OGATE
keywords to be exchanged on output. This, of course, pro-
duces a very confused nodelist!
IT IS IMPERATIVE that if you ran V2.02 in process mode, that
you upgrade to 2.03 IMMEDIATELY. Errors generated by 2.02
will "stick" until 2.03 corrects them. Note that this cor-
rection should be automatic and require no intervention on
your part.
No other changes were made in this version. There were no
documentation changes.
V2.02 -- 03/05/88 -- Bug fixed, added feature
If the first data file is not processed (happens frequently
in test mode) MakeNL returned an erroneous result code. The
problem was caused by an uninitialized variable. You would
not notice this one until you tried to use MakeNL's result
codes to automate weekly processing in a daily event in your
batch file.
One minor feature was added. MakeNL will now accept the
keyword "OGATE" in a net list. (OGATE is invalid in a
Region.) In order to use OGATE, you and all coordinators in
the chain above you must be using V2.02! Earlier versions
of MakeNL will reject the OGATE keyword. For this reason,
the documentation has not been updated to reflect it's
support at this time.
No other changes were made in this version. There were no
documentation changes.
4
V2.01 -- 01/16/88 -- Bug fixed
Found a bug that's been there since the beginning of time.
Wonder why nobody ever reported it??? In the FILES section
of the .CTL and explicit file name might be as many as 12
characters (file name (8) plus "." (1) plus extension (3)),
but the field width was set to 11!
The only other changes made in this version is that the
entire package has been recompiled with MS C 5.0. Please
advise me immediately of any problems encountered!
Documentation has not changed, however, the order of this
file was reversed (newest version first).
V2.00 -- 12/28/87 -- Distribution restrictions removed
Ken Kaplan expressed concern over the logistics of the re-
quirement for IFNA control of the distribution of MakeNL.
Therefore, with this release distribution restrictions are
removed and MakeNL will be distributed as "shareware" in the
future. See section 9 in MAKENL.PRN for details.
New feature:
This release extends the level of NL maintenance all the way
to individual nodes. Note that Coordinators may still fully
maintain their segments if they wish, but now they may also
require each node to maintain its own entry in the list.
If you wish to make use of this feature, I suggest you cre-
ate a file for each node in your segment and mail it to the
applicable node with a message text reading "Enclosed is a
file containing you nodelist entry. If there are any
changes, edit this file and mail it back to me. DO NOT
CHANGE THE FILE NAME." Replace each NL entry with an appro-
priate NODE entry in the FILES section of your control file,
set up an external event to execute MakeNL daily, and forget
about 'em.
Old feature:
The "indentation" feature of the files section of the con-
trol file was designed as "cut-over" aid, and should no
longer be needed. MakeNL still supports it, but all refer-
ences to it have been removed from the documentation. The
next release will remove it from the program.
Several minor bugs were found and fixed.
DOCs with change bars:
MAKENL.PRN received more updates than the program did!
Change bars have been added in the right margin to reflect
5
changes since V1.21. Figures 2 through 7 were moved to
avoid several nearly blank pages. Since the change bars
were added automatically, this action caused several in-
stances of false change bars. Oh well, you can't have
everything. Nothing that WAS changed escaped being marked.
It's just that some marked passages were not actually
changed.
V1.21 -- 11/14/87 -- MERGE clarified
The requirements for the MERGE option were not clear, and
code did not test that necessary network address information
was present. So:
1) Added ability for MakeNL to select a default net-
work address based on MAKE command if NETaddress
data is missing.
2) Changed MERGE to use the first zone it finds in
the distribution file if no zone address is
available.
3) Changed MERGE to cancel if no region or net ad-
dress is available. This only happens when MAKing
a HUB, and no NETaddress command is given.
Added "change bars" to right margin of documentation. This
edition reflects changes since V1.10.
V1.20 -- 11/08/87 -- Bug fixes, one added feature
Bug fixes:
1) This wasn't really a bug. The MS library date/time
handling routines seem to make automatic adjust-
ments for DST (at the wrong cross-over points, I
might add). According to their docs, setting the
environment variable "SET TZ=CST+6" should turn it
off, but they lie! They recognize the minus sign,
but not the plus sign.
"SET TZ=CST6" will turn it off, but MakeNL can't
rely on that being set right.
The problem occurs just after the date MS thinks a
change to or from DST should have happened and you
run MakeNL within an hour the wrong side of mid-
night. Day numbers for backward dates get screwed
up because the time gets shifted across the mid-
night boundary, and MakeNL can't find its master
files!
Well, it's fixed, and I'm sorry for any inconve-
nience it may have caused.
6
2) Fixed a problem in renaming master files two weeks
old. (They were being deleted.)
3) Fixed a similar problem renaming output master
files when no changes occur.
4) Fixed some minor problems surrounding the creation
of archives and difference files. If you specify
an OUTDIFF parameter, you should force the cre-
ation of archives as well as difference files,
EVEN IF NO CHANGES OCCUR AND YOU WOULD OTHERWISE
GENERATE NEITHER! Now you do.
New Feature:
If you use a generic OUTFILE name, and if you create differ-
ence and/or archive files, they tend to accumulate in your
OUTPATH di rectory over time. By default, MakeNL ignores
them completely. This is done so that OUTPATH can point to
a "download" directory where several editions might be made
available to users.
I had some complaints about this behavior. Some users don't
appreciate having to "clean up after MakeNL!" So, I added
the CLEanup command to MakeNL's repertoire in this version.
When MakeNL operates in process mode and CLEanup (no argu-
ments) appears in the control file, after all other process-
ing is done, it searches the OUTPATH directory for old dif-
ference and/or archive files and deletes any it finds.
CLEanup has no effect on current files or the handling of
output master files. It has no effect whatever when MakeNL
is operated in test mode.
V1.10 -- 08/19/87 -- Bug fixes
This release is mostly bug fixes, but a new feature has been
added, and behavior has been modified in one respect.
Bug fixes:
1) A check was added to insure that all defined data
directories are distinct. V1.00 loses files if
two are defined for the same directory.
2) Corrected a bug in the parsing of the /M command
line switch.
3) Added a check for and removal of IBM extended
characters in text fields.
4) Corrected file move operation to account for the
use of the DOS JOIN command.
7
5) Corrected bugs in directory (path) verification.
In fact the function was rewritten, and is (I
hope) close to bullet proof.
6) Removed the use of "DOS COPY" to eliminate false
warning messages.
Added feature: Added the "NOTIFY SELF" statement to control
file.
Modified behavior: ALL output except merge file goes in the
defined OUTPath directory, or if not defined, in the MASter
directory. V1.00 places submittal and distribution files in
the current directory.
V1.00 -- 08/11/87 -- Initial Release
8
