1.5w+
社区成员
锁闭光驱的问题（就是锁闭光驱面板上的弹出/关闭按钮）
刚在这里http://topic.csdn.net/t/20030221/13/1451340.html找到一个代码，在VC2005、windows2003下测试通过。
但是在查找MSDN时，发现有这么个东西：
The IOCTL_STORAGE_MEDIA_REMOVAL control code enables or disables the mechanism that ejects media, for those devices possessing that locking capability.
The IOCTL_STORAGE_EJECTION_CONTROL control code enables or disables the mechanism that ejects media. Disabling the mechanism locks the drive.
前面的代码中是用IOCTL_STORAGE_MEDIA_REMOVAL实现光驱的锁定、解锁的，以我相当贫乏的英文水平看上面2段MSDN说明，IOCTL_STORAGE_EJECTION_CONTROL与IOCTL_STORAGE_MEDIA_REMOVAL的作用好像是一样的吧？可是为何使用IOCTL_STORAGE_EJECTION_CONTROL却不能达到相同的目的——DeviceIoControl总是返回FALSE
但是在查找MSDN时，发现有这么个东西：
The IOCTL_STORAGE_MEDIA_REMOVAL control code enables or disables the mechanism that ejects media, for those devices possessing that locking capability.
The IOCTL_STORAGE_EJECTION_CONTROL control code enables or disables the mechanism that ejects media. Disabling the mechanism locks the drive.
前面的代码中是用IOCTL_STORAGE_MEDIA_REMOVAL实现光驱的锁定、解锁的，以我相当贫乏的英文水平看上面2段MSDN说明，IOCTL_STORAGE_EJECTION_CONTROL与IOCTL_STORAGE_MEDIA_REMOVAL的作用好像是一样的吧？可是为何使用IOCTL_STORAGE_EJECTION_CONTROL却不能达到相同的目的——DeviceIoControl总是返回FALSE
...全文
当前发帖距今超过3年，不再开放新的回复
发表回复
gnuljf 2008-01-17
我靠，还是没人解答啊，算了，结贴
gnuljf 2007-12-03
继续顶上去
gnuljf 2007-10-12
上去，咋就没人帮忙看看呢？
ribut9225 2007-10-02
帮顶
偶也是金山受害者
偶也是金山受害者
lubf 2007-10-01
定
gnuljf 2007-08-18
唉，可怜啊，没人关注
gnuljf 2007-08-10
以下是从MSDN Online中找来的，谁能帮忙解释一下
IOCTL_STORAGE_EJECTION_CONTROL
Operation
Locks the device to prevent removal of the media. If the driver can prevent the media from being removed while the drive is in use, the driver disables or enables the mechanism that ejects media, thereby locking the drive. A caller must open the device with FILE_READ_ATTRIBUTES to send this request.
Unlike IOCTL_STORAGE_MEDIA_REMOVAL, the driver tracks IOCTL_STORAGE_EJECTION_CONTROL requests by caller and ignores unlock requests for which it has not received a lock request from the same caller, thereby preventing other callers from unlocking the drive.
A driver for a removable-media device - can support this IOCTL must do the following:
Keep a lock count, tagged by caller, in the device object extension.
Keep the lock count per physical device.
When called with this IOCTL, if the flag to prevent removing the media is set, increment the count; if the flag is clear and the driver has previously received a lock request from the same caller, decrement the count.
Prevent removal of the media unless all lock counts are zero.
Under normal circumstances, the caller who locked the device using IOCTL_STORAGE_EJECTION_CONTROL, unlocks the device by sending IOCTL_STORAGE_EJECTION_CONTROL again with Irp->AssociatedIrp.SystemBuffer set to a boolean value of FALSE. However, sometimes the caller fails to unlock the device properly.
To ensure that media removal locks are released properly, the class driver keeps track of callers who lock the media with IOCTL_STORAGE_EJECTION_CONTROL. If the caller terminates without unlocking the device, the class driver unlocks the device.
Input
The buffer at Irp->AssociatedIrp.SystemBuffer contains a Boolean value, with TRUE indicating that the driver should lock the media in the drive.
Output
None
I/O Status Block
The Information field is set to zero. The Status field is set to STATUS_SUCCESS, or possibly to STATUS_INVALID_DEVICE_REQUEST, STATUS_NO_MEDIA_IN_DEVICE, or STATUS_DEVICE_NOT_CONNECTED.
Requirements
Headers: Defined in ntddstor.h. Include ntddstor.h.
IOCTL_STORAGE_EJECTION_CONTROL
Operation
Locks the device to prevent removal of the media. If the driver can prevent the media from being removed while the drive is in use, the driver disables or enables the mechanism that ejects media, thereby locking the drive. A caller must open the device with FILE_READ_ATTRIBUTES to send this request.
Unlike IOCTL_STORAGE_MEDIA_REMOVAL, the driver tracks IOCTL_STORAGE_EJECTION_CONTROL requests by caller and ignores unlock requests for which it has not received a lock request from the same caller, thereby preventing other callers from unlocking the drive.
A driver for a removable-media device - can support this IOCTL must do the following:
Keep a lock count, tagged by caller, in the device object extension.
Keep the lock count per physical device.
When called with this IOCTL, if the flag to prevent removing the media is set, increment the count; if the flag is clear and the driver has previously received a lock request from the same caller, decrement the count.
Prevent removal of the media unless all lock counts are zero.
Under normal circumstances, the caller who locked the device using IOCTL_STORAGE_EJECTION_CONTROL, unlocks the device by sending IOCTL_STORAGE_EJECTION_CONTROL again with Irp->AssociatedIrp.SystemBuffer set to a boolean value of FALSE. However, sometimes the caller fails to unlock the device properly.
To ensure that media removal locks are released properly, the class driver keeps track of callers who lock the media with IOCTL_STORAGE_EJECTION_CONTROL. If the caller terminates without unlocking the device, the class driver unlocks the device.
Input
The buffer at Irp->AssociatedIrp.SystemBuffer contains a Boolean value, with TRUE indicating that the driver should lock the media in the drive.
Output
None
I/O Status Block
The Information field is set to zero. The Status field is set to STATUS_SUCCESS, or possibly to STATUS_INVALID_DEVICE_REQUEST, STATUS_NO_MEDIA_IN_DEVICE, or STATUS_DEVICE_NOT_CONNECTED.
Requirements
Headers: Defined in ntddstor.h. Include ntddstor.h.
gnuljf 2007-08-10
以下是从MSDN Online中找来的，谁能帮忙解释一下
IOCTL_STORAGE_EJECTION_CONTROL
Operation
Locks the device to prevent removal of the media. If the driver can prevent the media from being removed while the drive is in use, the driver disables or enables the mechanism that ejects media, thereby locking the drive. A caller must open the device with FILE_READ_ATTRIBUTES to send this request.
Unlike IOCTL_STORAGE_MEDIA_REMOVAL, the driver tracks IOCTL_STORAGE_EJECTION_CONTROL requests by caller and ignores unlock requests for which it has not received a lock request from the same caller, thereby preventing other callers from unlocking the drive.
A driver for a removable-media device - can support this IOCTL must do the following:
Keep a lock count, tagged by caller, in the device object extension.
Keep the lock count per physical device.
When called with this IOCTL, if the flag to prevent removing the media is set, increment the count; if the flag is clear and the driver has previously received a lock request from the same caller, decrement the count.
Prevent removal of the media unless all lock counts are zero.
Under normal circumstances, the caller who locked the device using IOCTL_STORAGE_EJECTION_CONTROL, unlocks the device by sending IOCTL_STORAGE_EJECTION_CONTROL again with Irp->AssociatedIrp.SystemBuffer set to a boolean value of FALSE. However, sometimes the caller fails to unlock the device properly.
To ensure that media removal locks are released properly, the class driver keeps track of callers who lock the media with IOCTL_STORAGE_EJECTION_CONTROL. If the caller terminates without unlocking the device, the class driver unlocks the device.
Input
The buffer at Irp->AssociatedIrp.SystemBuffer contains a Boolean value, with TRUE indicating that the driver should lock the media in the drive.
Output
None
I/O Status Block
The Information field is set to zero. The Status field is set to STATUS_SUCCESS, or possibly to STATUS_INVALID_DEVICE_REQUEST, STATUS_NO_MEDIA_IN_DEVICE, or STATUS_DEVICE_NOT_CONNECTED.
Requirements
Headers: Defined in ntddstor.h. Include ntddstor.h.
IOCTL_STORAGE_EJECTION_CONTROL
Operation
Locks the device to prevent removal of the media. If the driver can prevent the media from being removed while the drive is in use, the driver disables or enables the mechanism that ejects media, thereby locking the drive. A caller must open the device with FILE_READ_ATTRIBUTES to send this request.
Unlike IOCTL_STORAGE_MEDIA_REMOVAL, the driver tracks IOCTL_STORAGE_EJECTION_CONTROL requests by caller and ignores unlock requests for which it has not received a lock request from the same caller, thereby preventing other callers from unlocking the drive.
A driver for a removable-media device - can support this IOCTL must do the following:
Keep a lock count, tagged by caller, in the device object extension.
Keep the lock count per physical device.
When called with this IOCTL, if the flag to prevent removing the media is set, increment the count; if the flag is clear and the driver has previously received a lock request from the same caller, decrement the count.
Prevent removal of the media unless all lock counts are zero.
Under normal circumstances, the caller who locked the device using IOCTL_STORAGE_EJECTION_CONTROL, unlocks the device by sending IOCTL_STORAGE_EJECTION_CONTROL again with Irp->AssociatedIrp.SystemBuffer set to a boolean value of FALSE. However, sometimes the caller fails to unlock the device properly.
To ensure that media removal locks are released properly, the class driver keeps track of callers who lock the media with IOCTL_STORAGE_EJECTION_CONTROL. If the caller terminates without unlocking the device, the class driver unlocks the device.
Input
The buffer at Irp->AssociatedIrp.SystemBuffer contains a Boolean value, with TRUE indicating that the driver should lock the media in the drive.
Output
None
I/O Status Block
The Information field is set to zero. The Status field is set to STATUS_SUCCESS, or possibly to STATUS_INVALID_DEVICE_REQUEST, STATUS_NO_MEDIA_IN_DEVICE, or STATUS_DEVICE_NOT_CONNECTED.
Requirements
Headers: Defined in ntddstor.h. Include ntddstor.h.
marrco2005 2007-08-08
mark
gnuljf 2007-08-08
汗，没人来……
自己顶一下
自己顶一下
测试开发笔记 代码走查 测试过程 上一阶段为下个阶段提供重点指导 用户参与的测试或用户反映回来的错误和问题为下次测试的或测试补充的必备内容 第二章 测试过程 1.测试模型 H模型： H模型图 优点： 1 介入早 与开发并行 更早的...
2000-XP-2003操作系统常见问题 内容索引： 第一部分：安装启动问题 1、关于所有版本XP在安装进度还剩下34分钟进度条就停止不动的说明以及解决方法 2、双启动菜单丢失 3、XP系统启动时出现NTLDR is missing的错误提示 4、XP系统启动时提示找不到HAL...
系统技巧和故障处理 修改文件右键菜单（比如...该分支下有两个主键HexWorkshopContextMenu和Winzip(自己安装的程序)，删去后即可发现原来文件的弹出菜单上的Hex edit 和Add to Zip两项不见了。当要在弹出菜单中添加一些可执行文件时（以no
注册表知识and技巧大全 二进制值，第一字节的每位对应于不同的驱动器，如果对应位置为“1”则表示关闭自动运行功 能，如果对应位置为“0”则表示打开自动运行功能。下表是各位对应的驱动器类型 第0位：未知驱动器 第2位：可移动驱动器 ...
make xconfig详解 make menuconfig 图形化的内核配置 ...make mrproper 删除不必要的文件和...make oldconfig 如果只想在原来内核配置的基础上修改一些小地方，会省去不少麻烦 make config 基于文本的最为传统的配置界面，不推
注册表知识和技巧大全 二进制值，第一字节的每位对应于不同的驱动器，如果对应位置为“1”则表示关闭自动运行功 能，如果对应位置为“0”则表示打开自动运行功能。下表是各位对应的驱动器类型 第0位：未知驱动器 第2位：可移动驱动器 ...
电脑故障 ：关掉机器，设置主板上关于显示卡器的跳线 DMA Error ： DMA 控制器出错 DMA #1 Error ： 第 1 个 DMA 控制器出错 DMA #2 Error ： 第 2 个 DMA 控制器出错 FDD Controller Failure ： ...
注册表知识与技巧大全 二进制值，第一字节的每位对应于不同的驱动器，如果对应位置为“1”则表示关闭自动运行功 能，如果对应位置为“0”则表示打开自动运行功能。下表是各位对应的驱动器类型 第0位：未知驱动器第2位：可移动驱动器第3...
UBUNTU教程之菜鸟飞飞 <br />本文转自 ...本人尽力解释<br />为准备本文，收集了很多资料，前几日，在ubuntu论坛看到有热心网友把一切都总结的很好了，虽然是在8.10基础上写的，但对于9.04也同样适用，为<br /
注册表故障 修改文件右键菜单（比如添加打开方式）运行...该分支下有两个主键HexWorkshopContextMenu和Winzip(自己安装的程序)，删去后即可发现原来文件的弹出菜单上的Hex edit 和Add to Zip两项不见了。当要在弹出菜单中添加一...
Linux命令 所以，在Linux系统上工作离不开使用系统提供的命令。要想真正理解Linux系统， 就必须从Linux命令学起，通过基础的命令学习可以进一步理解Linux系统。 不同Linux发行版的命令数量不一样，但Linux发行版本最少的命令...
注册表修改完全攻略 注册表狂修改(1-300) 不要告诉我连注册表是什么都不知道，呵呵，打开你的开始菜单，点运行，在弹出的对话框中输入“Regedit”就知道了...........1.自动刷新 每次在窗口添加一个文件夹或删除一个对象后，须要按键对...
linux中常用的60个命令及作用详解 所以，在 Linux 系统上工作离不开使用系统提供的命令。要想真正理解 Linux 系统，就必须从 Linux 命令学起，通过基础的命令学习可以进一步理解 Linux 系统。 不同 Linux 发行版的命令数量不一样，但 Linux 发行版本...
