i use a SealShield silver surfer wireless.. for my chat pad for my 360 no drivers needed..
Need Xbox 360 Chatpad driver
Hi,
one year ago i buy a Xbox 360 Controller Made by Microsoft Corporation and a Chatpad for it. on the box was info about use for Windows-based PCs but until now no driver... so i am here to ask for some help. For now i can turn the backlight on sending
ctrl 0x41 0x0 0x1f 0x02 # Init (without this, no led wil work)
ctrl 0x41 0x0 0x8 0x02 # capslock
ctrl 0x41 0x0 0x9 0x02 # square
ctrl 0x41 0x0 0xa 0x02 # circle
ctrl 0x41 0x0 0xb 0x02 # people
ctrl 0x41 0x0 0xc 0x02 # backlight
ctrl 0x41 0x0 0x11 0x02 # capslock
ctrl 0x41 0x0 0x12 0x02 # square
ctrl 0x41 0x0 0x13 0x02 # square and capslock
ctrl 0x41 0x0 0x14 0x02 # circle
ctrl 0x41 0x0 0x15 0x02 # capslock and circle
ctrl 0x41 0x0 0x16 0x02 # circle, square
ctrl 0x41 0x0 0x17 0x02 # circle, square, capslock
ctrl 0x41 0x0 0x1b 0x02 # makes led go on on keypress
ctrl 0x41 0x0 0x1e 0x02 # Init2 >>> Ep6: [5] { 0xf0, 0x03, 0x00, 0x01, 0x01 }
ctrl 0x41 0x0 0x1f 0x02 # Init (without this, no led wil work)
i also have acess to USB protocol analyzer (but it is not mine... sorry) to have the info that travell between the controller and the Xbox
also we can recive one key press but after it is dead.... and i dont know why... a lot of people are working on it but microsoft made it so at leas you can help us to try make a driver...
2nd byte flags:
shift/capslock = 0x01
square = 0x02
circle = 0x04
people = 0x08
3rd byte keycodes:
1 = 0x17
2 = 0x16
3 = 0x15
4 = 0x14
5 = 0x13
6 = 0x12
7 = 0x11
8 = 0x67
9 = 0x66
0 = 0x65
q = 0x27
w = 0x26
e = 0x25
r = 0x24
t = 0x23
y = 0x22
u = 0x21
i = 0x76
o = 0x75
p = 0x64
...
...
...
Windows for home | Previous Windows versions | Gaming
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
81 answers
Sort by: Newest
-
Anonymous
2010-06-12T01:24:22+00:00 -
Anonymous
2010-03-14T07:25:09+00:00 Hey everybody, there are tons of people out there who want these drivers made as you can see. I just set up a forum to rally us together to hopefully convince Microsoft or, if not, then maybe put together a donation fund and have a third-party driver made. I know it's been a long time since most of these posts were written, but if you're still interested PLEASE just sign up on the forum and make a 2-second post saying you're still interested, you don't have have to confirm your email:
There are legions of people -- especially HTPC (home-theater PC) users -- who need this, and seeing as the Xbox360 controller is arguably the best joystick, I know there are a ton of future possibilities for the chatpad. I would like to develop for it myself, but without ANY way to interface with it, it's a wonderful piece of hardware with no purpose to PC users. Again, please just sign up on the forum link above and let us know that you're one of many who would like to use this.
THANK YOU!
-
Anonymous
2010-02-13T09:11:11+00:00 I would think developing a driver for a mini keyboard would be a simple task.
I'm pretty sure Microsoft simply decided there wasn't enough money in it to invest a couple hours of work into making a driver.
-
Anonymous
2010-02-06T01:53:41+00:00 Please go back and read where I did say that I could see the advantages of having a driver for the Chatpad. As for my smugness in quoting myself, that was to bring attention to the points that others have missed without having to type the same thing over again. These same points that you seem to have missed also. All I did was state the obvious and seemingly little known truths that everyone seems to forget.
P.S. Now that games for windows is out and has a special software just for this, maybe now the chatpad will work. I haven't tested this because I gave my chatpad away.
I hold to a simple philosophy: just assume everyone's a piece of c.r.a.p. and then be pleasantly surprised if you find anyone who isn't.
-
Anonymous
2010-02-03T17:08:23+00:00 @DatDarkOne
First, as others have pointed out, initially the packaging did say that the chatpad would work with Windows Live Messenger, so either your recollection is poor, or you did not buy the device when it had this packaging. Granted, it doesn't explicitly mention that it will work with Windows, but it also does not explicitly say that it will not, and given the fact that Windows Live messenger is a Windows based program, I figured there was an implicit understanding that this device would work with windows, especially when you consider my second point...
I bought the chatpad without even owning an xbox 360, because I had already purchased the controller with the adapter to connect to my PC. The chatpad very clearly and explicitly claimed to work with my device in a manner in which I intended to use it (i.e. I am gaming on windows, and I have Windows Messenger open. I receive a message and I can respond to it, without having to put down my controller, get up from my couch, walk over to the keyboard, then type my response, while I am getting fragged in the meantime in the game.)
If you really cannot imagine how a device like this would be useful with a PC that already has a keyboard attached, then you sir, have no imagination.
Lastly, A buy a lot of devices that do not have software media in the box, but that I can still get drivers for. Frankly I am always surprised when I get a device with a driver CD, given the fact that the majority of computer I see these days, (e.g. netbooks, slim laptops, mini-PCs, etc...) do not even have optical drives.
I have never responded to a forum topic here before, but this particular issue has bugged me for quite some time, and your response (quoting yourself) was so smug, I just had to chime in.
@Madrang (if you even still monitor your account)
I have never written a driver before, but this seems like it would be a worthy weekend project that I would like to work on. Could you point me to some good articles that might help me get started.
Cheers!