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: 1, Informative) by Anonymous Coward on Wednesday October 19 2016, @12:06PM
This has worked for years, at least in Firefox.
What hasn't worked, is the Windows update process itself. Fire up a new Windows 7 or 8.1 machine and try to update it. It will take WEEKS to find updates, if it ever does at all.
The Windows update system was re-written in summer 2016 (Microsoft acknowledging the problem), and the removal of svchost.exe in current builds as well as the all in one monthly updates will help alleviate the update problem, but if using anything other than Windows 10, you will have to use Windows Update itself (or WSUS) to ever see the new Windows Update at all.
Windows is waaaay over-engineered, and the update process is broken because of this. Recent changes to update methodology only serve to hide this fact. What's needed is hiring people like tedu@ to remove all the cruft from Windows and move the operating system forward.
(Score: 2) by butthurt on Wednesday October 19 2016, @12:42PM
Microsoft Baseline Security Analyzer was said (prior to the 11th of this month) to work with Windows versions prior to Windows 10.
(Score: 3, Touché) by Nerdfest on Wednesday October 19 2016, @01:02PM
This is obviously some new definition of the word "over-engineered" I wasn't previously aware of.
(Score: 2) by Celestial on Wednesday October 19 2016, @02:54PM
Microsoft Windows' "cruft" that you want to remove is precisely one of the main reasons why it's so popular. Most applications and games that were made for Microsoft Windows back in 1999 still work today.
(Score: 0) by Anonymous Coward on Wednesday October 19 2016, @08:56PM
Most applications and games that were made for Microsoft Windows back in 1999 still work today
You can get that with FOSS stuff too.
Ever hear of a "fat binary"?
If you like old stuff, just keep an install of a distro of that vintage.
With FOSS, you have the source code and can compile it (using the old kernel with its old dependencies) and include all the dependencies **in** the app.
You (and/or your friends) can then run that binary under a modern distro.
You can also run the game in a virtual machine with that old distro installed there.
If you meant to impress someone with MICROS~1's awesomeness, you fell short.
-- OriginalOwner_ [soylentnews.org]
(Score: 1, Informative) by Anonymous Coward on Wednesday October 19 2016, @09:44PM
Ever hear of a "fat binary"?
Yep every distro runs with them right? Oh wait pretty much no one does it. Apple did it for awhile when they moved between architectures but soon dropped it.
and include all the dependencies **in** the app.
Ah so reverse dependency hell. Just copy everything into one dir and hope for the best approach. You can do that in windows too if you want. It rarely works out good in the end.
So I have a bit of software from say 2002. The company is long since gone. I should just say 'aw fuck it I am going to use the open source version of it'. OH WAIT it does not even exist.
If you meant to impress someone with your 'linux skilz' You can do better.
(Score: 0) by Anonymous Coward on Thursday October 20 2016, @12:58AM
Just copy everything into one dir
You are a complete nitwit.
-- OriginalOwner_ [soylentnews.org]
(Score: 0) by Anonymous Coward on Friday October 21 2016, @11:44PM
To get a "fat binary", you INCLUDE all the dependencies IN the executable when you COMPILE that, nitwit.
That's how the thing gets fat, dumbass.
That's also how you get version independence.
You don't make calls to the OS's on-disk stuff--not to libraries; not to e.g. the Windoze Registry.
So, putting more DLLs (or the equivalent) in a directory doesn't make the slightest different for this paradigm, idiot.
You can also get -machine- independence.
You can even put the app on a thumbdrive and carry it with you.
If you want the Windoze paradigm that parallels this, that's PortableApps--sorta.
-- OriginalOwner_ [soylentnews.org]