Build Your Own Arcade Controls Forum

Software Support => GroovyMAME => Topic started by: xga on August 03, 2015, 08:33:05 am

Title: CRT_EmuDriver with ATI Mobility Radeon HD 4300/4500 series on notebook
Post by: xga on August 03, 2015, 08:33:05 am
Hi Guys and Calamity,

I have a HP 6550b notebook which GPU-Z under Windows 7 reports having a "ATI Mobility Radeon HD 4300/4500 Series" graphics chipset.  I thought that this notebook might be a worthy contender to run Groovymame out the external VGA port to a CRT, but I can't get the CRT_EmuDriver to install.  I removed the old Windows 7 HDD, installed a new HDD and began installing Windows XP.  Once Windows XP SP3 was installed, I attempted to run the CRT_EmuDriver setup.exe but shortly after it started, I received the error message "This display driver is not compatible with the display adapter(s) installed in your system".  I then attempted to use the Mobility mod tool to modify the driver, but that failed to install as well.

Can you think of anything else I can try? 

Thanks in advance for any assistance provided.

Cheers,

Xga
Title: Re: CRT_EmuDriver with ATI Mobility Radeon HD 4300/4500 series on notebook
Post by: Calamity on August 03, 2015, 12:44:47 pm
Why didn't you try with W7?
Title: Re: CRT_EmuDriver with ATI Mobility Radeon HD 4300/4500 series on notebook
Post by: xga on August 03, 2015, 09:23:01 pm
I wanted to start from scratch with a fresh install of Windows without any drivers installed and I didn't have access to Windows 7 installation media at the time, only XP.

Do you think I would get a different result with Windows 7?  I thought it might be an issue with the device ID (0x9555) of the graphics chipset not being recognised by the CRT_EmuDriver.
Title: Re: CRT_EmuDriver with ATI Mobility Radeon HD 4300/4500 series on notebook
Post by: Calamity on August 04, 2015, 05:54:37 am
Quote from: xga on August 03, 2015, 09:23:01 pm
I wanted to start from scratch with a fresh install of Windows without any drivers installed and I didn't have access to Windows 7 installation media at the time, only XP.

Do you think I would get a different result with Windows 7?  I thought it might be an issue with the device ID (0x9555) of the graphics chipset not being recognised by the CRT_EmuDriver.

Windows 7 drivers just might have that ID already, haven't checked. Anyway, did you check if the mod tool actually added that ID to the .inf files?
Title: Re: CRT_EmuDriver with ATI Mobility Radeon HD 4300/4500 series on notebook
Post by: xga on August 04, 2015, 10:59:39 am
I'm away from that notebook at the moment, but I've just downloaded the Windows XP driver again and checked (specifically CX_76825.inf) that it has that ID already.

Code: [Select]
"ATI Mobility Radeon HD 4500 Series"             = ati2mtag_R7X,     PCI\VEN_1002&DEV_9555
The only thing that I note that is different is, in the device manager under Windows 7, the graphics card is reported as "ATI Mobility Radeon HD 4300/4500 Series".  Should I need to change the entry in the CX_76825.inf file from "ATI Mobility Radeon HD 4500 Series" to "ATI Mobility Radeon HD 4300/4500 Series" so that they match exactly or should that not matter?
Title: Re: CRT_EmuDriver with ATI Mobility Radeon HD 4300/4500 series on notebook
Post by: xga on August 05, 2015, 09:58:21 am
In case anyone is interested, changing the entry in the CX_76825.inf file from "ATI Mobility Radeon HD 4500 Series" to "ATI Mobility Radeon HD 4300/4500 Series" fixed the issue and allowed the driver to successfully install.
Title: Re: CRT_EmuDriver with ATI Mobility Radeon HD 4300/4500 series on notebook
Post by: Calamity on August 07, 2015, 05:08:43 pm
Quote from: xga on August 05, 2015, 09:58:21 am
In case anyone is interested, changing the entry in the CX_76825.inf file from "ATI Mobility Radeon HD 4500 Series" to "ATI Mobility Radeon HD 4300/4500 Series" fixed the issue and allowed the driver to successfully install.

Thanks for reporting this. There must be a duplicated label in the inf files, so previously that pci id was ignored. Just changing the name to whatever else will work too. I'll be fixing this soon.