Windows

 Required 
 softs 
You will need first to install ActivePerl to use W3Perl.
Fly (graphics) , gzip (compression) and wget (retrieve logfiles) binary tools are provided with the installation.

If you don't have access to your server's logfiles, you can install the Tag package which will generate logfiles on your server. Then Install the 'No Server' locally in order to retrieve your remote logfiles and process them (using the config-tag.pl configuration).

 IIS 

 Apache 
An installer is provided for IIS : w3perl-iis.exe

You can select on which website you want to install the package. The configuration file is ready to run.
An installer is available for Apache 2.2.1X : w3perl-apache.exe

Older Apache need a manual install.

 Abyss 

 No server 
An installer is available for Abyss Web Server
An installer is provided for user without server : w3perl.exe

Configuration file should be edited manually to reflect your settings or build from the w3perl online tool.

 Limitations 
Windows server can produce CLF (Common Logfile Format), IIS format or Extended W3C format. W3Perl can read any of those formats. Just select the one you want to use in the configuration file. Lots of different date string format are used with IIS server so you'll need to describe your date format in the administration interface. Select one of your logfile and edit it via Notepad to check the month/day/year format used.

Error are stored in an event database on Windows so no file are produced. But you can use redirection with an HTML error page for the different status code and your error pages will be logged in the logfile.

 Thanks 
The installation have been greatly enhanced thanks to the NSIS package.
W3Perl have been fully tested on Windows 2000, Windows XP and Windows Server 2003 and 2008. Positive feedbacks have been sent from Vista.