#1 Burning Software

I got a "Burn data" error when using Startburn SDK.
Thanks for your help.

Drive: DVDRAM GSA-4167B HL-DT-ST (DL12)
Transport: SPTI
Disc Type: DVD-R
Burning Speed: 8.0x (11081 KB/sec)
Send OPC: Yes
Burning Mode: Track-At-Once

Device::CdvdBurnerGrabberCreate: StarBurn_CdvdBurnerGrabber_CreateEx() failed, exception 5, status 32, text 'StarBurn_ScsiTransportSPTI::CStarBurn_ScsiTransportSPTI(): DeviceIoControl( 0x4a4 ( STAROPEN_IOCTL_OPEN ), 0x222004, 0x02EDB460, 2060, 0x02EDB460, 2060, 0x02EDB454, 0x00000000 ) failed, status 32 ( 0x20 )'

You have sharing violation opening device (standard Windows error code of 32). Either make sure you don't have other apps using the same device when you do (running "alien" burner in the background, running VMware with ATAPI device mapping, StarWindLite to share ALL of the burners or *quite possible* you have a bug in your app and you just don't close device handle after enumeration in the other thread - I can bet it's this case!).

Or you can open device in non-exclusive mode (check the parameters to the CreateEx(...) call). But this one is NOT recommended as burning will not be reliable.

P.S. And make sure to send ALL the info from the log and not the quotation you THINK is the sort of the problem. It worked THIS time but it's kind of an exception

I did use the original code from Videoburner.But the problem is some of my PCs/burners can finish the burinning task successfully but some not and show a burn data error.So I do not think the reason was due to the device handle does not close properly.Thanks again.
Meanwhile,would you please let me know if the "open drive handle"parameter was in "FindDevices", because I have called "FindDevices" before burn data.Thanks.

Below please find the log information.

RefreshMediaSize(): TOC IsValid Yes, IsDVD Yes, NumberOfSessions: 1, NumberOfTracks: 1

RefreshMediaSize(): Track blank: Yes, NWA valid: Yes, free LBs 2298496, NWA 0, track number 1

Drive: DVDRAM GSA-4167B HL-DT-ST (DL12)
Disc Type: DVD-R
Burning Speed: 8.0x (11081 KB/sec)
Send OPC: Yes
Burning Mode: Track-At-Once
Started
CDevice::CdvdBurnerGrabberCreate: StarBurn_CdvdBurnerGrabber_CreateEx() failed, exception 5, status 32, text 'StarBurn_ScsiTransportSPTI::CStarBurn_ScsiTransportSPTI(): DeviceIoControl( 0x4a4 ( STAROPEN_IOCTL_OPEN ), 0x222004, 0x02EDB460, 2060, 0x02EDB460, 2060, 0x02EDB454, 0x00000000 ) failed, status 32 ( 0x20 )'

Started Error!

1) The burning even did not started as you've failed to open the device. In the other words - you cannot crash the car as you have NO car yet Now let's try to find out what's happened.

2) To help you I need full StarBurn log to trace the command execution history. What you're sending me is NOT StarBurn debug log, it's only the text from the UI controls. Enough to find out what the problem really is but not enogh to tell why it happened this way. Please check the FAQ on how to generate debug log and send complete one to support@rocketdivision.com.

3) Yes. Durning device lookup phase we do allocate device handles. So if you did not do "house cleaning" properly you may have device handle (CdvdBurnerGrabber object) unallocated preventing you from opening the same device later in exclusive mode.

One more question,may I?Thanks.
Would you please kindly let me konw to brun dvd in non-exclusive mode ?

For ASPI and SPTI (Create(...) and CreateEx(...)) if you don't have StarOpen (non-Admin user management) driver installed access will be always Non-Exclusive. If you do have StarOpen installed it depends on the "Exclusive" key settings (see StarOpen.reg for more details). For SPTD there's a dedicated parameter in CreateExEx(...) call called "IsExclusiveAccess". As VideoBurner you've used as a skeleton can work in ANY listed mode I don't really have a clue about the one you've actually used.

P.S. On your place I'd issue RDS team with a log and let them do the rest of the things.

Hi again,
I encountered a createExEx error:

CDevice::CdvdBurnerGrabberCreate: StarBurn_CdvdBurnerGrabber_CreateExEx() failed, exception 5, status 5, text 'CStarBurn_ScsiTransportSPTD::CStarBurn_ScsiTransportSPTD(): SptdUserGetPlatformInfo( 0x00000000, 0x0357B664, 0x0357B644, 0x00000000 ) failed, status 5 ( 0x5 )

Thanks for your prompt reply.

SPTD layer is not installed OR you've used static linking against StarBurn and did not sign executable to work with the SPTD (only dynamic linking for CreateExEx is supported so far, docs are fixed).

I think burn data by using non-exclusive mode is the solution of the matter of "CdvdBurnerGrabberCreate: StarBurn_CdvdBurnerGrabber_CreateEx() failed"

If the problem was regarding to SPTD,how can I solve it?But maybe SPTD was not the root cause because I have tried burn other file before and all successfully.
I am using dynamic link StarBurn.dll
Thanks again.

It's not a solution. It's "begging for troubles" (c) ... B/c it means you have other thread touching the same device at the same time. It will lead to unstable burning you'll blame us in Please send us complete log of the enumeration/burning process. Also I've asked you about other burning software co-installed on the same machine. Do you have any?

StarBurn CD/DVD/Blu-Ray/HD-DVD Burning, Grabbing and Mastering Toolkit for Windows 95/98/Me/NT/2000/XP/2003/Vista/Longhorn Version 7.2.20 ( 0x20070220 )
Copyright (c) Rocket Division Software 2001-2006. All rights reserved.

CStarBurn_ScsiTransportSPTI::CStarBurn_ScsiTransportSPTI(): StarOpen driver version 0x20070220

< reset of the incomplete log was deleted by Anton >

Sorry I have no idea what you've really wanted to tell me posting truncated log and no comments at all. See this:

viewtopic.php?t=741

Initially what I can see you've ignored the comments and allocating burner object with the smallest amount of cache. It will work for reading but it will not work for writing.

Got the log from you, thank you! From the log it's quite clear you do handle device object from lookup procedure. Is it possible to get your application binary (or probably source) as it's the fast way to point to you where it happens? Or we can dump thread ID during device allocation/de-allocation you could match in your app. How would you prefer to proceed?
Thanks!