Guglielmo
1st January 2009 23:55 UTC

Manipulate the PATH environmental variable with NSIS
Hello,

On the web, I found many examples describing how to edit the PATH environmental variable through NSIS (i.e. http://nsis.sourceforge.net/Path_man...on_in_run-time). However, considering that NSIS has a limitation on the size of a string (1024 bytes), I was wondering if it's safe to edit the system PATH environment variable directly through NSIS by editing the registry entry or if it's better to use an external DLL that handles all the editing and to which simply pass the path to add/remove. All the examples I found seem to don't consider the limit to the string size. So, is the size limit a real problem?

Thank you.


Guglielmo

Comperio
2nd January 2009 05:37 UTC

...However, considering that NSIS has a limitation on the size of a string (1024 bytes)...

Animaether
2nd January 2009 05:41 UTC

The size limit is a problem if the path sting is more than 1024 characters. If you think that may occur, try the special build that goes up to 8192 characters (I think) or, indeed, use a DLL (or a system call - if one exists).

Guglielmo
3rd January 2009 02:13 UTC

That's what I thought :-(... OK, I will probabilly go with an external DLL..

Thanks guys for the replay