Environment Variables
As part of the package we add a SYSTEM variable to PATH. On some machines, by adding this path we have exceeded the maximum length of the Path variable allowable by Windows.
How do we resolve this issue ?
Thanks
skj
How do we resolve this issue ?
Thanks
skj
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
dj_xest
18 years ago
Hey GUys,
Any ideas on here? I am also waiting for an aswer for this problem... My only fix for this is to use an Application Path in the registry or maybe use an isolation method like .local or manifest for the executables. If you have any better ideas please post it here..
Any ideas on here? I am also waiting for an aswer for this problem... My only fix for this is to use an Application Path in the registry or maybe use an isolation method like .local or manifest for the executables. If you have any better ideas please post it here..
Posted by:
spartacus
18 years ago
Have you considered making the addition to the path in short filename format ?
e.g. instead of adding C:\Program Files\LongFolderName\EvenLongerSubFolderName
just use
C:\Progra~1\Longfo~1\Evenlo~1
This might buy you some time, but sooner or later you may need to rationalize the size of the PATH environment variable on the machines affected. Searching for and removing duplicate or obsolete entries is one step you could take.
As an aside, some repackaging software suites - you know who you are [;)] - have an annoying habit of creating duplicates in the Environment table, when snapshotting legacy applications. So make sure any future packages you develop create only the additions they really need to the PATH variable.
Regards,
Spartacus
e.g. instead of adding C:\Program Files\LongFolderName\EvenLongerSubFolderName
just use
C:\Progra~1\Longfo~1\Evenlo~1
This might buy you some time, but sooner or later you may need to rationalize the size of the PATH environment variable on the machines affected. Searching for and removing duplicate or obsolete entries is one step you could take.
As an aside, some repackaging software suites - you know who you are [;)] - have an annoying habit of creating duplicates in the Environment table, when snapshotting legacy applications. So make sure any future packages you develop create only the additions they really need to the PATH variable.
Regards,
Spartacus
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
