| |
G0TWN > TPK 06.08.97 00:44l 67 Lines 2865 Bytes #-10477 (0) @ WW
BID : 11108_G0TWN
Read: GUEST
Subj: (OK4STA)More re "Don't let this happen"
Path: OE3XSR<DB0WGS<DB0RGB<DB0ABH<DB0SRS<DB0ZDF<DB0AIS<DB0NDK<DB0RWI<PI8ZAA<
PI8GCB<PI8HGL<PI8VNW<GB7PMB<GB7ODM<GB7DHI<GB7LEN<GB7OAR<GB7SAM<GB7MAX<
GB7COV<GB7COV<GB7LWB<GB7BEN
Sent: 970805/1248Z @:GB7BEN.#43.GBR.EU #:40851 [Bletchley] FBB7.00c $:11108_G0T
From: G0TWN@GB7BEN.#43.GBR.EU
To : TPK@WW
G0TWN/TPK 1.83b Msg #:11108 Date:05-08-97 Time:13:40Z
Hello TPK'ers,
Just some comments on B›rge,
In all the years I have used TPK I have _N_O_T_ experienced a problem
having included 'BR MSG_PRIV E K' in my CONFIG.TPK however I bow to B›rge's
experience and now disclaim any onus.
>..., this will give some
>disaster the day you are in a hurry and stop your TPK on your way out the
>door...
You will need to have read B›rge's complete message so as not to get the
following out of context.
Well being one who likes to test all eventualities I tried it. I shouted at
TPK to 'hurry up!' because I wanted to go out. Made no diffence as it still
took just as long to shut down (exit).
I came back later and started
up TPK again and found no corruption. I am co-sysop of the BBS here and
logged on and found I had not missed or lost forwarding of any personal
mail, curious? But then I know that TPK does _N_O_T_ call CONFIG.TPK on
close down. I had mail tagged for fowarding and when TPK was restarted it
was still tagged for fowarding (collection). I would be interested to hear
more B›rge and look into this further
because I would never wish to give information that would mislead
or do any harm.
>>.LST
If you re-read my message B›rge I said the .LST file is textual, it is. It
contains text! Then I mentioned how you should edit a .LST file and assuming
most have access to an editor like MSEdit I pointed out that you must use
such an editor in binary edit mode with line width of 80 characters. For
those that have a TRUE binary editor and thus more knowledgable, my text
would have made it clear that a .LST file is a binary file of which each
line (terminated by carriage return + linefeed) is exactly 80 characters
long and contains text. B›rge was in fact correct when .LST files do not
normally contain TABS but they do when the message sender has embedded one
into the header! My mistake, .LST files only normally contain textual
characters, whitespaces, linefeeds and carriage returns.
The wise amongst us would have viewed the structure of all such critical
files and made notes prior to disaster. Those however who would not wish to
dabble would do something simular as I have done and backed up such files. I
have explained one method how to do this in a previous bulletin.
There many methods and approaches to any task, I have suggested one and
B›rge has suggested another plausible method. It is good to see that there
are still TPK enthusiasts out there and keep the comments, hints and tips
coming!
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 the social workers took Christopher Robin away.
Read previous mail | Read next mail
| |
