I have run into an issue with IS5, which prevents using AMD CodeAnalyst completely (profiling fails to start). (codeanalyst can be located for free at
here)
I have pinpointed the conflicting module to be AvastSvc.exe, which does not turn off even when all shields are turned off. When I shut down AvastSvc.exe (via services panel) profiling starts to work again.
This is happening on AMD X2 4400+ proc /w 4GB mem running WinXP x64.
Any idea what might be the root cause and what might be done to make both software live peacefully together? Something in IS5 core module is preventing talking to the AMD profiler driver.
