| |
VK4ZR > TPK 08.01.00 13:36l 32 Lines 1148 Bytes #-9385 (0) @ WW
BID : 1186_VK4ZR
Read: DL2MEL DL8SER GUEST
Subj: YK2 - TPK1.83
Path: DB0AAB<DB0SL<DB0RGB<DB0MAK<DB0SON<DB0SIF<DB0AIS<DB0NDK<DB0ACH<ON0RAT<
ON0RTB<ON0OB<ON0CK<ON1CED<ON6AR<WB0TAX<VK3BBS<VK4ATD<VK4DGQ<VK4KUG
Sent: 000108/0203Z @:VK4KUG.#LGN.QLD.AUS.OC #:55670 [LOGAN] 7.00e $:1186_VK4ZR
From: VK4ZR@VK4KUG.#LGN.QLD.AUS.OC
To : TPK@WW
VK4ZR/TPK 1.83b Msg #:1186 Date:07-01-00 Time:5:59Z
ZS6AES wrote:
>Hope everyone has had a bug free Y2K rollover. I have a user here running TPK
>1.82 and date is shown as 01-01-100 and cannot sync with local BBS - anyone
>know what the fix is and where the patch can be obtained please. Thanks and
>have a happy new year..
Maybe it is TPK 1.82?
I have no problem with TPK 1.83b on an old NEC APCIV 286 - see msg date.
My BIOS was not compliant so I installed YEAR2000.EXE from RighTime into
Autoexec.bat and that made it work ok on New Year's Day - to the point
where, on January 2 , that programme advised that it had done its job so
could be taken out.
I have 'rem'med it out in case it is needed for 29/2/00 - just in case !!
I thank RighTime for that Freeware programme.
HNY 2000 and 73 to all,
de Peter, VK6HU
I am running TPK1.83b and the date appears as above (01-01-100) but all
works OK through my local BBS. I thought it may create a problem but every
thing appears to be functioning OK at the moment. I'll keep my fingers
crossed.
73 de Kev, VK4ZR
Read previous mail | Read next mail
| |
