Hi,
I’m developing a virtual disk driver but when creating the inf file I took as a base the ramdisk.inf file that comes with wdk because my driver works in a similar way than ramdrive sample does.
My question is that the ClassGuid “{78A1C341-4539-11d3-B88D-00C04FAD5171}” is not documented but some drivers I saw on the web (WinUsb) uses it.
Is this guid correct or must I replace it with something else?
Best regards,
Mauro H. Leggieri
xxxxx@caiman.com.ar wrote:
I’m developing a virtual disk driver but when creating the inf file I took as a base the ramdisk.inf file that comes with wdk because my driver works in a similar way than ramdrive sample does.
My question is that the ClassGuid “{78A1C341-4539-11d3-B88D-00C04FAD5171}” is not documented but some drivers I saw on the web (WinUsb) uses it.
Is this guid correct or must I replace it with something else?
There are a small number of pre-defined install classes (perhaps a dozen
or two) that have specific meanings and requirements. However, you can
create your own class any time you want. All you have to do is generate
a new ClassGUID and invent a Class name. Except for a few standard
classes, the ONLY purpose for the Class and ClassGUID is to group your
devices in the Device Manager user interface. That’s it.
The GUID you mention was invented by the author of the UMDF samples in
the WDK, and has the class name “Sample”. I’m guessing that is not what
you want your INF to use. So, just make up your own.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Thank you Tim for the clarifying answer.
Regards, Mauro.