That's fine, and probably something I should comment out eventually. Normally, the USB endpoint that corresponds to the controls (thumbsticks, buttons, etc.) does nothing but send a bunch of 20-byte messages, if I recall correctly. Occasionally, for whatever reason, you'll get a short message like that, and since the control utility doesn't know what it is it prints that message out.
BLizzard, I can not seem to keep the Command Prompt Window to stay open, even running it in administrator.
I ran the Installer ... said it was successful. Ran the control, the first time it did show a bunch of text and then went away after about 5 seconds. Now, the control comes up for a mere second and then dissappears quickly.
Edit: After a restart, it repeats the same way.
One of the changes I made for my next version is to make the command prompt stay open until you hit a key. Unfortunately your version doesn't have that.Originally Posted by revel911
What you can do is go to your start menu and find the command prompt (Start->Programs->Accessories, or somewhere around there), and then do right click -> run as administrator. Then, use commands like these to run the control utility:
cd c:\your_chatpad_directory\some_folder
chatpad_control_amd64.exe
(Or use i386 if you are running on a 32-bit machine)
Once you run the control utility and it exits, you should have a bunch of messages that you can then post on the forum or email to me, and I'll do my best to get it working.Note that you can use the right click -> "Mark" option to select text from the command prompt, and then hit enter to copy it to the clipboard for easy pasting into a web browser.
Holy crap ... you are fast.
Code:c:\chatpad>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 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. Thread shutdown detected while in ControllerReadFunction. Reading thread for chatpad data has ended, with nStatus == 0 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. c:\chatpad>^A^A
Excellent, looks like you just need the new init code. Try unplugging your controller, plugging it back in, and then dowloading this file:
http://code.google.com/p/chatpad-sup...3.exe&can=2&q=
Save it to the same directory as your current control utility, and then run it. It should work on your 64-bit system. If this works, it's another issue which should be fixed whenever I get the next version out. Good luck!
i purchased a plug n play kit. it comes with the plug and a rechargable battery pack ~$20 from amazon. should be here tomorrow (hopefully!)
couldn't find this at wal-mart/best buy either
Definitely closer.
I was able to get the chatpad to light up and recognize the people, green and orange buttons. Besides that .... nothing.
Code:***** 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. Reading thread started for chatpad data. Worker thread started for mouse data.
No worries! Unplug the controller, and follow the instructions in this post to get rid of the extra virtual devices that you probably have:
CONTEST: Xbox Chatpad Driver Challenge
GAF, I've got a question about configuration.
Is it at all possible to reassign the dpad when using the "CONTROLLER_WINDOWS_MODE" switch? I'm currently using my chatpad for lazy web development, and a full set of arrow keys would be immensely helpful. I've tried "CONTROLLER_DPAD_****" and "CONTROLLER_BUTTON_****", but the control utility just crashes on load, so I guess those are out for it. My last guess is mapping an axis, which would be wonderful if possible, but I'm not getting my hopes up.
Mapping an axis, which seems like the only likely alternative, given windows sees it as axis01/02 for the dpad, would let me map axis05/06 (right thumb stick) as my mouse wheel, letting me scroll with some ease while browsing code/web pages.
I know it seems selfish to ask so much, and if it's not possible, feel free to say so.
As always, any help would be much appreciated, and I'd still be more than happy to help with testing, or anything else that you might need help with.
Sorry about the long winded posts / small walls of text.
tl;dr: I want to map axis01/02(dpad) to direction keys, but can't figure it out.
Sorry to inform you friend but the plug n play kit will not work with this.
I was going to get a wired controlled for christmas, but m brother who bought it for me said the man behind the till reccomended the plug n play it -_- I got pwnt!
Posting Permissions
LinkBack URL
About LinkBacks
Reply With Quote
Bookmarks