Islam

Shouldn't there be an audible warning for the center pumps low pressure (when the center tank goes out of fuel)?

Just a small reminder that the autopilot will not engage below 400 ft AGL during takeoff.

I could observe that, during installation of the NGX, setup asks for authorization to install Direct X, which I always allow. Currently, I am having a chronic problem with my new laptop (purchased specially for the NGX), which is a recurrent problem occurring usually during playing FSX (although not always the case). I downloaded one of the software that analyzes the memory dump files, and it shows that the faulting driver is "dxgkrnl.sys". Please provide help with the following: 1. Are you allowing installation of Direct X during setup of the NGX? Or can we bypass this and install a more recent driver for Direct X? 2. Have any of you faced this problem before? Thanks.

Thanks for help. First, sorry for the confusion, as the specs written in my signature are those of my desktop not the new laptop subject of this problem. My laptop has i7 processor (intel). Second, as I mentioned above, they have already tried updating the drivers in the first repair visit. They have also installed a new clean W7 after format in the second repair visit. None of this has helped, and the problem re-occurred after the two visits. I have never done an overclock and actually do not know what it is.

How can I configure windows to do that?

Unfortunately I have purchased an LG A520 laptop seven months ago, exclusively to boost my FSX experience, for a relatively low price (nearly $ 1000). The laptop has i7 processor, 8 GB RAM, 2G Nvidia GPU, and Windows 7 64 bit OS. After two months from purchase, it started showing blue screen of physical memory dump, followed by automatic restart. The event was happening intermittently not related to any specific activities. I took it to the horrible service center and they delivered it back after "updating some outdated drivers" according to them. Two months later, same problem occurred again. I took it to the service center, along with printed screen shots from Event Viewer that show the list of CRITICAL events that show that windows has been rebooting without cleanly shutting down. After a week at the service center, they delivered it back after "format and reinstalling the OS". This did not make any sense to me because I got a strong impression that the problem is related to hardware, as I have been using my software for years, and I know how to manage. After painful arguments I had to take it back. Several days later, and after I spent those days reinstalling my applications, and doing the FSX painful tweaks, same problem occurred again. Now the laptop has been with the service center for a complete month, because I don't want to receive it back and keep asking for a refund or replacement. They keep saying that they have checked the hardware and it is perfectly fine. They also say that my problem might have been happening because I was using the "Hotspot Shield" software which "might put my computer at internet risks", or the problem maybe related to my external hardware (joystick, wireless keyboard and mouse... etc). They say they have not seen the problem while they were testing the laptop during that period. So they have taken absolutely no maintenance actions at this repair visit, and they want me to receive it back. Looks like they also have been manipulating the registry because the event log does not have the critical events any more. I have escalated this to every person I could manage to reach within LG and outside LG, and they all did not show any help. The problem is that if I take it back again, after several days or weeks, the problem is going to happen again and there will be no different scenario than the current. I need your help with the following: 1. Is there any kind of a quick test or check that I can perform before them at the service center, that confirms there is a problem with a hardware component? Is there any ERROR in the event viewer log that proves there is a hardware problem? I have lots of KERNEL POWER error events still existing in the log (but not the critical ones). 2. Is there a possibility that my software is causing this problem, although I have been using same software for years with other computers? Can Hotspot Shield cause this really?!!! 3. If I take it back, would there be any pust-to-the-limits test to let me reproduce the problem, and confirm if it is related to software or hardware issue? 4. Do you have any tips on how can I deal with this unhappy situation? Thanks for your help.

Unfortunately I have purchased an LG A520 laptop seven months ago, exclusively to boost my FSX experience, for a relatively low price (nearly $ 1000). The laptop has i7 processor, 8 GB RAM, 2G Nvidia GPU, and Windows 7 64 bit OS. After two months from purchase, it started showing blue screen of physical memory dump, followed by automatic restart. The event was happening intermittently not related to any specific activities. I took it to the horrible service center and they delivered it back after "updating some outdated drivers" according to them. Two months later, same problem occurred again. I took it to the service center, along with printed screen shots from Event Viewer that show the list of CRITICAL events that show that windows has been rebooting without cleanly shutting down. After a week at the service center, they delivered it back after "format and reinstalling the OS". This did not make any sense to me because I got a strong impression that the problem is related to hardware, as I have been using my software for years, and I know how to manage. After painful arguments I had to take it back. Several days later, and after I spent those days reinstalling my applications, and doing the FSX painful tweaks, same problem occurred again. Now the laptop has been with the service center for a complete month, because I don't want to receive it back and keep asking for a refund or replacement. They keep saying that they have checked the hardware and it is perfectly fine. They also say that my problem might have been happening because I was using the "Hotspot Shield" software which "might put my computer at internet risks", or the problem maybe related to my external hardware (joystick, wireless keyboard and mouse... etc). They say they have not seen the problem while they were testing the laptop during that period. So they have taken absolutely no maintenance actions at this repair visit, and they want me to receive it back. Looks like they also have been manipulating the registry because the event log does not have the critical events any more. I have escalated this to every person I could manage to reach within LG and outside LG, and they all did not show any help. The problem is that if I take it back again, after several days or weeks, the problem is going to happen again and there will be no different scenario than the current. I need your help with the following: 1. Is there any kind of a quick test or check that I can perform before them at the service center, that confirms there is a problem with a hardware component? Is there any ERROR in the event viewer log that proves there is a hardware problem? I have lots of KERNEL POWER error events still existing in the log (but not the critical ones). 2. Is there a possibility that my software is causing this problem, although I have been using same software for years with other computers? Can Hotspot Shield cause this really?!!! 3. If I take it back, would there be any pust-to-the-limits test to let me reproduce the problem, and confirm if it is related to software or hardware issue? 4. Do you have any tips on how can I deal with this unhappy situation? Thanks for your help.

The PAPI was all white with me, and yes I was to far to the left and had to recenter. Looks like it turned out for me to be the worst of you guys.

Grateful enough, when a girl makes the first move, I tend to output a BSOD rather than respond. Most probably because I am nearly certain that she is trying to make a fool of me, not make a real approach, because simply I am not the type of guys that cause such attraction, specially when I am sitting in the cafe bringing in the whole FS Gear, which looks freaky enough :) Let go the girl started touching the back of my nick while I was on short finals trying hardly to correct my too high glide path.. I would have never looked backwards.

To start with, I made it at first trial, on my laptop, in the middle of a crowded costa cafe, with a spoiled teen girl trying to distract me. Never thought I'd do it that way!!

Thank you very much guys for the comprehensive responses. This was pretty useful.

And how in real world I get to listen to the Morse? I think it is essential to verify the Morse against the station name.

So in real world, if I tube 112.8 on NAV while turning on the NAV speaker, I would get the ATIS instead of the Morse code? What about the Morse then?

Dear All,Happily enough, I can see that most of the frequencies published on the NDAC charts are working perfectly in FSX, namely the ground stations and the ATIS frequencies. To my understanding, the ground stations should be tuned on the VHF NAV radio, while the ATIS frequency should be tuned on the VHF COM radio, which both of them operate on same type of waves (VHF) but in different ranges (although quite near to each other).Now, while preparing to descent to Larnaca (LCLK), I should be tuning ATIS on the VHF COM radio to hear about the weather and available runways for landing. I do that using the VHF COM 2 radio. The chart - for some reason - says that the ATIS frequency is 112.8, which seems like a NAV frequency that cannot be tuned on the COM radio.Even when I tried to tune it on the NAV radio, while turning on the NAV speaker, I get nothing except the MORSE audio code of the LCA station which has the same frequency 112.8!!!Anybody got a clue on how this should be handled with radios?

Did you check the failures on the mcdu?

Thank you very much guys. I will try the wide screen feature and see.

So I don't need to change my graphics card to be able to use the 1920 x 1080 monitors? I mean this resolution setting will appear automatically in my resolution menu when I hook up the large monitor in the HDMI port?

Dear All,When flying in the VC, camera at the pilot head position or so, and in order to have a view wide enough to include part of the windscreen, the main panel, the whole MCP, and the center upper DU, I have to set the zoom level (as displayed in red in screen upper right corner) to around 0.5 zoom. This is done by mouse wheel in conjunction with space bar.The 0.5 zoom is wide enough, but makes graphics not sharp as they were designed, and it becomes a bit difficult to read numbers and move knobs and buttons near each other, let go using the FMC. I thought this problem would become less sensible if I hook up my 35" LCD via the HDMI. But this didn't happen. Still I can see that graphics are way better when zoom level set to 1.0 zoom, as things look actually as PMDG designed them to be.I thought in order to have the wide view, same time with zoom set to 1.0, I have to increase my screen resolution. This wasn't possible because I was already working on the maximum screen resolution allowed in my menu, 1366 x 768.So, if we have a graphic expert here, or someone from support staff, I have the following questions:1. What is the screen resolution PMDG was built on?2. Increasing the maximum screen resolution can be achieved only by hooking a bigger capable monitor, or I have to install a more capable graphics card as well?Thanks.

What exactly does this function do?

Really!!... With no autopilot nor autothrottle!!... Never heard of it. Will look it up then.

Dear All,Have any one experienced hearing the sound of the THS trim wheel rolling on its own during final approach, after the autopilot and autothrottle disconnected?Any explanation?

Dear All,At first I'd like to thank you very much for that file that finally have me salvation from my chronic problem with the Level D 767.I would just like to add a piece of information that might be useful here. My problem with the 767 was always happening at anytime I try to use the Ground Commands menu, which makes it a lot easier to trace the problem and reproduce it. Every single time I try to open this menu (a menu featured in the Level D 767 only), the system CTDs at once.When I downloaded your file (which really seams the first correct file I get to use), the problem was instantly cured, and I was able to run the menu normally without problems. But actually after my first restart, the problem reappeared again although the file is still in its place in the FSX root folder.After my previous search over the forums, I got to know that, most probably you have to register this file in the system registry so as to keep its effect at all times, and avoid the need to remove and recopy it each time you restart your system.Actually after I did this registration, the problem looks like gone for good!To register the file, open a new command prompt (write CMD in the RUN field), then navigate by DOS commands to the FSX root folder where you have put file, and finally write down the following command:REGSVR32 UIAUTOMATIONCORE.DLLPress ENTER, and you should see a message confirming successful registration of the file.

Have you checked the failures on the CDU? Perhaps there is a flaps failure that you have to clear from the CDU?

I agree. I actually never saw them increasing for me even with a RTO.

Oh yeah... really really unbeleivable!!!