| |
VK6JY > TPK 11.01.00 04:04l 69 Lines 2213 Bytes #-9382 (0) @ WW
BID : 42240-VK6JY
Read: DL6KCF DL2MEL GUEST
Subj: No year 100 in my TPK 1.82
Path: DB0AAB<DB0SL<DB0RGB<DB0MAK<OK0PKL<OK0PPR<OK0PRG<OK0NCG<OK0POK<9A0YRB<
HI8GN<WU3V<N5VDA<VE1SMU<VK7AX<VK2KAW<VK6BBS<VK6ZSE<VK6BBR<VK6RAW<
VK6DDS<VK6JY
Sent: 000109/0429Z @:VK6JY.#ALY.#WA.AUS.OC #:42240 [Albany] FBB7 $:42240-VK6JY
From: VK6JY@VK6JY.#ALY.#WA.AUS.OC
To : TPK@WW
Hello to all interested... TPK is really not at fault!
I rarely run TPK so my TNC is usually in KISS or HOST mode.
I tested TPK 1.82 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".
I do not have TPK 1.83 here to test.
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 BR SYNC and the 2 status lines in EVIDENCE:-
.............................................................................
VK6JY-9>FBB [09-01-00 11:10:46] <UI C>:
42234 B 5449 TODOS @WW CT1EMT 000109 amazonas
42235 B 1961 YAESU @WW DB8ZH 000109 FT290RII und Mic.Gain?!?!
42236 B 7240 SATELL@WW IS0AGY 000109 W.A.I.P. SATELLITE ^.htm
VK6JY-9>FBB [09-01-00 11:10:49] <UI C>:
42237 B 3131 TODOS @WW CT1EMT 000109 amazonas parte 3
42238 B 2605 WINPAC@WW ZR6YY 000109 problem with upload
Alarm VK6DW ³ 8bits ³ Log:No ³ FRQ:144800 ³ 399 ³ Com2: 4800 ³ 11:11:40
BR VK6JY-9 SYNC
BellþPMSþF1:? 2:MH 3:DOS 4:Print 5:Access 6:Break 7:Cmd 8:Cnx 9:Dcnx ³ 09-01-00
.............................................................................
73 from John, VK6JY @ VK6JY Albany, WA. TST HOST 1.43c
ps - the same TNC in HOST mode and the same BBS does give the "100" error
under TST 1.43c BUT ONLY in Date/Time stamping of MONITORED packets!
All internal lists are rendered correctly, as in my TPK.
The KISS software is probably doing that.
These conclusions probably apply to TST and WPK in a general way too,
that users have many variable contributing programs...
Regards from John, VK6JY @ VK6JY.#ALY.#WA.AUS.OC
Albany WA FBB 7.00g 09-JAN-2000 12:16 WAST
Read previous mail | Read next mail
| |
