This content has been marked as final. Show 11 replies
I found similar results with my testing.
I found it better too..
BUT whenever I run ODS howver small i set the cpu util option to use it always seems to come back to 50%..... is this just me?
I've had similar results. Mem usage for mcshield.exe is typically at or below 20MB. I was also encouraged to see that McScript_InUse.exe peaked at 50% cpu during a dat update instead of 100%. McScript_InUse still spikes mem usage up pretty high. But it seemed to be a very brief spike for an incremental dat update. It's probably pretty difficult to avoid that mem spike during an update.
The McScript_InUse.exe still using 99% cpu & >120mb ram during update, and keep there for over a minute, it really disturb other processes e.g. freeze of playing video.
Same behavior here, DAT update still kills the computer which is a problem on 24/7computers and prevent us from deploying DATs to the general population as soon as they're available, have to wait during off hours.
Let us know if this helps.
I checked in the new VS 8.7 Patch 1 in EPO today and i agree to most of the people, it's a lot faster.
The memory usage is nearly half than before. Most of our workstations also had the problem that a Windows start (WinXP SP2) tooks 3-5 minutes from login screen to desktop.
That problem is now also fixed (login now takes 20 to 30 seconds wich is ok).
So I can recommend to update asap.
How to fix problem when logon?
Could you explain this for everybody here?