jimmyliu86 / chatpad-super-driver

Automatically exported from code.google.com/p/chatpad-super-driver
0 stars 0 forks source link

The functionality of the controller is lost after installing the driver. #17

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Steps to reproduce:

1. Install the "chatpad_installer_amd64.exe" driver.
2. Reboot.
3. Observe.

What is the expected output? What do you see instead?

The expected output is the normal functionality of the Chatpad, although not 
only that the Chatpad does not function but the controller also lost 
functionality.

What version of the product are you using? On what operating system?

The issue was reproduced using the 0.0.3a version of the driver for a wired 
PC/Xbox360 Controller on Windows 7 Ultimate x64.

Please provide any additional information below.

After running "chatpad_control_amd64.exe" in an administrator command prompt 
window, the following message was displayed: "Failed to open connection to Xbox 
360 controller.".

Original issue reported on code.google.com by gopo.dre...@gmail.com on 12 May 2011 at 1:28

Attachments:

GoogleCodeExporter commented 9 years ago
I have the same issue. Running Windows 7 Ultimate x64. Version 0.0.3a

Original comment by Win7...@gmail.com on 3 Feb 2014 at 6:34

GoogleCodeExporter commented 9 years ago
At the time I was using a modified version of Windows which booted by default 
with "Disable Driver Signature Enforcement" ON. After experiencing the issue I 
switched back to the regular version of Windows and the driver worked properly. 
Keep in mind that you have to enable "Disable Driver Signature Enforcement" on 
every single boot. Also, if you want to never worry about the drivers ever 
again, download a tool called DSEO (look it up on Google) and with it switch 
your Windows to Test Mode, sign the drivers and remove the Test Mode watermark 
(I think you need to reboot between all of these actions). Afterwards, you can 
transform "chatpad_control_amd64.exe" into a system process using FireDaemon 
Pro, this will allow it to start automatically in the background whenever 
Windows starts. After doing all of this your drivers should be running like any 
normal drivers would, with no need for any user interaction.

Original comment by gopo.dre...@gmail.com on 3 Feb 2014 at 8:40