Writelog has:
CW decoder
Real rotor control
A real band map
What K1MM has:
An attitude. When I inquired about rotor control, I was told in so many
ways that the rotor feature is not needed in contest logging software.
In fact, "they" are so convinced; they wanted to know why I used rotor
control in a contest.
My interpretation of what "they" are saying: No contester in their right
mind would ever use rotor control.
When in actuality, I use it all the time. When working stateside as well
as JA's. We can do that here on the west cost with only one rotateable
Yagi.
73
Jim W7RY
-----Original Message-----
From: writelog-bounces@contesting.com
[mailto:writelog-bounces@contesting.com] On Behalf Of Alan Maenchen
Sent: Sunday, December 11, 2005 10:40 AM
To: writelog@contesting.com
Subject: Re: [WriteLog] Does WL or N1MM have any neat features the other
We used N1MM at the recent K7C expedition. Here's what I found:
In DXpedition mode N1MM worked just fine until the log started filling
up.
Then the CW keying became flakey. It was a little different than the 'ol
Writelog stutter. Individual characters seemed to complete OK, but the
spacing between characters became erratic. Eventually, most of us gave
up on
computer sent code and manually sent everything.
The SSB guys didn't get off without problems though. Just logging a QSO
would occasionally take an excessive amount of time. The op thinks he
didn't
actually hit the enter key so he hits it again .. resulting in a double
entry in the log. Or, since the last call was still in the entry
window,
the op starts copying the next call concatinating with the previous call
..
causing all sorts of interesting comments by the op.
N1MM networking was almost perfect. We had 7 computers networked and
built
up one single log .. a copy of which was on each computer. HOWEVER, N1MM
would throw up an error message in your face whenever it couldn't see
one of
the other networked computers due to some timeout. You have to grab the
mouse to clear it! Sometimes this happened so often and so fast the
error
windows couldn't be cleared even with rapid fire clicking... while the
unruly pileup waits... Several times we gave up and simply rebooted the
machine. This is a serious problem!
N1MM uses a standard dbf format for the log. This is the reason we chose
N1MM in the first place. MS Access can play with the log during the
event
without bothering the operation. Plus one for N1MM!
N1MM has a fatal flaw in that it crashes (all networked computers crash
at
the same time) when the log exceeds 32,000 QSOs. This isn't something
that
is likely in SS, but in a DXpedition it happens.
We did not use a lot of the features. The Yak function worked fine. The
learning curve wasn't too steep.
I still use Writelog at home.
73, Al AD6E
----- Original Message -----
From: "Barry" <w2up@mindspring.com>
To: <writelog@contesting.com>
Sent: Saturday, December 10, 2005 3:19 PM
Subject: [WriteLog] Does WL or N1MM have any neat features the other
doesn't?
> I was reading some of the N1MM docs this morning... All logging pgms
> basically do the same thing, but each has its own way of doing things.
> I was wondering if WL or N1MM has any neat features that the other one
> does not?
> 73,
> Barry
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|