I've come across a problem that occurs on my NT 4.0 SP5 PC, that happens on someone elses but not the same way. Before you write this off as a configuration issue let me continue...

I've compiled my own (oh no I here you say) php.exe Thread Safe program with NO extra extensions added. Just the core PHP stuff. I've also downloaded and used the php4win.de pre-compiled binary and extensions and the same occurs.

So what is it that occurs? Basically if there is an error of some type (e.g. a timeout set in the php.ini file, or some other "fatal" error it will generate on my PC an "OleMainThreadWndName: php.exe - Application Error" message saying that "The instruction at0x41249623 reference memory at 0x41249623. The memory could not be read. Click on OK to terminate the application. Click on CANCEL to debug the application". I can get this to occur with a simple 3 second timeout within my php.ini file and running something that takes a little longer.

Now, I have Microsoft Visual C++ 6.0 Sp4 installed on my PC, hence the message to DEBUG the application. In particular I have a bit of code that will interegate an ODBC data source that will generate an error when it hits a certain database table (this is not the issue). An ODBC error will generate from PHP that again causes the application error. However, on a friends PC that is almost identical in configuration (NT 4.0 SP5) but WITHOUT MS Visual C++ 6.0 installed on his PC. Using the same php4win.de binaries his won't cause an application error for the timeout, but DOES cause a Dr. Watson error for the others. This leads me to believe that perhaps the PHP WIN32 version doesn't "cleanup" too well when an error occurs. Could someone try a simple timeout with MSVC60 installed? I'm very much open to suggestions there is some configuration issue, but given what I've explained above it would appear there is perhaps more to it than just that.

Any help would be greatly appreciated.

Regards,

Mike Berry-Porter
mikebp@gallery-software.com