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: Missing ROMs but empty scan results

« on: 01 January 2021, 22:28 »

Glad you found it. I am a professional tester for HW/SW/FW etc. so I usually find things like this.

Additional:

When I ran 4.040 I had some problems. I did Rebuilder to add the missing files, then did a Scan. Mostly it was fine, but one thing that happened was that the first scan said the files were in where they should be in alg_bios but it showed that they were in mameroms also. I searched for the files in mameroms and could not see the files. I ran the scanner again and the second time it was correct with no files missing and no extra files in mameroms. I am very happy now. Thanks for 4.040 and all you do.

2

clrmame Discussion / Re: Missing ROMs but empty scan results

« on: 01 January 2021, 04:02 »

Yes all my sets are selected. All systems are selected including alg_bios. All set information is selected. Hide fully missing sets is NOT enabled. All regions are selected.

Files attached

3

clrmame Discussion / Re: Missing ROMs but empty scan results

« on: 30 December 2020, 20:20 »

Yes I did finally use the test version and it had the same folders with the numerical extensions that came from the bad list (that took 2 days to produce), expanded to the individual files:

crimep2_11/cp2_1.dat
crimep2_11/cp2_2.dat
crimepat_12/cp_1.20_u1.bin
crimepat_12/cp_1.20_u2.bin
crimepat_14/cp01.dat
crimepat_14/cp02.dat
fastdraw_130/fast_01.bin
fastdraw_130/fast_02.bin
gallgall_21/gg_21_rom1.bin
gallgall_21/gg_21_rom2.bin
lastbh_006/bounty_01.bin
lastbh_006/bounty_02.bin
maddog2_100/md2_1.0_1.bin
maddog2_100/md2_1.0_2.bin
maddog2_110/md2_1.10_u1.bin
maddog2_110/md2_1.10_u2.bin
maddog2_202/md2_01.bin
maddog2_202/md2_02.bin
maddog_202/md_2.02_u1.bin
maddog_202/md_2.02_u2.bin
maddoga/maddog_01.dat
maddoga/maddog_02.dat
spacepir_14/sp_14_u1.bin
spacepir_14/sp_14_u2.bin
wsjr_15/wsjr151.bin
wsjr_15/wsjr152.bin
zortonbr_100/zb_u2.bin
zortonbr_100/zb_u3.bin

I have searched every directory that could have those files and found nothing. The versions of the files that I had around before, I moved to a completely different disk that is not shared with the computer that is running clrmamepro. So, I am at a loss as to where clrmamepro is finding those files. These files are all from alg_bios if you don't recognize them.

4

clrmame Discussion / Re: Missing ROMs but empty scan results

« on: 30 December 2020, 07:13 »

cmpro.log is empty, even after ending cmpro. Yet it still shows files missing in the summary and nothing in the scan. Should I be using the version you provided in this thread?

5

clrmame Discussion / Re: Missing ROMs but empty scan results

« on: 28 December 2020, 02:37 »

It turns out that the files were not bad but in another directory parallel to my directory called mame_bios_soft:
\
 |-mame_bios_soft               in ROM-Paths
 |-mame_bios_soft_bad        not in ROM-Paths
 |-mameroms                       in ROM-Paths
 |-mameroms_bad                not in ROM-Paths
Files were moved before the scan run from a correct directory (mame_bios_soft) to the parallel directory (mame_bios_soft_bad) that contained bad ROMs from previous scans. I keep bad old ROMs around for awhile just to make sure they are not needed. Of course those files had correct Checksums but names that had an extension added like crimep2_11.zip instead of crimep2.zip. This was done by clrmamepro in previous scans.
So now you know what the problem is when there are zero ROMs listed in the error list but ROMs showing as Missing. Certainly another weird thing that is still in clrmamepro.

6

clrmame Discussion / Re: Missing ROMs but empty scan results

« on: 27 December 2020, 07:36 »

I am getting the same results with my scans. I am using split sets (which I need to convert) but I get 20 missing ROMs but no listing of them. I understand you have looked at this problem already and it probably has to do with BIOS sets. I am using 0.226 MAME and cmp4039a_64 so everything is up to date there. One other problem is that the listing of "Missing Sets" now takes two days to complete when it used to take a minute.

Thank you for your update to cmp4039a_64 because I was having monumental problems with clrmamepro for a few months. But, cmp4039a_64 seems to have fixed all of my problems except for the BIOS sets. Thanks for all you do.

7

clrmame Discussion / Re: Strange things happening with some new System Paths in MAME

« on: 20 March 2020, 06:44 »

the latest nightly is from march 8th 2020.
for your path problems I need more info...turn off the fix options and let me know what the scanner tree says

Boy am I embarrassed  for not looking at the date on the download instead of the date of the post.

Yes the fortnightly release seems to have fixed the problem. It created a new path for one of the problem paths, and the others seem to be working correctly now. Thanks for all your work.

8

clrmame Discussion / Strange things happening with some new System Paths in MAME

« on: 19 March 2020, 18:34 »

I have been updating my MAME files using clrmamepro. For the last two versions of the DAT 0.218 and 0.219 I have gotten strange results with new paths added by the DAT.

Some of the paths; specifically bbc_flop_68000, spectrum_cart, sv318_flop, and others have problems. What happens is that when you enable the path to those directories with ROMS in them, clrmamepro goes through and deletes those directories and ROMS. If you disable those paths the directories remain but clrmamepro doesn't see the ROMS. It is very strange.

I have checked the SHA1s of all the files and they are correct. Even if it found those wrong should it have removed the directory?

I am on the latest version of clrmampro 4.036a.

By the way, your nightly downloads topic is out of date by over two years. I assume you are no longer doing nightlies.