I have here the similar structure and do prefer keep program files separate
from the data files. Then doing upgrade to the next version is much easier
and all the files are easy to find and sort. Just leave it the way it is. It
is much more flexible this way and therefore in tune with the rest of the
TRlog philosophy. As soon as you put the path to tr.exe into autoexec.bat
you can organize all your data files the way YOU want.
>I like to keep the data separate from the executables, and use
>a simple tree structure. I'll probably continue to organize all
>of my TR-Log files as follows:
>
>
>c:\log -- nothing but TR executables, help files, and ROMASTER.DTA
> (my own TRMASTER.DTA made from my own contest QSOs only.)
>
>c:\contest -- root level contest data directory
>
>c:\contest\1998 -- a subdirectory for each year...
>
>c:\contest\1998\sscw98 -- and a subdirectory for each contest...
>
>c:\contest\1998\sscw98\logcfg.dat ...
>.
>. (individual files for that contest...)
>.
>c:\contest\1998\sscw98\restart.bin ...
>
>
>I find that this scheme helps me with backups, archiving, and browsing.
>I suppose everyone has their own favorite way of doing this. The new
>scheme might help those just getting started.
>
>-Kirk K4RO
>
>--
>FAQ on WWW: http://www.contesting.com/trlogfaq.html
>Submissions: trlog@contesting.com
>Administrative requests: trlog-REQUEST@contesting.com
>Problems: owner-trlog@contesting.com
>Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
>
>
--
FAQ on WWW: http://www.contesting.com/trlogfaq.html
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
|