| |
G0TWN > TPK 14.08.97 10:38l 27 Lines 919 Bytes #-10468 (0) @ WW
BID : 11193_G0TWN
Read: GUEST
Subj: TPK/Winpack stuck unproto loop
Path: OE3XSR<DB0WGS<DB0PV<DB0AAB<DB0AHO<DB0KFB<DB0ZKA<DB0LX<DB0RBS<DB0SEL<
DB0ZDF<DB0LJ<DB0ACH<DB0ACC<PI8DRS<PI8ZWL<PI8APD<PI8GCB<PI8WFL<PI8VNW<
GB7PMB<GB7MAX<GB7COV<GB7COV<GB7LWB<GB7BEN
Sent: 970813/1701Z @:GB7BEN.#43.GBR.EU #:43573 [Bletchley] FBB7.00c $:11193_G0T
From: G0TWN@GB7BEN.#43.GBR.EU
To : TPK@WW
G0TWN/TPK 1.83b Msg #:11193 Date:13-08-97 Time:17:21Z
VK3AEO outlined a problem with low disk space and thus the chances of a TPK
station getting stuck in a unproto sync loop. This could also happen to a
Winpack user too and is embarrising because until you intervene, no one on
frequency will get an update!
I aggree with all VK3AEO's suggestions and just wanted to add that if you
see a station stuck in such a loop but cannot contact the operator then I
suggest instead you contact the BBS Sysop or Co-sysop who can then
temporarily disable the sync facility for that user until they have resolved
their problem.
Best regards,
de David (FISTS 1334)
AX25: G0TWN @ GB7BEN.#43.GBR.EU
Co-sysop GB7BEN - South of England TPK Support BBS
Secretary MKPAC (Milton Keynes PACket user group)
ūG0TWN TPKCookie:
"Bother," said Pooh, as he realised the limitations of Warp.
Read previous mail | Read next mail
| |
