Why does it keep creating so many temp files starting with JET. Is it not possible for the program to clean these out after use. The temp folder is going to fill up very quickly with all these.
It also creates its own temp subfolder and then not uses it to keep them. They go in the main temp folder and the subfolder is left empty. Why is this.
If the program used the subfolder it created to dump its temps then it would be easy to clean them out every week or so with a single folder delete. Can a path be changed somewhere to rectify all these happenings
The Jet* files are created by Microsoft Jet drivers (used by avast!). If they are left in the TEMP file, I suggest to update these drivers (downloadable from Microsoft as MDAC package).
Or, if you have avast! 4 Home, you may switch the avast! database from ODBC to XML - that will prevent avast! from using these drivers (in \Data\avast4.ini, change the line Database=ODBC into Database=XML).
Oh you can make it…
But there are a lot of applications that do it for free: BeClean, Internet Sweeper, etc.
You can Google or find some hints into ‘Links’ in my signature
Why Igor ? Can you please explain this little bit closer ? I’m running avast! Pro and I’ve always had avast! storage set as XML inside my avast4.ini file. I really never had any visible problems, although I don’t know what’s happening in background… that’s why I wonder why is not a good idea to switch from ODBC to XML if you use Pro version…
Yes, XML storage doesn’t make it possible to store results of previous sessions.
Appart from that, Enhanced User Interface behaves “strange” when switched to XML storage - when a task is started, another instance of it appears in the list (of the tasks, not of the corresponding sessions!). I must admit I didn’t explore the problem deeper yet, so I’m not sure if it’s a bug or just something caused by the inability to store additional info in the storage - but simply said, XML storage is currently considered just a backup option for avast! Home.
