#1 Burning Software

I have ported a cd burning application to StarBurn and it has been performing very well, but I was just about to call it a job well done when all of a sudden it started crashing during StarBurn_CdvdBurnerGrabber_TrackAtOnceFromPipeEx(). Here's a snippet of the last entry in the log. Where should I e-mail the full log to?

CStarBurn_CdvdBurnerGrabber::TrackAtOnce(): Reading track information for CD-R(W)

CStarBurn_DumpAndParseTrackInformation(): WARNING! Length 34 less then 40!

Track Information Dump:
Track Number: 1, Session Number: 1
Track Mode: 0x00, Copy: No, Damage: No
Data Mode: 0x0F, FP (Fixed Packet): No, Packet: No, Blank: Yes
RT (Reserved Track): No, NWA_V (Next Writable Address Valid): Yes
Track Start Address (LBA): 0, Next Writable Address (LBA): 0
Free Logical Block(s): 359474, Fixed Packet Size: 0 LB(s)
Track Size In LBs: 359474, Last Recorded Address: 0

A few details I forgot to mention: It seems to crash at the same "place" in the burn every time when I test with the same test track. The problem seems to stem from, or cause a corrupted stack (the stack is trashed when I check it out in the debugger).

We need a complete log for this issue... And what do you burn? Can you supply a failing track to us as well?

Hi Anton,

Not to sound like an ass, but did you read my post??? *Where* do I send the log to? I checked your sticky on logs, and it says not to post them in the forum, so I didn't, but it doesn't say where to send them. It doesn't matter what I burn, any attempts to burn, data or audio, crash immediately when I call BurnTrackAtOnceFromPipeEx() (I am calling the Ex version, not the basic version).

Don't post them at the forum as a text. Attach message to forum post or send it to support@rocketdivision.com. There are plenty of questions like this. Search rules!

Anton, try to remember I'm a paying customer, not your enemy. Obviously I don't need to be told not to post the full log, I didn't, and I won't. I read your rule about logs already (as indicated by both of my previous messages), and the rule, written by you, specifically says NOT to attach logs to forum posts. As I have already said, it also neglects to say where to e-mail logs to. I would recommend that you (A) update your sticky on log messages to correctly indicate that log messages can be attached to forum posts, (B) update your sticky to say where to e-mail logs to in the case of using e-mail, and (C) fully read messages before you reply to them and be a little more gracious towards those of us who are doing our best to comply with your rules. Just a recommendation.

Now that we have that bickering out of the way, I have attached the full log to this message... Thanks for looking in to this for me. It is very odd because the function, like all of StarBurn, has up until now been performing excellently.

It does not matter are you paying customer or not - it's still not possible to trace the issue with log quote you've provided...

If you can reproduce the issue in 100% of the cases - this is good! Can we have your app binaries to run at our test lab? B/c we cannot make StarBurn crash here using pipe burning Having your app will help us dramatically, in the other case we'll have to play with parameters and exchange with e-mails for quite a time...

Thanks!

P.S. And I've re-phrased sticky post, thanks for pointing!

Anton,

Thanks for checking into this. Unfortunately the application only runs on special hardware. Is there nothing useful in the log file? Can I provide some additional information which would be helpful?

That's no problem! I'll bring in touch with you one of our programmers and he'll verify and reproduce your app calls with our prototype.

Log was not helpful this time unfortunately ((

I tried e-mailing support@rocketdivision.com with the details of the calls that I am making and got the following response:

Could you have someone contact me as soon as possible? I believe that we (Format Unlimited Inc.) have purchased some kind of premium support package? Thanks!

Vitali is already working on embedding your code to console app we'll try to reproduce the issue with. You should receive my e-mail so far. Thanks!