I'd like to know the answer too - same problem with the DXP38 TNC. Usually my noise level is high enough that the squelch is opened anyway, but would like to be able to turn off the rig and have the
I don't know what you're using for a TNC, but since you're running FSK, it could be that your TNC is not set to the correct frequency pair on receive that match the transmit mark/space freqs. This is
Not at all - ICOM, Ten-Tec and others allow you to use ONE COM PORT to address multiple rigs. Running KW's, you have to have a com port for every rig (in addition to your TNC's, bandswitch boxes, etc
I had the same problem in RU this year. Occasionally, and randomly, the TX would lock up (mark or space? no monitor on my Omni VI+)and nothing would be sent. I had to hit "Esc" and then press the fun
Maybe what you are describing is what I used to call a lack of "forgiveness" in certain keyers. One particular MFJ that I had made me think I had forgotten how to send with a paddle. Turns out, when
Last weekend I did a migration install of WinXP on my formerly WinME system. Most things have worked well, and the improved stability was immediately obvious (but then WinME would make anything look
This is a multi-part message in MIME format. --NetAddressPart-00--=_cgvC0272S086c8675bb Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I think I found the prob
Not necessarily true, Jon. I'm using a DXP38 on one COM port, a KPC-9612 on another, and my Omni VI+ on a third. All work fine with one exception. XPWare (RTTY software) does not like WinXP. Gary Joh
This is a multi-part message in MIME format. --NetAddressPart-00--=_ggCv5264S09529d8e48 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable My reason for upgrading
OK, we just saw question & answers about Ritty, but what about WriteLog itself and the use of external hardware TNC's (DXP38, in my case) hanging on COM ports. How about the CW keying interface on th
Its strength is its weakness - it is a super contesting program. It is only a fair overall logging program. I highly recommend DX4WIN. I've tried and owned a number of the logging programs, and I've
The same thing happened to me several times during the JARTS, and I only spent a couple hours in the contest. Something's broke! 73, Duane AC5AA Anyone understand this? ______________________________
Two possibilities I know of: Lava card http://www.lavalink.com Byterunner http://www.byterunner.com/products/serial_cards.html Both have PCI serial port extenders for the ~$50 range. The Lava 2-port
Since it's a RTTY contest this weekend, chances are he's either prepping for the contest, or travelling to where he's going to operate. 73, Duane AC5AA Michael, K1JE _________________________________
A few months ago I "upgraded" my PC. This weekend I tried to get on the SARTG RTTY contest for a bit and found that WriteLog and the HAL DXP38 won't talk together properly (no response on tuning indi
Thanks, John - I know it is workable because it worked fine with the exact same setup on the last PC. And, the TNC works fine with XPWIN (XPWare) and with DXPWin (HAL). Something about the way it is
Found the problem. Well, let's say I cured the problem. Nothing about this one made sense, so I did what we all do when nothing makes sense - I reinstalled WriteLog. Now it works fine. Something in t
Not sure if I posted something on this already or not. Regarding PCI Serial port extenders, I use a Lava (made in Canada) card which I purchased locally, and it has worked fine for me. Also comes wit