As I have said before, PRISM really is meant to be installed under the LFS directory, in a sub directory called addons. This is so that PRISM can make use of configuration files that LFS has, and to make use of any assets that LFS uses (Like the path files, or AutoX layouts.) The point of this being not only to make addons clearer, where things like Airo would be installed to $LFS/addons/Airo/ and PRISM would be installed to $LFS/addons/PRISM, it also give us access to LFS directly.
Knowing where LFS.exe is very helpful to PRISM when used on the same computer as the LFS instance. It give us direct access to the configuration files, allowing us to read and parse this data. This means that, as long as PRISM is installed correctly into the $LFS/addons/PRISM directory, PRISM, in the coming versions, will not require any configuration at all. It will simply work with LFS. You don't need to give it any passwords, or anything of that nature, as it has access to that already in the config files. You don't need to setup the hostname, or tell it the InSim port, because it also has that information already. It will just work. I think in many cases, this will get around any problems that people might have with installing PRISM on their computers and servers.
The only draw backs is that it will not configure the HTTP interface, or the telnet interface. But for people that don't use it, I don't see it being a problem. If I do add the HTTP interface to PRISM as apart of the NCN setup, then it would be on port 8080 as to get around the permission problem with Windows Vista / 7.
Knowing where LFS.exe is very helpful to PRISM when used on the same computer as the LFS instance. It give us direct access to the configuration files, allowing us to read and parse this data. This means that, as long as PRISM is installed correctly into the $LFS/addons/PRISM directory, PRISM, in the coming versions, will not require any configuration at all. It will simply work with LFS. You don't need to give it any passwords, or anything of that nature, as it has access to that already in the config files. You don't need to setup the hostname, or tell it the InSim port, because it also has that information already. It will just work. I think in many cases, this will get around any problems that people might have with installing PRISM on their computers and servers.
The only draw backs is that it will not configure the HTTP interface, or the telnet interface. But for people that don't use it, I don't see it being a problem. If I do add the HTTP interface to PRISM as apart of the NCN setup, then it would be on port 8080 as to get around the permission problem with Windows Vista / 7.