| |
G0TEZ > PACKET 27.11.11 11:04l 49 Lines 1461 Bytes #999 (0) @ WW
BID : C30111G0TEZ
Read: GUEST
Subj: Re: VK6BE > before Winpack
Path: IZ3LSV<IK2XDE<DB0RES<DK0WUE<7M3TJZ<CX2SA<GB7CIP
Sent: 111127/0341Z @:GB7CIP.#32.GBR.EU #:18270 [Caterham Surrey GBR] $:C30111G0
From: G0TEZ@GB7CIP.#32.GBR.EU
To : PACKET@WW
Quite right Bob.
I don't remember all the programmes I have tried but a lot of them, even
as far back as PaKet 5 and PaKet 6, had various automatic features such as
collecting and decoding 7Plus.
The first fully automatic prog i was going to try was FBB 5.15, courte4sy
of a friendly sysop bit, just in time, I discoverd TPK which was written
by F6EBN, a friend of F6FBB. They both used the same website so, not
surprisingly,TPK was written to communicate automatically with BBSs using
FBB, which was most of them. I even used a script file to stop TPK txing
during peak periods because someone complained that my system was set to
be too "aggressive" and was causing a disconnect. One of the beauties of
TPK was it could be simple or clever depending on how you felt.
One example is the CONFIG.TPK file where you can add all sorts of
instructions such as:
BR RXMSG TO PACKET @ WW
and it will automatically connect and download every message to that
topic.
Such line as:
BR RJMSG TO LANDY would make all messages to the topic of landrovers
disappear while,
BR RJMSG FROM G4EBT
Would do the same to an unwanted station.
Winpack + Telnet will not do any of this, certainly not over the 'net.
The above were very useful when we were getting over 200 headers per day.
One prog I really do miss.
73 - Ian, G0TEZ @ GB7CIP
Message timed: 03:26 on 2011-Nov-27 GMT
Message sent using WinPack-Telnet V6.80
Read previous mail | Read next mail
| |
