Prev: microsoft.public.win32.programmer.kernel
Next: inftest.exe generates 3 errors for winusb.sys
From: Ajay on 3 Jun 2010 01:01
Hi all.

We have a filter driver, which attaches to different device-types. We log
the device names in a log file.

Occasionally, on some systems running the filter driver, we observe device
kernel-names like type "\Device\HarddiskVolumeShadowCopy14", but we haven't
been able to reproduce the issue consistently.

Is there a consistent way to replicate attaching to devices of such type?
From: Ajay on 4 Jun 2010 07:25
We managed to hit upon, while creating restore point on Vista.

In our code, we use
"FILE_DEVICE_VIRTUAL_DISK == StorageStackDeviceObject->DeviceType"
as the check (where "StorageStackDeviceObject is "PDEVICE_OBJECT" object),
to check for shadow-volumes in WIN-2003 and above. However, the test fails
for Vista.

Has there been a change in the device-type enumeration for Vista?

Will be grateful for a reply.

Regards
Ajay

"Ajay" wrote:

> Hi all.
>
> We have a filter driver, which attaches to different device-types. We log
> the device names in a log file.
>
> Occasionally, on some systems running the filter driver, we observe device
> kernel-names like type "\Device\HarddiskVolumeShadowCopy14", but we haven't
> been able to reproduce the issue consistently.
>
> Is there a consistent way to replicate attaching to devices of such type?
From: Maxim S. Shatskih on 4 Jun 2010 10:28
> "FILE_DEVICE_VIRTUAL_DISK == StorageStackDeviceObject->DeviceType"
> as the check (where "StorageStackDeviceObject is "PDEVICE_OBJECT" object),
> to check for shadow-volumes in WIN-2003 and above. However, the test fails

Get the driver object name using ObQueryNameString and compare it to \Driver\volsnap

--
Maxim S. Shatskih
Windows DDK MVP
maxim(a)storagecraft.com
http://www.storagecraft.com

 | 
Pages: 1
Prev: microsoft.public.win32.programmer.kernel
Next: inftest.exe generates 3 errors for winusb.sys