16,548
社区成员
发帖
与我相关
我的任务
分享锁闭光驱的问题（就是锁闭光驱面板上的弹出/关闭按钮）
刚在这里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
...全文
请发表友善的回复…
发表回复
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
- 打赏
- 举报
汗，没人来……
自己顶一下
自己顶一下
