| |
PY1BKJ > KAM 02.03.96 08:06l 37 Lines 1863 Bytes #-11082 (0) @ WW
BID : 661_PY1BKJ
Read: DJ5ZH DF7NZ GUEST
Subj: EASY KAM RESET
Path: DB0AAB<DB0SL<DB0RGB<OK0PPL<OK0PKL<DB0MAK<DB0HOT<DB0LPZ<DB0MER<DB0BAL<
DB0OCA<DB0FC<DK0MAV<DB0HB<DB0EWB<DB0RDB<DB0HES<OZ7BOX<OZ2BOF<OZ9PAC<
OZ4BUL<OZ3BUL<OZ2BBS<OZ2BOX<OZ6BBS<SK7CY<SK6FV<SK7QJ<SK7BK<SM7DLZ<
N0RSE<VK7HIL<VK7AX<VK3BBS<F6CNB<PU3DTA<PY3PS<PY3SS<PY4SM<PY2ZE<PY2DNX<
PY0FF<PT7FX<PY1AA
Sent: 960207/1848Z @:PY1AA.#RIO.RJ.BRA.SA #:54597 $:661_PY1BKJ
From: PY1BKJ@PY1AA.#RIO.RJ.BRA.SA
To : KAM@WW
PY1BKJ/TPK 1.82 Msg #:661 Date:07-02-96 Time:13:58Z
PY1BKJ/TPK 1.82 Msg #:650 Date:07-02-96 Time:8:50Z
Hello:
One day I "x" myself out of TPK with everything shipshape and
turn the power off, as is normally done day in and day out.
Next morning the computer is booted back, TPK runs and the KAM will
not initiliaze. Amidst garbled characters one may find the dreaded "‡" which
would be asking for another dreaded character (*) to be pressed for
recognition.
Did that ever happen to you? Have you ever spent many (literally
many) hours trying to reinitiliaze your KAM? Did you ever have to finally
open it up and do a hard reset? Have you ever experienced some problem,
even after a hard reset?
May be it only happens to me. It is possible (and probable) that
my TNC is moody or syndicated - or both. It does not happen very frequently
but when it does it is enough for me to recall the experience for a long
time. And it usually happens when you dont have the time to hang around
trying to fix it, as Murphy had anticipated it would happen long ago.
Do you have any idea why a TNC like KAM, running with TPK software,
would act up like that - sporadically? Any ideas which I might pursue in
preventing this occurrence?
In the meatime, for any of you who might be facing my predicament,
here is the result of lengthy experimentation and suffering - an easy KAM
reset which I have to resort to when I need to reinitialize it:
I have the software THUNDER as a backup. Within TPK I switch over
to DOS (using F3) and run THUNDER. It will automatically and promptly
initialize the KAM unit. I then exit and return to TPK with the problem
neatly solved.
Best of luck and 73's from Clarindo - PY1BKJ
Read previous mail | Read next mail
| |
