Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 64127 invoked by uid 500); 9 Jun 2002 12:51:35 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 64114 invoked from network); 9 Jun 2002 12:51:34 -0000 Errors-To: Message-Id: <5.1.0.14.2.20020609074257.03026c48@pop3.rowe-clan.net> X-Sender: wrowe%rowe-clan.net@pop3.rowe-clan.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sun, 09 Jun 2002 07:46:49 -0500 To: dev@httpd.apache.org From: "William A. Rowe, Jr." Subject: Re: Problems with Apache 2.0.3.x as service on WinXP In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Juergen, Yes, isn't even a path. Try . Same for DocumentRoot. "r:" says "The current working directory, on r:" which is absolutely meaningless for a service (and too vague for general practice.) At 05:17 AM 6/9/2002, JHeckel@t-online.de (Juergen Heckel) wrote: >Hi, >I have since v2.0.32 these two problems despite of the newest patches: > >"Fix the working directory *for WinNT/2K/XP services only* to >change to the Apache directory (one level above the location >of Apache.exe, in the case that Apache.exe resides in bin/.) >Solves the case of ServerRoot /foo paths where /foo was not >on the same drive as /winnt/system32. [William Rowe]" > >First, >I'm the admin, the Apache service has admin rights, no problems when >Apache runs as console app., and no problem when Apache runs as service >on a Win2000 server; only XP makes troubles. > >1. If Directory points to a mapped network drive (e.g. R:) the service >does not start: > Syntax error: path is invalid. > >2. If DocumentRoot points to a mapped network drive (e.g. R:) the >service does not start: > Syntax error: DocumentRoot must be a directory. > > >UNC-names are accepted instead of the mapped drives (local drives are ok >too), >but now mod_perl.so does not load: >The Apache service named reported the following error: > >>> Cannot load F:/Apache2/modules/mod_perl.so into server: The module > was not found. >and PHP has similar problems. >Therefore I have to use mapped drivenames. > > >Juergen