http://bugs.winehq.org/show_bug.cgi?id=20555
Summary: inconsistent handling of Audio-CDs Product: Wine Version: 1.1.32 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll AssignedTo: wine-bugs@winehq.org ReportedBy: hoehle@users.sourceforge.net
mci "open cdaudio" fails on pure Audio CDs, but the bug is not within MCI rather than in volume management or kernel32/ntdll (the MCI calls GetDriveTypeW).
Case A) When an audio-only CD is inserted before Wine is started, it creates the link dosdevices/d:: -> /dev/scd0 and in system.reg: [Software\Wine\Drives] "d:"="cdrom" mciSendString "open cdaudio" fails (MCIERR bad device) because GetDriveTypeW does not return a CDROM type. It would succeed on MS-Windows.
Wine creates the additional link d: -> /media/cdrom0 only when using a data-only CD-ROM or a mixed data + audio CD. In the latter case, mciSendString "open cdaudio" succeeds.
Conversely, an existing dosdevices/d:: link causes dosdevices/d: to be removed when Wine starts with a pure Audio-CD in the drive.
For consistency, you should have dosdevices/d:: point to your CD-ROM device, because of another bug in volume management: MCI "open e:\ type cdaudio" fails, while open d:\ succeeds even when E: is the CD-ROM!
Case B) Defining a CD-ROM myself (or like Wine did years ago?) using: dosdevices/d: -> /media/cdrom (which is in turn a link to /media/cdrom0 in Ubuntu) dosdevices/d:: does not exist. [Software\Wine\Drives] "d:"="cdrom" mciSendString "open cdaudio" succeeds. "play cdaudio" causes the drive to spin, but is sometimes returned with MCIERR_HARDWARE. AoE2 sends slightly different MCI commands and manages to play the CD. Even Crazy Machines successfully plays the audio CD with this setup.
Using Ubuntu Intrepid.