chris1341
August 10th, 2009, 08:01 AM
Hi Mike,
I started looking at the early beta's but other commitments meant I could not complete that, getting back to it now. Apologies for that. Fortunately most of ther early questions I was going to post have been answered elsewhere but I'm still not clear on the new caching arrangements. Apologies if it's noted somewhere I've missed.
I always used memory caching but notice this option is gone and I seem to recall it's replaced by some hybrid memory/disc caching type approach. If thats the case is how is that applied? What rules if any decide if a change is written to disc or stored in memory? Is it simply random based on available disc/memory or is it more logical based on type of change? Looking at it it seems to me it's just straight disc caching. If it's not how can you offer a 'save all changes' option?
Any official reason why memory caching is out? Would it be possible to also confirm the page file/hyberfil etc are not cloned as in previous versions?
As if that's not enough (!) I have a few sundry questions also:
Can the splash screen be disabled?
Can you confirm whether the F-Prot AM scans only files saved to the real system in System Safe mode or will it scan anything you save but intend to drop on restart? In System Safe mode is the scan on execution only?
Are the scan logs even for System Safe with all changes dropped retained somewhere, if so where are they and what is noted in them?
How long will version 2 be supported after V3 release?
As usual any help would be much appreciated.
Thanks
I started looking at the early beta's but other commitments meant I could not complete that, getting back to it now. Apologies for that. Fortunately most of ther early questions I was going to post have been answered elsewhere but I'm still not clear on the new caching arrangements. Apologies if it's noted somewhere I've missed.
I always used memory caching but notice this option is gone and I seem to recall it's replaced by some hybrid memory/disc caching type approach. If thats the case is how is that applied? What rules if any decide if a change is written to disc or stored in memory? Is it simply random based on available disc/memory or is it more logical based on type of change? Looking at it it seems to me it's just straight disc caching. If it's not how can you offer a 'save all changes' option?
Any official reason why memory caching is out? Would it be possible to also confirm the page file/hyberfil etc are not cloned as in previous versions?
As if that's not enough (!) I have a few sundry questions also:
Can the splash screen be disabled?
Can you confirm whether the F-Prot AM scans only files saved to the real system in System Safe mode or will it scan anything you save but intend to drop on restart? In System Safe mode is the scan on execution only?
Are the scan logs even for System Safe with all changes dropped retained somewhere, if so where are they and what is noted in them?
How long will version 2 be supported after V3 release?
As usual any help would be much appreciated.
Thanks