[WriteLog] Need RTTY help with version 12.23j

[Ed Muns]

A Com port is only used for FSK, but you mention choosing AFSK below.  So
first of all, decide which transmission method you are going to use: FSK or
AFSK.  What did you use in the past with WL version 11?

Next, decide if you will use MMTTY's FSK or AFSK feature or if you will use
the Rttyrite native FSK or AFSK.  Which one of these four choices requires a
different configuration.

If you are trying to use AFSK transmission, then go into the MMTTY Options
menus and select 'None' for the Com port.

The Windows error message about the Com port not being available means that
you have a Com port selected in MMTTY (and, are therefore trying to setup
for FSK) that is in use by another device or that Windows thinks is assigned
to some interface.  Make sure nothing is using the Com port number you want
to use for your FSK interface.  Sometimes, Windows will say a Com port is in
use only because it saved that configuration from a prior use of that Com
port number.  In that case, you can just ignore the message and use that
number.  Windows will then reassign it to your current interface, though it
may take an exit and reload of WL and/or Windows.

Rest assured that WL 12 works fine, just as WL 11 did, for either FSK or
AFSK RTTY transmission.  But, of course, it has to be configured correctly.

Ed W0YK

-----Original Message-----
From: WriteLog [mailto:writelog-bounces at contesting.com] On Behalf Of Gary
Gross
Sent: 06 March, 2018 22:03
To: writelog at contesting.com
Subject: [WriteLog] Need RTTY help with version 12.23j

Back in January I purchased V12.23j after running version 11 for many years
without any problems. I haven't been able to get my rtty running
successfully yet. I usually run MMTTY with writelog rittywrite for RTTY.
Every time I click my mouse on the call sign entry box my ritty screen
disappears. I had previously asked for help with this problem and was told
to download and register xmmt.ocx and delete the original mmtty plug in
module which I also did. Still no luck. If I change TU mode in the ritty
screen to xmmt.ocx I receive  a com port not available message. If I choose
Soundboard AFSK in the TU section I get the same results, the ritty screen
still goes away. Please help. Thank-you. Gary KE6QR

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
WriteLog mailing list
WriteLog at contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/