1
clrmame Discussion / Re: Site Problems
« on: 14 February 2025, 00:35 »
And Edge seems to be working well now too although I have been getting a different error (attached)
- 12 November 2025, 14:09
- Welcome, Guest
News:
The new forum is online, hope you enjoy it!
Show Posts
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.
Pages: [1] 2
2
clrmame Discussion / Re: Site Problems
« on: 14 February 2025, 00:30 »
Thanks - logging out and back in solved the issue...
3
clrmame Discussion / Re: ClrMAMEPro / MAME 0.274 Issue
« on: 14 February 2025, 00:28 »
I had already tried mame.exe -listxml > x.txt using a command prompt run as an administrator. It created the x.txt with 0 bytes. I tried with your entry and same effect. I tried restarting, disabling virus scanner (McAfee/Trellix), admin command prompt entry and ClrMAMEPro again. Nada. I had already MAME (both from mamedev.org and progettosnaps.net with no effect and checked the CRCs.
I think it has to do with new version of MAME. From the website:
I am running a Core2 Duo processor. So I think I am SOL unless I update my PC.
I think it has to do with new version of MAME. From the website:
Quote
After several years, we’ve decided it’s time to start taking advantage of features of newer (or at least slightly less outdated) CPUs. Starting with MAME 0.274, official Windows binary releases will require so-called x86-64-v2 features. These features have been available in all popular x86-64 CPUs for close to a decade. They were introduced in the following CPU families:
Intel “Nehalem” (2008), or “Silvermont” (2013) for low-power CPUs
AMD “Bulldozer” (2011), or “Jaguar” (2013) for low-power CPUs
VIA “Nano C” and “Eden C” (both 2015)
If you still want to run up-to-date versions of MAME on older systems running Windows, you’ll need to compile it from the source code.
I am running a Core2 Duo processor. So I think I am SOL unless I update my PC.
4
clrmame Discussion / Site Problems
« on: 13 February 2025, 11:50 »
I can't seem to post a response in my last thread without getting a Javascript error even though it is enabled (in Google). Site is blocked completely in Microsoft Edge.
5
clrmame Discussion / ClrMAMEPro / MAME 0.274 Issue
« on: 12 February 2025, 01:41 »
I loaded MAME 0.274 on my cabinet and ClrMAMEPro is having issues (no XML file being created) - see attachment pics. ClrMAMEPro worked with 0.273 last month. I use Microsoft RDC to do the updates - could it possibly be related to an Win11 update on my desktop PC and running ClrMAMEPro? Did anyone have an issue with 0.274 or use Microsoft RDC?
-Thanks-
-Thanks-
6
clrmame Discussion / Re: Titles setup (non-zipped)
« on: 09 October 2023, 00:44 »
Now I got it - thanks! 
7
clrmame Discussion / Re: Titles setup (non-zipped)
« on: 08 October 2023, 18:03 »
What other settings should I set (or uncheck) if zip files are not needed? When I had raw files in instead of titles.zip it deleted all the *.png files. After messing with other settings, it was screaming 'No ROM-Paths specified'.
Should 'You want to scan' be checked for 'Sets' and/or 'ROMs'?
Under 'Settings' should it be 'ROM-Paths along with the 'C:\MAME\titles' sub-directory?
Should 'You want to scan' be checked for 'Sets' and/or 'ROMs'?
Under 'Settings' should it be 'ROM-Paths along with the 'C:\MAME\titles' sub-directory?
8
clrmame Discussion / Re: Titles setup (non-zipped)
« on: 08 October 2023, 12:46 »
Awesome - thanks!
9
clrmame Discussion / Titles setup (non-zipped)
« on: 08 October 2023, 00:29 »
Can ClrMAME be set up to use resources that are NOT compressed (i.e. zip, rar, 7z)? The large size of the titles.zip file took a LONG to scan and I wanted to switch to individual (*.png) files in the titles directory. What do I change to do that?
10
clrmame Discussion / Re: 4.038a - Extremely long scan time (titles.zip resource)
« on: 05 November 2020, 03:27 »
Tried canceling the operation over an hour and a half ago - no response.
11
clrmame Discussion / Re: 4.038a - Extremely long scan time (titles.zip resource)
« on: 05 November 2020, 01:23 »
Turned off fix missing option but not belonging advanced fixed missing option. Still is taking forever and was never this long.
You indicated the secondary resources don't need to be zipped/7z'ed/rar'ed. Why did ClrMAMEPro re-zip them into the 7z archive? Is there a setting for this?
You indicated the secondary resources don't need to be zipped/7z'ed/rar'ed. Why did ClrMAMEPro re-zip them into the 7z archive? Is there a setting for this?
12
clrmame Discussion / Re: 4.038a - Extremely long scan time (titles.zip resource)
« on: 04 November 2020, 01:16 »
Roman-
Thanks for the prompt reply.
I am hesitant to uncheck the fix missing because in the past it seemed like a few 'fell through the cracks' - the update file was missing something that need to be fixed from the prior release.
I tried upzipping the png's and placing in the titles directory but ClrMAMEPro re-zipped them into a titles.7z zip file. Do the png's have to be zipped? Is there any way to leave them in their native png state in the titles (logo, etc.) directory and still use the fix missing option?
-Thanks-
Thanks for the prompt reply.
I am hesitant to uncheck the fix missing because in the past it seemed like a few 'fell through the cracks' - the update file was missing something that need to be fixed from the prior release.
I tried upzipping the png's and placing in the titles directory but ClrMAMEPro re-zipped them into a titles.7z zip file. Do the png's have to be zipped? Is there any way to leave them in their native png state in the titles (logo, etc.) directory and still use the fix missing option?
-Thanks-
13
clrmame Discussion / 4.038a - Extremely long scan time (titles.zip resource)
« on: 03 November 2020, 01:39 »
I updated to version 4.038a and was able to run successfully with MAME 0.226. I tried running my Titles zip resource (from http://www.progettosnaps.net/snapshots/) and it ran for over 12 hours before I stopped thinking was hung. Granted my machine is not the latest vintage but it never took more than a few minutes. I tried again and had the same result. Thinking my titles.zip file was corrupt, I downloaded the base set and updates. I cannot seem to get through a scan (with 'fix') on the base set with 0.225 dat file. Don't know if this is a corrupt dat file, corrupt titles.zip file, or issue with ClrMAMEPro update. I was able to scan my logos.zip file is reasonable time without issue.
Anyone have similar issue?
Anyone have similar issue?
14
clrmame Discussion / Re: Strange Behavior
« on: 29 July 2017, 16:50 »
The log file shows two 'missing rom' listed in the list but 3 at the bottom summary. After this log file I only performed a Pippin rebuild and added the missing CHDs. Somehow the 317-0432-jpn.data rom was magically recognized after adding the CHDs. Regardless, I have a clean set and just wanted to point out a potential anomaly.
15
clrmame Discussion / Strange Behavior
« on: 28 July 2017, 23:54 »
Roman,
The attached log file reflects the latest 0.188 MAME with your 32 bit 4.032 code running under Win 10 (32 bit). It is essentially a snapshot of all ROMs updated and prior to adding the updated CHDs. It is incorrectly flagging 317-0432-jpn.data as missing. I tried using the rebuilder with the file and it would not rebuild. When I finally attached the CHDs, the issue went away. It also indicates that 3 ROMs are missing (when there are none). I am not complaining but just simply alerting you to this strange behavior.
-Thanks-
The attached log file reflects the latest 0.188 MAME with your 32 bit 4.032 code running under Win 10 (32 bit). It is essentially a snapshot of all ROMs updated and prior to adding the updated CHDs. It is incorrectly flagging 317-0432-jpn.data as missing. I tried using the rebuilder with the file and it would not rebuild. When I finally attached the CHDs, the issue went away. It also indicates that 3 ROMs are missing (when there are none). I am not complaining but just simply alerting you to this strange behavior.
-Thanks-
16
clrmame Discussion / Re: 0.182 'missing' ROM
« on: 31 January 2017, 01:12 »
For me I was using the latest 32 bit version (4.031c) in the scanner mode with 'Fix' checkbox selected for 'Missing' and 'Name'. ClrMAMEPro usually detects and creates/adds the missing files but not in this case.
17
clrmame Discussion / Re: 0.182 'missing' ROM
« on: 30 January 2017, 01:01 »
I too had a problem. I had the aa003.bin and was missing the aa008.bin and ClrMAMEPro did not seem to want to fix. I simply copied aa003.bin and renamed as aa008.bin within the zip files based on coccola's retroroms.info post and everything was good. I just posted here to see if you were aware of.
Has anyone else experienced this?
Has anyone else experienced this?
18
clrmame Discussion / Re: 0.182 'missing' ROM
« on: 29 January 2017, 13:41 »
coccola-
Thanks for the reply. I didn't know if Roman was aware of the issue and was just pointing it out.
Thanks for the reply. I didn't know if Roman was aware of the issue and was just pointing it out.
19
clrmame Discussion / 0.182 'missing' ROM
« on: 29 January 2017, 02:19 »
Roman-
Thanks for the prompt replies on my other posts. Are you aware of the issue on Joshi Volleyball (josvolly)? It was discussed in the thread at:
http://www.retroroms.info/forum/topic/MAME-0-182-ROMs-sooner-arcade-mess-.htm
I don't know if it's real or not.
-Thanks-
Thanks for the prompt replies on my other posts. Are you aware of the issue on Joshi Volleyball (josvolly)? It was discussed in the thread at:
http://www.retroroms.info/forum/topic/MAME-0-182-ROMs-sooner-arcade-mess-.htm
Quote
That's not a real new ROM, it's a rename and has the same hash info as aa003.bin, but aa008.bin has baddump status.
It's probably being rejected as a duplicate in most ROM managers.
Perhaps this will require another small update to clrmamepro? As you can see it seems to be some kind of placeholder ROM for the 2nd MCU. Usually when there are multiple MCUs in a game, there are separate (non-identical) ROMs for each one. I don't know of any other games where there are identical ROMs on different MCUs, but I haven't looked for them. I don't know what clrmamepro's proper behavior is in such a case.
<machine name="josvolly" sourcefile="gsword.cpp">
<description>Joshi Volleyball</description>
<year>1983</year>
<manufacturer>Allumer / Taito Corporation</manufacturer>
<rom name="aa003.bin" size="1024" crc="68b399d9" sha1="053482d12c2b714c23fc80ad0589a2afd258a5a6" region="mcu1" offset="0"/>
<rom name="aa008.bin" size="1024" crc="68b399d9" sha1="053482d12c2b714c23fc80ad0589a2afd258a5a6" status="baddump" region="mcu2" offset="0"/>
</machine>
I don't know if it's real or not.
-Thanks-
20
clrmame Discussion / WWW Mode
« on: 28 January 2017, 15:45 »
I added the progettosnaps site to the Profiler WWW Mode. I then tried to add MAMEUI's DAT files link since it is a zip file with a static name. For some reason, CLRMamePro doesn't like MAMEUI's DAT file path (http://www.mameui.info/MameUI_DATs.zip). Any reason I can't do this?
Pages: [1] 2