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: CMPro64 4.029b (2016-06-19) doesn't move chd from root to folder

« on: 10 March 2023, 20:57 »

Thanks for the tips.
This is how I solve the problem with the rebuilder.

for /d %%i in (o:\ROMs\MAMESL\*) do (
  @echo %%~nxi
  @o:\emulator\clrmamepro\rebuilder.exe -i "o:\ROMs\backup\" -x o:\emulator\mame\hash\%%~nxi.xml -o "o:\ROMs\MAMESL\%%~nxi" -m full -r -d
)

2

clrmame Discussion / Re: CMPro64 4.029b (2016-06-19) doesn't move chd from root to folder

« on: 19 February 2023, 14:59 »

Just found this old topic reflecting the same issue happened nowadays.
wrong places of software list chds don't seem to be auto fixable even in version 4.047.

For some unknown reason the scan for the latest update (mamesl 0.251) screwed all the folders and moves all 2.5T data into the backup folder.

Since most of the SL roms are chd and there is no way to add them back by just dragging and dropping.  So I put the backup files in one of the SL rom-paths and hoping the scan to auto fix thier location, and fortunately the scan does not work as expected.

That is, same approach works for Arcade roms and chds.  but not for SL.

Any suggestion or solution would be appreciated.

or, a new feature that automatically moves the chd files to the right place would be nice.

3

clrmame Discussion / Re: lossing existed Roms during "new scan"

« on: 16 December 2021, 00:12 »

The only thing I can think of is that you used the "MERGER" instead of the rebuilder in between...which can be the cause of this since that module is outdated and not really aware of SL.....

Yes, I found that after merger, things go wrong again, even if I only maintain SL roms.

4

clrmame Discussion / Re: lossing existed Roms during "new scan"

« on: 13 December 2021, 02:55 »

I found that the collection is totally spoiled by the said two-profiles when I woke up, before I see this post.  Sincerely feeling sorry about that.
Will be back when there's any useful update.

5

clrmame Discussion / Re: lossing existed Roms during "new scan"

« on: 12 December 2021, 07:56 »

updating the lastest findings.

using mameui.exe to generate two profiles.
1. one without sl,
2. one with sl.

scanning the same rom sets.
the first one is 100% ok.
In the second profile, only enable to scan the basic "standard/device/machanical/bios/" but no "SOFT", and the scanner removes pwrshovl, and reports missing rom/chd of power shovel.

I hope this unique case is duplicable to find the source of glitches.

6

clrmame Discussion / Re: lossing existed Roms during "new scan"

« on: 11 December 2021, 02:43 »

Thanks.
Took 12 hours falling back to step 1.

1. isolate SL from arcade.
An arcade only profile is created to rebuild and scan the rom sets.
7000+ unneeded Roms are surpringly moved out of the Rom path ...\ROMs
It appears that the previous processes actually merge the arcade sets and SL sets into one parent.
That might explain why there are so many random confusions because SL and arcade overlap so much.
The independent arcade rom sets are now cleaned and confirmed 100% correct in mameui.exe

2. Will do SL in independent folders and profiles to see if things still happen. (to be continued)

7

clrmame Discussion / Re: lossing existed Roms during "new scan"

« on: 10 December 2021, 07:47 »

Thanks.  Will try to narrow down the issue.

BTW, the "new scan" is concluded, rendering a total different report, wherein I accepted every fix it proposed.  It is indeed random and scary.

Missing
·Sets                 7953/174315
·ROMs                 9235/543182
·CHDs                 8687/11652
·Samples              664/19344
·Bytes                2gb/435gb

Fixed Wrong Case
·Sets                 0/0
·ROMs                 0/0
·CHDs                 0/0
·Samples              0/0

Fixed Unneeded
·Sets                 0/0
·ROMs                 96/96
·CHDs                 10/10
·Samples              0/0

Fixed Wrong Name
·Sets                 0/0
·ROMs                 5/5
·CHDs                 0/0

8

clrmame Discussion / Re: lossing existed Roms during "new scan"

« on: 10 December 2021, 02:14 »

The "new scan" is ongoing, and asks to rename wrong names.
This is newly occured situation, too.

9

clrmame Discussion / Re: lossing existed Roms during "new scan"

« on: 09 December 2021, 23:49 »

After the last scan that I agreed to remove 500ish roms, the report shows 0 missing.
Then I rebuilt the total sets from mirror again, no new files created.  (this took me 8 hours)

However, odd things happened.
In the "audit all sets" in mameui.exe, roms including 1943 are confirmed affected.
To this step, I can confirm that one of the previous scans actually affects the arcade roms, but the report shows false result.

Using "new scan" in the scanner to double check, new odd behavior occured.
new unneeded roms are asked to be removed, including 1943 in the arcade ROM path.
(enclosing the removed 1943.zip FYI)

Looks like a confusion between arcade and software list.
and I wonder why "new scan" and "scan" get different results.

path problem should be excluded.  the config file looks fine.
and I stick to one profile at all time. 
Now I may decide to separate the SL and arcade into two profiles to get rid of this mystery.

In the "new scan" this time, it asks to add missing rom.
This is new.

10

clrmame Discussion / Re: lossing existed Roms during "new scan"

« on: 09 December 2021, 10:47 »

Not telling lie, I scanned all sets after the 1-set scan, and accepted all the removal.
The report turns into 0 missing.
Running rebuilder from the removed files in the backup folder does not create anything new, confirming that they are truely unneeded.
Still no technical explanation yet.
----------
Missing
·Sets                 7535/174315
·ROMs                 0/543182
·CHDs                 8685/11652
·Samples              0/19344
·Bytes                0/435gb

Fixed Wrong Case
·Sets                 0/0
·ROMs                 0/0
·CHDs                 0/0
·Samples              0/0

Fixed Unneeded
·Sets                 0/0
·ROMs                 481/481
·CHDs                 0/0
·Samples              0/0

11

clrmame Discussion / Re: lossing existed Roms during "new scan"

« on: 09 December 2021, 09:56 »

I rebuilt the complete rom set and redo the scan with only a7800\aceoface
It is placed at O:\Games\Emulator\Mame\Software\A7800\ in a zip file.
O:\ is totally local drive.

The prompt comes again, I accepted 3 removals and denied 6 of them.
But the report shows 0 missing roms this time.
This leads to two questions:
1. Why does the rebuilder rebuilds the roms but the scanner wants to remove them.
2. The removed roms are not reported as missed this time, this leads to further works to identify those being removed and reported missed. (which may be a long list to test)

Is that because I choosed the "merge" mode which may be confused between different systems ?

BTW: the removal this time creates a backup file in the backup folder, named aceoface.zip comprising the 3 removed roms.  But even weirdly, running a rebuilder from the backup path does not recreate anything from the backuped aceoface.zip.  So they are truely  unneeded?

12

clrmame Discussion / Re: lossing existed Roms during "new scan"

« on: 08 December 2021, 04:22 »

Further enclosing a log of the scanning when I refuse to "remove the unneeded roms" but keeping them.

The report now indicates that I miss 0 roms.
----------
Missing
·Sets                 7538/174315
·ROMs                 0/543182
·CHDs                 8688/11652
·Samples              0/19344
·Bytes                0/435gb

13

clrmame Discussion / Re: lossing existed Roms during "new scan"

« on: 08 December 2021, 03:01 »

1. I unified the BIOS/Standard/Device paths into .../ROMs
2. encosing to scan logs (before and after) which may be differentiated to tell what part was lost. (mostly software listed roms)
3. attaching an image showing a rebuilder recreating thousands of the lost files.
4.  including the prompt to remove an unneeded file in the "scan" after the rebuilder

14

clrmame Discussion / lossing existed Roms during "new scan"

« on: 07 December 2021, 11:42 »

This happens several times, and I suspect there is a bug in the scanner which misinterprets the same rom name of different systems as unneeded.

I have a complete arcade rom collection 0.238.
Now trying to incorporate SL chds into the collection with one single profile.

The system PATHs are individually defined.

The "new scan" function in "scanner" asks permission to remove unneeded files in the "fix unneeded file" window.
After the scanning, the report shows that my complete arcade collection turns into an incomplete one, in which thousands of ROMs are reported as missed.

Some of them can be found in the backup folder.
Some of them gone forever.

This is not the first time I bumped into this problem.
At first, I thought that was my misconfiguration.
Now I can replicate the problem by adding SL (MESS) CHDs into the corresponding software folder and do a new scan.

enclosing my cmp file FYI.

15

clrmame Discussion / Re: Can't get Software List paths set up properly

« on: 29 November 2021, 07:46 »

Thanks Roman,

As responsed in another thread of discussion, the Rom path issue is solved by adding a "\" at the end of each line.

Regarding the batch profile approach, I considered but there are 600ish separate profiles to import, each with different destination to setup.   I did not find a one-click wizard to prepare the system-paths for all the profile at once, and the amount is infeasible for manual operation, so I decided to stick with the one-profile approach and try to make it work.

16

clrmame Discussion / Re: Many "misplaced romset: (move to a rompath)" on latest nightly 20200904

« on: 29 November 2021, 07:33 »

Thanks for your prompt answer, Roman,

I kind of found the reason why my configuration did not work.

The system paths require a "\" at the end.
for exmaple:
wrong: O:\Games\Emulator\Mame\Software\wizard_cart
correct: O:\Games\Emulator\Mame\Software\wizard_cart\

When I redo the configuration, sl roms go to the right places as expected.
It will be nice to have a smart wizard aiming at this kind of issues.

17

clrmame Discussion / Re: Many "misplaced romset: (move to a rompath)" on latest nightly 20200904

« on: 29 November 2021, 05:57 »

Surprisingly found the same issue still happening in the latest release

Following my issue here:
https://www.emulab.it/forum/index.php?topic=5273.msg21178#msg21178

My observation from the behavior of clrmamepro concludes that: the scanner/rebuilder does not seriously treat the manually assigned system ROM paths for software-lists, and implicitly assign a destination path unexpected by the user. 

In my case, the rebuilder undesirably creates software-listed roms in $mameroot\software instead of $mameroot\software\$mycustomed_system_path, and when the scanner does the checking, the created roms are deemed as "misplaced", generating a significant amount of error messages without the capability to move them to the correct place.

I am not sure if it is technically hard to add some intellegence in defining the rom paths.

18

clrmame Discussion / Re: Can't get Software List paths set up properly

« on: 28 November 2021, 17:46 »

Greeting, Sirs:

I successfully completed the collection of 0.237.
when 0.238 comes out, I decided to include software list by creating a profile from mameui -listxml

the first problem I get is the issue of "path need to be unique", which I quickly overcame by creating a batch to mkdir all the system paths inside mame/software/$system

next I begin to rebuild the romsets from the download folder, which comprise a complete collection of mame-sl-merged 0.238.   This step took me nearly 24 hours, and it creates 65000+ files in my mame/software folder without going into the defined system paths (which supposed to be mame/software/$systems).  This is the first issue I don't understand.

Next I found my previous ROM collections are all screwed when doing the scanning.
Thousands of rom files are lost for good, not even in the trashcan or the backup folder.  The scanning shows that a lot of arcade Roms are missing, and they cannot be played anymore in mameui.

I suspect that there is something wrong in the process, so that duplicated named ROM sets overwrite the original collections.

Luckily I have a nas mirroring the previous complete collections.
The thing needed is to go over the collection process again.
but I might need some suggestions about how to prevent the error again.

Enclosing my cmp file for your reference.

PS.
The auto path assignment function does not really help in this case, it keeps assigning the paths to "not unique" paths which the scanning complains about.  I have to manually edit the cmp config file to make the Misc_SoftwareLists parameter work.
Even so, clarmamepro keeps deleting my created folders in the scanning process, and then complains that my path settings are "invalid".   Need some enlightment here.