magarner
asked on
MPR.DLL Error
I am working to install an application that was originally written for Windows 95 on a Windows XP machine. I have had several problems but with some work and help from other experts I have made my way through most everything. When I try to install the application I get the error that a specified module can be found. Through some other experts help I have downloaded dependecy walker and determined where the error is.
There error is in the MPR.DLL specifically with the function WNetRestoreConnectionA. I get the error - Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.
Now originally I thought that the application I am trying to install was looking for this function and it just wasn't going to work. However I have now come to realize that if I run dependecy walker on just the MPR.DLL I still get the error. This tells me it has nothing to do with my app specifically but instead this DLL. I have even run dependecy walker on other XP machines MPR.DLL and get the same results.
It is critical for our business that I get this app to run on XP otherwise I will have to contract someone to write a new app. Any help or direction is appreciated
There error is in the MPR.DLL specifically with the function WNetRestoreConnectionA. I get the error - Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.
Now originally I thought that the application I am trying to install was looking for this function and it just wasn't going to work. However I have now come to realize that if I run dependecy walker on just the MPR.DLL I still get the error. This tells me it has nothing to do with my app specifically but instead this DLL. I have even run dependecy walker on other XP machines MPR.DLL and get the same results.
It is critical for our business that I get this app to run on XP otherwise I will have to contract someone to write a new app. Any help or direction is appreciated
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Have you tried running the install with Windows 95 compatibility mode?
ASKER
The install program is a .msi. I do not have that option. I think you can only do that with .exe. Unless I am wrong.
Hmm no I don't think you can with an .msi either.
Makes me kind of wonder if it's looking for old VB runtimes or something.
Would be nice it at least told you which module was missing.
Do you know what complier they used to write the program?
If you can find out if it was created using Visual Basic or Visual C++ etc., and what version you might be able to locate the old runtimes for those versions and see if that fixes it.
Makes me kind of wonder if it's looking for old VB runtimes or something.
Would be nice it at least told you which module was missing.
Do you know what complier they used to write the program?
If you can find out if it was created using Visual Basic or Visual C++ etc., and what version you might be able to locate the old runtimes for those versions and see if that fixes it.
ASKER
Unfortunately I do not know the answer to that. I have pieced together everything so far - there is no supporting documentation nor is there source code. I know the .msi is trying to intall 2 .ocx programs that is all I can gather.
Hmm since it's an MSI, you might try enabling Windows Installer logging. Then after running the install again, look at the log for any clues.
http://support.microsoft.com/kb/314852/
http://support.microsoft.com/kb/314852/
ASKER
OK - I got it to create the log - per MS I turned on all options to start. Any ideas what I should be looking for it is a huge log file. Or should I turn of some of the options?
We are probably only worried about error messages so could disable all but them. There is a also a nice log anyalyzer that might be useful to find where the problem is.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/wilogutl_exe.asp
If you don't want to download the Platform SDK to get that tool, you could upload the log file to the web, provide a link, and I can analyze the log.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/wilogutl_exe.asp
If you don't want to download the Platform SDK to get that tool, you could upload the log file to the web, provide a link, and I can analyze the log.
ASKER
I will try the analyzer but I turned everything off except - 'e' and this is what I got.
gging started: 12/13/2006 15:38:06 ===
Error 1904. Module C:\Program Files\Vertex\utils\geo.ocx
Error 1904. Module C:\Program Files\Vertex\utils\qsut.oc
=== Logging stopped: 12/13/2006 15:38:19 ===
gging started: 12/13/2006 15:38:06 ===
Error 1904. Module C:\Program Files\Vertex\utils\geo.ocx
Error 1904. Module C:\Program Files\Vertex\utils\qsut.oc
=== Logging stopped: 12/13/2006 15:38:19 ===
Well, if those ActiveX controls are needed for the program to work...then that would explain the problem.
HRESULT -2147024770 I believe is a missing module error, which most likely means someone those .ocx files are dependent on is missing.
You could try running Dependecy Walker on those .ocx files and see what you find out.
HRESULT -2147024770 I believe is a missing module error, which most likely means someone those .ocx files are dependent on is missing.
You could try running Dependecy Walker on those .ocx files and see what you find out.
ASKER
When I run either one through Dependency Walker I get the same message. Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module. The Module that is highlighted it MPR.DLL. I am stuck in a vicious circle.
Well, the MPR.dll might still actually be the problem. It's possible that those .ocx actually do need the delay-load function. I unfortunately have no idea.
Most likely those just need some function in a dll that doesn't exist in XP.
Wish I could help you out a little more, but I'm at a loss of what to do next.
If you aren't ready to have a developer write a new program, you might consider running Virtual PC with Windows 95 just to run that application. Especially since Microsoft made Virtual PC free.
http://www.microsoft.com/windows/virtualpc/default.mspx
Most likely those just need some function in a dll that doesn't exist in XP.
Wish I could help you out a little more, but I'm at a loss of what to do next.
If you aren't ready to have a developer write a new program, you might consider running Virtual PC with Windows 95 just to run that application. Especially since Microsoft made Virtual PC free.
http://www.microsoft.com/windows/virtualpc/default.mspx
ASKER