[Trlog] Does this sound like a hardware issue

[Bob Evans]

Hi Guys,
 
I appreciate the pre-SS SSB comments on DVKDELAY, especially from
Bernie, ZS4TX.  I didn't have time to fully implement it, but that's
next in line.  I need to play with it to fully understand where it fits
for me.
 
My issue today...I too had freeze ups (which hadn't happened before),
but I'm not sure if it was software or hardware.  What I saw 4-5 times
later on (after 800 or so Qs) in the contest was this:  I would lose
both frequency readouts (2  IC-765s with IC-V interfaces) at the same
time and then I would notice that I lost the ability to move the cursor
around even though the clock kept ticking on screen.  I was able to exit
the program normally, however, and instantly restarted TRlog (no
rebooting the machine) and everything, including both freq readouts,
came back normally.  I seem to remember this occurred while I was moving
around on the second rig.  Only lost one Q (I hope that guy responds to
my email hi hi) and it wasn't something I would even comment on, but
since I see other freeze up posts, it may help paint a better picture of
a possible bug.  My remaining memory indicator was well over 100K, so I
don't think it was that, but I think I must have overloaded the I/O
system (i.e. too fast a refresh setting).  At least that is what I'm
going to check first.  I also have that LEGACY radio setting on TRUE, I
believe.
 
Does that sound more like my hardware settings rather than a software
issue?
 
Bob K5WA
 
P.S.  I wasn't taking SS SSB too seriously until I saw 20-30 over S9 "Q"
signals on 15M (where I started) and VY1JA called me on 40M during the
first four hours of the contest handing out contact #33, THEN I decided
that I better stick around.  Had good conditions from STX until I got 2
inches of water in the shack due to a massive storm that hit Houston
late Sunday afternoon.  I only missed 2 hours of sub-30 Qs/hr rate, I'm
sure.  If I ever sounded "watery", that's why.