#1 Burning Software

I am using StarBurnX Version 10.0.00 ( Build 2008-03-3).

I am using the DataBurner class for writing data onto the CD. I set the property to true while burning. But after setting this to false after burning, the drive cannot be ejected. Also, in the .NET sample after completion of burn, the drive doesn't unlock. Even after closing the sample application, the drive is not actually unlocked.

Is there something else I need to do to get the drive tray to be allowed to open?

There was a bug in StarBurnX wrapper fixed in V10. Just update to the official release.

Please provide a link to the official release.

thank you

Get into download section and grab official V10 release.

Hello Support,

I) Locking tray process works fine while Burning in
1) DataBurner
2) ImageBurner

but this process fails in DiscEraser class. If I am pressing drive eject button then drive gets ejected. Even it should give me error in this erasing process. But no error is given.
If the same lock mechanism like DataBurner will be done in DiscEraser class then it will be great for users like us.

II) Suggestion: DataGrabber class is not having LockTray property if this class will also have the locking capability then accidental eject button press and followed by DataGrabbing aborting will handled automatically.
Otherwise for Dual Layer discs after completing 75% grabbing process in 1 hour if accidental eject will be very bad. User can abort this process as we are already having Cancel Button on burn form.

Thank you.

Hello,

Yes, You are right .... already fixed .... thanx!!

Regards,

Dmitry

Hello Support,

In the current build I was checking for the locking mechanism in DiscEraser and Grabber classes, it is not included in this pre-release dll version.

Thank you.

Hello,

Hmm ... at least DiscEraser should work ... so ... we will make new build today.

Thanx,

Dmitry

Hello Support,
Thank you for reply.

I would like to remind you that I am a StrBurnX user. So please update StarburnX and will you please give me the change log.
Thank you.

What's "change log"?

Hello Sir,

By "change log" I mean, help for newly added functionality how to use these and description for functions and parameters only.

Oh, OK I see now

Hello Support,

As per my request in various posts,
Locking mechanism for DataBurner, ImageBurner, Grabber works excellently.
Thank you Sir.

But, I was checking drive.lockTray() method as I want to lock the drive until I am doing some validations on the drive.
I think it is not locking the drive will you please kindly check that.
I want to use that because while creating image I am checking whether inserted disc is blank or not, for that I am using drive.DiscInfo after using this drive tray is automatically unlocked and accidently drive was ejected and as I gave call to grabDisc nothing happened further.
Is the problem clear to you?
Thank you in advance.

If you're not using SPTD SCSI transport in exclusive mode - drive cannot be locked permanently... Windows unlocks it in the device update polling thread.

Hello Sir,

Got it.
So by using StarBurnX how to use SPTD SCSI transport in exclusive mode?
Like I mentioned earlier also, Drive locking works but until I am not calling Drive.DiscInfo(). So though windows might be unlocking the drive during polling. But as it works until I am not calling Drive.State or any information related to drive. I guess something else must be the problem.

Will you please kindly look into the problem? Thank you.