C# HID and Vista 64

[Eric Renken]

Well I am working on trying to get some HID code to work on Windows XP,
Vista 32, and Vista 64. Working on XP and Vista 32 was easy as there are
some great resources on the web; however Vista 64 is a whole other problem.
The first problem was an easy one all the samples show this structure:

[StructLayout(LayoutKind.Sequential)]
public struct SP_DEVICE_INTERFACE_DATA
{
public int cbSize;
public System.Guid InterfaceClassGuid;
public int Flags;
public IntPtr Reserved;
}

For calling the this method, SetupDiEnumDeviceInterfaces, in the
SetupAPI.dll; however most exaple has Reserved as just an Int and on a 64
bit platform that doesn't give you the correct size for an IntPtr. So all
my following problems are related to Vista 64.

Now that I have gotten past that part I am having problems with this method,
SetupDiGetDeviceInterfaceDetail, in SetupAPI.dll. When I call I this method
I get this error from GetLastError: "An attempt was made to reference a
token that does not exist."

Here is what my declartions look like:

[DllImport("setupapi.dll", CharSet = CharSet.Auto)]
static public extern bool SetupDiGetDeviceInterfaceDetail(IntPtr
DeviceInfoSet, ref SP_DEVICE_INTERFACE_DATA DeviceInterfaceData, IntPtr
DeviceInterfaceDetailData, int DeviceInterfaceDetailDataSize, ref int
RequiredSize, IntPtr DeviceInfoData);

[StructLayout(LayoutKind.Sequential)]
public struct SP_DEVICE_INTERFACE_DATA
{
public int cbSize;
public System.Guid InterfaceClassGuid;
public int Flags;
public IntPtr Reserved;
}

[StructLayout(LayoutKind.Sequential)]
public struct SP_DEVICE_INTERFACE_DETAIL_DATA
{
public int cbSize;
public string DevicePath;
}

The program makes 2 calls to SetupDiGetDeviceInterfaceDetail. The first
call it to get the size of the structure and the second returns a pointer to
the data. However on the frist run both picese return the same error that I
stated above. Here is what the first call looks like:

Success =
DeviceManagementApiDeclarations.SetupDiGetDeviceIn terfaceDetail(
DeviceInfoSet,
ref MyDeviceInterfaceData,
IntPtr.Zero, 0, ref BufferSize, IntPtr.Zero);

Here is the deifinition of the caribales used:
Scuesses = bool
DeviceInforSet = IntPtr
BufferSize = int

After the API call this data is called:

// Store the structure's size.
//MyDeviceInterfaceDetailData.cbSize =
MyDeviceInterfaceDetailData.ToString().Length;
MyDeviceInterfaceDetailData.cbSize =
Marshal.SizeOf(MyDeviceInterfaceDetailData);

// Allocate memory for the MyDeviceInterfaceDetailData Structure using
the returned buffer size.
IntPtr DetailDataBuffer = Marshal.AllocHGlobal(BufferSize);

// Store cbSize in the first 4 bytes of the array
Marshal.WriteInt32(DetailDataBuffer, 4 +
Marshal.SystemDefaultCharSize);
Debug.WriteLine("cbsize = " + MyDeviceInterfaceDetailData.cbSize);

I am pretty sure I would need to change the 4 + to 8 + for 64 bit, but I am
not positive.

Then I call SetupDiGetDeviceInterfaceDetail again:

Success =
DeviceManagementApiDeclarations.SetupDiGetDeviceIn terfaceDetail (
DeviceInfoSet,
ref MyDeviceInterfaceData,
DetailDataBuffer,
BufferSize,
ref BufferSize,
IntPtr.Zero);

After that call this code is run:

IntPtr pdevicePathName = IntPtr.Zero;
if ( Marshal.SizeOf( DeviceInfoSet ) == 4 )
pdevicePathName = new IntPtr(DetailDataBuffer.ToInt32() +
Marshal.SizeOf(DeviceInfoSet));
else
pdevicePathName = new IntPtr(DetailDataBuffer.ToInt64() +
Marshal.SizeOf(DeviceInfoSet));

// Get the String containing the devicePathName.
SingledevicePathName = Marshal.PtrToStringAuto(pdevicePathName);
devicePathName[MemberIndex] = SingledevicePathName;

I just added the code to increment these values based on the Size of IntPtr.

The next time this code runs for the next HID device I get this error: The
supplied user buffer is not valid for the requested operation.

Any help would be greatly appriciated.

Thanks,

Eric Renken

[Ben Voigt [C++ MVP]]

>

Any help would be greatly appriciated.

Since all your problems have to do with p/invoke definitions, it would be
well worth your while to make a small C++/CLI dll project to handle all the
API calls. If you make a "public ref class" in C++/CLI and add it to your
application references, it will appear in your C# program just like any C#
class would. Since all the examples are already in C++, this should make
your life a lot easier.

>
Thanks,

Eric Renken

[Walter Wang [MSFT]]

Hi Eric,

I agree with Ben here that writing the code in C++/CLI will be easier and
cleaner.

Setupapi.dll also has a 32-bit version at %windir%\syswow64. If 32-bit
interop is already working fine, why not just compile your C# program in
32-bit so that it calls into 32-bit setupapi.dll?
Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Willy Denoyette [MVP]]

"Eric Renken" <Er********@newsgroup.nospamwrote in message
news:0D**********************************@microsof t.com...

Well I am working on trying to get some HID code to work on Windows XP,
Vista 32, and Vista 64. Working on XP and Vista 32 was easy as there are
some great resources on the web; however Vista 64 is a whole other
problem. The first problem was an easy one all the samples show this
structure:

[StructLayout(LayoutKind.Sequential)]
public struct SP_DEVICE_INTERFACE_DATA
{
public int cbSize;
public System.Guid InterfaceClassGuid;
public int Flags;
public IntPtr Reserved;
}

For calling the this method, SetupDiEnumDeviceInterfaces, in the
SetupAPI.dll; however most exaple has Reserved as just an Int and on a 64
bit platform that doesn't give you the correct size for an IntPtr. So all
my following problems are related to Vista 64.

Now that I have gotten past that part I am having problems with this
method, SetupDiGetDeviceInterfaceDetail, in SetupAPI.dll. When I call I
this method I get this error from GetLastError: "An attempt was made to
reference a token that does not exist."

Here is what my declartions look like:

[DllImport("setupapi.dll", CharSet = CharSet.Auto)]
static public extern bool SetupDiGetDeviceInterfaceDetail(IntPtr
DeviceInfoSet, ref SP_DEVICE_INTERFACE_DATA DeviceInterfaceData, IntPtr
DeviceInterfaceDetailData, int DeviceInterfaceDetailDataSize, ref int
RequiredSize, IntPtr DeviceInfoData);

[StructLayout(LayoutKind.Sequential)]
public struct SP_DEVICE_INTERFACE_DATA
{
public int cbSize;
public System.Guid InterfaceClassGuid;
public int Flags;
public IntPtr Reserved;
}

[StructLayout(LayoutKind.Sequential)]
public struct SP_DEVICE_INTERFACE_DETAIL_DATA
{
public int cbSize;
public string DevicePath;
}

The program makes 2 calls to SetupDiGetDeviceInterfaceDetail. The first
call it to get the size of the structure and the second returns a pointer
to the data. However on the frist run both picese return the same error
that I stated above. Here is what the first call looks like:

Success =
DeviceManagementApiDeclarations.SetupDiGetDeviceIn terfaceDetail(
DeviceInfoSet,
ref MyDeviceInterfaceData,
IntPtr.Zero, 0, ref BufferSize, IntPtr.Zero);

Here is the deifinition of the caribales used:
Scuesses = bool
DeviceInforSet = IntPtr
BufferSize = int

After the API call this data is called:

// Store the structure's size.
//MyDeviceInterfaceDetailData.cbSize =
MyDeviceInterfaceDetailData.ToString().Length;
MyDeviceInterfaceDetailData.cbSize =
Marshal.SizeOf(MyDeviceInterfaceDetailData);

// Allocate memory for the MyDeviceInterfaceDetailData Structure
using the returned buffer size.
IntPtr DetailDataBuffer = Marshal.AllocHGlobal(BufferSize);

// Store cbSize in the first 4 bytes of the array
Marshal.WriteInt32(DetailDataBuffer, 4 +
Marshal.SystemDefaultCharSize);
Debug.WriteLine("cbsize = " + MyDeviceInterfaceDetailData.cbSize);

I am pretty sure I would need to change the 4 + to 8 + for 64 bit, but I
am not positive.

Then I call SetupDiGetDeviceInterfaceDetail again:

Success =
DeviceManagementApiDeclarations.SetupDiGetDeviceIn terfaceDetail (
DeviceInfoSet,
ref MyDeviceInterfaceData,
DetailDataBuffer,
BufferSize,
ref BufferSize,
IntPtr.Zero);

After that call this code is run:

IntPtr pdevicePathName = IntPtr.Zero;
if ( Marshal.SizeOf( DeviceInfoSet ) == 4 )
pdevicePathName = new IntPtr(DetailDataBuffer.ToInt32() +
Marshal.SizeOf(DeviceInfoSet));
else
pdevicePathName = new IntPtr(DetailDataBuffer.ToInt64() +
Marshal.SizeOf(DeviceInfoSet));

// Get the String containing the devicePathName.
SingledevicePathName = Marshal.PtrToStringAuto(pdevicePathName);
devicePathName[MemberIndex] = SingledevicePathName;

I just added the code to increment these values based on the Size of
IntPtr.

The next time this code runs for the next HID device I get this error:
The supplied user buffer is not valid for the requested operation.

Any help would be greatly appriciated.

Thanks,

Eric Renken

It makes no sense to call SetupDiGetDeviceInterfaceDetail a second time when
the first call did NOT return ERROR_INSUFFICIENT_BUFFER.
Anyway, you need to pass a valid SP_DEVICE_INTERFACE_DATA when calling
SetupDiGetDeviceInterfaceDetail , that is you need to pass a structure that
is returned from a call to SetupDiEnumDeviceInterfaces ; it's not clear
whether you did call this API from your explanation.
So, please post some more code, especially what you did before calling
SetupDiGetDeviceInterfaceDetail is what we need.

Willy.

[Eric Renken]

Thanks everyone for the information. Walter, I did think about having that
DLL run as 32-bit only to make it work, but I am kind of interested in
getting this to work as a 64 bit HID. I think it will help other people
that are trying to do this.

I have never created a C++/CLI I assume I just need to make a C++ project
CLR Class Library.

Thanks,

Eric Renken
"Eric Renken" <Er********@newsgroup.nospamwrote in message
news:0D**********************************@microsof t.com...

Well I am working on trying to get some HID code to work on Windows XP,
Vista 32, and Vista 64. Working on XP and Vista 32 was easy as there are
some great resources on the web; however Vista 64 is a whole other
problem. The first problem was an easy one all the samples show this
structure:

[StructLayout(LayoutKind.Sequential)]
public struct SP_DEVICE_INTERFACE_DATA
{
public int cbSize;
public System.Guid InterfaceClassGuid;
public int Flags;
public IntPtr Reserved;
}

For calling the this method, SetupDiEnumDeviceInterfaces, in the
SetupAPI.dll; however most exaple has Reserved as just an Int and on a 64
bit platform that doesn't give you the correct size for an IntPtr. So all
my following problems are related to Vista 64.

Now that I have gotten past that part I am having problems with this
method, SetupDiGetDeviceInterfaceDetail, in SetupAPI.dll. When I call I
this method I get this error from GetLastError: "An attempt was made to
reference a token that does not exist."

Here is what my declartions look like:

[DllImport("setupapi.dll", CharSet = CharSet.Auto)]
static public extern bool SetupDiGetDeviceInterfaceDetail(IntPtr
DeviceInfoSet, ref SP_DEVICE_INTERFACE_DATA DeviceInterfaceData, IntPtr
DeviceInterfaceDetailData, int DeviceInterfaceDetailDataSize, ref int
RequiredSize, IntPtr DeviceInfoData);

[StructLayout(LayoutKind.Sequential)]
public struct SP_DEVICE_INTERFACE_DATA
{
public int cbSize;
public System.Guid InterfaceClassGuid;
public int Flags;
public IntPtr Reserved;
}

[StructLayout(LayoutKind.Sequential)]
public struct SP_DEVICE_INTERFACE_DETAIL_DATA
{
public int cbSize;
public string DevicePath;
}

The program makes 2 calls to SetupDiGetDeviceInterfaceDetail. The first
call it to get the size of the structure and the second returns a pointer
to the data. However on the frist run both picese return the same error
that I stated above. Here is what the first call looks like:

Success =
DeviceManagementApiDeclarations.SetupDiGetDeviceIn terfaceDetail(
DeviceInfoSet,
ref MyDeviceInterfaceData,
IntPtr.Zero, 0, ref BufferSize, IntPtr.Zero);

Here is the deifinition of the caribales used:
Scuesses = bool
DeviceInforSet = IntPtr
BufferSize = int

After the API call this data is called:

// Store the structure's size.
//MyDeviceInterfaceDetailData.cbSize =
MyDeviceInterfaceDetailData.ToString().Length;
MyDeviceInterfaceDetailData.cbSize =
Marshal.SizeOf(MyDeviceInterfaceDetailData);

// Allocate memory for the MyDeviceInterfaceDetailData Structure
using the returned buffer size.
IntPtr DetailDataBuffer = Marshal.AllocHGlobal(BufferSize);

// Store cbSize in the first 4 bytes of the array
Marshal.WriteInt32(DetailDataBuffer, 4 +
Marshal.SystemDefaultCharSize);
Debug.WriteLine("cbsize = " + MyDeviceInterfaceDetailData.cbSize);

I am pretty sure I would need to change the 4 + to 8 + for 64 bit, but I
am not positive.

Then I call SetupDiGetDeviceInterfaceDetail again:

Success =
DeviceManagementApiDeclarations.SetupDiGetDeviceIn terfaceDetail (
DeviceInfoSet,
ref MyDeviceInterfaceData,
DetailDataBuffer,
BufferSize,
ref BufferSize,
IntPtr.Zero);

After that call this code is run:

IntPtr pdevicePathName = IntPtr.Zero;
if ( Marshal.SizeOf( DeviceInfoSet ) == 4 )
pdevicePathName = new IntPtr(DetailDataBuffer.ToInt32() +
Marshal.SizeOf(DeviceInfoSet));
else
pdevicePathName = new IntPtr(DetailDataBuffer.ToInt64() +
Marshal.SizeOf(DeviceInfoSet));

// Get the String containing the devicePathName.
SingledevicePathName = Marshal.PtrToStringAuto(pdevicePathName);
devicePathName[MemberIndex] = SingledevicePathName;

I just added the code to increment these values based on the Size of
IntPtr.

The next time this code runs for the next HID device I get this error:
The supplied user buffer is not valid for the requested operation.

Any help would be greatly appriciated.

Thanks,

Eric Renken

[Eric Renken]

I do have a valid structure from SetupDiEnumDeviceInterfaces. Here is the
code that I call there:

Result =
DeviceManagementApiDeclarations.SetupDiEnumDeviceI nterfaces (
DeviceInfoSet,
0,
ref myGuid,
MemberIndex,
ref MyDeviceInterfaceData);

This returns correctly and I don't have any errors.

myGuid = System.Guid
MyDeviceInterfaceData = SP_DEVICE_INTERFACE_DATA

This code is not my own and is based on the code from there:
http://www.lvr.com/hidpage.htm.

Hope this extra code helps. FYI I don't call the code to get the Interface
details if Result= 0.

Thanks,

Eric Renken
"Willy Denoyette [MVP]" <wi*************@telenet.bewrote in message
news:76**********************************@microsof t.com...

"Eric Renken" <Er********@newsgroup.nospamwrote in message
news:0D**********************************@microsof t.com...

>Well I am working on trying to get some HID code to work on Windows XP,
Vista 32, and Vista 64. Working on XP and Vista 32 was easy as there are
some great resources on the web; however Vista 64 is a whole other
problem. The first problem was an easy one all the samples show this
structure:

[StructLayout(LayoutKind.Sequential)]
public struct SP_DEVICE_INTERFACE_DATA
{
public int cbSize;
public System.Guid InterfaceClassGuid;
public int Flags;
public IntPtr Reserved;
}

For calling the this method, SetupDiEnumDeviceInterfaces, in the
SetupAPI.dll; however most exaple has Reserved as just an Int and on a 64
bit platform that doesn't give you the correct size for an IntPtr. So
all my following problems are related to Vista 64.

Now that I have gotten past that part I am having problems with this
method, SetupDiGetDeviceInterfaceDetail, in SetupAPI.dll. When I call I
this method I get this error from GetLastError: "An attempt was made to
reference a token that does not exist."

Here is what my declartions look like:

[DllImport("setupapi.dll", CharSet = CharSet.Auto)]
static public extern bool SetupDiGetDeviceInterfaceDetail(IntPtr
DeviceInfoSet, ref SP_DEVICE_INTERFACE_DATA DeviceInterfaceData, IntPtr
DeviceInterfaceDetailData, int DeviceInterfaceDetailDataSize, ref int
RequiredSize, IntPtr DeviceInfoData);

[StructLayout(LayoutKind.Sequential)]
public struct SP_DEVICE_INTERFACE_DATA
{
public int cbSize;
public System.Guid InterfaceClassGuid;
public int Flags;
public IntPtr Reserved;
}

[StructLayout(LayoutKind.Sequential)]
public struct SP_DEVICE_INTERFACE_DETAIL_DATA
{
public int cbSize;
public string DevicePath;
}

The program makes 2 calls to SetupDiGetDeviceInterfaceDetail. The first
call it to get the size of the structure and the second returns a pointer
to the data. However on the frist run both picese return the same error
that I stated above. Here is what the first call looks like:

Success =
DeviceManagementApiDeclarations.SetupDiGetDeviceIn terfaceDetail(
DeviceInfoSet,
ref MyDeviceInterfaceData,
IntPtr.Zero, 0, ref BufferSize, IntPtr.Zero);

Here is the deifinition of the caribales used:
Scuesses = bool
DeviceInforSet = IntPtr
BufferSize = int

After the API call this data is called:

// Store the structure's size.
//MyDeviceInterfaceDetailData.cbSize =
MyDeviceInterfaceDetailData.ToString().Length;
MyDeviceInterfaceDetailData.cbSize =
Marshal.SizeOf(MyDeviceInterfaceDetailData);

// Allocate memory for the MyDeviceInterfaceDetailData Structure
using the returned buffer size.
IntPtr DetailDataBuffer = Marshal.AllocHGlobal(BufferSize);

// Store cbSize in the first 4 bytes of the array
Marshal.WriteInt32(DetailDataBuffer, 4 +
Marshal.SystemDefaultCharSize);
Debug.WriteLine("cbsize = " + MyDeviceInterfaceDetailData.cbSize);

I am pretty sure I would need to change the 4 + to 8 + for 64 bit, but I
am not positive.

Then I call SetupDiGetDeviceInterfaceDetail again:

Success =
DeviceManagementApiDeclarations.SetupDiGetDeviceI nterfaceDetail (
DeviceInfoSet,
ref MyDeviceInterfaceData,
DetailDataBuffer,
BufferSize,
ref BufferSize,
IntPtr.Zero);

After that call this code is run:

IntPtr pdevicePathName = IntPtr.Zero;
if ( Marshal.SizeOf( DeviceInfoSet ) == 4 )
pdevicePathName = new IntPtr(DetailDataBuffer.ToInt32() +
Marshal.SizeOf(DeviceInfoSet));
else
pdevicePathName = new IntPtr(DetailDataBuffer.ToInt64() +
Marshal.SizeOf(DeviceInfoSet));

// Get the String containing the devicePathName.
SingledevicePathName = Marshal.PtrToStringAuto(pdevicePathName);
devicePathName[MemberIndex] = SingledevicePathName;

I just added the code to increment these values based on the Size of
IntPtr.

The next time this code runs for the next HID device I get this error:
The supplied user buffer is not valid for the requested operation.

Any help would be greatly appriciated.

Thanks,

Eric Renken

It makes no sense to call SetupDiGetDeviceInterfaceDetail a second time
when the first call did NOT return ERROR_INSUFFICIENT_BUFFER.
Anyway, you need to pass a valid SP_DEVICE_INTERFACE_DATA when calling
SetupDiGetDeviceInterfaceDetail , that is you need to pass a structure
that is returned from a call to SetupDiEnumDeviceInterfaces ; it's not
clear whether you did call this API from your explanation.
So, please post some more code, especially what you did before calling
SetupDiGetDeviceInterfaceDetail is what we need.

Willy.

[Ben Voigt [C++ MVP]]

"Eric Renken" <Er********@newsgroup.nospamwrote in message
news:e6**************@TK2MSFTNGP06.phx.gbl...

Thanks everyone for the information. Walter, I did think about having
that DLL run as 32-bit only to make it work, but I am kind of interested
in getting this to work as a 64 bit HID. I think it will help other
people that are trying to do this.

I have never created a C++/CLI I assume I just need to make a C++ project
CLR Class Library.

Yes, and you'll almost certainly want these, taken from my C++/CLI project
with identical intention (the winsock2 is optional, but if you happen to
need it place it above windows.h):

#define INITGUID

#include <winsock2.h>

#include <windows.h>

#include <setupapi.h>

#include <cfgmgr32.h>

#include <devguid.h>

#include <regstr.h>

#include <assert.h>

#include <dbt.h>

With those, you no longer need *any* of your own declarations.

>
Thanks,

Eric Renken
"Eric Renken" <Er********@newsgroup.nospamwrote in message
news:0D**********************************@microsof t.com...

>Well I am working on trying to get some HID code to work on Windows XP,
Vista 32, and Vista 64. Working on XP and Vista 32 was easy as there are
some great resources on the web; however Vista 64 is a whole other
problem. The first problem was an easy one all the samples show this
structure:

[StructLayout(LayoutKind.Sequential)]
public struct SP_DEVICE_INTERFACE_DATA
{
public int cbSize;
public System.Guid InterfaceClassGuid;
public int Flags;
public IntPtr Reserved;
}

For calling the this method, SetupDiEnumDeviceInterfaces, in the
SetupAPI.dll; however most exaple has Reserved as just an Int and on a 64
bit platform that doesn't give you the correct size for an IntPtr. So
all my following problems are related to Vista 64.

Now that I have gotten past that part I am having problems with this
method, SetupDiGetDeviceInterfaceDetail, in SetupAPI.dll. When I call I
this method I get this error from GetLastError: "An attempt was made to
reference a token that does not exist."

Here is what my declartions look like:

[DllImport("setupapi.dll", CharSet = CharSet.Auto)]
static public extern bool SetupDiGetDeviceInterfaceDetail(IntPtr
DeviceInfoSet, ref SP_DEVICE_INTERFACE_DATA DeviceInterfaceData, IntPtr
DeviceInterfaceDetailData, int DeviceInterfaceDetailDataSize, ref int
RequiredSize, IntPtr DeviceInfoData);

[StructLayout(LayoutKind.Sequential)]
public struct SP_DEVICE_INTERFACE_DATA
{
public int cbSize;
public System.Guid InterfaceClassGuid;
public int Flags;
public IntPtr Reserved;
}

[StructLayout(LayoutKind.Sequential)]
public struct SP_DEVICE_INTERFACE_DETAIL_DATA
{
public int cbSize;
public string DevicePath;
}

The program makes 2 calls to SetupDiGetDeviceInterfaceDetail. The first
call it to get the size of the structure and the second returns a pointer
to the data. However on the frist run both picese return the same error
that I stated above. Here is what the first call looks like:

Success =
DeviceManagementApiDeclarations.SetupDiGetDeviceIn terfaceDetail(
DeviceInfoSet,
ref MyDeviceInterfaceData,
IntPtr.Zero, 0, ref BufferSize, IntPtr.Zero);

Here is the deifinition of the caribales used:
Scuesses = bool
DeviceInforSet = IntPtr
BufferSize = int

After the API call this data is called:

// Store the structure's size.
//MyDeviceInterfaceDetailData.cbSize =
MyDeviceInterfaceDetailData.ToString().Length;
MyDeviceInterfaceDetailData.cbSize =
Marshal.SizeOf(MyDeviceInterfaceDetailData);

// Allocate memory for the MyDeviceInterfaceDetailData Structure
using the returned buffer size.
IntPtr DetailDataBuffer = Marshal.AllocHGlobal(BufferSize);

// Store cbSize in the first 4 bytes of the array
Marshal.WriteInt32(DetailDataBuffer, 4 +
Marshal.SystemDefaultCharSize);
Debug.WriteLine("cbsize = " + MyDeviceInterfaceDetailData.cbSize);

I am pretty sure I would need to change the 4 + to 8 + for 64 bit, but I
am not positive.

Then I call SetupDiGetDeviceInterfaceDetail again:

Success =
DeviceManagementApiDeclarations.SetupDiGetDeviceI nterfaceDetail (
DeviceInfoSet,
ref MyDeviceInterfaceData,
DetailDataBuffer,
BufferSize,
ref BufferSize,
IntPtr.Zero);

After that call this code is run:

IntPtr pdevicePathName = IntPtr.Zero;
if ( Marshal.SizeOf( DeviceInfoSet ) == 4 )
pdevicePathName = new IntPtr(DetailDataBuffer.ToInt32() +
Marshal.SizeOf(DeviceInfoSet));
else
pdevicePathName = new IntPtr(DetailDataBuffer.ToInt64() +
Marshal.SizeOf(DeviceInfoSet));

// Get the String containing the devicePathName.
SingledevicePathName = Marshal.PtrToStringAuto(pdevicePathName);
devicePathName[MemberIndex] = SingledevicePathName;

I just added the code to increment these values based on the Size of
IntPtr.

The next time this code runs for the next HID device I get this error:
The supplied user buffer is not valid for the requested operation.

Any help would be greatly appriciated.

Thanks,

Eric Renken

[Eric Renken]

Well the C++/CLI is a great idea, but I don't have time to figure out how to
write it. I'm not that much of a C++ programmer. I don't want to put this
entire application in 32 bit format just because 1 DLL is having problems.

This code should work it is just a size of some of the objects. Once I get
this code working I should pretty much be home free, once I can get the
WaitForSingleObject section working on the WriteFile.

We would probably be interested in hiring someone to consult with us to get
this working in Vista 64.

Thanks,

Eric Renken
"Walter Wang [MSFT]" <wa****@online.microsoft.comwrote in message
news:WI**************@TK2MSFTNGHUB02.phx.gbl...

Hi Eric,

I agree with Ben here that writing the code in C++/CLI will be easier and
cleaner.

Setupapi.dll also has a 32-bit version at %windir%\syswow64. If 32-bit
interop is already working fine, why not just compile your C# program in
32-bit so that it calls into 32-bit setupapi.dll?
Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no
rights.

[Walter Wang [MSFT]]

Hi Eric,

I'm not familiar with the HID related code so currently I'm not able to
reproduce the issue you described. If you have a working reproducible
project at hand, that would be great.

Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Willy Denoyette [MVP]]

"Eric Renken" <Er********@newsgroup.nospamwrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl...

>I do have a valid structure from SetupDiEnumDeviceInterfaces. Here is the
code that I call there:

Result =
DeviceManagementApiDeclarations.SetupDiEnumDeviceI nterfaces (
DeviceInfoSet,
0,
ref myGuid,
MemberIndex,
ref MyDeviceInterfaceData);

This returns correctly and I don't have any errors.

myGuid = System.Guid
MyDeviceInterfaceData = SP_DEVICE_INTERFACE_DATA

This code is not my own and is based on the code from there:
http://www.lvr.com/hidpage.htm.

Hope this extra code helps. FYI I don't call the code to get the
Interface details if Result= 0.

Eric, seems like my latest reply on this got lost somewhere. What you should
do is take care of the padding and alignment of your structures. To do this
simply set the Pack argument in your SP_DEVICE_INTERFACE_DETAIL_DATA
StructLayout attribute to 4, like this.
[StructLayout(LayoutKind.Sequential), Pack=4]

Willy.

[Walter Wang [MSFT]]

Hi Eric,

Thanks for the code.

First issue:

If you're using Marshal.GetLastError, you should include "SetLastError =
true" in your DllImportAttribute; otherwise the last error code isn't
correct. If you add this assertion after first call to
SetupDiGetDeviceInterfaceDetail:

Debug.Assert(error == ERROR_INSUFFICIENT_BUFFER);

The assertion will fail since the reported error code isn't correct.

Next, setupapi.h uses pack(8) for x64 and pack(1) for x86:

#ifdef _WIN64
#include <pshpack8.h // Assume 8-byte (64-bit) packing throughout
#else
#include <pshpack1.h // Assume byte packing throughout (32-bit processor)
#endif

So you will need to declare your struct accordingly:

[StructLayout(LayoutKind.Sequential, Pack=8)]

This also affects the size of SP_DEVICE_INTERFACE_DETAIL_DATA: on x64, the
size will be 8, on x86, the size will be 6. Therefore, after you get the
size and allocated the buffer, use this code on x64:

Marshal.WriterInt32(detailDataBuffer, 8)

I don't think you will be able to use "Any CPU" configuration to make the
code run on both x86 and x64, you may have to use conditional compilation
to compile different assembly.

Hope this helps.
Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Eric Renken]

Thanks for the tip on SetLastError and the
Marshal.WriteInt32(detailDataBuffer, 8).

I changed this line of code:
Marshal.WriteInt32(detailDataBuffer, Marshal.SizeOf(deviceInformationSet) +
Marshal.SystemDefaultCharSize);

To this:
if (Marshal.SizeOf(typeof(IntPtr)) == 4)
Marshal.WriteInt32(detailDataBuffer, Marshal.SizeOf(deviceInformationSet) +
Marshal.SystemDefaultCharSize);
else
Marshal.WriteInt32(detailDataBuffer, Marshal.SizeOf(typeof(IntPtr)));

And now this part works on x86 and x64 machines. I don't even use the
SP_DEVICE_INTERFACE_DETAIL_DATA structure so I removed it from the code.
Now on to the next steps on loading the HID device that I want.

I'll be back when I hit the next problem.

Thanks for all the help.

Eric Renken


"Walter Wang [MSFT]" <wa****@online.microsoft.comwrote in message
news:RW**************@TK2MSFTNGHUB02.phx.gbl...

Hi Eric,

Thanks for the code.

First issue:

If you're using Marshal.GetLastError, you should include "SetLastError =
true" in your DllImportAttribute; otherwise the last error code isn't
correct. If you add this assertion after first call to
SetupDiGetDeviceInterfaceDetail:

Debug.Assert(error == ERROR_INSUFFICIENT_BUFFER);

The assertion will fail since the reported error code isn't correct.

Next, setupapi.h uses pack(8) for x64 and pack(1) for x86:

#ifdef _WIN64
#include <pshpack8.h // Assume 8-byte (64-bit) packing throughout
#else
#include <pshpack1.h // Assume byte packing throughout (32-bit
processor)
#endif

So you will need to declare your struct accordingly:

[StructLayout(LayoutKind.Sequential, Pack=8)]

This also affects the size of SP_DEVICE_INTERFACE_DETAIL_DATA: on x64, the
size will be 8, on x86, the size will be 6. Therefore, after you get the
size and allocated the buffer, use this code on x64:

Marshal.WriterInt32(detailDataBuffer, 8)

I don't think you will be able to use "Any CPU" configuration to make the
code run on both x86 and x64, you may have to use conditional compilation
to compile different assembly.

Hope this helps.
Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no
rights.

[Walter Wang [MSFT]]

Hi Eric,

I'm sorry but I cannot clearly tell you what might be wrong since I'm not
clear about following points and the code is not complete yet to reproduce
the issue you mentioned.

1) Is the issue also x64 only?
2) How can I test the code?

If by any chance that you could run the equivalent code in C++, I would
recommend that you test some core function in C++ first, interacting with
hardware is much easier if you're using C/C++.
Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Eric Renken]

Yes this is x64 only. I can send you the entire project but without the
hardware device I am using I am not sure how you could reproduce. Right now
I am using a prototype piece of hardware. That said with a couple code
change you should be able to easily modify my code to work with any HID
device. Let me know if you want the project.

Eric Renken
"Walter Wang [MSFT]" <wa****@online.microsoft.comwrote in message
news:3%****************@TK2MSFTNGHUB02.phx.gbl...

Hi Eric,

I'm sorry but I cannot clearly tell you what might be wrong since I'm not
clear about following points and the code is not complete yet to reproduce
the issue you mentioned.

1) Is the issue also x64 only?
2) How can I test the code?

If by any chance that you could run the equivalent code in C++, I would
recommend that you test some core function in C++ first, interacting with
hardware is much easier if you're using C/C++.
Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no
rights.

[Walter Wang [MSFT]]

Hi Eric,

Please feel free to send me the project. Thanks.
Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Eric Renken]

Can I email it to you? There is some stuff I woul prefer not to release to
the world.

Thanks,

Eric Renken

"Walter Wang [MSFT]" <wa****@online.microsoft.comwrote in message
news:xb**************@TK2MSFTNGHUB02.phx.gbl...

Hi Eric,

Please feel free to send me the project. Thanks.
Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no
rights.

[Walter Wang [MSFT]]

Hi Eric,

Sorry for not being very clear in my last reply. I meant to send me via
email, my email address is in my signature. Thanks.
Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Eric Renken]

OK, I finally have it reading and writing on x86 and x64. Now to work on an
OVERLAPPED read, so you may be hearing from me again. Just so everyone
knows the key to getting it to work on x64 was this:

fixed (byte* p = buffer)
{
result = FileIOAPIDeclarations.ReadFile(_hidHandle, p, buffer.Length,
&bytesRead, IntPtr.Zero);
Debug.WriteLine(MyDebugging.ResultOfAPICall("ReadF ile"));
}

fixed (byte* p = buffer)
{
FileIOAPIDeclarations.WriteFile(_hidHandle, p, buffer.Length,
&bytesWritten, IntPtr.Zero);
Debug.WriteLine(MyDebugging.ResultOfAPICall("Write File"));
}

The fixed keyword was the key. Otherwise all that was in your buffer was an
array of 0.

I also had to change the WriteFile and ReadFile declarations to handle this:

[DllImport("kernel32.dll", SetLastError = true)]
static public extern unsafe int ReadFile(IntPtr hFile, void* lpBuffer, int
nNumberOfBytesToRead, int* lpNumberOfBytesRead, IntPtr lpOverlapped);
[DllImport("kernel32.dll", SetLastError = true)]
static public extern unsafe int WriteFile(IntPtr hFile, void* lpBuffer,
int nNumberOfBytesToWrite, int* lpNumberOfBytesWritten, IntPtr
lpOverlapped);

Well I hope this helps someone else.

Eric Renken

"Eric Renken" <Er********@newsgroup.nospamwrote in message
news:0D**********************************@microsof t.com...

Well I am working on trying to get some HID code to work on Windows XP,
Vista 32, and Vista 64. Working on XP and Vista 32 was easy as there are
some great resources on the web; however Vista 64 is a whole other
problem. The first problem was an easy one all the samples show this
structure:

[StructLayout(LayoutKind.Sequential)]
public struct SP_DEVICE_INTERFACE_DATA
{
public int cbSize;
public System.Guid InterfaceClassGuid;
public int Flags;
public IntPtr Reserved;
}

For calling the this method, SetupDiEnumDeviceInterfaces, in the
SetupAPI.dll; however most exaple has Reserved as just an Int and on a 64
bit platform that doesn't give you the correct size for an IntPtr. So all
my following problems are related to Vista 64.

Now that I have gotten past that part I am having problems with this
method, SetupDiGetDeviceInterfaceDetail, in SetupAPI.dll. When I call I
this method I get this error from GetLastError: "An attempt was made to
reference a token that does not exist."

Here is what my declartions look like:

[DllImport("setupapi.dll", CharSet = CharSet.Auto)]
static public extern bool SetupDiGetDeviceInterfaceDetail(IntPtr
DeviceInfoSet, ref SP_DEVICE_INTERFACE_DATA DeviceInterfaceData, IntPtr
DeviceInterfaceDetailData, int DeviceInterfaceDetailDataSize, ref int
RequiredSize, IntPtr DeviceInfoData);

[StructLayout(LayoutKind.Sequential)]
public struct SP_DEVICE_INTERFACE_DATA
{
public int cbSize;
public System.Guid InterfaceClassGuid;
public int Flags;
public IntPtr Reserved;
}

[StructLayout(LayoutKind.Sequential)]
public struct SP_DEVICE_INTERFACE_DETAIL_DATA
{
public int cbSize;
public string DevicePath;
}

The program makes 2 calls to SetupDiGetDeviceInterfaceDetail. The first
call it to get the size of the structure and the second returns a pointer
to the data. However on the frist run both picese return the same error
that I stated above. Here is what the first call looks like:

Success =
DeviceManagementApiDeclarations.SetupDiGetDeviceIn terfaceDetail(
DeviceInfoSet,
ref MyDeviceInterfaceData,
IntPtr.Zero, 0, ref BufferSize, IntPtr.Zero);

Here is the deifinition of the caribales used:
Scuesses = bool
DeviceInforSet = IntPtr
BufferSize = int

After the API call this data is called:

// Store the structure's size.
//MyDeviceInterfaceDetailData.cbSize =
MyDeviceInterfaceDetailData.ToString().Length;
MyDeviceInterfaceDetailData.cbSize =
Marshal.SizeOf(MyDeviceInterfaceDetailData);

// Allocate memory for the MyDeviceInterfaceDetailData Structure
using the returned buffer size.
IntPtr DetailDataBuffer = Marshal.AllocHGlobal(BufferSize);

// Store cbSize in the first 4 bytes of the array
Marshal.WriteInt32(DetailDataBuffer, 4 +
Marshal.SystemDefaultCharSize);
Debug.WriteLine("cbsize = " + MyDeviceInterfaceDetailData.cbSize);

I am pretty sure I would need to change the 4 + to 8 + for 64 bit, but I
am not positive.

Then I call SetupDiGetDeviceInterfaceDetail again:

Success =
DeviceManagementApiDeclarations.SetupDiGetDeviceIn terfaceDetail (
DeviceInfoSet,
ref MyDeviceInterfaceData,
DetailDataBuffer,
BufferSize,
ref BufferSize,
IntPtr.Zero);

After that call this code is run:

IntPtr pdevicePathName = IntPtr.Zero;
if ( Marshal.SizeOf( DeviceInfoSet ) == 4 )
pdevicePathName = new IntPtr(DetailDataBuffer.ToInt32() +
Marshal.SizeOf(DeviceInfoSet));
else
pdevicePathName = new IntPtr(DetailDataBuffer.ToInt64() +
Marshal.SizeOf(DeviceInfoSet));

// Get the String containing the devicePathName.
SingledevicePathName = Marshal.PtrToStringAuto(pdevicePathName);
devicePathName[MemberIndex] = SingledevicePathName;

I just added the code to increment these values based on the Size of
IntPtr.

The next time this code runs for the next HID device I get this error:
The supplied user buffer is not valid for the requested operation.

Any help would be greatly appriciated.

Thanks,

Eric Renken