Thread: CONTEST: Xbox Chatpad Driver Challenge

I'm running Windows 7 64-bit home premium also, and I get the blue screen crash almost every time I unplug. It doesn't seem to matter if I am in mouse or joystick mode, and it also doesn't seem to matter if I close the utility and wait awhile, sometimes I quit the utility wait a few minutes and unplug okay, more often though I get the blue screen stop error. Any idea on a timeframe for the next release? My workaround right now is to shutdown my PC when I'm done playing a game but that's kind of a pain since you have to constantly do the driver signing enforcement on boot up, and I'd like to just disable it and let my PC on all the time. Please let me know if you need any troubleshooting info from my machine if it could be helpful at all, and I'll get you a quicker response next time

Hey, First post...

Just want to start off by saying all the work you've put into this is stupendous! Really looking forward to getting the chatpad working on my system.

Onto my question, I couldn't find anywhere else that had this problem, so i thought I would post here.

(Edit: Found an issues placeHere where I posted in reply to this same issue.)

Installed and everything seemed to go okay.

When I ran chatpad_control_i386, the command prompt instantly crashes at Please Wait...

Opened an administrator Command Prompt and re-ran the file, and got the following.




*****
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 am running a windows XP system, and the controller is currently plugged in with the current drivers from MS.

Thanks for everything, and I hope perhaps my little extra bit of information helps out in the debugging of this problem.

~Fox

P.S. Sorry for the long message......

Blackfox, do you have an official Microsoft wired 360 or "made for Windows" controller? The error code 2 indicates that the device could not be found, I think. That should only happen if the installer was not able to detect the controller and attach a filter driver. If you have a "special edition" controller or a Mad Katz version that could be the problem, for instance. I know Mad Katz does not work with my driver so far (may need yet another set of initialization codes or something like that).

GAFBlizzard,

I just wanted to say this, though I'm sure within the 600 replies this thread has, you've been told many times:

Thank you for stepping up on this and getting done what Microsoft refuses to put any effort into.


That being said. Because of this driver you've written, I will use the chatpad and my wired 360 controller, instead of an expensive (by comparison) bluetooth mini keyboard.

No, I have an official wired controller. I actually believe this was the controller that came with my first Xbox 360 that I bought several years ago...I know the controller is connected, and windows is finding it fine, as I have the lit up ring, and Xpadder can find it just fine. Not sure why the driver wouldn't be able to find it....

I'll see what I can come up with, until then, any thoughts??

Thanks again,
~Fox

Originally Posted by Blackfox42

No, I have an official wired controller. I actually believe this was the controller that came with my first Xbox 360 that I bought several years ago...I know the controller is connected, and windows is finding it fine, as I have the lit up ring, and Xpadder can find it just fine. Not sure why the driver wouldn't be able to find it....

I'll see what I can come up with, until then, any thoughts??

Thanks again,
~Fox

Hmm. Can you post a screenshot of your device manager, with any sections that are related to the 360 controller and/or chatpad expanded?

ok so it seems that while xpadder could find my controller, the drivers couldnt. after some fiddling around (and a couple of reboots) i was able to get it working. Im not entirely sure what happened, but i think it had to do with needing a reboot and some extra devices that were floating around from previous attempts. Regardless, its working great now, as evidenced by the fact that this was typed via my chatpad.

Thanks Gaf!!
~Fox

GAFBlizzard,

FYI, I was able to install the chatpad_0_0_3a_winxp.zip package on Windows Home Server, which is based on Windows Server 2003 32-bit. The Xbox 360 controller appears as a generic HID game controller. This is great news because the Microsoft driver does not support Windows 2003 and refuses to install, and I had no luck using the XBCD driver which installed but could not start the controller (code 10).

Rumble and headset audio output are working in the games that support it and let me choose the controller as audio output. I haven't tested the mic. The OS rebooted once when I unplugged the controller but it looks like one of the known issues being worked on.

Thanks GAFBlizzard!

Do you mean you're using it without the chatpad? Or the chatpad AND the rest of it work now that you installed that package?

I'm...rather surprised it worked actually, haha. My sympathies for you being stuck with Windows Home Server. :P