Would it be possible to also upload the source code of the driver right now? Or does that have to wait till the driver is finished?
I really need to fix the uninstaller tomorrow. You should be able to uninstall them all, you just have to uninstall the HID compliant keyboard and HID compliant mouse entries before you uninstall the XBox 360 Controller HID Keyboard for Chatpad (or HID Mouse for Chatpad) entries. If you're not sure whether a HID compliant keyboard/mouse belongs with the chatpad, right click it, go to properties, go to details, and see if you see anything like ChatpadKbd or ChatpadMouse. Otherwise, leave it alone.
The other thing I really need is someone else with Windows 7 to provide a test case with the latest code. If you made sure you deleted all the devices, and then ran the latest install, it installs for you and work fine on Windows 7 as far as I understand. My new clean install of Windows 7 64-bit works with the drivers too, so I need to track down where the problem is.
Would it be possible to also upload the source code of the driver right now? Or does that have to wait till the driver is finished?
I wanted to wait until I had things working for Windows 7, so I don't have to upload the source code as well as the binaries with each minor alpha change. I went through and made sure the files had the license line though, so worst case, if no one else manages to test Windows 7 today, I can upload the source anyway. I -might- be able to do some testing over the break but it's probably unlikely aside from responding to questions.
Of course, someone else could technically use my source code and what I'm about to tell you to get something working over the break and then claim the prize, but I'm hoping that won't happen especially since (as far as I know) I have a working Windows XP version at the moment.
Don't worry, I haven't forgotten about you. Are you able to test Windows 7? If you are still just patiently waiting for the protocol info so you can finish the Linux driver, the only messages you need should be as follows (all control requests) once the controller is ready for normal, non-chatpad use:
0x40, 0xa9, 0xa30c, 0x4423, 0x0000 (call will return failure)
0x40, 0xa9, 0x2344, 0x7f03, 0x0000 (call will return failure)
0x40, 0xa9, 0x5839, 0x6832, 0x0000 (call will return failure)
0xc0, 0xa1, 0x0000, 0xe416, 0x0002 (read 2 bytes, will return a mode)
0x40, 0xa1, 0x0000, 0xe416, 0x0002 (send 2 bytes, data must be 0x09 0x00)
0xc0, 0xa1, 0x0000, 0xe416, 0x0002 (read 2 bytes, this should return the NEW mode)
At this point you'll get a ton of chatpad messages and can handle them, sending the alternating keep-alive messages like in the trace logs.
The key thing is to use the 0x09 0x00 mode instead of the old 0x01 0x02 values we were seeing in a trace. This was apparently discovered by this guy: http://mbed.org/users/AjK/programs/S...8c_source.html I suspect it may have something to do with older chatpads, or "Made for Windows" vs. 360 chatpads, but I don't have confirmation yet. My original plan was just to try both modes and use the one that resulted in a proper mode change first. Note that the code I just linked claims that there is some sort of additional handshaking going on, but as far as I can tell there's no need for it besides the messages I sent above. It just seems to work.
Thanks for all the research help, Grumbel. I really appreciate the work you and others have done to help us get to this point.
Has anyone else been able to try the new install for Windows 7? I see 10 downloads now but the only confirmation positive or negative has been supporer.
GAFBlizzard: You are the first providing binaries, and are the only one with the sourcecode.
I think the best thing to do is, send the sourcecode to the mp3car Administrator, with your request that you would like to claim the prize. Then put it on code.google.com as well (or simultanously).
Great work fellow!
PS: if there's more testing to be done, i got both the wireless/wired controller, and have multiple machines here in house
W7 32/64 and (K)Ubuntu 10.04 /10.10 both 32 and 64 - let me know
I think SuperAngelo64 might be able to try it too. For your Windows 7 machine, I know you had the one machine with multiple devices showing up and I told you about deleting them. Did you happen to try doing a clean install on the -other- Windows 7 machine, with the updated INF I posted? I didn't realize you had two. If you already tried it on both, nevermind.
So I'm still having no luck with the driver.
I've managed to bypass the signature enforcement by booting with the 'allow unsigned drivers' mode and also running windows 7 in 'testmode' with cmd. So no more driver prompts.
However I keep getting the error
"Failed to update chatpad filter device driver: 0xe000020b"
Just to make sure I'm not missing anything obvious:
1. Did you make sure to manually uninstall the devices mentioned in the Troubleshooting section of the getting started guide (HID-compliant mouse, 360 controller mouse for chatpad, etc.)? It might be good to post a device manager screenshots with certain categories expended like I posted earlier.
2. Did you then use the latest 0.0.3a install zip, running the installer while the controller is plugged in and already showing up in the device manager?
3. If the answer to both of the above questions is yes, could you please delete/backup your C:\Windows\INF\setupapi.dev.log file, run the installer one more time, and email/upload the log somewhere so I can view it? Hopefully that will tell me why it doesn't even install for you.
I've gotta step out for a bit, but I'll get back to you on that in an hour or so.
So run through this quick:
1. Yes
2. Yes
3. Okay, I'll do it!
EDIT: I'm actually going to go back to a restore point of a week ago and redo all of this again very meticulously.
Well don't waste too much time. The log and device manager screenshots might be helpful, but it's probably some bug on my part. It's just frustrating for me since I did the clean Windows 7 install and it just seems to install and work, yet obviously it's different on different systems. Thanks a lot!![]()
GAFBlizzard: i fully cleaned the list, i made screenshots of how it looked after that... (i undocked my laptop > lenovo thinkpad 500, because i had a keyboard mouse/attached to that, plus already had a logitech bluetooth receiver in it, so that where 3 mice, 2 keyboards..)
but after doing so, trying to reinstall the driver, after uninstalling it... it completely locks my system, guess it brings the kernel to its knee's some how ( i have no stopcode/bscode)
after uninstalling, i couldnt boot in 'without driver verification mode..', i kept getting wdf01000.sys giving bluescreens, 0x0000000c9
then booted in normal mode, that went ok
im done with booting on this laptop for today, will try another machine tomorrow / unless you have a really good idea
Bookmarks