Jan 27, 2016. The thing telling you to install Silverlight is just a standard fallback picture you will see if the Silverlight object cannot render in the page. The most common cause of that on Windows with Internet Explorer is the browser security settings. Basically, you have settings which are stopping Silverlight. Download the current version of Silverlight. Double-click on Silverlight.dmg in your browser's Downloads menu. For Safari, the Downloads menu is in the upper right corner of the browser. For Firefox, Downloads is a separate window located in the Dock. Double-click on Silverlight.pkg. Follow the installation prompts. Close and reopen your browser and try Netflix again. Attempts to restart the computer and try to upgrade, install or uninstall Microsoft Silverlight again end in the same results. Cause This issue can occur if an existing installation or uninstall has become corrupt. Sep 27, 2018.
Firefox version 52 ESR Win XP OS. Silverlight plug-in stopped working just yesterday on Netflix and my Win XP Pro OS. I have uninstalled the older version and downloaded the correct version I need 5.1.4.1.2 and it is installed but still doesn't work with Netflix. I cannot find in the registry Netflix and Silverlight permission to run the plug in. This is a problem and needs to be fixed. I don't have the money or means to upgrade my OS at this time. I have no tv either. I have been in contact with Microsoft and Netflix and they determined that the problem lies with Mozilla. I cannot use any other browser as Chrome does not work with Netflix and Win XP either due to unable to update WidevineCdm on XP.
![]()
A few weeks ago Aaron Brazell mentioned on Twitter that he had been unable to run Silverlight on his brand new Macbook Air:
I have never been able to run Silverlight on my 3 month old Macbook Air. Can someone help me solve this? cl.ly/image/2r3U1H38…
![]()
This intrigued me, as many random things do. I love attempting to resolve obscure issues, and after watching him struggle for a few days I decided to help out. I spent about an hour, and learned some really cool things about the installation process for Mac apps packaged as ‘.pkg’ files, and how to go about installing them manually.
I had a hard time finding the information anywhere, and figured that, while this is somewhat specific to Silverlight, that it may be useful to others.
Although I use a Mac, and love the beauty of it’s UI, I spend most of my time on the command line. I am a Linux Systems/DevOps Engineer by trade, so I of course interact with most of my daily tasks from the command line.
I needed to download a copy of the Silverlight.dmg file, but quickly found that if you hit the Silverlight site, and already have Silverlight installed you couldn’t get to the download. Fortunately they link you to an uninstall page on their site, so I just deleted the paths specified there:
I restarted my browser, hit the Silverlight site again, and downloaded the Silverlight.dmg file. I did take this opportunity, to inspect my HTTP requests from my browser, and determined the actual URL where the file lives for future reference.
After downloading and double clicking to mount, you can just navigate directly into /Volumes/Silverlight/Silverlight.pkg from the command line. On Mac ‘.app’ and ‘.pkg’ as well as many other items that appear to be files, are actually just specially named directories. Mac styles them to look like files. If you really want, you can right click on such an item and select ‘Show Package Contents’.
Silverlight 4.0 Download Mac
Once inside, I took a look around, and quickly noticed that the
Contents/Archive.pax.gz file was where the majority of the data was located based on size, and looking in the Contents/Resources directory, I found some simple shell scripts and perl scripts.
There is an InstallationCheck perl script, that is used to validate that your system meets the requirements. After looking into it, I couldn’t determine why it would fail to succeed, and neither could Aaron. Attempting to modify this file and install, resulted in the installer reporting some generic error, which was the result of the signature of the InstallationCheck file being different than the stored value. With that option gone, I took a look at the other files.
I found
preflight was a shell script version of the uninstall instructions on the site. And postflight went around cleaning some things up and generating CPU specific optimized libraries for Silverlight to use, as opposed to just-in-time compilation.
Silverlight For Mac Os X
Back to
Archive.pax.gz …
I quickly recognized the ‘.gz’ extension, as that is a standard gzip file extension. I however, did not recognize the ‘.pax’ file extension, although after reading a little about it), I am a little surprised I didn’t.
In any case, after gunzipping and unarchiving using
pax , You basically get a directory hierarchy that can be dropped into the root (/) partition on your Mac. So to keep from wasting any more of your time, let’s get on to the actual steps to get it working:
Note: I wouldn’t try just copy/pasting that whole block. Run each command separately to avoid potential issue.
Close your web browser(s) and reopen visiting the following URL to test Silverlight:http://www.microsoft.com/getsilverlight/default.aspx
Microsoft Silverlight For Mac
At this point you should have a Silverlight working on your Mac, or at least it was for Aaron:
My Silverlight issue was solved manually by @sivel with this series of commands. Sheer brilliance. gist.github.com/b56105b0748f7e…
— Aaron Brazell (@technosailor) December 27, 2012
That Github Gist, still exists, and contains the same steps as outlined above.
Most of those instructions are pretty self explanatory, the one that is not is probably the
sed command. Basically in postflight it kicks off a number of commands into the background that utilize a binary called coregen_i386 . It also deletes the coregen_i386 binary. In my testing I found that it often deleted the coregen_i386 binary before all of the coregen_i386 commands had executed, causing some of them to fail. So the sed command does an inplace edit of the postflight file to remove the rm -rf commands to delete the coregen_i386 and coregen_x86_64 binaries.
Anyway, hopefully this helps someone else. Enjoy!
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2020
Categories |