There are a couple of issues driving a new release of TR in the next couple of days. There is a bug with rovers that puts garbage up in the exchange window as their initial exchange. This bug has bee
If I remember how to do it, version 6.73 has been released. Contact K5TR if you need to be added to the update list. Release notes for TR Logging Program Version 6.73 - released 10 June 2003 - This i
There is more than the log format in the Cabrillo spec. It includes the summary sheet information which isn't covered by ADIF. Beyond that, they chose to make it a more human readable format. Tree
Putting my Cabrillo hat on, I would expect the correct grid to show up in the sent information for each QSO. Nope. However, the only way I can think of to do this with TR is to have separate logs fil
Great. This certainly isn't one of TR's long suits. Not sure it ever will be unless I change the .DAT log format (something I have not done for 12 years now). One idea I have had is to use the Cabri
Not much of a secret. You can use any old version of INSTALL if you want. Mostly, I think it is more trouble than it's worth. Just creat a directory and put all the files in it - and include that in
Are we saying that things are really running at different speeds? I doubt that really happens. And even if it did, I don't think there timing error between 57600 and 56000 would be an issue. 56K is
The manual lies. Well, sort of. It won't do RIT increments - it will do absolute values. The Kenwood has a command that says "bump the RIT up (or down) by one count". The Yaesu requires you to read t
DirectIO should solve most of the issues - except for one. Windows-XP is based upon NT - and as far as I know, there is no way to make the OS send code well. Tree