#1 Burning Software

Hello,

There are many questions, I kindly ask you to answer all of them - I checked help files and samples, there are only those questions that I haven't understand yet. Thanks in advance.

I want to burn a single file on a disc. What should I check before burning? I suppose, that (in the order of checking):

1. Test unit ready (Maybe, it checks some following options itself?)
2. Something is inserted
3. Track-At-Once is supported
4. Inserted media is writeable (CD-R, but not CD for example)
5. Inserted media supported by device
6. ((Disc is blank or not finalized yet) or it's eraseable) and (there is enough space for my file).

Then, when I want to erase media and then burn the file, what should I do?

1. Lock drive
2. Set speed
3. Call StarBurn_CdvdBurnerGrabber_Blank
4. Unlock, Eject, Load and Lock again (is it really necessary?)
5. Create file tree
6. Get BUP, then enable it if supported
7. Set speed again
8. Import track
9. Add file to the tree (will it replace old file with the same name?)
10. Build tree (should I start from 0 or from NWA?)
11. Send OPC
12. Call StarBurn_CdvdBurnerGrabber_TrackAtOnceFromFile
13. Close session (do I actually need it if I want to allow disc modification in the next time?)
14. StopPlayScan
15. Verify (should I check the whole tree or only one burned file?)
16. Unlock drive
17. Destroy tree

P.S. And file of what maximum size I can burn on the single disc? All that StarBurn_CdvdBurnerGrabber_GetDiscFreeSpace returns?

P.P.S. Should I implement support of any other modes that TAO? Are there cases when TAO is not supported but some different mode is supported?

P.P.P.S. What is StarBurn_CdvdBurnerGrabber_BluRayFormat function? Blank function doesn't support BluRay and HDDVD?

We've spent quite a time doing simple console and and fancy GUI samples NOT to answer questions like this So for burning use TrackAtOnceFromTree sample and for erase use Blank sample. And cut-n-paste their code as a skeleton for your application.

With UDF file size is unlimited (well, nearly), with ISO9660/Joliet it's 2GB (actually 4GB but some OSes may treat 32-bit as signed so please stick with <2GB).

DAO is in need for overburning (nearly obsolete) and CD-Text recording. So if you don't play with them - don't implement DAO.

It's for Blu-Ray format (surprise) in the way you can play with re-map area size (and whole capacity). So you can use smaller spare area size (larger disc capacity) or larger spare area size (smaller capacity but more sessions). BD-RE discs come formatted in not always perfect (for you) way. You can fix this

Blank is supported for BD-RE and HD DVDs of course.

1. Is it necessary to Unlock, Eject, Load and Lock again between erasing and burning?
2. Will StarBurn_ISO9660JolietFileTree_Add replace the old file with the same name?
3. When I build the tree, should I start from 0 or from NWA?
4. Do I need it to close session if I want to allow disc modification in the next time?
5. What TestUnitReady actually checks (from my list)?
6. Is my list full or there any other points that I should check?
7. And is it a right erase-and-burn sequence.

I really carefully learned your samples, so you shouldn't think that I ask you only because of my lazy, I just don't want to miss something.

And what about Session-At-Once?

The same as DAO.

1) Yes. If you don't want your user to interrupt the process and do want the drive to refresh it's state.

2) Read help about collisions and check samples on how to detect and handle collisions.

3) Get NWA from the disc. Zero NWA is for blank discs ONLY.

4) No close session = no recorded disc.

5) Can you work with the drive + disc or not.

6) ...

7) No. Break burning into erase and actual burns. These are very different sequences so it's a bad idea to build spaghetti code.

OK, thanks.

You're welcomed

Is there any sample where I can learn how to create UDF-formatted data disc?

And are there really serious problems with UDF support on various systems?

1) UDFBuildImageEx is your friend

2) Yes. Try reading Blu-Ray movie content on Windows 2000 or Windows XP. For example...