New problems when running FSInn

[GerryR]

Hi L.D. James,

Well, I have some additional issues. As a reminder, I'm running on Windows 7.

First Problem: When flying in evening hours. Dusk, night. My default scenery disappears. This does not happen in daytime scenery. I have no addons as of now. Just using the default scenery.

Second Problem: When clicking on the WX icon, no box opens as before.

Hope there are some things you can suggest.

Happy Holidays and thanks,
Gerry

[J.Grzywacz]

Check weather FS and FSINN are running in admin mode. Click on the corresponding FS9.exe and set the correct checkmark in the Compatibility Tap. FSINN should run perfect with no change made after installation. If there are still some problems, do the same with:

FWINN.exe
FSINNUI.exe

[L. D. James]

Check weather FS and FSINN are running in admin mode. Click on the corresponding FS9.exe and set the correct checkmark in the Compatibility Tap. FSINN should run perfect with no change made after installation. If there are still some problems, do the same with:

FWINN.exe
FSINNUI.exe

Actually if the user followed the Quick Install Steps on the front page of http://flightsim.apollo3.com it’s unlikely that he’d have a problem. According to the Quick Install Steps, there should be no check marks in any of the FSInn modules. It’s my experience that placing check marks in those files have caused lots of problems.

It’s possible to make FSInn work with marks in those files, but it’s easier to make the application work by following the Install Steps.

Hi L.D. James,

Well, I have some additional issues. As a reminder, I'm running on Windows 7.

First Problem: When flying in evening hours. Dusk, night. My default scenery disappears. This does not happen in daytime scenery. I have no addons as of now. Just using the default scenery.

Second Problem: When clicking on the WX icon, no box opens as before.

Hope there are some things you can suggest.

Happy Holidays and thanks,
Gerry

The problem with the scenery might have something to do with an FSX install glitch. I don’t think that is FSInn related.

Not seeing the WX box open when clicking the icon can be a result of the box appearing out of the screen range. Are you running dual monitors?

-- L. James

--
L. D. James
ljames@apollo3.com
www.apollo3.com/~ljames (http://www.apollo3.com/%7Eljames)

[J.Grzywacz]

Larry you are right. I am just pointing toward the experience I had with FWINN.exe. On my System (WIN7 Prof. 32bit) FWINN.exe stopped service from time to time, at the stage it hasn't been assigned to run in admin mode. I guess it might be only with me, but as I provide user-to-user support at the VATGER (VATSIM GERMANY), this sollution helped some other guys, related to the issus with FWINN.exe.

However it should works fine for most users, sticking to the correct install steps.

[L. D. James]

Larry you are right. I am just pointing toward the experience I had with FWINN.exe. On my System (WIN7 Prof. 32bit) FWINN.exe stopped service from time to time, at the stage it hasn't been assigned to run in admin mode. I guess it might be only with me, but as I provide user-to-user support at the VATGER (VATSIM GERMANY), this sollution helped some other guys, related to the issus with FWINN.exe.

However it should works fine for most users, sticking to the correct install steps.

Jakob. You’re right. There are other methods to get FSInn working besides following the Quick Install Steps. I tested many of them including the method of putting check marks in the FSInn modules.

If you turn off UAC putting the check marks in the FSInn modules wouldn’t cause a problem. However, having to instruct the user to change the default of their UAC, as well as introducing a discussion on it came get complicated for many users, so I went with the method that will work regardless of the state of the UAC to make it simpler. Plus, I would rather discourage users from turning off that security feature. As a consultant, I find that my client’s computers require less maintenance with the security enabled. While many people complain about it, I fill it is a move by Microsoft in the right direction to relieve some of the exposure to system compromise that is so innate of Windows.

With UAC turned on, a user is prompted before many critical changes can be done to the computer. So if you put marks in FSInn’s modules you’re telling UAC to prompt you before allowing those changes. You can’t get the prompt when it’s being called in the background from another application, so it doesn’t run in the elevated mode. If you turn UAC off, then it will run in the elevated mode you specify without prompting the user.

Putting a mark in FSX will give the prompt when starting Flight Simulator, so the programs Flight Simulator calls will automatically run in elevated mode regardless of the UAC state unless you put a mark telling the system that you must be prompted by those modules.

You might consider looking again at the Quick Install Steps. You’ll find that if they are followed closely it’ll work the same for everybody. I’d be glad to help diagnose the problem with the configurations where you believe the Quick install steps fails. It might make your support sessions substantially easier when you can minimize the number of steps needed.

-- L. James

--
L. D. James
ljames@apollo3.com
www.apollo3.com/~ljames (http://www.apollo3.com/%7Eljames)

[J.Grzywacz]

Talking same ways Larry. Good to see we are on the same side of the medal :)