smeezekitty

What happens if you run MOM.EXE manually? Any DLL errors? Or crashes?

I don't have a solution to the user32.dll errors. I know it is not the most elegant to have an unclean boot but the user32 error doesn't cause any functional problem. powrprof on the other hand causes big problems and will even crash 3rd party programs. Your driver version looks good. Did you update the other catalyst components in addition to the manual driver install? (the normal installer does this) You have to update it before installing files. Also, just to make sure, you did follow the 64 bit instructions and not the 32 bit ones?

Thanks! That is great news Only if those files are unchanged. I am skeptical but it is hard to say what AMD will do. If those files are changed, the updated versions will need to be modded. Also, if it starts requiring more W7 specific functions, more elaborate wrapper DLLs might become required

Ok. I figured out that the 64 bit version is a mix of both 64 bit components and 32 bit components. I am not the very familiar with 64 bits so I am honestly guessing here. This is a 64 bit build of powrwrap.dll as well as 3 patched ATI/AMD files:https://www.mediafire.com/?id9ihz7xd9xew9a Extract that and drop it in C:\Windows\System32 Replace any ATI files that exist (might have to do it in safe mode) Next grab the zip on my original post (the 32 bit version) Extract it somewhere and copy the files as follows: Copy CLI.Aspect.PowerPlayDPPE.Graphics.Runtime.DLLCLI.Combined.Fusion.Aspects.Runtime.dllLOG.Foundation.dllMicrosoft.WindowsAPICodePack.dllall to your AMD Core-Static folder. (again you might need safe mode) I think it should be in C:\Program Files (x86)\AMD\ATI.ACE\Core-Static by default. Open the "system32" folder of the 32 bit pack and copy atiumdva.dll and powrwrap.dll to C:\windows\syswow64 (this is where 32 bit DLLs go on a 64 bit system) Reboot and check FTFY

hang on / never mind. Let me sort this out P.S. I HATE 64 bits!

I am having some problems compiling a 64 bit DLL on my 32 bit OS. I will try more later but I have to go to the city which is 3 hours each way so I might not have time today

I'll grab the 64 bit package and see if I can patch it. But I know zero about 64 bit software development so I don't know if I can do anything. POWRPROF.DLL definitely causes probems

What is the driver date in device manager? It should be late november for 13.12 -edit- To be clear, are you updating CCC and the other components along with the driver? Did you have any poweprof.dll related errors?

Unfortunately that is difficult for me to troubleshoot because I don't have a CFX setup nor a Vista 64 machine. But do you get any errors? If so, what are they?

IE5 stinks. Opera 3.60 is the browser to go to for 3.x

I have a feeling that Windows 7 is going to be around for a LOOONG time

I realize that the number of people running Vista is quite small and the ones running Vista with a recent AMD Radeon is smaller still. But I wanted to share a modification for making Catalyst 14.12 work on Vista since the last release officially supported for Vista was Cat 13.12. It seems like this is the go to place to share unofficial support for Windows stuff In addition to installing manually through and modding the driver inf file as I described previously for installing Catalyst 14.9 on Vista*, this mod also requires the use of several patched .exe and .dll files modified to use my wrapper for powrprof.dll (to cure crashes caused by a missing function) Here are the patched files and the wrapper DLL download: https://www.mediafire.com/?fz67e75glq0zeat -edit- Scroll down for 64 bit instructions -edit2- *Here are the instructions for doing the INF mod to install in the first place: http://www.tomshardware.com/faq/id-2335392/manually-installing-latest-amd-catalyst-drivers-windows-vista.html

PEinfo.exe did the trick! I changed Minor version number of required OS and Minor version number of subsystem from 1 to 0

Ok Maybe He will stop by? But what is changed in the executable that throws that message? And can it be changed with a hex editor maybe?

I tried a Windows XP only program on Windows 2000 and got "Not a valid Win32 Application" Now I fully expected to get DLL errors but I was surprised by that message. In fact I even re-downloaded it because I thought it may have gotten corrupted but the result was the same. Did something change in Windows EXEs that make them show that message?

Thanks! Well I read somewhere that it was. But it is certainly possible it was wrong

I created a tutorial for step by step installation of newer drivers on Vista over at tomshardware http://www.tomshardware.com/faq/id-2335392/manually-installing-latest-amd-catalyst-drivers-windows-vista.html

That worked! I was able to install Catalyst 14.9 by running the normal installer which updated CCC but not the drivers then going into C:\AMD\Support\14-9xxxxx\Packages\Drivers\Display\WB_INF I went into all the infs and changed all instinces of [ATI.Mfg.NTx86.6.1] to [ATI.Mfg.NTx86.6.0] and installed through device manager. It shows the driver date at 9-14 so it appears like it worked. Down side is the new CCC version shows the error "The procedure entry point QueryDisplayConfig could not be located in the dynamic link library USER32.DLL" on boot up and when I click certain tabs in it but it still works

So far it appears the latest AMD Catalyst graphics driver for Windows Vista in Catalyst 13.12 (despite still supporting 14.x for XP!) Now I know that Windows 7 isn't hugely different from Windows Vista so is there a mod to get the latest Catalyst drivers to install on Vista SP2 32 bit? Thanks