Hello, I've experimented the issue that many here also experimented : the new Catalyst drivers won't install because ATI changed the packaging of the drivers, and Mobility Modder has not been updated. So I've tried what I did before Mobility Modder existed : modifying the .inf files of the driver. Unfortunately, this does not work anymore unless you install the driver using the device manager. Impossible to install Catalyst Control Center. The reason is that not only you must modify the .inf files, but also plenty of .msi files. In order to follow this little HOWTO you should know well about the structure of inf files. It's not difficult to figure it out anyway. So here is what I did (manipulation for Windows 7 x64): 1 - Get the beta ATI drivers from AMD website : ATI Catalyst? Mobility Display Driver 2 - Run the installer, but don't install the driver. Files should be extracted to something like : C:\ATI\Support\9-9_beta_win7_64_dd_CC 3 - The inf files contained in C:\ATI\Support\9-9_beta_win7_64_dd_CC\Packages\Drivers\Display\W76A_INF will be your models. 4 - Download the stable drivers, desktop version, complete package, from Drivers & Support | GAME.AMD.COM and extract them the same way. It should be something like in C:\ATI\Support\9-12_vista64_win7_64_dd_ccc_wdm_enu. 5 - Using the beta drivers inf as model, add the missing entries in the desktop drivers inf. Double check that you forgot nothing. I personally added the following entry in the "[ATI.Mfg.NTamd64.6.1]" section : Code: "ATI Mobility Radeon HD 3650 (Gab mod)" = ati2mtag_M76, PCI\VEN_1002&DEV_9591 And all what is relative to this entry of course (refer to the beta drivers !) If you don't know what is your card device ID, just go to the command prompt and type : Code: wmic PATH Win32_VideoController GET PNPDeviceID I personally get the following output : Code: PCI\VEN_1002&DEV_9591&SUBSYS_95911002&REV_00\4&272D8707&0&0008 You can safely ignore all what is after the DEV section, for example I only kept "PCI\VEN_1002&DEV_9591". You can dump the SUBSYS section if you want, I even recommend it. But you can keep it if you like challenge or if you like to waste your time. 6 - Remember the values for your card : VEN (in my case, 1002 = ATI) and DEV (9591=Mobility Radeon HD 3650). Also the SUBSYS value if you decided to keep it. You will probably have a different DEV value than mine. When you added all the missing entries for your card in the desktop drivers inf files, your work is still unfinished. You have to patch all the .MSI files ! 7 - Locate an entry in the inf files that you will substitute in the .MSI files. This entry MUST have the same length as your card entry concerning the device ID : for example if your card is "PCI\VEN_1002&DEV_9591", you can choose "PCI\VEN_1002&DEV_9598" which is corresponding to the ATI Radeon HD3600 series in the .inf. If you choose to keep the SUBSYS field, then find one entry with a SUBSYS, for example "PCI\VEN_1002&DEV_9589&SUBSYS_30001787" which is also a Radeon HD 3600 Series. Be sure to choose a card whose DEV field is represented only one time in the .inf. 8 - Using your favorite hexadecimal editor, open the .msi files. You will have to do the manipulation for every .msi files of the driver, including the .msi of Catalyst Control Center, some don't have to be modified but most have to be. 9 - Search for the string of the DEV field inside the MSI file. Example : "0x9598" in my case. Replace it carefully with the value of the DEV field of YOUR card. Example : "0x9591" in my case. Be careful, sometimes the fields are not contiguous at all in the .MSI ! If you kept the SUBSYS field, search for the 4 first caracters and the 4 last characters of the SUBSYS value (for example "0x3000" and "0x1787") and replace them with the values of the SUBSYS of your card. 10 - Repeat the last step with all the .MSI files... 11 - If you did everything well, you should now be able to install the drivers ! How do you know when it worked ? Well when you are asked for which component to install in custom mode, "Catalyst Control Center" and "Ati display driver" are available Regards, Gabriel H.