Gary, Check Vista's internal settings for 'line (microHAM CODEC).' Vista may have it muted or have set the input level to zero. This is one of the big problems with Vista's audio system - it takes ab
No, Router is not overriding WriteLog. WriteLog implements the "pot lock" mode in WinKey and current versions of Router respect the application's settings. In "pot lock" mode, WinKey (and Router) re
The "V" command is internal to the microHAM Control protocol. It is not useful at the user level but is used for specific handshaking between an application (like a logging program) and microHAM Rout
Vista and Windows 7 have their problems but they do work if you take a few simple steps to deal with the paradigm shift - . particularly "User Account Control," the completely different audio interfa
Gary, Selecting the Software Generated FSK options causes RTTYrite to hold onto the FSK port. It generates the FSK directly and but does not work with DigiKeyer, microKEYER, microKEYER II and MK2R/MK
MMTTY puts PTT on the FSK port (DTR and RTS). Use a separate PTT driver transistor (in parallel with your "all mode" PTT) for FSK with the MMTTY plug-in. 73, ... Joe, W4TV ___________________________
Nothing abnormal about the K3 serial port. Use three wires 2-2, 3-3, and 5-5 ... no handshaking. Make sure Writelog is not trying to implement hardware handshake ... since the K3 does not assert DSR
The question is how Writelog does the mousewheel tuning vs. any other program. The FT-990 command set has only one "step operating frequency" option (Up or Down). The step size is set by the "fast" s
The issue is in your FT-990 not in Writelog. I've checked and Writelog is sending "00 00 00 01 8Eh" or "00 00 00 00 8Eh" for scroll down or scroll up. Those are the correct commands to for up/down on
I have uploaded updated setup guides for the WriteLog and microHAM MK2R/MK2R+ to the files area of the microHAM group on Yahoo (http://groups.yahoo.com/group/microHAM). The same files are available t
It appears that the FTDI chips will handle 5bit codes. The issue is that FTDI (and other chip houses) have increased the clock speeds to provide faster communication (up to 10 Mb/s) for non-communic
Gary, Have you set the mic level in the Windows Vista Mixer? Right click the speaker icon, select "recording devices" select Microphone - USB Voice CODEC, then the Levels tab. Make sure you have the
Recording within WriteLog is controlled by Writelog and Vista. The "soundcard" in microKEYER II is just like any other soundcard, it provides samples at the bit depth and sample rate that the operat
None of the Icom transceivers work with AFSK in RTTY mode. To operate AFSK you must be in LSB (or USB) for any rig prior to the IC-746Pro or IC-756ProII. Icom introduced LSB-D/USB-D in the 746Pro/75
The USB Interface II provides the same CAT, CW and FSK (except for pFSK in fldigi) capability along with audio isolation transformers (without the soundcard) at about the same cost as the RigBlaster
This should be added to the FAQ <G>. Note the "virtualstore" is a function of Windows' User Account Control (UAC). As with Vista, turning off UAC and installing WriteLog to a directory tree OTHER THA
Windows NT is Windows 4 - the first true 32 bit version of the Windows operating system and first version of Windows that was not built on an MSDOS base. It was the predecessor to Windows 2000. Even
First, you've been told how to fix it ... simply connect to a packet/tenet node if you have the window open or save your configuration so the packet/telnet window does not open automatically. Second
By default, the FT-2000 requires RTS/CTS handshake. You will need a cable with 2,3,5,7 & 8 or you will need to disable handshake in the FT-2000 menu (check your manual) and disable RTS support in Wr
9 wire cable should work correctly ... I used one for my "real" serial port when I had the FT-2000 on-line. It does but you also need to disable RTS/CTS handshake in WriteLog FT-2000 driver. See the