Chatpad control utility crashes (with error 121)

GoogleCodeExporter commented 9 years ago

For some people, the chatpad control utility quits very shortly after 
displaying the comand prompt.  If one runs it from the command line, an error 
may be shown near the bottom of the output messages that says "IOCTL failed, 
lastError == 121".

If you seem to be experiencing this issue and you are not sure how to run the 
control utility from the command prompt, please let me know and I can provide 
additional instructions.

If this issue happens to you, please report whether you are using a "Made for 
Windows" 360 controller, or a normal 360 controller that would go with an XBox 
360 game console.

Original issue reported on code.google.com by gtsche...@gmail.com on 29 Dec 2010 at 10:16

GoogleCodeExporter commented 9 years ago

I am running the white wired XBOX 360 controller with the new chatpad.  I am 
getting something similar, but the error is reported as "31", not "121."

Original comment by TranceW...@gmail.com on 5 Jan 2011 at 11:38

GoogleCodeExporter commented 9 years ago

TranceWarp (and others), I think the 121 issue is HOPEFULLY fixed.  To verify 
some test code I have, use one of the following links.

If you have a 64-bit system, try copying this control .exe into the directory 
that has chatpad_config.txt, and run it:

[http://code.google.com/p/chatpad-super-driver/downloads/detail?name=win7_amd64_
chatpad_control_test3.exe]

If you have a 32-bit system, try copying this control .exe into the directory 
that has chatpad_config.txt, and run it:
[http://code.google.com/p/chatpad-super-driver/downloads/detail?name=winxp_i386_
chatpad_control_test4.exe]

Let me know how it works out.

Original comment by gtsche...@gmail.com on 5 Jan 2011 at 11:50

GoogleCodeExporter commented 9 years ago

Still getting the error here.  Here's how the command window reads:

*****
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.

Original comment by TranceW...@gmail.com on 6 Jan 2011 at 12:57

GoogleCodeExporter commented 9 years ago

TranceWarp, if that is the log from the newer test programs, please email me 
(gtschemer at gmail dot com) with the command line output from the original 
chatpad control utility .exe, from the featured zips.  I would like to see if 
there is any difference between the two.  I would also like to ask for your 
help in getting some testing information if you have time for it.  Thanks.

Original comment by gtsche...@gmail.com on 6 Jan 2011 at 3:04

GoogleCodeExporter commented 9 years ago

That is the command line output.  I ran both for comparison:

C:\Users\TranceWarp\Downloads\Chatpad Drivers>chatpad_control_amd64.exe

*****
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.

C:\Users\TranceWarp\Downloads\Chatpad 
Drivers>win7_amd64_chatpad_control_test3.exe

*****
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.

They both act exactly the same.

Original comment by TranceW...@gmail.com on 6 Jan 2011 at 9:47

GoogleCodeExporter commented 9 years ago

Oh - about testing info...I'd be more than happy to do so.  I do bug reports 
for Wololo's Wagic game for PSP, so it's cool.

Original comment by TranceW...@gmail.com on 6 Jan 2011 at 9:58

GoogleCodeExporter commented 9 years ago

Thanks for the information.  You may have an unusual controller hardware 
version -- I have only seen two versions so far.  Is there an email address 
where I can send you a USB device info utility to get the hardware version?  
Also, could you post/email me exactly which controller you have (XBox 360, or 
"made for Windows") as well as the serial/model numbers on the back of the 
controller and chatpad?  At the mp3car forums we have been collecting some of 
these to try to see if there is a correlation.

Original comment by gtsche...@gmail.com on 6 Jan 2011 at 10:02

GoogleCodeExporter commented 9 years ago

Chatpad Info: Top number is X-852479-001.  Bottom number is 001379103512.

No such luck with the main controller.  I bought it used and the stickers were 
removed.

Original comment by TranceW...@gmail.com on 6 Jan 2011 at 10:30

GoogleCodeExporter commented 9 years ago

Hey Dude,
I've tried the Drivers on my Notebook, XP-32bit.
I got exactly the same output as TranceWarp.

Controller: Made for Windows, wired version but I purchased it for my Computer 
short time, after the Xbox360 was released.

Chatpad: Was bought 2 weeks after the Controller hast arrived.
Maybe I can help to ;-)

Original comment by mnolde...@googlemail.com on 9 Jan 2011 at 2:50

GoogleCodeExporter commented 9 years ago

@mnolde: check to see if the pad is working in games, I just found out that 
mine does not with the driver installed despite the controller "appearing" to 
be working.

Seeing as I'm not the only one, I'll check the hardware ID now.  I've been 
working from Ubuntu for the past couple of days, so I haven't checked my e-mail.

Original comment by TranceW...@gmail.com on 17 Jan 2011 at 5:15

GoogleCodeExporter commented 9 years ago

Here's my data from USBVIEW...

Device Descriptor:
bcdUSB:             0x0200
bDeviceClass:         0xFF
bDeviceSubClass:      0xFF
bDeviceProtocol:      0xFF
bMaxPacketSize0:      0x08 (8)
idVendor:           0x045E (Microsoft Corporation)
idProduct:          0x028E
bcdDevice:          0x0110
iManufacturer:        0x01
iProduct:             0x02
iSerialNumber:        0x03
bNumConfigurations:   0x01

ConnectionStatus: DeviceConnected
Current Config Value: 0x01
Device Bus Speed:     Full
Device Address:       0x07
Open Pipes:              7

Endpoint Descriptor:
bEndpointAddress:     0x81  IN
Transfer Type:   Interrupt
wMaxPacketSize:     0x0020 (32)
bInterval:            0x04

Endpoint Descriptor:
bEndpointAddress:     0x02  OUT
Transfer Type:   Interrupt
wMaxPacketSize:     0x0020 (32)
bInterval:            0x08

Endpoint Descriptor:
bEndpointAddress:     0x83  IN
Transfer Type:   Interrupt
wMaxPacketSize:     0x0020 (32)
bInterval:            0x02

Endpoint Descriptor:
bEndpointAddress:     0x04  OUT
Transfer Type:   Interrupt
wMaxPacketSize:     0x0020 (32)
bInterval:            0x04

Endpoint Descriptor:
bEndpointAddress:     0x85  IN
Transfer Type:   Interrupt
wMaxPacketSize:     0x0020 (32)
bInterval:            0x40

Endpoint Descriptor:
bEndpointAddress:     0x05  OUT
Transfer Type:   Interrupt
wMaxPacketSize:     0x0020 (32)
bInterval:            0x10

Endpoint Descriptor:
bEndpointAddress:     0x86  IN
Transfer Type:   Interrupt
wMaxPacketSize:     0x0020 (32)
bInterval:            0x10

Original comment by TranceW...@gmail.com on 17 Jan 2011 at 5:23

GoogleCodeExporter commented 9 years ago

Thanks for the update.  The bcdDevice version looks fine and should work with 
the newer test utility, but I did not yet compare the rest of the information.  
I hope to have something improved to try in the next week or so.  :(

Original comment by gtsche...@gmail.com on 17 Jan 2011 at 5:52

GoogleCodeExporter commented 9 years ago

I forgot to mention that the driver is working for mnold... who also reported 
this issue, but only under Windows 7.  I have not yet gotten a working binary 
for him under Windows XP.  I am not sure why a couple of people still have this 
issue.

Original comment by gtsche...@gmail.com on 17 Jan 2011 at 5:55

GoogleCodeExporter commented 9 years ago

Hey TranceWarp, as I mentioned before I got the same error code.

But now it works fine for me, also under my XP Version.

1. I pressed guide button and I've looked for new drivers, after this test
2. I used the test4.exe 
=> Now it works stable.

Original comment by mnolde...@googlemail.com on 17 Jan 2011 at 6:22

GoogleCodeExporter commented 9 years ago

The chatpad is working great now by using test 4!
I'm talking to you via the chatpad as we speak.

Original comment by TranceW...@gmail.com on 17 Jan 2011 at 9:02

GoogleCodeExporter commented 9 years ago

Thanks, Trance, I'm glad to hear it.  Did you have to update the drivers, using 
the guide button, like mnolde... mentioned?

Original comment by gtsche...@gmail.com on 18 Jan 2011 at 4:08

GoogleCodeExporter commented 9 years ago

Nope.  Just ran the new exe.

Original comment by TranceW...@gmail.com on 19 Jan 2011 at 1:21

GoogleCodeExporter commented 9 years ago

Im having the same issue as Trance, however, none of the control utility test 
files work for me. When I installed the driver, it gave me a message that said 
"Windows requires signatures" or something for the driver, even though I had 
booted into the "disable signature enforcement" mode. Could that be the problem 
and I should try re-installing? Or, is there something different going wrong 
here.

Command line output for chatpad_control_amd64:

*****
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.

The CMD output for all the control test files is all the same. Help would be 
much appreciated.

Original comment by KrostyCl...@gmail.com on 27 Jan 2011 at 5:13

GoogleCodeExporter commented 9 years ago

Krosty, I don't think you should get a message about requiring signatures.  
However, it looks like the driver still installed enough that the utility could 
connect to it.  Can you try rebooting, plugging in the controller from a fresh 
start, and running the test4.exe executable?  See if you still get the four 31 
errors in a row.  Three 31 errors is normal, but not four.

You could try reinstalling, but right now you will need to manually uninstall 
the virtual keyboard and mouse devices (four devices total?)...there should be 
some information in the troubleshooting section and/or the mp3car forum.  Sorry 
for the lack of a detailed response -- I'm unfortunately quite busy this 
weekend.

Original comment by gtsche...@gmail.com on 28 Jan 2011 at 6:20

GoogleCodeExporter commented 9 years ago

Mine doesn't crash per se, but it does close pretty much RIGHT after I open the 
control executable. The text when ran on a cmd line window is as follows:

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

Control utility started.
Opening chatpad filter driver.
Couldn't open chatpad filter: 2
Failed to open connection to XBox 360 controller.
Done. The exit status is -1.

I'm kinda new to this driver modification (not new to dos at least XP) so any 
and all help would be appreciated. I followed the same steps as I did for my 
laptop, which worked perfectly on it, not even a fuss, but installing it on my 
PC is giving me this. My laptop is a 64x Win7 and my PC is a 64x WinVista OS. 
Let me know if there is any information I missed to asses the problem.

Original comment by turpinat...@gmail.com on 2 Feb 2011 at 9:36

GoogleCodeExporter commented 9 years ago

If it closes right after open the executable.
You have to open the exe-file with the normal Comand Line window, I don't how 
it's called in english.

you can open it with "cmd"
Browse to the file location and start it, now the window won't close.
And you can write us the error code. :-)

P.S. sorry for my slacking english.. :-D

Original comment by mnolde...@googlemail.com on 3 Feb 2011 at 1:19

GoogleCodeExporter commented 9 years ago

Hi!

Firstly, thanks for your efforts!
I tried your driver with Xbox 360 controller that has a chatpad connected to 
it. I've followed the instructions and got the same error as in comment #7. 
Added to that, the light on the controller is on but it never blinks owing the 
error shared above.
I checked if the driver is loaded or not using OSR Driver Loader and found that 
drivers were loaded and running, 2 each for mouse and keyboard.
Here's the USB View log included with WDK:
[Port5]  :  XBox 360 Controller Filter Driver for Chatpad

          ---===>Device Information<===---
*!*ERROR:  no String Descriptor for index 2!

ConnectionStatus:                  
Current Config Value:              0x01  -> Device Bus Speed: Full
Device Address:                    0x03
Open Pipes:                           7

          ===>Endpoint Descriptor<===
bLength:                           0x07
bDescriptorType:                   0x05
bEndpointAddress:                  0x81  -> Direction: IN - EndpointID: 1
bmAttributes:                      0x03  -> Interrupt Transfer Type
wMaxPacketSize:                  0x0020 = 0x20 bytes
bInterval:                         0x04

          ===>Endpoint Descriptor<===
bLength:                           0x07
bDescriptorType:                   0x05
bEndpointAddress:                  0x02  -> Direction: OUT - EndpointID: 2
bmAttributes:                      0x03  -> Interrupt Transfer Type
wMaxPacketSize:                  0x0020 = 0x20 bytes
bInterval:                         0x08

          ===>Endpoint Descriptor<===
bLength:                           0x07
bDescriptorType:                   0x05
bEndpointAddress:                  0x83  -> Direction: IN - EndpointID: 3
bmAttributes:                      0x03  -> Interrupt Transfer Type
wMaxPacketSize:                  0x0020 = 0x20 bytes
bInterval:                         0x02

          ===>Endpoint Descriptor<===
bLength:                           0x07
bDescriptorType:                   0x05
bEndpointAddress:                  0x04  -> Direction: OUT - EndpointID: 4
bmAttributes:                      0x03  -> Interrupt Transfer Type
wMaxPacketSize:                  0x0020 = 0x20 bytes
bInterval:                         0x04

          ===>Endpoint Descriptor<===
bLength:                           0x07
bDescriptorType:                   0x05
bEndpointAddress:                  0x85  -> Direction: IN - EndpointID: 5
bmAttributes:                      0x03  -> Interrupt Transfer Type
wMaxPacketSize:                  0x0020 = 0x20 bytes
bInterval:                         0x40

          ===>Endpoint Descriptor<===
bLength:                           0x07
bDescriptorType:                   0x05
bEndpointAddress:                  0x05  -> Direction: OUT - EndpointID: 5
bmAttributes:                      0x03  -> Interrupt Transfer Type
wMaxPacketSize:                  0x0020 = 0x20 bytes
bInterval:                         0x10

          ===>Endpoint Descriptor<===
bLength:                           0x07
bDescriptorType:                   0x05
bEndpointAddress:                  0x86  -> Direction: IN - EndpointID: 6
bmAttributes:                      0x03  -> Interrupt Transfer Type
wMaxPacketSize:                  0x0020 = 0x20 bytes
bInterval:                         0x10

          ===>Device Descriptor<===
bLength:                           0x12
bDescriptorType:                   0x01
bcdUSB:                          0x0200
bDeviceClass:                      0xFF  -> This is a Vendor Specific Device
bDeviceSubClass:                   0xFF
bDeviceProtocol:                   0xFF
bMaxPacketSize0:                   0x08 = (8) Bytes
idVendor:                        0x045E = Microsoft Corporation
idProduct:                       0x028E
bcdDevice:                       0x0110
iManufacturer:                     0x01
*!*ERROR:  no String Descriptor for index 1!
iProduct:                          0x02
*!*ERROR:  no String Descriptor for index 2!
iSerialNumber:                     0x03
*!*ERROR:  no String Descriptor for index 3!
bNumConfigurations:                0x01

Xbox model number info -
It's an old controller I have that I borrowed from someone else. The serials 
have been erased out and I am sorry I am not able to share them.

PC Configuration:
Win 7 x64 Enterprise Edition running with Driver Signature Enforcement disabled.

I am new to driver programming but would love to contribute to this project if 
I can. As a beginning, I'd be happy to see this driver alive the way it is on 
your system.

Original comment by devg...@gmail.com on 15 Feb 2011 at 12:20

GoogleCodeExporter commented 9 years ago

Corrections: 
Error as in comment 5.
The tool used for getting the USB report came with WDK and is called UVCview.exe
---------
By mistake, the PC just restarted and it affected the way controller was 
behaving. I plugged in the controller *after* the PC started and changed the 
USB port too. Earlier, I just booted my PC with the controller connected.
The control utility output changed as follows and the light on the controller 
also blinked once while 'Worker thread started for mouse data.' was being 
displayed.

*****
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 ch
IOCTL failed, lastError == 31
IOCTL failed, lastError == 31
IOCTL failed, lastError == 31
Successfully sent IOCTL.  Bytes transferred:  2
Control response data received:  0x01 0x00
Successfully sent IOCTL.  Bytes transferred:  2
Control response data sent:  0x09 0x00
Successfully sent IOCTL.  Bytes transferred:  2
Control response data received:  0x09 0x00
Successfully sent IOCTL.  Bytes transferred:  3
Reading thread started for controls data.
Reading thread started for chatpad data.
Worker thread started for mouse data.
IOCTL failed, lastError == 121
Thread shutdown detected while in ControllerReadFunction.
Thread shutdown detected while in ChatpadReadFunction.
Reading thread for chatpad data has ended, with nStatus == 0
Reading thread for chatpad data has ended, with nStatus == 0
Reading thread for controls data has ended, with nStatus == 0
Worker threads successfully stopped.
Closing connection to virtual keyboard device.
Closing connection to virtual mouse device.
Closing chatpad filter driver.
Done.  The exit status is -1.
===================================================================
The USB report also changed. It has a lot more data in it now and looks like 
it'll be helpful. I am attaching it to this post owing to its length.

Original comment by devg...@gmail.com on 15 Feb 2011 at 12:52

Attachments:

[Controller USB output.txt](https://storage.googleapis.com/google-code-attachments/chatpad-super-driver/issue-2/comment-23/Controller USB output.txt)

GoogleCodeExporter commented 9 years ago

Sorry for so many comments in one go!

I got it working with 'win7_amd64_chatpad_control_test3.exe'! Yay!

There is one serious bug though. My PC was restarted when I unplugged the 
controller while all the drivers were loaded and the control application was 
accepting input.

I'd be glad if you pointed me to some resources where I can learn how to 
program drivers using WDK.

Original comment by devg...@gmail.com on 15 Feb 2011 at 1:40

GoogleCodeExporter commented 9 years ago

Dev, I'm glad you got it working.  I suspect that you might have had an issue 
with duplicate virtual mouse and keyboard drivers, since right now my installer 
does not properly remove them before installing new ones (issue 6).  The crash 
when the controller is unplugged is known, and tracked as issue 8.  I have not 
looked into it yet, but it should hopefully be fixed when I release the next 
version.  Thanks for the input!

I am afraid that I taught myself to make drivers with this project, so I am not 
an expert.  Google searching, and reading mailing list posts (such as 
http://www.osronline.com/cf.cfm?PageURL=showlist.aspx?list=NTDEV) helped me.  
OSR Online in general is helpful.  Bear in mind that if you post a question, it 
may take a while to get a response, or your question may get overlooked 
initially, so you will have to do research on your own.

The easiest place to start is probably to install the WinDDK (which you already 
have) and look for one of the installed examples that provides something 
similar.  For instance, if you want to make a USB driver, you can look through 
the "src\usb" directory.  Some directories have HTML files that can provide 
additional information about the example project.

I am afraid I will not be of too much more use for learning driver development, 
but I will toss a couple of quick links at you, ones that may have helped me 
along the way:
http://www.osronline.com/article.cfm?id=446
http://www.codeproject.com/KB/system/wdf_kmdf_basic.aspx
http://www.codeproject.com/KB/system/kmdf_osr_usb_fx2.aspx

Good luck!  I think in my case it took me maybe a month to come up to speed on 
a basic kernel driver in my spare time, though I'm sure it still has problems.

Original comment by gtsche...@gmail.com on 15 Feb 2011 at 2:36

GoogleCodeExporter commented 9 years ago

Hi,

I was having an issue with the normal control app. Now when I run the test3, it 
gives a different result. The chatpad works fine, but i cant move my mouse or 
get a response from the normal controller (well maybe i can but none of the 
buttons seem to work). Do I need to do anything special to make the control 
pads move my mouse? 

Here is the output now:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

E:\Users\Chris>cd "E:\Users\Chris\Desktop\chatpad"

E:\Users\Chris\Desktop\chatpad>win7_amd64_chatpad_control_test3.exe

*****
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
Successfully sent IOCTL.  Bytes transferred:  2
Control response data received:  0x01 0x00
Successfully sent IOCTL.  Bytes transferred:  2
Control response data sent:  0x01 0x02
Successfully sent IOCTL.  Bytes transferred:  2
Control response data received:  0x01 0x02
Successfully sent IOCTL.  Bytes transferred:  3
Reading thread started for controls data.
Worker thread started for mouse data.
Reading thread started for chatpad data.
^C
E:\Users\Chris\Desktop\chatpad>win7_amd64_chatpad_control_test3.exe

*****
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
Successfully sent IOCTL.  Bytes transferred:  2
Control response data received:  0x01 0x02
Successfully sent IOCTL.  Bytes transferred:  2
Control response data sent:  0x01 0x02
Successfully sent IOCTL.  Bytes transferred:  2
Control response data received:  0x01 0x02
Successfully sent IOCTL.  Bytes transferred:  3
Reading thread started for controls data.
Worker thread started for mouse data.
Reading thread started for chatpad data.

Original comment by chris12...@yahoo.com on 6 Mar 2011 at 12:37

GoogleCodeExporter commented 9 years ago

Chris, when you press the little "people" button on the chatpad, does it light 
up?  Your mouse controls should work then.  If they do not, then you probably 
are a victim of my installation stuff which unfortunately can make duplicate 
virtual keyboard and mouse devices.  If you check device manager and see such 
duplicate keyboard/mouse devices, let me know and I will try to find one of the 
places where I put instructions to fix it.

Original comment by gtsche...@gmail.com on 6 Mar 2011 at 12:53

GoogleCodeExporter commented 9 years ago

Hmm getting closer. Yes I do have 2 HID devices in device manager. Gonna keep 
messing around with it.

Original comment by chris12...@yahoo.com on 6 Mar 2011 at 1:00

GoogleCodeExporter commented 9 years ago

Okay, try the instructions in the "Troubleshooting" section of the Getting 
Started guide:

http://code.google.com/p/chatpad-super-driver/wiki/GettingStarted

Specifically, there are some instructions about "The uninstall process does not 
currently delete the virtual keyboard and mouse devices."

Original comment by gtsche...@gmail.com on 6 Mar 2011 at 1:09

GoogleCodeExporter commented 9 years ago

I worked around the issue with Chris.  It appears to have been due to duplicate 
chatpad keyboard/mouse devices as described above.  This should be fixed 
whenever the uninstall/reinstall code is corrected in the future.

Original comment by gtsche...@gmail.com on 6 Mar 2011 at 1:40

GoogleCodeExporter commented 9 years ago

If anyone else has this issue, this is what I did: (I am using a regular 360 
controller/wired, + a new black 360 chatpad that came with a headset.

Boot PC with F8 and disable driver signing

Plug in your controller

Open device manager (I right click my computer, choose manage, then go to 
device manager on left)

Expand the nodes for "Human Interface Devices", "Keyboards", "Mice and pointing 
devices" and "Microsoft Common Controller For Windows Class"

Starting in "Human Interface Devices" right click all the 360 stuff and do 
uninstall. You don't need to choose uninstall files. When you are done with 
this I believe most of the 360 devices should have disappeared from the other 
categories as well. If not uninstall all mentions of 360 devices.

Next plug in your controller with device manager left open.

If in the end you have 1 of each (keyboard / mouse) under Keyboards, Mice, and 
HID + Microsoft Common Controller, run the control app. (I used test3 for win7 
amd64)

Hopefully it works! Remember to hit the "people" key to enable the mouse 
functionality.

If this doesn't work for you, and you keep getting multiple devices when you 
plug in, keep uninstalling them and retrying. You might also experiment with 
uninstalling / deleting the files from Windows\System32\Drivers\keypad* and 
reinstalling.

Good luck, thanks again to the developer.

Original comment by chris12...@yahoo.com on 6 Mar 2011 at 1:48

GoogleCodeExporter commented 9 years ago

Can we get an update to the "Getting Started" guide (and compiled packages) 
that incorporates all of the above test files/etc., please? 

I am about to begin playing RIFT with my brother who is deployed overseas. I 
will be using my TV/PC combo (until my monitor arrives from storage in 3 weeks) 
. Therefore, I need to purchase a Chatpad. 

I will be using Windows 7 64-bit, AMD processor (last year's Phenom). I have 
the USB wireless dongle from MSFT and will be pairing it with a normal Xbox 360 
controller (the special red/black edition from the RE5 days).

THANK YOU! I hope to hear back soon.

Original comment by knale...@gmail.com on 15 May 2011 at 1:04

GoogleCodeExporter commented 9 years ago

I seem to have a similar problem as Trance had.  I am using Windows 7 32bit.  I 
tried test 4 (even though it is for xp) and got the same result.  This 
controller came with an xbox 360 pro console about a year after Xbox 360 
launched.  I did not get any errors during install.  Here is the results

C:\Users\Mike\Desktop\chatpad>chatpad_control_i386.exe

*****
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.

C:\Users\Mike\Desktop\chatpad>winxp_i386_chatpad_control_test4.exe

*****
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.

Original comment by Adam...@gmail.com on 15 Jun 2011 at 11:56

GoogleCodeExporter commented 9 years ago

Full uninstall, removed all devices from device manager, got a different result 
the first time:

C:\Users\Mike\Desktop\chatpad>chatpad_control_i386.exe

*****
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
Successfully sent IOCTL.  Bytes transferred:  2
Control response data received:  0x01 0x00
Successfully sent IOCTL.  Bytes transferred:  2
Control response data sent:  0x09 0x00
Successfully sent IOCTL.  Bytes transferred:  2
Control response data received:  0x09 0x00
Successfully sent IOCTL.  Bytes transferred:  3
Reading thread started for controls data.
Reading thread started for chatpad data.
Worker thread started for mouse data.
IOCTL failed, lastError == 121
Thread shutdown detected while in ChatpadReadFunction.
Reading thread for chatpad data has ended, with nStatus == 0
Thread shutdown detected while in ControllerReadFunction.
Reading thread for controls data has ended, with nStatus == 0
Reading thread for chatpad data has ended, with nStatus == 0
Worker threads successfully stopped.
Closing connection to virtual keyboard device.
Closing connection to virtual mouse device.
Closing chatpad filter driver.
Done.  The exit status is -1.

Original comment by Adam...@gmail.com on 20 Jun 2011 at 7:08

GoogleCodeExporter commented 9 years ago

Ok so after having the 31 error i finally got my chatpad to work yay!!! 

Heres what i did. I'm using Windows 7 Ultimate 64 bit.

Step 1: Restart Computer and press F8 after the bios screen and select disable 
driver signing. 

Step 2: Ran the Uninstaller for the chatpad

Step 3: Plugged in My xbox 360 wired controller with chatpad.

Step 4: Uninstalled all the drivers related to the xbox 360 controller from the 
Device Manager.

Step 5: Went to C:\Windows\System32\drivers and deleted any leftover drivers 
for the chatpad. (Chatpad filter.sys, Chatpad Keyboard.sys ect). 

Step 6: Plugged out my controller and plugged it back in so that windows 
reinstalled the controller drivers

Step 7: Downloaded win7_amd64_chatpad_control_test3.exe from
http://code.google.com/p/chatpad-super-driver/downloads/detail?name=win7_amd64_c
hatpad_control_test3.exe&can=2&q= (i put this into the same folder as the 
installer)

Step 8: Run chatpad_installer_amd64 and allow any information that pops up 
during the installation. This installation can take a few minutes so let it run 
until its finished. If you aren't sure that its finished check your task 
manager.

Step 9: Run win7_am64_chatpad_control_test3.exe, a command prompt will open and 
run, You may also notice that your xbox controller will flash, this means that 
your computer has successively connected to the controller.

Step 10: Hit the people button on your Xbox Chatpad and try move your joysticks 
:)

That's it, i hope it works for everybody else. The only problem with this 
method is that you have to repeat these steps everytime you restart or turn off 
your computer.

Original comment by gaz_cunn...@hotmail.com on 19 Jul 2011 at 12:38

GoogleCodeExporter commented 9 years ago

when i click on the chat pad installer it says ''failed to update chatpad 
filter device  0xe000020b

Original comment by Pepsicol...@gmail.com on 10 Mar 2012 at 4:00

GoogleCodeExporter commented 9 years ago

gaz_cunn...@hotmail.com What you suggested worked for me. I haven't tried 
restarting yet to see if i need to do it every time. Thanks a lot!.

Original comment by greatevi...@gmail.com on 15 Aug 2012 at 6:29

GoogleCodeExporter commented 9 years ago

Admin command prompt and win7 64 bit.

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

Control utility started.
Opening chatpad filter driver.
Couldn't open chatpad filter:  2
Failed to open connection to XBox 360 controller.
Done.  The exit status is -1.

Original comment by iFeny...@gmail.com on 19 Aug 2012 at 8:28

GoogleCodeExporter commented 9 years ago

gaz_cunn...@hotmail.com really thanks, but damn you re right, i have to repeat 
the process everytime i restart :( is there a way to avoid this?

Original comment by dannycol...@gmail.com on 26 Mar 2013 at 6:18

GoogleCodeExporter commented 9 years ago

ok i got it :), u don't have to make everything everytime, but after u did all 
the points wrote by gaz_cunn...@hotmail.com, everytime u restart the system u 
have to disable driver signin, then after login, unplug and plug again the 
joypad, and the run as administrator win7_am64_chatpad_control_test3.exe, and 
it will works everytime :)

Original comment by dannycol...@gmail.com on 26 Mar 2013 at 8:26

GoogleCodeExporter commented 9 years ago

TUTORIAL WORKS 100%!!! A user called Kenneth did this. Found it in the issue 
section!

JUST BEFORE DOING THIS... DELETE ALL THE DRIVERS MANUALLY IN THE DEVICE 
MANAGER... RIGHTMOUSE (DELETE DRIVER -> UNINSTALL? YES in the checkbox)

I HAD THE SAME PROBS AS YOU AND NOW IT'S WORKING!!! 

KENNETH:
Heres what i did i was having the same problem and i solved it heres how. 1.I 
unplugged the controller 2.uninstalled all the chatpad drivers 3.plugged the 
controller in one of my pc's back usb ports 4.went to device manager and 
updated my normal controller drivers( if the controller updated the drivers 
automatically its best to check but you should be ok) 5.restart and do the f8 
driver check disable 6.install AMD64 chatpad drivers and wait for it to 
finish(if you get the pop ups asking about drivers click install anyway) 7.once 
the drivers have installed restart the pc and do the f8 disable again 8. now 
unplug the controller and plug it right back into the same usb port 9.run the 
normal win7 amd64 test 3.exe and the command prompt should open and stay open 
10.once the command prompt finishes it will be open so press a couple buttons 
to see if they light up this works 100% of the time for me although it took me 
awhile to figure it out also im on win7 64bit too if it doesnt work retrace 
your steps because i just typed this entire message from my chatpad hope this 
helps good luck

Original comment by rogelio1...@gmail.com on 11 Jan 2014 at 6:45

poeskat / chatpad-super-driver

Chatpad control utility crashes (with error 121) #2