• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

New Legacy drivers!

GotNoRice

GotNoRice

[H]F Junkie
2FA
Joined
Jul 11, 2001
Messages
12,793
http://support.amd.com/en-us/download/desktop/legacy?product=legacy2&os=Windows 7 - 64

I was extremely excited when I saw this. I have a secondary system running 2x 4870x2 in Quad Crossfire and another running 2x 4850 in Crossfire. The 2x 4870x2 system in particular still gives very good performance, approaching that of a single GTX680 in many cases. Part of the reason I got my 2nd GTX680 is so it would actually feel like an upgrade over the 2x 4870x2 setup. It's nice to see them still getting good driver support :)

Previously the best driver available was the 13.1 drivers with the 13.5 caps installed on top.
 
Nothing for XP, either... I wish I'd get a driver that stopped BSOD-ing my machine in Chrome on certain websites :/
 
Matija said:
Nothing for XP, either... I wish I'd get a driver that stopped BSOD-ing my machine in Chrome on certain websites :/
Click to expand...

Windows XP is end of life as far as AMD (and, in April 2014, Microsoft) is concerned. Time to upgrade.
 
Using windows XP now is as ridiculous as using windows 98 when the first i7s came out.

No mercy.
 
KazeoHin said:
Using windows XP now is as ridiculous as using windows 98 when the first i7s came out.

No mercy.
Click to expand...

Agreed.. If you are still on XP, there is a problem. 12 years old now. There is no valid argument to still be on XP.
 
some of us are stuck with legacy industrial equipment and no new drivers
 
There's nothing wrong with XP and I have no reason to spend money to upgrade on an ancient PC. What _is_ wrong is that Chrome can BSOD it :p There's a 13.4 beta, so they could have pushed that to final.
 
Great! Thanks for the heads up, GotNoRice. Installed, and I will keep an eye out for changes.
 
Matija said:
There's nothing wrong with XP and I have no reason to spend money to upgrade.
Click to expand...

1: No support for UEFI bios.
2: No support for GPT storage volumes.
3: No support for 48-bit RAM adresses (>4gb system RAM)
4: No support for TRIM on SSDs.
5: No support for DirectX 10, 11.
6: No support for >3gb video cards (see point 3)
7: extremely well documented security loopholes.

I repair PCs as a career. I do not advocate windows XP.
 
KazeoHin said:
1: No support for UEFI bios.
2: No support for GPT storage volumes.
3: No support for 48-bit RAM adresses (>4gb system RAM)
4: No support for TRIM on SSDs.
5: No support for DirectX 10, 11.
6: No support for >3gb video cards (see point 3)
7: extremely well documented security loopholes.

I repair PCs as a career. I do not advocate windows XP.
Click to expand...

I don't repair pc for work. But what you are saying here is sad since I haven't seen anything on Windows but for gaming which makes it needed to install the rest is just asking for trouble. What was nice that XP was the 1st x64.

I can live without uefi that is just something which people list as a pro but really has little to no substance. Not sure what you are missing on the DX10 front since the only thing released on DX10 tend to be tech demos hardly anything worth installing.

Which windows does not have well documented loopholes in security. http://en.wikipedia.org/wiki/Windows_Defender entertaining really

With Windows you take "the risk" does not make any difference which flavour.
 
Last edited:
Pieter3dnow said:
I don't repair pc for work. But what you are saying here is sad since I haven't seen anything on Windows but for gaming which makes it needed to install the rest is just asking for trouble. What was nice that XP was the 1st x64.

I can live without uefi that is just something which people list as a pro but really has little to no substance. Not sure what you are missing on the DX10 fron't since the only thing released on DX10 tend to be tech demos hardly anything worth installing.

Which windows does not have well documented loopholes in security. http://en.wikipedia.org/wiki/Windows_Defender entertaining really

With Windows you take "the risk" does not make any difference which flavour.
Click to expand...

XP wasn't the first x64 version. It was only 32-bit. There was a Windows XP x64 edition, but it wasn't popular and it had too short of a life to solve a lot of the compatibility issues it had... if you could find drivers.

As for DX10/11 support, almost all games in the last few years have had a DX10/11 render path (even WoW uses DX11 now... and it's old). DX9 is dying.

Security wise, XP is simply not in the same league to Vista 7 or 8. So while running any version of Windows might be considered risky, running XP is almost a guarantee that you'll be compromised, especially after next year when MS stops patching the holes that are found.
 
jojo69 said:
some of us are stuck with legacy industrial equipment and no new drivers
Click to expand...

Why do you need new video card drivers for legacy industrial equipment? Protip: for industrial equipment, if it ain't broke, don't fix it with new drivers.
 
Ozymandias said:
Why do you need new video card drivers for legacy industrial equipment? Protip: for industrial equipment, if it ain't broke, don't fix it with new drivers.
Click to expand...

yeah, true enough, I was a bit off topic, just responding to the "no reason to keep XP" comments, yes, there ARE reasons to keep XP, and no, VMs can't really do the job right.

You are certainly correct with your protip. Critical equipment here has been removed from the internet and we have been hoarding motherboards and system images (on IDE drives) for some time.

I have no problem with these snazzy new drivers not supporting XP
 
i sitck with an operating system until something better for me comes along.

windows 98se>windowsnt>windows2000>windowsxpsp2>windows7>

windows 8.1 still isnt better for me.
 
Thank you for the heads-up. I'll notify a couple of clients who have 4800 series video cards to try these drivers.
 
KazeoHin said:
1..6: No support for -foo-
7: extremely well documented security loopholes.
Click to expand...
Here's what I wrote, and then you cut off the last part:

"There's nothing wrong with XP and I have no reason to spend money to upgrade on an ancient PC"

What the hell am I going to do with, say, UEFI support and TRIM on a computer that wasn't even top of the line in 2007? Spending money on a Windows upgrade gives me nothing - the only things I'm missing are the ability to play XCOM and have Chrome that won't BSOD my ATI drivers. Neither of those things are too important, since I don't even own XCOM, and Opera 12.x is my main browser.

I'll give you security loopholes, but considering I have never had an infection, I have no reason to worry and/or even run AV, and due to drive space constraints I've long given up on enabling Windows Update :)
 
jojo69 said:
some of us are stuck with legacy industrial equipment and no new drivers
Click to expand...
You're using legacy industrial equipment that requires a modern driver? :confused:

How did it work when it was new? Use that software configuration...it's a legacy setup, after all.

Matija said:
There's nothing wrong with XP and I have no reason to spend money to upgrade on an ancient PC. What _is_ wrong is that Chrome can BSOD it :p There's a 13.4 beta, so they could have pushed that to final.
Click to expand...
There's quite a bit wrong with XP, though your very own post exemplifies one major issue.

Windows XP uses a much older video driver model that can very easily cause the kernel to crash (which is what you're running into now) if the driver misbehaves. Windows Vista, 7, and 8 all use newer userland drivers that can recover from such crashes without effecting the OS at large.

KazeoHin said:
1: No support for UEFI bios.
2: No support for GPT storage volumes.
3: No support for 48-bit RAM adresses (>4gb system RAM)
4: No support for TRIM on SSDs.
5: No support for DirectX 10, 11.
6: No support for >3gb video cards (see point 3)
7: extremely well documented security loopholes.
Click to expand...
8: No ASLR, making it pathetically easy to rootkit.
9: Accounts are created as Local Administrators by default, and all software is run with admin privs.
10: No official support for user interaction with NTFS junction/reparse points.
11: No support AT ALL for Symlinks.
12: Requires the installation of Windows Search Services 4.0 in order to interact with modern SMB networks without enumerating the entire directory tree.
13: No support for IE9, IE10, or IE11 and their various security fixes (this is due to a lack of Direct2D support, which can't be supported because of the ancient driver model I mentioned earlier).
14: Support and updates from Microsoft will be ending soon, so don't expect many further security patches

The whole OS is just ancient...
 
Last edited:
Matija said:
Here's what I wrote, and then you cut off the last part:

"There's nothing wrong with XP and I have no reason to spend money to upgrade on an ancient PC"

What the hell am I going to do with, say, UEFI support and TRIM on a computer that wasn't even top of the line in 2007? Spending money on a Windows upgrade gives me nothing - the only things I'm missing are the ability to play XCOM and have Chrome that won't BSOD my ATI drivers. Neither of those things are too important, since I don't even own XCOM, and Opera 12.x is my main browser.

I'll give you security loopholes, but considering I have never had an infection, I have no reason to worry and/or even run AV, and due to drive space constraints I've long given up on enabling Windows Update :)
Click to expand...

How many monitors do you use?

My HD4850 used to BSoD on me because the video card would clock down too far, and not have enough power to drive both monitors. Ended in a BSoD everytime I opened anything in flash on it. Ended up editing the bios so all the clocks were the same regardless of performance mode. It used more power, but I never had an issue with a BSoD again from the Video Card. If they could only fix the damned random multi monitor mouse corruption I would probably go back to red team. Til then though, Nvidia I stay.
 
Unknown-One said:
You're using legacy industrial equipment that requires a modern driver? :confused:

How did it work when it was new? Use that software configuration...it's a legacy setup, after all.


There's quite a bit wrong with XP, though your very own post exemplifies one major issue.

Windows XP uses a much older video driver model that can very easily cause the kernel to crash (which is what you're running into now) if the driver misbehaves. Windows Vista, 7, and 8 all use newer userland drivers that can recover from such crashes without effecting the OS at large.

8: No ASLR, making it pathetically easy to rootkit.
9: Accounts are created as Local Administrators by default, and all software is run with admin privs.
10: No official support for user interaction with NTFS junction/reparse points.
11: No support AT ALL for Symlinks.
12: Requires the installation of Windows Search Services 4.0 in order to interact with modern SMB networks without enumerating the entire directory tree.
13: No support for IE9, IE10, or IE11 and their various security fixes (this is due to a lack of Direct2D support, which can't be supported because of the ancient driver model I mentioned earlier).
14: Support and updates from Microsoft will be ending soon, so don't expect many further security patches

The whole OS is just ancient...
Click to expand...

Agreed.
 
You must log in or register to reply here.
Back
Top