Don't get me wrong, I'm not saying there is an 'error' in couatl, I'm just saying there is a problem with it. There is.
But there isn't. The problem is in the other software that we'll eventually identify (since you seem to be sure it's not the antivirus, it must be something else) that is causing Windows to wrongly believe Couatl.exe is not a valid Windows program, when it clearly is.
A google search for couatl shows that there are numerous problems in running it.
But as I've said, NONE of these were fixed by having to change something in it, ALL of them were caused AND fixed by acting on something else, being the antivirus, or else.
Any program that refuses to run on so many systems (as shown in these forums for example) has a problem.
No, it doesn't. It only causes a problem which you already had to surface. It would have, eventually, regardless of Couatl.
It may well be caused by something else on the system but couatl should have error trapping algorithms that explain the problem or get around it.
That's not the case. We are discussing on something that happens even BEFORE Couatl has the chance to start. So, there's not "trapping" that Couatl can do, if it doesn't even get the chance to start.
I've been using computers for almost 40 years and have never come across a professionally written piece of software of this size that doesn't 'get on' with other kids on the block.
Then you must have been very lucky...and size doesn't have anything to do with it. Couatl is small because it's pure executable code written in C++, and the .exe is just a small part of it, since if you check its folder, you'll find hundreds of support files.
But as I've said, any discussion about its own complexity, as if that might be an indication of the chance to have undetected bugs, is not relevant in this context at all, since the program doesn't even get a chance to start, so the issue is entirely related to the OS, being tricked by something that it's not supposed to allow that .exe to start.
I have done EVERYTHING suggested on your forums
If still not running, it can only means there are other things you haven't tried.
Removed antivirus (didn't really like that idea)
Nobody told you to do that. The solution about the antivirus was always to:
- Download and install when it's OFF
- Configure it properly to exclude the Couatl.exe file from scanning.
- Turn it back on
re-downloaded gsx
re-installed gsx
Since the problem is caused by something external to any of our products, you must act on those external causes.
Are you seriously suggesting I wipe my hard disk, reinstall windows, reinstall P3D just so I can use GSX. It ain't going to happen.
Nobody told you that of course. Yes, the problem will likely be fixed that way, eventually proving it was never GSX to begin with, but I haven't said to do that.
I have noticed that in several of the threads on this forum you are obviously very passionate about your program, I understand that, and any suggestion that there may be a problem with it is dismissed out of hand informing the writer that it is their fault as there is nothing wrong with your program.
No, I'm only sticking to the facts. And facts are, in all the these threads you are referring to, it ALWAYS turned to be something else.
I'll repeat it again: NONE of the problems that were caused by Couatl.exe not even starting, were NEVER, EVER fixed by changing something with it. There were ALL fixed (and they all were) by doing something else, finding the offending products, fixing whatever system problem the user already had, which affected Couatl.
It just needs to be error trapped more so it can get along with the others.
You mean, trying to find which of those "other", is causing the issue, and not getting along with it.
Do you have a policy on refunds?
Surely not, because all our products are sold in Trial version, and the whole point of having a Trial version, is that you can check for any incompatibility with your system and/or your other installed products, because you can download and install BEFORE purchasing. This is of course explained on the License agreement you must agree on in order to complete the purchase, if it wasn't already logical that a product sold in Trial version, doesn't usually come with a refund policy for reason that "it doesn't work", because you are given plenty of chances to check it does.
But of course, not having a right to a refund, doesn't mean you will not be supported until the problem is fixed so, let's try it again.
You can start by trying to identify what OTHER program you are running which might cause this. Try, for example, to disable every other .EXE that starts with P3D, by setting the line
<Disabled>True</Disabled>
in the %APPDATA%\Lockheed Martin\EXE.XML file. Disable them all, except Couatl.exe of course, and if it runs, you would KNOW it's something that runs together with P3D.
If still doesn't work that way, you would know is NOT something that runs with P3D, but something that start/runs in Windows.
Knowing this, could be a starting point.
