PeterLk

Ok, the thing is solved. Obviously, among many other things, FSUIPC saves also messages that were created by add-ons (like LINDA) in binary files named <FlightName>.ipcbin. Me setup of FSUIPC was configured always to load the ipcbin-File associated to the current flight file. As the ipcbin-file of the default flight contained the LINDA-message, it was occasionally reproduced under not so clear conditions (I think it was when FSUIPC considered to re-initialize itself). Once I deleted the ipcbin-File the ghost has gone.

Wow, thanks for the quick reply. However, Linda is definitely not running, and I have even removed the ipcready.lua to prevent the linda-startup script for being executed. I cannot find any reference in the FSUIPC.log either and searched already a lot of files for the string. So far only found in LINDA's "events.lua" This is my setup: FSX-ACC FSUIPC (licensed) SPAD-Driver --> mostly mapped to FSUIPC virtual buttons HIDMacros.exe --> the same FSINN AES (only free parts) PS: Maybe you saw my post in the Dev-board on how to get the Saitek-Panels adressed in LUA/FSUIPC?

I get frequently this message, even after removing LINDA from the modules directory (i.e. Linda.exe and ipcready.lua). Any idea? best regards, Peter

Me too.Any option to skip it and continue with most recent weather?If not surely a thing to ask for in a next SP.

Hi,first of all, I'd like to say, that I'm well aware of the implications of old software as FSX on new OS as W7/64.However, I'm running all my FS software (and some other old software, too) as restricted user with UAC on without any problems, by giving the appropriate access rights to the relevant parts of the registry and program files directory.I understand also, that Hifi is not imposing these potential problems to standard users, but I personally would prefer running AS2012 as restricted user, too, as my PC is not only for FS and has to some other important stuff as well. I can't see any reason why this should be technically impossible. However, the hard coded request for admin rights prevents this way of using the software finally, thus requiring me to type in my admin password all the time (with plenta chances to get logged by malware), when running FSX from its dedicated restricted account.Is there any way to let AS2012 in restricted mode, or will this be considered in future (e.g. by means of a "power user option" in the command line?bests