This thread has been enlightening to say the least, even if it is re-visited after each contest. It would be nice if everyone that has responded with "their opinions" would spend half that amount of
-- ORIGINAL MESSAGE --(may be snipped) REPLY: As I said, you rarely if ever see it because most ops DO place an {ENTER} command at the start of each macro. Without the {ENTER} the problem would exist
-- ORIGINAL MESSAGE --(may be snipped) REPLY: There is one other common cause for wrong frequency spots that has nothing to do with skimmers. Stations using AFSK often spot the suppressed carrier fre
Jerry, I think you're a WriteLog user. If so that would explain why you don't see lines jumping up the screen. Wayne W5XD was very clever in his programming of the Rttyrite window - analogous to the
There is also a non-scrolling window in N1MM now. That was included from the start of the + version.. 73 Rick N2AMG Jerry, I think you're a WriteLog user. If so that would explain why you don't see l
Oh YES Lee! All this make it very clear, I suppose that from who is the originator of the entry there could be applied any further check about the skimmer in use. Perhaps what seemed to me is wrong .
I saw several cases where the leading and/or trailing character of a call sign got clipped. Perhaps the skimmer is seeing something like that. We have had the discussion many times about how to minim
Hi Larry. Yes, you are right. But I was supposing/speculating, maybe wrongly, that the latest RTTY skimmer is a little bit more prone to that kind of error. It seemed to me that the DL4RCK RTTY wasn'
Indeed Rick... But for some reason, it doesn't work exactly the same as Writelog. I was a long time Writelog user, (at least 7 years) and it was great... the N1MM+ version is not the same. 73 Jim W7R