search

j3p0 / chatpad-super-driver

Automatically exported from code.google.com/p/chatpad-super-driver
0 stars 0 forks source link

IOCTL failing four times, error initializing chatpad #58

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Unsuccessfully install chatpad on win7 64 before rebooting with the correct 
options.
2. Successful install.
3. Run chatpad_control_amd64.exe

What is the expected output? What do you see instead?
I don't know the expected output but I imagine a working keypad or some such. 
Instead I see this:

*****
Chatpad control utility version 0.1a started.
*****
Please wait...

Control utility started.
Opening chatpad filter driver.
Successfully opened chatpad filter driver.
Successfully connected to XBox 360 controller.
Opening connection to virtual keyboard device.
Successfully opened connection to virtual keyboard device.
Successfully connected to the virtual keyboard device.
Opening connection to virtual mouse device.
Successfully opened connection to virtual mouse device.
Successfully connected to the virtual mouse device.
Microsoft initialization has been finished, so we can init the chatpad now.
IOCTL failed, lastError == 31
IOCTL failed, lastError == 31
IOCTL failed, lastError == 31
IOCTL failed, lastError == 31
Control response data received:  0x00 0x00
Error initializing chatpad.
Closing connection to virtual keyboard device.
Closing connection to virtual mouse device.
Closing chatpad filter driver.
Done.  The exit status is -1.

What version of the product are you using? On what operating system?
Where would I find the version info? It's neither in the README or the LICENSE, 
so my best guess is 0.1a. I'm in win7 home 64bit.

Please provide any additional information below.
It might be that the previous installs weren't completely removed or 
overwritten. Also, I've been using JoyToKey for a while now...is there any way 
to maintain the original xbox360 controller drivers along with the keypad 
drivers, so that I can use both optimally? Perhaps the new controller drivers 
will prove just as functional though, once I get them working.

Original issue reported on code.google.com by ian.a.mc...@gmail.com on 2 Nov 2013 at 7:00

GoogleCodeExporter commented 8 years ago 
https://code.google.com/p/chatpad-super-driver/issues/detail?id=2#c35
this worked for me

Original comment by ian.a.mc...@gmail.com on 2 Nov 2013 at 7:21