AMD/ATI Drops Windows XP Support
Billly Gates writes "The latest beta drivers for the Catalyst drivers control suite only list Vista as the lowest version they will support. We still have almost a year before Windows XP support finally ends. Will NVidia follow? So if you own a AMD system you will not receive audio, chipset, video, or any other drivers for your XP system and must upgrade or use an outdated legacy version. Looks like another death knell for this very long lasting platform."
If you're buying the latest and greatest gaming cards, you're probably going to want DirectX 10 or 11, good multicore support, and an OS that can handle more than 3-ish GB of RAM.
How can I believe you when you tell me what I don't want to hear?
..just because the system is an amd system doesn't get any new/bugfixed drivers, the summary makes it sound like you can't get new network controller drivers for your intel nic if you are running it an amd system..("or any other drivers").
I'm more surprised that they were still producing new drivers for xp, actually, than them dropping the support. it's not like they, or nvidia, are known to bringing on package mentioned features to older cards by driver updates even.
as always, you're only certain to get what you get when you buy the thing.. trusting them to bring newer features to older cards newer worked out.
world was created 5 seconds before this post as it is.
So if you own a AMD system you will not receive audio, chipset, video, or any other drivers for your XP system and must upgrade or use an outdated legacy version.
Ummm, yeah. Microsoft is going to stop releasing security patches for the OS. If you're still running XP, using older video drivers should be the least of your concerns.
$x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
$x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
Total non-issue. If you're still using Windows XP, then you're also stuck on DirectX 9 and all the other outdated technologies. New code means new risks, which you're avoiding by sticking to Windows XP, anyway. Also, the submission is wrong; this affects only the Catalyst drivers, which handle video and HDMI audio.
Then I noticed that this is a timothy story. Sometimes I think he posts the most inane story submissions just to get the Slashdot readers all riled up and posting comments, thus generating hits and ad revenues.
Have a nice time.
Is getting more attractive by the day...
Ironically I am thinking about buying an ATI card for Linux due to its more open nature(Not intel open), so long term support is built into it. Perhaps AMD is only partly responsible.
If you have an XP system, you either:
1. Have an old hack that you are never going to update, since it just works, or
2. Are a corp user with (hopefully) a decent tech team which will ensure you don't buy & support hardware where this will be an issue...
Or (obscure security-related issues aside) am I missing something?
Ummm, yeah. Microsoft is going to stop releasing security patches for the OS. If you're still running XP, using older video drivers should be the least of your concerns.
http://www.microsoft.com/en-us/windows/endofsupport.aspx except that is not happening for another year. The initial date (although I suspect it will be pushed back) April 8 2014.
Its also the date of the end of support for Office 2003. Most of the i915 and above machines (with 1GB of Memory) should simply be moved to Ubuntu and Libreoffice.
But the reality is as the summery states AMD are jumping the gun on this.
XP systems are older systems. You haven't been able to buy XP for years.
How many people have XP systems and are buying new graphics cards?
If it still works, who cares.
If you've hit something where the graphics drivers are obsolete, there's probably a lot more wrong.
keeping up with advances and supporting older systems is EXPENSIVE. AMD made a cost decision, it's not worth it.
Hospitals, schools, and many corporations buy the latest and greatest and then image XP on them and expect them to work. ATI Catalyst is the driver mechanism for all AMD hardware now. Not just video cards.
Ethernet cards, chipsets, and other AMD hardware require ATI catalyst drivers to function properly as they are bundled with it.
Many buy AMD hardware because it is cheaper and a better value than a crappy icore3 when they want more than 2 cores for their staff.
It won't really be a problem if you're not running into security problems. However, if someone finds a way to use the video driver to get SYSTEM or Administrator access to your computer, you'd really want the vendor of said video driver to come with an update. Since MicroSoft is still supporting the OS in terms of security updates, you'd expect the video driver vendor to do the same.
Mind you, just because there's no XP support in the latest beta driver doesn't mean AMD won't fix security flaws if those would arise. It's pure speculation to suggest that something like that might or might not happen. I have a gut feeling that the people at AMD would be smart enough to at least just fix the bug and do a minor version bump if something like that would happen in the period that MicroSoft still supports XP.
I was promised a flying car. Where is my flying car?
I've recently bought an AMD card, and it had rendering errors in XP, although it was with a 2004 game.
Upgrading to 7 fixed the issue.
So support for newer cards on XP was already rather poor.
http://gs.statcounter.com/#os-ww-monthly-201205-201305 you will be one in five users who have not updated from XP
People aren't updating because computers are expensive, Intel and Microsoft take all the profits and walk away with a gross profit margin of over 70%...and new versions of the Microsoft Windows software, are poor tablet interfaces.
Make sure you buy an older card. The free software driver driver for 7000+ cards is a broken joke. Works well for older cards, though. Evil proprietary drivers does sort-of work alright with newer cards but doesn't support older cards. Also know that you can't use 1 old and 1 new card since free driver only works with old cards and proprietary only new.
9/11: Never forget it was a false-flag operation
Had that problem when everything went 64 bit OS. I had an Epson scanner, and they made no 64 bit drivers for any older device. Suddenly every old device became useless. It's not like a new scanner is that much better than an old one. Just make a basic driver so you can at least get hardware to function.
XP is Legend. old Richard Matheson reference.
Find old versions right here: http://support.amd.com/us/gpudownload/windows/previous/Pages/radeonaiw_xp.aspx
I went to AMD's driver site, which I found with the google search, "amd catalyst download". I clicked on "Windows XP (32 bit)". Then I clicked on "Previous Drivers and Software."
The submitter is reading too much into this. The drivers linked are beta drivers - this is not the first time AMD hasn't published an XP version of a beta driver, due to the relatively low number of XP users on 5000/6000/7000 series video cards (all of which are post-Win7). XP is supported by the current WHQL certified driver (13.4) and I expect the next certified driver will support XP, too. If and when AMD does drop XP support they'll announce it a couple of versions ahead of time, just as they did for Win9x and Win2K.
In the statscounter data, where is Android in the "Operating System" chart? IOS is there at 3.18% and if you select the "Mobile OS" chart, Android is higher than IOS. So where is Android in the Operating System chart?
The real "Libtards" are the Libertarians!
Also, there's an important point here which isn't being addressed in the summary.
Vista and later (all NT 6.x versions) use a new "WDDM" driver model for video drivers. Although there are various characteristics of WDDM, the really defining one is that only a tiny shim that basically wraps the direct hardware access lives in kernel mode. Everything else - the actual program logic of the video driver - lives in user mode. This is fantastic for a number of reasons:
1) All the crash-prone code is now user-mode. When a XP video driver crashes, it causes a bluescreen. When a Win7 video driver crashes, it causes a blank screen for about a second while the user-mode driver restarts.
2) Updating and rolling back video drivers no longer requires a reboot; in fact, it only takes a couple seconds. It's actually practical, if you really want to, to switch video drivers between games (for example, if the latest and "greatest" doesn't work with one of your older games, but you want to use it for everything else).
3) Developing and debugging user-mode code is a lot easier than doing the same for kernel-mode code. This change lets developers spend a greater portion of their time improving the driver logic, rather than making the driver work with the various configurations of the NT kernel.
My guess is that AMD decided the benefits of item #3 were worth more than continuing to release drivers for 12-year-old OS. By no longer maintaining the pre-WDDM version, they can focus their resources on supporting modern platforms that are also easier to develop for.
There's no place I could be, since I've found Serenity...
There are a few reasons more likely than the simply no longer supporting XP at all:
... to state two.
* Perhaps this release changes nothing that is relevant to XP. Perhaps all the changes are in codepaths only touched under DX10 or later which is irrelevant to XP.
* Perhaps the early testing was done on limited systems. OK so it is odd for a platform to be ignored in beta tests, but I perhaps if the expected impact on XP is low or zero (see above) they didn't publically release the alpha for XP and someone forgot to update the release details for the beta.
While XP's market share is dropping rapidly now, there are still plenty of home installs out there - plenty enough that ATI/AMD aren't going to risk creating uproar by not supporting them until the official death date from MS (April next year).
Stop this shit Windows XP news. It's 2013. Why is this relevant news for nerds? I mean come on editors! Is this submission better than so many other worthy submissions? How many of us care about this crap? Stop assuming that most of us are some XP support drones looking for jobs on Dice.com. Many of us are scientists, engineers etc in various fields.
Seems arbitrary to me. It shouldn't be difficult to maintain the extra package as the code is largely the same anyway. The only thing that changes from 2k/xp to vista/7/8 is the kernel module itself, a tiny part of the whole driver.
Lots of people still use XP, supported or not, and it's stupid to not support the platform even past the OEM's due date. AMD's customer isn't microsoft, it's the people using hardware with their gpus.
I've had so many issues with newer Radeon drivers screwing up my system, I stopped updating once I hit Catalyst 12.02. Hardware acceleration under XP-32 is totally broken, IMO.
Last year I bought my first nVidia card in 6 years, and I'm astounded at how many of my old games now work properly. If AMD isn't going to bother making XP drivers that work, they may as well stop updating them.
XP or AMD?
“He’s not deformed, he’s just drunk!”
XP service Pack 3(XP was awful pre service pack 2 and delayed Vista for years) only had replaced by Vista Jan30 2007 and only then was not a viable replacement (XP continued to be sold on Netbooks)
And how many netbooks have ATi/AMD graphics chips? Didn't they almost all have crappy Atom CPUs with equally crappy Intel graphics processors on the northbridge/PCH? (Most of them didn't even support hardware decoding of H.264 and other common video formats; Atom was the last PC platform to not include this feature.)
Ethernet cards, chipsets, and other AMD hardware require ATI catalyst drivers to function properly as they are bundled with it.
Virtually every AMD motherboard I've seen in the past couple of years has had a Realtek NIC (usually 8111E). Likewise, the onboard sound is usually one of the Realtek HD codec chips. All of these drivers are available from Realtek's website, including for XP.
You do need "text mode" AHCI drivers to get past the install screen on XP, unless you switch the SATA ports to legacy mode in the BIOS. (And these have to be either slipstreamed into the CD or loaded from a *floppy* at install time – no thumb drive allowed. Ugh!) But these can be found with a bit of digging, and aren't part of the main Catalyst distribution as far as I know.
You should always assume the system's not secure whether you have patches for it or not. Think about it, if there were patches yesterday, and you can assume there'll be patches tomorrow, that means it's still not secure right now. This is true for any software really.
because I have an nVidia GT240. It likes to pretend it's a Directx 10 card, but it's not fooling anyone. Games run like crap in Win7 for me, but run great in XP. If I had $200 lying around I could just buy a new card, but I've got better things to spend, and Arkham City runs just fine on my 6 year old 6000+ with a GT240.
Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
XP64 is a joke- there's very little driver support for it and things were wonky. It was more of a beta test by Microsoft than anything really significant.
The new driver model is much better - and if you're going to do a 64-bit driver, you might as well start afresh with the new driver model than to try to maintain a dead 64-bit port as well.
Dude as someone that has to work on PCs six days a week let me make ONE thing clear, there is NOTHING extra you gotta do to pwn XP, that OS is oooolllllldddddd, okay? It has had 3 service packs, God knows how many patches, hell when it came out a decent PC was a 700Mhz P3 with 128MB of RAM!
Look I get wanting to save old gear okay? But XP wasn't great to start with and its practically ancient now, let it RIP okay?
There's nothing wrong with an old OS as long as it is supported. It's actually often a good thing since nothing is perfect and needs time to be proven.
XP64 worked just fine as long as you ran it on supported hardware and used only supported software. It was never mainstream, but it sure wasn't a joke.
Googling for AMD dropping XP I found posts from October 2012 claiming the same thing: a driver came out with no XP support, end of the world is coming. I haven't been able to find anything official about AMD discontinuing XP support. Doesn't mean it doesn't exist, but I feel that a post will at least have a link to relevant proof. Linking to a beta driver as a form of proof just doesn't cut it IMO.
On Linux I just update to the new and shiny new Fedora, Ubuntu or Debian. Zero costs and I get new software versions with added features or fixed bugs. So I don't really understand why it is to update from Windows XP to Windows 7 is such an issue.
http://www.mueller-public.de - My site http://www.anr-institute.com/ - Advanced Natural Research Institute
Make sure you buy an older card. The free software driver driver for 7000+ cards is a broken joke.
I have the 6770. The open source driver worked well when I briefly used the very latest kernel in Arch. I couldn't stand the constant updates and installed Scientific Linux. Now the open driver is back to being slow and horrible again. The proprietary driver crashes instead. I can use the 6770 on the desktop without compiz-like effects and it doesn't crash, but I can't do any gaming in wine. I'm getting an nVidia GT640, it's been ordered. I think it's a bit sad because ATI are clearly working on their open drivers, but I just need a video card that works. I think it's a bit unfortunate, as the ATI seemed to work well on 3.9 and possibly 3.8 kernels. I played some Heroes of Newerth and it worked well, and I don't expect much from Wine gaming even with nVidia.
*I'm 99 % sure that the issues I have are due to the video card and driver, but I also run ZFS which does some funky memory management things, so I can't rule that out as the culprit. Will post back here in a few days if nVidia one is just as troublesome.
I almost forgot about the nice way to enable power management on the open driver. /sys/class/drm/card0/device/power_method /sys/class/drm/card0/device/power_profile
echo profile >
echo low >
You can set it to low speed or full speed. Even on a desktop it's kind of annoying to have to do that manually. I ended up running at low speed all the time because I forgot to change it (except when using Gnome3, but that's a separate rant) and it worked fine, but it's still kind of lame.
Thank you and I do NOT sound like a damned 13 year old, watch any of those god damned reality shows featuring teens to see how they talk like fricking aliens.
And the P3 was EASILY the most popular CPU when XP was released by a long shot, at the time i stayed pretty damned close to the cutting edge and i had a P3 running at a blistering 1100MHz. The office boxes i was working on at the time were new enough they had WinME stickers on them (needless to say I got a LOT of work wiping ME for XP) and the average was between 650MHz to 900MHz depending on the OEM line and RAM was 128Mb pretty much across the board.
I know people were shocked as hell to see mine had a full 512Mb because that was practically unheard of at the time but I got lucky and knew a guy that could get me RAM at cost and it was still a pretty penny for 2 256Mb chips my friend.
ACs don't waste your time replying, your posts are never seen by me.
So the proprietary driver at least claims to work with some not so new cards.
ATI just supports whatever they want, and fuck you if you don't like it. They still don't provide mobile driver downloads directly. The free driver has never supported R690M properly (I get massive trashing even with accel disabled) and neither has fglrx. When I bought the system with the chipset in it, fglrx already claimed it was too old to be supported. And I can't download a Windows 7 driver from ATI, unlike nVidia which is happy to provide mobile driver downloads and has been for years. Stupid me, this was my third ATI GPU. Never again.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
Honestly, users who are still using windows XP [quite clearly] don't care about getting software updates, why would they care?
Even thought this sounds like flaimbait/troll, I'm being pretty much sincere. Someone who's using an unsupported, 12 year-old OS doesn't seem to be the type of person constantly updating their driver anyway.
You make it sound like getting supported hardware was a hard thing.
My mum bought her computer about 5 years algo, and XP x64 worked fine without any issues. We never consulted if it would work or not - you could just assume it would, much like XP would run on almost any machine you could build at the time.
That would be true of Win 7, hell even Vista, but XP had a serious flaw you just can't easily fix, and that is the entire OS and ecosystem expecting you to be running as Admin 24/7/365 which is just BAD design friend.
With XP there are just too many programs, hell too many drivers, that expect admin and will choke and pitch a fit if not outright crash if you try to run as a limited user and even if you manage to get it working the number of permission pop ups will drive you nuts, it'll make Vista look quiet in comparison.
Look I get wanting to keep some of the old stuff, i really do, but XP is just waaaaay past its prime. its had patches on top of patches, 3 service packs, you can run a clean install for a week and then run something like CCleaner or Comodo system cleaner and find the registry already starting to pile up the orphan links and crap,its just not that good to begin with and now that hardware has passed it by (hell the $100 specials at a lot of places have more RAM than XP can handle without hacks) it really is time to let it go.
I mean for the love of Pete we are talking 14 fricking years by the time MSFT pulls the plug, in OS terms it might as well have come on 8-track.
ACs don't waste your time replying, your posts are never seen by me.
XP64 was problematic because it wasn't a 64-bit build of XP; it was Windows Server 2003 with the server features stripped out.
Benford's Corollary to Clarke's Law: "Any technology distinguishable from magic is insufficiently advanced."
24 * 7 = 364. There's 365 days in a year (366 on leap years), so adding the extra "365" does make sense. 24/7/52 would be stupid, because you're effectively saying that 1 day out of the year, something different is happening or not working.
Actually, 24 * 7 = 168. Nice try, though.
Sorry, 52*7 = 364.
Yes OLD... ... just load a version of Linux or FreeBSD.
Hardware that old
Truth is stranger than fiction, but it is because Fiction is obliged to stick to possibilities; Truth isn't. Mark Twain.
The example of OS/2 provides an example for what the future might be for Windows XP. IBM (and almost all vendors) dropped support for OS/2 in 1996. However, even to this day people are still able to use OS/2 due to support from the open source community and new vendors who provided the support that the old vendors dropped. If there are enough Windows XP users, it is likely that drivers and software support for XP will appear from similar new vendors. Windows XP was the last Windows that Bill Gates was involved in. The story of its demise might be premature.
To be fair, XP64 was more than a beta test, as the Windows NT it was based on was ported early on to a 64 bit architecture and many of the kinks worked out (specifically NT Workstation on the DEC Alpha). Driver support, on the other hand, was a nightmare. I had to support both Alpha NT and XP 64, and the latter was definitely less trouble, but still not perfect.
As for AMD/ATI killing XP support, I guess I can understand - XP is the last supported version of Windows with the old driver model, so this most likely cuts support costs significantly.
Most XP machines are sitting in offices, warehouses or your parents house. The will run facebook or office just fine on outdated drivers. I have a xp laptop with display drivers last updated in 2008 and it still works fine for daily tasks. Unless your playing breaking edge games or doing serious video editing updating your drivers with each new release isnt needed.
24/7/52 may not be exact, but 24/7/365 is stupidly redundant. Just say 24/365. Or, if the issue is being exact, then go with 24/365.242 :)
She is suddenly able to talk again, its the damnedest thing and all I get from docs is "Your guess is as good as mine" which is frustrating as hell but what can you do? Just enjoy these periods and hope they last, all I can do really.
ACs don't waste your time replying, your posts are never seen by me.