[714] in winnt
Re: path variable gets messed up (Win2k)
daemon@ATHENA.MIT.EDU (Jonathan McIndoe Hunt)
Mon Sep 10 08:39:08 2001
Message-Id: <5.1.0.14.2.20010910083445.04998e58@hesiod>
Date: Mon, 10 Sep 2001 08:38:50 -0400
To: Dave Broderick <djbroder@mit.edu>, winpartners@mit.edu
From: Jonathan McIndoe Hunt <jmhunt@MIT.EDU>
In-Reply-To: <200109061803.OAA09884@melbourne-city-street.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
The BrioQuery installer changes the registry key type for the path variable
such that the system variables like %SystemRoot% are not expanded when
using the command prompt. If you modify the path manually in System
Properties it should set the key type back to normal. One thing to check
is to type "path" at a command prompt and see what displays. If your see %
then it is not expanding.
I do not believe Windows NT or 2000 have a limit that we need to worried about.
Jon
At 02:02 PM 9/6/2001 -0400, Dave Broderick wrote:
>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
>
></x-html>