Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

1

clrmame Discussion / Re: Strange issue with No-Intro DATs

« on: 04 February 2020, 08:44 »

Thanks Roman, OK yes I will do that tonight when I get home.

2

clrmame Discussion / Re: Strange issue with No-Intro DATs

« on: 02 February 2020, 16:30 »

Ah wait a sec, I think you mean here don't you? I've not seen this screen before. I think that is where I'm going wrong!

3

clrmame Discussion / Re: Strange issue with No-Intro DATs

« on: 02 February 2020, 10:35 »

Thanks for the reply, yes I have been using the re-builder, but I'm sure in the past the scanner used to fix based on hash check. I do actually already have the option you mentioned turned on (see image) but it's still not checking. It's no major biggie just wanted to check.

4

clrmame Discussion / Strange issue with No-Intro DATs

« on: 02 February 2020, 09:55 »

I use CLRMame Pro mainly for updating my No-Intro sets.I have started noticing a strange issue. I am using the latest version (4.036a), this is what's happening.

I open the DAT in CMP then go to settings and set the ROM and ADD paths. I then go to Scanner and tick all the options to repair/change. I do a scan of my ROM path, but if there is a missing ROM in the ADD path that does not match the name in the DAT it does not rebuild the ROM even though the CRC32 hash is correct, so its the correct ROM but it does not rebuild it. I have to manually change the name of the ROM for it to rebuild it to the ROM path.

I'm sure I never used to have this issue.  Any ideas?

I thank you in advance for any help you may be able to offer.