timwhit
Hairy Aussie
If MS doesn't write a frontend for it, someone else will.
I think the goal is to get consumers on board for a streaming release cycle.
Other than one very minor change (no execute support, which was implemented in Athlon64 and last-generation Pentium 4s as long as they have ca. 2007-era chipsets) going from 8 to 8.1, there hasn't been anything different about Windows hardware requirements in more than eight years.
I also think that end users, especially those who haven't experienced Windows 8 because they were warned away from it, will like the performance enhancements. I expect some whining about the new Settings app that replaces Control Panel, but even that is a place where end users hardly spend any time.
Minor? It was a very serious change which crippled a great many perfectly good, fast systems. Microsoft lied: they said it would only cripple a handful of 10-year-old systems because the very first CPUs and chipsets with appropriate support came out ~ 10 years before 8.1. In actual fact, Windows 8.1 refuses to install or run on millions of fast, modern, mainstream CPUs and chipsets which were being sold in large numbers right up until just before the 8.1 release.
So now it takes longer to find anything in the CP? It's not the end of world.
My problem in general is that with every new Windows release it seems that some older apps no longer work properly or at all.
In some cases the apps are no longer available or replacements are much crappier bloatware.
Bah - as if 32-bit Windows is any good to anyone these days. There are millions of perfectly good, fast modern machines out there which have been effectively bricked by this stupid change. Now if MS has announced a brand new Windows version and said it wouldn't support chip X, that's one thing.
Both Intel and AMD can issue a microcode update to include new instructions (LAHF-SAHF, CMPXCHG16B and PREFETCHW), BUT it'll require support from motherboard vendors (CPU microcode updates can be shipped as part of the BIOS image or as part of the OS) and OS vendors. In reality, both AMD and Intel will just sell you a new CPU instead...There's probably also a way to fix or hide the issue via a firmware fix, if anybody actually cared to make one.
I have already made these points. I think Tannin's mad 'cause he built a lot of AthlonX2 machines and his customers gave him an ear full.
Actually, implementation of the NX bit solves a host of issues with exploit mitigation, stopping both remote and local exploits from occurring... Whilst NX won't stop trojans, it can and does stop a whole range of other malware of performing the initial infection... And with AV solutions being as crap as they are, I'll take anything I can get to help the situation.For example, the NX bit is of almost no consequence, because if someone wants to give users a virus, by God they will give them one.
Allows large page support, reducing pressure on the TLB and paging system leading to better performance.And PAE as a requirement?
Some Windows 2000 server versions (Datacenter) and Windows 2003 server (Enterprise and Datacentre) used PAE to utilise above 4GB RAM. MSSQL and Exchange (of appropriate versions) could access more than 4GB of RAM in these environments whilst still being 32bit applications... For home users, that didn't really apply as most machines in 2000-2003 only had 256MB-512MB of RAM at most...Why? Why, when they have never and likely will never extend 32-bit Windows to even think of using more than 4GB RAM?
The biggest issue was enforcement of having a CPU that supported CMPXCHG16b for 64bit Windows. As this effects people who have more than 4GB RAM, and even some users who have 4GB of RAM, forcing them to run 32bit Windows and losing a chunk of RAM that could be used otherwise... As for why CMPXCHG16b is important, the use of the this instruction allows test and set operations atomically in 64bit environments in a clean and safe manner, especially for the memory management system (eg updating the page tables, setting semaphores and mutexes when a large amount of threads are running, etc).But at the end of the day, it's Microsoft making decisions that are good for Microsoft. Really, what else could we reasonably expect them to do?
They are bricked. Windows 8.0 support ends October 18th, 2015. People bought Windows 8 because their Windows XP support was ending - and then got shafted with this disgraceful scam.
And they didn't have to explain diddly squat. All they had to do was refrain from wiping out major slices of the installed base by stealth, using a service pack. It would be a different matter if they had done it the normal way, coincident with a major release, giving people a much better chance to become aware of the new hardware requirements, and giving existing purchasers of the previous, hardware compatible version, their normal, as-promised, support cycle.
Just no more security updates for the core OS... You may still get updates for things like IE and other shared/common components like .NET, etc after this date, but nothing for the core OS itself.Are there no security updates or doesn't it boot?
Just no more security updates for the core OS... You may still get updates for things like IE and other shared/common components like .NET, etc after this date, but nothing for the core OS itself.
IIRC, the MS policy is to stop support for a version once the next service pack has been released for 2 yrs. Windows 8.1 (which is considered a service pack for 8.0) was released on Nov-2013, therefore support for 8.0 will cease on Nov-2015.
Source: http://support.microsoft.com/lifecycle/?c2=16796
You're catching on.So some computers that run 8.0 won't run 8.1? That would be horrible.
From a functional standpoint I do not equate Win8/8.1 with Vista at all.
You're catching on.
From a functional standpoint I do not equate Win8/8.1 with Vista at all. Aside from the ridiculous metro UI (which is easily changed using classic shell or Start8), Win8.1 has been a pleasure to use which is NOT something I will ever say about Vista. I find myself using the system and not noticing the OS. That means it's been staying out of my way so I can remain productive. It has been very stable. I often go a month of uptime before a reboot which is due when security patches are applied. If Win10 ends up being equally as fast and stable I'll consider changing over to it but I don't see a need to migrate at this time.
Windows Search forcing the use of Cortana/Bing and Windows Defender's default behavior of overriding the hosts file are fairly huge privacy concerns, plus letting Microsoft analyze the content of your OneDrive account if you're using that. But most of us disclose the same information completely willingly to Google and/or Facebook.