--==_500309==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed And that is the problem. I cannot select CW on the same port as I control the rig. CW is on an independent port. If I wa
--==_1354828==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed In order to test that using a port for CW will turn off the DTR, I selected port 4 and I get the message that shared ra
--==_44638376==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed That will not wrok. Of course I want COMM PTT to wrok. I tried it anyway. To all I have rewired my cables and rest my
--==_44930997==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed It is responding as the program is designed and I agree it is not brain surgery. As my other post shows I have capitul
--==_10786029==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Unless you are trying ot sound out letters, ramdrive will be of no help. Sounding out letters is not a good thing in a
--==_10884921==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed And the contest module should handle this. It is very easy ot do and would be easy to let the program handle it. You a
--==_63984164==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed I am using WriteLog for RTTY and also use the MMTTY Plugin, although RTTYWrite is not too bad. I still would get the M
--==_132930964==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed I use WIN2000. I commend you for trying to eliminate ME! I have Rig control on COMM3 and I have CW and PTT on COMM 2.
--==_135490985==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed That thread talks about how to operate, but it does not mention a contest module. Again, is there one or isn't there?
--==_7730195==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed I think there is little likelihood of this requirement being scored? Perhaps if another contest has this it could be mo
--==_9024186==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Read the document and copious warnings given by the author. LPT is NOT supported in NT, or WIN2000 and by extension XP.
--==_49415655==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Hi; I found it but there are better ways to do this. DXTELNET itself has files of how to do it that seem to work with
--==_65353513==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed DXTELNET/HELP/Links to other applications. It is all in the help file. It tells a way to use any program but do not us
--==_3671319==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed I have the DXTELNET to WriteLog link set up according to the instructions in the dxt2wl.txt that comes with DXTELNET. I
--==_5543961==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed To: <writelog@contesting.com> I just tried DXTELNET shortcut too and it makes no difference. This uses CQ IRC connectio
--==_48404672==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed I have the DXTELNET to WriteLog link set up according to the instructions in the dxt2wl.txt that comes with DXTELNET.
--==_56172351==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed WELL WELL WELL, MY APOLOGIES to all. It was working all of the time. I just did not realize it. The spot form WriteLog
--==_61043395==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Right you are. See my earlier post with a mia culpa. Gil Baron http://members.home.com/gbaron W0MN 44.08208 N 92.51263
--==_61305722==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed On the DXTELNET home page link to the setting up. Maybe my font was making it look like that? You do NOT use UDPSEND U
--==_61412416==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Of course I meant INTO or NOT ? Gil Baron http://members.home.com/gbaron W0MN 44.08208 N 92.51263 W 1055' "Baila como