#1 Burning Software

Hi

I can't find how to determine whether the drive supports R and W of BluRay Disks as the relevant functions don't reference it:

StarBurn_CdvdBurnerGrabber_GetSupportedMediaFormats[ExEx]

B/c you're looking at the wrong place. These API calls are kept for backward compatibility only. Use

StarBurn_CdvdBurnerGrabber_GetAdvancedSupportedMediaFormats(...)

API call instead of them.

Thanks Anton.

However you really need to keep your sample code in sync with your releases. Most customers like myself will base their code on your samples, assuming that the latter to be the model of best practice.

At the very least comment the sample code with the disclaimer that "xyz" is no longer the recommended method and "uvy" should be used instead.

You're right! But it's 7.xx version, we're in sync with V10 release.

Um OK, when will v10 be released?

What happened to versions 8 and 9

P.S. spelling error on:

http://www.rocketdivision.com/starburn.html

"Sysytem"

1) Very soon.

2) The same what happened to Solaris versions f.e. 4 and 5.

3) Fixed, thanks a lot for pointing!

2) Sun didn't skip any versions, they only changed their external product names (marketing):

SunOS 4.x - Solaris 1.x
SunOS 5.0 - Solaris 2.0
SunOS 5.1 - Solaris 2.1
SunOS 5.2 - Solaris 2.2
SunOS 5.3 - Solaris 2.3
SunOS 5.4 - Solaris 2.4
SunOS 5.5 - Solaris 2.5
SunOS 5.6 - Solaris 2.6
SunOS 5.7 - Solaris 7
SunOS 5.8 - Solaris 8
SunOS 5.9 - Solaris 9
SunOS 5.10 - Solaris 10

Sun switched from a BSD kernel to a System V kernel when they switched from SunOS 4 to SunOS 5. Then they started to use the new Solaris marketing name for their OS. They left out the major 2. version when they switch from 2.6 to 7. Confusing...? Yes, I agree, but they never really skipped an (internal) version.

Off-topic? Yes, sorry ...

The current version of StarBurn SDK is 7.2.20, which I thought meant 20/02/2007. Does that mean we have to wait until 2010 for version 10?

Regards,
Marcel

OK, OK... We've also glued two codebases and that's why decided to drop sequential numbering as more then 50% of the code hand been changed. We're not syncing versions with build dates as well.

V10 has been published Gold and we're just completing some final checks. That's the story...

To support your argument, Netscape went directly from v4 to v6. Though I trust SB10 will be significantly less buggy than Netscape v6 was

To those that think v10 has taken a long time to deliver:

http://duke.a-13.net/

The software gets more and more complicated and it's really difficult to gather all the things together.........................

And will version 10 available for free for us?

If you've subscribed less then a year ago - YES.

Thank you.

Nothing for yet

really need to keep your sample code in sync with your releases. Most customers like myself will base their code on your samples, assuming that the latter to be the model of best practice.