If your Web server isn't listed, check the server's documentation on how to set up a CGI interpreter. In general the process is as follows: Associate a file extension like .pl with the perl binary, and let the server know where the binary is. This may be a shell association, as described in question 4.10, or a custom association. Ensure that the user account that the Web server uses can read the script as well as any ancillary files (perl binary files, library files, modules, etc.).

Microsoft Personal Web Server for Windows 95 is a scaled-down version of Microsoft Internet Information Server. Although it is not documented, it appears that the method used to support Perl for Win32 with IIS will also work with Personal Web Server. See question 6.3.

Make sure that the bin subdirectory of your Perl directory is in the system PATH variable. This should be the subdirectory where perl.exe is located, such as C:\Perl\5.00500\bin\MSWin32-x86. Note that this must be set in the Control Panel, not on the command line, and it must be a system environment variable, not a user environment variable. Make sure that your script has the extension .pl. This is the only way that the https service recognizes the file as a Perl script.

Microsoft Internet Information Server (IIS) ships with Windows NT Server. Peer Web Services (PWS) ships with Windows NT Workstation. Configuring the products is essentially the same. First, you should consult Chapter 8, Publishing Information and Applications, in the IIS documentation. Also read the Microsoft Knowledge Base article covering this issue, "Configuring and Testing a PERL [sic] Script with IIS," (http://www.microsoft.com/kb/articles/q150/6/29.htm).

Most Windows NT and Windows 95 servers that use the CGI standard or ISAPI will run Perl for Win32 scripts. The following servers are known to work with Perl for Win32 (known protocols in brackets): Alibaba from Computer Software Manufaktur [CGI, ISAPI] http://emwac.ed.ac.uk/html/internet_toolchest/https/contents.htm Microsoft Internet Information Server [CGI, ISAPI] http://home.netscape.com/ mod_nsapi home page: http://interact.canoe.ca/~bsugars/nsapi_perl.

If you're using Netscape 1.x servers, you must wrap your Perl scripts in batch files. Refer to these Netscape tech notes: The following information is for Netscape FastTrack Server 2.0. Other 2.0 Netscape Servers (Communications, Enterprise) should be similar [? -ESP]. First, read the Netscape documentation. Next, read the technote on Shell CGI (http://help.netscape.com/kb/server/960804-35.html). Set up a "Shell CGI Directory" to run Perl scripts.

The following instructions are for Purveyor 1.2 for Windows NT. Other Purveyor products should be similar. In the Purveyor Control Panel, use the CGI Mapping tab to map the .pl extension to perl.exe. Make sure that you use the full path to the executable. Also in the Purveyor Control Panel, use the Virtual Servers section to set your CGI Scripts directory. You need one scripts directory for each virtual server you support. The scripts directory must be in the data path for the server.

The following information is for setting up O'Reilly WebSite to use Perl for Win32 for standard CGI (not PerlIS). Other O'Reilly servers (WebSite Professional) should be similar [? -ESP]. Associate Perl scripts with the perl interpreter, if you haven't already. See question 4.10 for how to do this. You may need to re-start the server after making the association. Set up a "Standard CGI Directory" to hold your Perl scripts. You can use the Server Properties dialog box do to this.

The following information is for setting up O'Reilly WebSite Professional to use Perl for Win32 for standard CGI (not PerlIS). Open Server Properties and click the Mapping tab. Server Properties is in the WebSite Professional folder on the Start menu. If there is an existing mapping for the extension you want to use (such as .pl), highlight the mapping and click Delete. Click Apply to immediately apply the change. Choose a file extension for Perl, such as .

By default, the Perl for Win32 installation maps the .plx extension to Perl for ISAPI. You can override the extension used during installation. Because the installation does this only when IIS is already installed, you must install IIS first, then install Perl for Win32. If you need to reconfigure these settings, or if you must set these by hand, the instructions in this section will prove useful. Microsoft Internet Information Server (IIS) ships with Windows NT Server.

Microsoft IIS 4.0 ships with Windows NT Server 5.0, and PWS 4.0 ships with Windows NT Workstation 5.0. Both IIS and PWS are available as part of the Microsoft Windows NT 4.0 Option Pack. You can find a link to the Option Pack at http://www.microsoft.com/iis/ Open the IIS 4.0 Internet Service Manager. This will bring up the Microsoft Management Console with the Internet Service Manager snap-in selected. From the tree display on the left, select the level at which to apply the mappings.

Some servers have no facility for this; you may be able to adjust your monitor to correct somewhat. Later versions of XFree86 allow these server options: gamma f set gamma value (0.1 < f < 10.0) Default: 1.0 -rgamma f set gamma value for red phase -ggamma f set gamma value for green phase -bgamma f set gamma value for blue phase

There's an example of a socket server, TCP-SERVER, in the eg directory of your perl directory. In general, information on socket programming for UNIX is applicable to Perl for Win32. See especially the perlipc page of the documentation. If you need to develop a server that can service multiple clients at once, take a look at the IO::Select module. This module allows you to write servers that can manage open connections from multiple clients.

You are not able to uninstall Perl for Win32 from the Add/Remove Programs section of the Control Panel (if you have such a section). In your original perl directory, there is a file called uninstall.bat. Use this to clear out the registry settings created by install.bat. uninstall.bat does not delete your Perl for Win32 files for you. You can do this manually with Explorer, File Manager, or "del [perl directory]\*.* /S /Q", where [perl directory] is your perl directory.

On December 4, 1996, ActiveWare released a beta version of Perl for Win32 at the 5.003 level. It corrects many of the flaws of the 110 build at the 5.001m level. It's available at Perl for Win32 is a Win32 command-line program. It expects to be run from the command line, not from Explorer. If you want to run a Perl script, write the script out using a text editor like Notepad.

Most Windows NT and Windows 95 servers that use the CGI standard or ISAPI will run Perl for Win32 scripts. The following servers are known to work with Perl for Win32 (known protocols in brackets): Microsoft Internet Information Server and Peer Web Services [CGI, ISAPI] (http://www.microsoft.com/iis/) Netscape Communications Server, Enterprise Server, and FastTrack Server [CGI] (http://home.netscape.com/) Fnord for Windows 95 [CGI] (http://www.wpi.

The Perl for Win32 package is available as a ZIP archive by anonymous FTP from ActiveWare and from CPAN, the Comprehensive Perl Archive Network. There are 4 distribution packages: one for Intel x86 machines, one for DEC Alpha machines, one for PowerPC machines, and one source code package. These packages are named XXX-i86.zip, XXX-Alp.zip, XXX-Ppc.zip, and XXX-src.zip, respectively, where XXX is the current build number. The current build number is 110.

Because the Perl for Win32 package contains long file names (LFNs), normal zip file handlers like PKZip will not open them correctly. [Does the newest version of PKZip handle LFNs correctly? -ESP] You need to get a zip file opener that can work with LFNs, such as: To extract the archive, make a new directory on your hard drive that will become your new perl directory ("C:\Program Files\perl5" and "C:\perl5" are good candidates).

X Server is a program that provides display and user input services to other programs. In comparison, a file server provides other programs with access to file storage devices. File servers are typically located in a remote location and you use the services of a file server from the machine that you are located at.

Microsoft Personal Web Server for Windows 95 is a scaled-down version of Microsoft Internet Information Server. Although it is not documented, it appears that the method used to support ActivePerl with IIS will also work with Personal Web Server. See How do I configure IIS 3.0 or lower to support ActivePerl?.

Starting with Solaris 10, kdmconfig will also offer the option of running the Xorg X server. The Xorg server is configured using /etc/X11/xorg.conf but tries to do the right thing without configuration.

The main Perl interpreter available for the Win32 platform is Perl for Win32. It was developed by ActiveWare, Inc. (originally Hip Communications) for Microsoft Corporation for inclusion in the Windows NT Resource Kit. It has since taken on a life of its own. When people talk about "Perl for Win32", it is this package that they mean. The Perl for Win32 package includes perl, PerlIS, and several Win32-specific modules developed by ActiveWare.

The source code package includes make files for Visual C++ versions 2.x and 4.x. The following instructions are for Visual C++ 4.x. [Does anyone have instructions for VC++ 2.x? How about other Win32 C++ compilers? -ESP] The source distribution only includes Intel targets. If you're building for another platform, like DEC Alpha, you may have to fiddle with the build settings to get them to work.