none
COMPORT Driver ClassGUID RRS feed

  • Question

  • I am using a Custom SILABS USB CHIP Driver created with the CustomUSBDriverWizard by Silabs.

    I chose Virtual Com Port Driver Installtion for my Custom file.

    Now when pluggin in the USB, the device is recognized and installed correctly. The Device appears under COM Ports in the Device Manager. Now i want the Device to appear in a different section, lets call it "MySection" in the Device Manager.

    What i did in the .inf file was changing :

    Class=Ports
    ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}

    to

    Class=MyClass
    ClassGUID={****MY GUID HERE***}

    and added:

    [ClassInstall32]
    AddReg=ClassRegistry

    [ClassRegistry]
    HKR,,,,%ClassFName%
    HKR,,Icon,,"-16"
    HKR,,SilentInstall,,1

    [Strings]

    ClassFName="My Classes"

    Now the Device is isntalled like it should be, and the device appears under My Classes. But the Com Port is not recognized. When i select a COM Port manually in the Options, the setups crashes...

    Is it actually possible to let the COM Device appear under a different ClassGUID?

    Greetings

    Wednesday, March 5, 2014 2:31 PM

Answers

  • The ClassGUID is there so programs and the system can recognize the device as a Comport.  So when you change it you break its use for most applications and the system.  Live with it as a Comport.


    Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr

    Wednesday, March 5, 2014 2:38 PM
  • It should be possible (maybe with some more tweaks), but you're telling the OS that the device is NOT a standard COM port. This has a price: you will have to make the device detectable by applications, or hack the applications to detect your device. You decide if the appearance in dev. manager is worth it.

    -- pa

    Wednesday, March 5, 2014 4:21 PM

All replies

  • The ClassGUID is there so programs and the system can recognize the device as a Comport.  So when you change it you break its use for most applications and the system.  Live with it as a Comport.


    Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr

    Wednesday, March 5, 2014 2:38 PM
  • Hello,

    thank you for your reply.

    So that means, it is not possible?

    I just wonder because the Silabs USBXpress Driver for the same device worked out when changing the ClassGUID..... 

    Wednesday, March 5, 2014 3:04 PM
  • Hum okay, so the main reason is to integrate more than one Driver in one inf file.

    That means USBXpress and COMPort.

    Is it maybe possible to have 2 [Version] Sections in one inf file?

    Something like USB\VIDXX1&PIDxx1 should use Version Section 1,

    and USB\VIDXX1&PIDxx2 should use Version Section2. Because the ClassGUID is defined in the Version section.

    Gretings

    Thursday, March 6, 2014 8:00 AM
  • Thank you for your support!

    Thursday, March 6, 2014 3:40 PM