Please login or register.

Login with username, password and session length
Advanced search  


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.

Messages - Roman

Pages: [1] 2 3 4 5 6 ... 136
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.

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.

clrmame Discussion / Re: Language selection in 1G1R mode
« on: 22 March 2020, 08:30 »
most likely you need multiple release elements

release name="xxx" region="EUR" language="De"
release name="xxx" region="EUR" language="En"

the latest nightly is from march 8th 2020.
for your path problems I need more info...turn off the fix options and let me know what the scanner tree says

A set is always a parent unless it's a clone ;-)

clrmame Discussion / Re: dir2dat and CHDs in 4.036a
« on: 08 March 2020, 16:48 »
just a quick note, next nightly build will have a "keep chds as roms" switch....

ah...nice finding....found and fixed ;-)
Will be included in next nightly build......later today

clrmame Discussion / Re: TOSEC folder structure
« on: 08 March 2020, 07:59 »
Well, I've checked the latest TOSEC pack and since they use " - " as separator in the dat header like "Commodore Amiga - Games - Public Domain - [ADF]", there is no "subfolder" definition in there. I can check if it's easy to add something like an "treat - as subfolder" option.......but iirc they used real subfolders in the past (ok, last time I've checked was most likely 10 years ago...)

thanks. I'm able to reproduce the problem with Mint.....so that's a good start to fix it ;-)

ok...virtual box setup, linux mint 19.3 64 bit installed.....installed latest wine stable (5.0) and ran cmpro 4.036a. Loading a mame datfile (e.g. from progetto snaps page) works fine.

I can see in your screenshot that it shows "building prefered names" which indicates that you use a set with 1g1r mode possibilities. Which dat are you using? Can you send it please, so I can test that one

clrmame Discussion / Re: ZIP compression level
« on: 07 March 2020, 18:56 »
erm....if you scan an empty path you get an empty path afterwards...unless you got fix-missing enabled which looks into your setup addpaths, the rompaths and the backup path for something which might be the missing file and adds it.
But nothing, really not a single bit gets over the line (unless you use network drives ;-))

no trick, I guess I used Ubuntu 18.04 LTS last time...but as I said, as soon as I installed a virtual machine with Mint 19.3, I give it a try....

clrmame Discussion / Re: ZIP compression level
« on: 07 March 2020, 16:36 »
"by the end of that scan CMP has downloaded some missing bits and pieces"

eeeeh...what? cmpro does not download anything by the end of a scan...
What makes you think that cmpro download anything?

well, yes you can give the latest nightly a try but in general the wine fixes in there are for some specific thread api call which causes problems on Macs (and would appear earlier and not during loading a profile).
During that Mac issue I tried it on Ubuntu/Wine and it went well....but I give Mint a try as soon as I find a little time.

clrmame Discussion / Re: ZIP compression level
« on: 07 March 2020, 11:43 »
"I'm still scratching my head about against what the initial - empty, so to speak - scan runs.
That is: yes I'm left with the difference, but the difference between the datfile at hand and.. what?"

erm...I don't get that part? what do you mean with "initial" scan run?

clrmame Discussion / Re: ZIP compression level
« on: 06 March 2020, 17:25 »
The usual method of updating is:
Load the updated dat/profile
Scanner, run a full scan with all fix options on
After that you should only have missing stuff left
Then drag'n drop the "new" stuff into the scanner window...
(this internally runs a rebuild operation, which adds the new stuff to your collection, if your rebuilder destination points to your rompath)

So normally, on a modern system (SSD, fast CPU), a MAME update is done within minutes.....

clrmame Discussion / Re: ZIP compression level
« on: 06 March 2020, 14:14 »
you mean the 3 users out there who run rebuild jobs which take longer than half an hour ;-)
hehehehe......good to hear it helped you.

clrmame Discussion / Re: ZIP compression level
« on: 05 March 2020, 14:43 »
lucky you....


Packer_Zip_CompressionLevel = 9

clrmame Discussion / Re: cmpro not removed unneeded chds
« on: 05 March 2020, 13:41 »
I don't see a problem.

I've created a romfolder "test", added a subfolder in there named "4ddrivin", added your "old" file in there and renamed it to "4d driving (japan).chd". Created a new profile based on your datfile, added the romfolder "test" and ran a scan.
The file gets listed as:

wrong chd sha1: 4d driving (japan).chd [wrong: b09e774be4ee926dc32efd2e3b28dd72bc223c76] [right: 68794807a59b1095c2b10bf2e6a4da3eb6371f8f]
unneeded diskimage: E:\Temp\test\4ddrivin\4d driving (japan).chd

So I turned on the fix options and the file gets MOVED to the backup folder.
Even if you keep your old file in there (without renaming) and put the new one there in addition, it works fine and moves the file.

If it fails for you on your system, there might go something wrong during the move/delete part (e.g. access rights).

So...no problem here.

Pages: [1] 2 3 4 5 6 ... 136

Page created in 0.182 seconds with 20 queries.