#1 Burning Software

Hi,

when comparing the required disc size (UdfDataBurner.Size) to the actual free disc space (drive.DiscInfo.TotalSize- drive.DiscInfo.UsedSize), it may happen that enough free disc space is reported, yet when burning, an "insufficient disc space" exception (STARBURN_ERR_DISC_NO_FREE_SPACE) is thrown by the Burn() method.

In my particular case:
UdfDataBurner.Size * 1024 = 736289792 bytes
(TotalSize - UsedSize) * 2048 (= Mode1_LB_Size) = 736960512 bytes

So either one of the sizes is incorrect, or the exception is incorrectly thrown. Please fix.

Does it happen immediately or @ the end? Lead-in & lead-out also occupy space.

Immediately.

We will check this week.

Will be fixed in the nearest week.

Currently, there is a huge "buffer" of approx. 10MB calculated in the databurner objects. This has lead to numerous user complaints, since you can not use the full (or nearly full) disc space anymore. Other burning applications do not reserve 10MB fo burning. COuld you possibly look into that and reduce the reserved space if possible?

Hello,

We can investigate this and implement calculation more accurate.
But we can't do it in the nearest release update.
We will try to do it next nearest release update.

I further tested the situation. It is not related to the type of drive, but caused by something related to the motherboard (SATA controller, driver, etc.). Currently I use Intel DQ77MK. The problem doesn't appear on other motherboards I could test. Further I installed an LSI SAS controller into the Intel motherboard and plugged one LG drive to the SAS the other to the SATA on the motherboard. Tray status is reported correctly through the SAS controller, but gives wrong result through the SATA. I attach the logs. Test were run twice. First both drives' tray open, second closed and media present.

Possible you chose a wrong thread, because the tray status doesn't connected with the disc space.