| |
ZL4CW > TPK 21.08.96 20:17l 90 Lines 3218 Bytes #-11049 (0) @ WW
BID : 710077ZL4CW
Read: GUEST
Subj: Errata re TPK BEACONs.
Path: DB0AAB<DB0PV<DB0WGS<OE3XSR<OK0PBX<OK0PBB<OK0PAB<PU3DTA<VK3ERM<VK4CJO<
VK4CJO<VK4DGQ<VK4CXX<ZL2TZE<ZL2TZE<ZL2VGB<ZL2WA<ZL4AA<ZL4TAY
Sent: 960820/0023Z @:ZL4TAY.#95.NZL.OC #:25786 Bluff 5.15c $:710077ZL4CW
From: ZL4CW@ZL4TAY.#95.NZL.OC
To : TPK@WW
An ommision on my part will have caused the beacon to be sent out once
only, and then no further beacons. The error was in line 5 of the BEACON
file. I had omitted to put EX BEACON at the end of the A %TIME%+45
command!!!!!
My apoligies to all who were inconvienced.
My only excuse is the late hour that the bulletin was written at, before
it was sent!!!!!!
Here is a re-send of the bulletin with the corrections added;
Having had TPK 1.82 for a while, I often wished it had the feature to
BEACON and to also have a CONNECT TEXT. VK7VEE brought it to my attention
that a timer does exist that will allow a message to be sent out at
regular timed intervals. I should also mention that this is for TPK using
a Baycom style modem.
Where you see ZL4TAY, substitute your BBS callsign.
The following expects that BR ZL4TAY SY is removed from, or a # put in
front of the command, to REM it out of the CONFIG.TPK file. EX BEACON is
entered into CONFIG.TPK, this sends out the BEACON and the FBB sync
request on startup.
The following file I have named BEACON;
Change the text to suit your BEACON TEXT and BBS.
ATT 5
CONV
<<George - Invercargill - TPK 1.82 - PMS is ZL4CW-1>>
BR ZL4TAY SY
A %TIME%+45 EX BEACON
The ATT 5 causes a 5 second delay before sending out the BEACON and the
FBB sync request. This prevents some of the other commands in CONFIG.TPK
from being sent out with the beacon and the FBB SYNC on startup.
The CONV puts TPK into the CONVERSE mode so that the following BEACON text
is sent. I still have to find a more satisfactory way to get out of the
CONVERSE mode, the BR ZL4TAY SY sync request works, and puts it into the
COMMAND mode and is relatively harmless. At present there doesn't seem to
be any key or control sequence that will return TPK to the COMMAND mode,
other than pressing F6.
The A %TIME%+45 EX BEACON sets the timer ticking, so that the present
TIME + 45 minutes expires before the BEACON file is sent out again. I
felt that seeing as the FBB sync request is sent out at the same time,
45 minutes would be a short enough time period for a BEACON.
It is not a good idea to press a key while the BEACON is being sent. In
my case it aborted the BEACON process totally! Pressing F6 returned me
to the command mode, typing A told me there was no timer programs listed,
and typing EX BEACON got the process running again.
Don't type EX BEACON a second time, or you will have two BEACON timers
set, and at different times! Typing EX BEACON sets up more timer programs.
Use the EFA command to remove them till only one timer program exists.
I also didn't know until quite recently that a CONNECT TEXT could be used
with TPK 1.82. The following has to be entered into CONFIG.TPK;
Again, change the text to suit your CTEXT
CMSG ON
CTEXT <<Welcome to TPK 1.82 Type /AIDE or /HELP for help. PMS is ZL4CW-1>>
I should mention that I run a ZLModem (Baycom style) with TPK on a laptop,
and a TNC on my main computer using Winpack. The two computers share the
same transceiver using a LM3900 op amp as a mixer. The PMS in the texts
refers to the TNC.
73 - George, ZL4CW @ ZL4TAY.#95.NZL.OC
Message timed: 11:02 on 20 Aug 96
Read previous mail | Read next mail
| |