| |
VK3QS > TPK 17.04.98 08:33l 33 Lines 1142 Bytes #-10206 (0) @ WW
BID : 480_VK3QS
Read: GUEST
Subj: TPK and flying C rectification!
Path: DB0AAB<DB0FSG<DB0SL<DB0RGB<DB0MAK<DB0HOT<OK0PKL<OK0PPR<OK0PRG<OK0PAB<
PU3AKM<PP5BLU<WU3V<WB0TAX<KE4HSB<VK4ATV<VK3BBS<VK3ECC
Sent: 980411/0143Z @:VK3ECC.#MEL.VIC.AUS.OC #:60933 [Bayswater] 7.00e $:480_VK3
From: VK3QS@VK3ECC.#MEL.VIC.AUS.OC
To : TPK@WW
VK3QS/TPK 1.83c Msg #:480 Date:08-04-98 Time:11:44Z
Hello TPK users!
If you have moved TPK with a backup program from computer to computer, and
encountered, when a channel is allocated on screen, and the program going
into CONFERENCE MODE, I have found the problem.
The problem occurred in my Tiny2.set, as I use a PacCOMM tiny2 unit.
The item that causes the problem is NEWMODE and NOMODE settings, which can
I understand be altered from the keyboard, which I tried, and it worked
till I switched on the computer again and got a message, when it went back
to CONFERENCE again.
The Solution:
I edited TINY2.SET and found the line <NEWMODE OFF) which is the default
setting according to the manual of the Tiny2, BUT there was missing NOMODE O
FF which is also the default setting, in other words it apparently had
disapppeared. So I added the line in the Tiny2.SET, <NOMODE ON> and the
program has run magnificantly since, and I have done that in TPK 1.83c, so
I hope that may help someone scratching their head over that one!
Cheers!...Graeme
Read previous mail | Read next mail
| |
