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: Updated to 4.048 - seems to crash when looking for unknown sets/unneeded?

« on: 30 October 2023, 18:31 »

OK, I think I solved the problem.   I deleted the fmtowns_cd and MSX1 sets that were acting up from the profiler and dragged the hashes from MAME 0.260 into the profiler and recreated new profiles for those three.   Scans are OK now.   I had to replace a number of CHDs from my backup for fmtowns that somehow had been removed in trying the different versions.

This is really odd as I delete all old hashes from the MAME install hash folder prior to installing a new version (so I am sure I have updated hashes) and then drag the new hashes to CLRMAME Pro profiler to update and do a rescan on all.   For some reason, something happened to those three system profiles and caused the weirdness.   Once recreated, all is as expected.

Sorry for the wild goose chase on this last issue.  I would not have expected that on just three of all the systems for no apparent reason.   Strange.  All good now.

Thank you Roman for fixing the other issues, your time and effort is appreciated!

2

clrmame Discussion / Re: Updated to 4.048 - seems to crash when looking for unknown sets/unneeded?

« on: 30 October 2023, 08:15 »

I use individual profiles for FM towns, one in a software list CHD folder (fmtown_cd) and in a software list Roms folder (fmtowns_cd, xxx_flow_cracked, xxx_flop_misc, xxx_flop_orig).

I DO have both rom_paths added in the FMTowns_cd profile (the software list CHD path and software list Roms path).   I tried to split them once or move them to either the CHD or ROMS folders I have for software lists, but it complained and it did seem odd to me that there is a set in each when you download them.   Is there a recommended setup for fmtowns_cd?

Also, the MSX1 systems listed are also an issue (MSX1_flop, MSX1_cass).

Merge mode is merged.

There should be no other tasks.  4.047 will scan them and complain only about the samples.  The 4.048x wants to do all the renaming or removing of these systems.

I added a zip with the requested files.   Let me know if there is anything else you need.

3

clrmame Discussion / Re: Updated to 4.048 - seems to crash when looking for unknown sets/unneeded?

« on: 29 October 2023, 20:43 »

E:\Emulation\Emulators\MAME>chdman info -i "E:\Emulation\Emulators\MAME\roms software list\CHDs\fmtowns_cd\kiwame\kiwame
 (japan).chd"
chdman - MAME Compressed Hunks of Data (CHD) manager 0.260 (mame0260)
Input file:   E:\Emulation\Emulators\MAME\roms software list\CHDs\fmtowns_cd\kiwame\kiwame (japan).chd
File Version: 5
Logical size: 10,653,696 bytes
Hunk Size:    19,584 bytes
Total Hunks:  544
Unit Size:    2,448 bytes
Total Units:  4,352
Compression:  cdlz (CD LZMA), cdzl (CD Deflate), cdfl (CD FLAC)
CHD size:     593,348 bytes
Ratio:        5.6%
SHA1:         03237f11476eb1c4d2acc8075507ef64ebc9fae1
Data SHA1:    bbac0170e5daba6e9f9e88fb22894718ad3b7be4
Metadata:     Tag='CHT2'  Index=0  Length=91 bytes
              TRACK:1 TYPE:MODE1_RAW SUBTYPE:NONE FRAMES:4350 PREGAP:0 PGT

E:\Emulation\Emulators\MAME>

4

clrmame Discussion / Re: Updated to 4.048 - seems to crash when looking for unknown sets/unneeded?

« on: 29 October 2023, 18:32 »

In the FMTowns_CD, the tool is asking me to delete "deep (japan).chd" as unneeded.  Also, flashback (japan).chd, kiwame (japan).chd, and that's toukou - natsu no tokushuugou(japan).chd.

The MSX1_cass and MSX1_flop also wants to do renaming and removing of unneeded files.

Example:
MSX1_cass wants to rename mandragore to mandragr and wants to remove akalabeth.zip (this is two of many other reported issues)
MSX1_flop wants to remove 10progor.zip and says bswriter is missing (this is two of many other reported issues)

Software list all completed with 4.047b and 4.048.  This just started on these three systems with 4.048a.

5

clrmame Discussion / Re: Updated to 4.048 - seems to crash when looking for unknown sets/unneeded?

« on: 29 October 2023, 18:09 »

That looks to have fixed the MAME scan.

I reran all the software list scans with the new version and now have reported missing CHDs for "Fujitsu FM Town CD-ROMs",  "MSX1 cassettes", and "MSX disk images".  The files I have seem to match those available on pleasuredome github, so trying to figure out what is different, if anything.

6

clrmame Discussion / Re: Updated to 4.048 - seems to crash when looking for unknown sets/unneeded?

« on: 29 October 2023, 07:51 »

Software list scans are perfectly fine.  I can just no longer run a scan for MAME using my Mame profile.  I cleared the cache and reloaded it, but that did not help.

Note that Miss List and Have List complete and write files.  I just cannot perform a New Scan or Scan (Diff Scan is greyed out since it is a first scan).

Update - I have a full backup of my prior clrmamepro folder.  I deleted the upgraded 4.048 version folder and copied the entire backup folder for 4.047 in its place.   Started it up and did a full scan with no problems (apart from it wanting to delete samples.zip) for the new samples.  I then disabled all antivirus and upgraded it to 4.048.  Crashed when doing the initial check as detailed above.  I wish I could see a log entry for what might be causing the crash with the updated version.  Mame files and folders have not changed.

7

clrmame Discussion / Update...remove BIOS_3dobios folder, then fails on next system - BIOS_airlbios

« on: 29 October 2023, 04:03 »

I allowed clrmamepro to update itself.   Looking at the files in the saved download file, it looks like files did update in my clrmempro folder.

It appears to be failing on the initial check for unknown sets.

Not sure what happened as the prior 4.047b did not have this issue and would successfully scan to completion other than wanting to delete the new sample sets for mame 0.260.

I attached a screenshot of the dialog where it quickly hangs and then the entire application crashes.  The cmpro.log is also empty so I cannot look to see if there is an error reported to try to address.

Hopefully this helps.   Please let me know if you need any additional information.

8

clrmame Discussion / Updated to 4.048 - seems to crash when looking for unknown sets/unneeded?

« on: 29 October 2023, 03:17 »

Cache was cleared, clrmamepro went through loading from the executable.  When selecting to scan, it stops on my BIOS_3dobios folder and crashes.

Is there something we need to manually clear?

9

clrmame Discussion / Re: All roms indicated as "wrong name" on new install of ClrMamePro?

« on: 30 October 2022, 00:29 »

It was a bit weird.   All I had to do was simply open the zip files that were throwing errors and close them.  After they, they scanned and the fix was auto applied.   Oh well, all seems ok now. 

Got it all moved, new mame and software list profiles set up and scannned. 

One quick question:   Is there a way to “apply” the merge, all fix, etc settings to all the software list profiles without having to open each one and manually selecting them?   I know I can batch mode scan and use the dialog there, I was just wondering if you can have the tool update all the profiles to always use merged sets and all fix options selected. 

10

clrmame Discussion / Re: All roms indicated as "wrong name" on new install of ClrMamePro?

« on: 29 October 2022, 04:26 »

Looks like that was what caused that issue.

Right now, I updated to .249 and used the rebuilder.   

It seems that there are a lot of files with "wrong name", but the tool indicates that they were not fixed.  I have all the fix options selected.   Any idea why the tool will not fix the zip file by renaming and/or deleting extra files in the zip?

11

clrmame Discussion / All roms indicated as "wrong name" on new install of ClrMamePro?

« on: 27 October 2022, 04:03 »

Hi Roman, I just upgraded my laptop after about 10 years and made a copy of my 0.248 complete ROM set (including software lists).  I created a fresh install of clrmamepro, set up a mame.exe profile, set the rom paths similar to my old machine, and set up all the scanner options except I turned off all fix options just in case I did something incorrectly.

Well, when I choose to scan for MAME (no software list), all the roms are reported with errors - "wrong name".  For example:

10-Yard Fight (World, set 1) [folder: 10yard - size: 129kb]
wrong name: E:\Emulation\Emulators\MAME\roms\10yard\yf-a-5c.5c [wrong: yf-a-5c.5c] [right: yard.1c]
wrong name: E:\Emulation\Emulators\MAME\roms\10yard\yf-a-5d.5d [wrong: yf-a-5d.5d] [right: yard.1d]
wrong name: E:\Emulation\Emulators\MAME\roms\10yard\yf-b-2p.2p [wrong: yf-b-2p.2p] [right: yard.2m]
wrong name: E:\Emulation\Emulators\MAME\roms\10yard\yf-b-2r.2r [wrong: yf-b-2r.2r] [right: yard.2n]
wrong name: E:\Emulation\Emulators\MAME\roms\10yard\yf-b-3l.3l [wrong: yf-b-3l.3l] [right: yard.2h]
wrong name: E:\Emulation\Emulators\MAME\roms\10yard\yf-b-5b.5b [wrong: yf-b-5b.5b] [right: yf-b.5b]
wrong name: E:\Emulation\Emulators\MAME\roms\10yard\yf-b-5c.5c [wrong: yf-b-5c.5c] [right: yf-b.5c]
wrong name: E:\Emulation\Emulators\MAME\roms\10yard\yf-b-5e.5e [wrong: yf-b-5e.5e] [right: yf-b.5e]
wrong name: E:\Emulation\Emulators\MAME\roms\10yard\yf-b-5f.5f [wrong: yf-b-5f.5f] [right: yf-b.5f]
wrong name: E:\Emulation\Emulators\MAME\roms\10yard\yf-b-5j.5j [wrong: yf-b-5j.5j] [right: yf-b.5j]
wrong name: E:\Emulation\Emulators\MAME\roms\10yard\yf-b-5k.5k [wrong: yf-b-5k.5k] [right: yf-b.5k]
wrong name: E:\Emulation\Emulators\MAME\roms\10yard\yf-s-1a.1a [wrong: yf-s-1a.1a] [right: yf-s.1a]
wrong name: E:\Emulation\Emulators\MAME\roms\10yard\yf-s-1b.1b [wrong: yf-s-1b.1b] [right: yf-s.1b]
wrong name: E:\Emulation\Emulators\MAME\roms\10yard\yf-s-3a.3a [wrong: yf-s-3a.3a] [right: yf-s.3a]
wrong name: E:\Emulation\Emulators\MAME\roms\10yard\yf-s-3b.3b [wrong: yf-s-3b.3b] [right: yf-s.3b]

18 Wheeler (set 1) [folder: 18w - size: 8kb]
wrong name: E:\Emulation\Emulators\MAME\roms\18w\18w_b2.rom2 [wrong: 18w_b2.rom2] [right: 18w_a2.rom2]
wrong name: E:\Emulation\Emulators\MAME\roms\18w\18w_b4.rom4 [wrong: 18w_b4.rom4] [right: 18w_a4.rom4]

1941: Counter Attack (World 900227) [folder: 1941 - size: 3mb]
wrong name: E:\Emulation\Emulators\MAME\roms\1941\41_23.13b [wrong: 41_23.13b] [right: 41_9.12b]
wrong name: E:\Emulation\Emulators\MAME\roms\1941\41_30.12c [wrong: 41_30.12c] [right: 41_18.11c]
wrong name: E:\Emulation\Emulators\MAME\roms\1941\41_31.13c [wrong: 41_31.13c] [right: 41_19.12c]
unneeded file: E:\Emulation\Emulators\MAME\roms\1941\41e_18.11c

I looked on my old machine with a completely up to date rom set (no errors) with mame .248 and the ROMS are identical to these on my new machine, and running a scan on the old machine is still clear.   I cannot see any difference between scanner settings.

Any ideas what might be doing this, unless my old machine was really not properly scanning the ROMS and they need fixing?   I just find it odd that it seems every rom is flagged with this same problem?

I expect that I should be able to run a scan and have no errors as I can on my old machine since nothing really has changed?

Thank you for any help.   

Matt

12

clrmame Discussion / Re: pcmx2 set removed in latest ClrMamePro build/MAME 0.242?

« on: 02 April 2022, 19:43 »

A rescan solved it.   Thanks Roman.  Appreciate the great tool. 

13

clrmame Discussion / Re: pcmx2 set removed in latest ClrMamePro build/MAME 0.242?

« on: 01 April 2022, 20:54 »

Thank you Roman.  I will give it another scan in about an hour and report back.   I have been just copying it back and running the scans.   

14

clrmame Discussion / pcmx2 set removed in latest ClrMamePro build/MAME 0.242?

« on: 01 April 2022, 19:30 »

Updated my roms for 0.242 and am at latest ClrMamePro build.  Scanning for MAME removes the pcmx2 set.  And then reports it missing?

Curious if anyone else has seen this. 

15

clrmame Discussion / Re: clrmamepro 4.044b released

« on: 26 February 2022, 06:07 »

Thanks Roman, the b version seems to address the issue that was remaining.  Appreciate your great work.

16

clrmame Discussion / Re: MAME v0.241 snes.xml

« on: 25 February 2022, 04:48 »

I was about to post the same thing.  Get error on both Nintendo SNES cartridges and Sinclair ZX Spectrum cassettes.

Error for Nintendo SNES cartridges says:  "Found an incomplete datfile or a bad exe-output" for flintsmp.

Next dialog reads: "An error occurred while reading information from "...snes.dat
You either stopped the loading process or the file is corrupt."

Similar error for dizzya and Sinclair ZX Spectrum cassettes

17

clrmame Discussion / Cmpro states that bonuspak.chd is unneeded, but when removed reports as missing

« on: 30 July 2021, 15:20 »

Curious as to what might be causing this as well.

18

clrmame Discussion / Re: Folders "Magnavox Odyssey 2/Philips Videopac" vs. "Philips Videopac/Odyssey 2"?

« on: 02 April 2021, 08:45 »

It was not a clean install, so I am sure that is what caused that confusion.  I was trying to figure out what the deal was in the last few builds and finally decided to get to the bottom of it.  Thank you for the information.  It cleared it up.

19

clrmame Discussion / Folders "Magnavox Odyssey 2/Philips Videopac" vs. "Philips Videopac/Odyssey 2"?

« on: 02 April 2021, 05:23 »

Clrmamepro 4.041
Mame 0.230

No software lists selected.  Dragged all new hash files to profiler.

I see both "Magnavox Odyssey 2/Philips Videopac cartridges"  and  "Philips Videopac/Odyssey 2 cartridges" profiles?  Is one of them deprecated?  Did I leave an extra profile in place in clrmame pro that I should have deleted when I let MAME replace the contents of the hash folder?

I think the "Philips Videopac/Odyssey 2 cartridges" is correct with the softwarelist roms folder "videopac"?

20

clrmame Discussion / I think I found the answer...simply set "Don't show statistics"?

« on: 02 January 2021, 01:40 »

Looks like if "Don't show statistics" if set, that it will still stop if "Don't ask before fixing" is unchecked but continue if something is missing so it can be addressed later.