If you want to work with ASP (Active Server Pages) on your personal computer, you need to install the Personal Web Server (PWS). As the name indicates, it's a server. Unlike the normal HTML pages, dynamic pages (either created with CGI, PHP, ASP or Cold Fusion) require some sort of a server to carry on their business. Without a server, you can create a dynamic page, but you cannot view it decently in the run-time mode.

This section concerns installing Microsoft's Personal Web Server (PWS) 4.0 on Windows 98 SE, since that's the system I had available to install and test on. PWS is also available for Windows 95 and NT.

Come on, admit it! You have just finished a page where you loop through a record set, you load the page up, and suddenly PWS freezes! Damn, you forgot that RS.MoveNext! And now your PWS loops forever!! You go into the PWS manager to start and stop your PWS, but that doesn't help. So you do that fun ritual of rebooting your machine...

Mike knows the pain and frustration of having a web server crash unexpectedly... it happens when we least expect it. In this article, he's going to describe a simple way to create an ASP page that will allow us to view our web servers log files in a standard web page across the Internet.I know the pain of having a web server die unexpectedly, and let’s face it... it happens even to the best of us. If you run a small web site and need to know when/if your web server is having any problems, then your best bet would be to read over the log file to see what’s gone wrong. But how do you read the log file when you’re not at home…or out on the road?

As an IIS administrator it sometimes gets downright annoying having to fend off all the insults from Apache admins I meet claming innate server superiority. Generally the discussion about Web administration starts first with all the various security holes plaguing IIS and the negative press the platform garnered over the last year. Then it invariably moves to a discussion about how Netcraft and other stats sites show Apache as the dominant server on the Web, or how a certain big site uses Apache, or how there are so many cool modules to add to Apache. Pointing out that scads of non-identified corporate in-house servers run IIS, or that it too is a free server (since it comes with the operating system), or that there are in fact plenty of cool add-ons for IIS (including many that provide source code) -- all this does little to dissuade these server chauvinists of their opinion. Rather than whining about rude Apache admins, however, I thought it would be a more useful response simply to write down some of the ways I've found of improving IIS. So without further delay here are my top ten tips for making the most of your IIS.

So you have just installed IIS and the includes are not working and you do not know what a Virtual Directory is! Hmmmm! This tutorial will help you set up virtual includes on IIS 5.x.

As an IIS administrator it sometimes gets downright annoying having to fend off all the insults from Apache admins I meet claiming innate server superiority. Generally the discussion about Web administration starts first with all the various security holes plaguing IIS and the negative press the platform garnered over the last year. Then it invariably moves to a discussion about how Netcraft and other stats sites show Apache as the dominant server on the Web, or how a certain big site uses Apache, or how there are so many cool modules to add to Apache. Pointing out that scads of non-identified corporate in-house servers run IIS, or that it too is a free server (since it comes with the operating system), or that there are in fact plenty of cool add-ons for IIS (including many that provide source code) -- all this does little to dissuade these server chauvinists of their opinion. Rather than whining about rude Apache admins, however, I thought it would be a more useful response simply to write down some of the ways I've found of improving IIS. So without further delay here are my top ten tips for making the most of your IIS.

Masking or anonymizing a Web server involves removing identifying details that intruders could use to detect your OS and Web server vendor and version. This information, while providing little or no utility to legitimate users, is often the starting place for crackers, blackhat hackers and "script kiddies". This article explores some ways you can minimize the risk of such detection. Most of the following examples focus on Microsoft’s Internet Information Server (IIS), since it has been most widely lambasted for its vulnerabilities, but some Apache detection countermeasures are also covered. While IIS users probably have the most vested interest here, server anonymization is relevant to anyone responsible for administering a Web server.

MS Script Debugger can be used to debug both client side and server side scripts. Here is how to set up your system to debug server side VBScript pages.

Learn how to install Internet Information Server(Win xp pro).