> On my desktop, WL, DX4WIN, and WKTest all work with my
> WinKeyer USB on COM8, but none of them work on COM10. What
> is the difference (other than 10 is 2 greater than 8)? My
> COM10 is on a USB hub, but my COM8 is a USB port that is part
> of my PC itself. I'm 99% certain I had WL working on COM10
> last year for November SS, but can't make it work now.
DX4Win only supports CW on ports other than COM1 - 8 simply
because the programmers have not allowed that choice. I can't
speak for WKtest. However, Writelog works with any port.
For WriteLog see the help file under [Ports] (WriteLog.ini)
| There are 4 "slots" available for WriteLog rig interfacing.
| By default, CommSlot1 is COM1:, but you can change that by
| changing the number on the right of the equal sign. These
| settings are not used for RTTY or for packet
|
| CommSlot1=1
| CommSlot2=2
|
| In this example, the third and fourth slots are on COM7 and
| COM8. COM15 is as high as is supported.
|
| CommSlot3=7
| CommSlot4=8
|
Add the proper CommSlot#=* line to the [Ports] section of your
WriteLog.ini file and you will be able to use WinKeyer USB on
any port you want.
73,
... Joe, W4TV
> -----Original Message-----
> From: writelog-bounces@contesting.com
> [mailto:writelog-bounces@contesting.com] On Behalf Of Kelly Johnson
> Sent: Tuesday, August 05, 2008 1:22 AM
> To: writelog@contesting.com
> Subject: [WriteLog] WL won't work with WinKeyer USB on some PCs
>
>
> OK, here's another plea for help with this issue.
>
> On my desktop, WL, DX4WIN, and WKTest all work with my
> WinKeyer USB on COM8, but none of them work on COM10. What
> is the difference (other than 10 is 2 greater than 8)? My
> COM10 is on a USB hub, but my COM8 is a USB port that is part
> of my PC itself. I'm 99% certain I had WL working on COM10
> last year for November SS, but can't make it work now.
>
> On my laptop, WKTest works with my WinKeyer USB, but WL does
> not. The COM port used on the laptop is COM2. One thing
> special about this case is that when I first installed the
> virtual serial port driver, Windows assigned a really high
> COM port number (like 25) for it because I had previously
> installed a whole bunch of BT drivers on that machine which
> were assigned lower numbers. I manually changed the COM port
> number for that device to COM2. Could that have anything to
> do with why WL won't work? Like I said, WKTest works fine.
>
> Someone suggested a baud/parity problem, but I tried manually
> forcing the virtual COM port to the desired 1200,8N1 and it
> still doesn't work.
>
> Suggestions?
> _______________________________________________
> 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/
|