the future, and patches to allow Apache to work on 95, 98 and
ME are welcome!</p>
- </div><div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#req">Requirements</a></li><li><img alt="" src="../images/down.gif" /> <a href="#down">Downloading Apache for Windows</a></li><li><img alt="" src="../images/down.gif" /> <a href="#inst">Installing Apache for Windows</a></li><li><img alt="" src="../images/down.gif" /> <a href="#run">Running Apache for Windows</a></li><li><img alt="" src="../images/down.gif" /> <a href="#use">Configuring Apache for Windows</a></li><li><img alt="" src="../images/down.gif" /> <a href="#service">Running Apache for Windows as a Service</a></li><li><img alt="" src="../images/down.gif" /> <a href="#cmdline">Running Apache for Windows from the Command Line</a></li><li><img alt="" src="../images/down.gif" /> <a href="#signalsrv">Signalling
Service Apache when running</a></li><li><img alt="" src="../images/down.gif" /> <a href="#signal">Signalling Console Apache when running</a></li></ul></div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="section"><h2><a name="req" id="req">Requirements</a></h2>
+ </div><div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#req">Requirements</a></li><li><img alt="" src="../images/down.gif" /> <a href="#down">Downloading Apache for Windows</a></li><li><img alt="" src="../images/down.gif" /> <a href="#inst">Installing Apache for Windows</a></li><li><img alt="" src="../images/down.gif" /> <a href="#run">Running Apache for Windows</a></li><li><img alt="" src="../images/down.gif" /> <a href="#use">Configuring Apache for Windows</a></li><li><img alt="" src="../images/down.gif" /> <a href="#service">Running Apache for Windows as a Service</a></li><li><img alt="" src="../images/down.gif" /> <a href="#cmdline">Running Apache for Windows from the Command Line</a></li><li><img alt="" src="../images/down.gif" /> <a href="#signalsrv">Signalling
Apache when running as a Service</a></li><li><img alt="" src="../images/down.gif" /> <a href="#signal">Signalling Apache when running as a console application</a></li></ul></div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="section"><h2><a name="req" id="req">Requirements</a></h2>
<p>If running on Windows 95, the "Winsock2" upgrade MUST BE
INSTALLED. "Winsock2" for Windows 95 is available <a href="http://www.microsoft.com/windows95/downloads/">here</a>.</p>
- <p>If running on NT 4.0, installing Service Pack 3 or 6 is
+ <p>If running on NT 4.0, installing Service Pack 6 is
recommended, as Service Pack 4 created known issues with TCP/IP
and WinSock integrity that were resolved in later Service
Packs.</p>
<ul>
<li><p>As a <a href="win_service.html#service">"service"</a>
- (available on Windows NT/2000, or a pseudo-service on Windows
+ (available on Windows NT/2000/XP, or a pseudo-service on Windows
95, 98 or ME). This is the best option if you want Apache to
automatically start when you machine boots, and to keep
Apache running when you log-off.</p></li>
</code></p></div>
<p><strong>Complete the steps above before you proceed
- to attempt to start Apache as a Window NT/2000
+ to attempt to start Apache as a Window NT/2000/XP
service!</strong></p>
<p>To start Apache as a service, you first need to install it
Running</a> for more information on installing and controlling
Apache services.</p>
- <div class="note"><strong>Apache, unlike many other Windows NT/2000 services,
+ <div class="note"><strong>Apache, unlike many other Windows NT/2000/XP services,
logs any errors to its own <code>error.log</code> file in the
<code>logs</code> folder within the Apache server root folder.
You will <em>not</em> find Apache error details in the Windows
- NT Event Log.</strong></div>
+ Event Log.</strong></div>
<p>After starting Apache running (either in a console window or
- as a service) it will be listening to port 80 (unless you
+ as a service) it will be listening on port 80 (unless you
changed the <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> directive in the configuration
files). To connect to the server and access the default page,
launch a browser and enter this URL:</p>
<p>Once your basic installation is working, you should
configure it properly by editing the files in the
<code>conf</code> directory. Again, if you change the
- configuration of the Windows NT/2000 service for Apache, first
+ configuration of the Windows NT/2000/XP service for Apache, first
attempt to start it from the command line to assure that the
service starts with no errors.</p>
<p>Because Apache <em>CANNOT</em> share the same port with
- another TCPIP application, you may need to stop or uninstall
+ another TCP/IP application, you may need to stop or uninstall
certain services first. These include (but are not limited to)
other web servers, and firewall products such as BlackIce. If
you can only start Apache with these services disabled,
reconfigure either Apache or the other product so that they do
- not listen on the same TCPIP ports.</p>
+ not listen on the same TCP/IP ports.</p>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="section"><h2><a name="use" id="use">Configuring Apache for Windows</a></h2>
Apache only support the default service name
"Apache".</strong></div>
- <p>You can install Apache as a Windows NT service as
+ <p>You can install Apache as a Windows NT/2000/XP service as
follows:</p>
<div class="example"><p><code>
- <p>The Start menu icons and the NT Service manager can provide
+ <p>The Start menu icons and the Windows Service manager can provide
a simple interface for administering Apache. But in some cases
it is easier to work from the command line.</p>
<p>Apache will execute, and will remain running until it is
stopped by pressing control-C.</p>
- </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="section"><h2><a name="signalsrv" id="signalsrv">Signalling Service Apache when running</a></h2>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="section"><h2><a name="signalsrv" id="signalsrv">Signalling Apache when running as a Service</a></h2>
- <p>On Windows NT, multiple instances of Apache can be run as
+ <p>On Windows NT/2000/XP, multiple instances of Apache can be run as
services. Signal an Apache service to start, restart, or
shutdown as follows:</p>
apache -n "service name" -k shutdown
</code></p></div>
- <p>In addition, you can use the native NT <code>NET</code> command
- to start and stop Apache services as follows:</p>
+ <p>In addition, when running on Windows NT/2000/XP, you can use the
+ native <code>NET</code> command to start and stop Apache services
+ as follows:</p>
<div class="example"><p><code>
NET START "service name" <br />
NET STOP "service name"
</code></p></div>
- </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="section"><h2><a name="signal" id="signal">Signalling Console Apache when running</a></h2>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="section"><h2><a name="signal" id="signal">Signalling Apache when running as a console application</a></h2>
- <p>On Windows 95, Apache runs as a console application. You can
+ <p>On Windows 95/98/ME, Apache runs as a console application. You can
tell a running Apache to stop by opening another console window
and typing:</p>
INSTALLED. "Winsock2" for Windows 95 is available <a
href="http://www.microsoft.com/windows95/downloads/">here</a>.</p>
- <p>If running on NT 4.0, installing Service Pack 3 or 6 is
+ <p>If running on NT 4.0, installing Service Pack 6 is
recommended, as Service Pack 4 created known issues with TCP/IP
and WinSock integrity that were resolved in later Service
Packs.</p>
<ul>
<li><p>As a <a href="win_service.html#service">"service"</a>
- (available on Windows NT/2000, or a pseudo-service on Windows
+ (available on Windows NT/2000/XP, or a pseudo-service on Windows
95, 98 or ME). This is the best option if you want Apache to
automatically start when you machine boots, and to keep
Apache running when you log-off.</p></li>
</example>
<p><strong>Complete the steps above before you proceed
- to attempt to start Apache as a Window NT/2000
+ to attempt to start Apache as a Window NT/2000/XP
service!</strong></p>
<p>To start Apache as a service, you first need to install it
Running</a> for more information on installing and controlling
Apache services.</p>
- <note><strong>Apache, unlike many other Windows NT/2000 services,
+ <note><strong>Apache, unlike many other Windows NT/2000/XP services,
logs any errors to its own <code>error.log</code> file in the
<code>logs</code> folder within the Apache server root folder.
You will <em>not</em> find Apache error details in the Windows
- NT Event Log.</strong></note>
+ Event Log.</strong></note>
<p>After starting Apache running (either in a console window or
- as a service) it will be listening to port 80 (unless you
+ as a service) it will be listening on port 80 (unless you
changed the <directive module="mpm_common">Listen</directive> directive in the configuration
files). To connect to the server and access the default page,
launch a browser and enter this URL:</p>
<p>Once your basic installation is working, you should
configure it properly by editing the files in the
<code>conf</code> directory. Again, if you change the
- configuration of the Windows NT/2000 service for Apache, first
+ configuration of the Windows NT/2000/XP service for Apache, first
attempt to start it from the command line to assure that the
service starts with no errors.</p>
<p>Because Apache <em>CANNOT</em> share the same port with
- another TCPIP application, you may need to stop or uninstall
+ another TCP/IP application, you may need to stop or uninstall
certain services first. These include (but are not limited to)
other web servers, and firewall products such as BlackIce. If
you can only start Apache with these services disabled,
reconfigure either Apache or the other product so that they do
- not listen on the same TCPIP ports.</p>
+ not listen on the same TCP/IP ports.</p>
</section>
Apache only support the default service name
"Apache".</strong></note>
- <p>You can install Apache as a Windows NT service as
+ <p>You can install Apache as a Windows NT/2000/XP service as
follows:</p>
<example>
<title>Running Apache for Windows from the Command Line</title>
- <p>The Start menu icons and the NT Service manager can provide
+ <p>The Start menu icons and the Windows Service manager can provide
a simple interface for administering Apache. But in some cases
it is easier to work from the command line.</p>
<section id="signalsrv">
- <title>Signalling Service Apache when running</title>
+ <title>Signalling Apache when running as a Service</title>
- <p>On Windows NT, multiple instances of Apache can be run as
+ <p>On Windows NT/2000/XP, multiple instances of Apache can be run as
services. Signal an Apache service to start, restart, or
shutdown as follows:</p>
apache -n "service name" -k shutdown
</example>
- <p>In addition, you can use the native NT <code>NET</code> command
- to start and stop Apache services as follows:</p>
+ <p>In addition, when running on Windows NT/2000/XP, you can use the
+ native <code>NET</code> command to start and stop Apache services
+ as follows:</p>
<example>
NET START "service name" <br />
<section id="signal">
- <title>Signalling Console Apache when running</title>
+ <title>Signalling Apache when running as a console application</title>
- <p>On Windows 95, Apache runs as a console application. You can
+ <p>On Windows 95/98/ME, Apache runs as a console application. You can
tell a running Apache to stop by opening another console window
and typing:</p>
projects / apache / commitdiff