| |
VK2ZRG > TPK 06.04.04 10:51l 65 Lines 2856 Bytes #999 (0) @ WW
BID : 460_VK2ZRG
Read: DB0FHN GUEST
Subj: A problem (bug?) in TPK
Path: DB0FHN<DB0FOR<DB0MRW<DB0WUE<DK0WUE<HA3PG<7M3TJZ<CT1EJC<ON4HU<VK3TE<
VK6ISP<VK2BNR<VK2TGB
Sent: 040406/0743Z @:VK2TGB.#SYD.NSW.AUS.OC #:52457 [Valley Heights] FBB7.00g
From: VK2ZRG@VK2TGB.#SYD.NSW.AUS.OC
To : TPK@WW
VK2ZRG/TPK 1.83d Msg #:460 Date:06-04-04 Time:7:41Z
Problem in TPK.
In TPK 1.82 and 1.83d I have found that files in my private message
directory get overwritten occasionally. I have now found the reason.
How it happens
If you get a header from a FBB BBS into your MSG_PRI llist and do
NOT have the message down loaded in the current session of TPK, the last
file in MSG_PRIV directory will be overwritten the next time that you run
TPK and have the file down loaded.
Why it happens.
TPK uses two permanent files and two temporary files to manage the
entries in the private message page of TPK.
MSG_PRIV.LST has details of the message files in MSG_PRIV directory.
MSG_PRIV.NUM stores three numbers. The first is the number of the last
message downloaded or sent. This number is updated every time that you
send or receive a message. The second number is the difference between
the first number and the number of entries in MSG_PRIV.LST. The second
number is updated when TPK is started. It doesn't change while running
TPK unless some message numbers in MSG_PRIV.LST are killed and you
re-initialise TPK. The third number controls where the screen text
colour changes from yellow to white.
One of the temporary files is RXMSG.TPK that exists only while there
are tagged files that have not been down loaded. This file stores the
destination directory name, the BBS message number and the MSG_PRIV.LST
entry number.
When a new message header arrives for your private list, TPK either
creates RXMSG.TPK or adds a new entry to it. Before download, the new
entry in MSG_PRIV.LST carries the BBS message number. TPK puts an entry
number into RXMSG.TPK of one more that the number of files listed in
MSG_PRIV.LST. The message number after down load is the entry number
from RXMSG.TPK plus the second number from MSG_PRIV.NUM.
The second number from MSG_PRIV.NUM, as I said, generally remains
constant in the current session of TPK. So a newly downloaded file
will receive a number (name) of one more that the previous one when it
is downloaded in the current session of TPK.
However if a the pending message is NOT downloaded in the current
session of TPK, TPK will recalculate the second number in MSG_PRIV.NUM
as 1 less because it uses the number of entries in MSG_PRIV.LST and NOT
the number of message files in MSG_PRIV directory. The result is that
the downloaded file (from the header received last time that you ran TPK)
will be given the same number (name) as the last existing message file.
How to avoid this happening.
Simple, just make sure that your private message list does not have
any files tagged for download before you close TPK down. i.e Have ALL
tagged messages downloaded before you quit from TPK.
73s from Ralph VK2ZRG@VK2TGB.#SYD.NSW.AUS.OC
/qsl
Read previous mail | Read next mail
| |
