Software Limited User Installation Help

[TrayMurphy]

I am trying to get the Orbiter program to install so it runs for a (very) Limited User.

I need to install the program in C:\Program Files\{whatever it wants to call its folder}, NOT the user documents directory (this is poor programming practicce). However, the program fails the DirectX check on first run when the limited user first runs it. It will pass if an Administrator runs it, but this is not recognized by the program if the Limited User tries to run the program.

Basically, I need to know if there is a way to get this program to write to a User folder while executing from a Program Files folder since our users are prohibited from writing to Program Files, and cannot execute out of User folders. This prevents them installing and running any software we do not explicitedly approve and install for them.

I don't see any Registry keys that direct the program to write in a specific location, so I assume it defaults to trying to write to its installation folder.

Does anyone have any ideas on how to fix this? Our entire AFJROTC class is hoping to be able to use this software, but it's not looking good since it wasn't programmed using best practices.

Thanks!
Tray Murphy
Systems Administrator
Henrico County Public Schools
Henrico, VA

 

[orb]

The DirectX check is only performed once after Orbiter has been installed, so it can be done by Administrator who installed Orbiter to Program Files, as well as the initial setup, which can be performed by that Administrator, because Orbiter configuration is stored in the installation folder too.

Scenario files can be moved to a user writable directory if they need to be saved, and an entry responsible for setting path to scenarios changed (by Administrator) by editing Orbiter.cfg, which is in the Orbiter installation folder.

 

[Urwumpe]

Especially editing Orbiter.cfg is one important tip for your situation, you can produce a single standard installation of Orbiter even on a network drive and store the scenario files (equivalent of savegames) on the local user directory.

EDIT: There is no registry key of Orbiter, luckily. You can have multiple Orbiter installations on the same PC, it is one big advantage if you are developer for add-ons.

 

[orb]

Just to clarify a little editing the entry responsible for scenarios directory location, as new Orbiter versions don't echo default settings to the configuration file by default (it can be changed by toggling "EchoAllParams" setting inside of Orbiter.cfg to TRUE):

ConfigDir = .\Config\
MeshDir = .\Meshes\
TextureDir = .\Textures\
HightexDir = .\Textures2\
ScenarioDir = .\Scenarios\

Those are (default) locations of directories that can be configured, so to change the location of directory where scenarios have been moved, you need to set the path pointed by ScenarioDir..

 

[Ripley]

Does Orbiter.cfg accept system variables, like %HOMEPATH%, and such??