• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

AGP ATI Radeon 1950 PRO 512 DirectX wont Work ???

phpdog

Senior member
Hi ,

I just bought an AGP ATI Radeon 1950 PRO 512 DirectX wont Work ???

It wont work with any drivers , ive tried Vista and MCE ?

HELP Please
 
Originally posted by: phpdog
Hi ,

I just bought an AGP ATI Radeon 1950 PRO 512 DirectX wont Work ???

It wont work with any drivers , ive tried Vista and MCE ?

HELP Please

What exactly is happening when you game?

Are you using it with the rig in your sig?

What power supply are you using? make and model number?

There are know issues with Catalyst 7.8 and 7.9 and AGP Pro's. Have you tried the 7.10s as most have had success with those. If that doesn't work, fall back to Catalyst 7.6. Also do a driver clean out in Safe Mode, including old Nvidia Drivers, between installs.

 
Catalysts drivers don't like AGP versions of cards. Start back with the drivers from the cd. The highest driver I can go with my AGP x1950gt is the 7.7's.
 
Originally posted by: onlyCOpunk
Catalysts drivers don't like AGP versions of cards. Start back with the drivers from the cd. The highest driver I can go with my AGP x1950gt is the 7.7's.

There's a fixed using the Cats 7.8 and 7.9, before installing the drivers make sure that your AGP Aperture Size is set to 256MB. I'm currently using the Cats 7.10 with the Aperture set at 128MB with my X1950XT and I don't have any issues at all. Those issues affected any X1950 AGP based card (X1950PRO, GT, XT)
 
Originally posted by: evolucion8
Originally posted by: onlyCOpunk
Catalysts drivers don't like AGP versions of cards. Start back with the drivers from the cd. The highest driver I can go with my AGP x1950gt is the 7.7's.

There's a fixed using the Cats 7.8 and 7.9, before installing the drivers make sure that your AGP Aperture Size is set to 256MB. I'm currently using the Cats 7.10 with the Aperture set at 128MB with my X1950XT and I don't have any issues at all. Those issues affected any X1950 AGP based card (X1950PRO, GT, XT)

Aperture size? Did this work for just you? or have others confirmed this? Cat. 7.10 has fixed the previous issues for most people.

For those that need to use Catalyst 7.8 or 7.9 for some reason should really try this ......

This workaround was posted on Rage3D and has worked for quite a few on that forum and ATI is looking into why according to Sound_Card who works with the Developers.

1. Install your last known working Catalyst drivers pre 7.9 if you haven't already (ie. 7.8,7.7, etc)

2. Go to "C:\windows\system32" and copy "ati3duag.dll" to your desktop.

3. Uninstall your drivers, use Driver Cleaner to remove any remnants of the drivers, and reboot.

4. Install Catalyst drivers 7.10, and reboot into safe mode.

5. Using the pre 7.9 file "ati3duag.dll" from the desktop (I used 7.7), OVERWRITE the "ati3duag.dll" file from 7.10 in the C:\Windows\system32 folder.

6. Reboot, and test it out with Dxdiag, or one of your fav games or whatever.



 
Using the aperture size fix it worked for me with Cats 7.9, I didn't try them with 7.8. When it was set to 128MB, my system would boot, but the icons in the desktop failed to drawn and the SmartGart wasn't working, everything was off (PCI Writes, PCI Reads etc). But with current Cat 7.10 anything works like it should (At least for me) For people having issues with 7.10 should try the Aperture Size Fix or that ati3duag.dll fix posted by ManWithNoName.
 
I've tried setting my aperture size to 256, that's what it's at now, and the 7.10's still didn't work. But will try the fix Manwithnoname has given.
 
Originally posted by: onlyCOpunk
Manwithnoname, I applaud you as your solution has worked for me.

Your welcome and glad it worked, but it really wasn't my solution. Don't really know who really came-up with it. All I did was copy and paste that from a post on Raged3D and that person just did a copy and paste from some where else. The poster on Rage3D didn't say where it actually came from.


 
Either way you have delivered a solution to me whereas I've been looking for over a month now for a solution and had not found one until today.
 
Back
Top