Hi John,
I had the same problem as you described several times when I was
reconfiguering WriteLog and my computers. The reason for this behaviour
was always the same: There were other requests for the rig com port,
e.g CW or RTTY were mapped to the same port. Or other applications
outside of WriteLog wanted to use this port.
73 + 55
Wolf, DL6JZ
John Griswold schrieb:
> Again, thanks for all the responses - you are all very
> supportive.
>
> It has been suggested that I look at interrupt latency,
> inter-poll timing, the operating system, and loose
> connectors as issues, and also to perhaps view the
> problem at the radio not talking to WriteLog v. WriteLog
> not talking to the radio.
>
> When I had set WriteLog up to use COM1, I didn't have any
> trouble, so I'm opting to swap the serial ports so that
> WL talks to the radio on COM1. I'll go with the
> assumption that there are simply too many devices sharing
> the one PCI interrupt.
>
> 73,
> John KB1HDO
>
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web: http://www.writelog.com/
>
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|