A2.0 causing page-lock crashes under W2K?

My main dev machine is a 2GHz P4 with 1G memory running W2Ksp4. Until
this morning, I've been running a dev environment of Apache 1.3.27,
PHP 4.3.0, and MySQL 4.0.20a. I'm typically connected to the Internet
by a Verizon ADSL line, but ZA Pro 3.1 prevents Apache from
advertising or serving outside my local system.

I've had that running for months with absolutely no problems.

This morning, deciding to up to PHP 4.3.7 to see if that fixed a funny
sessions problem I've been seeing, I decided to also up to Apache 2.0.
After an annoyingly large struggle, I finally got it to start serving
pages, though I had to de-install the v1.3 version and re-install the
v2 version several times. But I've been having multiple page-lock
crashes. Since these are the first page-lock crashes I've ever seen,
and I saw them before I succeeded in integrating the new PHP, my
immediate thought was that it's an Apache problem.

The funny part, though, is 2-3 months ago I upped to Apache 2.0 on my
laptop (same MySQL, but PHP 4.3.4), a P3/512Mb machine running W2Ksp3.
I have seen no problems at all with that installation.

Any thoughts?

TIA,
Margaret
--
(To mail me, please change .not.invalid to .net, first.
Apologies for the inconvenience.)

Margaret MacDonald <scratch65536 DeleteThis @att.not.invalid> wrote:
 > v2 version several times. But I've been having multiple page-lock

What you describe have been already described and usually due to
problems with antivirus/firewall software on Windows platforms.
Besides, on the PHP website they still suggest to _not_ use PHP 4
and Apache 2 togheter.

Davide

--
| Well, if you can't believe what you read in a comic book, what can
| you believe?!
|
|<!-- ~MESSAGE_AFTER~ -->