Question about IFileSystemImage

Hello,

I'm using IFileSystemImage to do some data burning, and I need you guys help here~

here are my questions:

1. After importing data from previous session by ImportFileSystem() or adding some files, is there any way to reset the IFileSystemImage Do I have to release current one and re-create a new instance if I want to restart the creation of image

2. I found that after AddFile() of IFsiDirectoryItem, it seems a temp file would be created at tmep path for generation of CreateResultImage. For example, I add in a 200 MB file by AddFile() then a 200 MB tmp file would come out in my temp path. I want to know when will this temp file be deleted Is there any way to manual clean up this temp file Even after I release the IFileSystemImage instance, the tmp file is still there...

3. The last one,,, I find that I would get E_UNEXPECTED from write() of IDiscFormat2Data when I pass the IStream pointer from IFileSystemImageResult::get_ImageStream. This issue would occur if I have burnt a data disc by IFileSystemImage before ( and yes, the previous temp files are still there). I'm not sure if it's the problem of IFileSystemImage or my calling sequence. Please kindly help check if you guys have this problem too.

Very thanks for any help !

1. Absolutely. First thing you want to do is call 'changePoint = get_ChangePoint()'. Later, you can revert the image to this point by calling RollbackToChangePoint(changePoint). Note, however, that once you call CreateResultImage(), the FSI object becomes read-only and cannot be rolled back. If you add in the computational complexity, and the possibility of bugs (it's a non-trivial code path), the best recommendation is to simply create a new FSI object.

2. The temp files are created with the following flags to CreateFile():

Thus, the only reason the file would continue to exist is because of a reference to it. This is typically caused by a refcount leak to the FSI object. Debugging COM ref count leaks is a very in-depth topic which is outside the scope of this forum.

3. (This is just conjecture) If you want to use the resulting IStream more than once, please make sure that you reset the file pointer by Seek()'ing back to the start of the stream. Please let us know if this allows you to burn multiple copies. BTW, I'm not entirely sure I understand the full sequence of your calls. I presumed it was something like:

If this is not the general sequence, and the Seek() workaround doesn't help, please give more details on the sequence in your next post so we can consider it more thoroughly.

hth,

Hi,

1. Thanks for your suggestion. I would try to use get_ChangePoint() in my function.

2. After my test, I find that indeed it's a reference count problem. My FSI object (and temp files) could be released correctly if I'm burning on a blank disc.

My problem is that after importing previous session by put_MultisessionInterfaces(), the reference count of FSI object seems to be increased!!!

I have to call FSI->Release() several times to clean up the temp files... I don't expect the count to be increased by the following code:

3. No, my case is not to use the "same" generated IStream more than once.

My case is like "go through the entire burn process twice". Re-create all necessary interfaces to do the data burning again.

I have tried to seek() before write, but it didn't work... Hope you could find any clue why I would get error code at second burn.

The following is my sequence example, the first round is perfect but I get error at second round:

Hi, Henry,

About the 3rd question, I think I found the solution!!

I found that I always used the same IDiscFormat2Data interface pointer...

After re-create the IDiscFormat2Data instance, I could burn multi-pass successfully !! Thanks God!

So one IDiscFormat2Data instance could be used only "once" for image recording

About the 2nd question, I'm trying to figure it out.

If you could, please kindly provide the possible functions that might increase the reference count of IFileSystemImage.

Great thanks!