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.

61

clrmame Discussion / Re: [SCANNER] Questions about filtering sets (filters, syntax, ecc)

« on: 20 May 2020, 20:28 »

Hey Roman!

catver.ini, no but in setinformation you can load a file with setnames to filter (From File)

Let's see if I understood correctly... When you say setnames and (From File), you mean a *.txt file with inside what? ...    I mean, I don't need filtering particular stes by their names, I need to filter them by DAT' nodes... I'm a little confused... 

62

clrmame Discussion / [UNSOLVABLE] Rebuilding CHD with progettoSNAPS' DATs

« on: 20 May 2020, 20:23 »

Hey!
I just discover today that there are dedicated DATs for CHDs-only (progettoSNAPS).
Now... I have a lots of scattered CHDs in various folders in my external HDDs.
I don't want to do manual work by checking CHDs and copy/paste in my main roms folders.

I tried using that CHD-DAT, but Rebuilder and also Scanner do nothing.
Rebuilder only shows me the list of vaild CHDs.
I'm using tha DAT ad a "roms" DAT, so my ROMPath is CHD destination and ADD-Paths have all my folders with various CHDs.

Can you please help me??

Thanks, bye!! 

63

clrmame Discussion / [SOLVED] Questions about filtering sets in SCANNER (filters, syntax, ecc)

« on: 20 May 2020, 20:09 »

Hi to all cmamep guys!! 

As in topic's title: I'd like to learn how to properly filter my sets in Scanner before going on with useless rebuilding.
What is the syntax to use? Where can I set desired filters? 

I'd like to filter my sets using node from DATs to exclude all  "driver status="preliminary"". I know, I'm aware of the "risks" of filtering sets with this, I am ok with that.

Also, please tell me if it's good to unset [MECHANICAL] from Scanner--->Systems, or should I take extra steps?

And also: could cmamep take advantage of catver.ini (from AntoPISA' progettoSNAPS) to help users filter their sets?


Many many thanks!!
Bye

64

clrmame Discussion / Re: [SOLVED] chdman v4 > v5 changes SHA1, clrmamepro reports wrong chd sha1sum

« on: 14 April 2020, 13:54 »

After years of my goodbye to MAME (around 2005 ~ 2006 I guess) I'm rediscovering all my old backups and returning to this dark side of (MAME) emulation... Eh eh eh
Just to pass the time while remainig home due to COVID-19...

A lot of things changed in MAME world, btw!

65

clrmame Discussion / Re: [CMPRO SETTINGS] "Adv_ShareRead=" and "Adv_ShareWrite="

« on: 14 April 2020, 12:11 »

Ok!

66

clrmame Discussion / Re: chdman v4 > v5 changes SHA1 (NO Data), and so clrmamepro reports wrong chd

« on: 14 April 2020, 12:09 »

And then I'll uncheck "List CHD version mismatches during scan" (Settings>Compressor>CHDMAN)! 


Thanks Roman!

67

clrmame Discussion / Re: chdman v4 > v5 changes SHA1 (NO Data), and so clrmamepro reports wrong chd

« on: 14 April 2020, 11:31 »

Yup, you're right... I know, but...
See if I'm right with this example:

• Scanner finds a correct CHD, and gives a softwarning about version mismatch (when there is one)
• Scanner saves that CHD entry (I mean CHD name and alos set name) in cmamep database and associate to that both SHA1 and Data SHA1
• With chdman -copy will the change CHD version
• SHA1 changes, Data SHA1 not
• Scanner finds the new CHD (changed version) and gives only a softwarning because SHA1 changed, but in cmamep' internal database the Scanner knows that CHD is working because it also checks for Data SHA1

You think it's worth adding in cmamep?


Bye!

68

clrmame Discussion / [CMPRO SETTINGS] "Adv_ShareRead=" and "Adv_ShareWrite="

« on: 14 April 2020, 11:14 »

Hey Roman!
As in title: what are these options for...?

Do I need to change or care about them?
What changes if I set them to on? ... I tried, but I see no changes 


Thanks!

69

clrmame Discussion / Re: chdman v4 > v5 changes SHA1 (NO Data), and so clrmamepro reports wrong chd

« on: 14 April 2020, 11:08 »

calling chdman internally (I'm not sure if running an exe works in a WINE environment, it surely does under Windows...)

I can confrim it works! 100% sure 
You first need to define the correct path to chdman.exe in settings (or via cmpro.ini)... Then when the Scanner calls chdman internally the WINE environment brings up chdman.exe correctly 

Code: [Select]

[CMPRO SETTINGS]
[...]
Packer_ChdMan_Exe = C:\Program Files\mame0174\chdman.exe
[...]
Btw, Roman, is there a way to add a feature in cmamep to do the doublecheck between SHA1 and Data SHA1?
Are you intereted in adding it? 

70

clrmame Discussion / [SOLVED] chdman v4 > v5 changes SHA1, clrmamepro reports wrong chd sha1sum

« on: 14 April 2020, 09:25 »

Hey Roman, congrats for you huge work with that nice piece of software which is cmamep... It's super! 
And also fits really nice in Linux via WINE! 

As in title, I'd like to have a clarification by you, please be so kind!

I'm using Latest Nightly Build.
So... I found some CHDs have mismatch version for what I say in cmamep to check against to.
Some of them are v4 and some others are v5.
I tried and done some experiments... 'Cause I'd like to have all CHDs converted to v5! 
If I change the version to v4 to v5 the SHA1 also changes, and cmamep found a wrong CHD entry (before conversion, that CHD was was recognized as correct).

Here's to you what happens:

Code: [Select]

ls *.chd | parallel chdman info -i {}               
chdman - MAME Compressed Hunks of Data (CHD) manager 0.218 (unknown)
Input file:   gdl-0012.chd
File Version: 4
Logical size: 1,344,333,888 bytes
Hunk Size:    9,792 bytes
Total Hunks:  137,289
Unit Size:    2,448 bytes
Total Units:  549,156
Compression:  zlib (Deflate)
CHD size:     110,731,452 bytes
Ratio:        8.2%
SHA1:         aae4c1321fdee37d5405c6cbe648e0596624ed13
Data SHA1:    6326b21cfdc04490eb0ba82bc15d2fbc1ac8fac8
[...]

chdman - MAME Compressed Hunks of Data (CHD) manager 0.218 (unknown)
Input file:   gdl-0012v50174.chd
File Version: 5
Logical size: 1,344,333,888 bytes
Hunk Size:    9,792 bytes
Total Hunks:  137,289
Unit Size:    2,448 bytes
Total Units:  549,156
Compression:  cdlz (CD LZMA), cdzl (CD Deflate), cdfl (CD FLAC)
CHD size:     66,551,507 bytes
Ratio:        5.0%
SHA1:         d2097461b5c6cffca5214a4fc7c685e5b620c156
Data SHA1:    6326b21cfdc04490eb0ba82bc15d2fbc1ac8fac8
[...]

chdman - MAME Compressed Hunks of Data (CHD) manager 0.218 (unknown)
Input file:   gdl-0012v50218.chd
File Version: 5
Logical size: 1,344,333,888 bytes
Hunk Size:    9,792 bytes
Total Hunks:  137,289
Unit Size:    2,448 bytes
Total Units:  549,156
Compression:  cdlz (CD LZMA), cdzl (CD Deflate), cdfl (CD FLAC)
CHD size:     66,551,507 bytes
Ratio:        5.0%
SHA1:         d2097461b5c6cffca5214a4fc7c685e5b620c156
Data SHA1:    6326b21cfdc04490eb0ba82bc15d2fbc1ac8fac8
[...]
Is this a normal behaviour? I mean, MAME uses only SHA1 in its xml list to check CHD's datas' correctness?
Or cmamep can also verify internal SHA1 (Data SHA1)?

I did a test with some settings in Scanner, with no luck  :'(



Thanks, bye!!