Thread: CONTEST: Xbox Chatpad Driver Challenge

@GAF

Try this, it work for me.

Originally Posted by ddxcb

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.

I got the abominable blue screen of death a few minutes ago when I unplugged my controller from the USB port. I figured I'd post as much info as I could, in case it was caused by the chatpad... which of course is a good possibility lol. (Just for the record, it has worked wonderfully for me aside from this )

Some general info:

Using Windows 7 Ultimate x86
Chatpad "serial" is: X814365-001
Had chatpad_control_i386.exe open when it happened
Simply unplugged the USB connection... I didn't see anything for safe removal in the notification area.

Not much else I can really report, other than this log I found in the Event Viewer (eventvwr.msc):

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

And this under details:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2011-01-02T05:27:18.253213600Z" />
<EventRecordID>26275</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Kevin-Media</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="BugcheckCode">127</Data>
<Data Name="BugcheckParameter1">0x8</Data>
<Data Name="BugcheckParameter2">0x807c8750</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>

[EDIT]
It happened again... this time I caught a glance of the stop code: 0x0000010D

I had the chatpad utility open again this time; on the other hand, I tried unplugging the controller without it running... no BSoD.
[/EDIT]

[EDIT]
It appears to be caused by my specific setup >_< I'll try to explain this best I can.

I had a shortcut under the Startup folder in the start menu that launched the EXE automatically. This is the command I used to do it:

C:\Windows\System32\cmd.exe /C "C:\Chatpad\chatpad_control_i386.exe"

My thought process for doing it this way was that by setting it to cmd.exe instead of directly to the chatpad EXE, it could be started initially minimized. *In retrospect* I realize that I could have accomplished this either way.

Anyway, doing it "the hard way" as I did, unplugging the controller causes the BSoD. If you launch it directly, it works fine. D'oh!

So in the very unlikely event that anyone else, now or in the future, does it this way... Don't.

That will be all.
[/EDIT]

@kevinmd88

ya dont unplug the controller when the chatpad_control.exe is running.

very bad xD

Thanks for the reproduce method...I was going to say I was having a hard time deciphering the blue screen otherwise. If I can get it to reproduce I should be able to track it down, thanks! Unplugging the controller shouldn't crash things, but I probably didn't try it while running the control utility.

Well, what I was trying to explain in my last post is that it doesn't crash your system, as long as you open it properly.

@GAFBlizzard

I try to include as much info as I can when problems arise. Haha. Anyway, the following is a completely uneducated guess... but... Could the exit code have something to do with it? Maybe the actual command prompt doesn't like it...

To find out how the XBOX 360 Wireless controller (connected with the chatpad) communicates with the XBOX console. So it can be implemented in the Windows/Linux drivers (GAFBlizzard and Grumbel wrote). We need to hook in a usb-analyzer between the XBOX 360 motherboard, and the RF module, that is used for communication with the controllers. As Grumbel / I pointed out earlier, the RF module is a USB device.

I am able to spend money on a XBOX 360 for this.. but the usb-analyzer, for me, this is a problem.

if someone reading this is able to borrow me a USB analyzer, then i'm sure we can get the wireless done

otherwise, i will have to wait till the OpenVizsla ( http://www.openvizsla.org/ ) analyzer becomes available, and buy that.

That may take a few months tough.

Just wanted to chime in and say that Windows recognized my 360 headset when I plugged it in via the chatpad.

just wondering if anybody could help me. I still cant figure out how to get backslash with chatpad using uk keyboard layout.

Originally Posted by masterfaz

just wondering if anybody could help me. I still cant figure out how to get backslash with chatpad using uk keyboard layout.

There's a fix for that, but I need to get the latest source files off my laptop, and include it in the next overall driver release. If you need it sooner, I can do a test build of just the control utility for you.