There is additional info in this thread, but since it's a lot of pages,.. succes with that
Moderator: Moderators
Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39).
Anumunrama wrote:I hope someone will write an insallation guide fpr x64 vista
RBC9 Driver - TEST x64 build.zip 2009-01-14
bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKSbrandon9271 wrote:I just installed RCB9 and it tells me "spacePilot not found"not sure why it does this but all my other apps are working fine. The only thing I can guess is that its because my SpacePilot is brand HP..
Was really looking forward to playing some RTS with this thing..
kabesc wrote:Hello to all,
I have read most parts of this thread, since I also want to use my Space Navigator to work as a joystick and/or mouse. I am using Vista x64 - seems to be the reason, why the solution provided and discussed here poses some problems.
Recently I found out, that one can access the Space Navigator (and possibly all of the other 3d mices?!) via DirectInput. So, I am wondering if it wouldn't be easier to just write a small app, that continuously reads the axes and buttons data and transforms it to mouse movements/mouse clicks (by Windows API calls)?!
I guess, someone else tried this before - so I would be happy if I get some response, why this would work/not work.
Regard,
Karl
Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)
Return to Windows Discussion Forum
Users browsing this forum: No registered users and 3 guests