Yet another option that works here:
Edit the .DOM file, save it under the original name, then WRITE PROTECT it.
I've used this technique for the JIDX (or was it KCJ?) and CQP for the past
several years to correct similar annoyances. It works, but with the
unwelcome side affect that a program update complains that it cannot
overwrite the file when the new version is unzipped. Just say "NO" to
overwriting the few .DOM files, and everything remains fine. Keep backup
.DOM files in a subdirectory, just in case you mess up and accidentally
overwrite the edited version.
Of course, we haven't had this "problem" with updates for quite some time
73 de Bob, K6XX
We probably should e-mail these edited files to Tree, so he can include them
in the next release...
> -----Original Message-----
> From: email@example.com
> [mailto:firstname.lastname@example.org]On Behalf Of VR2BrettGraham
> Sent: Wednesday, March 23, 2005 6:11 AM
> To: email@example.com
> Subject: Re: [Trlog] customised files - was: Re: RUDX Contest Bug?
> DL2ZAV suggested:
> >put your customised files using the original name (i.e. RUSSIAN.DOM)
> >into your working directory from where you operate the contest, which
> >hopefully should override the one with the same name installed
> into C:\LOG
> Seeing how Tree sometimes slips old CTY.DAT files or
> whatever into new releases, I think it better to make a
> new .DOM file with a different file name for busted
> ones like RUSSIAN.DOM.
> Otherwise, next release when unZIPed replaces one's
> fixed .DOM file with the busted one & problem returns.
> The potential for disaster I suspect increases if one has
> to keep track of which files are which in which subdirectories.
> No matter how you go about it, one thing is for sure: the
> original .DOM file needs fixing. The default one for ARRL 10m
> is also screwed up - or was at some point... I've forgotten, as
> I just fix them & get on with operating. ;^)
> 73, VR2BrettGraham
> Trlog mailing list
Trlog mailing list