My chatpad says "X814365-001"
My chatpad is X852479-001, I couldn't find a corresponding serial for my controller but it is a "Made For Windows" wired version. I also have a headset register when I plug in the chatpad, regardless of whether or not the drivers are installed.
(Vista 32-bit)
My chatpad says "X814365-001"
Hey Gaf.. Xbox 360 wired controller serial XD its very old so i cant read it
but here is the chatpad serial X814365-001
still havnt been able to get past the chatpad.... txt issue
*****
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: 0x09 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.
Worker thread started for mouse data.
Reading thread started for chatpad data.
since IOCTL failed, lastError == 31 showed up analogue mouse is very slow to respond and chatpad double types keys
Just saw unofficial chatpad on ebay
Link: http://cgi.ebay.co.uk/Keyboard-w-Aud...#ht_7697wt_906
If scroll down the page a little bit it say
"Allows text and voice chat through the online Xbox Live service
Or via the Internet when the controller is hooked up to a Windows PC"
Anyway prob good substitute for wireless controller until driver can be made.
Cheers and happy new year
Precisely, sorry if I wasn't clearer about that.
I actually spent a fair bit of time last night reworking some of the file loading code.
xCKxHolyChaos and Aidan91, check your PMs, since I sent you both a PM with a version of the control utility that should either fix the problem or give us an idea about what's wrong.
Sorry you're having problems.If you reboot does it fix it by any chance? Those three lastError == 31 messages are normal, and I think I even have a note to myself that I should probably stop printing them so they do not alarm people. If MORE than 3 messages show up then there are problems.
After you reboot, if you see the same problem, how does the mouse behave exactly? Is there a pause before the mouse moves, or does it just move very slowly? Thanks for the help!
Wow, if they made their own Windows drivers and it works with wired and non-wired controllers then that fixes everyone's problems. :P It's cheap too. I wonder if their drivers would even work with the official chatpad! If they're perfect then at least my 2-3 months of work were educational for me... XD
thanks for the support blizzard i did a reset and was still doing it the mouse was just moving slowly and key presses were delayed after about 15 min it all started working normally
i also did the key edits u suggested and @ £ and the brackets are all in the right place i also edited to put ~ # in the right places but i still dont have back slash cant figure it out it always ends up as #
Something's still not right, so I still made a note to try to maybe get you a test build that could work better with the mouse stuff. If this is something like a netbook then I might be sending mouse messages too quickly. Keypresses definitely shouldn't be delayed.
I have a solution to the backslash thing now, but it's not in the currently released version. If you have Win7 64 I already have a test utility version uploaded as http://code.google.com/p/chatpad-sup...trol_test2.exe if you want to try. It will allow you to add lines in the config file like this:
CHATPAD_KEY_A = KEYBOARD_KEY_ID_50
CHATPAD_KEY_B = KEYBOARD_KEY_ID_100
Those key IDs correspond to special non-US keys, and for a UK keyboard I think they should provide \|#~ characters if you don't already have them (use shift for | and ~, no shift for \ and #). The key IDs correspond to usage IDs in the HID Usage Tables PDF spec...if anyone is interested in the gory details of that, send me a PM or something.
Heya GAF, Just curious, any plans for a wireless controller version of the chatpad driver? Will it be easier to port now that it's working for wired? or will it be a totally new rewrite?
The plan is to try to get wireless support working if I can get past the major problems a few people have reported for the wired driver. I am really not sure how hard it will be. It should not be a totally new rewrite, and a lot of the code and knowledge I've gained should be useful for experimenting with the wireless controller, but I won't know until I actually get into the protocol that the wireless stuff uses.
General question for trader and everyone else with wireless controllers: I seem to recall that once upon a time there was a wireless base + controller combination for Windows, but that was discontinued, and the only option now is to buy a wireles dongle with the controller. Is that correct? If I do end up getting such a controller (with contest money or not), I want to make sure I'm getting the right product. I hope that I don't end up in a situation where the dongle works but the base station works differently, or something silly like that.![]()
Bookmarks