EMULAB Forum

Please login or register.

Login with username, password and session length
Advanced search  

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.

Topics - john iv

Pages: [1]
1
clrmame Discussion / Renamed, but where?
« on: 10 September 2025, 02:31 »
Hi Roman, I'm seeing this rename error in the logs on every run.  It might be nice to include the containing zip or file that the renamed ROM is coming from so I can go double-check it or have a DEV rename it properly in the source.

2
clrmame Discussion / clrmame just closing
« on: 15 April 2025, 01:22 »
Hi Roman, seems within the last 24 hours or so when I run clrmame on my exported mame.xml it starts to build the full view and then closes without an error.  Very odd.  The softwarelist.xml scan is fine, but not the mame one.  My mame.exe is tip of master on github.  I'm able to import the .exe's xml into my front-end as normal so I don't think it's malformed?  No errors or logging.

[Update] Crashes with a fresh settings, also crashes reading from mame.exe vs. my exported mame.xml.
[Update] Old clrmamepro 4.049 works w/ this mame.exe.

mame -version
0.276 (mame0276-217-gf6d743b9378)


3
clrmame Discussion / Scan deleted my softwarelist.xml
« on: 23 January 2025, 22:49 »
Hi Roman, I've seen this a few times now where a scan is deleting the underlying software.xml file during its scan and failing.
1. Manually output mame.exe -listsoftware > softwarelist.xml
2. Point scanner to softwarelist.xml
3. Observe directory from step 2.
4. Run scanner on softwarelist.xml.
5. softwarelist.xml disappears from directory.
6. Log of scan shows a bunch of 'adding hashes'
7. End of log says, can't parse the softwarelist.xml as it's not there

Any code path that would actually delete the used stand-alone softwarelist.xml?  Attaching log file.

Nightly build from top of tree, x64 Win11.

4
clrmame Discussion / Rename failure?
« on: 14 November 2024, 03:17 »
Hi Roman, starting w/ today's tip of master I'm getting a rename warning over and over regardless of how many times I run the scan.
c:\O\Games\MAME>mame -version
0.271 (mame0271-231-gc87f8a3801a)



5
clrmame Discussion / Checks to prevent offscreen UI placement
« on: 09 November 2024, 18:25 »
Hi Roman, I just hit an interesting issue in clrmamepro that cropped up a long time ago w/ my front end we had to code around.
I'm not sure what produced it, perhaps some combo of windows key + arrows with snap, but clrmame when it saved out to settings.xml put a large negative number in its UI position settings.  The next time the app was run, it couldn't be displayed on any of my multiple screens and you couldn't 'get to it' w/ alt-tab etc.
I had to kill the UI portion of settings.xml and restart.  So maybe you need an extra check to prevent incorrect/negative co-ordinates from being used.  This is my regular working section, I think <right> ended up like -3544 or something:

<Clrmame>
      <UI>
         <window>
            <right>2569</right>
            <top>0</top>
            <left>1271</left>
            <bottom>1401</bottom>
         </window>
         <activeTab>0</activeTab>
      </UI>
   </Clrmame>

6
clrmame Discussion / Unnecessary dialogue?
« on: 11 September 2024, 20:48 »
If you have loaded a software list, is there a reason to have the top-level list dialogue vs. just displaying the software list dialogue?
I've made the mistake a few times of setting my options in the top dialogue instead of the bottom one when using a software list.

7
Is there a way to get the clone's name to appear in the unexpanded new scanner result like old clrmame; so I know in this instance at a glance to get the automatm zip without expanding the branch?

8
clrmame Discussion / New scanner having trouble w/ neogeo.xml
« on: 25 August 2024, 17:16 »
Different behaviour between classic cmpro and the latest new scanner using the \hash\neogeo.xml list.
cmpro doesn't report anything incorrect w/ the PD set.
the new scanner flags 50 as partly wrong.  It thinks present items are unneeded.  Attaching output and screenshot.

9
So I currently have 35 \mame\software directories with contents.
With each MAME release how can I check them all in the fewest moves. :)
Can I use mame -listsoftware to an xml file and then use the scanner to take care of all 35 directories in one swoop somehow? Or is there another easier way?  Actually does -listsoftware contain the same information as the \hash\*.xml files?

10
clrmame Discussion / New scanner, filtering
« on: 23 August 2024, 18:38 »
So I set up the scanner to take the a2600.xml from MAME.
I left the rom paths c:\mame\roms and c:\mame\software (the a2600 directory exists in c:\mame\software).
I then ran the scanner with the attached settings and it tried to remove as uneeded all the non-a2600 content and eventually crashed/closed as my temp directory on a ramdrive filled up completely.

With these settings I feel I should probably using filtering or pattern of some kind but I haven't done that before.. or is the preferred way to just change the rom path to the a2600 directory.

11
Morning Roman (UTC-7), I just got around to trying your two new apps and am pleased w/ the speed and efficiency.  I'm glad you're having fun again w/ 'new code'. :)

Couple of questions:
1. How soon are the exports xmls purged?  They're adding up with as frequently as I build MAME; is there a setting for their removal, like 'one day' or something?
2. Could there be an option to remove add files after fixing in the *scanner* or could you add a button like legacy cmpro to jump between scanner and rebuilder? My use case is I download needed MAME files to my desktop (an add rom path) and then run the scanner and would like it (or the rebuilder) to clean up after itself. :)

Have a great day -

12
Hi Roman, is there a way to have cmpro use as many CPU cores as possible to run through its deep -verify check on a CHD scan?  I'd still like to finish off checking my collection (made it to the guitar freaks last time) but it seems to do one at a time and take a good amount of time.  I thought I saw an option for cores somewhere in my wanderings of your settings.  Thanks -

13
clrmame Discussion / Full Merge Mode
« on: 27 February 2024, 00:19 »
Hi Roman, troubleshooting all the CHD delta stuff and unavailables after audit recently, I switched from my long standing 'Normal Mode' to 'Hash Collision Name' for the Full Merge Mode to see if that would help on some rebuilds.  What's the difference and is it rare to use that mode vs 'Normal' or should I?

14
Been looking at this for a couple of days brought on by an audit in the MAME UI (F1) and the available filter.  Shows 14 damaged delta CHDs that can't be -verify or -info'ed with chdman. Before I posted at mametesters I was hoping for a confirmation here, note that clrmame doesn't flag these w/ default settings.  Possible commonality? CHDs marked as 'Bad Dump'.

Current tip of tree chdman.exe (or release .262) is producing some delta chds that will error on run with 'CHD ERROR: Decompression error'. Resulting in machine placement into unavailable filter folder in MAME UI.

One such example is the child/clone photoply_sprt_xt_2004_sp_u.chd in Photo Play Spirit Xtreme (Spanish) / photopsxsp

Steps to repro:
1. Use full merged storage method.
2. Place the two Photo Play Spirit Xtreme (Spanish) CHDs into their appropriate directory:
"C:\MAME\Roms\photopsxsp\photoply_sprt_xt_2004_sp_u.chd"
"C:\MAME\Roms\photopsxsp\photoply_sprt_xt_2004_sp.chd"

7,283,106,173 photoply_sprt_xt_2004_sp.chd
3,427,733,716 photoply_sprt_xt_2004_sp_u.chd

3. Launch MAME.exe and do an audit with F1 from the UI.
4. Confirm Photo Play Spirit Xtreme (Spanish) is not present in the Unavailable filter/folder.
5. Convert the child CHD to a delta w/ clrmamepro or manually.
6. New child CHD gets cut down to size to:

1,977,511,281 photoply_sprt_xt_2004_sp_u.chd

7. Attempt to verify this chd:
\MAME\ROMs\photopsxsp>chdman verify -i photoply_sprt_xt_2004_sp_u.chd -ip photoply_sprt_xt_2004_sp.chd
chdman - MAME Compressed Hunks of Data (CHD) manager 0.262 (mame0262-152-g0636e54bb60)
Error opening CHD file (photoply_sprt_xt_2004_sp_u.chd): Decompression error
Fatal error occurred: 1

8. Run audit in MAME's UI with F1.
9. Observe Photo Play is now in the unavailable filter/folder due to the error.
10. A normal run with clrmamepro does not find this.


---
c:\O\Games\MAME\ROMs\photopsxsp>chdman info -v -i photoply_sprt_xt_2004_sp_u.chd
chdman - MAME Compressed Hunks of Data (CHD) manager 0.262 (mame0262-152-g0636e54bb60)
Error opening CHD file (photoply_sprt_xt_2004_sp_u.chd): Decompression error
Fatal error occurred: 1

Before delta creation, child CHD is ok:
c:\Users\jhard\Desktop\ROMs\MAME 0.262 CHDs (merged)\photopsxsp>chdman info -i photoply_sprt_xt_2004_sp_u.chd
chdman - MAME Compressed Hunks of Data (CHD) manager 0.262 (mame0262)
Input file:   photoply_sprt_xt_2004_sp_u.chd
File Version: 5
Logical size: 160,041,885,696 bytes
Hunk Size:    4,096 bytes
Total Hunks:  39,072,726
Unit Size:    512 bytes
Total Units:  312,581,808
Compression:  lzma (LZMA), zlib (Deflate), huff (Huffman), flac (FLAC)
CHD size:     3,427,733,716 bytes
Ratio:        2.1%
SHA1:         dac230cae6efaa24362260101d39b421d5fccd45
Data SHA1:    5c60dcfee2c635e4c20fa733aad37c60c003b600
Metadata:     Tag='GDDD'  Index=0  Length=37 bytes
              CYLS:310101,HEADS:16,SECS:63,BPS:512.

c:\Users\jhard\Desktop\ROMs\MAME 0.262 CHDs (merged)\photopsxsp>chdman verify -i photoply_sprt_xt_2004_sp_u.ch
chdman - MAME Compressed Hunks of Data (CHD) manager 0.262 (mame0262)
Raw SHA1 verification successful!
Overall SHA1 verification successful!

Actual delta CHD creation goes through 100%:
c:\O\Games\MAME\ROMs\photopsxsp>chdman copy -i photoply_sprt_xt_2004_sp_u.chd -op photoply_sprt_xt_2004_sp.chd -o newchild.chd
chdman - MAME Compressed Hunks of Data (CHD) manager 0.262 (mame0262)
Output CHD:   newchild.chd
Parent CHD:   photoply_sprt_xt_2004_sp.chd
Input CHD:    photoply_sprt_xt_2004_sp_u.chd
Compression:  lzma (LZMA), zlib (Deflate), huff (Huffman), flac (FLAC)
Hunk size:    4,096
Logical size: 160,041,885,696
Compression complete ... final ratio = 1.2%

02/22/2024  12:18 PM     1,977,511,281 newchild.chd

Info and verify of new delta CHD fails and goes to unavailable upon audit.
c:\O\Games\MAME\ROMs\photopsxsp>chdman info -i newchild.chd
chdman - MAME Compressed Hunks of Data (CHD) manager 0.262 (mame0262)
Error opening CHD file (newchild.chd): Decompression error
Fatal error occurred: 1

15
clrmame Discussion / Delta CHDs new feature.
« on: 21 October 2023, 17:55 »
Hi Roman, I assume you've seen:
https://github.com/mamedev/mame/commit/d1172bf710f2a7b1777ed7687f5ba65748d90ee9

This could lead to significant savings on child CHDs becoming deltas of their parents. Have you got your mind around how to support it? I'm not sure how to produce one of these deltas, but a guide might be nice for the potential space savings.

16
clrmame Discussion / Exclude a whole driver?
« on: 24 August 2022, 17:18 »
Hi Roman, you probably saw what happened today w/ kpython2. :) I've never had to look for it but does clrmame have a way to 'exclude' a driver's machines?  Could we say run everything as normal (scanner / rebuilder) but ignore all kpython2 games?  Cheers -

17
clrmame Discussion / Help req: CHD errors and renaming reqs.
« on: 18 January 2020, 19:10 »
Hi Roman, I've outgrown my NVME 2TB SSD which I was keeping a full set of MAME on w/ CHDs.  So I've moved the CHDs to a second SATA SSD.  I'm trying to do this for rompath:
c:\o\games\mame\roms
d:\chds

CHDs are stored in d:\chds\setname\*.chd structure.

I've added those to clrmame in settings rom-path (and mame.ini of course).
Mame plays fine and can find the CHDs, no problem there.

When I audit with clrmame I am getting a bunch of wrong name messages that I never did before, here's a sample:
wrong name: D:\CHDs\area51mx [wrong: D:\CHDs\area51mx] [right: a51mxr3k] [not fixed]
wrong name: D:\CHDs\area51ta [wrong: D:\CHDs\area51ta] [right: area51t] [not fixed]
wrong name: D:\CHDs\blitz [wrong: D:\CHDs\blitz] [right: blitz11] [not fixed]
wrong name: D:\CHDs\bm2ndmix [wrong: D:\CHDs\bm2ndmix] [right: bm2ndmxa] [not fixed]
wrong name: D:\CHDs\bmcompmx [wrong: D:\CHDs\bmcompmx] [right: hmcompmx] [not fixed]

Then I get the following messages referencing a wrong SysDefPath and clrmame wanting to put the CHDs back to their prior location it seems:
2 Spicy [folder: 2spicy]
wrong SysDefPath: 2spicy [wrong: D:\CHDs\] [right: C:\O\Games\MAME\ROMs\]
Area 51: Site 4 (HD Rev 2.01, September 7, 1998) [folder: a51site4]
wrong SysDefPath: a51site4 [wrong: D:\CHDs\] [right: C:\O\Games\MAME\ROMs\]

So where in clrmame can I re-set the sysdefpath for the CHDs to go to the new d:\CHDs location and what is happening w/ the renaming requests for about these 30 CHDs?  Thanks!

18
Hi Roman, I'm getting into Visual Pinball again after 6 years, laugh.  I'm looking at clrmame to help with ROM usage, I wonder if it can keep unique pinmame roms in one location and leave mame roms used in both in another.  To explain:

c:\mame\roms
c:\vp\roms

\mame\roms has a lot of the pinmame roms already, I want that to remain where it is so I get a perfect result w/ a scan of mame.exe.
\vp\roms is missing about half of vpmame.exe's supported roms.

I have rebuilt vpmame.exe's roms from \mame\roms into \vp\roms.  So I now have of course unwanted duplication between the two directories.  I can easily have vpmame use its ROM paths to draw from \mame\roms and \vp\roms.

So the question.  Can I have clrmame somehow create *unique* to pinmame roms in the \vp\roms directory while also recognizing the shared roms in \mame\roms so I can get a 100% scan result for pinmame between the two directories.  Does that make sense?

19
Hi Roman, hope all is well in Germany. 

Last few days clrmame is reporting something interesting, a bunch of games that don’t have any ROMs in them but are missing the set.  Is this you or MAME? :) Cheers –

Black Velvet [system: Model 110 - folder: blvelvet - manufacturer: Game Plan - size: 4kb]
missing set: Black Velvet

Camel Lights [system: Model 110 - folder: camlight - manufacturer: Game Plan - size: 4kb]
missing set: Camel Lights

Chuck-A-Luck [system: Model 110 - folder: chucklck - manufacturer: Game Plan - size: 4kb]
missing set: Chuck-A-Luck

Circa 1933 [system: Allied System - folder: circa33 - manufacturer: Fascination Int. - size: 3kb]
missing set: Circa 1933

Disco '79 [system: Allied System - folder: disco79 - manufacturer: Allied Leisure - size: 3kb]
missing set: Disco '79

Eros One [system: Allied System - folder: erosone - manufacturer: Fascination Int. - size: 3kb]
missing set: Eros One

Flame of Athens [system: Allied System - folder: foathens - manufacturer: Allied Leisure - size: 3kb]
missing set: Flame of Athens

Foxy Lady [system: Model 110 - folder: foxylady - manufacturer: Game Plan - size: 4kb]
missing set: Foxy Lady

Hearts & Spades [system: Allied System - folder: heartspd - manufacturer: Allied Leisure - size: 3kb]
missing set: Hearts & Spades

Hoe Down [system: Allied System - folder: hoedown - manufacturer: Allied Leisure - size: 3kb]
missing set: Hoe Down

Real [system: Model 110 - folder: real - manufacturer: Game Plan - size: 4kb]
missing set: Real

Rio [system: Model 110 - folder: rio - manufacturer: Game Plan - size: 4kb]
missing set: Rio

Roy Clark - The Entertainer [system: Allied System - folder: royclark - manufacturer: Fascination Int. - size: 3kb]
missing set: Roy Clark - The Entertainer

Star Shooter [system: Allied System - folder: starshot - manufacturer: Allied Leisure - size: 3kb]
missing set: Star Shooter

Super Picker [system: Allied System - folder: suprpick - manufacturer: Allied Leisure - size: 3kb]
missing set: Super Picker

Take Five [system: Allied System - folder: takefive - manufacturer: Allied Leisure - size: 3kb]
missing set: Take Five

Thunderbolt [system: Allied System - folder: thndbolt - manufacturer: Allied Leisure - size: 3kb]
missing set: Thunderbolt

Pages: [1]

Page created in 0.077 seconds with 20 queries.