On Fri, 18 Dec 2009 13:10:58 -0800, Jeff Liebermann
wrote:

On Fri, 18 Dec 2009 15:48:15 -0500, John Ferrell
wrote:

I prowled around the registry without anything looking interesting.
Upon examining the folder containing the tlw3.exe file I found a file
"TL.DEF" which I replaced from with the one from the working backup
machine and all is well!
I will now return to my matching studies...

Thanks for the help,
John Ferrell W8CCW

Nicely done. TL.DEF is created when you first run TLW. I assumed
wrongly that the settings were saved in the registry. It would have
been messy to fix if they were because uninstalling most programs
preserves the user settings in the registry. When you reinstall, the
problems just return.

I suppose the uninstall program was leaving the TL.DEF file and the
folders intact in the same manner. The problem remained after an
uninstall-install sequence. I simply removed the corrupted copy from
my laptop and a new TL.DEF file was created on the next execution.

My personal preference would be to always operate this way. Keeping
the parameters & execution info in the programs subfolder makes it
possible to sanitize as required.
Thanks again!
John Ferrell W8CCW

John Ferrell wrote in
:

I simply removed the corrupted copy from
my laptop and a new TL.DEF file was created on the next execution.

My personal preference would be to always operate this way. Keeping
the parameters & execution info in the programs subfolder makes it
possible to sanitize as required.


Fortunately a lot of coders now agree. I think the infatuation with the
registry is declining. What's really weird is that in *nix systems, BSD
and Linux etc, that have different filing subsystems, it's not common
practise to put related config files in the base dir for the executable, so
arguably they'd have more use for a common registry than Windows does but
they don't have one. Life is strange... On the other hand, BSD and all do
tend to use human-readable and editable configs more so it's easier to change
things and back them up reliably while the program isn't running.