Closed Bug 421820 Opened 14 years ago Closed 9 years ago
New Microsoft Windows Media Player 11 plugin is only installed for the system default Firefox version
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b5pre) Gecko/2008030904 Minefield/3.0b5pre While trying to check the fix for bug 393845 with attachment 278687 [details] I noticed that I don't have the needed new WMP 11 plugin installed on my system. I had to manually install the plugin over the Plugin Finder Service. The setup quits with success and the plugin is listed within the software list. After reloading the page with the attachment, restarting Firefox, or even restarting Windows the plugin isn't started and Firefox cannot play the movie. Instead I get presented the Plugin Finder Service again. The list of plugins under the Add-ons manager doesn't show the newly installed plugin. Even the registy doesn't list the plugin under HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins. Only Silverlight and WPF exists there. So I'm not sure if this is our fault or the plugin isn't installed correctly. Setting this bug as major and asking for blocking1.9.
I used following URL to install the plugin: http://port25.technet.com/archive/2007/04/16/windows-media-player-plug-in-for-firefox.aspx As I read on http://kb.mozillazine.org/Windows_Media_Player#Installing_the_new_plugin the installer copies the np-mswmp.dll into the Firefox installation directory. Does it have trouble to detect the correct one - when using a nightly build or a custom set folder?
works for me on Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4, as talked on irc, it seems that the plugin is only for firefox and not "minefield". So i don't think its blocking here and maybe this bug is invalid because its a specific plugin issue.
Ok I did some tests and I found the reason why it happens. The installer checks if Firefox is installed on the system by searching for "Mozilla Firefox" under HKEY_LOCAL_MACHINE\SOFTWARE\Mozilla\. It does not detect Minefield as a Firefox installation and silently stops the installation. I installed Firefox 3 beta4 rc2 to have a test with an official release. Starting the installer afterwards correctly installs the plugin into the sub folder of the Firefox installation. So the installer will definitely work. => Remove the blocking1.9 flag and updating summary.
Summary: New Microsoft Windows Media Player 11 plugin does not work / not detected → New Microsoft Windows Media Player 11 plugin cannot be installed if only nightly builds are installed
(In reply to comment #2) > So i don't think its blocking here and maybe this bug is invalid because its a > specific plugin issue. It's a plugin issue, yes. But I'm not sure if we should close it immediately. The way of how this plugin is installed doesn't seem to be correct. Why it is not installed in a seperate folder and linked here: HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins Any chance to inform Microsoft so that they can enhance their WMP11 plugin installer?
This will also affect multiple installations of Firefox. Only for the default version the plugin will be installed at the moment.
Summary: New Microsoft Windows Media Player 11 plugin cannot be installed if only nightly builds are installed → New Microsoft Windows Media Player 11 plugin is only installed for the system default Firefox version
This issue makes it difficult for new users to decide whether to jump to FireFox3 leaving FireFox2 installed. At first glance it looks like FireFox3 is broken and doesn't play a whole bunch of videos, users will then opt to go back to FireFox2.
Ok, lets return to this issue. As what I've seen lately, it's easy to get the wmv plugin working with any installed development build of Firefox. You only have to perform the following steps: 1. Use the official installer to get the plugin installed for your Firefox version. 2. Copy the file "np-mswmp.dll" from within the plugins folder to "c:\Program Files\Windows Media Player\Plugin\np-mswmp.dll". You have to create the Plugins folder manually. 3. Download and run this attached registry file. If you are using another shared folder update it within the registry file first. After a restart your development builds should also play MWV content now.
Attachment #356704 - Attachment description: Temporary registry patch for wmv plugin → Registry hack for all Firefox instances
> Created an attachment (id=356704) [details] > Temporary registry patch for wmv plugin Eeek. The mime type claims to be text/plain but it's actually UTF-16 or something weird.
Attachment #356704 - Attachment mime type: text/plain → application/octet-stream
Ok, lets go with application/octet-stream for now.
Everything sounds so easy, but it isn't! Actually, I assumed that the np-wswmp.dll was included in the wmpfirefoxplugin.exe file but apparently it was not. Nothing on C:, nothing on my other partition where Minefield was installed. Nada. I had to do something I'd rather avoid: install this dll previously shared on one of those numerous file hosting services. I'm not really alone with this: see http://kb.mozillazine.org/index.php?title=Talk:Windows_Media_Player&printable=yes I also have Windows XP Sp2 (upgraded from WinXPsp1) and WMP10. I downloaded wmpfirefoxplugin.exe from (SITE) [...] I did a Windows search on "NPMSWMP.dll" and "NPMSWMP*" just to make sure, and nada, nothing was copied anywhere." Correct. And unfortunately, I have no way to trace what is copied where to because everything goes so damn fast. Nor could I find any log file or something of that sort. Weird stuff.
(should be np-*m*swmp.dll sorry for the typo)
OK me again ... I investigated this even further: I figured out that the ffplugin.msi is actually a self-extracting .cab. So I wondered whether I could maybe open that thing with WinRAR by simply renaming it to .cab. But this failed. The file contents (LicenseRtf / NPMSWMPdll / RelNotesTxt) can be viewed, but all I get is "the archive is corrupt". But maybe the MS archive *DOES* have an issue? Maybe this is also the reason why the actual DLL doesn't get installed on many users' systems.
It works also flawlessly in the good old Mozilla|Plugins directory: C:\Users\username\AppData\Roaming\Mozilla\Plugins\np-mswmp.dll It even prefers that location over every other location even if the plugin in the other location is newer (Bug 435993).
Component: Plug-ins → Windows Media Player (Microsoft)
Product: Core → Plugins
QA Contact: plugins → microsoft-wmp
Version: Trunk → unspecified
Flawlessly? I beg to differ! I have here C:\Users\username\AppData\Roaming\Mozilla\Extensions\ and C:\Users\username\AppData\Roaming\Mozilla\Firefox. The plugins subdirectory did not even exist. However, $FIREFOX_INSTALL_PATH\plugins worked, though I had to copy in the dll by hand. Plus, there seems no way to _specify_ the plugins directory in about:config. Registry seems the one and only way out. Not good.
Because bug 692446 already has a resolved status.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 692446
Product: Plugins → Plugins Graveyard
You need to log in before you can comment on or make changes to this bug.