home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
HAM Radio 1
/
HamRadio.cdr
/
packet
/
ap381
/
read.me
< prev
next >
Wrap
Text File
|
1989-06-15
|
4KB
|
100 lines
June 10, 1989 - APLINK Version 3.81 - Changes from Version 3.71
To install 3.81, replace your existing USERS.EXE with the one on this
disk and replace your existing AP.EXE with either the AP.AMT or
AP.232 on this disk. Add the parameter NTS=OFF to your APLINK.CNF
file. If you have ARRL bulletins in your system (entered with SA)
they will have to be converted to regular bulletins using your MCB
editor. Your standard help bulletins should be deleted and replaced
with the new ones on this disk using the new SH command. Any others
already in your system will need to be converted to the new help-type
message using your MCB editor. (See below)
____________________________________________________________________
Here is a list of the important changes and fixes in Version 3.81
over 3.71.
____________________________________________________________________
1. There are now only three types of messages that users may input
into the system. Private (SP), NTS (ST), and Bulletin (SB). Any
S-type messages received will convert to SP and any SA-type bulletins
will convert to SB. Amtor users may now add a name to the SB command
to give a bulletin something other than 'ALL' in the TO field.
The sysop has a fourth type of "message", SH. It should be used to
enter help files rather than using the bulletin designator. The
system will never autoforward an SH file so the TO, AT and FROM
fields may be used creatively. Existing help files should be changed
to the new type.
Existing ARRL bulletins must be changed to regular bulletins using
the MCB editor.
These changes make APLINK compatible with the latest practice in
PACKET bbs's.
2. The Sysop commands have been reworked to provide better responses
and more importantly, to provide direct entry of messages into the
system from the keyboard.
The commands Sx <call> and Sx <call> AT <call>, without a file name
following, directly invoke the Norton Editor. The message can then
be typed directly into the editor (the first line being the subject).
Type F3-E to end the message (no NNNN or /EX please), and the message
is in the system. To abort the process just end the editing with
F3-Q-Y. Try it, you'll like it.
There is a new Sysop command 'LP' (for list pending) that lists all
messages in the system with the status 'N' or 'A' (messages pending
forwarding).
2. Some changes have been made in the way NTS messages are handled.
The file NTSOPS.DOC should be studied to understand how it all works.
There is a new sysop command, 'NTS', that lists all NTS messages in
the system not yet archived. From the AMTOR or PACKET ports the same
command lists all NTS messages marked FILED or ACCESSED unless the
config file has NTS=ON in it. In that case . . . well read
NTSOPS.DOC.
3. A new function key command has been added. If you hold 'Alt' and
hit F9 something like the following (with different calls of course)
will be transmitted on the AMTOR channel while in the AMTOR keyboard
mode:
KB1PJ DE W5SMM/4
LOGOUT
And presto you will log off the APLINK station you are talking to.
4. Some minor and not so minor AMTOR autoforward protocol bugs have
been fixed. Still compatible with 3.71 however.
5. A potential for a hang on the PACKET channel has been fixed.
6. A potential for the list command to malfunction has been fixed.
7. A change has been made in the AMTOR user protocol. The AMTOR
user may now end any command with +? if he prefers that to cr/lf.
APLINK will respond the same either way to a valid command. To an
invalid command, if the user uses the +? termination, APLINK will
respond with ?? +? if the station is not logged on, and with ?? GA+?
if the station is logged on.
8. APLINK now extracts the originating bbs call from incoming
message headers where possible and stores it in the mcb. (For future
use.)
9. When a station logs in, he receives a QRU if there is no traffic
for him and QTC #/# when there is traffic. The first number is the
number of messages for him and the second number is the number of
messages he would received if he issued an RFRF connamd.
10. During UPDATE the system looks to see if there is a batch file
named UPDATE.BAT in the APLINK directory. If there is, it is
executed before returning to APLINK. Use it for any housekeeping you
may want to do at update time.
11. A packet timeout bug has been fixed.