EMULAB Forum

Please login or register.

Login with username, password and session length
Advanced search  

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.

Messages - Roman

Pages: 1 2 [3] 4 5 6 7 8 ... 158
41
"Why someone would not to parse the merge attribute (as declared inside M. A. M. E.'s XML) of a clone's rom name?"

Let's get back in time....clrmamepro was there before merging was there....and parent/clone relationships did exist before mamedevs introduced merge attributes. And there was a time where merge attributes were completely wrong or each rom had one and so on....back then it was not so reliable as today.
So...coming back from such ancient times, there needed to be a way to see which roms were shared and which were unique within a parent/clone relationship. clrmamepro did that by hash and name compare, i.e. identical hashes with different names were still 2 unique roms. And that's exactly what happens when you disable that option (which is enabled by default by the way). So it's a just a different way of finding out which roms are and which aren't shared.
Same applies for disk merge attributes.


"Hash Collision"

There are parent/clonerelations where roms have identical names but different hashes. So if you fully merge them, one gets overwritten. Unless you put them in subfolders. MAME would load them fine in subfolders when you use 7z/zips. So to prevent data loss when using full merged sets, cmpro can create such a subfolder for you (usually the name of the set but you can change it). "Single File" means, only the file in question gets the subfolder, single clone means, all (clone) files belonging to the clone with the hashcollision get the subfolder, "all clones in relationship" means, all clone files (there can be n clones for 1 parent) get the subfolder. So this option is more a matter of taste/cosmetics, e.g. if you want all or just single files with a subfolder.
"Normal mode" means, that only the set with a hash collision gets subfolders while "Hash Collision Name" means all sets (no matter if they have a collision or not". So with the latter one, you store your fully merged sets where the parent holds its roms on root level of the archive and each clone has a subfolder on its own.


"Your example"
It is correct for split merge mode.
For full merge mode, you wouldn't have mame/hotd4a/dvp-0003a.chd since it's a clone and also for chds, you would put them to the parent...so you'd have mame/hotd4/dvp-0003a.chd and mame/hotd4/dvp-0003b.chd.


Last but not least: This storing mechanism and tricks with subfolders to prevent overwriting of hash collisions isn't defined. MAME itself doesn't care. It follows the romof and deviceRef chain to locate files and doesn't care about names when loading, it loads by hash compare (at least when we talk about archived files).

42
clrmame Discussion / Re: Exclude a whole driver?
« on: 24 August 2022, 17:49 »
yeah..just saw the cpp files ;-)

43
clrmame Discussion / Re: Exclude a whole driver?
« on: 24 August 2022, 17:46 »
hi John,

no...I didn't hear yet....(makes me a bit nervous though...)

You can exclude on source file name.....for example:
Scanner->SetInformation->SelectSets->%s=konami/kpython.cpp -> Apply
This would enable the kpython.cpp ones.... Then hit invert (so you get all enabled except the kpython ones) and check "initial invert" (so this simulates the invert click on each startup)


update: Hmm...I see some driver updates...with some ;-) new machines....and a software list....time to get some more hd space I guess

44
Powershell redirects data in utf16 by default (and redirecting is very slow in powershell, too).
So you need to run it with utf8 encoding in powershell:

mame.exe -listxml | out-file mame.xml -encoding utf8

If you only need to use the data in clrmamepro, you don't even need to run this manually, you can simply use Profiler->Create and let cmpro point to your mame exe file.

45
????
What file are you talking about?
The full driver xml from the official page (https://github.com/mamedev/mame/releases/download/mame0246/mame0246lx.zip) works fine and also a simple redirected mame -listxml.

Maybe you've compiled one yourself and the -listxml output is simply broken/incomplete (which can happen on not clean compiles).

46
clrmame Discussion / clrmamepro 4.046b released
« on: 18 August 2022, 14:01 »
4.046b
fixed: unsorted disk array can rarely cause random unneeded chd messages

47
clrmame Discussion / Re: clrmamepro 4.046a released
« on: 18 August 2022, 13:20 »
thanks...ah found it...nice one....a wrong sorted chd vector (nocase instead of lowercase)...which only failed for your dat.....that's in since ages...nice finding

48
clrmame Discussion / Re: clrmamepro 4.046a released
« on: 18 August 2022, 04:48 »
Can you give me a concrete example please? Which chd is stored where and is listed as unneeded. And since you mentioned a datfile, can you send me that one plus the belonging .cmp file from cmpro‘s settings folder and cmpro.ini please.

49
clrmame Discussion / Rebuilder 0.02 released
« on: 16 August 2022, 15:25 »
2022-08-16 V0.02 released
- since MAME can't handle subfolders in decompressed sets, decompressed sets and chds are always stored flat in folders (no clone/dependency subfolders in full or standalone mode). When kept compressed, the archives will hold subfolders
- not existing romOf reference leads to removed merge information for the machine

50
clrmame Discussion / clrmamepro 4.046a released
« on: 16 August 2022, 13:41 »
4.046a
fixed: support for other sample extensions is broken
fixed: more compatibility for standalone rebuilder tool in handling disk names  in full merged mode (hash collision mode) (revert in 4.046a)
fixed: more compatibility for standalone rebuilder tool in handling of devices with romof attributes in full merged mode
misc: updated 7zip sdk/dll tp 2201

51
clrmame Discussion / Re: clrmamepro 4.046 released
« on: 15 August 2022, 23:08 »
ok...I just saw that MAME itself can't load clone chds from a subfolder. I will rollback that disk requirement in hash collision name mode.
gimme a day

52
clrmame Discussion / Re: clrmamepro 4.046 released
« on: 15 August 2022, 17:11 »
no I did not...if you'd follow the right storing method you'd fine :-)

fix-missing is your problem...so for now, turn if off till I've fixed it...you can solve your problem manually or with the new rebuilder anyhow ;-)

53
clrmame Discussion / Re: clrmamepro 4.046 released
« on: 15 August 2022, 16:55 »
ok..gimme a second....the fix-missing (which is causing the trouble) seems to have a problem when creating the new subs...

54
clrmame Discussion / Re: clrmamepro 4.046 released
« on: 15 August 2022, 16:07 »
It does not want to move chd files.

It simply does not find them since you store them not correctly (for the hash collision mode). And then "fix missing" thinks it needs to do its work, detects the missing one and tries to add them. And since chds belong to a rompath, it tries to put them where it finds they fit best and that's most likely the place where your roms are stored (separating chds from their sets is..erm...well...your taste).

So...fix-missing is the problem for you....missing check detects a missing chd, fix missing finds it somewhere and adds it (it never moved files).

So turn it fix missing off...of course this fixes your storage pattern. This can then be done either manually or you can use the standalone rebuilder on your chd folder to rebuild the files in full merge mode to a new folder....(if this is on the same hd, this can take a while...)

55
clrmame Discussion / Re: clrmamepro 4.046 released
« on: 15 August 2022, 15:26 »
There is nothing wrong.

You're using not using the normal full merge mode but the "hash collision mode" one, i.e. all clone files are in subfolders of the parent.
In the past this was only done for roms (so you got subfolders in your zipfiles) while disks were simply forgotten. This has changed now and disks follow the same pattern.

So to answer your first post "this build separate Mame CHDs ( full merge mode) in subfolders" -> yes, it's intended.

Regarding your second post "cmpro wanna move mame chds to roms folder" -> no, it tried to fix a missing one and fix missing tries to add it to a suitable place. A suitable place is a rompath since chds are stored in rompaths. The problem arises since your current storage pattern for disks does not match the "hash collision mode". So you may need to manually adjust the paths a bit or turn off fix-missing or maybe changing the order of the rompaths (the one with chds at first) may help.


So in your example, the correct storing pattern would be: your_rompath\aa3010\aa3020\riscos311_apps.chd

56
clrmame Discussion / Re: clrmamepro 4.046 released
« on: 15 August 2022, 04:50 »
Yes but that's intended for an enabled Settings->Full Merge Mode -> Hash Collision Name

57
clrmame Discussion / clrmamepro 4.046 released
« on: 14 August 2022, 16:48 »
4.046
fixed: support for other sample extensions is broken
fixed: more compatibility for standalone rebuilder tool in handling disk names  in full merged mode (hash collision mode)
fixed: more compatibility for standalone rebuilder tool in handling of devices with romof attributes in full merged mode
misc: updated 7zip sdk/dll tp 2201

58
clrmame Discussion / Re: Cmpro "misplaced a romset" !?
« on: 12 August 2022, 06:31 »
hmm...interesting...however I don't think it was your setup....must be some old weird random bug somewhere.....hard to say as long as I can't repeat it myself.....I still got your cmp files so I will do some more testing I guess.....but good to see it's back working for you

59
clrmame Discussion / Re: Cmpro "misplaced a romset" !?
« on: 09 August 2022, 16:21 »
Thanks for the files...unfortunately I cannot repeat your problem at all yet, I will however do some more tests.

Just for a test, untick the addpath or try to setup a new profile from scratch.

Since you only have 1 rompath, you can also disable the use of system default paths (System->unbind all)

60
clrmame Discussion / Re: Cmpro "misplaced a romset" !?
« on: 09 August 2022, 08:38 »
can you send me:

cmpro.ini and the .cmp file from cmpro's settings folder which belongs to your profile. I assume you've imported the data directly from a MAME binary (if not, also add the used datfile). And I assume that you're not importing softwarelists

Pages: 1 2 [3] 4 5 6 7 8 ... 158

Page created in 0.116 seconds with 20 queries.

anything
anything