#1 Burning Software

It was not my idea unfortunately... I've converted both FindDeviceEx and FindDeviceExEx to use shared enumeration loop so if you'd write me from your company e-mail (for some secret reason I end with "bad user" in all my attempts to reach your @hotmail.com account) I'll provide you with a code making your life quite easy Thanks!

I just got a report from a user who says that when using our burner keeps getting partially burned coasters. However when using the same drive, media and content with both Nero and ImgBurn the disks come out just fine.

Her drive is a Lite-On SHM-165H6S with firmware HS0E and the media is Ritek G05 DVD-Rs.

Any ideas?

Dan

No logs = no ideas. PROBABLY it's filter driver (but you don't use SPTD). PROBABLY it's 32KB burn buffer (but you don't use dynamic linking so I cannot ship experimental build for you with 64KB writes). I don't even know the command failed and the code it completes (as you don't allow logs).

I just modified my code to use the DLL instead of static linking for my STPD tests, so if you have an experimental build with 64KB buffer support then send it over. I'll send the customer a special build and see if it helps. I'll also try turning on logging while I'm at it so we can see that as well.

Edit: Please send both debug and release builds if you've got them. As I said before other portions of my code don't work in debug builds, so I really can't send a debug build to the customer. However I'd still like to have a debug build for my own use.

Dan

Good! I'm doing some final tests here over the "Zoo" of the devices we have so we'll see how 64KB + SPTD will work on your customers side.

Dan, we don't have debug with the debug libraries. They all have release RTL so it's only logging enabled/physically removed what's different. So you have to have ZERO problems with using our debug version of the StarBurn.

So the 64KB thing will only work with STPD? Or does it also work with STPI? I just want to make sure I enable the right mode, and instruct my customer to install the STPD redistributable if that's the case.

Dan

No!!! Variable buffer size will work with ANY builds. I just want your customer to give a try to the SPTD to isolate possible third-party burning software interferences issues

Can you send me that test DLL with the 64KB feature? I'd like to send it to the above user along with the updated code to enable SPTD.

Dan

Yes of course. Just some final checks and I'll be done.

OK, sorry to rush you. I thought you were waiting on me for some reason.

Dan

No problem absolutely! I'll send you .zip to the commercial e-mail and notify here. Thank you!

Back to the original problem... After a lot more research I've discovered that there is definitely something wrong with your IFO patching code. Based on the unofficial DVD specification guide the "Start sector of VTSM_VOBS" should always be set to 0 if the VTS_1_0.VOB file is not present. However in the sample folders I sent you the VTS_1_0.VOB did not exists yet StarBurn set the "Start sector of VTSM_VOBS" value to 6. Nero correctly set it to 0 as required by the specification.



I've tried StarBurn on several other DVD projects as well, which also do not contain a menu and as such do not have a VTS_1_0.VOB file, and SB always sets the "Start sector of VTSM_VOBS" value to 6 instead of 0 like it should.

Hopefully that will help lead you to the bug and allow you to fix it.

Dan

Sounds like you're correct! Please let me check this out. Thank you!

As soon as you get this fixed can you send me a new build? (we're still using static linking for our release build) Even if it's not the one with the beta features (i.e. 64KB, etc...) I need to get this fixed in our product ASAP.

Dan

Yes of course! Thank you very much for your patience.