No matter what I did (basically unstalling both and reinstalling PWS first)
the install script would not let me into the last two check boxes for
installing script mapping for Activeperl or PerlIS. The result was that
when the registry entry refered to below was added all that happened when
the script was called was that perl would start and hang. I had to pull up
the task list and kill it if I wanted to use my browser again.
"Associate the extension for your scripts with the appropriate interpreter
in the script map for IIS. This is under the Registry key HKEY_LOCAL_SYSTEM,
with the sub-key ``System\CurrentControlSet\Services\W3SVC\Parameters\Script
Map''. Many people map two extensions: one to perl.exe (for example, .pl)
and another to PerlIS.dll (for example, .plx). Note that mapping an
extension in the script map is not the same as associating the extension in
Explorer. Use the full paths to the executable files in the script map."
In regedit I found a folder called Activestate under
HKEY_USERS\.DEFAULT\Software .I copied that folder and all of its entries
and subfolders and their entries to HKEY_LOCAL_MACHINE\Software. In
addition I had stumbled across a DWORD value in the documentation provided
by Activestate called EnableCGIHeader, and added it to
HKEY_LOCAL_MACHINE\Software\ActiveState\ActivePerl\620 .I'll paste the docs
I found below:
" This is no longer necessary with the current version of Perl for ISAPI,
as Perl for ISAPI sends the correct headers. The Registry value that governs
this is EnableCGIHeader, a REG_DWORD value that is set to 1 by default. This
value is stored under the Registry key
HKEY_LOCAL_MACHINE\SOFTWARE\ActiveState\PerlIS. If you need to turn off the
automatic generation of the header, set this value to 0."
Please note I put this in yadayada...\ActivePerl\620 not ....\PerlIS I use
activeperl for CGI scripting as I'm not on a network and performance isn't
really an issue. I really can't claim to know if this step was necessary.
It currently works to handle CGI scripts with the extension .pl provided
they are properly published in PWS with Read access turned off and Execute
access turned on.
I'm currently running:
Windows 98 with service pack 1
Microsoft Personal Web Server 4.0
ActivePerl build 620
I think the Activestate installer did not recognize I had PWS up and
running for one of the following reasons(guesses).
1 Win98 version
2 PWS version
3 The fact I don't log onto my machine (most of the registry entries did
exist under HKEY_USERS, but not under localmachine???)
4 Something didn't get removed when I uninstalled ActivePerl (after the
uninstall I did a find on perl*.* and there were a couple of files in C:
\windows left behind and the C:\Perl directory was not removed. (had I any
brains I would have run the same search in regedit)
5 Some piece of networking software I never installed for Win98
If anyone experienced a normal install I would greatly appreciate it if they
would check their registry and clue me in on anything I am still missing. I
hope this helps, and that I put it in the right place. If not my apologies.
P.S. don't mess with regedit unless you either know what you're doing or
are willing to invoke the famed format C: command :-) I'm afraid I'm more
willing than knowing myself.
_______________________________________________
Perl-Win32-Web mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-web
