GUID Problem!!

NTDEV
1

Hi All,

I am facing problem in GUID.

Whenever we generate GUID using GUID generator it gives in the format

// {771B99E6-4941-4ef1-B364-6B635B14813B}
DEFINE_GUID(GUID_WINUSB,
0x771b99e6, 0x4941, 0x4ef1, 0xb3, 0x64, 0x6b, 0x63, 0x5b, 0x14, 0x81, 0x3b);

{771B99E6-4941-4ef1-B364-6B635B14813B} will be used in INF for registering
the Device interface which windows applications will use later.

DEFINE_GUID(GUID_WINUSB,
0x771b99e6, 0x4941, 0x4ef1, 0xb3, 0x64, 0x6b, 0x63, 0x5b, 0x14, 0x81,
0x3b); will be used in application for opening handle to device in
application.

Whenever I am using any GUID Generated by GUID Generator application is
working fine.

But in case of Device interface is alread registered with GUID, Lets
say({A7F2BFD9-10E8-437C-B79E-37F63B42A8DA}), We don’t have corresponding
DEFINE_GUID, So I am manually generating DEFINE_GUID(GUID_WINUSB,
XXXXXXXX-XXXX).

Is it ok do?

I am facing problem when I am using manaully generated DEFINE_GUID.
Application is not able to detect the device.

Possibly, manual generation creating problem, I am not sure!!

Thanks and Regards
Sunil

2

Typically predefined guide are declared in a wdk header. Which specific guid values are you redeclaring?

d

dent from a phine with no keynoard

From: Sunil Kumar
Sent: Thursday, March 03, 2011 9:38 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] GUID Problem!!

Hi All,

I am facing problem in GUID.

Whenever we generate GUID using GUID generator it gives in the format

// {771B99E6-4941-4ef1-B364-6B635B14813B}
DEFINE_GUID(GUID_WINUSB,
0x771b99e6, 0x4941, 0x4ef1, 0xb3, 0x64, 0x6b, 0x63, 0x5b, 0x14, 0x81, 0x3b);

{771B99E6-4941-4ef1-B364-6B635B14813B} will be used in INF for registering the Device interface which windows applications will use later.

DEFINE_GUID(GUID_WINUSB,
0x771b99e6, 0x4941, 0x4ef1, 0xb3, 0x64, 0x6b, 0x63, 0x5b, 0x14, 0x81, 0x3b); will be used in application for opening handle to device in application.

Whenever I am using any GUID Generated by GUID Generator application is working fine.

But in case of Device interface is alread registered with GUID, Lets say({A7F2BFD9-10E8-437C-B79E-37F63B42A8DA}), We don’t have corresponding DEFINE_GUID, So I am manually generating DEFINE_GUID(GUID_WINUSB, XXXXXXXX-XXXX).

Is it ok do?

I am facing problem when I am using manaully generated DEFINE_GUID. Application is not able to detect the device.

Possibly, manual generation creating problem, I am not sure!!

Thanks and Regards
Sunil
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

3

Sunil Kumar wrote:

…
Whenever I am using any GUID Generated by GUID Generator application
is working fine.

But in case of Device interface is alread registered with GUID, Lets
say({A7F2BFD9-10E8-437C-B79E-37F63B42A8DA}), We don’t have
corresponding DEFINE_GUID, So I am manually generating
DEFINE_GUID(GUID_WINUSB, XXXXXXXX-XXXX).

Is it ok do?

Of course. How else would you do it? These are just structures.
Nothing magical about them.

Are you sure you did the conversion correctly?
{A7F2BFD9-10E8-437C-B79E-37F63B42A8DA} would become

DEFINE_GUID(GUID_OurDevice,
0xA7F2BFD9, 0x10E8, 0x437C, 0xB7, 0x9E, 0x37, 0xF6, 0x3B, 0x42, 0xA8, 0xDA);

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.