#1 Burning Software

Hi

Somehow callback function is returning wrong numbers of using the buffer
I've burned some info to the disk and here is what it has returned

1st callback.
BufferCurrent = 1445330078212, BufferTotal = -8907334990593723017

From the second time results are the same:
BufferCurrent = 1443109011456, BufferTotal = 1608336.

No matter if BUP is enabled.

Seems this feature does not work or disabled.

How to get right numbers (enable this feature) ?

Thanks in advance for your support.

Alex,

what sample from SDK are you using? If not using the sample can you

1) replay the condition with the sample from SDK?

2) provide us with a source code snippet?

Thanks!

Hello

I had a look at sample and I've found my mistake in callback function.
It turned out I used Int64 type instead of DWORD.
After I had fixed it, your sample and mine reported the same buffer usage data,

First callback
BufferFree = 344771076, BufferTotal = -431950473, BufferPercent = 100
All subsequent ones
BufferFree = 0, BufferTotal = 1608336, BufferPercent = 100

BUT
I have burned 500 Mb and have not got any result except 100%.

Seems callback function is called too seldom. And buffer is flushed
onto the disc between two calls.

What the sence of this value could be then?

Thanks

Nice to know it was not our bug

If you want to see buffer status numbers less then 100% you can 1) set cache size for device (software cache I mean) less then default 64 megabytes 2) initiate some hard disk activity on the partition your burning files lay on.

If the system is not configured properly (ATAPI burner is in PIO mode, hard disk is too slow to provide data stream b/s it's just too slow or it also serves other tasks) hardware cache fill status would not be 100% and it would indicate to user something goes wrong. That's the way this stuff is used. If it's 100% this means everything is OK. And I'm not sure it's a good reason to blame us

Let me know if you'll need any additional help.