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 / Date/Time issue Nintendo DSi (Digital) CDN

« on: 07 March 2021, 20:29 »

Hi,

About these two ‘systems’ (DATs from Dat-O-Matic:

Nintendo - Nintendo DSi (Digital) (CDN) (CDN)
Nintendo - Nintendo DSi (Digital) (CDN) (CDNdec)


Examining the DATs I see it expects the date/time of the files inside the .zip to be between 2010 and 2012 aproximately….

But when I load the DAT and scan my collection with clrmamepro it reports a lot of time/date errors because it says the correct ones should be 1970-01-01 00:00:00

This is a file:

(see attachment)

This is what the DAT says:

<?xml version="1.0"?>
<!DOCTYPE datafile PUBLIC "-//Logiqx//DTD ROM Management Datafile//EN" http://www.logiqx.com/Dats/datafile.dtd>
<datafile>
             <header>
                           <name>Nintendo - Nintendo DSi (Digital) (CDN) (CDN)</name>
                           <description>Nintendo - Nintendo DSi (Digital) (CDN) (CDN)</description>
                           <version>20210217-055105</version>
                           <author>Hiccup and zedseven, Icyelut</author>
                           <homepage>No-Intro</homepage>
                           <url>http://www.no-intro.org</url>
             </header>
             <game name="10 Byou Sou (Japan)">
                           <description>10 Byou Sou (Japan)</description>
                           <rom name="titlePass.txt" size="8" crc="12EC7F82" md5="7D9AD0211D6493E8D55A4A75DE3F90A1" sha1="891A4AC3F0101A20236B7F3DBE519F0CD38413C4" status="verified"/>
                           <rom name="FFFFFFFE" size="0" crc="00000000" md5="D41D8CD98F00B204E9800998ECF8427E" sha1="DA39A3EE5E6B4B0D3255BFEF95601890AFD80709" status="verified" date="2010-04-06"/>
                           <rom name="tmd.0" size="2312" crc="85EE6011" md5="63F6D0E38D89055C2DB9A63C8C7CBCC0" sha1="44B03D20C330105E2562C9D5F9C09A34A41A6899" status="verified" date="2010-04-06" serial="000300044B4A554A"/>
                           <rom name="00000000" size="5332992" crc="A37D2952" md5="A45B846F7644A5F9FBF684DD07A33F33" sha1="72324CD81A68D3A3245848F8917AE131C0D2B8F9" status="verified" date="2010-04-06" serial="KJUJ,10SECRUN"/>
                           <rom name="FFFD0000" size="1060" crc="848F1E52" md5="5C490CACE022981C1C4B0E4DBA97C8E1" sha1="A2DAD37ACB882A745F37C77AE8861604D660CA2A" status="verified" date="2010-04-06"/>
                           <rom name="FFFD0001" size="1498" crc="07397E5A" md5="EA4ECDF5B627ADE14613CF4632A40DD0" sha1="052063417784E95F474EC1E9FE8CBD22902C60CF" status="verified" date="2010-04-06"/>
                           <rom name="FFFD0002" size="1443" crc="C6BAD356" md5="0F73446C75468721B55C2D1F19DB2AD0" sha1="9CC3767BFCC9670A41A25CC95E6043E4798F8660" status="verified" date="2010-04-06"/>
                           <rom name="FFFD0003" size="1721" crc="11F1481C" md5="F52F7882BC467BC27FB1A660C055D9F9" sha1="E9EB34B0018100B4082EDC661718DF81E496EB09" status="verified" date="2010-04-06"/>
                           <rom name="FFFD0004" size="4059" crc="C932E6A4" md5="CA9949C152514370998B35F727AD9F31" sha1="FF9DD22E646470B7A863EFBF4F1BD4CD128C6098" status="verified" date="2010-04-06"/>
                           <rom name="FFFD0005" size="2371" crc="8C23CA0A" md5="7BFFE5A9ECD7CA46332551DCAED07BEF" sha1="DA88099F62C5A477281A2FDEC1C514547B74F05D" status="verified" date="2010-04-06"/>
                           <rom name="FFFEFFFF" size="2312" crc="85EE6011" md5="63F6D0E38D89055C2DB9A63C8C7CBCC0" sha1="44B03D20C330105E2562C9D5F9C09A34A41A6899" status="verified" date="2010-04-06"/>
                           <rom name="titleKey.bin" size="16" crc="23E383DC" md5="8E63D778E79EB78780F5216DD566B4C9" sha1="7C3B58D9EA237B5488884760F359AFD70BB65006" status="verified"/>
             </game>
             


This is what clrmamepro reports when scanning:

10 Byou Sou (Japan) [folder: 10 Byou Sou (Japan) - size: 5mb]
wrong date/time: 00000000 [wrong: 2010-04-05 22:00:00] [right: 1970-01-01 00:00:00]
wrong date/time: FFFD0000 [wrong: 2010-04-05 22:00:00] [right: 1970-01-01 00:00:00]
wrong date/time: FFFD0001 [wrong: 2010-04-05 22:00:00] [right: 1970-01-01 00:00:00]
wrong date/time: FFFD0002 [wrong: 2010-04-05 22:00:00] [right: 1970-01-01 00:00:00]
wrong date/time: FFFD0003 [wrong: 2010-04-05 22:00:00] [right: 1970-01-01 00:00:00]
wrong date/time: FFFD0004 [wrong: 2010-04-05 22:00:00] [right: 1970-01-01 00:00:00]
wrong date/time: FFFD0005 [wrong: 2010-04-05 22:00:00] [right: 1970-01-01 00:00:00]
wrong date/time: FFFEFFFF [wrong: 2010-04-05 22:00:00] [right: 1970-01-01 00:00:00]
wrong date/time: FFFFFFFE [wrong: 2010-04-05 22:00:00] [right: 1970-01-01 00:00:00]
wrong date/time: tmd.0 [wrong: 2010-04-05 22:00:00] [right: 1970-01-01 00:00:00]



Do you know what could be happening?? Is it something related to the DAT?? Or to clrmamepro??

Thank you very much!!

Regards,

Javier

2

clrmame Discussion / ClrMamePro says 'wrong name' wrongly?

« on: 21 January 2021, 18:29 »

Hi Roman,

When using clrmame to check MAME 227 (dat obtained with clrmame from mame64.exe), it reports one file as wrongly named... but it seems that's it's a file that according to the set information, has to exist twice with different names. What could be happening?

See attached pic


Thank you!

3

clrmame Discussion / Skipped files while rebuilding and zip compression

« on: 31 May 2019, 19:29 »

Hi,

I have Clrmamepro 4.035 and .209 full set (merged). Only the .zips, without the chds.

I think split is better.... so pointed clrmamepro to the .209 binary and created a dat file (saying ‘no’ to software lists and then ‘ok to all’)

On the rebuilder option, selected as the source path the folder that contains all the zips of the merged roms, and as the destination path a new folder in other place.

I have two questions:

1.- On clrmamepro Settings->compression, there’s no ‘zip’ tab to select the compression level. (I think there is supposed to be a selector to select from 1 to 9) So what will the compression level that clrmamepro use when rebuilding?

2.- For example, now the rebuilding process is at 32% and says:
168244 matched
54500 created
2350 skipped

Why are there so many skipped things? I think that if I have a merged set, which is all files parent+clones on the same zip, and to convert it to split what clrmamepro does is create separate parent and clone sets, why it says it skipping things? Aren’t all the files of a merged full set useful for a split full set?

Thank you!

4

clrmame Discussion / Problem on CRC of darkhors

« on: 03 January 2010, 00:53 »

Hi,

i have got a problem on eeprom rom on darkhors
Dark Horse (bootleg of Jockey Club II) [folder: darkhors - parent: jclub2 - size: 6mb]

clrmame pro says its  missing
i have eeprom with crc:
45314fdb

and it says
missing rom: eeprom [size: 128] [CRC32: 1f434f66] [SHA1: e1bee11d83fb72aed9c312bdc794d8b9a6645534]

i cant find one with the correct crc

is it a problem of the dat? of clrmame? mine?
i made the dad with clrmamepro pointing to mameui32 version 136

thank you!!