From: bill_seitz at my-dejanews.com (bill_seitz at my-dejanews.com)
Date: Thu, 15 Apr 1999 14:43:33 GMT
Subject: stupid Win-CGI getting started question
References: <7f0f0h$pfb$1@nnrp1.dejanews.com> <8DA86302Bduncanrcpcouk@news.rmplc.co.uk> <7f2db8$dev$1@nnrp1.dejanews.com> <8DA96361Fduncanrcpcouk@news.rmplc.co.uk>
Message-ID: <7f4tuj$in6$1@nnrp1.dejanews.com>
Content-Length: 1222
X-UID: 1637                                                  

In article <8DA96361Fduncanrcpcouk at news.rmplc.co.uk>,
  Duncan Booth <duncan at rcp.co.uk> wrote:
> It sounds like you still don't have the right path to python, or it is
> protected so you can't access it. I would check the file permissions: you
> probably need to give SYSTEM (or whatever user the CGI process is running as)
> on the web server full access to the python directory.
>
> Try creating a CGI cmd file like this:
> ----access.cmd---------

Ugh, pardon my sloppiness. Your access.cmd worked fine. Then I went back to
the previous file, took off the stuff on your first line after the Python
path, and got the same error message followed by the rest of the contents of
the file. So that told me that the path was the offending line. I looked more
carefully, and realized (d'oh) that the path was not just a folder path to
your code files, or the path to the Python executable, but the actual path
including the executable filename itself. Once I adjusted my first line to
match that, it started working fine. Now, if only I could get .py files to
work...

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/       Search, Read, Discuss, or Start Your Own    




