Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
06808 Misc. Major Always 22 days ago 16 days ago
Tester wuemura View Status Public Platform MAME (Self-compiled)
Assigned To Resolution Unable to reproduce OS Linux (64-bit)
Status [?] Closed Driver cps3.cpp
Version 0.193 Fixed in Version Build 64-bit
Summary 06808: cps3boota: Case sensitive issue
Description Linux Specific!

mame -listxml
machine (
name cps3boota
description "CPS3 Multi-game bootleg for dead security cart (V5)"
year 1999
manufacturer "bootleg"
sourcefile cps3.cpp
cloneof cps3boot
romof cps3boot
rom ( name no-battery_bios_29f400_for_dead_security_cart.u2 size 524288 crc 0fd56fb3 sha1 5a8bffc07eb7da73cf4bca6718df72e471296bfd )
disk ( name unicd-cps3_for_custom_sh2_v5 sha1 50a5b2845d3dd3de3bce15c4f1b58500db80cabe )
)

cps3.cpp
DISK_IMAGE_READONLY( "UniCD-CPS3_for_custom_SH2_V5", 0, SHA1(50a5b2845d3dd3de3bce15c4f1b58500db80cabe) )

MAME listxml output the name in lowercase:
unicd-cps3_for_custom_sh2_v5.chd

But it return an error requesting a filename with a mix of lowercase and uppercase.
UniCD-CPS3_for_custom_SH2_V5.chd

Linux is case sensitive, I use ClrMamePro v4.0.33 over Windows to manage and rename the files.
Steps To Reproduce ./mame64 cps3boota
Additional Information This just happens in Linux
Flags
Regression Version
Affected Sets / Systems cps3boota
Attached Files
 
Relationships
There are no relationsihp linked to this issue.
Notes
1
User avatar
No.14616
AJR
Developer
16 days ago
edited on: 16 days ago
The -listxml output from MAME 0.193 for cps3boota includes the line:

<disk name="UniCD-CPS3_for_custom_SH2_V5" sha1="50a5b2845d3dd3de3bce15c4f1b58500db80cabe" region="scsi:1:cdrom" index="0" writable="no"/>

As you can see, MAME does not lowercase the names of disk image files, nor does it append the .chd extension. This is therefore almost certainly not a MAME bug; the way ClrMamePro processes the XML output might be faulty.

Alternatively, the problem might lie in whatever application the "XML" in the report was copied from, since that's definitely not raw XML. XML attributes are supposed to be case-sensitive, so why are they being converted to lowercase?