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: Crash/Close Out /w Many Scan Result Messages

« on: 03 December 2020, 00:13 »

Yeah, I think I was one of those users from years ago. A shame no ones been able to track this down to a more specific issue. I've since resolved enough issues that I can't replicate the problem any more without prepping up some test setup.

In any case, something is going wrong when scanning roms with significant lists of problems on a SAMBA share in Windows that causes the program to silently exit /wo error.

2

clrmame Discussion / Re: Crash/Close Out /w Many Scan Result Messages

« on: 02 December 2020, 20:01 »

It's scanning a Mame 0.226 derived dat /wo software lists on a NAS device over a SAMBA share. I was originally scanning inclusive of SL, but it was too large making the repeated restarted needed ridiculous.

Yeah, it's weird. It's not a crash, just a mysterious program close with no error. It doesn't seem to happen at any particular point/file.

There is some other issue happening as well where it seems unable to complete file moves. It seems to move the file, but be unable to remove them from the improper locations. Resulting in lots of "wrong placed file:" results and "Can't remove file from:" warnings. Keeping the fix options on and quitting out of a scan once I hit 15k+ messages, to move all the files listed in the warnings window, has allowed me to almost complete a scan after numerous restarts, but it's been frustrating.

3

clrmame Discussion / Crash/Close Out /w Many Scan Result Messages

« on: 02 December 2020, 17:03 »

After not updating Mame for many months I wanted to bring my collection up to speed. I've been running into trouble doing so as at some point each night I'd run ClrMAMEPro against my ROM collection it would mysteriously exit out without completing or providing any results.

As far as I can tell this may be related to some sort of overflow that occurs when many Scan Result messages are output (somewhere > 15k logs).

Repeatedly stopping the scan process, correcting things, and restarting it; has let me make progress, but it's been very frustrating. Hoping the issue causing the program to mysteriously shut down can be resolved, or if not that things could be revised to maintain results if a a scan is cancelled mid-course.

On Windows 10 using cmpro64.exe (Latest Nightly from Sunday, November 29, 2020, 7:24:36 PM).

4

clrmame Discussion / Re: Arbrary Sets of ROMs Marked as Missing

« on: 27 January 2015, 17:05 »

Thanks for the feedback Roman.

The disk scan came back as healthy, and as indicated previously it's a RAID6 array with 2 separate parity disks so it should be resilient to disk problems should they be present. For now I've just purged the copy that was acting oddly. Sorry that I'm not able to provide details to help pin down what may be going on in these situations. You can chalk up at least one more report that something odd sometimes happens when using network disks over Samba.

5

clrmame Discussion / Re: Arbrary Sets of ROMs Marked as Missing

« on: 27 January 2015, 04:38 »

I'm still unclear regarding what's happening, but it only seems to be effecting the files located in a particular directory. Copies of the files to new locations, or even the same named location (via copy+folder renames) allows for successful scans. A WinMerge compare of the problematic folder with ones that scan without issue doesn't indicate any differences in their contents.

The files are located on a NAS on a set of RAID6 drives. I'd think the RAID6 parity would ensure that even a bad disk wouldn't result in problems, but will be performing a more thorough drive scan shortly to see if that turns up anything.

6

clrmame Discussion / Re: Arbrary Sets of ROMs Marked as Missing

« on: 25 January 2015, 23:26 »

The scanner tree window is not empty, until the scan that eventually reports none missing but that can take 2-3 rescans to reach.

I think you may be confused regarding what I'm reporting though, there is no rebuilding or fixing occurring over these scans (i.e. all Fix options are disabled, and the scans are run back to back without rebuild runs in between or other changes to the files). The initial rebuild seems to create a complete set. The scans then make no changes to the files, but report fewer missing ROMs with each repeated scan until there are none. Repeating a new scan typically then shows missing ROMs again, but a different number than reported previously.

For example, I just reran "New Scan" on the set four times (again with all Fix options off, and no changes occurring to the files between runs). First run reported 466 missing ROMs, the second reported 613, third 550, and the fourth 452.

I've attached the requested items. I couldn't find an option to export the Scan Results window content, but included screenshots of the end of run 3 and 4's contents. Related ROM files can be pulled from: https://archive.org/details/Sharp_X68000_TOSEC_2012_04_23

Regarding the rebuilder, it will normally error fewer times than the scans do. On this set only ~50-70 failed adds vs the hundreds of missings reported by scan, similar to the scan the specific files and their number seem to change with each run. I'd guess the issues may be related though, in that both are failing to pick up on ROMs that are in place.

7

clrmame Discussion / Arbrary Sets of ROMs Marked as Missing

« on: 25 January 2015, 17:47 »

I'm seeing an issue with v4.016, where multiple runs of "Scan" on the same folder will report different sets of ROMs as being missing, even though all ROMs seem to be in place. Typically this has been against the most recently release TOSEC dats. For instance, multiple scans over "Sharp X6800 - Games (TOSEC-v20014-05-13)" dat gave the following results...

Initial "New Scan":
Sets: 0/3245
ROMs: 1173/3245

Initial "Scan"
Sets: 0/3245
ROMs: 158/3245

Secondary "Scan"
Sets: 0/3245
ROMs: 0/3245

Secondary "New Scan"
Sets: 0/3245
ROMs: 1148/3245

The folder contents were created with the Rebuilder, and no change to the folder or it's contents occurred between runs. I tend to see issues with the Rebuilder on these same sets where it will indicate there is an error adding files to a set on a few files. Usually these will be ROMs that appear to already be in the set.

I'm currently using 7z compression on the ROMs, unclear if the compression method makes a difference.