CD-ROM ioctl support on MacOS?

Hi,

what's the state of CD-ROM support on the Mac?
ntdll/cdrom.c contains quite a few #ifdef apple.

I'm asking because the mcicda currently uses these ioctl:
1. READ_RAW
2. READ_TOC
3. READ_Q -> POSITION

MCICDA could be changed to avoid the third one entirely
 -- when using the dsound output. Would that 
be enough to use mcicda on MacOS to play music?

Thanks for your help,
 Jörg Höhle

[Charles Davis]

On 8/5/10 9:16 AM, [e-mail] wrote:
> Hi,
>
> what's the state of CD-ROM support on the Mac?
> ntdll/cdrom.c contains quite a few #ifdef apple.

I was the last one to hack on that, so I'll bite.
> I'm asking because the mcicda currently uses these ioctl:
> - READ_RAW

That's implemented. I implemented it myself in
6368dbbd5939bf71b04f3c441dd3af8cd027b7fb.
> - READ_TOC

AJ implemented that in e6ce0da2f99cc8c249a453489b9b199bec1fe435.
> - READ_Q -> POSITION

That might never be implemented. Like I said earlier, the
IOCDAudioControl user client was removed in Mac OS X 10.4. I might be
able to implement this using a direct SCSI call, though. Come to think
of it, I might also be able to extend my experimental BSD client to
support this.
> MCICDA could be changed to avoid the third one entirely
>  -- when using the dsound output. Would that 
> be enough to use mcicda on MacOS to play music?

That might work.
> Thanks for your help,

No problem.

Chip

Hi,

Charles Davis wrote:
> > - READ_RAW
>
> That's implemented. I implemented it myself in
> 6368dbbd5939bf71b04f3c441dd3af8cd027b7fb.

It doesn't work here ("early 2009" mini with 10.5.8) as I mention in
http://bugs.winehq.org/show_bug.cgi?id=20323#c4
Perhaps it can read data tracks only, no audio?

Regards,
 Jörg Höhle

DVD/CD-ROM recognized as network drive/floppy disk on MacOS

Hi,

perhaps I should turn this into a bug report, but I'm hoping for a quick fix.

Using wine-1.3.21 on Mac OS X 10.5.8, I observed that winecfg reported
a data DVD as "network drive" and a data CD-ROM as "floppy disk".  An
audio CD was correctly reported.

This is probably caused by the recent changes in volume management?

Thanks for your help,
    Jörg Höhle