241
clrmame Discussion / Re: Cmpro "misplaced a romset" !?
« on: 06 June 2022, 19:36 »
Move them elsewhere and let the rebuilder readd them with recompression enabled.
- 16 April 2024, 05:29
- Welcome, Guest
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.
242
clrmame Discussion / clrmamepro 4.045 released
« on: 06 June 2022, 15:52 »
4.045
misc: updated to ZipArchive 4.6.8, unrar 6.11.100.427, 7Zip SDK/DLL 21.07
fixed: rarely list a set as missing when it does not contain any files on its own
fixed: 4.044d misplaced a romset regression (full merged sets only)
misc: updated to ZipArchive 4.6.8, unrar 6.11.100.427, 7Zip SDK/DLL 21.07
fixed: rarely list a set as missing when it does not contain any files on its own
fixed: 4.044d misplaced a romset regression (full merged sets only)
243
clrmame Discussion / Re: Cmpro "misplaced a romset" !?
« on: 06 June 2022, 12:14 »
no prob....and yes, keep your backups 
244
clrmame Discussion / Re: Cmpro "misplaced a romset" !?
« on: 06 June 2022, 11:19 »
ah ok....."full merged" ...that was the information which was missing....I'm able to repeat it....so assume it will be fixed soon
245
clrmame Discussion / Re: Cmpro "misplaced a romset" !?
« on: 06 June 2022, 10:52 »
Do you use a MAME import with or without softwarelist import?
What's your settings (would be great to send over cmpro.ini and the profile's .cmp file from cmpro's settings folder).
And...do you have an actual nes.zip, sc3000.zip etc on your disk? And what does it contain?
What's your settings (would be great to send over cmpro.ini and the profile's .cmp file from cmpro's settings folder).
And...do you have an actual nes.zip, sc3000.zip etc on your disk? And what does it contain?
246
clrmame Discussion / Re: loveber3cn Missing Set ARXMAX
« on: 06 June 2022, 10:43 »
Found your loveber3cn problem.
It normally doesn't pop up due to the unique chd for that clone. Since you're using a dat which does not use chds, a different issue is visible now.
It's gonna be fixed with the next release.
The reason...oh well....there's a flag which sees if a set does not need to exists (e.g. only devicerefs, only parent roms in a clone, only nodumps, etc) and that flag was set falsely in that case since loveber3cn references one bios file which its parent did not use at all...etc...blablab.... ;-)) Anyhow....it will be fixed.
It normally doesn't pop up due to the unique chd for that clone. Since you're using a dat which does not use chds, a different issue is visible now.
It's gonna be fixed with the next release.
The reason...oh well....there's a flag which sees if a set does not need to exists (e.g. only devicerefs, only parent roms in a clone, only nodumps, etc) and that flag was set falsely in that case since loveber3cn references one bios file which its parent did not use at all...etc...blablab.... ;-)) Anyhow....it will be fixed.
247
clrmame Discussion / Re: Cmpro "misplaced a romset" !?
« on: 06 June 2022, 09:00 »
You did read
https://www.emulab.it/forum/index.php?topic=6799.msg22037#msg22037
didn't you?
4.044d detects some unneeded sets which weren't detected before.
https://www.emulab.it/forum/index.php?topic=6799.msg22037#msg22037
didn't you?
4.044d detects some unneeded sets which weren't detected before.
248
clrmame Discussion / Re: Cmpro "misplaced a romset" !?
« on: 06 June 2022, 08:16 »
Well yes, but they are not existing sets on their own. They are only referencing devices.
So if you got a nes.zip, genesis.zip etc on your disk, you don't need them and you can remove them.
That it shows "misplaced romset" instead of "unneeded" could be an indicator that you're using an additional softwarelist import instead of scanning software lists individually.
So if you got a nes.zip, genesis.zip etc on your disk, you don't need them and you can remove them.
That it shows "misplaced romset" instead of "unneeded" could be an indicator that you're using an additional softwarelist import instead of scanning software lists individually.
249
clrmame Discussion / Re: loveber3cn Missing Set ARXMAX
« on: 05 June 2022, 19:09 »
Thanks, due to weekend/holiday I will have a look at it later this coming week
250
clrmame Discussion / Re: Cmpro "misplaced a romset" !?
« on: 05 June 2022, 19:08 »
Nothing needs to be unpacked.
Are you using a full softwarelists import? Since such files which are listed as misplaced are not part of MAME (without softwarelists). In other words: For a non-softwarelist MAME, they can be removed. For a software list import MAME profile, they simply don't belong to your Mame_ROMs folder. You can manually move them away.
Are you using a full softwarelists import? Since such files which are listed as misplaced are not part of MAME (without softwarelists). In other words: For a non-softwarelist MAME, they can be removed. For a software list import MAME profile, they simply don't belong to your Mame_ROMs folder. You can manually move them away.
251
clrmame Discussion / Re: loveber3cn Missing Set ARXMAX
« on: 05 June 2022, 19:03 »
No set behaviour at all is hardcoded.
You said you're using a datfile without disks. Can you send me that one please.
You said you're using a datfile without disks. Can you send me that one please.
252
clrmame Discussion / Re: loveber3cn Missing Set ARXMAX
« on: 04 June 2022, 06:37 »
You're right, dinokich and others should also appear then. Why it doesn't do it for you...well....hard to say without knowning all your settings but most likely you have an empty dinokich folder in one of your rompaths which fools the set check. If the set check finds a folder or an archive with the name, the set check will be ok....an enabled chd check will of course tell you that the chd itself is missing though.
253
clrmame Discussion / Re: loveber3cn Missing Set ARXMAX
« on: 03 June 2022, 20:25 »
You need to differ between the meanings of the check options "sets" and "chds", "samples","roms".
The set check checks if the set is available or not. The chd check would only moan about wrong named or missing chds inside the set. A set is a collection of roms and/or samples and/or chds. The rom check would tell you if a rom inside a set is wrong named, wrong checksum etc....
The mentioned set only cosist of shared parent roms but it uses an unique chd. So actually you'd need a rompath subfolder named after your set with the chd in it.
Since you're missing that chd, the set is missing and so the output is right.
The set check checks if the set is available or not. The chd check would only moan about wrong named or missing chds inside the set. A set is a collection of roms and/or samples and/or chds. The rom check would tell you if a rom inside a set is wrong named, wrong checksum etc....
The mentioned set only cosist of shared parent roms but it uses an unique chd. So actually you'd need a rompath subfolder named after your set with the chd in it.
Since you're missing that chd, the set is missing and so the output is right.
254
clrmame Discussion / clrmamepro 4.044d released
« on: 01 June 2022, 19:02 »
while working on *something else* I found two little things in the old thingie....
4.044d (2022-06-01)
fixed: wrong bios set assignments for clones which don't use the bios roms themselves (pwrshovla, v4frfact*)
fixed: not showing files as unneeded which became empty sets over time (e.g. microvsn, mach64, msm6222b, o2_voice)
4.044d (2022-06-01)
fixed: wrong bios set assignments for clones which don't use the bios roms themselves (pwrshovla, v4frfact*)
fixed: not showing files as unneeded which became empty sets over time (e.g. microvsn, mach64, msm6222b, o2_voice)
255
clrmame Discussion / Re: Scanning multiple folders to make new zips of roms
« on: 10 May 2022, 06:00 »
The rebuilder is the solution.
Let the rebuilder source point to your "messy collection" and rebuilder destination to a new folder. Use a datfile (or MAME binary import) for the data basis you want to create your target sets for.
The rebuilder matches anything valid (hash compare) in the source, no matter how it is named and creates all instances of the matches in the destination. Of course this doesn't mean it will create complete sets, just anything valid which can be found.
The rebuilder also supports drag'n drop and/or multiple source folders (via add paths).
Let the rebuilder source point to your "messy collection" and rebuilder destination to a new folder. Use a datfile (or MAME binary import) for the data basis you want to create your target sets for.
The rebuilder matches anything valid (hash compare) in the source, no matter how it is named and creates all instances of the matches in the destination. Of course this doesn't mean it will create complete sets, just anything valid which can be found.
The rebuilder also supports drag'n drop and/or multiple source folders (via add paths).
256
clrmame Discussion / Re: Creating custom rom sets
« on: 14 April 2022, 12:20 »
the rebuilder only rebuilds roms
257
clrmame Discussion / Re: Creating custom rom sets
« on: 14 April 2022, 08:35 »
I only took a quick look at the page and I guess it selects sets and then does a rebuild. And I'd have proposed the same.
Assuming your collection is ok and on your cabinet you're using the same MAME binary as you're using to scan the collection in cmpro it's like this:
Scanner -> Scan Results -> Set Information, use "select sets" or "from file" or manual ticking the sets which you want (maybe also ticking incl. devices/bios/clone/parent checkboxes)
and then doing a rebuild in the rebuilder where the destination points to a new path (and not removing rebuilt files of course).
Assuming your collection is ok and on your cabinet you're using the same MAME binary as you're using to scan the collection in cmpro it's like this:
Scanner -> Scan Results -> Set Information, use "select sets" or "from file" or manual ticking the sets which you want (maybe also ticking incl. devices/bios/clone/parent checkboxes)
and then doing a rebuild in the rebuilder where the destination points to a new path (and not removing rebuilt files of course).
258
clrmame Discussion / Re: ClrMame Tutorial
« on: 12 April 2022, 17:53 »
No...I only wanted to point out that it follows a general storing schema (and MAME follows it too).
Either you have your sets in archives (.zip or .7z) OR you keep them decompressed.
Of course 99.99999999999% use archives.
Either you have your sets in archives (.zip or .7z) OR you keep them decompressed.
Of course 99.99999999999% use archives.
259
clrmame Discussion / Re: ClrMame Tutorial
« on: 12 April 2022, 17:42 »
You can convert your sets by using the rebuilder by the way......
(in case your sets are compressed as zip, you can disable "recompress" in the rebuilder options, so it should run rather fast (depending on your system))
The rebuilder takes everything from the source which matches entries in the loaded dat (match by hash) and creates all instances of that match in the destination. There it uses the correct name etc....
(in case your sets are compressed as zip, you can disable "recompress" in the rebuilder options, so it should run rather fast (depending on your system))
The rebuilder takes everything from the source which matches entries in the loaded dat (match by hash) and creates all instances of that match in the destination. There it uses the correct name etc....
260
clrmame Discussion / Re: ClrMame Tutorial
« on: 12 April 2022, 17:23 »
Unmerged is not "stand alone"...simply due to the device references.
Modern Frontends should all handle split or full merged sets (this is nothing new...)
So there is really no real need to use unmerged (unless I add a real stand alone mode).
I'd say the most common is split....and of course there are some hd-space-gurus who have everything fully merged in solid 7z archives (hey wake up....it's 2022 and TB of HD space is cheap... ;-))
You can turn off Scanner->Advanced -> separate bios sets...in case each of your sets really contains the bios files for their own....(yikes)....
but really....believe me: noone (should) use unmerged sets :-)
Modern Frontends should all handle split or full merged sets (this is nothing new...)
So there is really no real need to use unmerged (unless I add a real stand alone mode).
I'd say the most common is split....and of course there are some hd-space-gurus who have everything fully merged in solid 7z archives (hey wake up....it's 2022 and TB of HD space is cheap... ;-))
You can turn off Scanner->Advanced -> separate bios sets...in case each of your sets really contains the bios files for their own....(yikes)....
but really....believe me: noone (should) use unmerged sets :-)