Re: CLIP Woes

[Michael Norman michael.norman@xxxxxxxx]

At 12/29/2004 01:35 AM -0500, Robert Holmgren wrote:
> > instructions say to put
> > KMD.EXE in the *first* directory in the path. For me that's actually a
> kind
> > of distant subdirectory: C:\PROGRAM
> > FILES\THINKPAD\UTILITIES;C:\WINDOWS\SYSTEM32;C:\WINDOWS......
> Put it in C:\WINDOWS\system32. Move the THINKPAD dirs further back in the
> PATH
> spec. IBM has a habit of adding their PATHs to the front of the spec --
> better
> to be first than last. But system32 *should* be first.
Moving forward I have a question. Here's the original path statement taken
verbatim from the E-Variables dialog:
C:\PROGRAM
FILES\THINKPAD\UTILITIES;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program
Files\ATI Technologies\ATI Control Panel;C:\Program Files\PC-Doctor for
Windows\services;C:\Program Files\Executive
Software\Diskeeper\;%SystemDrive%\IBMTOOLS\Python22;C:\XY\;C:\NBWIN7\
I wasn't sure you could begin a PATH statement just by moving the second
item in the list -- %SystemRoot%\system32 -- to the front so I, in effect,
duplicated it in the beginning with *C:\WINDOWS\System32*. I left what is
now the third item -- %SystemRoot%\system32 -- creating a redundancy.
Right? Or should I simply have moved %SystemRoot%\system32 forward. I
notice when you go to a DOS prompt and issue *echo %systemroot% I get
*C:\Windows* I'm not sure of the XP PATH conventions.
Michael Norman