Paul,

Don't use physical paths, and don't use spaces in the folder names within your virual 
web trees.  Neither is portable, so either will box your code in.   The advantage is 
that you canuse the same code on Unix without having to rewrite.  I would also 
recommend using forward slashes wherever possible, even in local file access, for the 
same reason.  The ActiveState engine abstracts the delimiter difference quite nicely.

I have, quite successfully, used constructs such as:
open (IN, "../sibling/datafile");
in Windows 2000, using ActiveState.

Joseph

Paul Kraus wrote:

> After getting it all working I created a new virtual directory. Setup
> the permissions and tested everything by loading static html pages with
> http://localhost/path/file and it works. I then load my form call my
> script and I get this error.
>
> The specified CGI application misbehaved by not returning a complete set
> of HTTP headers. The headers it did return are:
>
> Can't open Perl script "C:\Documents": No such file or directory
>
> now this one seems to be pretty straight forward. Originally my paths
> where c:\inetpub\wwwroot\test\cgi\file.cgi.
>
> When I created the new folder I put it in my documents for easy of use
> and development.
> so now the path is c:\documents and settings\pdk\my
> documents\personal\ltf\cgi
>
> so it appears that the Perl compiler is unable to get to the script.
> Must I contain my source files for CGI in directories without spaces?
> Remember this is development I would never do this on a live server.
>
> Paul Kraus
> Network Administrator
> PEL Supply Company
> 216.267.5775 Voice
> 216-267-6176 Fax
> www.pelsupply.com
>
>                                                   
>-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> --
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to