Topic: Xbox 360 Controller Chatpad Drivers v0.0.3a for Windows (Read 574 times)

tomgreen99200 · « **Reply #45 on:** January 01, 2011, 02:35:00 PM »

Here is what I get when i run the new control utility:

G:\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
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.
Reading thread started for chatpad data.
Worker thread started for mouse data.

It seems to just hang there and never returns the exit status. I left it open for 10 minutes. If you want more debug help pm me.

edit: While winxp_i386_chatpad_control_test4.exe is running I am able to use the chatpad! Still no mouse support though. While winxp_i386_chatpad_control_test4.exe is closed I loose support for the chatpad though.

This post has been edited by tomgreen99200: Jan 1 2011, 10:37 PM

GAFBlizzard · « **Reply #46 on:** January 01, 2011, 02:46:00 PM »

QUOTE(tomgreen99200 @ Jan 1 2011, 04:35 PM)

edit: While winxp_i386_chatpad_control_test4.exe is running I am able to use the chatpad! Still no mouse support though. While winxp_i386_chatpad_control_test4.exe is closed I loose support for the chatpad though.

That's correct behavior. The control utility has to be running for the chatpad to work. You can minimize the command prompt if you like, though...it's useful right now since it lets me get debug output.

To use the mouse, press the little "people"/MSN button in the lower left, next to the green button. It should light up, and the thumbsticks should start controlling the mouse instead of a game.

tomgreen99200 · « **Reply #47 on:** January 01, 2011, 04:05:00 PM »

This version works great. I posted this message using my chatpad. I also have mouse support. This is so cool, thanks!

GAFBlizzard · « **Reply #48 on:** January 01, 2011, 04:08:00 PM »

Awesome, thanks very much for the help. You and the other guy confirmed that this works, so I should be able to just add auto-detect code when I do another driver release for everyone, and the drivers should then work for people with either controller hardware variant.

Have fun with the drivers! You may encounter other bugs...I've been trying to make a list of them, but at least I'm also trying to fix them!

122275 · « **Reply #49 on:** January 01, 2011, 04:31:00 PM »

GAFBlizzard
Is there anyway I could get a copy of that winXPtestconfig4 file for win7 i386?
I can install everything fine but I cant use the chatpad or the mouse functions. The chatpad does light up for me when I press the buttons but does not output anything. I am using an original xbox 360 controller.(more than 2 years old)
Thanx for you effort on this app.

This post has been edited by 122275: Jan 2 2011, 12:34 AM

GAFBlizzard · « **Reply #50 on:** January 01, 2011, 04:34:00 PM »

QUOTE(122275 @ Jan 1 2011, 06:31 PM)

GAFBlizzard
Is there anyway I could get a copy of that winXPtestconfig4 file for win7 i386?
I can install everything fine but I cant use the chatpad or the mouse functions. The chatpad does light up for me when I press the buttons but does not not output anything. I am using an original xbox 360 controller.(more than 2 years old)
Thanx for you effort on this app.

Actually...try giving the WinXP version (test 4 executable) a shot under your 32-bit Windows 7. It might work, but be sure to right click and run it as administrator. If it doesn't work, I can do a build for you later tonight. Since it's just a Windows application I'm not sure if the version stuff is as important (I'm building everything from the different build settings in the Windows device driver development kit).

Also, for anyone trying key presses, make sure you switch to a notepad window or something before you try typing letters, since the letters you type won't show up in the command prompt window. You can just minimize the command prompt control utility window and use the chatpad with other applications.

This post has been edited by GAFBlizzard: Jan 2 2011, 12:38 AM

122275 · « **Reply #51 on:** January 01, 2011, 04:52:00 PM »

Yes GAFBlizzard that file works great. Thanks for everything. I you need any other testing please let me know.

GcRayden · « **Reply #52 on:** January 01, 2011, 05:31:00 PM »

When I try to install it on my Windows XP 64bit, it gives me the following error:

" Chatpad Installer Message: Failed to update chatpad filter device driver: 0xe0000235 "

I've tried going into properties and changing the compatibility to XP, but it won't work. Please help

GAFBlizzard · « **Reply #53 on:** January 01, 2011, 06:52:00 PM »

QUOTE(GcRayden @ Jan 1 2011, 07:31 PM)

When I try to install it on my Windows XP 64bit, it gives me the following error:

" Chatpad Installer Message: Failed to update chatpad filter device driver: 0xe0000235 "

I've tried going into properties and changing the compatibility to XP, but it won't work. Please help

Unfortunately right now I have an alpha version for every recent OS configuration except...XP 64.

I just checked and it should be possible to make one, but it won't be right away. I hope by next weekend I will have a new version out and I can try to include XP 64 support then.

122275 · « **Reply #54 on:** January 01, 2011, 07:01:00 PM »

GAFBlizzard
How can I map the directional pad on the controller to the up, down, left, right on the computer keyboard.

I tried this

CONTROLLER_BUTTON_UP + CONTROLLER_WINDOWS_MODE = KEYBOARD_KEY_UP

but I get a parse error. what are the correct buttons for that part of the controller?

GAFBlizzard · « **Reply #55 on:** January 01, 2011, 07:21:00 PM »

QUOTE(122275 @ Jan 1 2011, 09:01 PM)

GAFBlizzard
How can I map the directional pad on the controller to the up, down, left, right on the computer keyboard.

I tried this

CONTROLLER_BUTTON_UP + CONTROLLER_WINDOWS_MODE = KEYBOARD_KEY_UP

but I get a parse error. what are the correct buttons for that part of the controller?

My driver does not currently provide the ability to map the thumbsticks to anything but the mouse (I might just leave this, it seems to make sense to me), but it also does not let you map analog trigger buttons or the d-pad. I don't like using the 360 d-pad so it wasn't a priority for me, but I will add it to my list of requested features. I actually had plans to allow you to do things like invert the thumbsticks on the fly by pressing a button, in case that's useful in some games, or allow you to swap controller buttons around (like A <-> B ) in case a game did not let you change those controls. Right now, those are just possible future features though. If anyone thinks a certain feature would be really awesome, and tells me, I just make a note of it so it might get done sooner.

I believe XPadder is not free software, but it may provide the ability to do most of what I just described, if I'm not mistaken (or maybe joy2key). I think at least one person has used XPadder along with the chatpad driver. In fact, I think XPadder even provides an option for controller mouse control.

Ultimately, my drivers may do some of the same things that XPadder does, but right now there are several things that I have just put off because of time/life/bug-fixing getting in the way.

At minimum, I would like to support swapping buttons around, support mapping the dpad and analog triggers to simulated keyboard keypresses, and possibly support vertical thumbstick inversion.

122275 · « **Reply #56 on:** January 01, 2011, 07:33:00 PM »

Yes I was talking about the D-Pad for the up down left right not the analogs.

using the D-Pad will make for better and more precise movement in text situations.
Thanx for all of your help and I look foward to
D_PAD_UP
D_PAD_DOWN
D_PAD_RIGHT
D_PAD_LEFT
to come soon as usable/mapable strings

m4tr1x00 · « **Reply #57 on:** January 06, 2011, 03:50:00 AM »

Tested on Windows 7 64bit with stock wired Xbox 360 controller and stock Chatpad. Does not work at all for me, it makes the controller turn off after restart and I have to re install the stock drivers for the controller to make it usable again.. must be doing something wrong? Help please?

GAFBlizzard · « **Reply #58 on:** January 06, 2011, 08:17:00 PM »

QUOTE(m4tr1x00 @ Jan 6 2011, 05:50 AM)

Tested on Windows 7 64bit with stock wired Xbox 360 controller and stock Chatpad. Does not work at all for me, it makes the controller turn off after restart and I have to re install the stock drivers for the controller to make it usable again.. must be doing something wrong? Help please?

Did you make sure to follow the Getting Started information about pressing F8 on each bootup to enable unsigned drivers? This is required on 64-bit Vista and 7, unless you have one of the higher versions like business/ultimate. There is apparently a way to use gpedit.msc to disable the driver signing requirement then.

m4tr1x00 · « **Reply #59 on:** January 06, 2011, 10:55:00 PM »

Ah that was it, my controller is alive again after i install the drivers and restart with f8. But the chatpad is still not lighting up

Author Topic: Xbox 360 Controller Chatpad Drivers v0.0.3a for Windows (Read 574 times)