| |
VK2ZFE > TPK 13.01.00 07:30l 31 Lines 844 Bytes #-9380 (0) @ WW
BID : 2190_VK2ZFE
Read: DL6KCF DL2MEL GUEST
Subj: Re:TPK 1.82
Path: DB0AAB<DB0FSG<DB0SL<DB0RGB<DB0MAK<OK0PKL<OK0PPR<OK0PPL<OK0POK<9A0YRB<
HI8GN<WU3V<I1YLM<KE4HSB<VK7AX<VK7AX<VK2KAW<VK6BBS<VK6ZRE<VK6BBR<VK2IO<
VK2TGB<VK2MJV
Sent: 000108/0552Z 16425@VK2MJV.#CW.NSW.AUS.OC [PARKES] FBB7.00f $:2190_VK2ZFE
From: VK2ZFE@VK2MJV.#CW.NSW.AUS.OC
To : TPK@WW
VK2ZFE/TPK 1.82 Msg #:2190 Date:09-01-00 Time:3:44Z
From: VK2ZFE@VK2MJV.#CW.NSW.AUS.OC
To : ZS6AES@ZS6AES.WRJ.GAU.ZAF.AF
>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.
>73 DE ZS6AES
Hi ZS6AES
As you will see by the header on this msg, I am useing 1.82.
The problem is with the user's BIOS.
There are a number of patches floating around on the packet
net, also on the web. Thay are in the form of a TSR loaded
on computer start up from the CONFIG.SYS or AUTOEXEC.BAT.
I've found something that may help on the local PBBS.
I'll send it on.
Cheers from Frank.
Read previous mail | Read next mail
| |
