Writelog, another view

[Jim Worsham]

Having used Writelog for the past few years with the W4NH multiop I agree
with all your comments.  Also, the networking function is flaky and is
always giving us trouble but it is better than nothing.  If you (or anyone)
knows of a Windows based logging program suitable for multi computer/multi
op contesting (i.e. supports real networking like 10BaseT, rig control,
voice keyer, etc.) then I would love to hear about it.  As far as we know,
Writelog is the only game in town for that.

73
Jim W4KXY

----- Original Message -----
From: "Jeff Ach" <w2fu@rochester.rr.com>
To: <vhf@w6yx.stanford.edu>
Sent: Saturday, January 26, 2002 5:46 PM
Subject: Writelog, another view


> I have converted to Writelog for HF contesting about a year ago.  I found
it
> extremely good at just about everything and the added plus of being
windows
> based is obvious.  However, for VHF contesting it has significant
> shortcomings that made me dust off my old homebrew DOS software for our
> Multi at W2FU in the January Sweeps.
>
> I post this in case anyone has found workarounds or wish to follow up with
> notes to Writelog as I have about the shortcomings for VHF contesting wih
> Writelog.
>
> 1. When running stations up through the bands quickly, especially rovers,
it
> is a real chore to re-enter the call and grid for each band.  In my
software
> I had a shortcut single key that copied the station and grid from the
> previous QSO and plopped them into the current QSO entry line.  Another
one
> key change band and enter to log him.  I use buffers that go three calls
> deep to allow for working multiple rovers traveling together.  Without
this,
> it really gets cumbersome when you work WB2XXX/VE3/R on 10 bands in 3
> minutes.
>
> I thought that the windows cut/paste would do the trick but it doesn't.
If
> you select and copy the last QSO, then paste into the QSO entry window, it
> tries to put everything in the the first field (callsign).  If you copy
the
> call after you enter it then use it as the paste buffer, it does at least
do
> the trick for the call part.
>
> 2. My master database scheme has room for 6 digit grids and a note (could
be
> Name, bands active, or an alert that this a one of our local rovers).
This
> is extremely handy for 6 digit headings etc as well.
>
> 3. The direction headings in Writelog are not based on grid squares, but
use
> the country.  All headings point me to Kansas City.  Not much good for my
6'
> dish on 2304! You must use a separate distance bearing calculator and
enter
> the grids manually.
>
> 4. Finally (and possible the most serious because I couldn't come up with
a
> workaround) is that the chat function for multi-op does not do directed
> messaging, it's always a broadcast.  As all of you are aware, VHF
contesting
> is all passing from one band upwards. In Writelog, its more of an
> informational thing.  When the 432 station sees all the passing, its real
> easy to miss the ones for you.  In addition, there is no beep or flash to
> alert you that you just got a pass from another band.  Also the from
station
> indicator is just an assigned letter, not a named station.
>
> Again, if anyone has workarounds (I got no response on the WriteLog
> reflector) let me know.  I am going to follow up to K5DJ next week with a
> revised list of features for VHF contesting.
>
> ------
> Submissions:                    vhf@w6yx.stanford.edu
> Subscription/removal requests:  vhf-request@w6yx.stanford.edu
> Human list administrator:       vhf-approval@w6yx.stanford.edu
>



--
Submissions:              fourlanders@contesting.com
Administrative requests:  fourlanders-REQUEST@contesting.com
Problems:                 owner-fourlanders@contesting.com