I don't think that members are stupid, I think that
Medevil normally does his best to avoid posting clear questions, omitting examples, details and more genrally completely failing to help in being helped. (and that psc often does his best to avoid posting clear answers, but that's another topic).
@psc
Don't worry, the question is not yet clear, I anyway think I might have understood some parts of it and can provide a tentative suggestion. (that will be later discarded by
Medevil as being either not what he wanted or wroong, or not the way he likes it, or for any other reason)
@Medevil
Which OS/kind of PE are we talking about?

Use a variable with SETX or a similar "global" app variable I can suggest the much better SETENV:
http://barnyard.syr.edu/~vefatica/#SETENVCODE
SETENV syntax:
To set or change the value of a variable:
User environment: setenv -u name value (also /u)
Machine environment: setenv -m name value (also /m)
Default user environment: setenv -d name value (also /d)
Volatile environment: setenv -v name value (also /v)
To display a variable: setenv -u|-m|-d|-v name
To delete a variable: setenv -u|-m|-d|-v name -delete (also /delete)
To display an environment: setenv -u|-m|-d|-v
Use double-quotes around values containing spaces.
If a variable name or value is to CONTAIN a double-quote,
escape that double-quote as \"
Return codes: 0 = success 1 = variable not found
2 = access denied 3 = other error
4 = SETENV has shown this syntax message
Requested output goes to STDOUT; help and error messages to STDERR.
Of course at some given time you need to know the full path to the app in order to set the variable.
Or are you talking about specific OPERA settings / .ini?


Wonko