Nice work, Mark.

 

Regarding MSSE, you can exclude locations and/or processes (separate menus). If you add FSX to both, you should be ok (works here) while not having to disable any live protection for other parts of the system.

 

Of course, if you don't use the PC for any networked tasks and only fly, there's no need for such a program at all.

Nice work, Mark.

 

Regarding MSSE, you can exclude locations and/or processes (separate menus). If you add FSX to both, you should be ok (works here) while not having to disable any live protection for other parts of the system.

 

Of course, if you don't use the PC for any networked tasks and only fly, there's no need for such a program at all.

 

Thanks, that is what I have done now.  I have to say, great satisfaction finding and resolving problems of this type using Process Explorer.  I need to read the notes because I am sure there was an easier way to highlight problems rather than me staring at the FSX screen with one eye and PE with the other!

Powerful tool that is indeed.

me staring at the FSX screen with one eye and PE with the other!

Hey, that sounds like me!

Powerful tool that is indeed.

Hey, that sounds like me!

 

Well that explains your Avatar.

Hehe. On another occasion, I was wondering how the Concorde X is doing in FSX:SE. Would be a nice target considering the better VAS handling, no?

 

Is she working, even with all the dll dependencies?

Thanks Mark, I think I forgot to add SE to the MSSE program...,and X-Plane for that matter .

Hehe. On another occasion, I was wondering how the Concorde X is doing in FSX:SE. Would be a nice target considering the better VAS handling, no?

 

Is she working, even with all the dll dependencies?

 

Does not work unfortunately.  FSL says they need to reprogram some things and it will not happen until after the A320 release.....so we will probably be waiting quite a while.

Thanks for the feedback, Mark and sorry for my off topic question. :blush:

Well here is something Mark, that i just noticed. I started up Process explorer and noticed another "Steam" exe running, and sometimes over 400,000K. Not Steam.exe, but Steamwebhelper.exe, What the heck is that????? Like i don't have enough crap using up my valuable VAS!!!  It's usually 3rd on the list behind FSX and MsMpEng...geeeez 

Beats me, never noticed this.  Important to note that memory issues inside FSX will not be affected by programs running outside of FSX...like the Steam app...and if you have 8gig of ram you have nothing to worry about.

OK, nice to know that Mark...anyhow, I'm lov'n FSX-SE

Actually, I did notice those program now.  They actually take up very small amount of memory so don't worry about it.

Past comments on stopping Microsoft SearchProtocolHost:

 

1) Indexing (supposedly) makes searching faster. If you right click on each drive letter, select Properties. You will see a box marked "Index this drive for faster searching". Uncheck the box.

 

or:

 

2) To get around the problem, type Run, enter, and in the box type services.msc and press enter/click OK. Go down to Windows Search and double click on it. Stop the service and then disable it from starting

 

Good thread, Mark

 

Dirk.

Mark,

 

Very interesting thread, I to I am suffering pauses in FSX SE? re the MSSE what part do you exclude....  Steam itself or drill down to Steam Steamapps FSX. I cannot locate an actual FSX.exe file nowdays..

 

Many Thanks

 

Mark

I cannot locate an actual FSX.exe file nowdays..

 

The entire FSX structure is still there.  With a standard Steam install it is here:

 

Steam\steamapps\common\FSX

 

Pete