[WriteLog] A Learning Experience in the WAE CW Contest

[Kevin Rowett]

Look at:  https://k9jy.com/

See the writelog.ini section.

73, K6TD


> On Aug 14, 2023, at 1:57 PM, Keith Beebe W3KB <keith at w3kb.net> wrote:
> 
> 
> There is Indeed an .ini file.
> 
> It is your Callsign. Ini
> 
> So in my case w3kb.ini
> 
> There are various Sections of the INI file such as [CONFIGURATION] or [ENTRY} in that one file.
> 
> So in this particular case (as noted below) the AutoSaveCount=1 parameter went in the [ENTRY] section of the overall w3kb.ini file
> 
> Keith W3KB
> 
> 
> -----Original Message-----
> From: WriteLog <writelog-bounces at contesting.com> On Behalf Of robert beaudoin
> Sent: Monday, August 14, 2023 4:24 PM
> To: writelog at contesting.com
> Subject: Re: [WriteLog] A Learning Experience in the WAE CW Contest
> 
> 
>     Good Afternoon Keith and Jamie
> 
>         I believe there is no more writelog.ini ??  so what file did you guys  put  AutoSave in ?
> 
>                 73   BoB WA1FCN
> 
> On 8/14/2023 2:11 PM, Keith Beebe W3KB wrote:
>> Jamie NS3T
>> 
>> Highly appreciate that information.
>> 
>> In looking into the current HELP section of Writelog:   the AutoSaveCount parameter should now be in the [ENTRY] part of the .INI file and Not in the [CONFIGURATION] Section.
>> 
>> I took your advice to look into it and ***There is indeed a note that 
>> as of Version 12.29 if such a parameter was in the [CONFIGURATION] 
>> Section it is removed and now placed in the [ENTRY] section***
>> 
>> I am running the very latest Version 12.73F.
>> 
>> Therefore I have simply added In the [ENTRY] section of the .ini file:
>> 
>> [ENTRY]
>> AutoSaveCount=1
>> 
>> Let’s see how this works out.
>> 
>> Thanks !
>> 
>> Keith W3KB
>> 
>> 
>> From: Jamie Dupree <jamie.dupree at verizon.net>
>> Sent: Monday, August 14, 2023 10:01 AM
>> To: Keith Beebe W3KB <keith at w3kb.net>; WriteLog Reflector 
>> <writelog at contesting.com>
>> Subject: Re: [WriteLog] A Learning Experience in the WAE CW Contest
>> 
>> Keith -
>> 
>> You can set Writelog to save your log after every 'x' QSO, so you don't have to rely on the journal file.  I have my log save after every QSO, just in case.  It is done in the background, automatically, and does not cause any problems with my operating system.
>> 
>> This is an old item that I saved on how to do it.  You should check to 
>> see if this has changed over the years
>> 
>> - Paste this line into the [Configuration] section of the writelog.ini:
>> 
>> AutoSaveCount=1
>> 
>> This ensures the log will be saved after every entry. If you don't want it to save that often, just increase the number.
>> 
>> 73 Jamie NS3T
>> 
>> 
>> On Monday, August 14, 2023 at 09:29:41 AM EDT, Keith Beebe W3KB <keith at w3kb.net<mailto:keith at w3kb.net>> wrote:
>> 
>> 
>> 
>> I am a WriteLog contesting software user.
>> 
>> I was operating in the weekend's Worked All Europe (WAE) CW contest and had 110 QSOs and 25 QTCs (Messages) as of early Saturday morning. I had planned to operate all weekend.
>> 
>> All of a sudden there were multiple electrical power "Blips" (rapid On-Off)  that happened.  That "crashed" the computer logging the contest.
>> 
>> When I got back in operation I noticed my 110 contacts were still in the log but my QTC's were not.  What's going on?
>> 
>> I had to drop out of the WAE CW contest because my QTC's were gone and the Writelog software now thought I was back to QTC #1.  Could not realistically send another QTC because the content tracking of the specific messages and their composition plus the QTC numbers were gone.
>> 
>> Writelog does indeed have a safety mechanism for such situations in that it has what they call a "journal" backup file in case things like power outages happen.  It makes a journal of the log during a contest.
>> 
>> However, here's the part of that operation that I missed.  "These changes (QTCs) are Not written to the journal file and Cannot be recovered if you exit or crash without saving your log."
>> 
>> For this specific contest Writelog does not automatically backup QTCs during the logging process.  It recommends periodically Manually saving the log during the contest. Well, I didn't do that and of course along comes the power "blips".
>> 
>> I should have looked closer to Writelog's setup instructions for this specific contest.
>> 
>> At least I now know what happened and now know what to do in the future specifically for the WAE CW contest.
>> 
>> Keith W3KB
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> WriteLog mailing list
>> WriteLog at contesting.com<mailto:WriteLog at contesting.com>
>> http://lists.contesting.com/mailman/listinfo/writelog
>> WriteLog on the web:  http://www.writelog.com/ 
>> _______________________________________________
>> WriteLog mailing list
>> WriteLog at contesting.com
>> http://lists.contesting.com/mailman/listinfo/writelog
>> WriteLog on the web:  http://www.writelog.com/
> 
> _______________________________________________
> WriteLog mailing list
> WriteLog at contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web:  http://www.writelog.com/
> _______________________________________________
> WriteLog mailing list
> WriteLog at contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web:  http://www.writelog.com/