PHP output file(s) are missing or blank :: 64-Bit OS

[own3mall]

Hi All,

I'm running CSE HTML Validator Standard 10.02, and I can't seem to get PHP Syntax checking to work on my Windows XP x64 SP2 64-bit machine. When I was running a 32-bit OS, I was able to use the PHP syntax checking option. Now, on my 64-bit OS, I get this error when trying to check my syntax:

The PHP output file(s) are missing or blank. Is PHP and all its supporting files installed correctly?

I have the PHP validation options set to the path of C:\Program Files (x86)\PHP\php.exe, and I've also tried using C:\Program Files (x86)\PHP\php-win.exe. After I save my settings, I still get the error constantly, and it never works. Anyone know how I can get this to work in a 64-bit OS?

[Albert Wiersch]

Hello,

It should work if setup properly. I have been using 64-bit systems for years now.

Please see this link (especially the troubleshooting section):
http://www.htmlvalidator.com/htmlval/v1 ... r_node.htm

Here's the PHP Downloads page:
http://www.php.net/downloads.php

Download the Windows binaries, probably the zip file, and extract all the files to your PHP folder. Either the non thread safe or the thread safe versions should work.

I hope this helps.

[own3mall]

Well, I had to do this step to get it to work sometimes:

If using a php.ini file, make sure display_errors is set to "On".

However, it takes about 7-10 tries before it actually validates and doesn't return the "The PHP output file(s) are missing or blank. Is PHP and all its supporting files installed correctly?" error. At least it's working sometimes now, but why doesn't it always work?

[Albert Wiersch]

However, it takes about 7-10 tries before it actually validates and doesn't return the "The PHP output file(s) are missing or blank. Is PHP and all its supporting files installed correctly?" error. At least it's working sometimes now, but why doesn't it always work?

It could be your virus/security software interfering. If you turn it off, then does it work? You may also want to consider upgrading to v11. There were some changes made to address issues that might be contributing to this problem.