What advantage is there to CDA recognizing your drive?

MLG wrote on 11/10/2001, 9:00 PM

So if CDA doesn't recognize your drive and you use the MMC successfully, what's the difference? Speed or coaster protection of some sort? So what if CDA doesn't recognize your drive if you can still use it with the MMC driver?

Thanks,
MLG

Comments

BrentA wrote on 11/11/2001, 2:40 PM

The benefit I got in modifying the DLL to allow CDA to recognize my current drive (TDK VeloCD 16) are:

1) Easier to switch between my other CDA supported drives (Yamaha 4260, Ultraplex 32) w/o having to re-input MMC settings for the VeloCD each time I want to use it.

2) I can rip from the VeloCD from CD Architect. I couldn't when I was just using the MMC route.

Features I am still missing:

a) Ability to choose burn speed...it always is "max"
b) Incorrect "time remaining" display during burn process.

Other than that, burns are 100% successful so far.

philokeefe wrote on 11/11/2001, 9:36 PM

So can you tell us EXACTLY (step by step for us non-computer programmers) how you made the changes using that Hex editor? I opened up one of the files in a hex editor and it didn't say anything I could see regarding specific drive info.

Thanks

BrentA wrote on 11/11/2001, 11:09 PM

The drive stuff is about halfway through the file. Check out these threads for more info:

http://www.sonicfoundry.com/forums/ShowMessage.asp?ForumID=5&MessageID=75507
http://www.sonicfoundry.com/forums/ShowMessage.asp?ForumID=5&MessageID=78601