Hello All, Hi Two separate users, one of whom is me, using two versions viz 10.36G and 10.35x have failed to disable autosave by the prescribed method. Surely there is a problem. Wayne? Yes indeed, a
I did a search in the Writelog archive. Does the following answer the question? ** For autosave, WL only offers one configuration option: you can tell it the maximum number of QSOs that can be in the
Steve, 1) What value did you set for AUTOSAVECOUNT, 2) are you sure you typed the parameter name correctly, and 3) what was the CPU speed and memory of the machine(s) in question. At 8P8P we did over
There are clearly some unexplained differences between experiences here, and from my personal perspective they are *not* related to computer speed or RAM. Steve experienced the problem as described,
For those of you who may be reluctant to disable AUTOSAVE, remember that WL journalizes QSOs in a separate ascii file. If WL terminates before the log is saved, it will automatically prompt you about
First of all, bear in mind that WL writes the entire log file to disk every time it does a save. The only way to avoid this would be a complex record I/O system that would take Wayne a lot of time to
snip Such is true. However, I think I have a work around, at least I never run low on memory. What I do is take control of Virtual Memory, and set it to a value of High and Low to 384. Think I got th