[WriteLog] V11.10G work arounds for EA test

[Gary AL9A]

Don,

Sorry for the dupe on 15M.  Supe Check partial decoded two calls as new 
mults and you were number two.  When I hit Insert it started sending to the 
first call instead of you.  I hit Esc and then clicked on AA5AU and did the 
exchange, but then messed something up on the keyboard and it didn't enter 
into the log.  I didn't notice this until later when I saw AA5AU in the band 
map again, but as a mult, not a dupe!  Huh?  So I had to work you again and 
do it right the second time.

I ran using the suggestion in point two below.  I configured Rttyrite for 
software genereated FSK and it seemed to work ok.  The only problem I 
noticed was if I shut down WL for a break I had to reconfigure Rttyrite for 
software generated FSK again.  It doesn't retain that setting when you shut 
down.  I never could get 2Tone configured to work in transmit in the main 
Rttyrite window so I just ran it in a cloned window.  I did notice 2Tone 
decoded several calls where two MMTTY windows missed them.

73,
Gary AL9A


----- Original Message ----- 
From: "Don AA5AU" <aa5au at bellsouth.net>
To: "WL" <writelog at contesting.com>
Sent: April 05, 2013 1:32 PM
Subject: [WriteLog] V11.10G work arounds for EA test


> Sorry this is so long, but it's a lot of information I feel needs to be 
> communicated. I think it's well known now that there are several issues 
> with V11.10G. Here are some work arounds if you plan on using 11.10G for 
> the EA RTTY Contest this weekend.
>
> 1. MMTTY plug-in freezing Rttyrite when accessing the TU Type menu:
> The initial work around for this would seem be to uninstall the MMTTY 
> plug-in and use MMTTY via XMMT.ocx. However, that's broke too since when 
> using MMTTY via XMMT.ocx causes AFC to be turned on automatically when the 
> Entry Window is cleared. If you really want to use the MMTTY plug-in, the 
> work around is to clear Rttyrite entries in writelog.ini, open WL, open 
> Rttyrite, select MMTTY as TU type, then DO NOT TRY TO ACCESS TU TYPE MENU 
> AGAIN. It will lock up but you can get out using Windows Task Manager to 
> close Rttyrite.
>
> Tutorial on how to clear writelog.ini:
>
> http://rttycontesting.com/writelog/rttyrite/rttyrite-clear.html
>
>
> 2. Transmit characters are sent to Rttyrite all at once instead of one 
> character at a time:
> This problem exists using either hardware generated FSK or FSK via MMTTY 
> regardless of whether you use the plug-in or XMMT.ocx. Same goes if you 
> use 2Tone and hardware generated FSK. The work-around is to use 
> software-generated FSK. Another workaround MAY be to use EXTFSK for MMTTY 
> via XMMT.ocx. I'm not 100% sure if EXTFSK is available when using MMTTY 
> via EXTFSK. Need to test it. But software generated FSK can be used even 
> if you use a legacy COM port and transistor keying. Steve AI9T and I have 
> confirmed this works and sends transmit characters to the Rttyrite screen 
> correctly.
>
> 3. AFC turning on automatically when the Entry Window is cleared when 
> using MMTTY via XMMT.ocx. There is no work around for this, only a 
> suggestion. Try using 2Tone in the main Rttyrite window and MMTTY via 
> XMMT.ocx in a clone window. Use software generated FSK. This is what I 
> plan on doing. Just do whatever works for you but make sure you get into 
> the contest!
>
> If you want to uninstall the MMTTY plug-in for WriteLog, here's a tutorial 
> on that:
>
> http://rttycontesting.com/writelog/mmtty/plugin-uninstall.html
>
>
> All tutorials are now on the Tutorials page of rttycontesting.com although 
> I have yet to complete MMTTY and 2Tone setup pages. Most people already 
> are familiar with MMTTY and new 2Tone users can gain enough information 
> from the 2Tone help file 2Tone.PDF that comes with each version of 2Tone 
> in the zipped file.
>
> Another suggestion - if you are new to 2Tone and using 13.03a, try the 
> latest version 13.04a. It has a faster AFC response time. I'm not sure 
> what happened between 13.02b and 13.03a, but something changed. 13.02b is 
> better than 13.03a. David sent me a special version which I tested in 
> BARTG and it was very good. I have to believe it may be part of 13.04a 
> even though I have yet to try 13.04a.
>
> If you use AFSK, I don't believe there are any work arounds, but I may be 
> wrong on this.
>
> 73, Don AA5AU
> _______________________________________________
> WriteLog mailing list
> WriteLog at contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web:  http://www.writelog.com/
>