FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: eren on January 16, 2013, 01:08:38 am
-
Dear All ,
Yesterday I bought GSX.But I got a problem about installing.First I was installed GSX which one as I had from official website.When I was run FSX it was ask me for ADD-ONN Manager.I olso installed ADD-ONN Manager But stil I got error massage same like picture.I'm try to solve this issue I found this topic from our forum( http://www.fsdreamteam.com/forum/index.php?topic=6765.0;prev_next=next#new ) I did everthing but stil I got problem.Please help me about this issue
Thank for your attentions
Best Regard
eren
http://i1299.photobucket.com/albums/ag72/Eren_Gunkaya/error1_zpsfd625e1e.jpg (http://i1299.photobucket.com/albums/ag72/Eren_Gunkaya/error1_zpsfd625e1e.jpg)
-
stil I got error massage same like picture
The most important thing that message tells you, is that you can see what the error was, by checking the Couatl.err file, and indicates you the exact folder where this is located.
Can you post the content of your Couatl.err file ?
-
First of all thanks for your quick answer I found Coualt.Err in the AppData/Roaming/Virtuali folder I open error file whit notepad you can see below that was writing there
couatl v2.0 (build 2337)
panic log started on Tue Jan 15 23:42:34 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Tue Jan 15 23:43:14 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Tue Jan 15 23:46:40 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Tue Jan 15 23:47:17 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Tue Jan 15 23:50:31 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Tue Jan 15 23:51:53 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Tue Jan 15 23:52:29 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Tue Jan 15 23:53:06 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Tue Jan 15 23:54:20 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Wed Jan 16 00:40:45 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Wed Jan 16 00:41:22 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Wed Jan 16 00:48:31 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Wed Jan 16 00:49:07 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Wed Jan 16 00:49:43 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Wed Jan 16 00:50:21 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Wed Jan 16 00:50:57 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Wed Jan 16 00:51:33 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Wed Jan 16 00:52:09 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Wed Jan 16 00:52:47 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Wed Jan 16 00:53:23 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Wed Jan 16 00:53:59 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Wed Jan 16 00:54:34 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Wed Jan 16 00:55:10 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Wed Jan 16 00:55:46 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Wed Jan 16 00:56:22 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Wed Jan 16 00:56:58 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Wed Jan 16 00:57:35 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Wed Jan 16 00:58:12 2013
Executable integrity compromised
couatl v2.0 (build 2337)
panic log started on Wed Jan 16 00:58:48 2013
Executable integrity compromised
Thanks For Your Attentions
Best Regards
eren
-
If you searched in the forum using the "Executable integrity compromised", you would have found several discussions about this, it's a problem caused by another product (probably non-flight sim related) that is using very dangerous methods to attach to all your running programs.
One of the most common causes, is the "ATI Tray Tool" utility, with the "automatic overlock" feature turned on. But if you don't have that one, there might be similar products, one user had it with a power management utility.
-
Dear Umberto,
I had searc error massage forum as you said.I founded 2 topic about this ıssue
1-http://www.fsdreamteam.com/forum/index.php?topic=6923.0
The "Integrity compromised" problem is caused by "Lenovo One Key Theater". After disabling it, the couatl engine works fine now.
But the GSX installation error message still exists.
Please see attached screenshot.
I did same like that but error stil there (olso Im using LENOVO)
2-http://www.fsdreamteam.com/forum/index.php?topic=7817.0
Hello
Problem solved. There was a false bglXXX file in FSX directory. Have this deleted, then ran it.
Thank you!
regards
G. Sauerborn
I m did same but which bgl file I couldnt find?
Is there any options for solve this problem I bougt 3 GSX my other 2 friends use whit out any mistake but I m stil waiting for this issue I m try everthing I m gonna be crazy.
Thanks For Your Attentions
King Regards
eren[/b][/i][/size]
-
I did same like that but error stil there (olso Im using LENOVO)
Then you probably haven't correctly removed the offending program which is causing this.
-
I had removed program.I guest that was not about that program
-
I had removed program.I guest that was not about that program
It was probably *another* program. As I've said, there might be more than one. The ATI Tray Tool and the Lenovo tool is just two we know about, but that doesn't mean there aren't any.
Try to quit all the running processe one at the time, you'll eventually find who's the offending one.
-
I'm going to be crazy.Still the same problem continues,What must I do ? have someone who can help me ?
-
As I've said, the problem is caused by a resident program you have installed in your system that attaches to all executable (it might even be a real virus), so the solution is:
Try to quit all the running processe one at the time, you'll eventually find who's the offending one.
-
Yes finally i solved my problem. 8)
That was about my computer LENOVO I uninstall lenovo one keytheatre and its done.If you take any error same like that, and ıf you use lenovo you must uninstall one key theatre.
and thanks to Umberto Colapicchioni for your attentions and direcktions.
-
Congratulations on your detective work! I don't know whether I would have thought of that particular step, although I have learned to beware of any special key or software that "enhances" a computer or its peripherals. That's especially true for laptops. If you're having problems getting a program to work as it should, try uninstalling the software for these features. (Before you do that, make sure you can reinstall it if you find that it's not the cause of your problems.)