jdk2

Your scenerio doesn't apply to me as I'm not running any A/V software.I formatted/reinstalled Vista Ultimate x64 SP1, installed FSX Acceleration, and the PMDG 744X with the provided integrated installer.The issue remains. I've got UAC off, permissions for FSX allowing full access in it's own folder on another hard drive dedicated to FSX. Regards,Jim Karn

Uninstalled the 744X and reinstalled using the integrated installer. The same issue is present.Using Vista Ultimate x64 SP1 on FSX with Acceleration with no anti-virus or disk checking utilities active. Installed with the "Run as administrator" option. All drivers are up-to-date and no malware is present.As others have stated, as soon as the autopilot is activated, the aircraft appears to go into slew mode at a 16X sim rate and spins in a violent nose to tail attitude. The wings remain fairly level during this brief process until the aircraft crashes.Regards,Jim Karn

The issue was with FSX. Those download links are for installation into FS9.Regards,Jim Karn

Well said. Let's hope he will reconsider.Regards,Jim Karn

Hi James,I can confirm the same behavior after the update in Vista x64 and FSX. I uninstalled and reinstalled the entire application and am still seeing the same behavior with the violent spinning when activating the A/P.Additionally, in the Cargo variant, I still can't click on any of the buttons where the FMC, Autobrake etc are displayed in their own window in the VC.Regards,Jim Karn

When you pull up the nVidia Control Panel, go to Manage 3D settings and in the right pane, click the Program Settings tab.Regards,Jim Karn

From Lamont Clark as posted on Phil Taylor's Blog: http://lc0277.nerim.net/wiki/index.php?Dis...airport%20namesRegards,Jim Karn

Aero is disabled when running FSX since they both would be trying to access the same resources. FSX and most 3-D applications aren't compatible with the new Desktop Window Manager and Aero in Vista.Regards,Jim Karn

Glad it's fixed but you may want to mention your exact problem so that Bryan can have a look at it. He's the developer of FS2Crew and asked you previously in this thread.Regards,Jim Karn

Hi Timo,Unfortunately, it's a "feature" and there's nothing you can do but revert to DX9. nVidia has been less than helpful with the issue and it's doubtful the problem will ever be addressed.The following link will take you to nVidia's site to report bugs found at the driver level. You might want to fill it out. Sort of "the squeaky wheel gets the grease."https://surveys.nvidia.com/index.jsp?pi=749...8f09e040b4a437aRegards,Jim Karn

This post explains why and what you can do to solve the issue: http://forums.avsim.net/dcboard.php?az=sho...ing_type=searchRegards,Jim Karn

http://www.techpowerup.com/downloads/1031/...U-Z_v0.1.9.htmlGPU-Z 0.1.9 just released.Regards,Jim Karn

Acceleration includes SP1 and will install it if it doesn't find it.Regards,Jim Karn

Hi Richy,Follow Jim's advise. The repair option will only replace files that are missing.Regards,Jim Karn

Hi Robert,I suspect you aren't giving the memory enough voltage which is causing the crash. If you didn't get any documentation with the memory, check Corsair's website. You're memory should be able to withstand 2.1v easily, and probably needs 2.2v. Try 2.1v and test the system. There's usually a setting in the BIOS to adjust it.Regards,Jim Karn

Dave,There is no boot.ini file created in Vista. sargeski posted the exact steps to expand the process address space and I guess I'll give it another go:From the Start menu > All Programs > Accessories then right-click on Command Prompt and choose "Run as administrator"When the Command Prompt opens, type the following at the blinking cursor:bcdedit /set increaseuserva 2560Phil Taylor explains the whole enchilada in excrutiating detail here: http://blogs.msdn.com/ptaylor/archive/2007...ress-space.aspxBill Leaming also explained it here: http://forums.avsim.net/dcboard.php?az=sho...ing_type=searchRegards,Jim Karn

The first thing comes to mind is the voltage being applied to the RAM. Do you know what it's set at? It may need just a little bit more. And you may need to relax the memory timings as well until you can get it stable.Regards,Jim Karn

Sanal,As John indicated, you need to make FSX >2GB aware either by installing SP2 or Acceleration. If you're not willing to install SP2 or Acceleration, you can follow the directions here: http://forums.avsim.net/dcboard.php?az=sho...ing_type=search Regards,Jim Karn

Hi Gary,Enter the following into an *elevated command prompt:BCDEDIT /set increaseuserva 2560*To get the elevated command prompt, choose Start > All Programs > Accessories > then right-click on Command prompt and select "Run as administrator".Then try the same flight that exhibited the OOM. The fix above may cure the issue.Regards,Jim Karn

Run this small application and you should be set: http://www.flight1software.com/files/FS_Registry_Repair.exeRegards,Jim Karn

John,It's not that they're staying away; you're situation appears to be unique. There has to be something different about your setup that's effecting the outcome of saving flights. Either in your Documents folder permissions where, by default, FSX saves them or possibly in the way Norton is interacting with the OS. You said you've disabled it, but is it really disabled, if you know what I mean? It could be interferring with the OS enough to not allow the changes needed to save a flight.On my system with Vista Ultimate x64, permissions in the Flight Simulator X Files folder under Documents are still default where I, as the user, don't have full control enabled and the flights save just fine. I never changed any user or system permissions in that folder at all. But I do have UAC turned off. Regards,Jim Karn

You're missing the title= line at the beginning of the section under fltsim.4. It also appears you're using a different .air file as well. It will need to be named Airbus_A321 easyjet.air for the aircraft to be displayed. Regards,Jim Karn

This utility from Flight1 will restore the registry settings for FS9 or FSX: http://www.flight1software.com/files/FS_Registry_Repair.exeRegards,Jim Karn

I can also feel your pain, but don't look back Your system should be more than capable. Regards,Jim Karn

>after reducing the tree to my main drive>using the "cd .. " tricks...For future reference, that's not necessary. It works from the cmd prmpt default location C:UsersYour_User_Name.Regards,Jim Karn