> I know. I have patches for all that. Did I not just write an email back
> to Roderick talking about the SCSITaskDevice?
Easy now. I didn't get your reply to Roderick until after Emmanuel's
response. Not only that, but with pretty large differences in time
zone, it's normal to have delayed resp
Emmanuel Maillard wrote:
> Hi,
>
> For peoples interested with cd-rom support on Mac OS X, i think that you
> need to investigated in IOKit,
> especially in SCSITaskDeviceInterface and MMCDeviceInterface.
>
> Emmanuel
I know. I have patches for all that. Did I not just write an email back
to Rode
joerg-cyril.hoe...@t-systems.com wrote:
> Chip,
>
> I had hoped that your patch would allow mcicda to work,
> cf. bug #20323, alas it is not so. Instead I get to see
>
> ERR("This version of Mac OS X does not support IOCDAudioControl"
> on Leopard.
>
> I googled slightly and found a message fro
Hi,
For peoples interested with cd-rom support on Mac OS X, i think that
you need to investigated in IOKit,
especially in SCSITaskDeviceInterface and MMCDeviceInterface.
Emmanuel
Le 14 oct. 2009 à 17:50, Roderick Colenbrander a écrit :
Hi,
I don't know much about the cd-rom stuff on osx
Hi,
I don't know much about the cd-rom stuff on osx but I expect there are
much more issues of which some are more severe than this (and the
solution might fix all the issues). I believe that on osx there is no
such thing as direct cd-rom access (anymore) and due to this I think
wine can't read au
Chip,
I had hoped that your patch would allow mcicda to work,
cf. bug #20323, alas it is not so. Instead I get to see
ERR("This version of Mac OS X does not support IOCDAudioControl"
on Leopard.
I googled slightly and found a message from 2004:
http://lists.apple.com/archives/darwin-drivers/200
On Mon, Oct 12, 2009 at 2:18 PM, Charles Davis wrote:
> Keith Muir wrote:
>> Charles Davis wrote:
>>> Damn it, I keep forgetting to reply all.
>>>
>>> Charles Davis wrote:
>>>
Vitaliy Margolen wrote:
> Charles Davis wrote:
>
>> Hi,
>>
>> My name is Charles Davis, but
Keith Muir wrote:
> Charles Davis wrote:
>> Damn it, I keep forgetting to reply all.
>>
>> Charles Davis wrote:
>>
>>> Vitaliy Margolen wrote:
>>>
Charles Davis wrote:
> Hi,
>
> My name is Charles Davis, but you all can call me "Chip".
>
> I'm new to Win
Damn it, I keep forgetting to reply all.
Charles Davis wrote:
> Vitaliy Margolen wrote:
>> Charles Davis wrote:
>>> Hi,
>>>
>>> My name is Charles Davis, but you all can call me "Chip".
>>>
>>> I'm new to Wine development, and frankly, I'm kinda scared because I've
>>> heard and read that getting
Oops, forgot to reply all.
Charles Davis wrote:
> James McKenzie wrote:
>> Charles Davis wrote:
>>> Hi,
>>>
>>> My name is Charles Davis, but you all can call me "Chip".
>>>
>>> I'm new to Wine development, and frankly, I'm kinda scared because I've
>>> heard and read that getting patches into Win
Charles Davis wrote:
> Hi,
>
> My name is Charles Davis, but you all can call me "Chip".
>
> I'm new to Wine development, and frankly, I'm kinda scared because I've
> heard and read that getting patches into Wine is very difficult. In
> fact, every time I got ready to send this first patch, I chi
Charles Davis wrote:
Hi,
My name is Charles Davis, but you all can call me "Chip".
I'm new to Wine development, and frankly, I'm kinda scared because I've
heard and read that getting patches into Wine is very difficult.
Lie. First of all avoid looking at native dumps, disasms, decompiled
outpu
Hi,
My name is Charles Davis, but you all can call me "Chip".
I'm new to Wine development, and frankly, I'm kinda scared because I've
heard and read that getting patches into Wine is very difficult. In
fact, every time I got ready to send this first patch, I chickened out
and couldn't do it. So,
13 matches
Mail list logo
