DB0FHN

G0TEZ  > TPK      09.01.99 21:57l 34 Lines 883 Bytes #-9753 (0) @ EU
BID : 953_G0TEZ
Read: DL2MEL GUEST
Subj: Re: Y2000 Doesn't work With TPK.
Path: DB0AAB<DB0AHO<DB0KFB<DB0CZ<DB0GE<DB0HOM<DB0ZDF<DB0AIS<DB0SIF<DB0HSK<
      PI8DRS<PI8DAZ<PI8GCB<PI8WFL<PI8MBQ<PI8VNW<GB7PMB<GB7WXM<GB7DEE<GB7OAR<
      GB7BOB<GB7WRC<GB7HVU
Sent: 990109/1215Z @:GB7HVU.#16.GBR.EU #:27154 [East Lancs] $:953_G0TEZ
From: G0TEZ@GB7HVU.#16.GBR.EU
To  : TPK@EU

G0TEZ/TPK 1.83c Num: #:953  Date:09-01-1999  Time:12:01 GMT COLNE Lancs

Just a msg to say Roy's method also works with TPK 1.83c.
Quoting:

>From: G0OSW@GB7SOU.#48.GBR.EU
>To  : TPK@GBR
>
>G0OSW/TPK 1.82 Msg #:3962  Date:08-01-1999  Time:23:28Z
>
>>       You need to edit the English.lng file on the 1st Jan 2000 to :-
>>
>>       "$0TPK  Msg N§ $2  Date:%date dd-mm-20yyz%  .
>>
>>       Then 2000 will be displayed instead of 00
>
>
>I tried this, it didn't work - it just says Err.date instead of the date.
>
>*However*, the following line DOES work:
>
>       "$0TPK  Msg N§ $2  Date:%date dd-mm-yyyyz%  .
>
>and what's more it works NOW by putting in the correct 4-digit year, as you
>can see at the top of this message!
>
>Maybe the other way works with 1.83?  No matter, the 2nd method should work
>anyway.
All the best. Ian.



Read previous mail | Read next mail