R
Richard Steinfeld
I need a program that will show which programs on my system are making
calls to a specific .dll file, and will reveal the specific directory
where that call is going to.
-----------------------------------------
The problem is that there are three different versions of msvcrt.dll on
my system. I'm running Windows ME.
I just installed GanttPV.
The program won't load. I get the message:
"GANTTPV has caused an error in msvcrt.dll"
It is probable that GanttPV installed a new version of this file in my \
Windows\System\ directory because a new version of GanttPV has come out
within the last few days, and there's a version of msvcrt.dll in my
\Windows\System\ directory. This msvcrt.dll is dated 30 July, 2005 (14
days ago!).
I've got a much older version residing in \Windows\System32\, as well as
yet another version in a directory of program files specific to my printer.
Microsoft's web site references compatibility problems with this .dll,
but their error string example is not identical to "...an error in
msvcrt.dll." The string that they reference is "...has caused a page
fault in msvcrt.dll." Their situation examples are different enough for
me to have concerns about proceeding with their "fix." That's because
their "fix" can't be reversed.
Any good ideas?
Richard
calls to a specific .dll file, and will reveal the specific directory
where that call is going to.
-----------------------------------------
The problem is that there are three different versions of msvcrt.dll on
my system. I'm running Windows ME.
I just installed GanttPV.
The program won't load. I get the message:
"GANTTPV has caused an error in msvcrt.dll"
It is probable that GanttPV installed a new version of this file in my \
Windows\System\ directory because a new version of GanttPV has come out
within the last few days, and there's a version of msvcrt.dll in my
\Windows\System\ directory. This msvcrt.dll is dated 30 July, 2005 (14
days ago!).
I've got a much older version residing in \Windows\System32\, as well as
yet another version in a directory of program files specific to my printer.
Microsoft's web site references compatibility problems with this .dll,
but their error string example is not identical to "...an error in
msvcrt.dll." The string that they reference is "...has caused a page
fault in msvcrt.dll." Their situation examples are different enough for
me to have concerns about proceeding with their "fix." That's because
their "fix" can't be reversed.
Any good ideas?
Richard