- 1. [RTTY] PROBLEM SOLVED (score: 1)
- Author: alan.r1 at comcast.net (Alan Realey)
- Date: Tue May 27 17:53:45 2003
- Well, as usual, I spoke too soon. I was able to solve my problem by going to the set-up options of MMTTY and choosing "sound and COM FSK". I can now monitor my output. Sorry for the waste of bandwidt
- /archives//html/RTTY/2003-05/msg00206.html (6,187 bytes)
- 2. [RTTY] problem solved (score: 1)
- Author: "Mike Brown" <k9mi@sbcglobal.net>
- Date: Fri, 16 Jul 2004 16:42:23 -0000
- As I thought, it was in a software setting in MMTTY and the MMTTY Engine for WriteLog. Thanks for all the suggestions, and hope to have plenty of free time for NAQP tomorrow. Thanks again...73 Mike K
- /archives//html/RTTY/2004-07/msg00149.html (6,657 bytes)
- 3. [RTTY] Problem solved (score: 1)
- Author: "Ron Hall" <ronkp2n@earthlink.net>
- Date: Mon, 13 Mar 2006 14:39:36 -0500
- Thanks to Rich, VA1CHP, and Chuck, N6OJ, I now have the proper exchange working in N1MM. Hope to work you from W4GAC M/S in BARTG. 73 Ron KP2N _______________________________________________ RTTY mai
- /archives//html/RTTY/2006-03/msg00193.html (6,113 bytes)
- 4. [RTTY] Problem solved (score: 1)
- Author: "Dick White" <whiter26@sbcglobal.net>
- Date: Mon, 17 Mar 2014 16:15:19 -0500
- Thanks to those who offered help on a problem I had. I could not get MMTTY or N1MM to send out a signal from a OMNI-7. I received a lot of good advice and tried everything I could think of. Being a C
- /archives//html/RTTY/2014-03/msg00167.html (7,601 bytes)
This search system is powered by
Namazu