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 / Dates older than 1980 = Invalid?

« on: 22 April 2019, 01:56 »

Hello, long time no speak.  I was adapting a dat for DOS era content, and many files are dated 1979-12-03, functionally as placeholders for unknown values.  This is posing a problem for use with clrmamepro as I've found that all dates prior to 1980-01-01 00:00:00 are treated as illegal values.  Was this set arbitrarily? Can it be set so something more accommodating, such as 1900?  The first hard drives were commercially produced even before the UNIX epoch (1970-01-01), and floppy disks were becoming normal during the mid to late 1970s.

Alternatively, is there a way to store a file WITHOUT a date set, or is that a violation of the zip standard?

Example:
game (
   name "Las Vegas Blackjack v1.05 (1982)(Quala Software) [Strategy, Cards]"
   rom ( name "AUTOEXEC.BAT" size 24 date "1979-12-03 00:04:00" crc 282A252C )
   rom ( name "BASICA.COM" size 16256 date "1981-08-04 00:00:00" crc 1DF9FAD6 )
   rom ( name "BLACKJAK.BAS" size 23296 date "1982-07-27 00:06:26" crc 9D3CA6FC )
   rom ( name "COMMAND.COM" size 3231 date "1981-08-04 00:00:00" crc 5016C475 )
   rom ( name "DATE.COM" size 252 date "1981-08-04 00:00:00" crc EEF91299 )
)

Thank you,
Z

2

clrmame Discussion / [BUG] RAR volume open lockup

« on: 15 December 2013, 07:40 »

The newest version of cmpro x64 (4.012) contains an updated UnRar64.dll (5.0), which introduces a lockup/freeze scenario that pegs the CPU at max until cmpro is terminated.  This is caused by attempting to read, least from the Rebuilder, a multipart RAR that itself has been zipped or RAR'd. Example here. With the previous DLL version (4.20) it failed gracefully with the reported message: foo.part1_12345.rar got volume open error. Using the new DLL with an older version of cmpro does the same lockup, while using the old DLL with the new version of cmpro returns the error message.

3

clrmame Discussion / Rebuild log (+ typo?)

« on: 22 July 2013, 12:42 »

I have had need for more extensive rebuild logging. '[EXISTS]' hardly helps when I am trying to find what certain files were matched after rebuild+removal. I also see '[SKIPPED Reason: ]' which appears incomplete.  Existence is probably determined easily based on the loaded cache, but it would be useful to not have to manually calculate the hash of the file and search that in the datfile for the associated filename.

Secondarily, I wonder why the .cmp config entry "bRebuilder_ShowStats" has a leading b.

4

clrmame Discussion / Detector rule: size

« on: 26 January 2013, 07:07 »

I was attempting to write my first header skipper containing offset rules for files less than a specific filesize, and became frustrated that it was seemingly ignoring them, when it dawned on me that the skipper must be depending on the dat for size info rather than the physical files. The dat does not contain size info, so I must find another method to determine if a file is under a tested size. Is this possible?

There is no particular series of bytes marking the end of 'real data' in these files, and EOF can slide 100s of bytes between files.  I considered forcing an illegal seek to default to EOF, but this also resets start_offset to 0.

I'll be the first to admit that I am less than spry with logic, so I hope you can show me the light with this. Or else confirm there is a limitation that I needn't feel stupid for anymore. 

5

clrmame Discussion / 7z rebuild with @ in filename

« on: 17 January 2013, 13:21 »

Dat entry:
<game name="@rkanoid Beta V0.01 by Ducker (PD)">
<rom name="@rkanoid Beta V0.01 by Ducker (PD).GBA" crc="<snip>" sha1="<snip>"/>
</game>

7zr.exe: a -y -r -ms=off -mx0 %1 %2


Same result with 7z.exe 9.30. Compress as .zip and .rar work OK. (Rar.exe: a -y -r -ibck -m5 -s- %1 %2)

a -y -r -ms=off -mx0 "%~1" %2 = Same error.
Rebuild log: B:\scan\@rkanoid Beta V0.01 by Ducker (PD).gba [SKIPPED Reason: Create Destination Problem]

a -y -r -ms=off -mx0 "%~1" "%~2" = the rom is counted as being created in post-rebuild statistics but the archive isn't found anywhere... apparently built into the nether.
B:\scan\@rkanoid Beta V0.01 by Ducker (PD).gba
  -> @rkanoid Beta V0.01 by Ducker (PD).7z\@rkanoid Beta V0.01 by Ducker (PD).GBA

a -y -r -ms=off -mx0 %1 "%~2" = archive is created in destination, but no entry added. Only 32bytes of 7z header is written.

a -y -r -ms=off -mx0 "%1" "%~2" = 32byte archive, but filename is truncated after space. (@rkanoid.7z)

a -y -r -ms=off -mx0 %~1 %~2 = counted as created in stats, but no archive in destination.

Changed Dat entry:
<game name="@rkanoid Beta V0.01 by Ducker (PD)">
<rom name="Arkanoid Beta V0.01 by Ducker (PD).GBA"
...Rebuild works fine with a -y -r -ms=off -mx0 %1 %2

Changed Dat entry:
<game name="@rkanoid Beta V0.01 by Ducker (PD)">
<rom name="&#64;rkanoid Beta V0.01 by Ducker (PD).GBA"
...Same error again.

"@" is used in MSBatch to mute output, but only if at the start of a line.  It is echo-able.  Is there a commandline that can make 7z behave with this character?  I cannot find references to this problem elsewhere.

6

clrmame Discussion / [bug] version[64].ini check problem

« on: 07 January 2012, 03:33 »

When the following conditions existed:
• cmpro.exe is absent
• cmpro64.exe is present
• version.ini is present, 4.0010
• version64.ini is present, 4.0020

...An update check in cmpro64.exe (4.02) claimed that my version is outdated (4.01). I was able to clear this incorrect message by removing version.ini, leaving only version64.ini. I think there is a minor oversight somewhere in the state analysis code.

Thanks for the tools, and HNY to all.