I think if the built-in RTTY decoder had MMTTY's display feature fewer of
us would opt for MMTTY as a plug-in. I will vote for the MMTTY waterfall
every time! Also the upper humped display (or whatever it is called) looks
smoother and easier to interpret in MMTTY.
I am seriously thinking of going back to a hardware modem. I still have a
couple of ST-6s and PK-232s. Hate to give up the AFC, though. As long as
some of the guys are mis-using AFC, all of us need it.
I also had a few freeze-ups this past weekend. Thanks to those who waited
while I fixed it. On one one of my computers, all I had to do was switch to
dumb terminal and then back to MMTTY within a few seconds, but the other
computer actually froze up completely a few times and took several minutes
to get back online.
I didn't have as much trouble with MMTTY a year ago. I wonder if there
might be some mismatches between certain version combinations of the 3
pieces (MMTTY engine, plug in enabler, and WL).
Don't forget that other programs running in the background could affect
your success. Strip it down to a bare Explorer and Systray (see what is
running with the ctl+alt+delete) before you start WL up and see if that
helps (didn't help me).
Guys with extra serial ports could run MMTTY as a modem for WL without
"plugging it in" by routing the 5-bit output to a port and then using a
null modem cable to connect the ports. I used it this way as a "dumb
terminal" modem before the plug-in-enabler was available.
Wayne, is it possible to integrate MMTTY fully into the program without
having to rely on the plug-in-enabler? Maybe if we didn't have so many
pieces to coordinate versions for it would be more reliable.
Jerry W4UK
At 18:13 9/30/02 -0400, you wrote:
>Well, goodbye at least to Writelog with the MMTTY engine.
>
>Some of you may remember that a year ago I purchased Writelog after
>hearing that the MMTTY engine worked with it. After following AA5AU's
>instructions, it worked perfectly in the 2001 CQWW RTTY test until I
>closed the program at sleep time. The next day all I got was a stuck
>"initializing MMTTY" message and Writelog and MMTTY never worked again. I
>tried a ZILLION things including uninstalling and re-installing, all to no
>avail. Several on the Writelog reflector tried to help and one other
>person had the exact same problem.
>
>After weeks of trying to find a fix, I gave up. The experience kinda
>spoiled my appetite for for RTTY tests, I really liked Writelog and was
>hooked on MMTTY. I did not have the enthusiasm required to switch back to
>my PK232.
>
>Well, a couple of months ago I had cause to re-format my hardrive. Low
>and behold after I installed everything Writelog and the MMTTY engine
>worked !!!! So, this weekend I was all set to actually use it in a
>contest for the first time. I again used AA5AU's advice (very, very
>helpful) and was eagerly awaiting 0000 UTC for the start of the test. All
>systems were go and MMTTY purred away on a few test contacts. As the
>contest started my PC froze...uh-oh, time to re-boot Writelog an
>MMTTY. Would you believe it, exact same thing as last year occurred, the
>"initializing MMTTY" stayed there and no matter what I did , it would not work.
>
>After a couple of hours I switched to another logging programs that uses
>MMTTY and it worked well for the entire contest.
>
>I really like Writelog but there is something about it, when combined with
>MMTTY, that my PC does not like. So, its goodbye Writelog with MMTTY. I
>did at least give it a good try.
>
>Andy KB2EOQ
|