| |
VK2IAQ > TPK 20.05.96 23:11l 51 Lines 2706 Bytes #-11142 (0) @ WW
BID : 552_VK2IAQ
Read: IN3GRK GUEST
Subj: Auto message problem KPC9612/TPK1.82
Path: DB0AAB<DB0PV<DB0WGS<DB0RGB<DB0ABH<DB0SRS<DB0ZDF<DB0GV<DB0SIF<DB0NHM<
DB0EWB<DB0HB<DB0OQ<DB0HRO<OZ4BOX<OZ3BOS<OZ7PAC<OZ3BUL<OZ3BOD<SK6FV<
SK7YX<SK7QJ<SK7BK<SM7DLZ<VK2GJB<VK2DAA<VK2GDM<VK2XY<VK2XBR<VK2TGB<
VK2CZR
Sent: 960519/0335Z @:VK2CZR.#SYD.NSW.AUS.OC #:55968 [St Clair] 5.15c $:552_VK2I
From: VK2IAQ@VK2CZR.#SYD.NSW.AUS.OC
To : TPK@WW
VK2IAQ/TPK 1.82 Msg #:552 Date:19-05-96 Time:3:26Z
G'day all, Ian here in Sydney.
I have a small problem with TPK1.82, running with a KPC9612 TNC. If
I leave the system running with 8BITCONV ON in the TNC and 8 bits enabled
in TPK, the KPC9612 will interpret all received chars and if the correct
combination for changing IO streams arrives, the KPC will go right ahead
and change the stream!! This can mean that the next time an auto forward
period comes around, the TNC tries to connect to my local 1200 Bd 2m BBS
using 9k6 on 70cm, which of course doesn't work, as well as looking a bit
silly...
This problem seems to be solved by leaving the TNC with 8BITCONV
OFF, but I now find that uploads to the BBS won't work, as FBB sends
its "received correctly" byte in the hex $FA-$FF range, which the TNC then
converts to $7A-$7F for some reason, and the upload fails. I don't know why
it does this, as the sign-on graphic from the BBS comes up OK on the screen
on connection, and it uses characters like ุืฺ and the like. I am running
the connections in TRANS mode, and 8BITCONV shouldn't come into play in
TRANS mode, as I understand it.
Is there a way to modify the connect sequence in TPK to set
8BITCONV ON when the connection is made, then set 8BITCONV OFF again when
TPK disconnects. This needs to happen for uploads only, downloads of
message from the BBS are all fine. I know the BR VK2CZR C VK2CZR line can
be modified to, say, BR VK2CZR C VK2CZR^M^78BITCONV ON^M, which is fine for
the connection stage, but after a message upload, how can 8BITCONV OFF be
sent automatically to the TNC? Or is there another way around this?? Are
there any other KPC9612 + TPK1.82 users out there with the same trouble??
Cheers for now!
73s from Ian VK2IAQ@VK2CZR.#SYD.NSW.AUS.OC
ษอออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออป
บ 73s from Ian Chennell VK2IAQ บ
บ QTH: Bowen Mountain New South Wales AUSTRALIA QF56IK บ
บ PACKET: VK2IAQ@VK2CZR.#SYD.NSW.AUS.OC TPK V1.82 บ
บ INTERNET: vk2iaq@k2cc.sos.clarkson.edu บ
บ บ
บ Sent at 13:37 on 19/05/96 บ
บ 24 hours in a day and 24 beers in a case. Hmmmm..... บ
ศอออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออผ
Read previous mail | Read next mail
| |