Re: DKIOCCDREADTOC returning BCD numbers?
Re: DKIOCCDREADTOC returning BCD numbers?
- Subject: Re: DKIOCCDREADTOC returning BCD numbers?
- From: Chris Sarcone <email@hidden>
- Date: Fri, 4 Jan 2008 17:18:42 -0800
| Stephen --
The only drives I'm aware of that do this are non-compliant Plextor drives and very old Apple SCSI CD-ROM drives (nicknamed "Hollywood" drives).
-- Chris On Jan 4, 2008, at 5:14 PM, Stephen F. Booth wrote: Hi Chris and Dave,
Thanks for the responses!
Have you tried setting the MSF bit to 1 by setting cd_read_toc.formatAsTime = 1?
if you set formatAsTime to 1, you get an error 5 (dsChkErr), so that's clearly not an option
I haven't had a chance to push out a debug build to the user experiencing the problem, so I'm not sure if this will help for him or not. If it makes a difference I will follow up to the list. i work around it by doing my darndest to detect BCD and correct it before i return from my call.
if i can't prove i've detected it, then i fall back on reading the ".TOC.plist" file, which sucks IMHO
if you need help or want code let me know
Have you been able to deduce any rhyme or reason to drives exhibiting this behavior? Of the two users reporting the problem to me, one was using a Plextor PX-712A inside an external enclosure (AMS VENUS DS-2512B2BK) and one was using a Plextor Premium.
FWIW, one of the users who reported this said he updated his drive's firmware (using a PC) and the problem went away.
Stephen
------------------ 6 Infinite Loop M/S 306-2MS Cupertino CA 95014 phone: (408) 974-4033 fax: (408) 862-7577 email: email@hidden |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden