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: Can't Load / Update from MESS 0.226

« on: 21 November 2020, 17:59 »

Load it as MAME, not as MESS.
The MESS exe type is for the "old" original MESS before MAME and MESS were merged.

2

clrmame Discussion / Re: Two Small Feature Requests

« on: 18 November 2020, 18:50 »

2) https://mamedev.emulab.it/clrmamepro/binaries/cmpro20201118.7z

3

clrmame Discussion / Re: 32k Path Length Issue

« on: 18 November 2020, 18:43 »

Fixed in next nightly....

funnily enough the path is exactly 260 chars long (which is identical to the system's MAX_PATH).
But hitting this means I have to auto add the 32k prefix stuff....so I had to change the check from < MAX_PATH to <= MAX_PATH

https://mamedev.emulab.it/clrmamepro/binaries/cmpro20201118.7z

4

clrmame Discussion / Re: Two Small Feature Requests

« on: 14 November 2020, 09:00 »

1) profiler context menu  -> Hide -> red/green/grey
2) oh yes...that's something I want too

5

clrmame Discussion / Re: 32k Path Length Issue

« on: 12 November 2020, 18:43 »

did you use the lastest nightly?

If no, try it. If yes, send me the dat, the file in question, your *.cmp file (cmpro's settings folder) and cmpro.ini

6

clrmame Discussion / Re: 4.038a - Extremely long scan time (titles.zip resource)

« on: 05 November 2020, 11:21 »

"Why did ClrMAMEPro re-zip them into the 7z archive?"

If it does that on your machine then you're using 7z archives. Simply as that.

cmpro autodetects how you stored your sets (either not compressed or rar/zip/7z). So you store your snaps in titles.7z it of course adds found missing files into that 7z. "Adding" can mean different operations. Adding from one zip archive to another takes no time since it copies the compressed data. Adding from a decompressed file to an archive takes compression time for that file. Adding to a solid 7z archive means repacking the full archive.

Again, for progretto snaps I'd go with decompressed sets (at least for checking).

7

clrmame Discussion / Re: 4.038a - Extremely long scan time (titles.zip resource)

« on: 04 November 2020, 06:03 »

Titles/Snaps/Bosses/etc etc don't have to be zipped/7z'ed/rar'ed at least not for checking. For the actual use it depends on the frontend.
Regarding fix progetto snaps, I usually do the following:
- run a scan with all fix options but fix missing
- use the rebuilder to add the update packs and if something is still missing you may rebuild the backup folder to readd stuff which was put there. Most of the time you end up with 100% if not you may want to take a manual look at it

8

clrmame Discussion / Re: 4.038a - Extremely long scan time (titles.zip resource)

« on: 03 November 2020, 18:20 »

If I add it yes, for now: no
For such 1 sets-100000 files sets it's currently better to follow my advice from the start of this post

9

clrmame Discussion / Re: 4.038a - Extremely long scan time (titles.zip resource)

« on: 03 November 2020, 05:38 »

Turn off fix missing and belonging advanced fixed missing options.

The reason is that progetto sets consist of 1 set with thousands of files and often it holds a pretty large amount of pngs placeholders (identical 'default' pngs). So if you miss them, cmpro looks into the set (and addpath, backup), finds it somewhere and adds it (recompress), then the next one...same procedure again...and again...when using compressed sets it's evil....when using solid 7z archives it's hell.

For progetto snaps it's better to add files with the rebuilder instead of using fixmissing...and consider simply using not compressed files instead of archived ones.

10

clrmame Discussion / Re: Missing ROMs but empty scan results

« on: 26 October 2020, 17:06 »

So what's confusing? fixing missing files works exactly like that.

hng64 missed 3 files and cmpro found the files in other places, so "fix missing" automatically added them and so hng64 won't appear in the scan results tree since it's ok now. If you don't turn on the fix options and you got the 3 files missing in hng64, you will see hng64 in the tree appearing. So it works as expected since the tree result only shows problems. The stats most likely shows something like 3/3 missed/fixed whatever.

cmpro looks in addpaths, backup folder and parent/clone relationship sets for missing files and in your case it found them somewhere there....

11

clrmame Discussion / Re: Missing ROMs but empty scan results

« on: 26 October 2020, 10:29 »

here we go: https://mamedev.emulab.it/clrmamepro/binaries/cmpro20201026a.7z

12

clrmame Discussion / Re: Missing ROMs but empty scan results

« on: 25 October 2020, 16:41 »

Well, I actually thought that your intention was to use not merged sets ;-)
...but there's a lack in your plan. Device sets. Nearly each set requires device sets, too...and they aren't put in a non merged sets and currently they are not handled like non-separated-biossets.
I already got requests to add something similar for device sets but had no time yet to add it.

For sure I will double check the missing tree print out very soon.

13

clrmame Discussion / Re: Missing ROMs but empty scan results

« on: 25 October 2020, 13:25 »

ok...I can now for sure tell you that your stats/scan results tree mismatch is based on the disabled "separate bios sets" option.

If this mode is enabled and the bios sets itself misses files (but all the sets using this bios got the bios files included already) show no entry in the scan results tree but stats count them as missing.
This is of course a wrong behaviour. It should list the bad bios set in the tree. I will check why it does not appear (for whatever reason cmpro might saw the existing files in the single sets and didn't pop out the bios itself).

Thanks for helping me by sending your config.....but you should really think about split merged mode and separated bios sets....you will gain diskspace.

14

clrmame Discussion / Re: Missing ROMs but empty scan results

« on: 25 October 2020, 13:18 »

One thing I've spotted in your settings is Scanner->Advanced -> you got "Separate BIOS sets" disabled. This means you waste pretty much space by keeping the bios files in each and any set instead of keeping them separated (e.g. each neogeo set keeps the neogeo bios files instead having 1 neogeo.zip holding them). Disabling that option is very very very rarely used...actually so rarely used that I can imagine it's the cause of your stats issues. I will do some checks on that option but you should turn that option on. The same option exists in rebuilder->advance.
And you're using non-merged sets...again, not a good idea. You waste a lot(!) diskspace and actually nobody uses this
The common modes are split merged or fully merged sets (split sets / merged sets).

So...really think about switching your merge mode to something common ;-)

Regarding chd versions...no luck here to repeat the behaviour yet.

15

clrmame Discussion / Re: Missing ROMs but empty scan results

« on: 25 October 2020, 12:19 »

Can you tell me a bit about your system?
Which OS (version, 32/64bit),  I can see that you store your data on drive D...what kind of drive is that?

If things happen randomly there is a chance that something interfears. There were cases in the past where bad samba network drivers caused issues or virusscanners simply blocked access and lead to weird results. Not to mention overclocked systems where RAM simply produced flipped bits here and then.
I don't say that your system has a problem but if you got the chance to test stuff on a different drive or machine, it would be interesting to see the results there.

But of course I will double check the chd version check (surely a not correctly initialized variable may cause random issues, too). But again.....no one else reported such kind of things..... ;-)

16

clrmame Discussion / Re: Missing ROMs but empty scan results

« on: 25 October 2020, 08:54 »

The chdversion problem sounds even more weird.
Since the chd file holds the version which is simply read and compared to the one which you've set in settings->compressor->chdman->req chd version.
Does it always show the same results or random?

If random it more sounds like a system problem where something is interfearing, where "something" can be anything from bad network drivers when the data is stored on a network drive, bad RAM/HD, virusscanner or other 3rd party tools interfearing etc..etc..
Don't worry, sounds more dangerours at it is....but such errors were never reported before.

17

clrmame Discussion / Re: Missing ROMs but empty scan results

« on: 24 October 2020, 18:24 »

Do you really miss the files in the log file or do they actually exist in your paths?

It's pretty normal that you need to run two scans to cleanup some stats/listed entries.
There are some rare cases where a first scan puts parts to the backup folder and a second one will add them back to their correct places. ...but still weird that you get an empty results tree and entries in the stats....never seen that one though.

can you send me your:
cmpro.ini
and the used dat (in case you didn't import from a mame binary) and the beloning *.cmp settings file for your used profile (in cmpro's settings folder).

18

clrmame Discussion / Re: Missing ROMs but empty scan results

« on: 24 October 2020, 17:05 »

Did some tests with 159 and 160...and I can't reproduce your problem. If the files are missing, they are listed in the tree.

19

clrmame Discussion / Re: Missing ROMs but empty scan results

« on: 24 October 2020, 11:21 »

But they definetly should appear as missing in the scan results tree if they were really missing (and all hide this, hide that, disable this/that was turned off).
I will do some tests

20

clrmame Discussion / Re: Missing ROMs but empty scan results

« on: 23 October 2020, 18:56 »

Did you give that version a try with your old MAME version? Would be interesting to see which roms are marked as missing