pschlute

Try the wiew menu in the sim. Change to windowed mode then exit the sim.

STOP !!!
 
Before you do a re-install, take the magdec file and put a copy of it in a new folder named scenery. Then place that folder in a new folder named magdec. Place the magdec folder into the existing addon scenery folder and add the folder to the scenery library. Keep it at the top of the library screen so it is a higher priority than any other scenery. Restart FS9 and test.

You need one further step in win7, just click anywhere in the dialoge box after pressing OK and it will work

The assumed temperature will be arrived at through a calculation. Runway length plays a part here as well as obstacle clearance in addition to aircraft weight, wind direction and OAT. A tool such as TOPCAT can do the calculation for you.
 
OAT should be the actual OAT, so if you calculate an assumed temperature takeoff of 50c and the OAT is 20c  the FMC input should be 50/20
 
When conducting a normal (non-autoland) landing, you should disengage the A/P and A/T somewhere between 1000 and 1500 feet above the airport elevation. Different airlines will have different procedures, but you should be in landing configuration (flaps and gear down) and in a stabilised approach with regard to descent path and speed. The height at which this takes place will be decided by the airline's SOP, you will get no guidance from the aircraft itself.
 
Decision HEIGHT is a term that is usually used for autolands as it refers to radio height above the ground. When conducting a Cat 1 ILS or VOR/NDB (manual landing) you will be using decision ALTITUDE which is barometric altitude. The two numbers will vary widely depending on the altitude of the airport. But note that DH or DA are the point at which the pilot must decide to continue the landing if the visual requirements are met (seeing the runway) or not continuing the landing (going around) if the visual requirements are not met. These heights/altitudes are published on the approach charts for each individual runway.  DH or DA are not where the pilot takes manual control of the aircraft, that must happen before.
 
Different aircraft have different recommendations for use of A/P and A/T. The 737 is one where Boeing recommends the A/T should be disengaged when the A/P is disengaged on approach.

It wont cause the engines to run any faster. They will run as normal and your cruise KIAS or Mach number will be the same as in still air.
 
What will be different is the chunk of air you are flying in is being moved away from your destination at say 70 nm per hour. Thus your groundspeed, lets say 450 knots in still air, will now be 380 knots.
Assume the cruise section of the flight is 450 nm and this is where you encounter the headwind. in still air you would cover that in 1 hour at 450 knots groundspeed. At 380 knots groundspeed it will take you 1.18 times as long , so 1 hour and 11 minutes. You will need to know how much fuel your aircraft burns per hour, do the calculation for 11 minutes extra and add that on.

Throttles at idle ?

Some addon aircraft handle sim speed up better than others. You could try changing out of VNAV/LNAV when you want to speed up and use ALT HLD and MACH HLD instead. This helps with the PMDG aircraft.

Nvidia inspector worked great for me Try the settings in this post.  http://www.simforums.com/forums/drivers-nv-inspector-fsxcfg-complete-guide_topic36586.html

It may be an addon scenery you added that is causing it.
 
I believe one solution is to create a new addon scenery folder called for example Magdec. Put your magdec file in a scenery folder within it.. Then add to the scenery library and keep near the top (high priority).
 
I am not 100% sure of this solution so hopefully someone else will confirm.

You are doing everything correctly.
 
Only thing i notice is fltsim.10 has no entry for title=.   Will that cause the following entries not to show?  I dont know. Can you see the other ai a/c from 11 onwards ?
 
Only other thing is the use of the qutation marks within quotation marks.... ".....'Michael Otto'"   Again I have no idea if this would affect.
 
I think you have already done this but I always use speeds for jets in the aircraft.txt file of 200 if I use flightplans with the @ symbol (using TTools). If there is a problem with the flight time, using the realistic speeds can prevent an a/c arriving on time, though wont affect a departure.
 
You obviously know what you are doing so I assume you have looked in the sim an hour either side of the scheduled departure times to allow for the FS9 time bug ?

Like the other poster said, that is too tight to both get down and slow down.
 
 
 
 
There isn't really any Autoflight mode. Pressing the Autoflight button once on the ground arms the A/T. Pushing the throttles beyond about 70%  N1 engages A/T in TOGA. Pressing Autoflight again once in the air (above 400 feet i think) engages A/P. There are separate buttons to disengage A/P and A/T. You can fly manually with A/T engaged or not. 
 
 
 
 
Yes:
when you change altitude, dial the new alt and pull the Alt button for level change or use VS. You are now out of Profile (FMS) mode.
 
heading....dial the required heading and pull the hdg knob, you are now out of FMS nav mode.
 
speed ... dial your required speed and pull the speed knob. You are now out of FMS speed mode.
..........If you are in level change at the time the A/P will use pitch to maintain the climb/descent at that selected speed with either climb or idle thrust from the A/T.
..........If you are in level flight or VS descent when you pull the speed knob the A/T will use thrust to maintain that selected speed.
 
Good luck and post again if you have any questions.
 
ps... the MCP knobs for ALT SPEED HDG can be pushed as well as pulled. Make sure you are pulling them.

Try TOPCAT

The great thing about FSUIPC is you can make assignment/sensitivities for each different aircraft type you have.
 
For searching forums use the advanced search function...little cog wheel icon to the right of the search window.