21
clrmame Discussion / Re: delta chds, cmpro test version
« on: 28 October 2023, 19:52 »
D'oh, I was watching the other thread and missed this! Downloaded the new release build and am testing. Thanks Roman!
- 29 April 2024, 02:05
- 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]
22
clrmame Discussion / Re: Delta CHDs new feature.
« on: 25 October 2023, 19:32 »
Looks like good planning so far Roman.
[Update] Occurs to me that there may be potential with conversion and backing up original clone CHDs for folks to run out of HD space, does clrmame error out gracefully at that point?
[Update] Occurs to me that there may be potential with conversion and backing up original clone CHDs for folks to run out of HD space, does clrmame error out gracefully at that point?
23
clrmame Discussion / Re: Delta CHDs new feature.
« on: 23 October 2023, 23:20 »
One of the things that's taking time here manually doing it is that because I use split-sets the CHD clones are in their own directories so I have to copy the parent into the clone directory before kicking off the delta operation. Are you accounting for this 'split' with your cmpro technique? Actually I wonder if chdman can take full paths for its -input -output arguments or if it expects them to be in the same folder.
24
clrmame Discussion / Re: Delta CHDs new feature.
« on: 23 October 2023, 20:02 »
Yes these conversions take a while even on quick machines with beefy memory and cores. I like the idea of being able to identify the candidates and then act on one or all of them; so folks could go one at a time to verify things are progressing properly and then turn the system loose on the rest overnight or whatever. Like I said at Mameworld I've shaved off 200GB already on just the kpython2.cpp clone CHDs manually doing about 12 of them.
25
clrmame Discussion / Re: Delta CHDs new feature.
« on: 23 October 2023, 19:20 »
Looking good, see you have been interacting w/ Vas and getting good info on mameworld.
26
clrmame Discussion / Re: Delta CHDs new feature.
« on: 22 October 2023, 16:18 »
Roman, the new .exe worked. It didn't flag the four CHDs I've converted. Good job. 
27
clrmame Discussion / Re: Delta CHDs new feature.
« on: 21 October 2023, 20:41 »
I could see people abandoning the child .chds and just keeping the deltas, so was curious if you'd have to account for that. Guess we'll see!
[Update] I just converted gtfore04a and it went from 1GB to a delta of 90MB. Clrmame scan flagged the chd 'missing' though it was in the right place w/ the right name, fwiw.
[Update2] Roman, it would be cool if you could use Clrmame or one of your external tools to find eligable CHDs and prompt to create their deltas all in one pass.
chdman copy -i sf2049tea.chd -op sf2049te.chd -o sf2049tea-delta.chd
mv sf2049tea.chd sf2049tea-abs.chd
mv sf2049tea-delta.chd sf2049tea.chd
[Update] I just converted gtfore04a and it went from 1GB to a delta of 90MB. Clrmame scan flagged the chd 'missing' though it was in the right place w/ the right name, fwiw.
[Update2] Roman, it would be cool if you could use Clrmame or one of your external tools to find eligable CHDs and prompt to create their deltas all in one pass.
chdman copy -i sf2049tea.chd -op sf2049te.chd -o sf2049tea-delta.chd
mv sf2049tea.chd sf2049tea-abs.chd
mv sf2049tea-delta.chd sf2049tea.chd
28
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.
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.
29
clrmame Discussion / Re: Exclude a whole driver?
« on: 24 August 2022, 17:48 »
Cool, thanks. It's basically a driver dropping in Konami rhythm games DVD CHDs. 350GB. 
30
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 -
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 -
31
clrmame Discussion / Re: Help req: CHD errors and renaming reqs.
« on: 18 January 2020, 21:06 »
Thanks Roman, that worked. I unbound the systems and re-ran the full scan. Did not get the renaming options prompt this time around, so things look good to go.
What were those names that it was suggesting? They weren't the setname and they weren't the chd names, something internal?
What were those names that it was suggesting? They weren't the setname and they weren't the chd names, something internal?
32
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!
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!
33
clrmame Discussion / Wonder if clrmame can combine roms for MAME / PinMAME in two locations
« on: 07 November 2019, 18:21 »
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?
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?
34
clrmame Discussion / Re: Tip of Mame trunk and reportedly missing sets.
« on: 23 December 2016, 00:15 »Get 4.031c
Cheers, great work as always Roman. Happy Holidays fellow 20-year Mame-r.
John IV
35
clrmame Discussion / Tip of Mame trunk and reportedly missing sets.
« on: 22 December 2016, 18:54 »
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
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 [2]