|
VK6JY > TPK 14.01.00 00:11l 56 Lines 1911 Bytes #-9379 (0) @ WW
BID : 5025_VK6JY
Read: DL6KCF DL2MEL GUEST
Subj: No year 100 in TPK 1.83d
Path: DB0AAB<DB0SL<DB0RGB<DB0MAK<OK0PKL<OK0PPR<OK0PRG<OK0POK<9A0YRB<PP5BLU<
KA6EYH<N5VDA<VE1SMU<VK7AX<VK2KAW<VK6BBS<VK6ZSE<VK6BBR<VK6RAW<VK6DDS<
VK6JY
Sent: 000111/0418Z @:VK6JY.#ALY.#WA.AUS.OC #:42538 [Albany] FBB7 $:5025_VK6JY
From: VK6JY@VK6JY.#ALY.#WA.AUS.OC
To : TPK@WW
VK6JY @VK6JY / TPK 1.83d Msg #:5025 11-01-00 12:11 WAST
Hello to all interested... TPK is really not at fault!
This is a follow up to my comments on TPK 1.82 a few days ago.
I rarely run TPK so my TNC is usually in KISS or HOST mode.
I tested TPK 1.83d against my BBS which runs DOS - FBB 7.00 g23.
For TPK, the TNC is a TAPR TNC2 in TERMINAL mode... TAPR 1.1.8
The results shown in the screen dump below have several Date/Time stamps.
There is never a case where the 2-digit year is presented as "100".
TPK 1.83d arrived in good order and time from ZL2BAU.
If you do get "100" where there should be a "00" you can almost certainly
relax as it is likely to be purely cosmetic.
The problem MAY be occurring in your TNC itself, providing DATE/TIME stamps
and that may be a Harware TNC or a Software TNC.
In all other TPK screens viewed here there was again NO "100" blemish.
Here are 2 blocks of screen data and the 2 status lines in EVIDENCE:-
.............................................................................
VK6JY-9>FBB [11-01-00 11:41:26] <UI C>:
42536 B 201 MAP VK6JY 000111 AR call prefix map "ARMAP"
42537 B 1 NEWS! VK6JY 000111 \USERS\AUTO\... list
VK6DDS>VK6RAW [11-01-00 11:41:27] <RR C P R0>
VK6DDS>VK6RAW [11-01-00 11:41:34] <RR C P R0>
Alarm VK6DW ³ 8bits ³ Log:No ³ QRG:144800 ³ 399 ³ Com2: 4800 ³ 11:41:42
BellþPMSþF1:? 2:MH 3:DOS 4:Print 5:Access 6:Break 7:Cmd 8:Cnx 9:Dcnx ³ 11-01-00
......................................................................
Note that I have modified the lower status line to include a current
date to be shown at most times by a mod in ENGLISH.LNG
73, John.
Read previous mail | Read next mail
| |