IIS 4

There aren't any logging options.

A small oversight. Do the following:

cd \winnt\system32\inetsrv
regsvr32 logui.ocx

I get cgi-bin2 when trying to set up my cgi-bin directory.

You get this when trying to create a cgi-bin, because there's already one there. So you need to get rid of the old one, which IIS won't let you do.

I haven't done this myself, but apparently you need to remove the execute permissions from the existing cgi-bin directory first, before you can remove it.

Another approach has been to remove and reinstall IIS, making sure no FrontPage elements were installed. This is probably a little drastic, though.

What's the difference between PWS and IIS4?

Apparently, not a lot. It seems that they're the same thing, except that PWS is just the web services, while IIS4 brings along the NNTP, SMTP, FTP, etc.

Can PWS/W95 run Perl?

Yep. I've heard that installing PWS as a network service, instead of using the PWS Install option from the Option Pack, and then installing the ActiveState distribution, has worked. So it's possible.

Personally, when I was using W95, I used Apache instead of PWS...

I get "Cannot detect OS type" when installing

This is apparently addressed in the release notes for NT 4 Options Pack:

"When installing IIS 4.0 on a computer running Windows NT Server, the NetLogon and Computer Browser services must be running. If these services are not running, you will receive a dialog that says "Cannot detect OS type" and Setup will fail. "

And you need NT4.0 with Service Pack 3.

Any hotfixes for IIS4? What about Service Pack 4?

Dunno, to be honest. The reason for this is that I'm not the only person dealing with my IIS installation, so I'm not at liberty to install whatever I want. So, while I know that there is a set of patches for IIS4, I haven't installed them. Part of the reason for this is that when I looked, I couldn't find a clear list of what they changed/fixed. I'm from a UNIX background, where the wisdom is, "if it doesn't fix a problem you've got, don't install it.". Just applying patches because they're there doesn't sit well with me.

The same applies to Y2K fixes, which happen to need SP4. Well, sorry, but I'm not the NT administrator for the machines in question either, so there's no way I'm going to install SP4 on a major server just because IIS4 isn't rated as Y2K-compliant without it...

All this is a long-winded way of saying, if anyone has any experience, good or bad, about IIS versions after Option Pack 4, I'd like to hear about it.

Steve Kilbane. Whitecrow home.