Crazy, the dll is loaded from my TeX installation directory??
…TeX\texmf\miktex\bin\msvcr80.dll
I will rename it there and check for changes in reaction of avast.
Crazy, the dll is loaded from my TeX installation directory??
…TeX\texmf\miktex\bin\msvcr80.dll
I will rename it there and check for changes in reaction of avast.
The Error is not displayed after renaming msvcr80.dll to msvcr80.dll.sv
So this dll is the reason for the Error. The TeX dir is in PATH variable so this could be a reason why it is found.
But what should I do now?
The dll is probably needed by at least one program of the MikTeX distribution otherwise it would not be there.
(after rerenaming the dll the error is displayed again)
The fact that it’s in PATH doesn’t explain why it’s loaded there… the modules are loaded by name and avast! doesn’t use msvcr80.dll at all (it uses msvcr71.dll).
I haven’t been following MikTeX lately, but I wouldn’t expect it to load into other processes… it’s mostly a bunch of console apps ![]()
Is there any reference to this particular path (miktex\bin\msvcr80.dll) in registry?
Is there actually any reference to miktex path in registry (except for the main miktex key, and maybe associations like Yap)?
miktex\bin\msvcr80.dll is nowhere in the registry
(msvcr80.dll is found at [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\PatchedComponents] in 2 Keys starting with %windir%\winsxs.…)
as mentioned the MikTeX directory is in the PATH Variable
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment] “Path”
As a brute force method, could you please try searching the whole hard drive for the occurences of files that have the string msvcr80.dll in them?
This should give us an idea about who might be loading it into the avast address space…
I know it’s a bit of a nuisance (and time consuming) - but can be quite effective.
Thanks
Vlk
Here are all occurences for all drives:
Well, I didn’t really mean occurences of the file (i.e. search by file name) but occurences of the string “msvcr80.dll” inside any files (i.e. search by file contents)…
I hope I’m being clear. :-[
Thanks
Vlk
Sorry, did not read well, it is late already. Search will last longer for string search, but it is in progress…
You know what? Let’s first try ListDlls… please simulate the problem once more and than run ListDlls (it’s a command-line tool) http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/ListDlls.mspx and post the output here (you can redirect listdlls’ output to a file by typing something such as
listdlls > out.txt
and than posting out.txt).
Thanks
Vlk
Edit: if the search is already running, no need to abort it, it may be useful as well. ![]()
The listdlls does not finish when Runtime Error is displayed!
It stops the listing. The last lines are
ashDisp.exe pid: 740
Command line: “C:\PROGRA~1\ALWILS~1\Avast4\ashDisp.exe”
But after clicking “OK” the msvcr80.dll is not loaded by ashDisp.exe any longer.
Here is the result of the text search
Interesting indeed… please, one more experiment :-[
When ashDisp.exe is running but the problem has not yet occured (i.e. the Runtime Error window is NOT there yet), please download and run ProcMon http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/processmonitor.mspx
Run the program, and in the Filter dialog, add the following condition:
Process Name is ashDisp.exe Include
This will confine the output only to events that take place inside the ashDisp.exe process. After you confirm with OK, click the Registry and File icons on the toolbar to exclude events related to registry and filesystem activity. The only activity icon that we want to monitor is Process and Thread (that’s the icon with the Windows symbol on it - that one should stay pressed).
Now, simulate the problem. This should hopefully cause some events to get generated (i.e. added to the window) - I’m talking about “Load Image” events here.
When you’ve got the events generated, choose File → Save… and save the output (current filter only) to a file that you can either send to my email address or rename and attach to the forum.
Thanks again for all your help, hopefully we’ll solve this soon ![]()
Vlk
I hope this helps. (full file via mail)
For your information: renaming mozMapi32.dll let the error not appear, too.
I am sure that at least some proportion of avast users are running, as I am, with mozMapi32.dll (as part of Thunderbird) without encountering this error.
For information, it is the Thunderbird 3.0a1 version, not an standard version.
I did some testing and realized that when displaying the information with fileinfo plugin for Total Commander the same error is displayed for totalcmd.exe
And guess what, when displaying DLL dependencies MSVCR80.DLL is displayed!
So I think mozMapi32.dll Version 1.9a2pre: 2007011003 is the error causing dll.
EDIT: After updating the fileinfo plugin to the most recent version the error does not occur any longer!
It may be some confirmation of Quelb’s findings that I receive the C++ runtime error popup in attempting to install Thunderbird 3.0a1.
Since Thunderbird 2 is not yet the production level of the product and version 3 will not be a concern of mine or those I support anytime soon I shall happily leave this issue to Quelb and the avast team.
Nevertheless can anyone explain why the mozMapi32.dll is loaded ???
Hold on, we’re working on it…
It’s sort of a problem in TB (probably worth filing - do you know where to do that?) but we have created a workaround that should prevent it from happening.
The fix will be in the upcoming avast update (due very soon…).
Thanks
Vlk