Author Topic: Avast! 5.0.462 still blocks Acronis Image Mounting  (Read 5159 times)

0 Members and 1 Guest are viewing this topic.

Offline frg

  • Jr. Member
  • **
  • Posts: 26
Avast! 5.0.462 still blocks Acronis Image Mounting
« on: April 09, 2010, 10:42:43 AM »
Hello,

I have installed Avast! Internet Security 5 on 3 computers, and I have the exact same problem as described previously in this thread:
http://forum.avast.com/index.php?topic=50815.15

These PCs run with Windows XP, and the problem occurs as well with Acronis True Image 9 and 10.

Any suggestion?

Offline pk

  • Avast team
  • Super Poster
  • *
  • Posts: 2078
Re: Avast! 5.0.462 still blocks Acronis Image Mounting
« Reply #1 on: April 09, 2010, 12:01:21 PM »
ok, I can re-test it...
Can you mount those images in read-only mode? What file-system is used in those images, NTFS or FAT32?
Thanks.

edited: tested Acronis True Image Home 2010 (Win7) and works ok with r/o + r/w NTFS .TIB images...
« Last Edit: April 09, 2010, 12:26:35 PM by pk »

Offline frg

  • Jr. Member
  • **
  • Posts: 26
Re: Avast! 5.0.462 still blocks Acronis Image Mounting
« Reply #2 on: April 09, 2010, 01:02:32 PM »
Everything is in NTFS.
I tried in read-only mode.

But I am working with Windows XP, not Seven.

When mounting the image, the whole system hangs, Acronis True Image then appears as "not responding" when checking in the Task Manager window, and when tracing what process is the cause, Acronis sends to explorer.exe.

It is then impossible to soft-reboot, only a hard-reboot is possible, using the reset switch.

I have the exact same behaviour on 2 PCs.

On one of them, I re-installed the image I created (with Acronis), just before installing Avast (Norton Security was then used).

With this "pre-Avast" configuration, I had no problem in mounting an image.

Offline pk

  • Avast team
  • Super Poster
  • *
  • Posts: 2078
Re: Avast! 5.0.462 still blocks Acronis Image Mounting
« Reply #3 on: April 09, 2010, 01:10:08 PM »
I see, would you mind generating kernel dump so we can see why your computer hang? Previous problems with Acronis were caused by NTFS journals, but it should be already fixed.

1) Enable kernel dumps (Start->Run, type sysdm.cpl, go to Advanced tab, Startup & Recovery, choose "Kernel dump"). Howto in more detail: http://msdn.microsoft.com/en-us/library/ff542953.aspx
2) Run regedit.exe, go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\i8042prt\Parameters, create a value named CrashOnCtrlScroll, and set it equal to a REG_DWORD value of 0x01.
3) Reboot
4) Mount the image, when your computer hang, press right CTRL key and press the SCROLL LOCK key twice.
5) Crashdump will be generated in \Windows\Memory.dmp - please compress that file (zip/7z/rar) and upload it to our FTP (http://support.avast.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=18)

Thanks a lot!

Offline frg

  • Jr. Member
  • **
  • Posts: 26
Re: Avast! 5.0.462 still blocks Acronis Image Mounting
« Reply #4 on: April 09, 2010, 02:56:38 PM »
I just finished uploading the file, under MEMORY-FRG.rar, size: 37.4 MB.

Offline pk

  • Avast team
  • Super Poster
  • *
  • Posts: 2078
Re: Avast! 5.0.462 still blocks Acronis Image Mounting
« Reply #5 on: April 11, 2010, 12:27:12 AM »
Thanks for the dump - it was a nice conflict between avast + Acronis True Image which results in deadlock during volume mounting. The issue was already fixed.

Offline frg

  • Jr. Member
  • **
  • Posts: 26
Re: Avast! 5.0.462 still blocks Acronis Image Mounting
« Reply #6 on: April 11, 2010, 09:03:53 AM »
Sorry to sound so "newbie", but "already fixed" where?
Is there a new version that contains that fix?

Offline pk

  • Avast team
  • Super Poster
  • *
  • Posts: 2078
Re: Avast! 5.0.462 still blocks Acronis Image Mounting
« Reply #7 on: April 11, 2010, 09:47:54 AM »
It means, it was fixed in avast source code - new version should be available within 2-3 days, I guess.

Offline frg

  • Jr. Member
  • **
  • Posts: 26
Re: Avast! 5.0.462 still blocks Acronis Image Mounting
« Reply #8 on: April 11, 2010, 10:13:37 AM »
OK, understood.
Thanks a lot!
 8) 8) 8)