Recently built a new system and had to reinstall all the software.
Since then, am unable to get MMTTY under DX4WIN to key the FSK line.
MMTTY as stand-alone works just fine and keys proper PTT and FSK lines
as it has for many years. MMTTY under DX4WIN keys the PTT line just
fine, but not the FSK line. Looking for ideas as to why. Here's how
I'm set up: DX4WIN V7, MMTTY 165B. In DX4WIN setup parameters: CW/PTT
control- COM4, DTR is CW keying, RTS is PTT Control. RTTY tab - Type =
NONE. In MMTTY setup, Misc Tab, TX port set to COM-TxD(FSK). In MMTTY
window, keying setup, PTT Control set to RTS.
MMTTY window is opened from DX4WIN, receive is just fine. If I hit the
TX button, RTS line comes up on COM4 for PTT, but no FSK. As you'd
expect to see if MMTTY were set up for AFSK. Again, MMTTY stand-alone
works perfectly. Any ideas?
73, Floyd - K8AC
From [EMAIL PROTECTED] Wed Mar 29 23:27:53 2006
From: [EMAIL PROTECTED] (Jim Reisert AD1C)
Date: Wed Mar 29 23:32:52 2006
Subject: [Dx4win] DX4WIN.CTY Release #28 - last call
Message-ID: <[EMAIL PROTECTED]>
I have posted updated release notes for DX4WIN.CTY Release #28:
http://www.ad1c.us/dx4win/history.htm#28
The list of callsign exceptions and QSL manager changes is current as
of 29 March 2006.
I expect there will be another jump in the number of QSL managers
when I finish processing the calls from CQ WPX SSB. There are no
radical changes to the size of the QSL manager database this
time. Remember, only QSL manager *changes* are listed in the release
notes, it would take up too much space to list all the additions.
The release will be sometime this weekend (April 1/2).
73 - Jim AD1C
--
Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.us
