EMULAB Forum
clrmamepro [English] => clrmame Discussion => Topic started by: oddi on 04 June 2022, 09:45
-
Roman, what is that "misplaced a romset", i have this sets, use cmpro 4.044d
(https://i.postimg.cc/ZKNw86Vk/2022-06-04-124154.jpg)
-
Roman, what is that "misplaced a romset", i have this sets, use cmpro 4.044d
(https://i.postimg.cc/ZKNw86Vk/2022-06-04-124154.jpg)
I can confirm oddi's findings as I have the exact same....error?
Clrmame pro version 4.044d
Mame roms - merged sets
Tried removing and rebuilding but same error occurs.
Cheers,
RCade
-
Those are all systems, not roms.
They should be in your "software" folder & unpacked since that zip is probably already full of zipped files for the system...
-
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.
-
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.
Hi Roman,
These were from Mame's main rom set (not software list). I've shamelessly rolled back to 4.044c and this has resolved the misplaced issue.
To add more information, I compiled latest commit from Mames github (cant confirm if oddi did the same) and updated to 4.044d and thats when I noticed the misplaced romsets.
Anything else I can help wih please let me know.
Thanks again.
-
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.
-
Hello Roman, me too tested with the last mame git, result:
with 4.044c --> it's ok
with 4.044d --> above issue
Thank you :)
-
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.
-
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?
-
Roman,
Thanks for point out that ti detects unneeded sets. I removed those files from the roms folder (put them into a temporary folder in case I need them at some point). The "unneeded sets" errors no longer appear in clrmamepro, but I still have the "missing set" errors (makes sense since those aren't in the roms directory anymore). Note that I did NOT import software lists into clrmamepro.
What's curious are some of the results: It shows an error for "Famicom (folder: famicom - size 0)" with subitem "missing set: Famicom" ---- does does "folder: famicom - size 0" mean? Just an empty folder under the "roms" directory? If I create an empty "famicom" folder, it still complains about it.
-
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.
Hi Roman,
I dont use any software lists as mentioned before as these files are from Mame's main rom set. I use mame's exe direct in clrmame.
I've removed the files shown as misplaced, updated to clrmame pro 4.044d and done another merged set scan and all now show as missing. I have noticed that the parent set of each has a 0 file size whereas the clone of each does have a file size associated with it. Not sure if this is the problem or not?
Ninja'd by paultup :)
-
ah ok....."full merged" ...that was the information which was missing....I'm able to repeat it....so assume it will be fixed soon
-
ah ok....."full merged" ...that was the information which was missing....I'm able to repeat it....so assume it will be fixed soon
Ah, apologies Roman. Thought I had included that info but clearly not :)
Thanks for looking at this.
-
no prob....and yes, keep your backups :)
-
OK, I just download Roman's 4.045 and tried running it again... the "unneeded sets" issue doesn't appear, but it's still giving me the same "missing set" and "missing rom" errors for all the files mentioned above. I have confirmed those .zip files are in my roms directory (and the "missing roms" are actually within that ZIP file)
The common factor I see: Each one of these sets include an embedded clone set (abp/abpv2, famicom/famitwin/nes, genesis/genesis_tmss, etc.) which has an embedded folder within the .zip file.
My clrmamepro setup:
* Prefer merged sets
* Scan sets/ROMs/samples/CHDs
* Check and fix ALL types (Missing, Case, etc.)
* Separate BIOS sets is checked
- Paultup
-
Move them elsewhere and let the rebuilder readd them with recompression enabled.
-
Roman,
That took care of the issue - thank you!!!
- Paultup
-
Move them elsewhere and let the rebuilder readd them with recompression enabled.
So I've had this issue since 4.045 and tried to fix.
same settings ;
My clrmamepro setup:
* Prefer merged sets
* Scan sets/ROMs/samples/CHDs
* Check and fix ALL types (Missing, Case, etc.)
* Separate BIOS sets is checked in (Rebuilder and Scanner)
Delete ARB.ZIP
Run 'New Scan'
'Set ARB V2 Sargon 4.0' 'do you want to add missing ROM'
Yes
Recreates ARB.ZIP in ROMS folder
Move
ARB.ZIP to add-paths folder
Run rebuilder, rebuilds ARB.ZIP to ROMs folder
Run scanner, 'misplaced ARB.ZIP' comes up again
'Set ARB V2 Sargon 4.0' 'do you want to add missing ROM'
and repeat .....
what's wrong. how did Paultup fix it. I tried every fix mentioned here.
Help
-
I can check it next weekend.
-
arb (the parent) itself does not have any roms on its own.
It only consists of device_refs. The clone (arbv2) has exactly 1 rom "sargon_4.0".
So all you need is a zip file, named arb.zip which holds that one rom (name="sargon_4.0" size="65536" crc="c519c9e8" sha1="d7597d50c0f4f9aa6d990c8d3b485e39cb44ff06").
If you still get a message about a misplaced set, you may want to check if you got an arbv2 or arb folder in one of your rompaths or your equally named zipfiles somewhere. You can also try to clean the profiler cache and reget the data from an official mame binary. And then do a new full scan.
What makes me wonder is that you always mention an uppercase ARB, while in MAME it's definetly lowercase...or maybe you just use uppercase yourself here...
-
I've checked all the folders I use, which is just one for ROMS and a couple for Add-paths, only 1 zip exists with correct info as you mentioned below. (arb pic)
Cleared my cache and did a reload of mame 0.246 and then a full scan with 2nd picture (scan pic)
-
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
-
Yes, always import from the MAME binary (MameUI) each time new one released, clearing previous cache.
No don't use softwarelists.
Thanks again for your support.
-
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)
-
Will try fresh install from scratch, let's see what happens, thanks.
-
Just to let you know, after I did an uninstall and did a fresh install, this problem has gone?
So thanks for the help but obviously was my setup.
Thanks for your great program
-
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