Author Topic: HID Device in Windows 7  (Read 16860 times)

Carl

  • Member
  • ***
  • Posts: 2
HID Device in Windows 7
« on: July 27, 2010, 10:29:25 am »
I used the HID class to implement a device for use around my lab several years ago.  It has always worked well until I installed it on a Windows 7 64-bit machine.  My application runs on the windows machine and the HID device appears to connect fine and shows up in the Device Manager but the application does not seem to be able to connect to the HID device.   Does anyone know what may have changed in Windows 7 to cause my application to not see the HID device?

Jan Axelson

  • Administrator
  • Frequent Contributor
  • *****
  • Posts: 3033
    • Lakeview Research
Re: HID Device in Windows 7
« Reply #1 on: July 27, 2010, 11:28:25 am »
32-bit applications sometimes need some mods to be compatible with 64 bits.

Here is one link:

http://msdn.microsoft.com/en-us/library/aa384214%28VS.85%29.aspx

Also see my HID applications on my HID page:

www.Lvr.com/hidpage.htm

With advice from several helpful folks, I modified the apps for 64 bits though I haven't tested them myself on 64 bits.

Jan

Carl

  • Member
  • ***
  • Posts: 2
Re: HID Device in Windows 7
« Reply #2 on: September 09, 2010, 05:41:52 pm »
In case anyone else runs into this, the key for me was in the Visual Studio project options.  I had to build for x86 rather than Any CPU.  Any CPU lets it run natively on the current CPU, so 64-bit on a 64-bit CPU.  x86 target tells it the project is intended to run only as a 32-bit process.  This fixed my problem connecting to my USB HID device on 64-bit, Windows 7 processors. 

The link below describes this.

http://visualstudiohacks.com/articles/visual-studio-net-platform-target-explained/

Good luck.

jcddcjjcd

  • Member
  • ***
  • Posts: 14
Re: HID Device in Windows 7
« Reply #3 on: September 19, 2010, 11:55:12 pm »
I commented at http://www.lvr.com/forum/index.php?topic=72.0 that the updated generic_hid works well on Window 7 64bit.
Anyone who wants it to work will need to update to the newer implementation.
Regards,
John.