[SD-User] Beru.

[Paul O'Kane]

----- Original Message ----- 
From: "brian coyne" <g4odv at yahoo.co.uk>

> No1 - the keyer was corrupted, had to wind down to about
> 10wpm to get a true speed of 30wpm and then suffered
> interuptions/ delays.

Did the CALIBRATE command make any difference?

Regardless of whether it did, we can't depend on the internal
CW from any Windows PC being smooth.  Sometimes it is perfectly
OK, and often it's not.  It is caused by Windows doing its own
thing internally.

The only reliable solution is an external keyer - I use WinKey
USB.  I think it's wonderful because it combines the best of
an integrated keyer and the flexibility of a standalone keyer.
It works with most up-to-date contest loggers.  They are
usually readily available from k1el.com, although there may
be a backlog at present because K1EL was injured in a car
crash recently.

> Whilst the foc.lst was loaded nothing at all appeared
> when a members c/s was keyed in.

I can't comment other than to say that SDC works OK here
with FOC.LST loaded.

> on several occaisions I forget to change bands in the heat
> of moving people around.

I strongly recommend rig control, if your rig supports it.
That way, you can forget about having to change bands on 
the software.  The biggest benefit, however, is in moving
people around.  Just type the new frequency, and the rig
moves there.  Type " (Quotes) to repeat the callsign and
log the QSO, then F10 (twice) retuns you instantly to your
original run frequency - no other logger is as efficient.

> Tried using the band change edit function using the
> shift/F1 key gave a message 'valid only in c/s field'

Shift/F1 etc. is the procedure for updating the F1 etc.
messages.  F1 on its own edits the band - when the cursor
is in the callsign field of the QSO to be edited.

> and wipes the qso,

I don't think so :-)   Enter, on its own, restores the
QSO you were attempting to edit.  The best option is
probably Minus - it abandons any Edit you have started
and takes you back to the logging line.

> Interestingly pressing F1 alone, without use of the
> shift key alters the scores in the scores window.

That's consistent with editing the band.

Regardless of all this, there were problems with editing
in V14.22.  Changes appeared as expected on-screen, but
did not always update the .ALL file on disk.  Anyone who
is unsure of the integrity of their log should send me
their .ALL and .AUD files (I need them both) from the
contest, and I will check them out.

I have fixed the editing bug, and am trying to find why
the audible dupe warning didn't work.  Once that's done,
I'll upload the new SDC.

73,
Paul EI5DI