1
clrmame Discussion / Problems with the latest TOSEC release
« on: 26 August 2014, 04:54 »
Roman,
With the last two TOSEC releases, I have noticed a rebuilder problem. Know-good files that were previously identified correctly were no longer being identified during the rebuild process and were unhappily skipped. The notes indicated that new SHA1s have been added to many DATs recently. Disabling MD5 and SHA1, leaving only CRC32, seems to solve the problem. A good example is the "Apple II - Compilations - Games - [DO] (TOSEC-v2013-10-29).dat" file. The following entry no longer recognizes the ROM when SHA1 and MD5 are enabled:
game (
name "ABM (1980)(Muse) & Invasion Force (19xx)(Gordon Lurie) & Missile Defense (1981)(On-Line Systems) & Norad (19xx)(-) & Planet Protector (19xx)(-)[cr] & Rocket Command (1980)(Bozo NYC)"
description "ABM (1980)(Muse) & Invasion Force (19xx)(Gordon Lurie) & Missile Defense (1981)(On-Line Systems) & Norad (19xx)(-) & Planet Protector (19xx)(-)[cr] & Rocket Command (1980)(Bozo NYC)"
rom ( name "ABM (1980)(Muse) & Invasion Force (19xx)(Gordon Lurie) & Missile Defense (1981)(On-Line Systems) & Norad (19xx)(-) & Planet Protector (19xx)(-)[cr] & Rocket Command (1980)(Bozo NYC).do" size 143360 crc f0760736 md5 cbc6dd038436029aaaab86e02be0a46a sha1 aa97ac5aac86d2fa614434af3377072926a10e1c )
)
Again, this is a rebuilder issue only. If the image is manually copied to the correct directory, then the image is correctly identified and recorded by the scanner. Do we have a possible line length issue in the parser?
Thanks,
Marc Sandusky
With the last two TOSEC releases, I have noticed a rebuilder problem. Know-good files that were previously identified correctly were no longer being identified during the rebuild process and were unhappily skipped. The notes indicated that new SHA1s have been added to many DATs recently. Disabling MD5 and SHA1, leaving only CRC32, seems to solve the problem. A good example is the "Apple II - Compilations - Games - [DO] (TOSEC-v2013-10-29).dat" file. The following entry no longer recognizes the ROM when SHA1 and MD5 are enabled:
game (
name "ABM (1980)(Muse) & Invasion Force (19xx)(Gordon Lurie) & Missile Defense (1981)(On-Line Systems) & Norad (19xx)(-) & Planet Protector (19xx)(-)[cr] & Rocket Command (1980)(Bozo NYC)"
description "ABM (1980)(Muse) & Invasion Force (19xx)(Gordon Lurie) & Missile Defense (1981)(On-Line Systems) & Norad (19xx)(-) & Planet Protector (19xx)(-)[cr] & Rocket Command (1980)(Bozo NYC)"
rom ( name "ABM (1980)(Muse) & Invasion Force (19xx)(Gordon Lurie) & Missile Defense (1981)(On-Line Systems) & Norad (19xx)(-) & Planet Protector (19xx)(-)[cr] & Rocket Command (1980)(Bozo NYC).do" size 143360 crc f0760736 md5 cbc6dd038436029aaaab86e02be0a46a sha1 aa97ac5aac86d2fa614434af3377072926a10e1c )
)
Again, this is a rebuilder issue only. If the image is manually copied to the correct directory, then the image is correctly identified and recorded by the scanner. Do we have a possible line length issue in the parser?
Thanks,
Marc Sandusky