I'm trying to fix the broken serial numbers in my SS CW log. If I scroll
thru the log from within CT, there are some duplicate and some out of order
serial numbers. Is there anyway to fix them in the .BIN file?
I tried running B2R9, but it simply generates a raw sequential QSO number
instead of pulling out the actual QSO/SentSerialNumber from the .BIN
file. I would then have to reverse correlate the whole log instead of just
fixing the bad ones. It doesn't look like the exchange data is in the .RES
file either, so I'm not sure if I can even do it using the .RES file.
It looks like manually editing the .LOG file is maybe the only
option. That's kind of a shame because if next year I want to look at last
years log, I'll surely forget the mishaps, and do WRITELOG and wipeout the
corrected log. :)
I realize that anytime there are serial numbers and more than one computer
networked, there is quite a potential for problems. However, there are
some of us SO2R guys who are more comfortable using two computers instead
of one. It would seem like a simple "fix" to update the "I'm going to send
this number" internal value when a new QSO is received over the
network. This would at least solve the problem for SO2R2C guys, and would
make the problem window smaller for true M/S guys.
73 de Doug, N6RT
/*-------------------------------------------------------------------*/
Doug Brandon http://members.home.com/dab dab@home.com
--
Submissions: ct-user@contesting.com
Administrative requests: ct-user-REQUEST@contesting.com
WWW: http://www.k1ea.com/
Questions: owner-ct-user@contesting.com
|