I fixed it by going to the device mgr after running the POWERED BY ATI version, and manually selecting what driver to install. I unchecked "show compatible hardware" and chose to install my Mobility Radeon AS A RADEON 7200/RADEON (Mobility 7500 folks should obviously try the RADEON 7500). After rebooting, I now have the Catalyst control panels! No word on what this may do with your laptop power consumption.
MOBILITY/CATALYST Fix!!!
- Thread starter wildcard
- Start date
scratch that....
scratch that....
Tested UT, which looked rather banded, then got a VGA incompatible error. Back to the 6039's for now
I'm comforted in the fact than anistropic filtering and most of the other Catalyst-supported features are allegedly not supported by the Catalyst driver build at this time, according to the FAQ.
scratch that....
Tested UT, which looked rather banded, then got a VGA incompatible error. Back to the 6039's for now
I'm comforted in the fact than anistropic filtering and most of the other Catalyst-supported features are allegedly not supported by the Catalyst driver build at this time, according to the FAQ.
bigpig1969
New member
Re: scratch that....
Re: scratch that....
Really? Why do you say that?
The FAQ claims the slider has not been fully optimized for OGL not for D3d by the way.
Re: scratch that....
wildcard said:
Really? Why do you say that?
The FAQ claims the slider has not been fully optimized for OGL not for D3d by the way.
INF fix available
INF fix available
Well, I've created this little patch. You still have to manually select Mobility Radeon from Device Manager or Desktop Properties.
Replace CX_04273.inf in wxp-radeon-6-13-10-6094-efg\Driver\XP folder with this version:
http://www.cs.ucl.ac.uk/students/njeewa/ati/CX_04273.inf
Hope it helps.
INF fix available
Well, I've created this little patch. You still have to manually select Mobility Radeon from Device Manager or Desktop Properties.
Replace CX_04273.inf in wxp-radeon-6-13-10-6094-efg\Driver\XP folder with this version:
http://www.cs.ucl.ac.uk/students/njeewa/ati/CX_04273.inf
Hope it helps.
INF error
INF error
got "service installation of this INF is missing" error.
I did get this working at one point as a RADEON, but with the display setting itself to a resolution of 1 by -1 pixels as soon as I played a game....
I filled out the ATI feedback form; they can figure it out.
THanks for all the people contributing fixes, we may find out how to fix this before the pros do!
INF error
got "service installation of this INF is missing" error.
I did get this working at one point as a RADEON, but with the display setting itself to a resolution of 1 by -1 pixels as soon as I played a game....
I filled out the ATI feedback form; they can figure it out.
THanks for all the people contributing fixes, we may find out how to fix this before the pros do!
Hi guys, just installed the Catalyst drivers on my Dell 8100 (Mobility Radeon 7500) running win98SE. Everything seems to work fine (3DMark2001, UT, GPL, N4, F1 2002 demo).
I had the last but one Omega driver installed, uninstalled them and ran the 9039 exe without rebooting. 9039 gave me an inf error but somehow finished the setup prog without freezing. After reboot it still showed the Omega driver installed. Manually installed the Catalysts by device manager. Reboot and driver version is now 9039. Although the new control panels were missing. Went to the driver folder and ran the setup.exe that I found in the CPanel folder, reboot and now I had the new control panel.
The driver are only slightly faster than the 9030 which were the fastest driver on my comp so far (9030: 4110, 9039: 4179).
One thing that I realized is that if I move the D3D main slider to the left (performance), 3DMark2001 freezes my comp during the environment bitmapping test. Any ideas?
Have fun and happy racing, GGP
EDIT: That is the 'Built be ATI' version, didn't try the 'powered by ATI' version.
I had the last but one Omega driver installed, uninstalled them and ran the 9039 exe without rebooting. 9039 gave me an inf error but somehow finished the setup prog without freezing. After reboot it still showed the Omega driver installed. Manually installed the Catalysts by device manager. Reboot and driver version is now 9039. Although the new control panels were missing. Went to the driver folder and ran the setup.exe that I found in the CPanel folder, reboot and now I had the new control panel.
The driver are only slightly faster than the 9030 which were the fastest driver on my comp so far (9030: 4110, 9039: 4179).
One thing that I realized is that if I move the D3D main slider to the left (performance), 3DMark2001 freezes my comp during the environment bitmapping test. Any ideas?
Have fun and happy racing, GGP
EDIT: That is the 'Built be ATI' version, didn't try the 'powered by ATI' version.
Last edited:
Flapjack1976
New member
Best setup (IMO) for the Radeon Mobility 7500
Best setup (IMO) for the Radeon Mobility 7500
Here's the best way I've found to install the drivers. This is assuming you already have the older OEM Mobility Radeon 7500 installed correctly.
First, I downloaded and installed the Made by ATI drivers, and got the "INF file" error. The rest of the program setup correctly.
Next, I used the latest beta drivers that just popped up, found in this thread.
http://www.rage3d.com/board/showthread.php?threadid=33621245
These drivers actually have Mobility Radeon 7500 in the .inf file, so it was a breeze. Now, I'm having absolutely zero problems, though I haven't had time to run a benchmark...
Best setup (IMO) for the Radeon Mobility 7500
Here's the best way I've found to install the drivers. This is assuming you already have the older OEM Mobility Radeon 7500 installed correctly.
First, I downloaded and installed the Made by ATI drivers, and got the "INF file" error. The rest of the program setup correctly.
Next, I used the latest beta drivers that just popped up, found in this thread.
http://www.rage3d.com/board/showthread.php?threadid=33621245
These drivers actually have Mobility Radeon 7500 in the .inf file, so it was a breeze. Now, I'm having absolutely zero problems, though I haven't had time to run a benchmark...
