I did a POST U E Z the other day & was surprised to see I've collected some 10-10 numbers. Don't know at what stage those crept in. New data either added manually with a text editor or TR logs with P
Tack: Really, it sounded like you were transmitting on two bands simultaneously to me. My friend was over at the time & he thinks the same, too - we switched one radio between two frequencies & each
Sorry, that reply to JE1CKA was supposed to go to him directly, especially when I took the piss about dualing-CQs (my first go at ^- in JIDX resulted in an allegation that I was running two transmitt
6.73 & the IARU.DOM file that came with it worked fine at VR2BG, without any problems logging anyone's zone or society name. DOS 6.22, QEMM & DVPTSR running on the machine. 73, VR2BrettGraham
Max: I don't seem to be able to find anything at ftp://nc7j.qrq.com/trlog - would like to play around with SETCOMM. Could you send a copy to me, please? Thanks! 73, VR2BrettGraham
S57AD's recent post about additional data edited into TRMASTER.DTA but vanishing from the .ASC file after doing POST U E A reminded me that I believed things were going missing on me, but couldn't qu
US5WE replied to KK1L Actually, it does. The 735 is odd in that it uses one less byte for frequencies than all other ICOMs. W9WI earlier noted: By any chance in one of those three versions of firmwar
Latest POST UEB bombs with 021F:484C on my trmaster.asc file. That file bombs with previous versions of POST (xxxx:484C), but a previous version of the .asc file works fine. The differences between t
By adding line-by-line the differences between an older version of my trmaster.asc file which works & my current trmaster.asc file & UEBing it each time, I have found the culprit: K6III =C03 =H261 =I
VE3IAY replied to NQ4U: Those are correct. I long ago pulled the battery from my PK-232, so if that is the default then this is why I don't recall ever setting that (either that, or I need more tea ;
K6XX noted: A version or two back - after TR READ was introduced - I was playing around in some contest not directly supported by TR & changing exchange, QSO point & multiplier parameters on the fly.
NQ4U continued: If you mean the FSK equivalent of wiring ones paddles backwards (having accidently connected low-on-mark output to rig instead of low-on-space), then tell the PK-232 this: TXR T This
AA0CY noted that the exchange that appeared in the exchange window for a HQ station in IARU after having been worked when tuned across would change to the ITU zone concerned if he typed the call in,
This is very much a bodge job, but below is how I managed to get TR to log the EQP. When you work a station without an Elecraft rig, enter "none" for the other op's name, otherwise enter "##&&", wher
The most important line for configuring the program fell through the cracks the first time - sorry. This is very much a bodge job, but below is how I managed to get TR to log the EQP. When you work a
Tree replied to VA7NT: I noted the pollng rate to radio 1 slows down significantly when radio 2 isn't there. I now notice that the clock updates every other second then, too. Serves as a good reminde