07832: twinklea: Twinkle (set 2) needs roms renamed.

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
07832	Misc.	Minor	Always	Dec 31, 2020, 19:39	Dec 31, 2020, 19:54

Tester	chaneman	View Status	Public	Platform	MAME (Official Binary)
Assigned To		Resolution	No change required	OS	Windows Vista/7/8 (64-bit)
Status [?]	Closed			Driver	kaneko/snowbros.cpp
Version	0.227	Fixed in Version		Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	07832: twinklea: Twinkle (set 2) needs roms renamed.
Description	Twinkle (set 2) roms "uh12.bin" and "ui12.bin" need to be renamed in order to load game properly and distinguish it from the parent set. Driver is loading same rom names as parent set and expecting a different checksum.
Steps To Reproduce	Load and run game.
Additional Information
Github Commit

Flags
Regression Version
Affected Sets / Systems	twinklea

Attached Files

No.18305 Tafoid Administrator Dec 31, 2020, 19:54	There is no issue here Clones can have the same labels with different hashes from a parent - there are literally hundreds of examples in MAME already of this. MAMEDEV has attempted to signify these with a comment in source "// sldh" (same label different hash). Tools such as CMPRO can easily handle this when scanning and will rename whatever label if that needed. MAME internally doesn't care so much about them as they use all metrics (label/hashes/size) to determine what to load. At one time there was some confusion as to keeping these the same label and most all were renamed to avoid confusion such as this. However, for the sake of accuracy, we needed to keep to exactly what the dumped rom chip had for a label even if that meant they are not 100% the same. Closing.

No.18305

Tafoid

Administrator

Dec 31, 2020, 19:54

There is no issue here

Clones can have the same labels with different hashes from a parent - there are literally hundreds of examples in MAME already of this. MAMEDEV has attempted to signify these with a comment in source "// sldh" (same label different hash). Tools such as CMPRO can easily handle this when scanning and will rename whatever label if that needed. MAME internally doesn't care so much about them as they use all metrics (label/hashes/size) to determine what to load.

At one time there was some confusion as to keeping these the same label and most all were renamed to avoid confusion such as this. However, for the sake of accuracy, we needed to keep to exactly what the dumped rom chip had for a label even if that meant they are not 100% the same.

Closing.