#1 Burning Software

You need initialize only once. But the system should not freeze of course.

Ok, thats what I thought.
Currently the whole Initialization is per thread and there doesnt seem to be any problem.

Maybe Dima has some good news lately.

It does not freeze during init according to the log. Rather the code stops responding when reserving track for DVD.

Sometimes both threads start to record but after some time the whole thing gets corrupted and I just get CDB errors.
A single burn completes without any kind of problems (thats why I asked about possible issues when initializing
things per thread / multiple times).

I must admit that I have my own routines to Load/Eject media but I guess that shouldnt cause a problem?
(had a first variant which used MCI commands to eject and load media but lately I replaced them with DeviceIoControl calls)

This does not sound like a valid bugreport. "Sometimes", "CDB errors" etc. Dima will fix exclusive device access, you'll update SPTD layer with the most recent one and we'll give another try to see what's wrong.

It's a bad idea to mix APIs. Stick with StarBurn API if you want to use StarBurn. Or you'll end up with tuning one device with two+ handles at the same time.

Well since the drive operations are done when I call the ActiveX to burn the image there shouldnt be an issue.
There are no handles open to the drive all is performed before or after the initialization / uninitialize of the StarBurnX component. And I guess drive operations on drives that arent bound to a StarBurnX object shouldnt trouble the whole ActiveX?

Ok. I downloaded the latest SPTD update and the problems seem to be gone.
Will do more test later today and tomorrow and finally post my results.

Good. Please keep us updated.

Ok, sorry for the late reply.
The burning now works as expected so the main thing was to switch to SPTD layer.
(and install latest available SPTD.sys)

Good. Please stick with this way on all the customers machines.