#1 Burning Software

Good evening

I'm trying to beef up logging in the program I'm working on. I see that logging requires little more than a few registry entries (which is cool) but I'm getting into multi-burner stuff.

Basically, for each burn I'd like to be able to capture an individual log either by file or directly in C# code.

For a single burner application it's easy: just rename the old log file before each burn and a new one will be generated.

But when burning to more than one writer at once, is there a way to separate things out? (Or maybe things shouldn't be because that way if I need to send you a log you can see if there is some sort of collision between the burners?)

Many thanks
- Shaun

Shaun, unfortunately it's not possible with the build-in burning... Doing multi-thread burning will raise a mess inside the log

Mighty I humbly request, as an enhancement, some form of logging that is friendly to individual burns on individual drives?

This would be incredibly helpful when trying to diagnose burn issues on a customer's machine. Sometimes it is impossible to reproduce something in the shop (thus the purpose of the log in the first place) and I think being able to look at individual burns would help remote troubleshooting considerably.

I'm doing this in the app I'm working on right now... logging pretty much everything that goes on. It has helped me in my own bug-slaying.

Thanks and keep up the great work!
- Shaun

There's some way to filter / highlight info from dedicated threads only. But you'll need to use DebugView or other third-party logger (not analyze StarBurn direct logs). Of course it's helpful and we'll have to add it! The only problem is I have no clue how to do it ATM

You guys seem to be pretty good at figuring stuff out

Thanks again
- Shaun

Unfortunately not always