Windows 7 path environment variable issue

zubairblaze

Honorable
Sep 10, 2013
2
0
10,510
hi, I can't install my oracle 10g due to this error:
"the value of the environment variable path is more than 1023 characters windows 7".

My system variables are
ComSpec: %SystemRoot%\system32\cmd.exe
FP_NO_HOST_CHECK: NO
Path: c:\Program Files (x86)\Intel\iCLS Client\;c:\Program Files\Intel\iCLS Client\;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Hewlett-Packard\HP ProtectTools Security Manager\Bin\;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\
PATHEXT:
.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
PROCESSOR_ARCHITECTURE:AMD64
PROCESSOR_IDENTIFIER: Intel64 Family 6 Model 58 Stepping 9, GenuineIntel
PSModulePath:%SystemRoot%\system32\WindowsPowerShell\v1.0\Modules\
PTSMInstallPath_X86:C:\Program Files (x86)\Hewlett-Packard\HP ProtectTools Security Manager\

I am using windows 7 ultimate edition. I want to know that what environment variable can be deleted to reduce the size from 1023

or

How the size of environment variable can be reduced less than 1023.


Thanks in advance
 
Solution
A lot of those path entries might not be needed in the path variable. I'm not familiar with those programs, but you could use trial and error: take each entry, cut and paste it to a text file, and see if your programs run okay without having it on the path. My first target would be the paired entries where one starting with "C:\Program Files" is almost identical to another starting with "C:\Program Files (x86)". I don't think you need both the 64-bit and the 32-bit version of the same program to be accessible via the path. If it had the same filename under both folders, running that name would always trigger the first copy the system finds in the path folders. If you wanted to run the other, you'd need to specify (or be in) the other...
A lot of those path entries might not be needed in the path variable. I'm not familiar with those programs, but you could use trial and error: take each entry, cut and paste it to a text file, and see if your programs run okay without having it on the path. My first target would be the paired entries where one starting with "C:\Program Files" is almost identical to another starting with "C:\Program Files (x86)". I don't think you need both the 64-bit and the 32-bit version of the same program to be accessible via the path. If it had the same filename under both folders, running that name would always trigger the first copy the system finds in the path folders. If you wanted to run the other, you'd need to specify (or be in) the other folder instead of relying on the path variable.
 
Solution