fnav77

I see that he doesn't recommend installing updates at the moment, but I don't see a solution.

Hi folks, Just to share what happened to me recently... Last week, I innocently installed the last batch of routine Windows 7 updates... Never again! On re starting the computer, I had a secure boot violation message and Windows would not start again. The message was then taking me to the BIOS/UEFI page of my ASUS motherboard. After some research online, I found out that a boot violation is a known problem. The motherboard basically stops the OS from starting if it does not recognise all the elements on the computer. To get rid of it, and therefore allow Windows 7 to start, you need to disable Secure Boot in your motherboard BIOS/UEFI. First hurdle, on my ASUS motherboard, there is no way to just disable secure boot. You either have to save the secure boot keys on a usb and then delete one part of them, or just delete/clear them altogether. Anyway, I deleted all the keys and disabled secure boot. Windows 7 came back to life straight away. What's following is even more disturbing....After more research on the topic, I found all sorts of stories on Windows 7 updates.... I will spare you the details! One of these updates would not uninstall and would always come back.... Anyway, I somehow cleared all the updates which I suspected caused the Secure Boot violation, then proceeded to install the boot keys again to re enable secure boot. To no avail. After more research, I found out that these updates had probably changed something in the boot manager and the keys were not valid anymore....also, Windows 7 was never supposed to be secure boot enabled, but the motherboard manufacturer somehow managed to make it compatible. Go figure out, this is way beyond me...! By now, after reading all this, you are probably realising this stuff is not for the common computer user... this is fairly advanced stuff! Anyway, I am giving up, I will not re-enable secure boot. I don't want to end up messing my PC and be unable to use FSX. One big lesson.... never install Windows 7 updates! As they say, if it ain't broke, don't fix it!

I will give this a try when I have my pc set up again, and will report back. In the meantime, I would be keen to hear more feedback about it. Thanks.

Thank you basementflyguy, welcome on board!

Thank you, Jaime, for the comments. Don't worry about offtopic, it does not bother me at all. I will look at your videos. Thanks.

Hello fellow simmers, Enjoy this very scenic approach. <youtube>

There should be a cross bleed procedure in the Supplementary Procedures (section 7, engines/apu), FCOM 1.

No worries. Some people seem to think that with that last update, the "inspector" does not work as well as it used to. I am not sure, but it took me a long time to get a decent set up (mind you I had forgotten what the settings were before). I am curious to find out what the nvidia control panel can do.... that is for another thread, I guess.

I think that if you have installed the latest nvidia gpu driver, then the nvidia inspector fsx profile will show as microsoft flight simulator 10. It is normal. There are a couple of threads around here in the Avsim forum about that.

You do need a good cpu for FSX, I think. Also, a few tweaks will help and using the nvidia inspector will improve things. With he cpu you have, you need to find the right compromise... All the best

I think that when you install the latest Nvidia driver, it changes the Fsx profile to flight simulator 10, that is at least what happened on my pc....Also, you apparently need to be cautious before updating the inspector with the latest version (there is a post somewhere in the forum about it)

Thanks Richard for the heads up.

Hi guys, This is the latest video on the channel. A good insight into flying a raw data ILS approach on the 777. Enjoy, and try it out.... it is good fun! <youtube>

It is actually a good idea to stick to UTC, I guess, even if local time does not match.

Are you surprised?

FSiPanel is good, but the main thing it does is position the aircraft for approaches. It does not really manage failures as such, except engine flame out....I don't know the others.

Talking of time zones in FSX, some areas/countries are not in the correct time zone.... is there a way to change that? Thanks.

Thank you, I am tempted by fs2crew 777....

Maybe it is wise to wait for the investigation to shed light on what happened. The "black boxes" have been found, so provided they can be deciphered, the investigators should easily work out what happened.

The Rex textures sit along ORBX Global nicely... no problems for me.

I have also noticed that NVidia Inspector was showing FSX as FS 10.... Does it mean that the inspector no longer works with FSX, or can you still "tweak" various settings, obviously using the Flight Simulator 10 profile (and editing it as required)? I can't roll back to the previous driver version for some reason. Nvidia Inspector makes the difference between good and excellent graphics, so I hope it is still usable.

Offer has now expired.... ah well, next time.

Very sad news indeed! I hope an open, transparent and unbiased enquiry will take place. Condolences to those involved.

Hello fellow simmers, Here is the latest video... Enjoy!

I think the PMDG 777 is a very good choice.... I would not hesitate one second.