[WriteLog] Packet spots

[Jim Idelson]

Dick,

I handle these issues by keeping the WriteLog Packet Terminal window alive all 
the time. This lets me see everything that's going on at the packet source. It 
also allows me to 'talk' and 'sh/wwv' any time. 

By the way, no one should complain about screen size when running WriteLog. You 
can increase available screen area in two ways:

1.	Use Windows Multiple Monitor Support. This is easy to do if you are using a 
laptop that supports this functionality. You can put your real-time logging 
interface on the main screen and the other information on the secondary screen.

2.	If you don't want to run multiple monitor support, you can network a second 
pc an use the second screen for WL information. This gives you the added 
benefit of a mirrored, redundant log . . . a bit of extra security in the event 
you have a problem on the primary logging machine.

73,

Jim K1IR

I noticed a couple of issues when using packet spots this weekend in CQWW SSB. 
I normally don't run assisted, so please forgive me if these issues have been 
raised before:

1. In other contest programs, the time of each packet spot appears in the spot 
window. This allows the op to quickly identify the spots that are getting a 
little stale. This would be a good addition for WL.

2. I could be wrong about this, but I think other contest programs log the call 
of the spotting station. This helps when the packet node is accepting spots 
from far away places that might have propagation when we don't. This is 
especially an issue when using Internet clusters (by far, the best way to use 
packet spots.) Whether the other programs do it or not, I think it's a good 
idea for WL. It looks like there's plenty of room in the spot window for this 
information.

73,

Dick WC1M 

--
WWW:                      http://www.writelog.com/
Submissions:              writelog@contesting.com
Administrative requests:  writelog-REQUEST@contesting.com
Problems:                 owner-writelog@contesting.com