• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Latest Vista "Update..."

n4gix

n4gix

Resource contributor
Messages
11,674
Country
unitedstates
Yesterday, I noticed that my flightsim machine had been "updated" via the automatic updater during the night.

I also found that my C400, SR20 and SR22 Avidynes would no longer work. In fact Vista's DEP would instantly HALT FSX entirely.

I discovered that this was true for all three products in both FS9 and FSX, so the "new problem" is clearly a result of the latest Vista "fixes..." :eek:

After reinstalling the C400 in FSX from the F1 Wrapper, not only was the C400 now operational again, but...

...the "problem" was fixed for both the SR20 and SR22 in FSX, and all three aircraft in FS9! :rolleyes:
 
Vista really frightens me - every time I think to upgrade something tells me that I should stick to XP. Seems to me that the user is no longer in control of their own computer :rolleyes:
 
For those three products we have an .exe "license verification" application stored in the ../Win32 folder. It is likely that one of the latest Vista auto-updates affected one of the native support files in some way. There's really no way for me to know since I didn't write the code for that executable (it's a service provided by Flight1 - for an additional fee of course).
 
scruffyduck said:
Vista really frightens me - every time I think to upgrade something tells me that I should stick to XP. Seems to me that the user is no longer in control of their own computer :rolleyes:
Click to expand...

You are totally right Jon, I disabled the auto update on my Vista and do it manually after checking what the new stuff does.
You are never sure what´s going on with this OS. I should have stuck with XP and recommend all that are developing with FSDS to do so...
 
As it turns out, the "culprit" was a "presetup for SP1" update that did the nasty deed.

MS has withdrawn that package for the nonce, whilst they sort out what made so many folks systems go pear shaped... :laughing:
 
I bought Vista but refuse to install on my "main" computer after reading this forum and a programming forum I frequent.

The only reason I got it all was for FSX and the eventual release of DX10 (which supposedly will never be available for XP ..is that still true?)

I'm sure Microsoft meant well but I find there are far too many annoying things built into Vista that attempt to "help" the average user (more like protect them from their own ignorance).

I put Vista in the same category as Windows ME; a bad first attempt at transitioning to a new OS concept. And functionally, it really isn't that much different from XP (unless, of course, you count "breaking" existing software and rendering many external devices non functional; at least upon initial release). Oh, the new "look" is nice but so what?

As someone said in the other forum I mentioned, "It's good looking crap!" :)
 
Last edited:
Well, it's not as bad as MS Bob.

I'll experiment with Vista64. I'll have two computers though. One on XP and the other on V64. It will be interesting to see how FS behaves on both and compare.

I fear that for scenery designing, I may keep using my WinXP machine, as I have my doubts that all of my tools will work 100% on Vista. Isn't there a 64-bit version of TCalcX here on FSDev somewhere?
 
Oh man, I had totally forgotten about MS Bob. What was THAT supposed to be?

I've just had an hysterical laugh attack. Thank you for making my day. :D
 
MichaelD said:
... (which supposedly will never be available for XP ..is that still true?)
Click to expand...

Yes, this will not change.

I have come to know Vista as a stable platform to run games. The FSX performance is pretty good with Vista32. But already developing for FSX starts to get annoying. You can no longer drag from the Explorer into a command window, and, and, and...

For business it is all XP. But the one thing which got me impressed with Vista is this: My son has his own PC, where he works with reduced rights. In XP not a single child game was running in this security context without me having to deep dive into the registry and ACLs to allow this and that. Bob Baumeister, Lars, and all others were a nightmare to get running.

This all has changed with Vista. Every game is running in reduced context without any additional action or hassle. That I like big time :D
 
Another update this past week came out for Vista32. Many with cameras are complaining they stopped working.

I noticed my Windows Media Player Ver 11 defaulted back to never being installed. When I went to run it I had to go through the setup steps once again.

All in all like Martin I have learned to work with Vista 32 and also am very careful not to shutdown background applications. It appears Vista handles these running applications much better then XP as long as we leave them alone.

FSX seems to need certain Vista applications and programs in order to stay stable. Shutting down DEP is a big mistake for me because if by chance VISTA crashes due to a driver issue and FSX is running the Stores become corrupt and a new install of FSX is in my future. Somehow the Stores relate to the activation of FSX and once that is gone no KB .exe that MS released for the 1722 error will fix FSX.

Defender also appears to have some internal ties to FSX. If I don't update and force a manual scan every now and then my FSX.cfg gets gauge corruption and FSX will not start properly and say certain certified gauges are not going to load because FSX can no longer find them. Once defender is updated and a scan performed FSX is back to normal on startup.

There are a few web sites that explan the running applications and what can be shutdown. That may be true for Windows to still function but FSX becomes unstable with some of these shutdown type tweaks.
 
jvile said:
FSX seems to need certain Vista applications and programs in order to stay stable. Shutting down DEP is a big mistake for me because if by chance VISTA crashes due to a driver issue and FSX is running the Stores become corrupt and a new install of FSX is in my future. Somehow the Stores relate to the activation of FSX and once that is gone no KB .exe that MS released for the 1722 error will fix FSX.
Click to expand...

This is true of WinXP also. If the TrustedStore becomes corrupt, you get the 1722 error, and even the MS KB fix will not save your FSX installation.

Pity this is still the case with Vista.

I will take this opportunity to ask you or any reading two questions about DEP and Vista:

1) My A64 cpu has some sort of DEP function on the chip (hardware). Is this DEP feature with Vista some sort of software data execution prevention mechanism?

2) Is DEP a known performance degrader?
 
You must log in or register to reply here.
Back
Top