By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,557 Members | 1,406 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,557 IT Pros & Developers. It's quick & easy.

Apache 2.2.2 and PHP 5.1.4 on Win2k crashing

P: n/a
I just installed Apache 2.2.2 on my Windows 2000 (SP4) machine to test
the new version.
Everything works except PHP (version 5.1.4): when starting Apache, it
pops out a message saying that it is unable to locate the module (even
set on the correct path!), stops the execution and exits. On the other
side, PHP works fine with Apache 2.0.55, so It's not a problem of a
broken build.

Got ideas?
Thanks.
--
Massimo Lombardo

Jun 12 '06 #1
Share this Question
Share on Google+
6 Replies


P: n/a
un**********@gmail.com wrote:
I just installed Apache 2.2.2 on my Windows 2000 (SP4) machine to test
the new version.
Everything works except PHP (version 5.1.4): when starting Apache, it
pops out a message saying that it is unable to locate the module (even
set on the correct path!), stops the execution and exits. On the other
side, PHP works fine with Apache 2.0.55, so It's not a problem of a
broken build.

Got ideas?
Thanks.
--
Massimo Lombardo


The binary interface of Apache 2.2 is different from that of Apache
2.0. You can't use the same DLL. If you really want to use Apache 2.2,
then you have to recompile the SAPI module yourself.

Jun 13 '06 #2

P: n/a

Chung Leong wrote:
The binary interface of Apache 2.2 is different from that of Apache
2.0. You can't use the same DLL. If you really want to use Apache 2.2,
then you have to recompile the SAPI module yourself.


Or wait for the new build from php.net, right?

Jun 13 '06 #3

P: n/a

un**********@gmail.com wrote:
Chung Leong wrote:
The binary interface of Apache 2.2 is different from that of Apache
2.0. You can't use the same DLL. If you really want to use Apache 2.2,
then you have to recompile the SAPI module yourself.


Or wait for the new build from php.net, right?


Which might take forever. Apache 2.2 is not exactly taking the world by
storm. Unless you need to server 2gig+ files, I don't see a reason to
upgrade.

Jun 13 '06 #4

P: n/a
Chung Leong wrote:
Which might take forever. Apache 2.2 is not exactly taking the world by
storm. Unless you need to server 2gig+ files, I don't see a reason to
upgrade.


Ah. Wow. Great. I have no 2+ GB file to serve...
Version 2.2: trashed.
Thanks.
--
Massimo

Jun 14 '06 #5

P: n/a
un**********@gmail.com wrote:
I just installed Apache 2.2.2 on my Windows 2000 (SP4) machine to test
the new version.
Everything works except PHP (version 5.1.4): when starting Apache, it
pops out a message saying that it is unable to locate the module (even
set on the correct path!), stops the execution and exits. On the other
side, PHP works fine with Apache 2.0.55, so It's not a problem of a
broken build.

Got ideas?
Thanks.
--
Massimo Lombardo


Yeah, Windows 2000 kind of sux... I'm running XAMPP fine on Windows XP
though, although I'd use Linux if I could.
Jun 16 '06 #6

P: n/a
Jackson Scott Peebles wrote:
un**********@gmail.com wrote:
I just installed Apache 2.2.2 on my Windows 2000 (SP4) machine to test
the new version.
Everything works except PHP (version 5.1.4): when starting Apache, it
pops out a message saying that it is unable to locate the module (even
set on the correct path!), stops the execution and exits. On the other
side, PHP works fine with Apache 2.0.55, so It's not a problem of a
broken build.

Got ideas?
Thanks.
--
Massimo Lombardo


Yeah, Windows 2000 kind of sux... I'm running XAMPP fine on Windows XP
though, although I'd use Linux if I could.


Things should improve on the Windows front now that Microsoft has
released a free version of Visual Studio, which will expand the pool of
developers who can compile from source. VC6 is really ancient (it was
designed for WinNT). Even if you are willing to pay for it it's not
easy to find.

Jun 16 '06 #7

This discussion thread is closed

Replies have been disabled for this discussion.