home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
High Voltage Shareware
/
high1.zip
/
high1
/
DIR2
/
AUTOS111.ZIP
/
AUTOSEND.DOC
< prev
next >
Wrap
Text File
|
1994-01-10
|
33KB
|
712 lines
┌────────────────────────────────────────────────────────────────────────────┐
│───════────══───══──════════──══════────═════───═══════──══────══──══════───│
│──══──══───══───══─────══────══────══──══───══──══───────═══───══──══───══──│
│─══────══──══───══─────══────══────══──══───────══───────════──══──══────══─│
│─════════──══───══─────══────══────══───═════───═══════──══─══─══──══────══─│
│─══────══──══───══─────══────══────══───────══──══───────══──════──══────══─│
│─══────══──══───══─────══────══────══──══───══──══───────══───═══──══───══──│
│─══────══───═════──────══─────══════────═════───═══════──══────══──══════───│
│ │
│ AutoSend v1.11 │
│ Copyright (c) 1993-1994 by Cris McRae │
│ All Rights Reserved │
│ │
│ An Automatic Subs Request Post Sender │
│ for WWIV v4.22+ BBS Systems │
│ │
└────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────┐
│░░░░ INTRODUCTION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
└────────────────────────────────────────────────────────────────────────────┘
AutoSend allows sub hosts to send posts to new subscribers who auto-request
their subs. The number of old posts to be sent is configurable. This lets
new subscribers more easily join in the discussion of new subs.
AutoSend Features (all are configurable):
■ Graphical packet scanning
■ Sends old posts to new subscribers
■ Keeps log of amount of posts sent
■ Posts sub rules on new subscriber's system
■ Posts subscription lists (colors are configurable)
■ Posts sub ads, rules, etc. on any sub
■ Removes unknown systems from N*.NET files and keeps a log
■ Keeps detailed error log if any errors occur
■ WWIV v4.23 multi-instance compatible
AutoSend conveniently displays packet information as it processes network
packets, so you can see the message types being processed. When an auto-sub
add request is detected, AutoSend checks to see if you host the sub being
requested, and also makes sure that it is auto-requestable.
AutoSend also keeps a log file called AUTOSEND.LOG in your GFILES directory.
You can use this to see who has subscribed to your subs and when. This option
can be turned off if you wish.
AutoSend is very cautious. It will make sure that the node requesting your
subs is still in the network on which the request occurs. It will make sure
that you in fact host the requested sub, and that it is auto-requestable. It
will only send posts that have been network validated, in case there are any
unvalidated posts on a sub that is requested.
┌────────────────────────────────────────────────────────────────────────────┐
│░░░░ REQUIREMENTS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
└────────────────────────────────────────────────────────────────────────────┘
AutoSend requires that you be running NET33+, WWIV v4.22+. AutoSend fully
supports WWIV v4.23 and multi-instance environments.
Here is the formula for finding out the >minimum< amount of memory AutoSend
will need on your system:
minbytes = 120846 + (max_subs * 63) + (max_subs * 89) + (num_nets * 158)
Here I refer to max_subs as the maximum number of subs you have configured in
INIT, and num_nets refers to how many networks are configured in INIT. This
amount is by no means exact, but it does provide a good estimate.
Without this amount of memory, AutoSend cannot function. However, AutoSend
can require >a lot< more than the minimum amount. If you have only a little
more than this amount free (5-10k), you may not be able to run AutoSend. A
rough estimate of the upper bound on the amount of memory required would be
to add 32k to the number you got for the minimum amount of memory.
┌────────────────────────────────────────────────────────────────────────────┐
│░░░░ PROGRAM AUTHENTICITY ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
└────────────────────────────────────────────────────────────────────────────┘
AutoSend has been archived with PKWARE's PKZIP 2.04g using Authenticity
Verification. When you unzip the archive, you should see "-AV" displayed
after every file name. When completed, a message that looks like this will
be displayed:
Authentic files Verified! # KRK282
Cris McRae
If this authenticity statement is not displayed, or the authenticity code is
not "KRK282", then you have a copy of AutoSend that has been tampered with.
Do >not< use any of the files contained within a tampered archive, as they
may contain viruses, trojans, or other harmful things.
AutoSend has also been encrypted by a powerful encryption program. If the
executable file is tampered with, it will display a CRC warning and will not
run.
┌────────────────────────────────────────────────────────────────────────────┐
│░░░░ INSTALLATION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
└────────────────────────────────────────────────────────────────────────────┘
To install AutoSend v1.11, you must unzip AUTOS111.ZIP to your main WWIV BBS
directory. Here is what should be included in the archive:
AUTOSEND.CFG - AutoSend v1.11 configuration file
AUTOSEND.DOC - AutoSend v1.11 documentation file
AUTOSEND.EXE - AutoSend v1.11 executable file
REGISTER.TXT - AutoSend v1.11 registration form
FILE_ID .DIZ - File description
Below, you will find out how to configure AutoSend for your system. Please
read everything before attempting to run AutoSend.
══[ CONFIGURATION FILE SETUP ]════════════════════════════════════════════════
Number of Posts:
AutoSend allows you to configure the number of posts it sends out to new
subscribers. The default value is 5. You may change this value to anything
between 1 and 20. I suggest using the default value.
Log File:
The log file will keep a log of messages sent out by AutoSend. This log file
will be named AUTOSEND.LOG and will be kept in your GFILES directory.
Quiet Mode:
AutoSend can be used in quiet mode. If you enable this mode, the colorful box
that is normally displayed will not appear. Instead, when AutoSend runs, it
will look very much like the network software's display.
Packet Scanning Speed:
While AutoSend scans a packet, it prints out the message info to the screen.
You can adjust the rate at which AutoSend prints this information, so you can
more easily read the packet information as it appears on the screen. This
option is disabled in quiet mode. The scanning speeds are 1, 2, 3, 4, and 5.
The lower the number, the faster the display. While AutoSend is running in
non-quiet mode, you may override the scanning speed by hitting the 'F' key,
and make it go as fast as possible. The 'F'ast mode is convenient when there
is a huge network packet and you do not wish to inspect each message.
Subscription Lists:
AutoSend will generate subscription lists and post them on subs you host.
It fully supports gated subs. AutoSend will generate these subscription
lists automatically on the day of your choice. I suggest you have AutoSend
post them on the 1st of every month. Read the section below entitled
"Subscription Lists" for further information. If you do NOT want to use
this option, simply do not read the section mentioned above.
Here is the sample AUTOSEND.CFG:
Line 1: 5 ; Number of messages to send [1-20]
Line 2: Y ; Do you want logging [Y/N]?
Line 3: N ; Do you want quiet mode enabled [Y/N]?
Line 4: 2 ; Packet scanning speed [1,2,3,4,5]
Line 5: 1 ; Day of month to post subscription lists [1-28]
Line 6: ----- ; Separating line to see colors easier
Line 7: 3 ; Subscription List Color #1
Line 8: 1 ; Subscription List Color #2
Line 9: 9 ; Subscription List Color #3
Line 10: 7 ; Subscription List Color #4
Line 11: 5 ; Subscription List Color #5
Line 12: 2 ; Subscription List Color #6
Line 13: 1 ; Subscription List Color #7
Line 14: 7 ; Subscription List Color #8
Line 15: 9 ; Subscription List Color #9
Line 16: 1 ; Subscription List Color #10
Line 17: 1 ; Subscription List Color #11
Line 18: 2 ; Subscription List Color #12
Line 19: 5 ; Subscription List Color #13
Line 20: 2 ; Subscription List Color #14
Here is a sample subscription list (without colors):
AutoSend v1.11 [Unregistered] (c) 1993-1994 by Cris McRae
Subscription List for "The Imaginary Sub"
Hosted by Ficticious BBS
════════════════════════════════════════════════════════════════════════════
Network: TerraNET Sub Type: 1234 Sub Host: 1234
Node BBS Name Phone Number Speed
───── ──────────────────────────────────────── ──────────── ────────────
1 &Blue Thunder BBS [ASV] 818-848-4101 16800/USR DS
───── ──────────────────────────────────────── ──────────── ────────────
TerraNET Sytems: 1
════════════════════════════════════════════════════════════════════════════
Total Systems: 144
In order for you to configure the color scheme of the subscription lists (if
you even do it, since the stock colors are so nice!), you need to use the
following example. Since there are so many colors to configure, it was
rather hard trying to show what colors are for what part of the list. When
a color # is shown at the beginning of a line, that whole line is colored
with that color. I try to use arrows to point areas that are colored where
possible. My best advice is to experiment. When experimenting, TURN NETWORK
VALIDATION ON, so your test posts do not go out on the network (remember to
delete them!).
#1 AutoSend v1.11 [Unregistered] (c) 1993-1994 by Cris McRae
#2 Subscription List for "The Imaginary Sub"
#3 Hosted by Ficticious BBS
#4 ══════════════════════════════════════════════════════════════════════════
┌── #5 ┌── #6 ┌── #5 ┌── #6 ┌── #5 ┌── #6
Network: TerraNET Sub Type: 1234 Sub Host: 1234
#7 Node BBS Name Phone Number Speed
#8 ───── ──────────────────────────────────────── ──────────── ───────────
#9 1 &Blue Thunder BBS [ASV] 818-848-4101 16800/USR D
└── #10 (the &,%,^ symbols)
#8 ───── ──────────────────────────────────────── ──────────── ───────────
TerraNET Sytems: 1
└── #11 └── #12
#4 ══════════════════════════════════════════════════════════════════════════
Total Systems: 144
└── #13 └── #14
══[ NETWORK INSTALLATION ]════════════════════════════════════════════════════
Create a file called EPREPROC.NET in >each< network data directory with the
"AUTOSEND.EXE" on the first line.
If you are using PackScan or another preprocessor, you may already have an
EPREPROC.NET in each of your network data directories. You can simply add
"AUTOSEND.EXE" either at the top or bottom of EPREPROC.NET. Each program
listing should be on a separate line.
══[ SUB RULES SENDING ]═══════════════════════════════════════════════════════
If you want AutoSend to send sub rules along with old posts, you must name the
rules files Nxxxxx.RLZ where xxxxxx is the sub type. So if you host sub type
1234, the rules file for that sub would be N1234.RLZ. This file should be
placed in the appropriate network data directory.
If you host a sub on multiple networks, using the same sub type, you may place
the Nxxxxx.RLZ file for that sub in the GFILES directory, instead of placing
a copy in the directory for each network the sub is hosted on.
If you have the same rules for all the subs you host, you can use the
GLOBAL.RLZ rules file. Place this file in your GFILES directory.
If GLOBAL.RLZ exists, but you want to override it for certain subs, just
create the Nxxxxx.RLZ file. AutoSend will detect the Nxxxxx.RLZ file and use
it instead of the global rules file.
══[ SUBSCRIPTION LISTS ]══════════════════════════════════════════════════════
AutoSend can create subscription lists. In order for AutoSend to know what
subs you would like to have the lists posted on, you need to create a file
in your main BBS directory called AUTOLIST.DAT. The format for the file is
shown below:
SUB1 DAY
SUB2 DAY
Each line must contain the FILENAME of a sub you host. You can find the
filenames in BOARDEDIT. They DAY field is completely >optional<. AutoSend
will default to the day of the month set up in the AUTOSEND.CFG file if you
leave this field blank. If you do list a day here, it must be a number
between 1 and 28. This optional date is useful if you want to post subscriber
lists on different subs on different dates.
You can find the filenames in BOARDEDIT. Here is an example:
NN AR Name FN RSL PSL AG MSG SUBTYPE
=== == --------------------------------------- ======== --- === -- === -------
24 O JAFO's Software Support JAFOSUP 30 30 0 50 JAFOSUP
As you can see, the filename ("FN") is JAFOSUP. So I would list JAFOSUP in my
AUTOLIST.DAT if I wished to have subscription lists posted on this sub.
In order for AutoSend to send subscription lists, you need to call AutoSend
like this:
AUTOSEND /SUBLIST [/AUTOPOST] [/REMOVE]
You should put the above line in your daily or external event batch file. The
/AUTOPOST and /REMOVE options can be used on the same command-line if you use
those features.
NOTE: If AutoSend locks your system up during the daily event, it probably
means you do not have enough memory free. The external event provides
a lot more memory, so you should probably run it there if you have
problems during the daily event.
This feature can make AutoSend use a >LOT< more memory than normal. It
all depends on how big your subscriber lists are. Some subs will have
so many subscribers that subscription lists will actually get cut off
at the 32k limit.
══[ AUTOMATED POSTING ]═══════════════════════════════════════════════════════
AutoSend can post sub ads, rules, etc. automatically. In order for AutoSend
to know what files you would like to post, and what subs to post them on, you
need to create a file in your main BBS directory called AUTOPOST.DAT. The
format for the file is shown below:
DAY FILENAM1.EXT SUBFILE1 Post title #1
DAY FILENAM2.EXT SUBFILE2 Post title #2
The first item on each line is the day of the month that you would like that
message posted. This is >not< optional as it is in the subscriber list
configuration file. This can be any number between 1 and 28. The second item
is the filename of the file you would like posted (i.e. MYSUBAD.ANS,
whatever). The third item is the FILENAME of the sub as listed in BOARDEDIT.
This is very similar to the subscription list setup. The last item is the
post title for that message. If you leave it blank, the post title will
appear blank. The title can be up to 60 characters long.
Here is an example AUTOPOST.DAT file:
5 MYGENERL.ANS GENERAL Advertisement for my general sub
10 FUNNY.ANS JOKES Advertisement for my joke sub
Note that each line has a maximum size of 100 characters. This is provided
so you can space out each item as you wish (you can put more than one space
between fields, but do not put more than necessary as anything past 100
characters will be chopped off). Note that there can be >NO< spaces before
the first item. The above example demonstrates the use of spacing perfectly.
The first message will be posted on the sub that uses the GENERAL filename on
the 5th of every month, using the given post title. The second message
(FUNNY.ANS) will be posted on JOKES on the 10th day of every month, using the
given post title.
You should put the files you would like posted in either your GFILES directory
or the appropriate network data directory for the sub you would like to post
the message on. If the sub is gated, AutoSend will search all the network
directories the sub is hosted on until it finds the specified file. If it
does not find it, then it will print an error message.
In order for AutoSend to post messages automatically, you need to call
AutoSend like this:
AUTOSEND /AUTOPOST [/SUBLIST] [/REMOVE]
You should put the above line in your daily or external event batch file. The
/SUBLIST and /REMOVE options can be used on the same command-line if you use
those features.
NOTE: If AutoSend locks your system up during the daily event, it probably
means you do not have enough memory free. The external event provides
a lot more memory, so you should probably run it there if you have
problems during the daily event.
This feature can make AutoSend use a >LOT< more memory than normal. It
all depends on the size of the files you are posting. If you post a
32k ANSI file, expect AutoSend to use it's base 160k requirement plus
32k for that file to be read into memory.
══[ REMOVING UNKNOWN SYSTEMS ]════════════════════════════════════════════════
If you would like AutoSend to remove unknown systems from your N*.NET files,
simply call AutoSend like this:
AUTOSEND /REMOVE [/SUBLIST] [/AUTOPOST]
You should put the above line in your daily or external event batch file.
AutoSend will create a file called AUTOREM.LOG in your GFILES directory.
This log file shows all systems removed during the /REMOVE process. This
feature is enabled if you have logging enabled in the .CFG file.
NOTE: You can combine the /REMOVE, /SUBLIST, and /AUTOPOST options. Simply
list both of them on the command-line. It is unnecessary to call
AutoSend twice to do each option.
┌────────────────────────────────────────────────────────────────────────────┐
│░░░░ MANUAL USE ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
└────────────────────────────────────────────────────────────────────────────┘
Normally, AutoSend is run by the WWIV network software automatically. If,
however, you want to send posts to a system automatically, you may do so with
the manual post send feature of AutoSend.
The manual send command-line is:
AUTOSEND <sub type> <node> <.net> [num msgs]
The sub type may be alphanumeric. The node is the system to which you want to
send posts. The network number is the network number as shown in INIT minus
one. If you are familiar with the "dot" commands of net31+, then you should
be able to use the "dot" command of AutoSend with no problems.
Here is an example. I am @8861 in WWIVnet, and host sub type 8861. WWIVnet
is my third network. So if I want to send posts on sub type 8861 to @1234, I
would type:
AUTOSEND 8861 1234 .2
Remember, subtract one from the network number as shown in INIT. If all goes
well, AutoSend should report that posts were sent to the node you specified.
The number of messages to send is not required. This option is only needed if
you want to send more than the default number of messages defined in
AUTOSEND.CFG.
══[ ERROR LOGGING ]═══════════════════════════════════════════════════════════
If AutoSend encounters a problem, it creates a file called AUTOSEND.ERR in the
same directory your executable file is located. AutoSend will try to be as
specific as possible, telling you when the error occured, where the error
occured (during what process), and what the exact error was.
Here is a list of areas AutoSend will report errors in:
N/A - Not applicable
Register - Registration process
AutoSend - Automated network control
Man Send - Manual sending
SendRule - Rules sending
SubList - Subscription list posting
AutoPost - Automated post sending
Remove - Removing systems from host files
Config - Configuration file setup
══[ WWIV MODIFICATION FOR USE WITH MANUAL SEND]═══════════════════════════════
For those who have registered WWIV, I have written a small modification to aid
in sending old posts to new subscribers when using WWIV v4.23's 'N' command
at the mail read prompt. With this modification installed, you will be asked
whether or not you would like to send starter messages to the new subscriber,
and if you answer yes, it will send the default number of posts as found in
AUTOSEND.CFG file.
This modification is on "void add_netsubscriber" in READMAIL.C. You should
simply replace this function with the one below:
void add_netsubscriber(unsigned short sn)
{
char s[10], s1[10], ns1[80];
FILE *host;
if (!valid_system(sn))
sn=0;
nl();
prt(1,get_string(1265));
nln(2);
prt(2,get_string(1266));
mpl(7);
input(s,7);
if (s[0]==0)
return;
strcpy(s1,s);
sprintf(ns1,"%sN%s.NET",net_data,s);
if (!exist(ns1)) {
nl();
ansic(6);
npr("%s%s",get_string(1267),ns1); nl();
return;
}
nl();
if (sn) {
outstr(get_string(1268));
npr("%u.%s",sn,net_name);
outstr(get_string(1269));
npr("%s? ",s);
}
if (!sn || !ny()) {
prt(2,get_string(1270));
mpl(5);
input(s,5);
if (!s[0])
return;
sn=atoi(s);
if (!valid_system(sn)) {
npr("@%u%s%s.", sn, get_string(1271), net_name);
nl();
return;
}
}
sprintf(s,"%u\n",sn);
host=fsh_open(ns1,"a+t");
if (host) {
fprintf(host,s);
fsh_close(host);
}
if (exist("AUTOSEND.EXE")) {
outstr("AutoSend starter messages? ");
if (yn()) {
sprintf(ns1,"AUTOSEND.EXE %s %u .%d",s1,sn,net_num);
run_external1(ns1);
}
}
}
┌────────────────────────────────────────────────────────────────────────────┐
│░░░░ SPECIAL NOTICE ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
└────────────────────────────────────────────────────────────────────────────┘
AutoSend has the ability to detect special message types (27/500) sent from
the author, and can return specific information about the version of AutoSend
you are running, as well as your registration status. In addition to this,
it will send the name of your BBS as spelled in INIT, to make registering
the software easier for the author, since the registration key code is based
on how you spell your BBS name in INIT.
This information is >only< sent to the author. Nobody else should send the
27/500 messages to you, and if they do, you should report them to the author.
Although the author has the ability to send out the 27/500 at any time, it
would be excessive to send more than one in any short period of time. The
author will probably send out a 27/500 message approximately 3 or 4 times
per year on the major WWIV networks.
In additional to being able to receive these 27/500 messages, AutoSend also
sends your AutoSend information to the author on a monthly basis, if you
happen to be on a network that the author on. This method provides an
excellent way of informing the author about who is using AutoSend, and also
removes the necessity of sending out a 27/500 message to >all< systems on a
given network.
If you do not wish the author to receive any information about your copy
of AutoSend, because you feel it is a violation of privacy, then you have
the right not to use this software. The author feels that knowing what
versions people are running is helpful in case an old version is dangerous
or defective.
Finally, the author will not hassle anyone about using the software beyond
the evaluation period. If you do, that is your decision. The author hopes
that, if you are using the software beyond the evaluation period, you will
deem the software to be useful and register it.
┌────────────────────────────────────────────────────────────────────────────┐
│░░░░ REGISTRATION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
└────────────────────────────────────────────────────────────────────────────┘
AutoSend is shareware. This gives the user an opportunity to evaluate the
program before actually registering the software. If, after a 30 day period,
you wish to continue to use AutoSend, you are required to register your copy
of AutoSend with the author. To register, please fill out REGISTER.TXT and
send it to:
Cris McRae
P.O. Box 1351
Burbank, CA 91507
Registration is $15.00 US per copy of AutoSend.
Note: Registration system used is REGKEY.
┌────────────────────────────────────────────────────────────────────────────┐
│░░░░ DISCLAIMER ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
└────────────────────────────────────────────────────────────────────────────┘
The author makes no warranties, expressed or implied, as to the quality or
performance of this program. Your use of this program constitutes your
release of the author from liability or litigation for any indirect or
consequential damages arising from the use of this program or its associated
files.
In no event will the author be liable to you for any damages, including any
lost profits, lost savings or other incidental or consequential damages
arising out of your use or inability to use the program, or for any claim by
any other party.
┌────────────────────────────────────────────────────────────────────────────┐
│░░░░ REVISIONS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
└────────────────────────────────────────────────────────────────────────────┘
Version 1.00 (07/25/93)
■ Initial release
Version 1.01 (07/26/93)
■ Fixed incorrect reporting that a sub was not auto-requestable instead of
printing the subscriber was already subscribed.
■ Fixed incorrect reporting that posts were sent when they actually were
not. This was because I initialized a variable outside a critical loop.
Version 1.02 (08/09/93)
■ Cleaned up code a little.
■ Fixed bug in alphanumeric sub type checking. Earlier versions sent posts
from the >first< sub with an alphanumeric sub type no matter which
alphanumeric sub type was requested.
(Bug found by Elston Gunn)
■ Added sub rules sending
■ Added configurable packet scanning speed
■ Added quiet mode
Version 1.03 (09/08/93)
■ WWIV v4.23 multi-instance compatible
(Thanks to Wayne Bell and Jim Wire)
■ Added manual send feature
(Requested by Sky)
■ Added a system check to make sure node you send posts to is actually in
network
■ Added 'F'ast mode
■ Changed graphical display
■ Changed quiet mode to look more like network software display
Version 1.04 (09/16/93)
■ Fixed registration routine bug (only found in v1.03)
(Bug found by The Posse)
■ Updated main type 27 message reporting
Version 1.05 (09/21/93)
■ Fixed two problems with the manual send feature
1. Could not send posts to systems that already were subscribers
2. Could not send posts on subs unless they were auto-requestable
(Bug found by Sky)
Version 1.06 (09/26/93)
■ Added DISALLOW.NET check before sending posts.
(Bug found by Chris Yarnell)
■ Fixed deleted message reporting. Deleted network messages have a major
type of 65535, and this messed up AutoSend's display. This has been
fixed.
Version 1.07 (09/30/93)
■ Fixed DISALLOW.NET checking. It seems I forgot to make a final variable
check before sending posts.
(But found by Chris Yarnell)
Version 1.08 (10/09/93)
■ Fixed another bug in the DISALLOW.NET checking routine. If DISALLOW.NET
was not found when a sub auto-req was detected, AutoSend would quit.
Version 1.09 (12/01/93)
■ Changed the WWIV v4.23 multi-instance code. Now uses Wayne Bell's file
sharing disk I/O routines.
■ Added ability to post subscription lists.
■ Added ability to remove unknown systems from N*.NET files and keep a log
of systems removed.
■ Increased registration fee from $5 to $15.
Version 1.10 (12/18/93)
■ Added ability to send Nxxxx.RLZ file from GFILES directory if it exists.
This helps if you host the same sub type on many different networks.
(Requested by ShadowSpawn)
■ Added modification to help registered WWIV sysops send starter posts to
new subscribers when using the 'N' command from the mail read prompt in
WWIV v4.23.
(Requested by ShadowSpawn)
■ Colors in sub titles are now stripped in subscription lists.
■ Added full color configurability to the subscription lists.
Version 1.11 (01/10/94)
■ Fixed bug that occured when a group BBSLIST or CONNECT update was
received. In Version 1.10 >only<, "%hu Update" was displayed.
■ Fixed halting problem under multi-instance environments. Versions 1.09
and 1.10 locked the STATUS.DAT during automatic network control and thus
halted other instances trying to read or write to STATUS.DAT until
AutoSend had finished.
■ Fixed minor bug when using AutoSend v1.10 on instances greater than 1.
It used the TEMP directory of instance 1 in all cases. This version
correctly uses the different TEMP directories set up under multi-instance
environments.
■ Added ability to post messages on subs automatically.
■ Removal of unknown systems is now done before generating subscription
lists or posting messages when combining those options. This makes sure
that AutoSend does not send messages to an unknown system, which could
lead to an unwanted DEAD.NET packet.
■ Changed the unknown system removal display. AutoSend now shows it's
progress, although it's so fast you probably can't read what it displays!
■ Changed the range of different speeds for packet scanning. New choices
are 4 and 5 (5 being the slowest rate possible).
■ Added display of "Sub not hosted here" when either you receive a sub auto-
req on a sub type not hosted locally or if you try to manually send posts
on a sub you do not host.
■ Added complete error logging.
■ Changed modification slightly to check for the existence of AUTOSEND.EXE
before trying to run it.
┌────────────────────────────────────────────────────────────────────────────┐
│░░░░ CREDITS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
└────────────────────────────────────────────────────────────────────────────┘
AutoSend v1.11 Copyright (c) 1993-1994 by Cris McRae
WWIV is Copyright (c) 1988-1994 by Wayne Bell
WWIVnet Software is Copyright (c) 1988-1994 by Wayne Bell
PKZIP is Copyright (c) 1989-1994 by PKWARE Inc.
REGKEY is Copyright (c) 1992 by Brian Pirie
Thanks:
King Lerxt 1@8863 WWIVnet for asking me to write this program, and for
helping me debug it.
Chris Yarnell 1@2914 WWIVnet for testing v1.09.
Everyone on WWIVnet who has supported my side on the 27/500 debate.
If you have any comments or questions about this program, you can reach me
at the following network addresses:
TerraNET : 1@1
WWIVnet : 1@8861
IceNET : 1@8857
SOLARnet : 1@8857
TARDISNet: 1@8857
WWIVLink : 1@18857
Internet : cris.mcrae@panasia.com
If you are a sysop on one of the above WWIV networks, you may also subscribe
to my support sub. The sub name is "JAFO's Software Support". The sub type
is JAFOSUP.
You may also call my BBS system:
Blue Thunder BBS
USR 16.8 HST Dual Standard
Open 24 Hours
(818)848-4101