What a great weekend!
My hat is off to all of you that contributed to this great program.
The contest organizers could have resolved the ve1 problem and saved
everyone a little grief but since I didn't work any, I don't care. hi
I still had fun.
Since I am antenna restricted to a vertical and indoor dipoles, I
decided to really study the usefulness of N1MMLogger way before the
contest even began and then continued studying it during and not
worry about a good score. Total result was only 100 qso's, however
that includes time spent...cleaning the garage and other honey do's.
Score still came up to 17407 which surprised me since it was all S&P.
Before I continue let me say that I will not be going back to my
pk232 or wf1b. This program is exactly what I wanted! It may have
it's rough edges right now, but I think you guys will work it out
First the problems I encountered were the following:
MMTTY tended to hang at the end of my xmissions necessitating a
restart of MMTTY but more often than not causing me to reboot or
restart the computer. This could have been from RF getting into the
computer though so am reserving judjment on this for now. I think
this was the cause of two errors, an EAccess Violation by MMTTY.exe
and RUNDL32 not closing properly because of MMTTY hanging.
Another transmit problem encountered was the receive window would not
keep pace with what was being transmitted. Usually half a
transmission behind. I am using a P3 600mhz with 250megs Ram with Win
98se so don't think it was the computer's fault. Resources never fell
below 80 percent anyway. The reason the jury is still out regarding
MMTTY is that if I cleared the receive window on a regular basis,
MMTTY did not seem to freeze as often. Does this sound like possibly
an MMTTY optimization issue? I am new to this program too and am
wondering if changing the sound card settings will help.
After downloading 1.1.248 N1MMLogger no longer wants to accept ANY
sections. I had to log without the section entered and then edit the
log to add the section. My copy is now saying that a mandatory
cty.dat upgrade is required and keeps on saying it even though I have
used "tools/reload" to update it each time as the warning note
specifies. Am now running 1.1.249 with the same problem. The warning
specifies that I should get cty.dat from the internet. Which site? I
am using the one extracted from the new files. Is there another I
should be using?
Here then are my observations/suggestions (pardon if someone has
already noted them):
A: The help files could use a section about how to print out the
scores at the end of the contest. You might want to add a link to a
site about Cabrillo too for those of us that are newer to Cabrillo
and are not sure how Cabrillo is formatted.
B: It would be nice if the MMTTY window with the waterfall was not
set to be always "on top". Even with two monitors running I still
found myself either having to close MMTTY to look at another window
or had to move it out of the way to the other monitor.
C: Having you guys working on the code during the contest, was in a
word, fantastic! I know it must have been tough deciding when to make
a change or to let it go till after the contest. Control Left click
to correct a call is nice even if it is temporary.
D: Although this was a rtty contest, could you add something more
about cw in the help file? I don't think my copy has any wav files of
cw in the wav folder but the help files seem to suggest that there
was a default set of wavs for cw. Specifically, how do I create such
files so I too can send cw or are they available on-line?
E: The info window and the three dimensional look to the PSK spectrum
are very worthwhile.
F: The zones problem was explained by Tom as a work in progress.
Perhaps when a problem with a feature like this is too much to do
just before a contest, maybe the feature should be turned off? I had
to go back through my log each qso just to be sure that I hadn't
forgotten to double check the zone. That could be a daunting task for
some of you "big" guns.
G: Grabbing calls seems to work as expected. If you don't have space
around the call it doesn't always work as Kevin N0RKX noted. WF1B had
the same problem. Using the space bar is a nice touch though.
That's probably enough for now. Hope I've added to the discussions.
Since I work as a LAN administrator I have lots of equipment
available to run tests on. Let me know if you need to test specific
configurations and I'll see what I can do to help. Just don't ask to
test on a PDP11/23 as that went to the trash today.
Tom Tate - WA7NPX