Here’s what we need to do: We develop a Windows application that has lots of legacy file writing code, including a third-party dBase-like library that we have no control over. We still want to write data and a viewer onto CDs and DVDs. These should be readable under a W2K or XP PC without any particular software installations.
Until now, we used Roxio’s DirectCD, which makes the drive letter transparently “writeable”, so we didn’t have to change our legacy code. This works quite well, but what we don’t like about this approach is that the user has to deal with both the DirectCD GUI and our application. We would like to be able to control the functionality needed with our application through an API.
Here’s what I have evaluated so far (please correct me on any points that I have gotten wrong!):[ul]
[li]What we want is probably “Packet Writing”, right? Since other writing modes demand the directory/file structure to be set fixed at the start of burning.
[/li][li]XP’s native Image Mastering API only supports CD, and it buffers all files on disk, which we don’t like.
[/li][li]Roxio’s DirectCD again doesn’t offer an API, and it doesn’t support DVD.
[/li][li]Neither Nero’s InCD nor Roxio’s Drag-to-Disc offers an API
[/li][li]NeroAPI’s Packet Writing offers only raw sector writing support, not the transparent file system support we need.
[/li][li]As a fallback strategy, we could make our application write a part of the data onto a temp disk file at a time, and then call a burning API successively. What is very hard for us to do, though, is give the entire directory/file structure at the start – that’s why the other (non-packet) NeroAPIs are hardly an option for us, either.
Are there other APIs out there that might fulfill our requirement? Have I overlooked something?
If you need further information, I’d be only too happy to give them. There must be solution …