Build Your Own Arcade Controls Forum

Main => Software Forum => Topic started by: kyoke on January 11, 2011, 12:22:53 pm

Title: CHD Problem --- Windows 7? CHD set too old?
Post by: kyoke on January 11, 2011, 12:22:53 pm

Hi All,

I'm finishing up on my bartop cab and getting the software configured.

Odd that MAME doesn't seem to recognize any of my CHDs... Here are some notes on my config:

1. MAME 0.141 compiled with hiscore diff
2. Newest ROMset (0.141)
3. Older CHDs (I think 0.135)
4. Windows 7, UAC disabled, using actual "Administrator" account
5. clrmamepro used (no CHDs are found even though they are in the correct folders/structure)
6. chdman used on a test item to update it, but MAME still did not recognize the CHD
7. MAME folder is like this: c:\user\desktop\MAX 2.10\mame0140

Given these items, could it be that the age of the CHDs aren't compatible with the ROMset? Or is it a Windows 7 issue, maybe with permissions?

Thanks to anyone that can give me some insight!

-kyoke

Title: Re: CHD Problem --- Windows 7? CHD set too old?
Post by: Paul Olson on January 11, 2011, 01:03:29 pm

You really need to update the CHDs to the MAME version you are using. Clrmamepro should be able to do that for you (renaming mostly, if there have been chds released since you downloaded your set, you will need to dl those). Did you check the chd box in clrmamepro? It should be able to scan for them.

Title: Re: CHD Problem --- Windows 7? CHD set too old?
Post by: kyoke on January 11, 2011, 01:55:27 pm

Thanks for your quick response. I'm in the process of getting the newest (0.141) CHD set.

Would the old CHD set cause "Missing" errors in RomCenter, even though the correct CHD folder/filename is available?

Title: Re: CHD Problem --- Windows 7? CHD set too old?
Post by: Donkbaca on January 11, 2011, 02:07:27 pm

I had this problem, I deleted the games in the diff folder and they worked great.

Title: Re: CHD Problem --- Windows 7? CHD set too old?
Post by: cdbrown on January 11, 2011, 09:30:03 pm

Even though the CHD might be there, mamedev may have changed the name slightly or redumped it which would change the md5 key.  There are ways to fix it using the chdman program along with the update files.  Or just like you are doing - redownloading the lot.