Re: NT Server -- first time user

>
> - Do I have to use an .asp extension to run ASP pages, or is there a
method
> similar to the Apache .htaccess with AddType and AddHandler so that the
ASP
> code can be parsed on plain old HTML pages? (Previously I have used this
> method on Apache servers to parse SSI on an HTML page).

Yes, there is a way to do this, but it's not advisable because if it is an
NT4 box, then every page must be parsed by the asp interpreter which can
hurt the number of concurrent users that the server can support.  On Win2k
boxes that isn't the case.  To do this on an NT 4 box, open IIS, right click
on the web site, and choose properties, then, click the "Home Directory"
tab, then click the "configuration" button, under application mappings,
select ".asp" and click "edit", from there, copy the path to the asp
interpreter, and close that dialog box, then click add and paste the path to
the .asp interpreter into the "executable" box and fill in the rest and
click "ok".  Then stop and start the web site.

>
> - There is a cgi-bin and a cgi-local folder on the server.  Which one do I
> use for CGI scripts and more importantly will Perl CGI work on an NT
server
> in the same way it does on Apache?
>

I believe that there are a few changes that you may need to make, depending
on the scripts and modules installed... dunno for sure here though. Of
course, you'll need to have activestate perl installed on the machine.
http://www.activestate.com


> - Can you Telnet to an NT server?  I have a feeling only UNIX based
machines
> will do that, yes?
>
> - Is there an Apache distribution of ASP for my localhost server?  I would
> like to be able to test my scripts offline.
Chilisoft makes an asp interpreter for apache  http://www.chilisoft.com

>
> - There are a number of files and directories with names similar to
> _vti_foobar  inspection of one of the files reveals it to be related to
> Frontpage (the previous designers used Frontpage to design the whole
> website... and they didn't know how to configure it to give streamlined
> code, thus we get code like this...

Front page sux... Bad...
I would leave the extensions though and use Visual Interdev to create the
asp pages. Visual Interdev uses the front page extensions to connect to the
site, the similarities stop there.  Used correctly it can be a powerful tool
for creating asp pages and will also help in the small learning curve to
learning asp.

>
>     <font size="1" face="Verdana, Arial, Helvetica,
sans-serif"></font><font
>     size="1" face="Verdana, Arial, Helvetica, sans-serif"><img
>     src="title.gif" width="400" height="30"></font>
>
> ... which is why I'm now the webdesigner).  What can be done with these
> files... I do not use Frontpage, I do not need Frontpage features.  Can
the
> files be safely deleted, or should I leave them clogging up space?

If you choose to delete them, I would not just delete the directories, but
instead remove the front page extensions via the properties of the web site.

Good luck with everything,

Andre

HWG hwg-techniques mailing list archives, maintained by Webmasters @ IWA