Slashdot is powered by your submissions, so send in your scoop

 


Forgot your password?
Close
typodupeerror
×
Intel Windows Operating Systems Software Hardware Technology

Windows 10 Creators Upgrade Cuts Support For Some Intel PCs Early (pcworld.com) 148

Posted by BeauHD from the end-of-the-road dept.
Windows PCs with Intel's Clover Trail Atom chips will not upgrade to the Windows 10 Creators Update, which could wind up being trouble in the future. PCWorld reports: Owners of some Windows 10 laptops and tablets are crashing into a worrying roadblock when they try to install the Windows 10 Creators Update. Windows Update initially says the notebooks are compatible with the upgrade, but fails to install it after downloading the setup files, instead displaying the following message: "Windows 10 is no longer supported on this PC. Uninstall this app now because it isn't compatible with Windows 10." That sounds ominous, but you don't need to uninstall your existing version of Windows 10, and there's no app to uninstall. Instead, the message means your PC's hardware isn't compatible with the Creators Update.

A recent ZDNet article thrust this issue into the spotlight, but Microsoft laid out details about the error in an April forum post. Microsoft won't let affected hardware install the Creators Update because "Icons and/or text throughout the Windows interface may not appear at all, or may appear as solid color blocks on some devices." Can I install the Windows 10 Creators Update? Nope. But you might be able to in the future, according to the April forum post. "Microsoft is working with our partners to provide compatible drivers for these processors. Until then, Windows Update will prevent devices containing one of the processors listed above from installing the Creators Update." [Devices with these Intel "Clover Trail" processors are impacted: Atom Z2760; Atom Z2520; Atom Z2560; Atom Z2580.]
This discussion has been archived. No new comments can be posted.

Windows 10 Creators Upgrade Cuts Support For Some Intel PCs Early More

Windows 10 Creators Upgrade Cuts Support For Some Intel PCs Early

Comments Filter:

  • low end 32bit only cpus at the amd was all 64 (Score:4, Insightful)

    by Joe_Dragon ( 2206452 ) on Monday July 17, 2017 @08:52PM (#54829773)

    low end 32bit only cpus at the time amd was all 64 for some time.

    • Wake me up when it game as good with the same IPC as a 6 year old 2600k?

      • Re: (Score:1)

        by aliquis ( 678370 )

        Wake me up when it game as good with the same IPC as a 6 year old 2600k?

        Mean-while in their ads content about the Epyc launch Intel mention how this is the first new core from AMD in six years time. .. yeah.. and look at all that progress Intel has done since Sandy-bridge!

        (Then again they actually have. Maybe like 50+%?)

        • Intel has improved IPC a bit each generation. Over the past 6 years that adds, up. But not nearly as much as the price.
          Clock speeds are around the same compared to the 2600k. Almost all of those would run 4.5 GHz on air with no real tweaking. With a few tweaks and good cooling you can push near (or to) 5 GHz. To break past 5 GHz on the 7700k you typically need to delid the CPU. Most OCd 7700k CPUs sit below or just at 5 GHz.

          The longevity of the 2600k is something Intel actively worked to dismantle by

  • Sounds like... (Score:3, Insightful)

    by The MAZZTer ( 911996 ) <(megazzt) (at) (gmail.com)> on Monday July 17, 2017 @08:56PM (#54829787) Homepage
    The problem is due to the vendor's failure to provide proper drivers in a timely manner. This sounds like it's a blatant attempt to capitalize on many people's hatred for Windows 10 by blaming Microsoft for Intel's (or Asus'?) problem.

    • Re: (Score:2, Insightful)

      by ArchieBunker ( 132337 )

      No Microsoft is stopping Windows from running on old hardware. You can't run Windows 7 on the latest i7 or Xeon chips.

      • Re: (Score:3, Insightful)

        by unixisc ( 2429386 )

        But this issue is the opposite - preventing not just the Creators upgrade, but Windows 10 itself from running on certain older CPUs. The mention of 32-bit vs 64-bit support doesn't make sense, since Microsoft made a conscious decision to include 32-bit support for Windows 10, despite the fact that one needs 4GB of RAM minimum to run this OS adequately.

        Microsoft can't have it both ways - try to force everybody to upgrade to Windows 10, but then throw up when people try to do it on computers that were oth

        • Re:Sounds like... (Score:4, Insightful)

          by ls671 ( 1122017 ) on Monday July 17, 2017 @09:28PM (#54829945) Homepage

          Also, "lack of proper driver to display icons and text correctly" doesn't really sound like a serious excuse.

        • Just because a CPU is 32 bit, doesn't mean it can't address more than 4GB. PAE has been around for a long time.
          None of those Atom CPU's can even address 3GB though. Some are limited to 2GB and others 2.4GB

          You could install 8GB of RAM on an 32bit Pentium 4 if you had a 955X chipset.
          Pentium 3's could run 8GB of RAM with the right motherboard.

          There are also a bunch of 64bit Atom CPU's (that will still run Windows 10) that only support 2GB of RAM. Some are less than a year old.

          • Even with PAE, a process couldn't address more than the 4GB limit, so you are still stuck if your single process app needed a larger memory space and you were on a 32bit x86 system :/

            • If you're still on 32bit and need more than 4GB RAM, you're doing it wrong

            • and if your 32bit single process app running on a 64bit OS needs a larger memory space you're still out of luck.

          • Does PAE apply to main memory, or storage? I thought it was the latter. Windows never had PAE, or else, they wouldn't have needed to go from 32-bit to 64-bit, since that involves a major hit in storage requirements, cost & performance

            I've never understood the artificial limits that are put on CPUs in terms of addressing. If something is 32-bit, let it address up to 2GB (assuming that one address line is needed for BIOS or IO or anything else. If something is 64-bit, there are enough addresses

            • PAE has a 64GB limit, as it only adds another 4 bits to the 32 address bits. 36 bits = 64GB address space.
              The OS needs to support it.
              Individual processes are still restricted to 32 bits of virtual address space. Windows generally has a 2GB limit, with the upper 2GB reserved for the kernel address space. It can be changed to 3GB but you could run in to problems.

              The limits in the Atom CPU's are physical limits. Their memory controllers can't handle any more.

              Even with PAE, the address space that each process h

        • Re: (Score:2)

          by rtb61 ( 674572 )

          The all new singing and dancing Windows 10 catch 22. You computer is now too old, it will not longer allow windows 10, buy a new computer but don't forget you previous copy of windows 10 is tied to the old computer we wont provide upgrades for, buy a new copy of Windows with the all new invasion of privacy feature, for your convenience, Doctors details for all family members and full medical record require, why because we want it, we will also require permission to access any camera or microphone, M$ softwa

          • Re: (Score:3)

            by Merk42 ( 1906718 )

            You computer is now too old, it will not longer allow windows 10, buy a new computer but don't forget you previous copy of windows 10 is tied to the old computer we wont provide upgrades for

            So it's like a Mac?

            • Okay fine, you don't like Apple. But lying doesn't accomplish anything apart from spreading FUD and diluting the real issues.

              Apple has never forced anyone to upgrade to a newer version of an OS, only to intentionally break that same version of the OS later on.

              Apple has very clear upgrade policies. You may not like them, but they are clear, and they don't change retroactively when it suits them. They don't pull "I have altered our agreement, pray I do not alter it further" bullshit the way Microsoft is do

            • You computer is now too old, it will not longer allow windows 10, buy a new computer but don't forget you previous copy of windows 10 is tied to the old computer we wont provide upgrades for

              So it's like a Mac?

              Except that w/ a Mac, you never buy an OS w/o a computer, since Apple doesn't support Hackintosh. You automatically get OS X when you buy a Mac: you never get a Mac w/o the OS. Yeah, you could replace it w/ Windows, if you are stupid, but otherwise, there is never a case where the computer is not preloaded.

              Besides, does Apple force previous owners to upgrade their OS the way Microsoft does? If my experience w/ iOS is any indication, after a certain point on an old device, the OS can't be updated. I

            • You computer is now too old, it will not longer allow windows 10, buy a new computer but don't forget you previous copy of windows 10 is tied to the old computer we wont provide upgrades for

              So it's like a Mac?

              Ah, another day, another incorrect Apple meme to dispel...

              No.

              If Windows were like a Mac (or more correctly, macOS), in MOST cases, hardware would be supported for as long as reasonably practical. Right now, pretty much every, or maybe even every, Mac back to at least 2009 is supported up through the upcoming High Sierra version (macOS 10.13). That includes most Macs that shipped with Snow Leopard (OS X 10.6), which is SEVEN major revisions ago.

              http://osxdaily.com/2017/06/06... [osxdaily.com]

              In other words, if it is a 64 b

          • Did Microsoft stop you from using periods to form sentences?

        • but they work with windows 10. they don't work with the "creators update" windows 10. the error message says they don't work with windows 10. but they are already in windows 10 using windows 10.

          you see, the cpu they have does have drivers for windows 10. just not for the windows 10 preview(creators update) it was updating to. you see, since microsoft decided that windows 10 is just windows 10 you will have hardware on the market that is windows 10 compatible that does not work with windows 10 eventually. an

        • Re: (Score:2)

          by kyrsjo ( 2420192 )

          Regarding 32-bit and 4 GB RAM, can't they do PAE? Surely no single process needs > 4GB ram to run Windows?

        • I fucking hate Microsoft, but I have an ASUS T100-chi with 32 but Windows 10 and 2GB of RAM. I haven't had time to put Linux on it yet because there is some hoop jumping related to Bluetooth only keyboard, so I am using Windows on it for now. In truth it performs quite well. In fact I will probably just keep Windows so I have the experience of developing on a Windows box, for the rare time when there is no other option ( i.e. it's all the client has available / is willing to use) Sorry to shatter your worl
          • So has Creators' Update broken what you have? If not, you're not the subject of what's being discussed

          • I fucking hate Microsoft, but I have an ASUS T100-chi with 32 but Windows 10 and 2GB of RAM. I haven't had time to put Linux on it yet because there is some hoop jumping related to Bluetooth only keyboard, so I am using Windows on it for now. In truth it performs quite well. In fact I will probably just keep Windows so I have the experience of developing on a Windows box, for the rare time when there is no other option ( i.e. it's all the client has available / is willing to use) Sorry to shatter your worldview.

            God, no WONDER it will NEVER be "The year of Linux on the Desktop!"

            2017 and Linux can't deal with a BT keyboard without "hoop-jumping"???

            Back to the days of DOS and having to install MSCDEX from a floppy just to read a CD to then install Windows without resorting to the 32-floppy install procedure...

            • Windows can't do it without hoop jumping either idiot. The difference is that it came pre-installed with an OS where ASUS already configured it. You are one stupid motherfucker.

              • Windows can't do it without hoop jumping either idiot. The difference is that it came pre-installed with an OS where ASUS already configured it. You are one stupid motherfucker.

                Then I guess they are BOTH inferior to macOS, which handles BT keyboards right out of the box.

                • It is not an add on / secondary keyboard idiot ... and Apple also pre-configures. You truly are a moron.

                  • It is not an add on / secondary keyboard idiot ... and Apple also pre-configures. You truly are a moron.

                    Apple does NOT "pre-configure". When you first startup an new (or newly-upgraded) Mac, you have to go through a little "Identify the Keyboard" dance.

                    But the DRIVERS are all there already. THAT's the difference!

                    So, it looks like it is YOU that is truly the moron, eh?

                    • All the drivers are there with Linux too, so I guess that makes YOU the moron. HAND and FOAD now :^)

                    • All the drivers are there with Linux too, so I guess that makes YOU the moron. HAND and FOAD now :^)

                      IF all the drivers are there, then why do you have to mess around?

                      Oh, I know, they may be PRESENT, but YOU have to decide which one to use, rather than the OS being smart enough to at least give you something that will work well enough to get started.

                    • Read your own post idiot. You just said you have to "Ness around" with Apple. So if all the driver's are there, why do you have to "mess around"? You are so fucking stupid it blows the mind.

                    • Read your own post idiot. You just said you have to "Ness around" with Apple. So if all the driver's are there, why do you have to "mess around"? You are so fucking stupid it blows the mind.

                      By "ness around" [sic], I mean that you have to press a couple of key sequences that the "new keyboard identifier" requests, so it can determine which keyboard LAYOUT is being added; NOT to determine whether there is keyboard activity on Bluetooth vs. USB.

                      NOW do you understand?!?

                    • Actually, you can't do it at all with Apple [cnet.com] as it turns out, but it sure was fun watching you make a fool of yourself. Thanks!

                    • Actually, you can't do it at all with Apple [cnet.com] as it turns out, but it sure was fun watching you make a fool of yourself. Thanks!

                      WTF does that article have to do with automatically recognizing Bluetooth Keyboards on a Mac?

                      I genuinely didn't see anything about that in my (admittedly fast) skimming of the linked article. So, if you'd like to continue your tirade, please point to the text in that article that has anything to do with Keyboard recognition on the Mac.

                    • You're both morons who should STFU. Simply put, if a Bluetooth keyboard just doesn't work out of the box without hassle, the MFG fucked up, not Windows or macOS.
                    • You are actually a bigger idiot than him. Amazing. Go back to the top of the thread and read again. Read it over and over again until you realize how incredibly fucking stupid you are for posting what you posted.

      • Re:Sounds like... (Score:5, Informative)

        by willy_me ( 212994 ) on Monday July 17, 2017 @09:15PM (#54829873)
        Of course you can run Windows 7 on the latest Intel CPUs. Windows will not use all the hardware features included with the new CPUs but it will still run - just in an unsupported state.
    • Comment removed based on user account deletion

    • Actually, IMO I would be angry with Microsoft. I mean have you ever install an app and it works up until you open it with a message like "it's no longer supported. Uninstall it now."

      It is the same as "Windows 10 is no longer supported on this PC. Uninstall this app now because it isn't compatible with Windows 10." In fact, Windows 10 isn't an app and it hasn't been installed so the second sentence only made more confusion.

      When what Microsoft should have done was to put a message like this, "This version

    • Re:Sounds like... (Score:5, Interesting)

      by fuzzyfuzzyfungus ( 1223518 ) on Monday July 17, 2017 @09:42PM (#54830009) Journal
      The fact that PowerVR-based Atoms have worthless driver support is Intel's fault: Microsoft's contribution to the debacle is creating a situation where upgrading the OS actually shortens the support window. If running Win8.1, these devices would get the pre "windows as a service" treatment; which in the case of 8.1 is mainstream support until 1/09/2018; extended support until 1/10/2023; if running Windows 10, a given major update gets only "at least 18 months"; after which you are potentially out of luck unless you can move to the next major update. And, since 'feature' and 'security' updates are now being aggregated; having a GPU with drivers that don't play nice with some aspect of WDDM means no security updates.

      Intel's support for the PowerVR-based Atoms has always been shamefully bad; and they deserve full blame for that; but that doesn't change the fact that Microsoft's big push for Win10 upgrades...doesn't look so good...for hardware where it now(well after users made the choice, and without any way for them to know) means that Win10 devices will fall out of support faster than Win8.1 devices will.

      It's also not a favorable anecdote for the 'Windows' glorious stable driver interface!' argument that always gets trotted out: It's not a huge surprise that an older part that always had shit support isn't getting shiny new drivers with WDDM 2.2 support; but Win10 1703 has apparently changed enough that those parts, which do have functioning drivers for earlier WDDM versions(probably 1.2 or 1.3; since they were introduced to support Win8; maybe 2.0 depending on how much polish they received for Win10) can't even continue to offer the features that they previously offered if you update to version 1703; while they did work in 1607.

      That sort of stability an backward compatibility used to be something that Microsoft at least tried at and cared about; the change isn't a flattering one. Entirely in keeping with Microsoft's Apple-envy approach of late; but not a good thing.

      • where is the basic VESA mode fail back driver?

        • I don't know if that is still a thing. UEFI Graphics Output Protocol has the knives out for VESA mode; though I don't know how many, if any, devices are now VESA-free; as opposed to supporting both.
      • Yeah, one of the many things I don't like about Windows 10 is that there's no notion of stable version any more. Windows 7 is still supported and, AFAIK, it hasn't had any notable changes in UI or features since it was released, it just gets security updates, as it should be.
        Windows 10 is developed in a sort of "agile" methodology: New versions every few months, any of which can contain any number of changes to the UI, and can add and/or remove features without notice. That's not something I like much in g

      • Re:Sounds like... (Score:4, Insightful)

        by Kjella ( 173770 ) on Tuesday July 18, 2017 @07:56AM (#54831861) Homepage

        That sort of stability an backward compatibility used to be something that Microsoft at least tried at and cared about; the change isn't a flattering one.

        On the application side perhaps, the driver side has never been that way. Microsoft releases a new version of the OS, the manufacturer may or may not update their driver. Which if it was a shitty vendor often did not happen on products more than a few years old because they already have your money and want to sell you the shiny new stuff. But that was okay because you could just stay on your current Windows version and get 5+5 years of support from MS even though the manufacturer dropped the ball after two.

        I thought it was bloody obvious what the consequences of "last version of Windows ever" and "the supported lifetime of the device" were, basically Windows will continually change and the hardware vendor has to keep up. If it doesn't, put it in the junk bin (or install Linux, but last I heard these PowerVR chips had even more terrible Linux support). Did you really think the plan was to continue to give you 10-15 years (manufacturer supporting version N+1, then 5+5 from Microsoft) of useful device life? Oh no, this is planned obsolescence at work.

    • The problem is due to the vendor's failure to provide proper drivers in a timely manner. This sounds like it's a blatant attempt to capitalize on many people's hatred for Windows 10 by blaming Microsoft for Intel's (or Asus'?) problem.

      Some computer OS providers write their own drivers. Just sayin,

      Microsoft's demand that other's write drivers is part of the reason for the hate. That has not changed.

      To the point where the Windows ecosystem is now inferior. I had some dual boot system setups that needed a USB to serial adapter. In Linux, they set up perfectly. Windows? Nope. No driver, and none would be available. Had to purchase ones that had the driver. So I tried the adapters on an OSX system. Worked perfectly.

      The hate is well a

  • Nothing to Worry about ... yet (Score:4, Informative)

    by williamyf ( 227051 ) on Monday July 17, 2017 @09:06PM (#54829841)

    Creator's Update was released On April 11 2017, and on THAT DATE Microsoft advised owners of affected chips NOT to apply the Update while the situation was resolved.

    Those people are (for the time being) on Aniversay update, which was launched on August 2016, and has 18 months of security updates. That leaves Micrusoft until May 2018 to solve the problem and alow those people to update, or since aniversary update is a "Current Branch for Business"release, and therefore, keep receiving security updates for 5+5 years, may release said patches to affected users, or declare defeat and officialy cut suppport for said chips.

    But, being that it's been only 4 months since the problem started, it is sort of premature to declare that support has been cut for said Hardware...

    The article was mostly clickbait... and boy so many clicked... (meesssa included, young yedi)

    More info here:
    https://www.thurrott.com/windo... [thurrott.com]

    • So what you are saying is Microsoft knew that they weren't going to support it, but rather than checking through software at the start of the process they put the onus on every user on the planet to have read about it, know what exact hardware they have, remember 4 months later, and then assume they hadn't resolved the issue, and then assume OK meant "PLEASE WASTE MY TIME AND THEN LIE TO ME AT THE POINT OF FAILURE"?

      • [...]but rather than checking through software at the start of the process[...]

        They check at the strt of the process and not perform the update IF you heed the advice and leave it to the automatic updates. If, on the other hand, you DO NOT heed their advice and installed MANUALLY three months later, well, this is bound to hapend, wart, confusing messages and all.

        Users were told not to install the update MANUALLY, but instead wait for it to arrive through automatic updates, and they went out of their way to install it MANUALLY. I know we are in slashdot, were reading TFA is frowned upo

        • I read enough to know that it isn't an update, and they didn't refuse to proceed, but rather went through the entire *INSTALL* before complaining, and then botched that too. Off you go now little troll ...

          • If you install by hand you are supposed to know what you are doing, so no check beforehand for you. Maybe you are testing, or are the actual ASUS/Intel/PowerVR/Microsoft developer trying to fix the issue.. who knows, but microsoft assumes you know what you are doing.

            If, on the other hand, you left things well alone, and waited for automatic updates as recomended by Microsoft for this specific case, you will never be offered the update in the first place, because the update system will check at the start of

            • It isn't an update dumbfuck. Stop misusing terms just because Microsoft misuses them.

              • It isn't an update dumbfuck. Stop misusing terms just because Microsoft misuses them.

                Potato-Potatoe-Patata
                Tomato-Tomatoe-Tomate
                Pineaple-Pi#a-Ananas

                If you prefer the word UPGRADE, that does not change any facts, so I'll use it then in order to humour you:

                * People with afected Hardware who, in April 11 2017 heeded Microsoft's advice waited for the WU program to deliver the Creators UPGRADE for them did not have any problem, becasue the WU Program performed a check before starting, detected the Hardware as not supported, and therefore, never offered said UPGRADE it in the first place. Leaving

    • Creator's Update was released On April 11 2017, and on THAT DATE Microsoft advised owners of affected chips NOT to apply the Update while the situation was resolved.

      But the update was installed three whole months later, and the problem was STILL not fixed. I also experienced a problem with the Creator's Update: The new Night Light feature (similar to f.lux) didn't turn off automatically. Searching for some answers, I found several posts about people reporting the same problem to microsoft... in April. Thre

      • But the update was installed three whole months later

        Yes, the Update was installed MANUALLY three months later.

        Users were told not to install the update MANUALLY, but instead wait for it to arrive through automatic updates, and they went out of their way to install it MANUALLY. I know we are in slashdot, were reading TFA is frowned upon, and bashing Microsoft is trendy, but please... "Un poquito de porfavor!"

  • If I read this correctly... (Score:4, Interesting)

    by QuietLagoon ( 813062 ) on Monday July 17, 2017 @09:28PM (#54829941)
    ... if the customers had stayed with Windows 8 and fought off the egregiously aggressive Windows 10 updates, those customers would continue to receive updates through 2023. But because Microsoft hijacked their PCs and all-but-forced an upgrade to Windows 10, updates for the PCs will be shutdown very soon.

    .
    Welcome to the new Micro[screw the customer]soft.

  • I noticed several titles re this sudden loss of support for Intel CPUs by W10. Cute, Intel Atom CPUs is accurate but very few would care about them. They are not a large market, never were and are quite literally a dead product line.

    Granted, click driver journalism isn't the gold standard even if it is the current standard.
  • Comment removed based on user account deletion

    • ...Came with Windows XP, but now runs 16.04 lubuntu.

      It's still running fine with a 2GB upgrade, and will probably do so until the Y2038 bug

      Why would that stop it? The unix clock can be 64-bit even if the processor is not ;)

  • Still crap (Score:4, Insightful)

    by martinX ( 672498 ) on Monday July 17, 2017 @10:43PM (#54830277)

    "Uninstall this app now because it isn't compatible with Windows 10."

    That sounds ominous, but you don't need to uninstall your existing version of Windows 10, and there's no app to uninstall. Instead, the message means your PC's hardware isn't compatible with the Creators Update.

    And that's reason number eleventy billion why Windows is still crap. A simple message that is completely wrong. They can't even get that right.

  • where freedom still exists....
  • Wouldn't running Windows 10 on a low end Atom processor be torture anyway?

  • I didn't think we could do any worse than that. I have a Surface Pro 3 which regularly has missing icons, as far as I've experience since they released a beta this has been an on and off issue. I always hated Apple for their quickly dropping hardware as "supported", it seems I need to readjust my expectations of Microsoft now.

    Windows 10 is a constant stream of lackluster "improvements". All a person has to do is open the "settings" to realize you still need a Control Panel, but in their infinite wisdom Mi

    • I didn't think we could do any worse than that. I have a Surface Pro 3 which regularly has missing icons, as far as I've experience since they released a beta this has been an on and off issue. I always hated Apple for their quickly dropping hardware as "supported", it seems I need to readjust my expectations of Microsoft now.

      Windows 10 is a constant stream of lackluster "improvements". All a person has to do is open the "settings" to realize you still need a Control Panel, but in their infinite wisdom Microsoft doesn't give you quick and easy access to that now.

      This whole upgrade strategy is bizarre if you ask me.

      Excuse me, but other than a few 32-bit Mac models, the last of which was discontinued in August, 2007, and some of the very earliest 64-bit machines, nearly every Mac since 2009 is STILL supported, even in the not-yet-released macOS 10.13 (High Sierra).

      • Well, "excuse me", for tamping on your happy deluded Apple Fanboi Day. Lol, my comment wasn't even a slight against Apple, so if you take it that way, maybe you should grow another layer of skin. Like any good professional I own all kinds of equipment, and "excuse me" if I can't say something truthful.

        You're right, Apple has continued to support the top-of-its-line computers all the while dropping support for it's lower-end units on a continuing basis. And while they may "upgrade" some hardware with the "l

        • You're right, Apple has continued to support the top-of-its-line computers all the while dropping support for it's lower-end units on a continuing basis.

          BZZT, wrong, Chucko!

          Some of the Macs "orphaned" along the way were 2007 and 2008 Mac Pros. Fortunately, I believe the Mac Hacker community alleviated that problem.

          And while they may "upgrade" some hardware with the "latest", it often may not function with the same level of compatibility it did with previous iterations.

          True. Some configurations have things like certain GPUs that simply cannot support things like GCD and OpenCL. I'm sure there are other examples I can't remember offhand.

          [...] unlike Apple, which kills it dead and you're stuck.

          And so your computer simply stops working if you can't upgrade the OS? Riiiiiight.

          All hardware support ends at some point. That's a fact. But Microsoft's sin was in prematurely an

  • all the metro type apps like the new shitty control panel ripoff have had solid colour icons for me for over a year now and i have a normal not atom intel.

Slashdot Top Deals

I have hardly ever known a mathematician who was capable of reasoning. -- Plato

Close