• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Hansworst

  • Rank
    New Member
  1. Mamutu updated to 2011-04-21 08:27: Mamutu 3.0 (revised) Main application - But there's no changelog on the blog: http://changeblog.emsisoft.com/ Can someone post the changelog?
  2. Ok I tried this now and it still takes three minutes, looking at Noobie's post, it doesn't seem like a conflict with 3rd party software.
  3. Yes, I've excluded them from each other, but it makes no difference. I've got a notebook which is a few years old, with a 2GHz dual core processor, RAM upgraded to 4GB and HDD upgraded to 7200 RPM, so it's quite fast. I keep it quite lite with only the neccesary processes at startup and not many services, it boots quite quickly and during those 3 minutes the HDD led light is almost off the whole time and CPU usage is 20-30% in the beginning and about 0% for the major part of the 3 minutes, so I don't think it has to do with slow computer and/or to many things to start. I'll try booting with all startups and non-MS services disabled later to be sure.
  4. Hi, Since somewhere in february, I think after a program update for Mamutu, Mamutu starts much slower on my computer. When everything is loaded and ready it still takes 3 minutes for the Mamutu icon to pop-up. Mamutu.exe is running though, but it doesn't seem to be working, as there are no pop-ups for starting a program that would normally cause a pop-up and the process can easily be killed with task manager. Starting Mamutu from Windows start menu doesn't do help either, as the process is already running, only thing that works so far is wait 3 minutes for it to finally work or kill mamutu.exe first and then start it from start menu. After that it does work and killing the process from task manager is no longer possible. This is on Windows 7 x64 Ultimate english. EDIT: Other running security software are Eset Smart Security 4.2 and Prevx 3.0 but neither contains a behaviour blocker or HIPS, so they shouldn't conflict and all 3 were running together peacefully before this problem arrived.