| |
G4IDE > TPK 15.08.97 03:05l 26 Lines 799 Bytes #-10467 (0) @ WW
BID : 9A0787G4IDE
Read: GUEST
Subj: Re: TPK/Winpack stuck unproto loop
Path: OE3XSR<DB0WGS<DB0RGB<DB0ABH<DB0SRS<DB0ZDF<DB0HOM<LX0PAC<ON7RC<ON1BWP<
ON6AR<ON1CED<ON4KTK<GB7SXE<GB7YUH<GB7COS<GB7HSN<GB7TUT<GB7DAA<LWBBBS<
GB7LWB<GB7BEN<GB7AVM<GB7WAR<GB7COV<GB7COV<GB7AYI<GB7BAD<GB7NOT<GB7MAM<
GB7ADH<GB7MRU<GB7WRG<GB7MAX<GB7SAM<GB7OAR
Sent: 970814/1526Z @:GB7OAR.#16.GBR.EU #:45571 [Wirral] $:9A0787G4IDE
From: G4IDE@GB7OAR.#16.GBR.EU
To : TPK@WW
G0TWN wrote:-
> 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!
etc...
I don't think this would normally happen to a WinPack user, because,
unless a user has altered the default INI file settings, WinPack will give
up after sync'ing 20 times on the same message number. At that point it
disables support for using the unproto headers until the system is
restarted.
73 - Roger, G4IDE @ GB7OAR
roger@peaksys.demon.co.uk
Sent using WinPack __o
09:19 UTC on 14 Aug 97 _`\-\,
___________________________(_)/ (_)______
Read previous mail | Read next mail
| |
