I just used Jotti Virus scan on it and I got this: http://bit.ly/e8Ep4V
Here's a new one. Does anyone happen to have Norton 360? Someone emailed me and said that the chatpad_installer_i386.exe executable on Vista is flagged as a threat. o_O
I just used Jotti Virus scan on it and I got this: http://bit.ly/e8Ep4V
I have bad luck with vehicles...
Right, I got this: http://www.virustotal.com/file-scan/...c09-1294006305
Apparently Norton 360 deletes the file though. I'm not sure whether it's before it even runs, or if it's responding to something the installer does. I'll edit this post if I find out.
thanks blizzard im in no rush to sort it, only time ive needed to use backslash is to create a destination folder when extracting .rar, was wondering if there was any edit to the config i could do to fix it
Does anybody have an idea how the Xbox360 detects the keyboard layout of the Chatpad or has anybody ever tried a foreign Chatpad on his native Xbox360? Is it just based on the language settings in the Xbox360 or does the Chatpad actually report its layout?
http://i54.tinypic.com/14imxlg.jpg
http://upload.wikimedia.org/wikipedi...60_ChatPad.jpg
Has anyone made any headway finding someone with a USB analyzer? I realize these can be prohibitively expensive, but if someone already has one, getting a used xbox360 will probably be fairly cheap... especially one prone to the good ol' RROD.
For my application, I don't see myself using the chatpad if it's not for a wireless controller, so of course that's the milestone I'm waiting for.
Just to update everyone on my current plans, I may get a wireless controller and dongle anyway, prize or no, if nobody else figures it out.
But, I don't want to do any wireless stuff until I get at least one more wired driver release out, one that includes some bug fixes and working uninstall/update code (to avoid the duplicate device issue). I still haven't heard from aidan or chaos about whether their text file loading issue was fixed by the test build I sent them, unless I just overlooked some posts.
Grumbel, when i try to use 0x09, 0x00 instead of the 0x01, 0x02 (for testing purposes with my wireless controller) - i get a segmentation fault. My C++ knowledge is limited, but i dont understand why i cant assign 0x09 to the char variable buf, in chatpad.cpp
Do you know why this is?
for the rest, i did implement the Chatpad class into the Wireless cpp.. and the boost threads are running in the background (toggling, etc)
I just started following this thread and read from page 1 to the end lol. Great job Bliz and I'm also of the wireless sort but this may give me a reason to look at those Afterglow wired controllers again![]()
I am eager to help test the wireless drivers.
I have 4 xbox 360 controllers - all wireless.
* 2 x black Made For Windows 360 controller with receivers
* 1 x white XBOX360 wireless controller
* 1 x white XBOX360 wireless controller
* 1 x black XBOX360 chatpad
* 1 x XBOX360 communicator headset & microphone (came with chatpad)
* 1 x XBOX360 throat mike with earpiece
I have access to 360's (but can't do tinkering on them).
I have lots of programming experience, but start to get annoyed when it's C code without managed memory... :P
When I don't have ANY drivers installed for the controllers, they work fine as long as I don't try and resync them after booting.
However, once I install 1.1 OR 1.2 windows drivers I can't get any of the 4 controllers to sync with EITHER of the receivers.
Chatpad - no experimentation with yet, other than using the throat mic and normal communicator with it plugged in. The communicator is fine, but for some reason it *feels* like the throat mic uses more CPU and thus jitters. It could be my imagination.
Great work GAFBlizzard, and to get this working for wireless I will be willing to donate some money, $20AUD if more funds are needed for, say, taht stupid USB disector doobey.
I have no experience reverse engineering USB protocols, other than using one of those advanced programs which remaps keys via low level protocols (e.g. remapping a function key on a laptop to be ALT). But will gladly be a test monkey.
Bookmarks