"Couldn't open chatpad filter: 2" Control not working

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install worked fine
2. Tried to run the Control as administrator from which it crashes and then if 
I use cmd to run it the window doesn't crash but I get the same message and it 
stops running.

This is what it says:

*****
Chatpad control utility version 0.1a started.
*****
Please wait...

Control utility started.
Opening chatpad filter driver.
Couldn't open chatpad filter: 2
Failed to open connection to XBox 360 controller.
Done. The exit status is -1.

I do not know how to fix this?

Original issue reported on code.google.com by Aspra...@gmail.com on 16 Mar 2011 at 2:26

[GoogleCodeExporter]

Having much the same problem. Only difference is I didn't have to run it using 
CMD, I was able to run it just fine from an Administrator opened Command Prompt/

Installed and everything seemed to go okay.

When I ran chatpad_control_i386, the command prompt instantly crashes at Please 
Wait...

Opened an administrator Command Prompt and re-ran the file, and got the 
following.

*****
Chatpad Control Utility Version 0.1a started.
*****
Please wait...

Control utility started.
Opening chatpad filter driver.
Couldn't open chatpad filter: 2
Failed to open connection to XBox 360 controller.
Done. The exit status is -1

I am running a windows XP system, and the controller is currently plugged in 
with the current drivers from MS.

Hope this helps, and Hope you can figure out a solution! This would be such an 
awesome thing for my home entertainment setup.

Original comment by BlackFo...@gmail.com on 30 Mar 2011 at 12:12

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Works! same problem: i was trying to install from a drive other than c:  
moved the files to C:ProgramFiles and everthing worked! (eventually)

Maybe that should have been common sense, but maybe it'll help someone else 
with this prob. 
 :D

Original comment by surgezi...@gmail.com on 25 Apr 2011 at 3:12

[GoogleCodeExporter]

exact same problem, and I have the files on the local C drive.  Any other fixes 
for this?

Original comment by neisl...@gmail.com on 27 May 2011 at 3:11

[GoogleCodeExporter]

I am using Win7 64-bit with a wired controller for PC and a Chatpad from the 
Messager Kit
  I have tried all 3 of the win7 tests and none of them have any other response then:

*****
Chatpad control utility version 0.1a started.
*****
Please wait...

Control utility started.
Opening chatpad filter driver.
Couldn't open chatpad filter: 2
Failed to open connection to XBox 360 controller.
Done. The exit status is -1.

I'd be happy to provide any more information, I'm just not sure what you need.

Original comment by neisl...@gmail.com on 27 May 2011 at 5:10

[GoogleCodeExporter]

Control utility started.
Opening chatpad filter driver.
Couldn't open chatpad filter:  2
Failed to open connection to XBox 360 controller.
Done.  The exit status is -1.

Windows Vista SP2

I got this to work once, but it gave me a BSOD about 5 minutes after I started 
using it. Ever since, no matter how many times I reinstall, it won't run. I've 
already tried removing all drivers associated with it before reinstalling, with 
no luck.

Original comment by scottj.b...@live.com on 6 Sep 2011 at 6:16

[GoogleCodeExporter]

The first time I installed this just fine. I ran the controll utility and got 
blue screen right after it started showing text. 
After I rebooted and I uninstalled everything and reran the install I get the 
same error these guys are having.

Control utility started.
Opening chatpad filter driver.
Couldn't open chatpad filter:  2
Failed to open connection to XBox 360 controller.
Done.  The exit status is -1.

_____

My OS is win7 64

so pretty much im having the exact same error.

When we extract the files from the .zip are we supposed to place them in some 
sub folder to run it or do we just run it as is?

Original comment by spitfac...@yahoo.com on 26 Dec 2011 at 7:12

[GoogleCodeExporter]

Same problem. Win7 64 bit.

Original comment by Preston....@gmail.com on 29 Jan 2012 at 9:58

[GoogleCodeExporter]

Same problem with Windows7 64bit. The filter driver makes my controller 
unusable/unrecognized. I had to install the official version to get my 
controller working.

Original comment by floogc...@gmail.com on 5 Feb 2012 at 3:10

[GoogleCodeExporter]

Same problem as OP. Installed everything seemed fine, but control exe closes 
immediately, have to run it from cmd elevated. Win7 64bit Ultimate. Under the 
device manager, the "XBox 360 controller filter driver for chatpad" Has a code 
52. the controller HID Keyboard for chatpad and mouse also have code 52s.

Original comment by NJSmith1...@gmail.com on 19 Sep 2012 at 11:19

[GoogleCodeExporter]

Same Error here.
Win7 64-Bit Ultimate

In Device-Manager the installed drivers from here are marked with yellow 
exclemationpoint, means Error 52 on each of the 3 devices.

My Controller can not connect to the system after restart anymore. The 4 LEDs 
are flashing whole the time.

I have already uninstalled the drivers by the uninstaller in the package, then 
uninstall manually in Device-Manager, then delete the rest in system32/drivers.

My system automatikly starts in Testmode, what means that the F8 mode is always 
disabled and i can install unsignied drivers when ever i want it.

Do not now what the issue is but in my opinnion there are not on each 
controller the same hardwareID. This means the driver here has to look on 
install for the rigth one or we has to change the HW_ID manually in the driver 
configs, but in time i was unable to find the entry...

Original comment by Fekalien...@googlemail.com on 28 Sep 2012 at 5:17

[GoogleCodeExporter]

lol wut?
Is there a solution to this one?
I got the cannot find the .txt & had to CMD\help & remember how to use the dang 
ol' thing.
 Now I get this exit status -1.
How do I shot web?

Original comment by Benjamin...@gmail.com on 23 Jan 2013 at 11:36

[GoogleCodeExporter]

Man, is there still no fix for this....? I really want to use chat pad, and 
i've gotten this far, am I just SOL?

Original comment by glock...@yahoo.com on 21 Jun 2013 at 8:23

[GoogleCodeExporter]

I am having the same issue. 
I hope someone decides to fix this soon!

Original comment by hallje1...@gmail.com on 29 Jul 2013 at 7:34

[GoogleCodeExporter]

Win7 Ultimate SP1 ::
I got the same error just after installation process. 
I restarted my notebook, chose "Disable Driver Signature Enforcement" in 
'Advanced Boot Options' (F8 after BIOS) and it works like a charm :)
Hope it helps and huge, huge thanks for those drivers!

PS.
"GettingStarted" wiki, under 'disabling driver signature enforcement', actually 
states: "You will need to choose that option with each boot for 64-bit systems, 
until we potentially get a kernel signing certificate." 

Original comment by gaertne...@gmail.com on 29 May 2014 at 1:32