Yes, and nothing special was needed for use with XP, using one transistor and a resistor. Keying is clean and smooth up to abt 42 wpm, (my max. speed for now.) I have tried this on the main board por
I find that the Alt-K keyer window works just as it should under XP. Text is 100% readable, operation smooth with the RttyRite CW window, all just as it was under Win 98SE. Perhaps reported problems
A while back, Don W6FFH, noted the publicity out on the Creative "Extigy" processor. I've finally tried one out, and thought I'd post what I've found, maybe to spare others some potential disappointm
Mel -- WL recognizes the KAM only for RTTY RX/TX. Sad to say, not for CW RX. Wish it did, as I have a KAM Plus for backup, and use it on CW with older tube rigs where the reed relay keeps everything
Jerry, I realize you are hoping to get everything to start all at once, but the only solution I have found so far is to not try to have the RTTY windows open automatically at startup. In other words,
I never _ EVER_ thought I'd need to recover lost log data the hard way! I'm pretty fanatical about backing up, but sometimes things don't go the way they should. (Murphy is stilll around.) Short vers
Jim, The Edit > GoToQSO command works fine once you type in a callsign in the Entry window. Once you've found what you're looking for, just punch F11 to clear the call out of the window, or just type
Since early January I've been using a slightly simpler Logitech wireless keyboard, model Y-RC-14, and really love it. It comes packaged with a cordless mouse - non-optical - which works very reliably
the Not at all, Don. As a result of running RTTY from OE2-land for several years, I also prefer to monitor 1275/1445 tones in FSK with the plug-in MMTTY module. So very much easier on the ears. Conf
Has anybody been successful in interfacing a classic TU, like the ST-8000, to a standard serial port under Windows XP or 2K? Mine works just fine under Win98SE (dual boot. ) I run MMTTY in one RttyRi
Looks like I have found the problem. The 8000 works fine under XP HE with a different serial port. Problem was a classic IRQ conflict. That should be easy to solve..... I hope. Jon K1US stuck
Bill, the previous year's contest file doesn't save the port setup. Hardware configuration is saved separately and is contest independent. I've used the Alt-PrintScreen facility to paste and via Pain
-- Over the last year I've been experimenting with using the same exchange for both. That way I just use INSERT for the exchange all the time with an all-purpose buffer set up on F10, like this %R %
Hi Dean, Don't give up! I'm sitting here right now reading your email message while my homebrew N6TR-style interface for the 850 is pumping out frequencies happily and speedily to and from the comput
Jim, I'd also add to your well-taken comments an unusually long initialization and shut down time either with stand-alone 1.62 or the plug-in. As much as 25 seconds on stand-alone, 15-20 secs on the
Jim, Bill, et al -- Actually the MMTTY stand-alone DOES have rig control, on the Setup TX tab below the PTT section. I use mine with either of my Kenwoods. But the delay in start-up and shut down is
After FireBrick Bill's timely reminder about the detailed Task Manager info available under XP, I've just finished a little research / comparison effort here using my dual -boot setup with XP and W98
Hello, Alessandro -- The error you are getting is very likely the result of problems in your WriteLog.INI file in the lines where file paths are listed. For instance, check the line in [Multipliers]
The Setup / Log Font tab allows free selection of any installed font. The Entry Window Font tab reduces the available choices to only a few very basic ones -- none of which will produce the slash zer