Mark Hensler — Thu, 14 Sep 2000 05:28:37 +0000

ooooohhh..
So on my Win98, I don't need the path to perl? Do I have to configure Apache somehow?
I've had scripts yell at me when I have the path wrong, but I've never tried without one.

Gil — Thu, 14 Sep 2000 01:13:55 +0000

That is correct. In most cases, NT web servers use ISAPI Filters which basically recognize the file extension (.cgi, .pl, etc.). It then matches the extension with the specified compiler path. So no, a path to perl (usually looks like #!/usr/local/bin/perl) is normally not needed on Win NT.

As for file format, the Windows NT file system is almost identical to Windows 98. C:\inetpub\wwwroot is a typical path for websites on Windows machines using IIS.

Rob Pengelly — Wed, 13 Sep 2000 22:42:58 +0000

I think that on NT servers, normally the path to perl is NOT required.

Mark Hensler — Wed, 13 Sep 2000 05:39:20 +0000

I don't know... I've just run CGI's on Win98 and UNIX/LINUX
But I would *think* that it you look like that.

Vorm — Wed, 13 Sep 2000 02:17:33 +0000

I have a quesiton a long the same lines. What does a typical NT path look like? Kind of like a Win 98 one? So an NT path would look like this: "C:\site\public_html\cgi-bin"?

Mark Hensler — Tue, 12 Sep 2000 23:12:52 +0000

On windows platforms, you don't worry about permissions.

The CGI will be writen the same on both platforms with a few exeptions:
-The path to perl will look different
-You can use any plaform specific code in yoou CGI (some people use UNIX shell command in their CGI's)

I have a UNIX host, but design my stuff on my Windows 98 machine. I have apache, perl, php, and mysql installed. As long as I change the path to perl, and be carefull about versions, the scripts work on both platforms.