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 - yescabernetnointernet

Pages: [1]
1
clrmame Discussion / [REBUILDER] multiple INPUT sources
« on: 04 October 2023, 15:48 »
Heya Roman!

Is it possible to declare 1 or more paths to the -i switch?

I'm getting this error and in documentation there's no mention on how many INPUT paths should be used:
Code: [Select]
--input: At Most 1 required but received 2
Run with --help for more information.
Quote
-i, --input: The rebuilder input folder. This folder is checked for matching data. This option is mandatory and the folder has to exist.


I was thinking something like this:
Code: [Select]
rebuilder -i "d:\roms\oldmame" "g:\backups\mames", or this if you prefer:
Code: [Select]
rebuilder -i f:\games\fixme -i s:\data\games\mame01 -i s:\data\romsets\arcade

2
clrmame Discussion / why some sample are unnedded?
« on: 26 August 2023, 20:03 »
cmp will always delete unneeded samples (which consist of whole machines) and then - running a 2nd NEW SCAN instance - will complain those previously unneeded sets are now missing.

Copying the parent sample into its clone sample will again then lead to unneeded.
Code: [Select]
$ cp samples/moepro90.zip samples/nes_jf29.zip
Example: nes_jf29 VS moepro90 http://adb.arcadeitalia.net/?mame=nes_jf29

Code: [Select]
NES Cart Bandai BT-554 PCB [folder: nes_bandai_pt554 - sampleparent: ftaerobi - size: 0]
missing device: NES Cart Bandai BT-554 PCB
missing sample: 00
missing sample: 01
missing sample: 02
missing sample: 03
missing sample: 04
missing sample: 05
missing sample: 06
missing sample: 07

NES Cart Jaleco JF-13 PCB [folder: nes_jf13 - sampleparent: moepro - size: 0]
missing device: NES Cart Jaleco JF-13 PCB
missing sample: 00
missing sample: 01
missing sample: 02
missing sample: 03
missing sample: 04
missing sample: 05
missing sample: 06
missing sample: 07
missing sample: 08
missing sample: 09
missing sample: 10
missing sample: 11
missing sample: 12
missing sample: 13
missing sample: 14
missing sample: 15

NES Cart Jaleco JF-19 + ADPCM (Moero!! Pro Yakyuu 88) PCB [folder: nes_jf19_pcm - sampleparent: moepro88 - size: 0]
missing device: NES Cart Jaleco JF-19 + ADPCM (Moero!! Pro Yakyuu 88) PCB
missing sample: 00
missing sample: 01
missing sample: 02
missing sample: 03
missing sample: 04
missing sample: 05
missing sample: 06
missing sample: 07
missing sample: 08
missing sample: 09
missing sample: 10
missing sample: 11
missing sample: 12
missing sample: 13
missing sample: 14
missing sample: 15
missing sample: 16
missing sample: 17
missing sample: 18
missing sample: 19

NES Cart Jaleco JF-23 (Shin Moero Pro Yakyuu) PCB [folder: nes_jf23 - sampleparent: smoepro - size: 0]
missing device: NES Cart Jaleco JF-23 (Shin Moero Pro Yakyuu) PCB
missing sample: 00
missing sample: 01
missing sample: 02
missing sample: 03
missing sample: 04
missing sample: 05
missing sample: 06
missing sample: 07
missing sample: 08
missing sample: 09
missing sample: 10
missing sample: 11
missing sample: 12
missing sample: 13
missing sample: 14
missing sample: 15
missing sample: 16
missing sample: 17
missing sample: 18
missing sample: 19

NES Cart Jaleco JF-24 (Terao no Dosukoi Oozumou) PCB [folder: nes_jf24 - sampleparent: terao - size: 0]
missing device: NES Cart Jaleco JF-24 (Terao no Dosukoi Oozumou) PCB
missing sample: 00
missing sample: 01
missing sample: 02
missing sample: 03
missing sample: 04
missing sample: 05

NES Cart Jaleco JF-29 (Moe Pro! '90) PCB [folder: nes_jf29 - sampleparent: moepro90 - size: 0]
missing device: NES Cart Jaleco JF-29 (Moe Pro! '90) PCB
missing sample: 00
missing sample: 01
missing sample: 02
missing sample: 03
missing sample: 04
missing sample: 05
missing sample: 06
missing sample: 07
missing sample: 08
missing sample: 09
missing sample: 10
missing sample: 11
missing sample: 12
missing sample: 13
missing sample: 14
missing sample: 15
missing sample: 16
missing sample: 17
missing sample: 18
missing sample: 19

NES Cart Jaleco JF-33 (Moe Pro! Saikyou-hen) PCB [folder: nes_jf33 - sampleparent: mpsaikyo - size: 0]
missing device: NES Cart Jaleco JF-33 (Moe Pro! Saikyou-hen) PCB
missing sample: 00
missing sample: 01
missing sample: 02
missing sample: 03
missing sample: 04
missing sample: 05
missing sample: 06
missing sample: 07
missing sample: 08
missing sample: 09
missing sample: 10
missing sample: 11
missing sample: 12
missing sample: 13
missing sample: 14
missing sample: 15
missing sample: 16
missing sample: 17
missing sample: 18
missing sample: 19

Another example:
Code: [Select]
<machine name="nes_bandai_pt554" sourcefile="src/devices/bus/nes/pt554.cpp" isdevice="yes" runnable="no" sampleof="ftaerobi">
<description>NES Cart Bandai BT-554 PCB</description>
<device_ref name="speaker"/>
<device_ref name="samples"/>
<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>

3
clrmame Discussion / -listxml VS hash/*.xml
« on: 21 April 2023, 20:51 »
Hey Roman, just tried importing -listsoft into cmp and found out it's loading by itself all (all? Maybe... ?) Software Lists in one shot.

Soooooo... I'm asking you: what's the point of loading all different SOFT xmls from the hash/ folder of MAME?  :o

Sure there's something I'm missing, but I do not understand what... ...  ;D

4
OK... First of all, let's define a legend:

SET
ROMset
ROM
CHD
Some Name
mame/somena.zip
mame/somena.zip/chip01
mame/somena/harddisk.chd
(or mame/somena/)
(or mame/somena/chip01)



Hey Roman, I'd like to understand more about the settings for merged sets.


PROFILER > OPTIONS > MISC PROFILER OPTIONS
  • Parsing Options
    • Parse ROM 'merge' Tags
         Why someone would not to parse the merge attribute (as declared inside M. A. M. E.'s XML) of a clone's rom name?
         I mean, if I want my sets to be merged I need to tell clrmamepro to parse the merge attribute, right?
    • Parse DISK 'merge' Tags
         As above... I want my sets to be merged, so both roms and CHDs should be merged accordingly to what's declared inside M. A. M. E.'s XML.

  • Hash Collision(is this enabled only when Hash Collision Name is selected in Full Merge Mode?)
    • Single File
         This will put only roms with same sha1sum inside its clone's subdirectory, right?
    • Single Clone
         This will put ALL roms of each clone with same sha1sum inside the relative clone's subdirectory, right?
    • All Clones in Relationship
         ?


SETTINGS
  • Full Merge Mode
    • Normal Mode
         ?
    • Hash Collision Name
         "You use the hash collision naming convention fo all clone files, no matter if a hash collision happened or not."
         ? ... Please could you elaborate on this in simple terms :)


Looking at this excerpt as a reference, could you help me by reporting a concrete example?
Code: [Select]
<machine name="hotd4a" sourcefile="sega/lindbergh.cpp" cloneof="hotd4" romof="hotd4">
<description>The House of the Dead 4 (Export) (Rev A)</description>
<year>2005</year>
<manufacturer>Sega</manufacturer>
<biosset name="bios0" description="6.0.0010 alternate version"/>
<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-0427-com.bin" merge="317-0427-com.bin" size="8192" crc="ef4a120c" sha1="fcc0386fa708af9e010e40e1d259a6bd95e8b9e2" 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-0003a" sha1="46544e28735f55418dd78bd19446093874438264" region="dvd" index="0" writable="no"/>
[...]
## tuncated output ##
[...]
</machine>


If I understood correctly the merge mode, I should end up with this:

Parent romset
Code: [Select]
mame/hotd4.zip:
317-0427-com.bin

Parent CHD
Code: [Select]
mame/hotd4/:
dvp-0003b.chd

Clone CHD
Code: [Select]
mame/hotd4a/:
dvp-0003a.chd

BIOS romset
Code: [Select]
mame/lindbios.zip:
6.0.0009.bin
6.0.0010.bin
6.0.0010a.bin
fpr-24370b.ic6
vid_bios.u504

BIOS CHD
Code: [Select]
mame/lindbios/:
mda-c0004a_revb_lindyellow_v2.4.20_mvl31a_boot_2.01.chd


Thank you Roman!

5
Adding M. A. M. E.'s XML (-listxml) via "Profiler > Add DatFile..." is NOT recognized by clrmame: the DatFile is not detected, although the corresponding "mame.dat" file is generated (alongside "mame.xml").

mame.xml:
Code: [Select]
mame.exe -listxml > mame.xml
It only works with the official MAME 0.nnn full driver information in XML format (downloaded from https://www.mamedev.org/release.php ).




One interesting thing is the two XML files differs in size:
Code: [Select]
## MAME 0.246 full driver information in XML format ##
mame0246.xml
size = 271978244 bytes
SHA-1 = F53FE5CDCB5207F586CCD34070367E0FB87FA51C

## mame.exe -listxml > mame.xml ##
mame.xml
size = 543956490 bytes
SHA-1 = F9D6669071371A357627A64CB3A1273BE0BE3C4D

6
clrmame Discussion / [SOLVED] Separate paths CHD VS nonCHD?
« on: 04 December 2021, 18:16 »
Hi Roman!
I've done some searchings digging through "CHD" discussions here in the forum but that lead me to much more confusion and now I'm lost...  :o

I'm about reorganizing the entire folders structure of my retro library.
I'd like to accomplish this arrangement (using real names as easier-to-understand example):
Code: [Select]
ROM sets path:
Z:\mame\0238\sets\chd0\gtmr.zip

###

CHD sets path:
Z:\mame\0238\sets\chd1\sf2049.zip
Z:\mame\0238\sets\chd1\sf2049\sf2049.chd
Any suggestions?

Also, what if I would to merge only the .chd files leaving the rest of my collection non-merged?


Thaaank you!!  ;)

7
Hey Roman, any advices about NFS (Network File System) shares when using clrmamepro?

Any programs of any kinds I use they all work seamless on files remotely stored on my server via NFS share: I can play music / film via VLC with no issues at all, I can convert video / audio files, read+write Steam Library, etc...

See: https://www.emulab.it/forum/index.php?topic=6308.msg21189#msg21189
With clrmamepro I have problems with write operations (read operations are good and work just fine).
As soon clrmamepro needs to perform a write (Fix, Copy, etc...) it tries but suddenly get stuck forever and then goes into "Non Responding".
There is no way at all to close it, neither shutting down Windows will work because it will stay on trying to close clrmamepro. Nor I can unmount the share, Windows simply get stuck at trying it.

The only way to close / kill clrmamepro (or Windows) is to shutdown the server.

Code: [Select]
Locale    Remoto                                 Proprietà
-------------------------------------------------------------------------------
S:       \\SERVERNFS\path\to\share           UID=1000, GID=1000
                                                rsize=1048576, wsize=1048576
                                                mount=soft, timeout=1.6
                                                retry=1, locking=yes
                                                fileaccess=755, lang=ANSI
                                                casesensitive=no
                                                sec=sys


Any suggestions?

8
Hey Roman, as per topic's title is this a knwon (and right) behavior?
And if so, in this case, how should such a problem be handled, given that there are no files???  :o  ???

Here's my Scanner's reports about latest M. A. M. E. XML (0.238 at time of writing):
Code: [Select]
MC68705P5 Programmer [folder: 705p5prg - size: 0]
missing set: MC68705P5 Programmer

MC68705P3 Programmer [folder: 705p3prg - parent: 705p5prg - size: 0]
missing set: MC68705P3 Programmer

MC68705R3 Programmer [folder: 705r3prg - parent: 705p5prg - size: 0]
missing set: MC68705R3 Programmer

MC68705U3 Programmer [folder: 705u3prg - parent: 705p5prg - size: 0]
missing set: MC68705U3 Programmer

Sweet Micro Systems Mockingboard Sound/Speech I [folder: a2mockbd - size: 0]
missing device: Sweet Micro Systems Mockingboard Sound/Speech I

Acorn 40 Column VDU Interface [folder: acorn_vdu40 - size: 0]
missing device: Acorn 40 Column VDU Interface

Alto-II [folder: alto2 - size: 0]
missing set: Alto-II

Arkanoid MC68705P3 Interface [folder: arkanoid68705p3 - size: 0]
missing device: Arkanoid MC68705P3 Interface

Arkanoid MC68705P5 Interface [folder: arkanoid68705p5 - size: 0]
missing device: Arkanoid MC68705P5 Interface

PC/AT Motherboard [folder: at_mb - size: 0]
missing device: PC/AT Motherboard

Atari CAGE [folder: atari_cage - size: 0]
missing device: Atari CAGE

Atari CAGE Seattle [folder: atari_cage_seattle - size: 0]
missing device: Atari CAGE Seattle

Sprow LCD Display [folder: bbc_lcd - size: 0]
missing device: Sprow LCD Display

PPP Speakeasy 64 [folder: c64_speakeasy - size: 0]
missing device: PPP Speakeasy 64

Tasc ChessMachine EC Interface [folder: centronics_chessmec - size: 0]
missing device: Tasc ChessMachine EC Interface

CMS High Resolution Colour Graphics Card [folder: cms_hires - size: 0]
missing device: CMS High Resolution Colour Graphics Card

Compis HRG [folder: compis_hrg - size: 0]
missing device: Compis HRG

Compis UHRG [folder: compis_uhrg - size: 0]
missing device: Compis UHRG

DEC 2000 Model 300 AXP [folder: d2k300axp - size: 1mb]
missing set: DEC 2000 Model 300 AXP

DEC 2000 Model 500 AXP [folder: d2k500axp - size: 1mb]
missing set: DEC 2000 Model 500 AXP

Data East/Sega/Stern BSMT2000 Sound Board [folder: decobsmt - size: 0]
missing device: Data East/Sega/Stern BSMT2000 Sound Board

6x09 SuperSprite FM+ [folder: dragon_msx2 - size: 0]
missing device: 6x09 SuperSprite FM+

EXORterm 155 [folder: exorterm155 - size: 0]
missing set: EXORterm 155

EXORterm 155 Terminal [folder: exorterm155_terminal - size: 0]
missing device: EXORterm 155 Terminal

Famicom (w/ Disk System add-on) [folder: fds - parent: famicom - size: 0]
missing set: Famicom (w/ Disk System add-on)

SYS68K/CPU-20 [folder: fccpu20sbc - size: 0]
missing set: SYS68K/CPU-20

SYS68K/CPU-21A [folder: fccpu21asbc - parent: fccpu20sbc - size: 0]
missing set: SYS68K/CPU-21A

SYS68K/CPU-21B [folder: fccpu21bsbc - parent: fccpu20sbc - size: 0]
missing set: SYS68K/CPU-21B

SYS68K/CPU-21 [folder: fccpu21sbc - parent: fccpu20sbc - size: 0]
missing set: SYS68K/CPU-21

SYS68K/CPU-21S [folder: fccpu21ssbc - parent: fccpu20sbc - size: 0]
missing set: SYS68K/CPU-21S

SYS68K/CPU-21YA [folder: fccpu21yasbc - parent: fccpu20sbc - size: 0]
missing set: SYS68K/CPU-21YA

SYS68K/CPU-21YB [folder: fccpu21ybsbc - parent: fccpu20sbc - size: 0]
missing set: SYS68K/CPU-21YB

Gottlieb Sound rev. 1 with Votrax [folder: gotsndr1vt - size: 0]
missing device: Gottlieb Sound rev. 1 with Votrax

Intel 82371AB [folder: i82371ab - size: 0]
missing device: Intel 82371AB

15IE-00-013 [folder: ie15 - size: 0]
missing set: 15IE-00-013

IE15 Terminal [folder: ie15_terminal - size: 0]
missing device: IE15 Terminal

SGI IOC2 (Full House) [folder: ioc2f - size: 0]
missing device: SGI IOC2 (Full House)

SGI IOC2 (Guinness) [folder: ioc2g - size: 0]
missing device: SGI IOC2 (Guinness)

The ChessMachine DR [folder: isa_chessmdr - size: 0]
missing device: The ChessMachine DR

Roland MPU-401 MIDI Interface (ISA) [folder: isa_mpu401 - size: 0]
missing device: Roland MPU-401 MIDI Interface (ISA)

Mephisto Display Module 2 [folder: mdisplay2 - size: 0]
missing device: Mephisto Display Module 2

miniFORCE [folder: miniforce - size: 0]
missing set: miniFORCE

EDGE-1 Graphics f/1 2Mp Monitor (55K/60) [folder: mpcb849 - size: 32]
missing device: EDGE-1 Graphics f/1 2Mp Monitor (55K/60)

Roland MPU-401 MIDI Interface (C-bus) [folder: mpu_pc98 - size: 0]
missing device: Roland MPU-401 MIDI Interface (C-bus)

MSX Cartridge - FM-PAC [folder: msx_cart_fmpac - size: 0]
missing device: MSX Cartridge - FM-PAC

Namco Driver's Eyes PCB stack [folder: namco_de_pcb - size: 0]
missing device: Namco Driver's Eyes PCB stack

Namco System 21 DSP Setup (5x C67 type) [folder: namcos21_dsp_c67_device - size: 0]
missing device: Namco System 21 DSP Setup (5x C67 type)

NES Cart Konami VRC-7 PCB [folder: nes_vrc7 - size: 0]
missing device: NES Cart Konami VRC-7 PCB

Horizon (North Star Computers, 4MHz) [folder: nshrz - size: 1kb]
missing set: Horizon (North Star Computers, 4MHz)

Horizon (North Star Computers, 2MHz) [folder: nshrz2mhz - parent: nshrz - size: 1kb]
missing set: Horizon (North Star Computers, 2MHz)

Number Nine Revolution 512x32/1024x8 [folder: number_9_rev - size: 0]
missing device: Number Nine Revolution 512x32/1024x8

NEC PC-9801-118 [folder: pc9801_118 - size: 128kb]
missing device: NEC PC-9801-118

StrongARM Risc PC [folder: sarpc - parent: rpc600 - size: 4mb]
missing set: StrongARM Risc PC

SG-1000 FM Sound Unit [folder: sega_fm_unit - size: 0]
missing device: SG-1000 FM Sound Unit

Pioneer LDV-1000 Simulator [folder: simldv1000 - size: 0]
missing set: Pioneer LDV-1000 Simulator

Pioneer PR-8210 Simulator [folder: simpr8210 - size: 0]
missing set: Pioneer PR-8210 Simulator

Super Nintendo Entertainment System / Super Famicom (NTSC) [folder: snes - size: 0]
missing set: Super Nintendo Entertainment System / Super Famicom (NTSC)

Super Nintendo Entertainment System (PAL) [folder: snespal - parent: snes - size: 0]
missing set: Super Nintendo Entertainment System (PAL)

SWTPC 8212 Video Terminal [folder: swtpc8212 - size: 0]
missing set: SWTPC 8212 Video Terminal

SWTPC8212 Terminal [folder: swtpc8212_terminal - size: 0]
missing device: SWTPC8212 Terminal

SYS1121 [folder: sys1121 - size: 0]
missing set: SYS1121

Taito MC68705 MCU Interface [folder: taito68705 - size: 0]
missing device: Taito MC68705 MCU Interface

Taito MC68705 MCU Interface (Tiger-Heli) [folder: taito68705tiger - size: 0]
missing device: Taito MC68705 MCU Interface (Tiger-Heli)

Taito SJ Security MCU Interface [folder: taitosjsecmcu - size: 0]
missing device: Taito SJ Security MCU Interface

Mousepacket Designs Colour VDU Card [folder: tanbus_mpvdu - size: 0]
missing device: Mousepacket Designs Colour VDU Card

Ralph Allen Colour VDU Card [folder: tanbus_ravdu - size: 0]
missing device: Ralph Allen Colour VDU Card

VGM player [folder: vgmplay - size: 0]
missing set: VGM player

PPP Speakeasy VIC-20 [folder: vic20_speakeasy - size: 0]
missing device: PPP Speakeasy VIC-20

Want PC Text/Image/Graphics Controller [folder: wangpc_tig - size: 512]
missing device: Want PC Text/Image/Graphics Controller


Here's attached screeshot:



As an exmaple, please have a look at entry <machine name="705p5prg" sourcefile="m68705prg.cpp"> inside M. A. M. E. XML:
Code: [Select]
<machine name="705p5prg" sourcefile="m68705prg.cpp">
<description>MC68705P5 Programmer</description>
<year>1984</year>
<manufacturer>Motorola</manufacturer>
<device_ref name="generic_socket"/>
<device_ref name="generic_socket"/>
<device_ref name="m68705p5"/>
<chip type="cpu" tag="mcu" name="Motorola MC68705P5" clock="1000000"/>
<sound channels="0"/>
<input players="1">
<control type="only_buttons" buttons="2"/>
</input>
<port tag=":SW">
</port>
<driver status="good" emulation="good" savestate="supported" nosoundhardware="yes"/>
<device type="romimage" tag="eprom_image" interface="eprom">
<instance name="romimage1" briefname="rom1"/>
<extension name="bin"/>
<extension name="rom"/>
</device>
<device type="romimage" tag="mcu_image" interface="mcu">
<instance name="romimage2" briefname="rom2"/>
<extension name="bin"/>
<extension name="rom"/>
</device>
<slot name="eprom_image">
</slot>
<slot name="mcu_image">
</slot>
</machine>

9
Hay Roman, I cannot select all sets with word "japan" inside their description definition inside the DAT file...
Will you please help me?

Here's regex:
Code: [Select]
\b(japan)
Am I missing something?

That's the DAT: http://redump.org/datfile/dc/

10
Hey Roman!
What do you thin about adding a feature to exclude also real machines at start, when importing Profiles?

I mean, take at look at recent XML lists in M.A.M.E.
OK we all know there are two kind of XML you can export from M.A.M.E.:
Code: [Select]
mame -listsoftwareor
Code: [Select]
mame -listxml
Now, let's have a look inside the XML from mame -listxml, for example: Dreamcast (Japan, NTSC).
Code: [Select]
<machine name="dcjp" sourcefile="dccons.cpp">
<description>Dreamcast (Japan, NTSC)</description>
<year>1998</year>
<manufacturer>Sega</manufacturer>
<biosset name="101d" description="v1.01d (World)"/>
<biosset name="1022" description="v1.022 (World)"/>
<biosset name="101c" description="v1.01c (World)"/>
<biosset name="101dch" description="v1.01d (Chinese hack)"/>
<biosset name="1004" description="v1.004 (Japan)"/>
<rom name="mpr-21931.ic501" bios="101d" size="2097152" crc="89f2b1a1" sha1="8951d1bb219ab2ff8583033d2119c899cc81f18c" region="maincpu" offset="0"/>

# [...] truncating irrelevant output [...]

<slot name="ata:0">
<slotoption name="gdrom" devname="gdrom" default="yes"/>
</slot>
<slot name="ata:1">
</slot>
<softwarelist tag="cd_list" name="dc" status="original"/>
</machine>


What about excluding all machines which have the <softwarelist /> node Element??

 

11
Hey Roman!
Would you consider adding the copy option (instead of Move All To Folder) inside the Warnings window when Scanner founds valid CHDs (drag'n'drop)?
I'm working from a readonly backup filesystem as source, so I cannot move (or cut / paste) files!   ;)

Thanks, bye!

12
Hey!
I just discover today that there are dedicated DATs for CHDs-only (progettoSNAPS).
Now... I have a lots of scattered CHDs in various folders in my external HDDs.
I don't want to do manual work by checking CHDs and copy/paste in my main roms folders.

I tried using that CHD-DAT, but Rebuilder and also Scanner do nothing.
Rebuilder only shows me the list of vaild CHDs.
I'm using tha DAT ad a "roms" DAT, so my ROMPath is CHD destination and ADD-Paths have all my folders with various CHDs.

Can you please help me??

Thanks, bye!!  8)

13
Hi to all cmamep guys!!  8)

As in topic's title: I'd like to learn how to properly filter my sets in Scanner before going on with useless rebuilding.
What is the syntax to use? Where can I set desired filters?  :o

I'd like to filter my sets using node from DATs to exclude all  "driver status="preliminary"". I know, I'm aware of the "risks" of filtering sets with this, I am ok with that.

Also, please tell me if it's good to unset [MECHANICAL] from Scanner--->Systems, or should I take extra steps?

And also: could cmamep take advantage of catver.ini (from AntoPISA' progettoSNAPS) to help users filter their sets?


Many many thanks!!
Bye 8)



14
Hey Roman!
As in title: what are these options for...?

Do I need to change or care about them?
What changes if I set them to on? ... I tried, but I see no changes  :o


Thanks!

15
Hey Roman, congrats for you huge work with that nice piece of software which is cmamep... It's super!  8)
And also fits really nice in Linux via WINE!  ;)

As in title, I'd like to have a clarification by you, please be so kind!

I'm using Latest Nightly Build.
So... I found some CHDs have mismatch version for what I say in cmamep to check against to.
Some of them are v4 and some others are v5.
I tried and done some experiments... 'Cause I'd like to have all CHDs converted to v5!  ;D
If I change the version to v4 to v5 the SHA1 also changes, and cmamep found a wrong CHD entry (before conversion, that CHD was was recognized as correct).

Here's to you what happens:
Code: [Select]
ls *.chd | parallel chdman info -i {}               
chdman - MAME Compressed Hunks of Data (CHD) manager 0.218 (unknown)
Input file:   gdl-0012.chd
File Version: 4
Logical size: 1,344,333,888 bytes
Hunk Size:    9,792 bytes
Total Hunks:  137,289
Unit Size:    2,448 bytes
Total Units:  549,156
Compression:  zlib (Deflate)
CHD size:     110,731,452 bytes
Ratio:        8.2%
SHA1:         aae4c1321fdee37d5405c6cbe648e0596624ed13
Data SHA1:    6326b21cfdc04490eb0ba82bc15d2fbc1ac8fac8
[...]

chdman - MAME Compressed Hunks of Data (CHD) manager 0.218 (unknown)
Input file:   gdl-0012v50174.chd
File Version: 5
Logical size: 1,344,333,888 bytes
Hunk Size:    9,792 bytes
Total Hunks:  137,289
Unit Size:    2,448 bytes
Total Units:  549,156
Compression:  cdlz (CD LZMA), cdzl (CD Deflate), cdfl (CD FLAC)
CHD size:     66,551,507 bytes
Ratio:        5.0%
SHA1:         d2097461b5c6cffca5214a4fc7c685e5b620c156
Data SHA1:    6326b21cfdc04490eb0ba82bc15d2fbc1ac8fac8
[...]

chdman - MAME Compressed Hunks of Data (CHD) manager 0.218 (unknown)
Input file:   gdl-0012v50218.chd
File Version: 5
Logical size: 1,344,333,888 bytes
Hunk Size:    9,792 bytes
Total Hunks:  137,289
Unit Size:    2,448 bytes
Total Units:  549,156
Compression:  cdlz (CD LZMA), cdzl (CD Deflate), cdfl (CD FLAC)
CHD size:     66,551,507 bytes
Ratio:        5.0%
SHA1:         d2097461b5c6cffca5214a4fc7c685e5b620c156
Data SHA1:    6326b21cfdc04490eb0ba82bc15d2fbc1ac8fac8
[...]

Is this a normal behaviour? I mean, MAME uses only SHA1 in its xml list to check CHD's datas' correctness?
Or cmamep can also verify internal SHA1 (Data SHA1)?

I did a test with some settings in Scanner, with no luck  :'(



Thanks, bye!!

Pages: [1]

Page created in 0.138 seconds with 18 queries.

anything