| |
G0TWN > TPK 01.08.97 13:07l 128 Lines 5197 Bytes #-10481 (0) @ WW
BID : 10976_G0TWN
Read: GUEST
Subj: Re: More re "Don't let this happen"
Path: OE3XSR<DB0WGS<DB0RGB<DB0ABH<DB0SRS<DB0ZDF<DB0LJ<DB0ACH<ON4RAT<ON5VL<
ON7AN<ON7RC<ON1BWP<ON6AR<ON1CED<ON4KTK<GB7SXE<GB7YUH<GB7WIG<GB7BAS<
GB7HSN<GB7DAA<LWBBBS<GB7LWB<GB7BEN
Sent: 970731/0950Z @:GB7BEN.#43.GBR.EU #:38828 [Bletchley] FBB7.00c $:10976_G0T
From: G0TWN@GB7BEN.#43.GBR.EU
To : TPK@WW
G0TWN/TPK 1.83b Msg #:10976 Date:31-07-97 Time:9:35Z
Hi TPK'ers,
A few of you seem to have simular problems and I hope the following reply to
Rob clears things up a little. Also I have added a little suggestion at the
end of this bulletin of how to backup and protect yourself from lists
corruption.
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)
---
Hello Rob,
>That is you don't want to keep it forever, so you "appear" to delete it by
>hitting Ctrl+U.
CTRL+U is for untagging a message from the list however, if the message has
already been collected it DOES NOT delete it. Pressing 'K' does kill the
message from the list and also deletes the file.
Using 'K' will eleviate your use of Xtree or whatever.
Whilst 'K' will delete the file, the message heading will stay on your list
until you do a tidy up. You can have the following commands in your
CONFIG.TPK:
BR MSG_PRIV E K
BR GB7BEN E K
^^^^^^
Your BBS here
Alternatively, I have the following macro which does full housekeeping for
me:
TIDY ^6CONOK OFF^M^7M QRX^MBR GB7BEN E K^MATT 2^MBR GB7BEN E DAYS 3^MATT 2^MBR MSG_PRIV E K^M^7M QRV^M^6CONOK ON^M
I hope this helps. TPK is a well thought out and tame beast. The manual may
seem to let it down but after several reads you can get quite conversant.
You do not need any external file utilities to keep TPK in working order.
---
OK that's your specific problem sorted. The other guy's problem, can't
remember his call, is related to the above. I think you will find that he is
correctly using 'k' to kill messages but his TPK system has not been set to
tidy up the listings at a later date and so his message list is filling up
with a lot of killed message headings:
K431943 P 1820 SYSOP @GBR G4VEL 970731 Another daft fbb query !!
431946 P 3202 G3LDI @GB7LDI GB7PZT 970731 LSTSRV report: 31/7/97 00:36
431947 B 1427 ALL @EU G7HMN 970731 Grand Canaria holiday
431948 B 2687 VHF @WW IW9EKK 970731 CONTEST !
K431949 P 1766 G8NRB G3VQP 970731 stuff
431950 B 18567 VHF @EU 9A4GL 970731 MSDSP034.P03/P05 7+
K431952 P 763 G8TTK SYSTEM 970731 *** Report for 31/07/97 ***
K431953 P 183 G8TTK GB7BEN 970731 WP Clean up summary
K431954 P 395 G8TTK GB7BEN 970731 WP Deletions
In my case again BR GB7BEN E K will tidy this up to this:
431946 P 3202 G3LDI @GB7LDI GB7PZT 970731 LSTSRV report: 31/7/97 00:36
431947 B 1427 ALL @EU G7HMN 970731 Grand Canaria holiday
431948 B 2687 VHF @WW IW9EKK 970731 CONTEST !
431950 B 18567 VHF @EU 9A4GL 970731 MSDSP034.P03/P05 7+
I hope that clears it up. I'll send a copy of this message as a bulletin too
Rob to help the other guy.
---
In all the years I have ran TPK (since v1.80) I have been fortunate to have
only experienced message list corruption a few times. Many scenarios could
cause this corruption but is typically due to computer lock up. I backup
certain essential files during TPK startup allowing me to recover from such
an event. The following may look long-winded but it works!
First I created a new directory to store the backups-
TPK\LISTS\RECOVER. I call TPK from a batch file that has the following
included:
COPY /Y \TPK\LISTS\RECOVER\MSG_PRIV.LST \TPK\LISTS\RECOVER\PRIV_LST.OLD
COPY /Y \TPK\LISTS\RECOVER\MSG_PRIV.NUM \TPK\LISTS\RECOVER\PRIV_NUM.OLD
COPY /Y \TPK\LISTS\RECOVER\GB7BEN.LST \TPK\LISTS\RECOVER\BEN_LST.OLD
COPY /Y \TPK\LISTS\RECOVER\GB7BEN.NUM \TPK\LISTS\RECOVER\BEN_NUM.OLD
COPY /Y \TPK\LISTS\MSG_PRIV.LST \TPK\LISTS\RECOVER\*.*
COPY /Y \TPK\LISTS\MSG_PRIV.NUM \TPK\LISTS\RECOVER\*.*
COPY /Y \TPK\LISTS\GB7BEN.LST \TPK\LISTS\RECOVER\*.*
COPY /Y \TPK\LISTS\GB7BEN.NUM \TPK\LISTS\RECOVER\*.*
As you can see I keep two backups of these files for absolute recovery! I'll
now explain why these files are so essential. The file extentions are as
follows:
.LST Files ending in .LST are textual files containin your message
listings in exactly the same format as the BBS's message listing.
You could edit these files with a text file editor but you must
remember each line MUST be 80 charcters long. View them with a
binary file editor and you will see they are padded with TAB's and
white spaces.
.NUM DO NOT try to edit these! These coded files keep track of the
numbering used in your listings. For your MSG_PRIV they note the
next available message number. For your <bbs> lisiting it keeps
track of last message number collected from BBS unproto broadcasts.
Corrupt this and you won't be able to syncronise with your BBS
correctly!
Now if anything goes wrong you can recover with whichever of the two backups
are uncorrupted.
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 Christopher Robin shut the washingmachine door!.
Read previous mail | Read next mail
| |
