tangent
IPCT Contributor
- May 12, 2016
- 4,606
- 3,957
Even though it's a 32bit plugin, I've often seen it installed in Program Files not Program Files (x86)
There are a bunch of things you can do to bend plugins to your will. I've done many of them over the years, but I've forgotten what works and what doesn't on the camera plugins.
Some thoughts/ideas:
mozilla based browsers check a whole bunch of different locations for browser plugins. There are a bunch of locations that may have /plugins directories as well as a bunch of registry keys used to point to plugins. Plugins that aren't in specific folders the browser checks are found by an environment variable or registry key.
This is a bit old, but you get the idea: Plug-in Basics
The Dahua plugins put a registry key at HKLM\SOFTWARE\Wow6432Node\MozillaPlugins\...
Before you go mucking up your registry or parts of your registry, export a backup of relevant settings.
If you look at other plugins in your registry (non-camera), you'll notice some of them do some things a little differently defining multiple mime types or defining multiple versions and pointing them to the same file. If I remember correctly it's possible to make some similar registry changes to improve compatibility of the plugins. Changes may also be required to a manifest file in the plugin directory.
You can also merge some of the files from different plugin installations together (add missing files) but that may not work.
It's possible to use userscripts to alter a webpage (greasemonkey), and do things like change the plugin detection code that runs on the webpages for certain devices.
Even if you can gain some additional functionality making some tweaks like this, it's likely you'd discover some things don't work right.
Last edited:
