#1 Burning Software

I've sent a link to the experimental build facing this issue to your registration e-mail. Please confirm receive. Thanks!

I received it. I'll build it into my app and send it to a few of my customers who were having problems and let you know the results.

Dan

Sure! You may run it against the different compilations you have (I did). Thanks!

OK I did some testing of my own, before sending it to the customer, and now I'm seeing other problems with the IFO...

1) Now the "First Sector of VTSM_VOBS" is always being set to 0. It should only be set to 0 if VTS_xx_0.VOB does not exists. (i.e. there is not VTS menu)

2) The "Last Sector of VTS" is also being set to 0, which is not right. It should be set to the total size of the VTS.



Dan

Hold on, looks like I've uploaded wrong build

Please download the same stuff from the same location. Thank you!

Any feedback from your you or your customer?

Sorry I missed this somehow. I'll try it now and let you know what I find out.

Dan

NP

Looking forward feedback from you.

Never heard back from the customer. However based on my own test this seems to have fixed the problem. Can I get a release build of this version? I know the only difference is the logging, but the debug build of the DLL is over 200Kb bigger and we'd like to keep our installer as small as possible.

Thanks,
Dan

Contacted the customer again and this time he got back to me. The problem appears to be fixed in this new build. So as soon as you can get me that release build I would really appreciate it.

Thanks,
Dan

Good! I'll be back on January 12th and will prepare custom build for you as it can take some time before we'll have official StarBurn SDK release this time (tons of samples, new StarBurnX wrapper etc). Thank you very much for your support & patience!

The 12th should be fine. We're at CES right now anyway, so I wont be back to work until Friday the 11th myself.

Dan

OK, so I'll do it on Saturday

Never got it. Do you have a build for me yet?

Also is there anything in the new build that would cause problems in x64 versions of Windows? I have two customers using x64 Windows who are complaining that this new build causes problems on their systems, even though previous versions did not.

Edit: More on the above. I have one customer who has two DVD burner, one Sony one Pioneer, and both were producing coasters when burning DVD+R DL media with the updated DLL. I sent him the old release DLL and both drives are now working again. So something is obviously regressed in the new build. Not 100% sure it has anything to do with x64, but I do have two customers with x64 OSes (one Vista, one XP) both with the same problem.

Dan