This is a multi-part message in MIME format.
------=_NextPart_000_0011_01C168D9.ED8E4340
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
The situation that Don, AA5AU and John, WA9ALS, described that when =
sending QTC, the DXP-38 goes into a diddle state.
I had a similar problem with WL and the DXP-38 during NA Sprint which =
was the first contest that I was planning on using WL and was going to =
use the 38 as a TNC. =20
When testing out the program, I had an intermittent problem with the =
exchange hanging up in the middle of and the TNC would just stop in =
Transmit. It was in diddle. I later turned the diddle off , but it still =
had an intermittent problem of hanging up.
I descovered that if I entered a callsign manually and the cursor was =
still in the call window, the exchange would hangup every time, but if I =
clicked on a callsign in one of the rttyrite windows, the exchange would =
go to completion. This describes it as well as I can remember. The =
DXP-38 is off line now and I cannot check it out further.
Later, I descovered that If when manually entering a callsign, if I =
woudl tab to the next field, the exchange would go to completion without =
problems.
On the matter of the diddled QTC, if you have manually entered the =
callsign and the curson is still in the callsign field, try to move it =
to the next field and see what happens. Also try clicking on a callsign =
and check the results here also.
I have used the DXP-38 and WF1B RTTY for the past two/three years in WAE =
and it has performed flawlessly when sending QTC.=20
I hope this is of some help.
Dave W7DPW (DoubleProofWhiskey)
------=_NextPart_000_0011_01C168D9.ED8E4340
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2919.6307" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>The situation that Don, AA5AU and John, =
WA9ALS,=20
described that when sending QTC, the DXP-38 goes into a diddle=20
state.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>I had a similar problem with WL and the =
DXP-38=20
during NA Sprint which was the first contest that I was planning on =
using WL and=20
was going to use the 38 as a TNC. </FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>When testing out the program, I had an =
intermittent=20
problem with the exchange hanging up in the middle of and the TNC would =
just=20
stop in Transmit. It was in diddle. I later turned the diddle off , but =
it still=20
had an intermittent problem of hanging up.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>I descovered that if I entered a =
callsign manually=20
and the cursor was still in the call window, the exchange would =
hangup=20
every time, but if I clicked on a callsign in one of the rttyrite =
windows, the=20
exchange would go to completion. This describes it as well as I can =
remember.=20
The DXP-38 is off line now and I cannot check it out =
further.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Later, I descovered that If when =
manually entering=20
a callsign, if I woudl tab to the next field, the exchange would go to=20
completion without problems.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>On the matter of the diddled QTC, if =
you have=20
manually entered the callsign and the curson is still in the callsign =
field, try=20
to move it to the next field and see what happens. Also try clicking on =
a=20
callsign and check the results here also.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>I have used the DXP-38 and WF1B RTTY =
for the past=20
two/three years in WAE and it has performed flawlessly when sending QTC. =
</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>I hope this is of some =
help.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Dave W7DPW =20
(DoubleProofWhiskey)</FONT></DIV></BODY></HTML>
------=_NextPart_000_0011_01C168D9.ED8E4340--
|