#1 Burning Software

Hi Anton,

I'm using the TrackAtOnceFromFile function to transfer pre-mastered images to either DVD or CD, depending upon what the user loads into the drive.

The image file we use is never deleted. This way the file is more likely to be sequential and is unlikely to become severely fragmented.

Here's the problem. The TrackAtOnceFromFile appears to copy the entire file, without looking at the image contents and seeing how big the actual file system it contains is. So if the first record is a full DVDs worth of data, this amount of data will always get transferred even if a new file system it contains is substantially smaller.

Do you have a method to limit how much of the image file is transferred, either the calling function specifying a file system size or your function that checks the contents of the image?

I've checked the header file and CHM help but couldn't see anything obvious.

Cheers,

Colin

First of all sorry for delayed reply - I've occasionally lost this message

Second, we have no clue about FS format you use. So it's up to you to get number of fee logical blocks and find out would your image fit into the media or not. Please correct me if I've got your question wrong.

Thanks!

Hi Anton,

Yep, you missed it.

Basically, I don't want to transfer the whole file. I want to keep the file big to avoid fragmentation, but only transfer the portion of the file that contains the UDF/ISO file system, i.e. limit how much of the file TrackAtOnceFromFile will transfer.

I think it's unlikely you'll be able to do this, but it's worth asking the question.

Thanks,

Colin

You can play with cache buffer size. StarBurn does read ahead only for cache size. Is it it?

No, I assume the cache buffer size will determine how much is read in advance, but it cannot be used to stop the reading before the end of the file.

I've looked around and the cache buffer loading and image file reading is controlled internally by your function, so there isn't an opportunity for the calling function to halt it after enough has been read. The internal function will keep reading until the end of the file is reached.

I don't think I've explained myself clearly here, but I've looked around again and am pretty sure you don't have what I need. So I'll truncate the image file myself prior to the call to TAO call.

Thanks,

Colin

So you have f.e. 1GB media and 10GB image, you're recording AS IS (I don't care why you need this - it's your own business...) and want us stop exactly at 1GB border? See, we would stop automagically after media would be full. It would be just media size (1GB in sample case) + cache size (160MB default) overhead.