#1 Burning Software

Hello. I recently noticed that we are having issues using StarBurn_CdvdBurnerGrabber_CreateExEx under 32-bit versions of Windows (XP, Vista, Windows 7). Specifically, when calling the routine while running under Visual Studio's debugger, we see strange behavior. Here is how it typically appears in the StarBurn log:

StarWave Media Streaming Toolkit for Windows 95/98/Me/NT/2000/XP/2003/Vista/Longhorn Version 10.5: Tomahawk ( 0x20081220 )
Copyright (c) Rocket Division Software 2001-2008. All rights reserved.

StarWave_CoInitialize(): >>> ENTERed
StarWave_CoInitialize(): CoInitialize( NULL ) successful, status 1 ( 0x1 )
StarWave_CoInitialize(): <<< EXITing with success
StarWave_UpStart(): <<< EXITing with success

... after this, we see this exception being returned from StarBurn_CdvdBurnerGrabber_CreateExEx()

CStarBurn_ScsiTransportSxxx::CStarBurn_ScsiTransportSxxx(): #1 ( 0x00000000, 0x0267EE44, 0x0267EE24, 0x00000000 ) failed, status 6 ( 0x6 )

To reiterate, the issue only presents itself when running under a debugger (such as Visual Studio's), and we cannot burn discs or even iterate devices in this situation. This only happens on 32-bit versions of Windows under the debugger. 32-bit versions work fine when not running in the debugger. Vista 64 and Windows 7 64 both work fine in and out of the debugger.

We recently upgraded our SPTD drivers from 1.56 to 1.60. I also noticed this behavior in 1.59, but it was not present in 1.56. I'm sure this is probably an issue with SPTD, but I'm not sure what calls StarBurn is making to SPTD, so I'm not sure how best to report the issue to Duplex Secure. Can you provide any assistance?

Thanks.

Wow... The only thing I could do here is to contact SPTD developers. I did... So waiting for their feedback )) We'll keep you updated!

Talked to SPTD developers. Here are a couple of statements:

1) It's not guaranteed SPTD layered software will work under debugger. SPTD has anti-tracing features embedded and also uses some non-debugger friendly techniques and tricks.

2) There should be no issues in general with MS debugger however and they use it as part of their own tests. So they will check it out.

3) They advice to test against different SCSI transport (ASPI or SPTI) and switch to SPTD for production only.

P.S. Burning does not work under debugger as well. Even in test mode My $0.02