Fw: [WriteLog] QTC problem with DXP-38
WA9ALS - John
Thu, 9 Nov 2000 23:24:48 -0500
Guys, guys - I think we're OK on this! Do you have your SHIFT-FKEY
buffers set up properly?? Mine were not. I then imported my buffers
from last year, and this includes SHIFT-F8 through SHIFT-F11 setup with
the appropriate messages related to QTCs. After I did that, it works VY
FB! I'm not sure I completely understand why having those messages
fixes it, but it does. Maybe WL's "looking ahead" for the appropriate
SHIFT-Fkey buffer about the time it hits the serial number, and hangs
because it can't find those buffers...??
I don't even remember where I learned how to set those up - probably
from Dick's web pages last year! OH yeah, I'm sure it's in the HELP doc
somewhere too! HI GL - 73
WA9ALS - John
----- Original Message -----
From: "Don Hill" <email@example.com>
To: "WriteLog Reflector" <Writelog@contesting.com>
Sent: Thursday, November 09, 2000 10:20 PM
Subject: [WriteLog] QTC problem with DXP-38
> I've been practicing sending and receiving QTC's on both of my
> radios/computers for tomorrow's upcoming WAE RTTY contest.
> I am finding that WriteLog does not send QTC's with a DXP-38 as
> the TNC. It works fine with a PK232.
> Can someone with a DXP-38 (or perhaps any HAL TNC) please confirm
> This is easily done. Log 10 bogus QSO's. Enter the callsign of the
> 11th QSO in the entry window. Hit ALT-S, hit the Xmit QTC's button.
> What I am finding is that WriteLog sends the first line with the QTC
> number OK and starts the first QTC. It sends the date, callsign and
> begins to send the serial number on the first QTC, but stops and
> only sends diddles from then on. Tried it several times.
> Not what I wanted to find less than 24 hours before the contest, but
> I can easily switch the PK232 to the rate station and relegate the
> to the multiplier station. As a fact, I'm doing this immediately.
> Don Hill, AA5AU
> WWW: http://www.writelog.com/
> Submissions: firstname.lastname@example.org
> Administrative requests: writelog-REQUEST@contesting.com
> Problems: email@example.com
Administrative requests: writelog-REQUEST@contesting.com