A7N266VM - USB/HID nightmare

  • Thread starter Thread starter Bill Fredette
  • Start date Start date
B

Bill Fredette

Hello, all. I am losing hope on this one, but here goes...

I have a powered tripod head (TrackerPod by Eagletron)for my
camcorder that will allow it to be remotely controlled via the
Internet. It connects to the 'puter with a USB cable, but the
manufacturer tells me it should be recognized by Windows as a human
interface device, and not a USB device.

Unfortunately, every time I plug it in, XP detects it as a USB device,
attempts to install it, and winds up listing it in the device manager
as an unknown USB device.

Now you may be asking why I am posting in this group. Well... I have
plugged this into another machine that has a Tyan motherboard and it
worked immediately. It will not, however, work on either of my two
machines that have the A7N266-VM motherboards. Both of those are using
bios version 1007, which as far as I can tell is the latest available.

I have searched far and wide for solutions, but cannot seem to find
any. I unpacked hidserv.dll, mouhid.sys and mouclass.sys from the
cabinet file on the XP install, and now the human interface device
service is running on my machine. However, I do not have a "human
interface device" entry in the device manager.

So does anyone have any idea whether this might in fact be a
compatibility problem with the A7N266 for some weird reason?

Or, does anyone know a way to force XP to recognize this thing as an
HID? Is there any way to stop it from being installed as a
non-functional USB device? I'm about ready to throw in the towel and
return the unit because I can't see how to get it working on my
machine, and the manufacturer doesn't have any ideas.

I would REALLY appreciate any suggestions you might offer. Thanks in
advance.
 
Bill Fredette said:
Hello, all. I am losing hope on this one, but here goes...

I have a powered tripod head (TrackerPod by Eagletron)for my
camcorder that will allow it to be remotely controlled via the
Internet. It connects to the 'puter with a USB cable, but the
manufacturer tells me it should be recognized by Windows as a human
interface device, and not a USB device.

Unfortunately, every time I plug it in, XP detects it as a USB device,
attempts to install it, and winds up listing it in the device manager
as an unknown USB device.

Now you may be asking why I am posting in this group. Well... I have
plugged this into another machine that has a Tyan motherboard and it
worked immediately. It will not, however, work on either of my two
machines that have the A7N266-VM motherboards. Both of those are using
bios version 1007, which as far as I can tell is the latest available.

I have searched far and wide for solutions, but cannot seem to find
any. I unpacked hidserv.dll, mouhid.sys and mouclass.sys from the
cabinet file on the XP install, and now the human interface device
service is running on my machine. However, I do not have a "human
interface device" entry in the device manager.

So does anyone have any idea whether this might in fact be a
compatibility problem with the A7N266 for some weird reason?

Or, does anyone know a way to force XP to recognize this thing as an
HID? Is there any way to stop it from being installed as a
non-functional USB device? I'm about ready to throw in the towel and
return the unit because I can't see how to get it working on my
machine, and the manufacturer doesn't have any ideas.

I would REALLY appreciate any suggestions you might offer. Thanks in
advance.
Click to expand...

I tried the usb.org website, and there is a bit of stuff on HID
here:

http://www.usb.org/developers/hidpage/

So, I guess HID is low speed input devices, like keyboards and mice.

Maybe if the BIOS is getting confused somehow, by what it is getting
from that device, maybe you could buy a cheap USB PCI card and plug
that in. Then, try connecting your HID device to the PCI card.

I just don't understand what could be going on, unless it has
something to do with the "legacy support" setting in the BIOS.
Other than that, it would have to be a higher layer software
problem, because lower layers probably don't care what is connected
and leave the parsing of info from the device(s) to the OS.

Paul
 
Thanks for the suggestions. I'll check out that site and poke around
one more time in my bios.

Bill
 
Back
Top