I used to do more requests, trying to more fully duplicate the controller initialization, but my current theory is that the official Microsoft controller driver should be doing the normal init, and I just add the chatpad init commands once the controller is already set up. I am indeed toggling 1F and 1E regularly (it should be sent in the chatpad_control_code.cpp file), which lets the chatpad stay alive.Originally Posted by supporer
My "for Windows" controller is X811616-005, and my chatpad is X814365-001, the same as supporer's. I think the issue may be specific to the controller instead of the chatpad, since the data you're seeing going to and from the device is control endpoint data, sent to the controller device itself.
By the way, supporer, thanks for helping with the research. You're a big help getting things working.
So the device showed up in Skype, WITH the (non-functional) chatpad plugged in, before the new drivers were installed? I wonder if the full messenger kit uses an additional/modified driver. Unfortunately I bought the chatpad used, from Gamestop, without the special headset attachment that fits into the chatpad, so I can't test that part right now. Sorry about that, but maybe someone else with the headset will have more ideas.
GAFBlizzard, thats a very interesting theory, i will get back on this (after digging a bit more).
My WIREDcontroller has the serial number X809483-002, people reading this
PLEASE, post the X80***** serial of both your WIRED XBOX360 controller + touchpad, i will list them in a sheet for on the google-code page.
didn't notice the blue screen code and i ave checked and no .dmp files if it does it again i will make sure to take notice
Hey try this.
1) Make sure that chatpad_control.exe is closed.
2) plug in mic into chatpad/controller
- if the device isnt installing go to step 3
3) with mic plug into chatpad and controller, remove the chatpad with mic and then insert back to controller.
- if this didnt work then im not sure as i use the wireless mic.
If you don't have any .dmp files then they weren't generated. You would have to get the codes out of an Event Viewer entry. Let me know if it happens again, and I will try to work with you to get better data. Sorry again about the crash, and I really hope you didn't lose any unsaved files. I know it's a danger of alpha drivers, but still.
Also, you mentioned you went back to your old config file. Did the new file crash every time, or were you just changing it back in case? I would suggest using the new file anyway, and seeing if the crash happens again since I think it is very unlikely it is related to the config file. The config file just controls what key/mouse codes get sent to the virtual devices, for the most part.
Side note, I'm going to try to send Philipp an updated control utility for him to test later today. Since it was easy, I added in a way to specify custom key codes from the HID Usage Tables, which should allow people with non-US keyboards to use special keys, such as the <|> key.
The suggested steps from ddxcb are good ones...gremelin, let me know how it goes.
supporer, just to be clear, the reason I say I have the theory about the MS driver initializing everything is because I'm acting as a lower filter driver. You may or may not be familiar with that, but the idea is that my software just sits between the hardware and the official Microsoft code, and I pass through everything that I do not need to mess with. This lets me do things like stop thumbstick data from controlling the game (when "Windows Mode" is turned on for mouse control), and it lets me send my own control commands to enable the chapad. Any device setup or microphone setup that works before the control utility starts up should hopefully keep working afterwards.
DEFINITELY the winner.1. Do you think GAFBlizzard is the winner? If not, please tell everyone why or what needs to be improved.
I would have absolutely no problem contributing to this. I guess set aside part of the pot for the necessary hardware? Or otherwise set up a new pot which I would be glad to donate to. But yes, I'll be honest, I'm personally not all too interested in the wired controllers... The way I am looking forward to using the chatpad is as a compact, versatile keyboard/mouse for an HTPC, which means I'll almost always be about 10 feet away from the computer... Obviously wired isn't ideal for this. XD2. Question from GAFBlizzard : If the donators agree that they want me to look into wireless support, I would take as payment whatever the most common official wireless 360 controller and wireless base/dongle combination is, so that I can work on driver development with it.
I'm not entirely sure how this would affect people on a per-case basis... Obviously there are plenty of x64 users, but as of right now I'm not one of them. Consider my standpoint on this to be the same as the majority of others. Heh.3. Question from GAFBlizzard : If the donators agree that unsigned kernel drivers, or test-signed kernel drivers, are a problem because of 64-bit operating systems, then a few hundred could be set aside to cover the cost of a driver signing certificate. I need to find out the full details of what would be required, but I do not think the cost is too bad and my understanding is that we would not need to go through the Windows quality labs just to sign a driver. The certificate might only last for a year, but as long as the kernel components are stable by the end of the year, I would hope that the signed kernel components would still be valid after that point.
You won the pot. You do whatever you want with it.4. Statement from GAFBlizzard : Whatever money remains after the above items would go to the Child's Play charity: http://www.childsplaycharity.org/
Also, while I did say that I'm not too interested in wired controllers, I think I'm gonna go buy a wired controller to see how it works, and if errors come up I'll do whatever I can to assist in their resolution.
its all working perfect at the moment been using it for a few days as my primary mouse and keyboard on my media center pc works great switching between mouse and gamepad is ideal for playing games xpadder is no longer in use on my system when the blue screen happened i didnt lose any data it would only crash when i tried using my custom keyboard layout but after that chatpad control wouldn't load all i changed in the chatpad config was the speed of the mouse to 13 when i copied the default config file back it worked fine was thinking when the crash happened i might of had the config file opened at the time
Hmm, thanks. Sorry for all the questions, but I want to make sure I understand everything correctly here:
1. Did you have more than one blue screen, or just the one crash?
2. After the crash, and your system restarted, you are saying that the control program would not run at all?
3. Would you please send me the bad config file if you still have it around? Or if you are positive that the only thing you had changed was the mouse speed to 13, I can just try that change myself. You said you were adding some international characters, so I wanted to get your version of the config file just in case something went wrong with that particular file.
Thanks!
yea i had the blue screen twice, after 1st crash i was still able to use chatpad control, the second time it happened i had changed the speed to 13. after that chatpad config wouldn't load, the crashes only happened when i switched to using my custom keyboard layout which i created using microsoft keyboard layout creator. i don't have the bad config because i just pasted over the top of it. im checkng to see if i have done anything wrong when creating a custom keyboard layout
Hmm, did the crashes happen exactly when you switched your keyboard layout? That could be a problem with my virtual keyboard device driver, since Windows probably tries to do something with it. A workaround for now would be changing to the proper layout, and then starting the control utility.
Are you only using the custom layout so you can get special UK keys? If so, let me know which symbols you need, and I can try to help you with the key mappings. I just sent Philipp the test binary (Windows 7 64-bit only) that allows special non-US keys to be used, and that will be available to everyone once it's tested and a new release is made.
For now you will be missing one or two keys, but you should be able to use these images to get most of the symbols you need in your country. Just compare against keys in the same positions, and hopefully that will work (i.e. use shift + 3 to get the pound sign):
http://en.wikipedia.org/wiki/File:KB...es-NoAltGr.svg
http://en.wikipedia.org/wiki/File:KB_United_Kingdom.svg
Posting Permissions
LinkBack URL
About LinkBacks
Reply With Quote
Bookmarks