Can't Run DOS Commands Outside System32 folder

[dave b.]

Windows XP Pro, V. 2002, SP1

For some strange reason, I can't run many commands from
any other folder than the System32 folder. When I change
to that directory, commands run fine. But from C:, the
system root folder, anywhere else... nothing works. Get
the "not internal/external command" error.

Here's my path statement: %SystemRoot%\system32;%
SystemRoot%;%SystemRoot%\system32\WBEM;C:\Program
Files\Common Files\Adaptec Shared\System;C:\Program
Files\ATI Technologies\ATI Control Panel;C:\Program
Files\Common Files\Autodesk Shared\;C:\PROGRA~1\COMMON~1
\ULEADS~1\Mpeg;

Thoughts?

 

[t@k]

Hi dave b.,

In microsoft.public.windowsxp.general you remarked...

Windows XP Pro, V. 2002, SP1

For some strange reason, I can't run many commands from
any other folder than the System32 folder. When I change
to that directory, commands run fine. But from C:, the
system root folder, anywhere else... nothing works. Get
the "not internal/external command" error.

Here's my path statement: %SystemRoot%\system32;%
SystemRoot%;%SystemRoot%\system32\WBEM;C:\Program
Files\Common Files\Adaptec Shared\System;C:\Program
Files\ATI Technologies\ATI Control Panel;C:\Program
Files\Common Files\Autodesk Shared\;C:\PROGRA~1\COMMON~1
\ULEADS~1\Mpeg;

Thoughts?

In 'My Computer' Properties> Advanced> Environment Variables> System
variables, do you see '.COM' and '.CMD' in PATHTEXT?

 

[Lem]

Windows XP Pro, V. 2002, SP1

For some strange reason, I can't run many commands from
any other folder than the System32 folder. When I change
to that directory, commands run fine. But from C:, the
system root folder, anywhere else... nothing works. Get
the "not internal/external command" error.

Here's my path statement: %SystemRoot%\system32;%
SystemRoot%;%SystemRoot%\system32\WBEM;C:\Program
Files\Common Files\Adaptec Shared\System;C:\Program
Files\ATI Technologies\ATI Control Panel;C:\Program
Files\Common Files\Autodesk Shared\;C:\PROGRA~1\COMMON~1
\ULEADS~1\Mpeg;

Thoughts?

It's been a while since I used the SET command, but you might try
putting quotes around those long file names, e.g.,
"C:\Program Files\Common Files\Adaptec Shared\System"

If the command interpreter doesn't like the format of the PATH
environment variable that you've set, it may just reject it entirely,
which would mean that commands would only execute from the directory in
which they are located -- which sounds like what you describe.