| |
VK4BB > TPK 05.01.00 18:38l 32 Lines 810 Bytes #-9388 (0) @ WW
BID : 5961_VK4BB
Read: DH9MAG DL6KCF DL2MEL GUEST
Subj: Re: Y2K msg from ZS6AES
Path: DB0AAB<DB0PV<OE6XHG<OE6XAR<OE5XBL<OE3XSR<OK0PBX<OK0PHL<OK0PBB<OK0PBR<
OK0PAB<HA5OB<WU3V<VE7KIT<VK3BBS<VK4ATD<VK4DGQ<VK4WIE
Sent: 000105/1248Z @:VK4WIE.#BNE.QLD.AUS.OC #:59802 [Brisbane] FBB7.00g
From: VK4BB@VK4WIE.#BNE.QLD.AUS.OC
To : TPK@WW
VK4BB/TPK 1.83c Msg #:5961 Date:05-01-00 Time:12:37Z
VK4BB/TPK 1.83c Msg #:5959 Date:05-01-00 Time:12:35Z
I also had this problem... All I did was at the dos prompt put in the
WHOLE year... ie 2000 not 00
eg DATE 05-01-2000 not 05-01-00
Now as you see above it reads 00 not the 100 I did get.
Fixed me! hi
Grahanm vk4bb
>R:000101/1719Z @:ZS6AES.WRJ.GAU.ZAF.AF #:8578 [ROODEPOORT, GAUTENG] FBB7.00g
>
>From: ZS6AES@ZS6AES.WRJ.GAU.ZAF.AF
>To : TPK@WW
>
>Hi There
>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..
>
>73 DE ZS6AES
Read previous mail | Read next mail
| |
