hello to all that still read this. i just spent the last few hours( granted i read semi-slow) reading all the posts on this form, and i can't belive that nothing is out there for the chatpad and windows. i accually live near one of the microsoft buildings here in charlotte, NC and have now thought about goin' to protest this issue... lol.
anyways, i too want to do anything i can to help this process along. i have some exp. with c++, java, vb, and understand a good bit of C#. So if yall need me, let me know.
oh, and i too fell victim to buyin' the 360 controller and got the chatpad thinking: 'it's all microsoft, it should work' WRONG!!!!! ms has gotten lazy it seems, as you all definitly seem to know.
Guys?! anybody ahs even tried lookign at the os x logs i posted??
I don't really knwo much about usb and I'm stuck trying to send basic things through a WDM driver ..... I have looked at them and i think a single keypress boils down to
(remember this is for the A key)
So this confirms the hex 37 for the A key. If we go back a bunch of pages we can see that some people managed to use a linux usb lib to receive aa single keypress.
00540.076 UHCI::FilterInterrupt (0x0564c000) active interrupts 0x0001
00540.106 -> UHCI::Begin HandleInterrupt (0x0564c000)
00540.107 UHCI::HandleInterrupt (0x0564c000) Processing interrupt USBSTS = 0x0000
00540.109 -> Controller::Return Isoc Done Q Start (0x0564c000) pEP 0x59eb200 pTD 0x0
00540.109 <- Controller::Return Isoc Done Q End (0x0564c000)
00540.110 -> Controller::Return Isoc Done Q Start (0x0564c000) pEP 0x59eb280 pTD 0x0
00540.110 <- Controller::Return Isoc Done Q End (0x0564c000)
00540.120 Controller::Complete (0x0564c000) completion: 0x925106, status: 0x0
00540.121 Controller::Interrupt Complete (0x0564c000) Bus: 0x1a, Address: 3, Endpoint: 6, (in) actual: 5, status: 0x0
00540.124 Controller::Interrupt Complete Data (0x00000000) Bus: 0x1a, Address: 3, Endpoint: 6 (in) length: 5, data: 0x00003700 0x00ff0000
00540.124 Controller::Complete (0x0564c000) completion: 0xfd9db6, status: 0x0
00540.204 -> Controller::Interrupt Start (0x0564c000) Bus: 0x1a, Address: 3, Endpoint: 6, (in) reqCount: 32
00540.211 <- Controller::Interrupt End (0x0564c000) error 0x0, (completion timeout: 0, noData timeout: 0)
00540.215 <- UHCI::End HandleInterrupt (0x0564c000)
just to throw an idea out there. It seem each keypress triggers an interrupt does these libs reset the interrupt after receiving the letter. Also note the second dword 0x00ff0000 maybe this is some sort of keyreleased thing... theres also that ischronous bit that I don't understand... anyway ... USB people out there... any ideas?
Can you also grab a log of just using the actual xbox controller?...press a button on that and lets compare that to the A key example. The problem i'm having is that no interrupts are triggered when a button on the chatpad is pressed only the xbox controller so i'm wondering if its a separate device.
Originally Posted by jeduars
ok, i'll post those later tonight
I'm still trying to get those log files, I'm in the middle of moving to a new apartment so I haven't had any time? has anybody tried to read the extra dword or send the completion with those usblib thingies?
I want to compare the hardware ids first...I think that may give me an explanation for the lack of data.
have you looked at post number #316?
you might be able to find the hardware ids there. Which hardware id's are you specifically talking about?
I need to see the xbox controller itself in use...not the chatpad...so I can compare the two