>On Thu, 22 Jun 1995 14:27:53 -0700 (PDT) Brian Smithson wrote:
>>I would really like it if the World Clock application on the Zoomer
>>would remember settings like `home', `destination', etc., between
>>shutting it down and re-starting it. Any simple answers on this ?
>
>It does, unless you remove the state files (specifically,
>"B:/GEOWORKS/PRIVDATA/STATE/WCLOCK__.000" or "wclock app (transparent)" to
>GEOS).
>
>State files are removed after a hard reset (which removes everything) or
>after a soft reset (which removes certain files, among them are the state
>files).
>
This has not been my experience using the Expert+ .ini settings and
(with, I think, related issues) the reason I don't use all of those
settings. When you close down an application completely, as you must
do when launchModel = 3 (and possibly any value other than 0 -- I
haven't checked too thoroughly) to load other applications, that
application will not write out a state file, nor will it read the
state file when it resumes. Use of state files with launchModel = 3
only occurs when Geoworks itself is restarted, as in after a complete
shutdown or some use of a DOS program. So, World Clock loses all of
its settings, and other programs which save options only in state
files (which seem like most of the built-ins) come back with their
defaults.
I have implemented another list member's suggestion on my system:
when I have the settings correct, I execute a .BAT file which copies
the state file to a subdirectory. When I want to reset the clock, I
first run in, then run another .BAT file which copies the saved state
file back into the /STATE directory, and when Geoworks comes back from
DOS, the World Clock app reads that file when it restarts. Note that
you can't just copy the file into the /STATE directory and then start
the clock: the system knows that it is not being restarted and so it
comes up clean.
Some of the above is a guess. I've seen some explanations of what the
various "launch" and "level" .ini settings do, but they weren't
completely clear and I'd love to have the real info.
Finally, I'm still trying to get GeoCalc to run and encountering that
"incompatible release" problem. Can anyone help?
Thanks,
Bill
smith@io.dsd.litton.com