Hans,
As a new user I just went thru this....
> Problem 1 -- Can't talk to the TNC. Period. Other
> logging programs (CT and HyperLog) work just fine,
> so I know the com port and the TNC are problem free.
You did not mention the type of TNC.
With a PK-232, the TNC must be initialized before WL can use it.
I use Hyper terminal to run the auto-baud routine on the TNC then I launch
the Packet/RTTY program. Use the same baud rates.
> Problem 2 -- I can run CW on COM1, or the radio on COM4
> (but not both). CT handles this just fine, so I know
> the hardware is good. In WriteLog, when I setup either
> port without setting up the other, it will operate
> just fine -- ie, I can set up the radio on COM4 and
> it works fine, or I can set up CW on COM1 and it works
> fine, but if I try to run both, the program freezes
> when I click "OK" in the setup window.
In CT I ran CW and the TNC off the same serial port. In WL this is not
possible. (future fix?)
I used the internet cluster for spotting and ran CW off the port.
Jim
--
WWW: http://www.writelog.com/
Submissions: writelog@contesting.com
Administrative requests: writelog-REQUEST@contesting.com
Problems: owner-writelog@contesting.com
|