#1 Burning Software

I've sent you the link to the custom build this Sunday. I'll ask Anton to duplicate this information from his account.

We use x64 machines and OSes as a primary development platforms here and have absolutely no issues. So can we have a bit more of the information about problems your customers have?

One of the two customers is working with me on the x64 issue. I first had him update the firmware on both of his drives to insure that is not the issue. It didn't help. I then enabled additional logging in my own code to track down exactly where the error was occurring. With that I was able to determine that the call to StarBurn_CdvdBurnerGrabber_VerifyTree is returning error code EN_SCSI_CDB_FAILED. (both the CN_CDVD_VERIFY_BEGIN and CN_CDVD_VERIFY_END call back codes are being sent before it returns if that matters) Anyway after seeing this I sent him another build which catches the error, but this time calls the StopPlayScan function then calls VerifyTree. My hope is that this might reinitialize the drive and allow the verify to complete successfully. He's trying it out now, so I'll let you know when I have results as to whether or not this approach works or not.

Dan

StopPlayScan(...) should return errors on DVD. Verification should not fail however. Do these customers have really working DVDs after burning?

Just had the customer try a couple of the DVDs and he says that they seem to play fine. So just the VerifyTree call is failing with EN_SCSI_CDB_FAILED the TrackAtOnceFromTree and CloseSession calls are completing successfully.

Also I had him try both SPTI and ASPI, and both produced the same result. I just sent him the new build you sent me. So if that doesn't fix the problem then I'll have him try SPTD as well. (the old build was debug and not signed, so I couldn't do SPTD)

Dan

I would LOVE to see the logs from these machines...

I was able to reproduce the problem on my machine. It only happens when the DVD is a DVD+R DL. Here is the log from a burn I just did which produced the same verification error...

I have zipped the log and sent it to you via email.

Dan

...

....

Sorry about the extra posts. I originally had posted my logs spanned across 3 messages, then I saw your request for people not to post logs in the forum.

Dan

They are truncated so the most interesting part is missing

OK, got the stuff from you. The issue has nothing to do with the x64 or verification. It's improper session close for +R DL media. I'll get LiteOn 160PS tomorrow or will bug you with the remote debugging if I'd fail to do it.

Thank you!

Odd because CloseSession was return EN_SUCCESS it was VerifyTree that was returning the error. In any case if you can fix it I'll be happy.

Dan

Drive reports it's done with the session fixation while it's not really true. Of course we'll have to fix it On Monday I'll tell do we have device available here or will we bug you

Just got a report from a user who had this same thing happen on a SL DVD+RW disk. This makes me wonder... Is it possible that the verification routine is simply returning the wrong error code? Perhaps this users disk is actually failing the verification but instead of returning EN_VERIFY_FAILED it's returning EN_SCSI_CDB_FAILED. If that's the case then it could explain why DL disks with the closing problem you discovered are causing the verification routine to return EN_SCSI_CDB_FAILED instead of EN_VERIFY_FAILED.

Just something to look at while you're at it.

Dan

I don't think so... There was a bug in the old StarBurn returning immediately after StopPlayScan(...) failing. Since you don't provide any logs I don't have a clue about do you have THAT build or not. Try updating the guys with the RC you have to see the difference. And get us the logs. B/c in your case it's quite possible it's BURNING failing and not real verification (as it happens on PS160 LiteOn).

This is happening with the new build you sent. It did NOT happen with the old 7.2 build. I do not use StopPlayScan! I go directly from CloseSession to VerifyTree. After getting reports of this error I added a catch statement which catches the error from VerifyTree and tries a StopPlayScan then calls VerifyTree again, but that did not help any of my customers.

I sent you the logs showing this error last week. You said it had something to do with the DVD+R DL disks not closing correctly. I was simply supplying this customers experience (i.e. same failure with a DVD+RW disk) as a point of reference so that you would know that this failure is not exclusive to DVD+R DL disks.

My theory about the wrong message was just that, a theory.

Dan