Re: Wrapped application directory oddity


"Jeff Godfrey" <jeff_godfrey@xxxxxxxxx> wrote in message
news:6aXgi.1993$zA4.138@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi All,

I have a TclApp wrapped application running on a remote web server.

More details on this subject...

I just had someone with the proper authority run my test CGI
application on the server box from a command terminal. The
application just issues the appropriate HTTP header, then spits out
some relevant path info from [info nameofexecutable], [info script],
[pwd], and $starkit::topdir.

Interestingly, when run that way, the returned paths are all
legitimate. That is, they all begin with "D:/WebHosting/...". Now,
when the same wrapped application is run as a CGI program via a
web-browser, the return values of most of the above are botched.
Specifically:

[pwd] - still OK (returns "D:/WebHosting/..."
[info nameofexecutable], [info script], and [$starkit::topdir] are bad
(return "//?/D:WebHosting/..."

I assume the CGI environment is more restrictive than that of the
local command shell test, which must be lending itself to this
problem. Any ideas on what would cause the botched paths under CGI?

Thanks,


Jeff


.