Since upgrading to an ASUS P8P67 Deluxe motherboard and a Windows 7 Ultimate 64 bit system. Directory Opus (Version 9.5.6.0) frequent stops with an Event 1000 Application error which describes the faulting application as dopus.exe version 4.0.2.28 and the faulting module as ADIST64.dll_unloaded.
I attach a Word document containimg the relevant details.
Can anyone please offer any advice on how to resolve this problem?
ADIST64.dll isn't part of Opus - a quick google suggests it might be part of Adobe Reader, so you could try un/reinstalling that.
FWIW, I found a thread about a similar crash in Explorer caused by ADIST64.dll:
social.technet.microsoft.com/For ... ab90a65eef
ADIST64.dll seems to be something to do with Adobe, though I'm not sure what and don't have it on my own machine.
An error involving ADIST64.dll_unloaded means that the DLL did created some Windows objects (probably a window or some kind of hook) which pointed to code inside the DLL, but then the DLL allowed itself to be unloaded by the process it was in (dopus.exe in this case) without destroying those objects. So when something triggers the user of those objects, the OS tries to call code inside the DLL that isn't there anymore.
To translate that into non-tech speak, there's a bug in ADIST64.dll 
Can you find where ADIST64.dll is on your system and work out what it's a part of? If the directory it's in doesn't make it obvious, try right-clicking the DLL and opening Properties, then look on the Details tab.
If you can find out what it's part of, updating that application/component might solve the problem.
Chances are it is part of a shell extension (e.g. something that adds right-click context menus to certain file types). If so, and if you can determine which one it is, you could tell Opus to ignore it. The ShellExView tool is useful for seeing which shell extensions are on your machine and which DLLs each one is coming from.
(Note that disabling things using ShellExView does not affect Opus 9; Opus has its own separate way to disable things. That said, Opus 10 will also respect the method ShellExView uses when it's released soon.)
[quote="leo"]FWIW, I found a thread about a similar crash in Explorer caused by ADIST64.dll:
social.technet.microsoft.com/For ... ab90a65eef
ADIST64.dll seems to be something to do with Adobe, though I'm not sure what and don't have it on my own machine.
An error involving ADIST64.dll_unloaded means that the DLL did created some Windows objects (probably a window or some kind of hook) which pointed to code inside the DLL, but then the DLL allowed itself to be unloaded by the process it was in (dopus.exe in this case) without destroying those objects. So when something triggers the user of those objects, the OS tries to call code inside the DLL that isn't there anymore.
To translate that into non-tech speak, there's a bug in ADIST64.dll
Can you find where ADIST64.dll is on your system and work out what it's a part of? If the directory it's in doesn't make it obvious, try right-clicking the DLL and opening Properties, then look on the Details tab.
If you can find out what it's part of, updating that application/component might solve the problem.
Chances are it is part of a shell extension (e.g. something that adds right-click context menus to certain file types). If so, and if you can determine which one it is, you could tell Opus to ignore it. The ShellExView tool is useful for seeing which shell extensions are on your machine and which DLLs each one is coming from.
(Note that disabling things using ShellExView does not affect Opus 9; Opus has its own separate way to disable things. That said, Opus 10 will also respect the method ShellExView uses when it's released soon.)[/quote]
Many thanks to your response. I have searched my entire PC and established that a single copy of ADIST64.dll exists in the Adobe Acrobat 9 Program Files (x86) folder used by my Adobe pdf reader. It puzzles me as to why Directory Opus should wish to connect with a dll used exclusively for a pdf reader? Nevertheless, I shall use your advice to try to get Opus to ignore it and will report back with my findings.
Adobe Acrobat installs a shell extension that file managers like Explorer and Opus -- and also any program that displays a File Open window -- will load.
I'm not sure exactly what this shell extension does, but Adobe Reader (not Acrobat) installs an extension which generates thumbnails for PDF files, for example.
[quote="leo"]Adobe Acrobat installs a shell extension that file managers like Explorer and Opus -- and also any program that displays a File Open window -- will load.
I'm not sure exactly what this shell extension does, but Adobe Reader (not Acrobat) installs an extension which generates thumbnails for PDF files, for example.[/quote]
I was using Adobe Acrobat 9 Pro and after looking at the Adobe web site I find that a new Reader called Adobe Reader X does everything I need and the Pro version is not required. I uninstalled Acrobat 9 Pro and ADIST64.dll went also. I installed Adobe Reader X and found that the installation does NOT include ADIST64.dll. Moreover, Opus now works without a hitch so my problem is solved - it was definitely ADIST64.dll that was causing the problem.
Many thanks for the assistance.
Glad it's fixed.
Adobe Acrobat Pro is definitely overkill if you just want a PDF reader.