1
clrmame Discussion / Re: cmnpro 4.034 released
« on: 11 May 2018, 18:58 »
I see... I noticed this when I press "Alt+Tab" to switch to another window. It pauses then for me. Maybe WINE handles this wrong...
- 01 May 2025, 16:02
- Welcome, Guest
News:
The new forum is online, hope you enjoy it!
Show Posts
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.
Pages: [1]
2
clrmame Discussion / Re: cmnpro 4.034 released
« on: 11 May 2018, 18:28 »
I am using clrmamepro in WINE... when I press the Alt-Key while clrmamepro scans or rebuild it pauses completely. It starts working again when I click on the window.
Is this "normal"?
Is this "normal"?
3
clrmame Discussion / Re: Header-File Rule-Tests are ignored?
« on: 02 September 2017, 10:23 »
Ah I see. Yes, my assumption was wrong. The checksum of the headerless file matches the dat file and if ClrMamePro detects "NES" in that file it skippes a couple of bytes.
So for me, if I want a collection with headers only I could remove that data test. ClrMamePro should now always skip the offset and every file without a header should now mismatch.
The only problem are BIOS files now which have no header. I could try to set a size test here. A name test for "starting with '[BIOS]'" would be nice.
The thing is, I want a clear distinction between "headered" and "headerless". A mode like I assumed in my starting post. "If there is a header, skip it for checksum calculation, but reject the file if there is no header"... well... except for BIOS files.
So for me, if I want a collection with headers only I could remove that data test. ClrMamePro should now always skip the offset and every file without a header should now mismatch.
The only problem are BIOS files now which have no header. I could try to set a size test here. A name test for "starting with '[BIOS]'" would be nice.
The thing is, I want a clear distinction between "headered" and "headerless". A mode like I assumed in my starting post. "If there is a header, skip it for checksum calculation, but reject the file if there is no header"... well... except for BIOS files.
4
clrmame Discussion / Header-File Rule-Tests are ignored?
« on: 02 September 2017, 02:13 »
Hello.
Lets say I have a NES headless ROM-Set. So no file starts with "NES" if I check them with a HEX-Editor. Then I download the No-Intro NES dat file with the no-intro_NES.xml header file for ClrMamePro. I put the no-intro_NES.xml into the headers directory.
The header file itself says:
So at the beginning of the file there has to be the value "NES". When I add the datfile to ClrMamePro it asks me to enable Header Support. I click Yes.
If I start up the Rebuilder and rebuild the headerless ROM-Set ClrMamePro should now find no files since all are missing the NES value at the beginning.
But for me ClrMamePro matches & rebuilds all files. Did I do something wrong?
Lets say I have a NES headless ROM-Set. So no file starts with "NES" if I check them with a HEX-Editor. Then I download the No-Intro NES dat file with the no-intro_NES.xml header file for ClrMamePro. I put the no-intro_NES.xml into the headers directory.
The header file itself says:
Code: [Select]
<rule start_offset="10">
<data offset="0" value="4E4553"/>
</rule>
So at the beginning of the file there has to be the value "NES". When I add the datfile to ClrMamePro it asks me to enable Header Support. I click Yes.
If I start up the Rebuilder and rebuild the headerless ROM-Set ClrMamePro should now find no files since all are missing the NES value at the beginning.
But for me ClrMamePro matches & rebuilds all files. Did I do something wrong?
Pages: [1]