SoylentNews is people
SoylentNews
Submitted via IRC for TheMightyBuzzard
Just a quick heads up for those users and system administrators who are tired of accessing the Microsoft Update Catalog in Internet Explorer or using the workaround to use other browsers: the site is now working in any modern browser.
Simply point your web browser to the main address -- http://www.catalog.update.microsoft.com/Home.aspx -- and the site should open just fine.
No more using Internet Explorer to download patches from the Update Catalog, or using the RSS feed workaround to download them using other browsers.
I have tested the site with Chrome, Firefox, Opera and Vivaldi, and it worked fine in all of them. Surprisingly though, it does not work in Microsoft Edge yet because there is still a script running on the page that checks for Edge and intercepts the connection.
Source: http://www.ghacks.net/2016/10/15/microsoft-update-catalog-works-with-any-browser-now/
(Score: 2) by VLM on Wednesday October 19 2016, @02:43PM
I can run windows stuff on my freebsd box via wine
https://wiki.freebsd.org/Wine [freebsd.org]
although I don't do it much.
For years I've been expecting some kind of embrace extend extinguish for linux (well, there is systemd) and unixes like freebsd. I figure it would come in the form of installing MS software via the usual repo stuff or similar.
I would guess there would be some people who would run MSIE as a browser sometimes to debug compatibility issues or shell scripts with #!/usr/local/bin/powershell
As a non-MS example of why I like the ability even if I don't use it, I have an apple airport wifi access point somewhere in my disorganized home network and I can use the airport utility to configure it from my wife's mac but if I want to configure it I'm told the windows configuration program runs just fine under WINE.
At the time I bought the airport I had a powerpc mac on my desk as one of the multiple machines I always have, so it wasn't an issue. Also, maybe unbelievably, I had never heard of a modern wifi device that was configured by a binary non-foss program instead of via the web so I rather ignorantly assumed of course apple airports were configured via web interface because all wifi access points are configured via a web interface...