Catalyst uses very many CPAN modules, and I am sure that not all of them are pure perl.

I've compiled Catalyst using VS6, so if ActivePerl is compiled with the same compiler, and Apache and mod_perl the same, I don't think it should be a problem.

I have also tried using an older ppm binary of Catalyst but with the same results.

But I think I might have a problem with the hardware, because sometimes right after booting the system the computer doesn't start, but just keeps restarting and nothing appears on the display, and I need to power it off, wait a little then power it up again in order to make it boot. That problem might be the same that causes Apache not work and I think the issue might be the motherboard.

So I will try to change it, because it is under the warranty, and I hope after that Apache will also work.

Octavian

----- Original Message ----- From: "Foo JH" <[EMAIL PROTECTED]>
To: "Octavian Rasnita" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <modperl@perl.apache.org>
Sent: Thursday, October 04, 2007 8:34 AM
Subject: Re: Best version of Apache for Win32 deployment


Sorry man, I'm not too familiar with Catalyst, so I can't pinpoint the problem. But if your tests are good with a clean install of Apache2 + mp2, you may want to check compiler used to build Catalyst (see Randy's email on the VC used for ActivePerl, Apache, and modperl). I suppose Catalyst is not a pure-perl implementation?

Reply via email to