Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

Perfect, big thank you.

Now it can be explained.
Thanks Roman!

With kind regards, NU.

No everything is fine and of course the crc32 is checked.
But such old MAME versions used bitwise inverted crc32 values to mark a bad dump in the datfile.
So your file is actually ok (but  a marked bad dump):

4fafa1e7 = BOOLEAN-NOT b0505e18

There's an option in the profiler options to enable the inverted crc32 mode, then the rebuilder also rebuilds it.


Yeah...there are some weird things in 20 year old MAME versions....that's one of the reason why people should stick with the current one

Hi Roman,

I ran into something I can't explain with the scanner, while scanning a set with an old crc32 only datfile.
Attached a datfile and zip of the MAME 0.36 turbotag set.
The ttprog1.bin in the zipfile has crc b0505e18.
The datfile shows crc 4fafa1e7 for ttprog1.bin.
The size of the file is as it should be, 8192 bytes.

The rebuilder doesn't pick up the ttprog1.bin file, as expected.
However, if you scan the zipfile with ttprog1.bin included, it won't mark it as unneeded.
If you add an empty ttprog1.bin file to the zipfile, it will be marked as unneeded by size.

Why is this file not recognized by the scanner as unneeded by crc?

With kind regards, NU.

OK. Thank you!

That zip is packed with the deflate64 compression method which is not supported. You can unpack it with e.g. 7z/winrar and pack it again as a zip and it will work.

When I try to add this zip to the profiler, it fails. WinRAR testing and unzipping is OK.

File name is fix_Sega - Mega Drive - MSU-MD (v2021-04-04).zip

@mjmattson3170
Take from mame source:

Author:         hap <happppp@users.noreply.github.com>
Author date:   7 months ago (23.8.2020 г. 17:33:40)
Commit date:   7 months ago (23.8.2020 г. 17:33:53)
Commit hash:   8cde9585e685bd08125d083102d51b3e84ec1b51
Child:         113de382
Parent:         5ed80089

odyssey2: rename hash files to videopac and videopacp

Think u must reorganization your SL
Good luck

It was not a clean install, so I am sure that is what caused that confusion.  I was trying to figure out what the deal was in the last few builds and finally decided to get to the bottom of it.  Thank you for the information.  It cleared it up.

There is only the following in MAME .230: videopac.xml <softwarelist name="videopac" description="Philips Videopac / Odyssey 2 cartridges">

Maybe MAMEDevs used a different file before with a different description and you only unpacked the latest MAME over your existing installation (no clean install).