WriteLog only supports FSK on COM1-COM8. That limitation also applies to the MMTTY plug-in since the FSK port is set by the WriteLog RTTY Window when the "TU" (MMTTY plug-in) is started. Since you a
If the port on the dock appears as COM1 in Windows, set RTTYrite for COM 1 before you open the MMTTY set-up within the plug-in. That should enable FSK on COM1. 73, ... Joe, W4TV ____________________
Don, The problem is that the MMTTY plug-in does not change rates in response to changing the mode menu in RTTYrite. If you select 75 baud in RTTYrite, close MMTTY (close the RTTY Window or change TU
Update for Writelog users: The MMTTY plug-in sets its data rate and mode (RTTY/ASCII) when it initializes. Changes in RTTYrite are not reflected until the plug-in is reinitialized. To change RTTY mod
You need two CT-17 interfaces and two serial/USB ports to use two radios in Writelog (and all other contest software that I know of). 73, ... Joe, W4TV _______________________________________________
No, Writelog will not support more than one radio on a single COM port. Neither will any of the other major Windows based contest software. 73, ... Joe, W4TV ________________________________________
Jim, Part of the Hardware Abstraction Layer that no longer exists in Windows Vista and Windows 7 is access to the Mux/Mute/Select switches on the soundcard mixers. Without that capability, I don't kn
microKEYER II already provides the ability to "echo mic" within its hardware and the original microKEYER provided for microphone bypass (audio routing "A"). Both designs are consistent with Wayne's
Gary, Let me amplify what Wayne has said and let you know that the current beta test version of Writelog works very well with microKEYER II in both Vista and Windows 7. I had previously checked it on
Steve, Do either of these solutions work in 64 bit Windows (Vista or Windows 7)? Most of the other similar LPT drivers are not 64 bit compatible. I've seen some information that UserPort is not compa
INPOUT32 is a substitute for DLportIO which was used for LPT access in N1MM Logger. DLportIO did not work with Writelog so I don't expect INPOUT32 to work unless WriteLog is updated to use the alter
Google finds several articles that indicates that PortTalk is not compatible with 64 bit systems. INPOUT32 is known to work with 64 bit systems but WriteLog would need to be modified to use it (just
This error message comes from MMTTY. It means that MMTTY can not find USERPARA.INI in the directory it is being loaded from or the file is corrupted. USERPARA.INI stores the settings for the many "p
I've had some discussion with AA6YQ who is currently maintaining MMTTY concerning userpara.ini. Dave confirms my understanding that userpara.ini is opened from the MMTTY program directory. Remember M
Here's the change log list since 10.73: 10.77 June, 2010 Update ARRL 10M Contest module to include Mexican states. Update PAQP to 2010 rules. Installer now supports Vista, Win7, and 64bits. Users nee
Which operating system? Where (disk/directory/path) are WriteLog and MMTTY installed? "mmtty tnc.dll" is the "shim" that actually runs MMTTY in the plug-in and should be located in the WriteLog prog
Try uninstalling the MMTTY Plug-in from Control Panel, then reboot the computer (cold boot) and reinstall the plug-in. I've just done a complete clean install of WriteLog 10.77H in Windows 7/64 (prof
OK, I can generate the MFC error but not using my normal log in as an administrator in Windows 7/64. If I create a second account with standard user permissions, I see the MFC error and can't run RTT