[WriteLog] MMTTY Plug-in problem

[Joe Subich, W4TV]

Jim,

Is you path to MMTTY pointing to a shortcut instead of the EXE file
- or is there a shortcut in the target directory?

The MMTY plug-in for WriteLog calls the exe file with some special
command switches to configure the correct display (information is in
programmer's documentation).  It is possible that calling a shortcut
instead of the .exe file can block the necessary command switches.

73,

    ... Joe, W4TV


On 7/29/2011 4:56 PM, Jim McDonald wrote:
> I know this is bizarre, but I've tried several different approaches and
> still have the problem.
>
> With Windows 7/64, WL 10.87, and the MMTTY plug-in installed with the legacy
> installer, when I open the Rttyrite window, I don't get the MMTTY control
> panel.  Instead I get the full MMTTY running minimized.  The standalone
> MMTTY is doing the decoding, not the Rttyrite window.
>
> I have Windows 7 UAC turned off.  I uninstalled WL, which had been in the
> Program Files x86 folder, into my C:\Ham\Writelog folder.  I have tried
> MMTTY.EXE with and without the "Run as Administrator" box checked.  I have
> deleted another user account on the computer that I had for my wife.  I have
> cleaned the registry with Norton Utilities.  Speaking of Norton, I do have
> Norton Internet Security, and I have tried turning that off.  (At this
> point, I'll uninstall it if that would help.)  I have tried a couple of
> different full installations of MMTTY, each of which works OK standalone.
>
> I can choose Rttyrite AFSK instead of MMTTY, and that works.
>
> Interestingly, after I uninstalled WL and reinstalled it into
> C:\Ham\Writelog, I didn't get a writelog.ini file copied into the
> ...\VirtualStore\Windows folder.  I did copy the initial one in from
> \Windows.
>
> I really am motivated to make this work.  WL supports the subreceiver in my
> K3, and I've had stability problems trying to get N1MM to work with SO2V.
> N1MM actually crashes the computer after I try to close the port configurer
> window if I select SO2V, and I have no way to recover but to do reboot it.
> Maybe that's a symptom of the same problem I'm seeing with WL.  I assume
> both are caused by my computer configuration.
>
> Any suggestions in solving this "Believe it or not" problem would be
> appreciated.
>
> Jim N7US
>
>
>
> _______________________________________________
> WriteLog mailing list
> WriteLog at contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web:  http://www.writelog.com/
>