All Ati Mobility Radeon driver using Mobility Modder

ATI have for many years had their hands tied with laptop manufacturers (OEMS) who request that ATI do not offer support for their device in the Catalyst Driver. This may seem strange, however makers such as Dell may have implemented their own support system and they do not want their customers downloading “reference” drivers from ATI’s home page.

Terry Makedon: AMD Manager for Software Product Management Graphics Product Group issued Driver Heaven with the following statement in April of 2007:

“AMD (formerly ATI) introduced the concept of Catalyst Mobility which is a generic driver that works decently for most laptops. The only way we are able to do this is through permission by a laptop manufacturer (OEM) to include their device in the Catalyst Mobility. We were the first company to provide graphics drivers for laptops to the general public, and we believe there is great value in this. At this point we only have permission from a few vendors and I personally wish more of them would let us. My suggestion is you contact your manufacturer and ask them to have your laptop included in Catalyst Mobility. As for Vista specifically we do not have permissions yet, but as soon as we do we look forward to releasing Vista drivers for laptops.”

Mobility Modder, the evolution

Unfortunately if you have just spent a few thousand $/£ on a new laptop and you want to keep your graphics drivers updated this leaves you in a bit of a pickle and many people frequently are waiting for their OEM to furnish them with new drivers. Right now the only option is to keep emailing your OEM to request that they update their drivers on a regular basis. However, we all know in real life that this rarely makes a difference.

This is where Driver Heaven comes to the rescue and has done now for years with our FREE Mobility Modder for Windows XP. Over 8,000,000 downloads would suggest that many people wanted the newest ATI drivers on their laptop, with good reason.

With the release of Windows Vista, things have changed, our old mobility modder didn’t work correctly as many people on our forums reported, so we have created a new release which is specifically made for VISTA. Currently this has undergone internal testing only so please if you are unsure about running beta software please wait a while until it goes to final build. We would however appreciate feedback on the application in our forums. With your help we can make it better!

The application is recoded in .net framework by the wonderful Ruud Ketelaars (author of the original DriverCleaner (not one of the copycats which are currently riding on the name success of our application) which is natively supported in vista and it is a very compact little program which will install no spyware, malware or anything we could class as dubious. We are enthusiasts just like you guys, so its a simple download with nothing remaining on your system.

Hardware supported:

Windows Vista
ATI MOBILITY RADEON HD 3430
ATI MOBILITY RADEON HD 3670
ATI MOBILITY RADEON HD 3850 X2
ATI MOBILITY RADEON HD 3870
ATI MOBILITY RADEON HD 3870 X2
ATI MOBILITY FireGL V5600
ATI MOBILITY RADEON HD 2700
ATI MOBILITY RADEON HD 3450
ATI MOBILITY RADEON HD 3470
ATI MOBILITY RADEON HD 3650
ATI MOBILITY RADEON HD 3850
ATI MOBILITY FIRE GL T2/T2e
ATI MOBILITY FireGL V3100
ATI MOBILITY FireGL V3200
ATI MOBILITY FireGL V5000
ATI MOBILITY FireGL V5100
ATI MOBILITY FireGL V5200
ATI MOBILITY FireGL V5250
ATI MOBILITY FireGL V7100
ATI MOBILITY FireGL V7200
ATI MOBILITY RADEON 9500
ATI MOBILITY RADEON 9550
ATI MOBILITY RADEON 9600/9700
ATI MOBILITY RADEON 9800
ATI MOBILITY RADEON X300
ATI MOBILITY RADEON X600
ATI MOBILITY RADEON X600 SE
ATI MOBILITY RADEON X700
ATI MOBILITY RADEON X700 XL
ATI MOBILITY RADEON X800
ATI MOBILITY RADEON X800 XT
ATI MOBILITY RADEON X1300
ATI MOBILITY RADEON X1350
ATI MOBILITY RADEON X1400
ATI MOBILITY RADEON X1450
ATI MOBILITY RADEON X1600
ATI MOBILITY RADEON X1700
ATI MOBILITY RADEON X1800
ATI MOBILITY RADEON X1800 XT
ATI MOBILITY RADEON X1900
ATI MOBILITY RADEON X2300
ATI MOBILITY RADEON HD 2300
ATI MOBILITY RADEON HD 2400
ATI MOBILITY RADEON HD 2400 XT
ATI MOBILITY RADEON X2500
ATI MOBILITY RADEON HD 2600
ATI MOBILITY RADEON HD 2600 XT
ATI RADEON XPRESS 200M Series
ATI RADEON XPRESS 1100 Series
ATI RADEON XPRESS 1200 Series
ATI RADEON XPRESS 1300M

Windows XP
ATI MOBILITY RADEON HD 3430
ATI MOBILITY RADEON HD 3670
ATI MOBILITY RADEON HD 3850 X2
ATI MOBILITY RADEON HD 3870
ATI MOBILITY RADEON HD 3870 X2
ATI MOBILITY FireGL V5600
ATI MOBILITY RADEON HD 2700
ATI MOBILITY RADEON HD 3450
ATI MOBILITY RADEON HD 3470
ATI MOBILITY RADEON HD 3650
ATI MOBILITY RADEON HD 3850
ATI MOBILITY FIRE GL T2/T2e
ATI MOBILITY FireGL 7800
ATI MOBILITY FireGL 9000
ATI MOBILITY FireGL V3100
ATI MOBILITY FireGL V3200
ATI MOBILITY FireGL V5000
ATI MOBILITY FireGL V5100
ATI MOBILITY FireGL V5200
ATI MOBILITY FireGL V5250
ATI MOBILITY FireGL V7100
ATI MOBILITY FireGL V7200
ATI MOBILITY IGP 320M
ATI MOBILITY IGP 340M/345M
ATI MOBILITY IGP 9000
ATI MOBILITY IGP 9000/9100
ATI MOBILITY RADEON
ATI MOBILITY RADEON 7500
ATI MOBILITY RADEON 9000
ATI MOBILITY RADEON 9200
ATI MOBILITY RADEON 9500
ATI MOBILITY RADEON 9550
ATI MOBILITY RADEON 9600/9700
ATI MOBILITY RADEON 9800
ATI MOBILITY RADEON X300
ATI MOBILITY RADEON X600
ATI MOBILITY RADEON X600 SE
ATI MOBILITY RADEON X700
ATI MOBILITY RADEON X700 XL
ATI MOBILITY RADEON X800
ATI MOBILITY RADEON X800 XT
ATI MOBILITY RADEON X1300
ATI MOBILITY RADEON X1350
ATI MOBILITY RADEON X1400
ATI MOBILITY RADEON X1450
ATI MOBILITY RADEON X1600
ATI MOBILITY RADEON X1700
ATI MOBILITY RADEON X1800
ATI MOBILITY RADEON X1800 XT
ATI MOBILITY RADEON X1900
ATI MOBILITY RADEON X2300
ATI MOBILITY RADEON X2300 HD
ATI MOBILITY RADEON HD 2400
ATI MOBILITY RADEON HD 2400 XT
ATI MOBILITY RADEON X2500
ATI MOBILITY RADEON HD 2600
ATI MOBILITY RADEON HD 2600 XT
ATI RADEON XPRESS 200M Series
ATI RADEON XPRESS 1100 Series
ATI RADEON XPRESS 1200 Series

Ok, let me have it, how do I use it?:

This is a step by step guide on how to run and use Mobility Modder on Vista AND XP, if you follow these instructions carefully in a step by step manner you will be fine. If you don’t then you more than likely will end up with a driver that doesnt correctly work so you have been warned ! (Don’t panic, even if you don’t mod the driver correctly you won’t hose your OS, the driver just won’t install (like it did before you came to this page – so pay attention!))

Installation step by step guide

1: Download MSXML 6.0 from Microsoft. (Default in Vista) – Install.

Step 2 is VISTA ONLY

2: Make sure UAC control in Vista is turned off. If you don’t know how to do this then read this guide (method 4 is the easiest) or click the “disable UAC” in Mobility Modder.net – please note you MUST reboot after disabling UAC. If you don’t want it disabled permanently, you can turn it back on after our mobility tool has finished, but it won’t mod the drivers correctly with UAC ON.

3: Download the newest desktop drivers from www.ati.com (or get them from Driver Heaven Downloads). If you are using Windows XP make sure to download .net framework from Microsoft (this is built into Windows Vista so there is no need to install it).

4: Run the downloaded driver, let it extract into c:/ATI/SUPPORT – but cancel the installation once the driver is extracted.

5: Run Mobility Modder – browse to the driver in C:ATI/SUPPORT/ – an example of Catalyst 7.4 would be C:\ATI\SUPPORT\7-4_vista32_dd_ccc_enu_44985 – hit modify. Wait until driver is modified.

6: In Vista, go to C:\ATI\SUPPORT\7-4_vista32_dd_ccc_enu_44985 (Or whatever the driver installation folder was called), and run the SETUP.EXE. Please note you might see a “Driver is not WHQL certified”, ignore this, as it is a side effect of the modification.

7: Wait until Install is finished and reboot. Enjoy the new drivers!

HomePage: http://www.driverheaven.net

DOWNLOAD

DrivermaX Your genious Vista Driver Finder

Note: DriverMax only works on Windows Vista, Windows XP and Windows 2003 (all service packs). Driver downloads are *only* available for Windows Vista and Windows XP users.

DriverMax is a new tool that allows you to download the latest driver updates for your computer. No more searching for rare drivers on discs or on the web or inserting one installation CD after the other. Just create a free account, log in, and start downloading the updates that you need.

You can also export all your current drivers (or just the ones that work ok) to a folder or a compressed file. After reinstalling Windows you will have everything in one place!

Most of the situations when Windows is running slower are caused by faulty driver installations. Windows stores all versions of older drivers just in case you want to go back; sometimes it messes up older versions with more recent ones. The Export Wizard will only export the drivers you select by copying the needed files to a folder or a compressed ZIP file.

After reinstalling Windows all drivers will be back in place in less than 5 minutes – sparing you of searching, inserting disc after disk and losing precious time. The Import Drivers wizard allows you to install all the drivers that you exported earlier. The entire operation might take up to 5-10 minutes.

Just one single computer restart will be required after all drivers are reinstalled!

DriverMax is able to display a complete report of all drivers (versions, release dates) installed on your system. This feature can also be very useful when you want to analyze the differences between the drivers installed on different machines.

detail :
What are the device drivers?

A device driver, or a software driver is a type of computer software, typically developed to make the hardware in your computer work. Typically this constitutes an interface for communicating with the device, through the specific computer bus or communications subsystem that the hardware is connected to, providing commands to and/or receiving data from the device, and on the other end, the requisite interfaces to the operating system and software applications. Often called a driver for short, it is a specialized hardware dependent computer program which is also operating system specific that enables another program, typically an operating system or applications software package or computer program running under the operating system kernel, to interact transparently with a hardware device, and usually provides the requisite interrupt handling necessary for any necessary asynchronous time-dependent hardware interfacing needs.

Device driver theory

The key design goal of device drivers is abstraction. Every model of hardware (even within the same class of device) is different. Newer models also are released by manufacturers that provide more reliable or better performance and these newer models are often controlled differently.

Computers and their operating systems cannot be expected to know how to control every device, both now and in the future. To solve this problem, operating systems essentially dictate how every type of device should be controlled. The function of the device driver is then to translate these OS mandated function calls into device specific calls. In theory a new device, which is controlled in a new manner, should function correctly if a suitable driver is available. This new driver will ensure that the device appears to operate as usual from the operating systems’ point of view.

Depending on the specific computer architecture, drivers can be 8-bit, 16-bit, 32-bit, and more recently, 64-bit. This corresponds directly to the architecture of the operating system for which those drivers were developed. For example, in 16-bit Windows 3.11, most drivers were 16-bits, while most drivers for 32-bit Windows XP are 32-bit. More recently, specific 64-bit Linux and Windows versions have required hardware vendors to provide newer 64-bit drivers for their devices.

Device driver development

Writing a device driver is considered a challenge in most cases, as it requires an in-depth understanding of how a given platform functions, both at the hardware and the software level. Because many device drivers execute in kernel mode, software bugs often have much more damaging effects to the system. This is in contrast to most types of user-level software running under modern operating systems, which can be stopped without greatly affecting the rest of the system. Even drivers executing in user mode can crash a system if the device being controlled is erroneously programmed. These factors make it more difficult and dangerous to diagnose problems.

All of this means that the engineers most likely to write device drivers come from the companies that develop the hardware. This is because they have more complete access to information about the design of their hardware than most outsiders. Moreover, it was traditionally considered in the hardware manufacturer’s interest to guarantee that their clients would be able to use their hardware in an optimum way. However, in recent years non-vendors too have written numerous device drivers, mainly for use under free operating systems. In such cases, co-operation on behalf of the vendor is still important, however, as reverse engineering is much more difficult with hardware than it is with software, meaning it may take a long time to learn to operate hardware that has an unknown interface.

In Windows, Microsoft is attempting to address the issues of system instability by poorly written device drivers by creating a new framework for driver development known as Windows Driver Foundation (WDF). This includes UMDF User Mode Driver Framework that encourages development of certain types of drivers – primarily those that implement a message-based protocol for communicating with their devices – as user mode drivers. If such drivers malfunction they will not cause system instability. The KMDF Kernel Mode Driver Framework model continues to allow development of kernel-mode device drivers, but attempts to provide standard implementations of functions that are well known to cause problems, including cancellation of I/O operations, power management, and plug and play device support.

Device driver applications

Because of the diversity of modern hardware and operating systems, many ways exist in which drivers can be used. Drivers are used for interfacing with:

Printers

Video adapters

Network cards

Sound cards

Local buses of various sorts – in particular, for bus mastering on modern systems

Low-bandwidth I/O buses of various sorts (for pointing devices such as mice, keyboards, USB, etc.)

computer storage devices such as hard disk, CD-ROM and floppy disk buses (ATA, SATA, SCSI)

Implementing support for different file systems

Implementing support for image scanners and digital cameras

Choosing and installing the correct device drivers for given hardware is often a key component of computer system configuration.

Virtual device drivers

A particular variant of device drivers are virtual device drivers. They are used in virtualization environments, for example when an MS-DOS program is run on a Microsoft Windows computer or when a guest operating system is run inside e.g. VMware. Instead of enabling the guest operating system to dialog with hardware, virtual device drivers take the opposite role and emulate a piece of hardware, so that the guest operating system and its drivers running inside a virtual machine can have the illusion of accessing real hardware. Attempts by the guest operating system to access the hardware are routed to the virtual device driver in the host operating system as e.g. function calls.

The virtual device driver can also send simulated processor-level events like interrupts into the virtual machine.

drivermax easily find tour device driver
source www.innovative-sol.com

DOWNLOAD DRIVERMAX