Open GoogleCodeExporter opened 8 years ago
Ive found this could be caused by not changing directory when in command
prompt, and instead typing out the full path and running the exe. Also, if you
click and drag the control exe into the command prompt and try running it like
that, which ends up being the same thing.
Original comment by guam...@gmail.com
on 5 Jan 2011 at 10:53
I am Also having the same problem it gives me exit code = -1
Original comment by zcle...@gmail.com
on 26 Feb 2011 at 7:43
wierd, are you running the utility from an administrator command prompt, and if
so, exactly which commands do you use to do it?
Original comment by gtsche...@gmail.com
on 26 Feb 2011 at 8:47
well to tell you the truth I'm pretty sure I just opened the command prompt and
dragged the file over to the command prompt and I was opening it as an admin
yes...I even tried changing the directory and that didn't work either.
Original comment by zcle...@gmail.com
on 26 Feb 2011 at 9:43
Dragging the file to the command prompt will probably not work.
Try right clicking a command prompt shortcut, choosing run as administrator,
and then changing the directory like "CD C:\Chatpad".
Then, type "DIR" and hit enter, and make sure that you see "chatpad_config.txt"
listed. Lastly, type the name of the control .exe, and send me a screenshot of
the result when the error comes up if possible. You can email me at gtschemer
at gmail dot com.
Original comment by gtsche...@gmail.com
on 26 Feb 2011 at 10:26
I am also having these problems (windows 7 32bit)
Original comment by michaelm...@gmail.com
on 13 May 2011 at 6:35
Here is my command prompt result. I was unable to change the directory (as I am
not quite sure if I am doing it right) to see if the file is listed. :( But I
do have it on the desktop *shrug*. Ill just go ahead and post now for fear of
sounding even more stupid :)
Original comment by ADSAILOR...@gmail.com
on 1 Jun 2011 at 2:11
Attachments:
Maybe this will help. I uninstalled and reinstalled the C++ Redistributable,
and once I did, by running the .exe itself (not in Command Prompt; that still
gives the above error), there's a split second when a bit of data shows up. I
was able to capture it, so hopefully it will help with this problem.
Original comment by zeroslyr...@gmail.com
on 1 Jul 2012 at 5:55
Attachments:
This is Bliz -- to run the utility from the command prompt, you need to use the
command "cd C:\Users\jason\chatpad", or something like that, depending on where
you put the chatpad control utility .exe file. It looks for the config text
file in the current directory, and that is why you saw the first error.
For the second problem, are you using an official wired Microsoft 360
controller? It looks like it might be a compatibility problem. You can try
using this control file instead:
http://code.google.com/p/chatpad-super-driver/downloads/detail?name=win7_amd64_c
hatpad_control_test3.exe&can=2
As a last resort, you could try posting a screenshot of your device manager
(start menu -> run -> devmgmt.msc), expanding all categories that have anything
related to the chatpad or 360 controller. Sorry you're having problems!
Original comment by gtsche...@gmail.com
on 1 Jul 2012 at 3:57
I'm also having this problem here. The installer for the chatpad drivers seemed
to of installed just fine. (Though they have the yellow ! in the device manager
due to unsigned drivers.)
But for some reason the control executable can't find "chatpad_config.txt"
I also tried the test3 version with the same results.
Original comment by Zepherio...@gmail.com
on 22 Dec 2012 at 11:51
Attachments:
Oh jeez. That was my bad. I accidentally had completely skipped the F8 part of
the whole process.
The control file still didn't work after I had properly gotten the drivers
installed and enabled. Same error as before.
I executed the control file though the command prompt (drag and drop) with the
same results.
CD worked, though. With a "Couldn't open chatpad filter: 2" and "Failed to open
connection to XBox 360 controller." error.
Unplugging and replugging my controller fixed it.
I am still of course getting the "chatpad_config.txt" error by opening the
program normally. So if you do need any information from me I'll do what I can
to get it for you to fix it.
Original comment by Zepherio...@gmail.com
on 22 Dec 2012 at 1:06
Attachments:
ZerpherionUltima, if I understand you correctly, you can run the control
utility from the command line, but not from say, a Windows desktop shortcut?
If that's the case, just make sure that the chatpad_config.txt file is in the
same folder as the control utility, and make sure that the "run in" directory
in the shortcut properties points to that directory so the control utility can
find the config file. Let me know if that doesn't work.
Original comment by gtsche...@gmail.com
on 23 Dec 2012 at 8:20
I can only get the control utility to find the chatpad_config.txt file if I run
it from the command line, using the CD command beforehand.
Just launching the control utility by itself never finds the chatpad_config.txt
file. (Using a shortcut or otherwise)
The control utility is in the correct folder (with all the other chatpad
executables and the folders with the drivers) but it still cannot find the
config file unless I launch it from the console with the CD command.
Original comment by Zepherio...@gmail.com
on 24 Dec 2012 at 9:11
ZerpherionUltima, here are two suggestions:
1. Open your shortcut properties and upload a screenshot somewhere (or include
an attachment here), just so I can double check the properties.
2. Try copying everything in that directory to a different directory, named
something very simple in the C: drive. Maybe "c:\chatpad" instead of a more
complicated directory name, just in case that could be part of the problem.
Original comment by gtsche...@gmail.com
on 24 Dec 2012 at 11:35
I moved the entire folder to C and renamed it to chatpad, like you said. And it
executed just fine and found the config file without having to launch it from
the command line.
I haven't been running it from a shortcut. Every time I ran it I would just go
to where I extracted the files and run the actual control utility.
There isn't any compatibility options selected for the control utility, and I
have full permissions.
I didn't have the chatpad actually plugged in when I ran it the last time
though. It didn't give me any errors. Until I closed it, which it gave me a
BSOD when I closed it and had to reboot.
Original comment by Zepherio...@gmail.com
on 25 Dec 2012 at 12:31
I'm sorry about the BSOD...there are probably some that aren't fixed. :(
So it sounds like if you use the C:\chatpad directory it works? I don't know
what bug I have that makes it not work from somewhere else, but hopefully the
control utility will work for you now, as long as you plug the chatpad in
first.
Original comment by gtsche...@gmail.com
on 25 Dec 2012 at 7:53
[deleted comment]
haha, Yeah as long as I launch it from a less-complicated directory (and keep
the chatpad plugged in) it seems to work just fine for me.
Thanks a ton. Sorry for being a bother.
Original comment by Zepherio...@gmail.com
on 25 Dec 2012 at 10:53
Yes. I have the exact same issues described above. I'm *trying* to get it
working on a particular Windows 8 x64 machine.
Installed devices successfully, but then they have the exclamation due to
unsigned drivers. Even with extra administrative rights, driver signature
enforcement disabled. Windows 8 is a pain for this (I know)!
I've tried installing in various compatibility modes, but result is always:
There was an error while attempting to load config file "chatpad_config.text".
Done. The exit status is -1
Original comment by mrboz...@gmail.com
on 24 May 2013 at 11:19
mrbozack, have you tried running the control utility from the command prompt in
the same directory as the chatpad_config.txt file? Try also copying them both
to a very simple directory name, like "C:\chatpad" and run from there.
Original comment by gtsche...@gmail.com
on 31 May 2013 at 5:03
"Couldn't open chatpad filter: 2" and "Failed to open connection to XBox 360 controller." error happens to me too but unplugging and plugging back in doesnt fix it, niether does switching to another USB port.
Original comment by ZarathLe...@gmail.com
on 15 Oct 2013 at 10:19
Original issue reported on code.google.com by
gtsche...@gmail.com
on 29 Dec 2010 at 10:29