Burn error using StarBurn SDK with Delphi 2007

Stojo303 · **Joined:** Sat Sep 15, 2007 3:54 pm **Posts:** 65

Hello,

A user of the application I develop has reported the following error: (Log follows)

Code:

52:51 Burning Audio CD
52:51      Adding audio file: C:\DOCUME~1\Tim\LOCALS~1\Temp\track000.wav
52:51      Adding audio file: C:\DOCUME~1\Tim\LOCALS~1\Temp\track001.wav
52:51 160 MBs of cache will be used during burn process
52:51 Testing unit ready
52:51 Track-At-Once: Yes, Session-At-Once: Yes, Disc-At-Once PQ: No, Disc-At-Once raw P-W: Yes
52:51 Getting BUP (Buffer Underrun Protection) support
52:51 BUP (Buffer Underrun Protection) Enabled: No, Supported: Yes
52:51 Enabling BUP (Buffer Underrun Protection)
52:51 Setting CD/DVD speeds
52:51 Getting current CD/DVD speeds
52:51 Current read speed 5645 KBps (5645 maximum)
52:51 Current write speed 706 KBps (1764 maximum)
52:51 Getting track information
52:51 Track Blank: Yes, NWA valid: Yes, free LBs 336073, track Â¹ 1
52:51 Getting disc information
52:51 Disc erasable: Yes, Disc status: 0x 0, Last session status: 0x 0, Disc type: 3
52:51 Sending OPC (Optimum Power Calibration)
52:53 Burning mode: Disc-At-Once PQ (from file)
52:53 Burning started
52:57 StarBurn_CdvdBurnerGrabber_DiscAtOncePQFromFile() failed, exception 8, status 0, text "CStarBurn_ScsiTransportSPTI::ExecuteCDB(): Command failed"

The users is having a system consisting of: Windows XP Pro sp2, 1.5GB memory on a Intel P4 2.8GHz.

Any idea how to solve this?

Thanks in advance,
Mikael

anton (staff) · **Posted:** Mon Oct 22, 2007 6:51 am

1) There's no way to solve this as it's drive firmware limitation. Drive reports you it cannot do DAO16 ("Disc-At-Once PQ: No") and you still do DAO16 with it ("StarBurn_CdvdBurnerGrabber_DiscAtOncePQFromFile()"). What for?

If you'd check the DAO samples we ship with the SDK you'd see we checking for either DAO16 or DAO96 supported and burn in appropriate mode. Please stick with the samples as they are your friends

2) It's a good idea to issue us with the StarBurn core log and no your application log. It worked OK for you this time but it does not in 99% of the cases...

Stojo303 wrote:

Hello,

A user of the application I develop has reported the following error: (Log follows)

Code:

52:51 Burning Audio CD
52:51      Adding audio file: C:\DOCUME~1\Tim\LOCALS~1\Temp\track000.wav
52:51      Adding audio file: C:\DOCUME~1\Tim\LOCALS~1\Temp\track001.wav
52:51 160 MBs of cache will be used during burn process
52:51 Testing unit ready
52:51 Track-At-Once: Yes, Session-At-Once: Yes, Disc-At-Once PQ: No, Disc-At-Once raw P-W: Yes
52:51 Getting BUP (Buffer Underrun Protection) support
52:51 BUP (Buffer Underrun Protection) Enabled: No, Supported: Yes
52:51 Enabling BUP (Buffer Underrun Protection)
52:51 Setting CD/DVD speeds
52:51 Getting current CD/DVD speeds
52:51 Current read speed 5645 KBps (5645 maximum)
52:51 Current write speed 706 KBps (1764 maximum)
52:51 Getting track information
52:51 Track Blank: Yes, NWA valid: Yes, free LBs 336073, track Â¹ 1
52:51 Getting disc information
52:51 Disc erasable: Yes, Disc status: 0x 0, Last session status: 0x 0, Disc type: 3
52:51 Sending OPC (Optimum Power Calibration)
52:53 Burning mode: Disc-At-Once PQ (from file)
52:53 Burning started
52:57 StarBurn_CdvdBurnerGrabber_DiscAtOncePQFromFile() failed, exception 8, status 0, text "CStarBurn_ScsiTransportSPTI::ExecuteCDB(): Command failed"

The users is having a system consisting of: Windows XP Pro sp2, 1.5GB memory on a Intel P4 2.8GHz.

Any idea how to solve this?

Thanks in advance,
Mikael

Stojo303 · **Joined:** Sat Sep 15, 2007 3:54 pm **Posts:** 65

Thanks for the reply Anton.

I must have mixed something up in the code since I'm allowing this :oops:

Quote:

It's a good idea to issue us with the StarBurn core log and no your application log.

This log is mostly taken from the (Delphi) samples, where is StarBurns own log stored?

Regards,
Mikael

anton (staff) · **Posted:** Mon Oct 22, 2007 7:09 am

Read the FAQ. There's a long section about this.

Stojo303 wrote:

Thanks for the reply Anton.

I must have mixed something up in the code since I'm allowing this :oops:

Quote:

It's a good idea to issue us with the StarBurn core log and no your application log.

This log is mostly taken from the (Delphi) samples, where is StarBurns own log stored?

Regards,
Mikael

anton (staff) · **Posted:** Mon Oct 22, 2007 9:54 am

How can I enable debug logging with StarBurn?

First of all you'll have to use Debug version of StarBurn. Either statically link to StarBurn.lib from Lib\Static\Debug or replace StarBurn.dll with the one shipped in Bin\Dynamic\Debug folder (StarBurn OCX component is already built with log files support so no additional activities required). Then you need to decide - how do you want to catch logs? You can either have them traced to system debug output (any debug output hooker can view them - we recommend either DebugView from www.sysinternals.com or DbgMon from www.osr.com) or just saved to the log file. In last case you need to run StarBurn.reg file located in Reg folder of StarBurn installation to enable log file generation. Edit DebugFileName field and
replace default log file name ("C:\StarBurn.log") with the one you want to use. Please keep in mind: all of the file log entries are appended! So it's a good idea to delete old file before starting StarBurn application if you want to send log to somebody (for example to us for analyze). We don't need whole of your development history stored there from the very beginning of the Earth â˜º

#1 Burning Software

Burn error using StarBurn SDK with Delphi 2007

Who is online