Hello,

"Timeout Error InternalTerminate" this is the message that I get after a while, trying to startup the IDE.
It takes always a lot of time, during it the IDE hangs, mouse hangs.. and after some time the IDE opens and
give me the error message.

This happens to me, since I upgraded to build 5933, and without using the debugger, just starting the program!

Any suggestion? Like this, I cannot work anymore... I would like to be able to run the IDE "normally" without all
these problems..

I am using NuSphere PhpED Professional version 5.9 (Build 5933) with php 5.2.6 and Apache 2.2.10

Thank you very much for help,

Giul

the same with me. the error reads:

IDE Timeout error.InternalTerminate

no more info is given.

symptoms are the same: laggy experience, file opens last long, file deletes last long, code navigator show nothing (exept file name), etc

this definitely needs a fix!

any thoughts from the developers?

i use 5.9 Build 5932

Same problem here. Did you ever resolve the issue?

I have no problems with build 5936.

I am also getting this error. It seems to lessen if I only have 1 project in a workspace but still happening. The more projects I have the longer it takes for the hang and error to be thrown.

running ver 5.9.5 build 5982

Is there a fix for this?

There is a problem that I'm having with the software. Time outs and application hangs. How does one get support?

Searched thru the FORUM and only found two threads for the subject matter.

Made a clean install of 6033 and have compatibility set with WinXP SP2. I am running Win7HomePrem.

Have run into this issue a couple times and think the last time using RUN AS ADMINISTRATOR for the install seemed to help it, but did not do much for me this time.

Am hoping someone has a GOOD FIX for this cause it basically makes PhpED unusable. Have not been able to run it for more than a minute before I get the following error:

IDE Timeout error.InternalTerminate

and the application goes out to lunch. Sometimes it makes it back, sometimes I get tired of waiting.

It has to be a compatibility issue cause I do not recall getting these errors back on WinXP.

Any help would be appreciated.

LarryG