本文介绍了IMAPI2:为什么现在IFileSystemImage :: CreateResultImage()访问CD?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我负责CD刻录应用程序,该应用程序必须与过滤器驱动程序配合才能访问CD驱动器.它始终处于暂存状态(即调用IFileSystemImage :: put_StageFiles(VARIANT_TRUE)).

I am responsible for a CD-burning application which has to cooperate with a filter driver to get access to the CD drive.  It is always staged (i.e. IFileSystemImage::put_StageFiles(VARIANT_TRUE) is called).

这种合作一直很好,直到最近,当它突然开始因调用IFileSystemImage :: CreateResultImage()返回C0AAB157而跳闸时,我相信这是过滤器驱动程序拒绝访问的结果.

This cooperation was working well until recently, when it suddenly started tripping up over a call to IFileSystemImage::CreateResultImage() returning C0AAB157, which I believe is the result of the filter driver refusing access.

三个问题:

  1. 该错误是否与过滤器驱动程序拒绝一致?
  2. 最近(相对)更改了此界面吗?特别是,它是否已作为以下内容的一部分进行了更改?Windows Feature Pack for Storage 1.0 ?
  3. 您能为我提供有关访问(或不访问)物理驱动器的IMAPI2接口的任何保证吗?
  1. Is that error consistent with a filter driver refusal?
  2. Has this interface changed (relatively) recently?  In particular,  did it change as part ofWindows Feature Pack for Storage 1.0 ?
  3. Can you offer me any guarantees about IMAPI2 interfaces regarding accessing (or not accessing) the physical drive?


回答政策:请参阅个人资料.


Answering policy: see profile.

推荐答案

您是否制作多会话图像?如果您不使用put_MultisessionInterfaces 文件系统映像现在对光盘刻录机一无所知.但是,在另一种情况下(您确实使用多会话),文件系统映像必须知道并从驱动器读取数据.

Do you do multisession image? If you don't use put_MultisessionInterfaces filesystemimage wouldn't even now anything about the disc recorder. However in the other case (you do use multisession) filesystemimage has to know and read the data from the drive.

Hth,
米哈伊尔(Mikhail)

Hth,
Mikhail


这篇关于IMAPI2:为什么现在IFileSystemImage :: CreateResultImage()访问CD?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

10-31 10:39