Could someone who has done all of the research please post a listing of what
needs to be inserted into the INI file to shut off all of this new stuff?
Or, will the next release change the default to off?
We used 10.45 at V26DX this past weekend, with fairly good results. The entry
area clearing and callsigns popping up that we were not trying to work were
very frustrating. When running, we'd often have the callsign of the station we
just worked pop up again. This was confusing as I thought that perhaps I had
forgotten to actually log the station. Then, I would be trying to enter a new
callsign, and it would be mixed up with the new station I was working, and I
had to stop running to sort it all out. Not good. I was OK with this myself,
but I had 3 other operators there who are new to Writelog, and they were
frustrated with this behavior.
Also - why can't you delete a QSO any longer during the contest? We had our
computers networked, and to test them out, we entered some dummy qsos. I then
went to delete them, and could not. I did not want to have to go through the
multi-step process of getting the network running, so I did not shut Writelog
down. Apparently, after shutting it down once, you can delete qsos. Perhaps
it has always been this way, but until the networking is more automatic, this
is very frustrating.
Regarding networking, we used 2 computers running Win98 and NetBeui, and had no
trouble whatsoever related to the network at all. I started the computers and
got them networked a couple of hours before the contest, and the worked
perfectly until the end of the contest.
We did see some strage behaviors however. QSO numbers were missing, or
duplicated. The QSO count shown in our summary differed quite a bit from what
the entry window showed. It didn't seem to make any difference, so I ignored
it. Strange anyway.
One of the computers did not recognize LB for Labrador, which caused that
computer to show one multiplier less than the other. I have no clue why they
were different. This was the only discrepancy between the two computers.
The auto save thing, and the auto save alert thing drove me nuts. I had the
autosave set to 50, 100, -1, and the silly warning message kept showing up. I
then found that there was another parameter that controls the alert. This
needs to default to off too.
Aside from these few minor quirks, it worked well.
I did identify a new problem, but it has nothing to do with Writelog. That
was when I asked a station if he could work us on another band. He replied
that we had already worked on that other band. I told him that my computer did
not show it, and I asked him when we worked on that band. His reply was "in
October".
73,
N5NJ
> ------------Original Message------------
> From: Steve Holton <sholton@optonline.net>
> To: writelog@contesting.com
> Date: Mon, Mar-8-2004 10:47 AM
> Subject: Re: [WriteLog] Anoyance during ARRL DX contest & AutoSave doesn't
> save
>
> When in doubt "RTFM" which I didn't - but I was unable to find them during
> the contest by searching the help - guess next time I should always study
> "what's new" carefully ;<(
> .
> There are several other relevant parameters which I missed including:
> AutoFillFromBandmapHz, AutoSetToSplitFromBandMap, and TuningDetectionCount
>
> I think adjusting these in combination can make this a pretty nice feature,
> but I also agree that, perhaps it's best to set the default to defeat them
> when first introduced.
>
> When grabbing spots with splits - like 40M & 80M in the SSB 'test I noticed
> a further wrinkle in this.....if you grab a spot with QSX and then have to
> tune the QSX frequency - this is frequent occurrence as the DX jumps around
> trying to find a clear listening frequency.....
> On my FT1000MP-MkV if I grab a spot with QSX and then change the frequency
> on the sub VFO-B - the AutoFill etc does not apply - I can tune to my
> hearts content and the Call in the entry window doesn't change.
> On my K2 that's not the case - the tuning AutoFill etc parameters apply
> when tuning VFO-B when running split- this was perhaps the most frustrating
> aspect of this new feature.
>
> On a completely different note AutoSaveCount no longer seems to work. Any
> number I put in there has no effect. If I set the count to 5 or 10 nothing
> is saved and it starts warning at 20 QSOs. If I set it to 25, it also
> starts warning at 20, but saves nothing when I hit 25.....
>
> 73
> Steve N1NB
>
>
> >The answer is in the "what's new" section of the help file 10.45.
> >
> >The ini.file [ENTRY] AutoClearOnTuneMinHz set to zero will disable
> >AutoFillFromBandmap as well. Set this to zero and WriteLog will not clear
> >the Entry window when the radio is tuned.
> >
> >Don KF2XF
>
> _______________________________________________
> 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/
|