[712] in winnt

home help back first fref pref prev next nref lref last post

path variable gets messed up (Win2k)

daemon@ATHENA.MIT.EDU (Dave Broderick)
Thu Sep 6 14:06:06 2001

Message-Id: <200109061803.OAA09884@melbourne-city-street.mit.edu>
Date: Thu, 06 Sep 2001 14:02:50 -0400
To: winpartners@mit.edu
From: Dave Broderick <djbroder@MIT.EDU>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	types="text/plain,text/html";
	boundary="=====================_2077874135==_.ALT"

--=====================_2077874135==_.ALT
Content-Type: text/plain; charset="us-ascii"

In the normal course of setting up some machines with the usual MIT stuff
(Netscape, Kerberos, Brio, Service Pack 2) and MS Office 2000, the "path"
environment variable gets badly mangled.

Trying to execute external commands (ping, tracert, etc) return the error
message: " 'ping' is not recognized as an internal or external command... "

Anyhow, editing the "path" variable in various ways can fix the problem. I do
notice that various programs (installs) add to the path statement.

I was wondering:
  Is there a limit to the length of such a statement? There used to be in
earlier 'windows'.
  Is %SystemRoot% no longer pointing to the Winnt directory?

The machines work when they come in from the vendors. Again, this is a problem
I can fix, but I'd like to know what's causing it. The machines work when they
come in from the vendors.

 
David J. Broderick 
djbroder@mit.edu 
    Senior Audio Visual Specialist 
    MIT AV 617 253 2808 
    FAX 617 253 5945 
    <http://web.mit.edu/djbroder/www>http://web.mit.edu/djbroder/www 

--=====================_2077874135==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
In the normal course of setting up some machines with the usual MIT stuff
(Netscape, Kerberos, Brio, Service Pack 2) and MS Office 2000, the
&quot;path&quot; environment variable gets badly mangled.<br>
<br>
Trying to execute external commands (ping, tracert, etc) return the error
message: &quot; '<i>ping' is not recognized as an internal or external
command...</i> &quot;<br>
<br>
Anyhow, editing the &quot;path&quot; variable in various ways can fix the
problem. I do notice that various programs (installs) add to the path
statement.<br>
<br>
I was wondering:<br>
&nbsp; Is there a limit to the length of such a statement? There used to
be in earlier 'windows'.<br>
&nbsp; Is %SystemRoot% no longer pointing to the Winnt directory?<br>
<br>
The machines work when they come in from the vendors. Again, this is a
problem I can fix, but I'd like to know what's causing it. The machines
work when they come in from the vendors.<br>
<br>
<x-html> <BR>
David J. Broderick <BR>
<b><font color="#0000FF">djbroder@mit.edu <BR>
</font></b><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Senior Audio Visual
Specialist <BR>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>MIT AV 617 <b>253 2808 <BR>
</b><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>FAX 617 253 5945 <BR>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><A HREF="http://web.mit.edu/djbroder/www">http://web.mit.edu/djbroder/www</A>
<BR>
</x-html>

--=====================_2077874135==_.ALT--


home help back first fref pref prev next nref lref last post