Replies: 1 comment 3 replies
-
Registering in the Windows Volume Manager is not necessarily the same thing as showing up in Disk Management. Here's an example of what happens when a program does not use the Windows Volume Manager: "OSFMOUNT", a program that mounts disk image files. After your disk image is mounted, you can access files fine, open them, whatever. But the Windows API call GetFinalPathNameByHandleW will break because the device isn't registered with the Windows Volume Manager. It will be unable to find the mounted drive letter. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In the mirror example there is the Option /O which uses the Windows mount manager, but the "drive" is not visible in the Disk Managment. is this a bug or not implemented? I don't even know if it's possible.
Is there a call that can be done within the userspace in order to do that?
I have heavily modified the mirror example to meet my needs, but that part never showed the disk in the Disk Manager.
Beta Was this translation helpful? Give feedback.
All reactions