Let's not feed the bear any more shall we?________________________________________________________________________________________________Intel D975XBX2 'Bad Axe 2' | Intel Core 2 Duo E6600 @ 3.20Ghz | 2 GB Super Talent DDR2 800 | Big Typhoon VX | eVGA 8800GTS @ 565/900 | Seagate 2x320GB SATA RAID-0 | OCZ GameXStream 700W | Creative X-Fi | Silverstone TJ-09BW | Matrox Triplehead Setup

>I've experienced the following problems with these payware>aircraft after installing SP1 with a clean install of FSX and>VS2005...did not have these problems pre SP1:>>FSD C337 FSX: Whenever I cycle through the views and return to>the C337 VC view I get an hourglass and the dreaded MS error>message. I don't have this problem with any of the default>aircraft.>>RealAir SF260 2007: MS Error message and freeze whenever I>right click the screen to check AI aircraft and then return to>the VC cockpit. I've also occasionally experience freezes>when cycling through views. Again, no similar problems with>the default aircraft.>>Anyone else experience this after installing SP1?>LOL!! I'm sure everyone has forgotten about my original post but in case anyone is interested I decided to remove the 93.71 drivers for my GeForce 7600gs and install the "old reliable" 91.47's and presto...problem gone! LIFE IS GOOD!!

I just booted into my xp array and installed sp1 and had no trouble updating fsx or running the cirrus sr20 afterwards. The plane runs so much faster than it does in vista. This plane just does not like vista on my machine. I plan on updating the video drivers for xp and vista on my machine this weekend just to see if i pick up anything or if i have to revert back.

>Of course you would love someone with a complaint about the liberty (which I can't myself speak of) to keep their comments restricted to your own forums. That way they can just sit there doing little damage as they are ignored or insulted away. We've maintained support forums since day one because it's part of the business...if you build 'em ya have to support 'em:-)Developers support forums are the best place for support since the development team knows their product better than anyone else.Sorry, at no time will we try to use a public forum like Avsim as our own support forum thus the invitation back to our forum.See how simple that is:-)

Glad to hear it Dave. If anything shows up on our end which will help you out on Vista we'll let you know. Would you be willing to test something out? If so, PM me at our forum.:-)

>The issue with DEP causing certain eaglesoft products to crash>is something any vista user will experience if they have DEP>turned on. If it really does not occur, then something is>wrong with your DEP protection. Of course the problem is>related to your aircraft and it is equivocation to call it>"vista problems". The DEP issue is unfortunate for eaglesoft,>but is not restricted to their products. The issue affects a>number of programs apart from fsx, and particularly add ons.That is just plain malarky (if unfamiliar with the term, google it).The simple fact is that when ACES first started working on FSX, even they had issues with Vista's overagressive DEP, which explains why so much stuff is now stored OUTSIDE of FSX's root folder structure.The problem faced by anyone writing a program (which is all addon a/c packages are after all) that needs to access FS's own database files for whatever reason (such as GPS lookups) will encounter DEP and UAC "issues" because FSX's data is normally installed within the Program Files area. All it takes is one "unauthorized lookup" for say, the list of closest airports and - BAM!!!Never mind trying to write to a file; simply attempting to READ data from an existing file is a big "NO-NO" under Vista's rediculously aggressive protection schema.In spite of your erroneous interpretation above, there's not one, single, solitary thing that any addon developer can do to "work around Vista's security."Given this, just how is that the ADDON DEVELOPER'S "problem???"If you know any answers, I'm sure we're all anxious to know! None of the crack developers at ACES seem have any solutions for third-party developers, so please, share your secrets...

Hi Ron,I have just purchased and installed the Columbia 400 for FSX and am having a bit of a problem with Vista not liking something that I have done.Do you have a FAQ page where I can have a look at the Vista related configuration options to get this excellent looking aircraft going.With thanks,Chris Porter:-outtaPerthWestern AustraliaIntel Core 2 Duo E6700ASUS P5N32-E SLI Deluxe Motherboard4GB Corsair VS DDR2 667Mhz RAMInno3D 8800 GTX 768MB GDDR3 590MHz VideoASUS MW221u 21" Wide Screen LCD2 x 320Gb WD SATA DrivesCreative X-Fi Platinum Sound Lian Li PC-B20B Aluminium Black CaseMS Vista Ultimate OEMCH FlightSim Yoke USBCH Pro Pedals USBTrackIR 4 Pro and Track ClipMSFS FSX Deluxe Edition Full install at 1400x960x32Check out my 5th Around the World flight with MS FSX at http://members.iinet.com.au/~portercbp/fly...W_05/index.html

Bill Learning,I know what malarkey is. I don't understand how I was unclear, if you'll read my last two sentences which you quoted above.What I meant is exactly what you said, that the issue is widespread. My criticism is simply that vista's problem is in fact the eaglesoft add on since that is the cause of the DEP violation. Ron's putting the responsibility on users for their vista security management is insulting and inaccurate business speak. They are not the only developer that has had to deal with vista's over-tight protection; but they are the only developer I have seen that has blamed the user for their own software's (understandable since it was written in xp) incompatibility. James Shretzman

Chris, look here: http://www.eaglesoftdg.com/forum/viewforum...b74ef9305cb0157And here: http://www.eaglesoftdg.com/forum/viewforum.php?f=56And one more: Click this link for more on the Flight One Ecommerce Wrapper system and Windows Vista http://www.flight1.com/view.asp?page=vista

>Weenie wrote: but they are the only developer I have seen that has blamed the user for their own software's (understandable since it was written in xp) incompatibility. Such a statement is preposterous. As Bill outlined, Vista users must give themselves permission to use their own system. :-) Suggest you read the three links I just posted to Chris and educate yourself a bit with regard to to Vista and its security requirements in order to avoid spreading misinformation.:-)

Thanks Ron, the only way I could get it to work was to globally disable DEP... Kind of drastic, but I got there eventually.Great job with the aircraft BTW. Most enjoyable.Cheers and thanks for your help,Chris Porter:-outtaPerthWestern AustraliaCheck out my 5th Around the World flight with MS FSX at http://members.iinet.com.au/~portercbp/fly...W_05/index.html

>Thanks Ron, the only way I could get it to work was to>globally disable DEP... Kind of drastic, but I got there>eventually.>>Great job with the aircraft BTW. Most enjoyable.>>Cheers and thanks for your help,>>Chris PorterYou are welcome Chris. Unfortunatly that is the way it is for the time being. Users will need to interact with Vista security settings:-(Having said that, we are actively working with the good folks at Flight One for a way to minimize users interaction with Vista and its Security settings. By the way, could you PM me in our forums?More on this as we progress..:-)Thanks for the feedback on the FSX Columbia 400. Everyone seems to be enjoying her in FSX and SP1!:-)

Whatever. This is what you said in this very thread:"Again, our answers are honest attempts to help folks realize that their Vista problems are not related to our aircraft.If they were then ALL of our users would report the same issues you have and that sir, is simply not the case."Vista DEP causes fsx to crash because of the aircraft. Take the aircraft out, and no crash. Every vista user who has DEP turned on will report this interaction because that is the nature of the security measure. I'm not saying it's eaglesoft's fault that the new operating system does not like their product. It's vista's fault. But I am saying that the aircraft was designed in such a way which makes it incompatible with vista in its standard security configuration. Many pieces of software are encountering this issue so it's nothing mysterious. Yet the way you depict things in the above quote is that the problem is somehow the fault of the user having "vista problems" and/or perhaps created by vista and not in any way caused by the product. This is absolutely not the case.And the way you described Bill's statement demonstrates to me that you know very little of what you're talking about. In this case, Vista users don't give themselves permission to use their own system but rather they change the way the system interacts with a particular set of programming - which is itself not part of the OS.More important, why don't you change your attitude towards your customers? I mean, how many offended people does it take for you to get the picture.

The sr22 is working ok for me but both of my Wilco legacy and citation x aircraft are having problems with killings FSX. My Eaglesoft Raytheon Beechjet doesn't seem very reliable now either. The problems seem intermittent. Several of them wouldn't load at all with Vista's DEP turned on so I had to disable it. It has been awhile since I used them so maybe it is Vista instead.The only other payware aicraft I have, have been fine being the SR22 and the Glasair III.

>Weenie wrote: And the way you described Bill's statement demonstrates to me that you know very little of what you're talking about. In this case, Vista users don't give themselves permission to use their own system but rather they change the way the system interacts with a particular set of programming - which is itself not part of the OS.Our statement stands. As Chris's success story above illustrates, disabling DEP eliminates the issue and the aircraft runs as designed.It should also be understood that third party developers build for a specific Flight Simulator Version, NOT a specific Operating System.You see, developers MUST build for a specific Flightsim Sim Version since that's where the product lives and operates.Please understand that we never intend to offend folks but neither do we stand aside while while folks post half of a story or post misinformation.:-)