WriteLog
[Top] [All Lists]

Re: [WriteLog] AutoSaveCount

To: "Ian White, G3SEK" <g3sek@ifwtech.co.uk>,<writelog@contesting.com>
Subject: Re: [WriteLog] AutoSaveCount
From: "FireBrick" <w9ol@billnjudy.com>
Reply-to: FireBrick <w9ol@billnjudy.com>
Date: Mon, 26 Jul 2004 06:36:23 -0500
List-post: <mailto:writelog@contesting.com>
http://www.kregli.com/
Check out WllniEdit
It's one of Keith's little 'Reglets' for Writelog.

----- Original Message ----- 
From: "Ian White, G3SEK" <G3SEK@ifwtech.co.uk>
To: <writelog@contesting.com>
Sent: Monday, July 26, 2004 2:10 AM
Subject: Re: [WriteLog] AutoSaveCount


> George wrote:
> >Yes, writelog.ini is the
> >heart and soul of WL.  Unfortuantely, the Help documentation for the 
> >writelog.ini
> >commands is not totally complete, which makes dealing with it even more
> >tricky.
> >
> >I find writelog.ini so important that I even keep a shortcut for it on my
> >Desktop.
> >
> As from two weeks ago, I now back up writelog.ini as carefully as the 
> master station log!
> 
> After trying to make some setup "improvements", I had somehow managed to 
> get the system into a state where the MP locked onto transmit each time 
> WL started up. The Setup Ports menu wouldn't change it, and didn't seem 
> to work right any more.
> 
> The problem undoubtedly lay in the ini file, but it was very difficult 
> to check - and I do know all the ways to look for information (including 
> this list, of course - tnx to everyone who made suggestions).
> 
> The undocumented lines in the ini file seem to be the ones that you 
> shouldn't edit anyhow - they are written by WL for its own information. 
> The rule of thumb seems to be: if a line in the ini file is not 
> documented in the Help file or in K9JY's pages, then don't touch it!
> 
> In case it helps someone else, the cure for my particular problem was to 
> un-install everything from the Setup Ports menu, so that WL is 
> completely cut off from the rig(s). Then save the ini file (Setup / Save 
> Config), close WL, and start up again with a fresh, "blank" contest. 
> Then reinstall the rig to the COM port, and build up the configuration 
> again in small steps. At each step, save the ini file and also use 
> Explorer to copy it to a numbered backup (like 1writelog.ini, 
> 2writelog.ini, which WL will ignore). In my case, WL came up smiling as 
> if nothing had happened.
> 
> But if I'd had an ini backup from *before* those would-be 
> "improvements", I could have been back on the air in five minutes. 
> Lesson learned!
> 
> 
> 
> -- 
> 73 from Ian G3SEK
> _______________________________________________
> 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/

<Prev in Thread] Current Thread [Next in Thread>