EMULAB Forum

clrmamepro [English] => clrmame Discussion => Topic started by: Interceptor on 01 February 2019, 13:10

Title: No-Intro header files are not recognized
Post by: Interceptor on 01 February 2019, 13:10

I did put the No-Intro header files into the headers directory.
I also tried selecting the header in settings headers.

But i always get the message that the dat needs a header file.
Tried it with NES and Lynx...

EDIT
You need to restart CMP then it works. Just refresh is not enough.

Title: Re: No-Intro header files are not recognized
Post by: Roman on 01 February 2019, 14:31

yeah...could be that headers are loaded during startup...can't remember at the moment but I can double check later at home

*update * ok...checked the source, yes...header xml files are only loaded on startup

Title: Re: No-Intro header files are not recognized
Post by: joaoluiz on 13 March 2020, 19:27

I had the same issue. Struggled with it for a while, and then found this thread. Restarting fixes it. Thank you.

Title: Re: No-Intro header files are not recognized
Post by: ikuzihsoyiroy on 23 March 2020, 21:23

Saturday ClrMame worked as usual. Tonight instead it wouldn't load any dats with header required.

Scan is always looking for files headerless.

Dats are different from many sets (XML format or Deprecated)

Dat Header instruction line is present.

Steps I followed:

Run it - Dat with headers (negative) - Exit

Run it - Reflesh list dats - Dat with headers (negative) - Exit

Run it - Using dat without headers - Dat with headers (negative) - Exit

Delete cache / fastscans / logs / scans / profiler.xml / cmpro.ini / profiler.cache / cmpro.ini / 

Run it - Reflesh list dats - Dat with headers (negative) - Exit

Dats were and are untouched from last 5 days.

CLRMame version is 4.0361 64bits.

I couldn't find any logical reason about this malfunction.

Bye

Title: Re: No-Intro header files are not recognized
Post by: Roman on 24 March 2020, 05:40

reboot your machine  :)

as you said, there is no logical reason. Header definitions need to be placed in cmpro's header folder, cmpro should be installed in a non-uac controlled path and not run with admin rights...that's basically at. Modifications in headerfiles or new ones get active when cmpro gets restarted.

So....assuming you haven't changed a single thing, there is no logical reason, so reboot ;-)
If you changed something or using a new datfile, do check the changes in detail.

Title: Re: No-Intro header files are not recognized
Post by: ikuzihsoyiroy on 24 March 2020, 10:43

Is there a command line debug logging?

Title: Re: No-Intro header files are not recognized
Post by: Roman on 24 March 2020, 12:10

Header support hasn't changed for a decade or more. I've just tested a clean install with no intro nes dat + header file and it works fine.

Maybe you should go to settings, switch the drop down box at the top (ROM-paths, ....) to "Header" and see if you got the header definitions enabled for your profile in question.

Title: Re: No-Intro header files are not recognized
Post by: ikuzihsoyiroy on 24 March 2020, 20:11

today I made a nes deprecated dat over actual set and it worked everything.

i didn't reinstall or modify anything about actual clrmame installation.

It's strange.

' (ROM-paths, ....) to "Header" and see if you got the header definitions enabled for your profile in question.

' It was enabled about old xml nes dat as the deprecated new one.