Posted: December 19th, 2013 | Author: kn00tcn | Filed under: Hardware, Software, Tips/Tutorials
Tags: annoyance, ATI, catalyst, CCC, drivers, fix
Looks like the Catalyst version isn’t being correctly stored for some users on the recent 13.12 WHQL release. This has happened before and it’s absolutely nothing to be alarmed about. The only time this would even matter is when a game or application is using this number as a version check such as Battlefield 4, but that is a problem in itself as you’ll notice that this number is merely a registry string.
As a user, all you need to do to change the number is to go into the registry like the example shown above. You can see how you can put any text in there. Many applications in turn read that string and I say it’s poor practice on their part.
The correct driver version number to look at is the packaging version. You can even see the date in its numbers! This is the only true way to tell if your driver has been installed. You could also simply look at the dates of the driver .DLL files. I can’t believe how many people are falling for this in forums, they’re wasting a whole day reinstalling things, it’s ridiculous. Few people seem to bother with any real (not to mention FAST and EASY) troubleshooting, ironic when they do it right with hardware issues. You don’t replace the tower if a component is acting funny, software is no different.
By the way, the Nvidia Forceware driver is the same. It also uses a string for the basic number that many applications read.
Last Modified: December 19th, 2013
Posted: October 11th, 2013 | Author: kn00tcn | Filed under: Software
Tags: ATI, CAPs, catalyst, drivers, gaming, grand theft auto, GTA5, leak, profiles, xml
UPDATE 4:Officially coming this fall
UPDATE 3: It’s now missing from both the profiles .blb and the dx10+ .dlls in the 14.1 mantle beta. Not that it appeared to be needed in the first place as ‘HighPerfGPUAffinity’ doesn’t sound like it’s doing much.
UPDATE 2: It’s in the driver .dll files now. Hex edit atidxx32.dll from 13.11 beta 6 and go to 0x69ae34.
UPDATE: In the new 13.11 Beta 3 leak, hex edit the .blb file, go to 0x192a8, GTA5 is there again (was missing in beta 1).
Well I never looked very closely at the CAP file for 13.10 beta 2, but I just noticed some interesting things.
<application Title="Grand Theft Auto V" File="GTA5.exe">
Want to prove it yourself? You don’t even need to convert the .blb to .xml, just hex edit the blb and go to 0x19130 and 0x19b88 locations.
And the usual games coming soon…
<application Title="Assassin's Creed 4" File="AC4BFSP.exe">
<application Title="Assassin's Creed 4 MP" File="AC4BFMP.exe">
<application Title="Batman: Arkham Origins" File="BatmanOrigins.exe">
<application Title="Call of Duty: Ghosts" File="iw6sp64_ship.exe">
<application Title="Planetary Annhilation (32bit)" File="PA.exe">
<application Title="Planetary Annhilation (64bit)" File="PA32.exe">
<application Title="Need for Speed sequel" File="Race.Main_Win64_Release.exe">
<application Title="Watch Dogs Demo" File="DuniaDemoLaunch_PC_r64.exe">
<application Title="Watch Dogs" File="Watch_Dogs.exe">
<application Title="Wolfenstein: The New Order" File="WolfNewOrder_x64.exe">
Looks like more 64-bit games are coming outside of Battlefield 4? Don’t think this suddenly means GTA5 magically comes out real soon, developers/porters also need working drivers for their games. I’m still expecting the usual +200 days after console launch.
(Guru3d backup post in case the site explodes, but it held up fine during Halo 3)
Last Modified: June 9th, 2014
Posted: March 17th, 2013 | Author: kn00tcn | Filed under: Software
Tags: ATI, CAPs, catalyst, drivers, gaming, halo, leak, profiles, xml
UPDATE: Want proof? Just look at the .blb file from the driver, or use the atiapfxx.exe tool to create the XML yourself. Try these locations of the .blb in a hex editor: 15a74 or 250b6.
Sup. From the CAP of the 13.3 Catalyst beta driver. Another point of interest after the steam app ID that showed up last month.
<profile Area="UDX" Usage="Halo3" Notes="Halo3">
<application Title="Halo3" File="halo3*.exe">
Not that this can fully confirm anything, we still have ‘BF1943Game.exe’ that never came out. You heard it here first… probably.
(Here is my guru3d post in case something happens from all this site traffic, consider it a mirror.)
Last Modified: October 11th, 2013
Posted: September 16th, 2012 | Author: kn00tcn | Filed under: Software, Tips/Tutorials
Tags: AMD, ATI, catalyst, drivers, file, time-saver
UPDATE 2: Instead of running the initial installer, you can use 7zip to browse and extract only the the .dl_ files you want, basically a much more sane step 1 and 2.
UPDATE: To expand every file in the current directory, type ‘expand -r *‘ and you’ll save a ton of time.
Since this comes up pretty much at least once a month on forums, I might as well write down the steps for reference. I assume you’re running Windows of course.
For leaked betas, usually you would skip step 1 since they come in an archive instead of an .EXE installer. Let’s take a look at the 12.8 WHQL package for Windows Vista/7/8 in this example.
Step 1: Run 12-8_vista_win7_win8_64_dd_ccc.exe and it will display a temporary path where it will extract the installation files. If you want, you can change it to something like H:\12-8\ for example. Note this path down as we’ll need it next, click ‘install‘ and once the Catalyst Install Manager appears, cancel it.
Step 2: If you go to the temporary folder from step 1, you should see files like setup.exe and some folders like Bin64, Config, Images, and Packages. Navigate into the \Packages\Drivers\Display\W86A_INF\ folder and then hold shift+right click the B143900 folder. In the context menu you should see ‘Open Command Window Here‘ so select that and now you should have a command prompt sitting in the location of the driver files.
Every file that ends with a _ will require you to expand it so that it can be usable as an actual file. For example, let’s expand atiumdag.dl_. Type ‘expand atiumdag.dl_ atiumdag.dll‘ (press enter to execute the command obviously) and you should now have the complete .DLL file appear in the B143900 folder.
That’s the gist of it, now you can copy atiumdag.dll to a game folder or just keep it for archival purposes in case you need it in the future. This is a much quicker way to test or use different driver versions without installing whole packages for the system. It’s quite handy when a certain game is known to work better on a specific driver version, simply hack up your own fix and you’re done.
Tip: In the command prompt window, you can press TAB to auto complete text, so if you type ‘atiu’ then hit TAB, it will automatically fill in the rest of the filename. If there are multiple files with the same beginning, just keep pressing TAB to cycle through them.
Some Useful Vista/7/8 .DLLs
atiumdag.dll – dx9 32bit
atiumd64.dll – dx9 64bit
atioglxx.dll – opengl 32bit
atio6axx.dll – opengl 64bit
atigktxx.dll / atig6txx.dll – additional 32bit / 64bit opengl files that may help fix very specific games if the above does not
aticfx32.dll + atidxx32.dll – dx10+ 32bit
aticfx64.dll + atidxx64.dll – dx10+ 64bit
Most games are 32bit so you would almost always be dealing with those files. Plus this technique of using a driver file from a specific package works for applications as well. Let’s say your 64bit Photoshop always crashes when opengl is enabled on every driver after 10.4. You would expand atio6axx.dll from 10.4’s package, since you know it works fine, and place it where the 64bit photoshop.exe is located.
Finally, if you’re legacy like me, you can’t really use newer files where support for your card is dropped. The same is true for using files that were compiled before your graphics card was released. The code simply is not there and you can see it in the filesize difference.
Last Modified: October 7th, 2013