Same here, except I'm using N1MM so looks like maybe its a MMTTY problem, not the logging software. -- Original Message -- From: Dave Hachadorian <k6ll@juno.com> To: <writelog@contesting.com> Sent: F
According to the MMTTY programmers reflector, Mako has a handle on this. Look for a fix soon. I ran N1MM this weekend and it happened with that software also, so its definitely a MMTTY bug. any that
I worked him but it was hard; not sure what he was using for TNC/radio/etc. but it seemed to me that if the station calling was in the clear, he came back to it. Perhaps he didn't have any rx filters
between MM does this also; 8 memories for cq/run and 8 for s/p Different PFkey definitions possible per mode. But the basic Sounds like the ESM (enter sends message) mode in MM The penalty paid is t
I think this was mentioned before but I missed the fix if there was one. Using 10.36g and the mmtty plugin, I'm getting extra character at the start of very transmission. Most of the times its AG, so
Yes, I had the transmit dropping problem also. But the plugin hasn't changed has it? Doesn't that use the mmtty engine and not the full ver 1.63? The engine is still at 1.62 I think. I'll try going b
Actually I think they are being transmitted; alot of guys answering me have 2 extra characters before my call. Can't tell for sure but it sure looks that way. The dribble over SO2R is bad enough, can
If you used MMTTY with Writelog for the contest, perhaps you have the contest "recorded" to a file in your MMTTY directory; look for a file 030125.txt. If you have it open it with word, notepad ,etc
Thanks to Phil, GU0SUP, and the ability of MMTTY to store its window to a file, we can now see once and for all the extra characters are not being transmitted. Here's what I sent: <030125 14:36:30 TX
Always wondered what this rather unique individuals call was? Is it W0MN? Any chance a "feature" could be implemented in writelog so if that callsign is being worked "GO AWAY GIL" could be sent inste
Used the software in JARTS and everything seemed fine; downloaded the latest version, imported my messages and now INS only grabs the call, it wont send the exchange?!?!?! the "+" works fine for the
I noticed the same thing on RTTY this weekend. I had the %C programmed in the TU message so I assume thats why its sent twice; once from the correction and the second from the TU message. Is there a
With the deadline fast approaching, I'm still looking for the proper way to get writelog to extract the log into single band ones as required by writelog. Don, did you get a chance to post on your si
I have had similar trouble with the last couple versions. I'm not sure whats changed but I keep unchecking a port in the setup/ports entry area and it keeps coming back checked. I just have to keep p
I think the correct command is CtCompatibleAccel=YES and I think it is case sensitive. 73 Jamie WW3S I am also seeing this. I know CT compatibility is working because F11 acts like Alt-W. Is this a b
No. I don't have that one; didn't see it listed on the K9JY site. However, mine started working ONCE I LOGGED A CONTACT. I don't remember having to do that before; just thought you had to do a save t