Closed Bug 161852 Opened 23 years ago Closed 23 years ago

ActiveX Plugin fails if VC++ runtime not in end user's computer

Categories

(Core Graveyard :: Embedding: ActiveX Wrapper, defect)

Product:
Core Graveyard
Component:
Embedding: ActiveX Wrapper
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED WONTFIX

People

(Reporter: bamm, Assigned: adamlock)

References

(
URL
)

Details

Using the fresh npmozax.dll created as attachment 83363 [details] viewable from Bug 143722, I get the following error when opening ActiveX enabled sites such as www.inq7.net. The dynamic link library MSVC60D.dll could not be found in the specified path C:\WINNT\System32;C:\WINNT\System;C:\PROGRA~1\mozilla.org\Mozilla; C:\WINNT\System32\Wbem. However, this error does not occur on my home computer, a Win98 box that has MS Visual C++ installed.
That should have been MSVCP60D.dll, missed the 'P'.
Summary: ActiveX Plugin fails if VC++ runtime not on end user's computer → ActiveX Plugin fails if VC++ runtime not in end user's computer
The error message box is not themed, therefore it was generated by either the OS or the plugin and not by Mozilla.
Yes, the plugin will fail if you're missing DLLs. See here to get them: http://www.iol.ie/~locka/mozilla/plugin.htm If the plugin had an installer it would do this, but it doesn't. BTW the 'D' in the "MSVC60D" means you have a debug npmozax.dll which you shouldn't be using distributing anyway.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
Ok. Would you mind if I make an installer for it that includes the missing DLLs? Is there a list of all its dependencies? If yes, would you prefer Wise, Installshield or XPI? Thanks for a great plugin. Verifying Wontfix.
Status: RESOLVED → VERIFIED
Mozilla has it's own installer in mozilla/xpinstall. That would be the preferred approach since it supports the usual installer like things and is open source. Docs are here: http://www.mozilla.org/projects/xpinstall/ AFAIK it would involve writing an install.js script, and zipping it up with npmozax.dll, MozAxPlugin.class, nsIMozAxPlugin.xpt and other dependent DLLs into an XPI file. This can then be put up on a website as an URL (for point and click installation in Mozilla) or bound to the stub installer exe. Please raise a bug to cover the issue and CC me to it. Preferably I'd like to see this appear as a new build target in the plugins Makefile.
Filed Bug 164610.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.