Finds the registry key that tells it where it's installed (based on 圆4 location), then searches for digabout.spb. Writting this log in FsPassengers folder. Config file 'FsPassengers\bin\FsXPath.cfg' written ok I was considering buying it too, but after seeing the price in combination with the installer having DRM, not sure Im keen on it as much. Attempting to write Config file 'FsPassengers\bin\FsXPath.cfg' Good luck convincing the FSP dev to do anything. Extracting file to: C:\***\Microsoft Games\Microsoft Flight Simulator X\FsPassengers dll.xml : ' Visual Effects Tool' Xml ok. dll.xml : ' Object Placement Tool' Xml ok. fsx.cfg found, writing dll.xml in: C:\Users\***\AppData\Roaming\Microsoft\FSX\dll.xml Found application data path, searching fsx.cfg C:\Users This is a fresh install, no previous version of FsPX detected.
FsPassengers will be installed in: C:\***\Microsoft Games\Microsoft Flight Simulator X\FsPassengers Detecting VISTA and FsPassengers install path. Checking FsX path, searching this file: C:\***\Microsoft Games\Microsoft Flight Simulator X\dialogs\dlgabout.spb FsX Directory found: C:\***\Microsoft Games\Microsoft Flight Simulator X\ I have version purchased on Live Marketplace with working FSPassneger.įrom Proccess Monitor by Sysinternals I found, that FSPassneger installer queries HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft Games\flight simulator\10.0\setupPath for install location and then does something with "įSPXInstall.log contains (*** = for my privacy policy): Maybe this way we can try to figure out what's going on by ourselves.
0 kommentar(er)
