Avast Home ACT! winmm.dll

When I have AVAST loaded, then try to open ACT! database software, ACT! crashes with “winmm.dll” message.

If I disable AVAST through msconfig, restart & open ACT!, ACT! is fine.

Closest I can come on ACT! site mentions Hawk Script Blocker as an ACT! problem.

Any ideas?

A few questions:
What version of avast! do you have? Home or Professional?
What operating system do you use?

Does it help when you only stop some of the resident providers (e.g. Standard Shield, or Script Blocker is you have Pro version) instread of disabling the whole avast?

What’s the exact crash message?

And one more from me: is this somethin new in the latest build (412) or was it happening before? Or you’ve just installed the program for the first time so you don’t know?

Thanks
Vlk

Just installed Avast Home a couple of days ago after uninstalling Norton IS.

Version 4.1 Home Edition
Build April 2004 4.1.412

OS = WIN98SE

Can’t remember the exact ACT! crash message. I think it is an IPF in winmm.dll.

Theres your problem i’m betting… Norton seldom uninstalls… Check their support area, they have a 200 step process to ensure its fully removed from your system and registry. Sadly, its basically a requirement with that product…

Right, you should try disabling/uninstalling avast before claiming that it is actually causing the problems…

Thanks.
Vlk

He DID disable avast and found that the problem did NOT occur. At least that’s what he said in his post.

I have…

  • Uninstalled & reinstalled Avast
  • Uninstalled & reinstalled ACT! using a new (empty) database
  • Defragged several times
  • Scandisk’ed several times
  • Tried all possible permutations of ACT!, Outlook Express & Avast in my start up config system
  • Repeatedly compacted all folders in Outlook Express
  • After compacting, scandisk indicates “The last-modified date or time for the file or folder was invalid.” in one to many folders

Based on my experiments, I believe that there is either

  • a date/time hook that runs between these 3 programs with winmm.dll as a bridge that can’t operate fast enough between the 3
  • I don’t have enough memory to have them load simultaneously

The winmm.dll crashes

  • if I load ACT!, OE & Avast simultaneously
  • if ACT! is trying to cope with time-based alarms

So, if the problem is repeatable, what is the exact crash message?
Does it help when you only stop some of the resident providers (e.g. Standard Shield) instead of disabling the whole avast?

Crash messae =
This program has performed an illegal operation and will be shut down.

ACT caused an Invalid Page Fault in module winmm.dll at 017f:bfdf6633

It’s some kind of heap corruption…

Does it help when you only stop some of the resident providers (e.g. Standard Shield) instead of disabling the whole avast! (and then start ACT)?