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: batch mode question

« on: 04 July 2015, 22:12 »

looks like that's not the culprit, the new nightly build cmp20150704 hasn’t fixed it yet... I found that if I changed the OS display language from my local language to English, the dialogs looked fine.

the contrastive screenshots

2

clrmame Discussion / Re: batch mode question

« on: 27 June 2015, 08:44 »

Now I know why. The profiler options window use MS Sans Serif font, and my OS has this font, so it looks fine. But the batcher options window use MS Shell Dlg font, but there isn't a MS Shell Dlg font in my OS, so it looks bad. I don't change anything about fonts, maybe related to the OS region. All other options windows use MS Shell Dlg font have the same problem.

3

clrmame Discussion / Re: batch mode question

« on: 27 June 2015, 07:23 »

Yes, I found it. I thought it's in the batcher option. Sorry for the post.
By the way, see all the screenshots above, why do some words have been interrupted?

4

clrmame Discussion / Re: batch mode question

« on: 26 June 2015, 20:21 »

No. I can't find an option for it.

5

clrmame Discussion / batch mode question

« on: 26 June 2015, 17:49 »

Hello Roman,
Can you hide the prompts which only have OK, OK TO ALL and Stop options when loading datfiles in batch mode? These prompts pause the batch mode, I have to click OK TO ALL to continue. It means I have to wait for it...

6

clrmame Discussion / Re: Sets, ROMs, Samples and CHDs question

« on: 18 June 2015, 22:27 »

Yes. Thank you!

7

clrmame Discussion / Re: Sets, ROMs, Samples and CHDs question

« on: 18 June 2015, 20:18 »

Thanks, Roman.
Yes, some of the sets only consist of the chd or sample, but some not

Code: [Select]

<machine name="2spicy" sourcefile="lindbergh.c" romof="lindbios">
<description>2 Spicy</description>
<year>2007</year>
<manufacturer>Sega</manufacturer>
<biosset name="bios0" description="6.0.0010 alternate version" default="yes"/>
<biosset name="bios1" description="6.0.0009"/>
<biosset name="bios2" description="6.0.0010"/>
<rom name="6.0.0010a.bin" merge="6.0.0010a.bin" bios="bios0" size="1048576" crc="10dd9b76" sha1="1fdf1f921bc395846a7c3180fbdbc4ca287a9670" region=":pci:1f.0" offset="0"/>
<rom name="6.0.0009.bin" merge="6.0.0009.bin" bios="bios1" size="1048576" crc="5ffdfbf8" sha1="605bc4967b749b4e6d13fc2ebb845ba956a259a7" region=":pci:1f.0" offset="0"/>
<rom name="6.0.0010.bin" merge="6.0.0010.bin" bios="bios2" size="1048576" crc="ea2bf888" sha1="c9c5b6f0d4f4f36620939b15dd2f128a74347e37" region=":pci:1f.0" offset="0"/>
<rom name="fpr-24370b.ic6" merge="fpr-24370b.ic6" size="4194304" crc="c3b021a4" sha1="1b6938a50fe0e4ae813864649eb103838c399ac0" region=":pci:1e.0:03.0" offset="0"/>
<rom name="vid_bios.u504" merge="vid_bios.u504" size="65536" crc="f78d14d7" sha1="f129787e487984edd23bf344f2e9500c85052275" region=":pci:01.0:00.0" offset="0"/>
<rom name="317-0491-com.bin" size="8192" status="nodump" region=":pic" offset="0"/>
<disk name="mda-c0004a_revb_lindyellow_v2.4.20_mvl31a_boot_2.01" merge="mda-c0004a_revb_lindyellow_v2.4.20_mvl31a_boot_2.01" sha1="e13da5f827df852e742b594729ee3f933b387410" region="cf" index="0" writable="no"/>
<disk name="dvp-0027a" sha1="da1aacee9e32e813844f4d434981e69cc5c80682" region="dvd" index="0" writable="no"/>

8

clrmame Discussion / Sets, ROMs, Samples and CHDs question

« on: 18 June 2015, 19:35 »

I use the "Create..." feature, and choose MAME 0.162 binary as source, the settings are
Settings -> Full Merge Mode: Hash Collision Name
Misc Profiler Options -> Parsing Options -> Parser ROM 'merge' tags: enabled (default)
Misc Profiler Options -> Parsing Options -> Parser DISK 'merge' tags: enabled (default)
Misc Profiler Options -> Hash collision -> Naming Pattern: %f\%1 (default)
Misc Profiler Options -> Hash collision: All Clones in Relationship

My roms are complete, and I've already disabled samples and chds, but the scan results are


I have to disable sets too, then the scan results are OK, but clrmame says "It's not recommended to do a scan without having 'set' enabled". Is there somthing wrong? I attach the miss list here.

9

clrmame Discussion / Re: old dat format question

« on: 17 June 2015, 12:14 »

About the bios sets with samples, I found another one:

Code: [Select]

<machine name="allied" sourcefile="allied.c" isbios="yes" sampleof="genpin">
<description>Allied System</description>
<year>1977</year>
<manufacturer>Allied Leisure</manufacturer>
<rom name="6530-009.u5" size="1024" crc="e4fb64fb" sha1="a3d9de7cbfb42180a860e0bbbeaeba96d8bd1e20" region="maincpu" offset="1400"/>
<rom name="6530-010.u6" size="1024" crc="dca980dd" sha1="3817d75413854d889fc1ce4fd6a51d820d1e0534" region="maincpu" offset="1800"/>
<rom name="6530-011.u3" size="1024" crc="13f42789" sha1="baa0f73fda08a3c5d6f1423fb329e4febb07ef97" region="maincpu" offset="1c00"/>
<device_ref name="m6504"/>
<device_ref name="speaker"/>
<device_ref name="samples"/>
<device_ref name="pia6821"/>
<device_ref name="pia6821"/>
<device_ref name="pia6821"/>
<device_ref name="pia6821"/>
<device_ref name="pia6821"/>
<device_ref name="mos6530"/>
<device_ref name="mos6530"/>
<device_ref name="mos6530"/>
<device_ref name="timer"/>
<sample name="bumper"/>
<sample name="chime1"/>
<sample name="chime2"/>
<sample name="chime3"/>
<sample name="chime4"/>
<sample name="hole"/>
<sample name="knocker"/>
<sample name="sling"/>
<sample name="coinin"/>
<chip type="cpu" tag="maincpu" name="M6504" clock="893137"/>
<chip type="audio" tag="mechvol" name="Speaker"/>
<chip type="audio" tag="samples" name="Samples"/>
<sound channels="1"/>
                .....
</machine>clrmame won't scan the samples in bios set, but if I scan it through using the whole datfile, I won't find any error, becasue there are other places of the datfile have code like this:

Code: [Select]

<machine name="mbossy" sourcefile="gp_2.c" ismechanical="yes" sampleof="genpin">
<description>Mike Bossy</description>
<year>1982</year>
<manufacturer>Game Plan</manufacturer>
<rom name="mb_a.716" size="2048" status="nodump" region="roms" offset="0"/>
<rom name="mb_b.716" size="2048" status="nodump" region="roms" offset="800"/>
<rom name="mb_c.716" size="2048" status="nodump" region="roms" offset="1000"/>
<rom name="mb.u9" size="2048" crc="dfa98db5" sha1="65361630f530383e67837c428050bcdb15373c0b" region="cpu2" offset="3800"/>
<rom name="mb.u10" size="2048" crc="2d3c91f9" sha1="7e1f067af29d9e484da234382d7dc821ca07b6c4" region="cpu2" offset="3000"/>
<device_ref name="z80"/>
<device_ref name="nvram"/>
<device_ref name="speaker"/>
<device_ref name="samples"/>
<device_ref name="i8255"/>
<device_ref name="z80ctc"/>
<device_ref name="timer"/>
<sample name="bumper"/>
<sample name="chime1"/>
<sample name="chime2"/>
<sample name="chime3"/>
<sample name="chime4"/>
<sample name="hole"/>
<sample name="knocker"/>
<sample name="sling"/>
<sample name="coinin"/>
<chip type="cpu" tag="maincpu" name="Z80" clock="2457600"/>
<chip type="audio" tag="mechvol" name="Speaker"/>
<chip type="audio" tag="samples" name="Samples"/>
<sound channels="1"/>
                .....
</machine>clrmame will scan the same samples in non bios sets, so I won't see any error.

10

clrmame Discussion / Re: old dat format question

« on: 17 June 2015, 11:52 »

I'm sorry. I thought runnable="no" means it's a bios...
The code I posted at the beginning of this thread is actually converted from the code at #5. It seems that there is no such a "device" definition in old datfile format, so you're right, the old format should be deprecated.

11

clrmame Discussion / Re: old dat format question

« on: 17 June 2015, 08:34 »

there is no sample support for bios sets at all

What doesn't support it? clrmame or old datfile format?
The new datfile format can support it, I've already tested this.

since it's not yet used in MAME

But I think MAME has used it already. Here is part of the MAME 0.162 XML output:

Code: [Select]

<machine name="nes_bandai_pt554" sourcefile="src/emu/bus/nes/pt554.c" isdevice="yes" runnable="no" sampleof="ftaerobi">
<description>NES Cart Bandai PT-554 PCB</description>
<sample name="00"/>
<sample name="01"/>
<sample name="02"/>
<sample name="03"/>
<sample name="04"/>
<sample name="05"/>
<sample name="06"/>
<sample name="07"/>
<chip type="audio" tag=":addon" name="Speaker"/>
<chip type="audio" tag=":samples" name="Samples"/>
<sound channels="1"/>
</machine>Do you mean although MAME lists bios sets with samples in the XML output, it hasn't use these samples yet?

I put it on the to-do list....but don't expect it too soon

Thank you. As you said, the old datfile format is deprecated, so it's not urgent.

12

clrmame Discussion / Re: old dat format question

« on: 13 June 2015, 05:42 »

It‘s not a dat file 15 years ago. It was generated by a tool recently, but the tool was made many yeas ago, so it output the dat file in old format.
Have a good holiday!

13

clrmame Discussion / old dat format question

« on: 12 June 2015, 20:14 »

Clrmamepro will ignore samples in "resource" field, is it a problem?
for example

Code: [Select]

resource (
    name nes_bandai_pt554
    description "NES Cart Bandai PT-554 PCB"
    sourcefile pt554.c
    sampleof ftaerobi
    sample 00
    sample 01
    sample 02
    sample 03
    sample 04
    sample 05
    sample 06
    sample 07
)
Clrmamepro won't scan the sample ftaerobi, just like it doesn't exist in the dat file.

14

clrmame Discussion / Re: Cannot Remove File error when scanning solid .7z

« on: 23 March 2015, 06:35 »

I see. Thank you for your answer.

15

clrmame Discussion / Re: Cannot Remove File error when scanning solid .7z

« on: 21 March 2015, 06:24 »

@Roman
 I'm sorry I didn't say clearly. I want to use the lowest compression level, not the highest one.

I always recompress roms with torrentzip after rebuliding, so it's actually unnecessary to compress roms with the highest zip compression during rebuilding, the best way is to compress them with the lowest compression to save time, is it right?

16

clrmame Discussion / Re: Cannot Remove File error when scanning solid .7z

« on: 20 March 2015, 20:21 »

@oxyandy
Hello,
how to change the compression level of zip? there is only 7z and rar option in the compressor setting.