#1 Burning Software

It would be nice if StarBurn_UpStart(...) (or it can be separate call) can take path to file for storing log messages. It would be even better if it can take "file" handle (win32 HANDLE) to this file because this allows passing for example pipe handle.

Current way of setting path throught registry is simply not correct because it is shared by all applications build on StarBurn SDK so output in this log can be mixed up.

Can you please look into this?

Regards,

Martin

Probably yes.

Can you please confirm, that StarBurn is reading "DebugFacility" and "DebugFileName" values from registry ONLY in StarBurn_UpStartEx(...) call? If I set this values to our private ones just before calling StarBurn_UpStartEx(...) restoring it afterwards, everything seems to work as expected: our instance of StarBurn is logging into our files and time-frame for collision with other application is limited to time consumed by StarBurn_UpStartEx(...) call. Is this correct?

Yes it is but's crazy hack and OF COURSE every instance should have own logs. We'll fix this in V12.

Logging throught named pipes is unfortunately not working - some of log messages gets lost ;o(

It was never expected to work as we've never tested it.

OK, good news for you. Upcoming V12 will allow you to select from:

- no logging
- debug console
- log file
- custom handle (it could be pipe or your onw log file or whatever HANDLE is)

and enable/disable this stuff per every application (no more global registry settings) and on-the-fly.

So... Stay tuned and don't switch the channel

Great news! I'm looking forward to V12 release. Do you have release time-frame yet?

Core is done and published "gold". Waiting for the rest of the team to update samples to 64-bit bit. Late October I guess...