I decided to open a new thread here, because I am also struggling with this issue in Windows 98 for now and I am using the most current non beta version. So I thought it would be a good idea to reopen the thread in the official version forum.
Currently I am using the workaround to stop the provider from the right-mouseclick menu to store the settings and then reboot.
I also observed the “settings not stored” issue after switching from ODBC to XML.
So in first place someone would ask: Why not use ODBC? Simple Answer: When using ODBC, it is impossible to do a defragment in Windows 98. The .mdb file is accessed like mad and windows 98 defrag doesn’t like that. It keeps restarting all the time… Pretty uncool to be honest.
After switching to XML it got a lot better. Still some frequent access to avast4.ini… But slow enough to let the defrag start. I think its unnecessary to read avast4.ini that often. I think once at program start is enough… Also Mark Russinovich from Sysinternals at a symposium last year mentioned some antivirus programs which keep reading the same setting-files over and over and cause the system to slow down slightly. We don’t want to play in that league do we?
Maybe alwil is using avast4.ini as a kind of communication medium… Looking for changed settings… Maybe has something to do with ADNM… hmm… sorry, but I don’t like this frequent access… no matter if its fast from ram or not.
Remark: I didn’t try the beta 4.5.529, so I cannot comment on that.
When using ODBC, it is impossible to the a defragment in Windows 98.
Pure nonsence. Run defrag while in safe mode.
Sorry, but before using avast it was no problem to defrag in normal mode. It is really the ODBC access which prevents defrag. For me this is unacceptable and there is no excuse. Sorry.
I only said that it is possible to run defrag in safe mode and that it will work despite the settings in Avast are set to ODBC. That is 100% sure.
He never said that he was running defrag while in normal mode (which in general isn’t advised to do anyway on 9x or ME systems)
But lets see if we can help this person. If I remember correclty there is a post somewhere on this board from someone who found a solution to a simulair problem. Trying to find it as we speak.
Sorry for quoting myself, but maybe someone did not read my whole message…
I did manage to save the settings using the workaround from the FAQ. After using the workaround the settings are saved. But rebooting windows without the workaround does not save settings. So at least in the release version the issue still exists.
Yes thats right. I am currently using the workaround with the right mouseclick on the avast icon and then stopping all providers and reboot.
VLK: I also noticed another “issue”. When switching to XML, the avast4.xml does not get generated automatically. I had to open the avast4 main application first and then go to settings. After exiting the settings of the main application, avast4.xml was created.
I knew I had seen it somewhere. ;D