Sign in to follow this  
falcon999

Please Please Help - constant Winrun.cpp crashes

Recommended Posts

I am sure this has something to do either with FlyScripts or C4TO. I recently installed both and since that time, have experienced frequent crashes. I originally thought it was only with the B777, but tonight I experienced the error in the SwissAir Ambulance (Hawker). I am at a loss, except to say that I have nearly no Winrun.cpp crashes without FlyScripts / C4TO. I've deleted and re-created default.keyI've deleted ALL aircraft HST filesI've deleted Autosave.sitI've tried flying in different parts of the world - no luck. NOTE: I installed Allen Kriesman's Flystart.dll today. Its possible it could have something to do with this, except I've been having frequent Winrun.cpp crashes since I installed FlyScripts and C4TO so I tend to think Allen's new code is not at fault.Anyone else with some ideas? Fly.ini attached. Here are my most recent CTD errors in GTFO.txt.....----------------------------------------------------------------Msg: Runtime execption code c0000005 (EXCEPTION_ACCESS_VIOLATION) at address 00667BF9File: WINRUN.CPP line 165Time: Tue Jun 04 22:04:50 2002errno = 2 (No such file or directory)----------------------------------------------------------------Msg: Runtime execption code c0000005 (EXCEPTION_ACCESS_VIOLATION) at address 6DA27EDEFile: WINRUN.CPP line 165Time: Sun Jun 09 18:46:36 2002errno = 2 (No such file or directory)----------------------------------------------------------------Msg: Runtime execption code c0000005 (EXCEPTION_ACCESS_VIOLATION) at address 004469D0File: WINRUN.CPP line 165Time: Sun Jun 09 18:58:09 2002errno = 2 (No such file or directory)----------------------------------------------------------------Msg: Runtime execption code c0000005 (EXCEPTION_ACCESS_VIOLATION) at address 00667BF9File: WINRUN.CPP line 165Time: Sun Jun 09 20:08:03 2002errno = 2 (No such file or directory)-DK----Fly! II v230Dell 8200 P4/1.8G, 512MB RAM, Nvidia GF4 Ti4600 v28.83, WinXP Home Edition.CH Pro Pedals and Yoke USB.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

the time you're spending hoping to find the cause will be better spent if you reinstall FLY2. I now keep two folders, so that if theprogram starts to give me winrun.cpp, I simply copy the other over it and everything goes away. Did you by anychance install the 777 over ver 2.3? tony

Share this post


Link to post
Share on other sites

I wasn't aware there was a B777 update to 2.3? Are you talking about Fly!II? I have version 1.2 for Fly!2 and checking the Precisionmanuals.com website, it doesn't appear to have been updated.On re-installing Fly!2, let me just make sure I've got this right - Start with 1.53 (on CD). Update to v210 and add the globe update and video update. Then install B777, then install v230. Right?-DK----Fly! II v230Dell 8200 P4/1.8G, 512MB RAM, Nvidia GF4 Ti4600 v28.83, WinXP Home Edition.CH Pro Pedals and Yoke USB.

Share this post


Link to post
Share on other sites

DK,My only suggestion comes from Rod Machado, famed Aviaition Speaker (paraphrasing):"If you move a switch and something bad happens, undo what you just did."Obviously, one software is not working with another. Remove both C4TO & Flyscripts. See if the WINRUP.CPP errors occur. May be with your install you just cannot use them. I do not run them. I had a problem a while back. When I removed them, formatted my drive and did not re-install them, FLY!2 was fine.It's not a fix for the errors but atleast you not may be crashing any more, able to enjoy FLY!2.Good luck.

Share this post


Link to post
Share on other sites

I have some time ago this type of problems, the culprit are my antivirus, I never see this interaction before, but at the moment I disable the antivirus software Fly! II run smooth as silk.I made high number of test, and the only program affected are Fly! II, the antivirus code appears to be too much MS-friendly :)

Share this post


Link to post
Share on other sites

As far as I remember,I used to get the "winrun.error" only when I messed with my render.ini.Try with the original and see if this helps.Rodger

Share this post


Link to post
Share on other sites

I have Norton Antivirus, but I disable it prior to flying. So this is probably not the culprit, although it is certainly possible.-DK----Fly! II v230Dell 8200 P4/1.8G, 512MB RAM, Nvidia GF4 Ti4600 v28.83, WinXP Home Edition.CH Pro Pedals and Yoke USB.

Share this post


Link to post
Share on other sites

I have definately changed my render.ini many times. Why would this affect fly's stability with FlyScripts / C4TO though? I could understand if Fly crashed all the time, but what Render settings conflict?Recall - these excessive Winrun.cpp errors seem only to happen when I'm using C4TO.-DK----Fly! II v230Dell 8200 P4/1.8G, 512MB RAM, Nvidia GF4 Ti4600 v28.83, WinXP Home Edition.CH Pro Pedals and Yoke USB.

Share this post


Link to post
Share on other sites

-DK,I have exactly the same system specs that you have (except for the dell) and I have no problem with FlyScript/C4TO. So I don

Share this post


Link to post
Share on other sites

I tried flying with default everything but it was too slow in populated areas. I then decided to bite the bullet and re-install Fly!2 from scratch. While I cannot say I flew a totally un-altered version of Fly!2 (because I had to install PMDG 777 and FlyScripts, it was as plain vanilla as it could be. No dice.There is clearly something conflicting on my PC with the B777 and C4TO that I cannot diagnose. It does not appear to happen with any other aircraft.Any other computer experts out there wish to venture a guess?-DK----Fly! II v230Dell 8200 P4/1.8G, 512MB RAM, Nvidia GF4 Ti4600 v28.83, WinXP Home Edition.CH Pro Pedals and Yoke USB.

Share this post


Link to post
Share on other sites

Hi DK,As far as I know, PMDG has not released an update to make the 777 compatible with FLY! II. The Boeing 777 was released for FLY!/FLY!2K and it worked very well with Flyscripts! and C4TO... I was actually a beta tester for the 777. If you're having problems running the 777 with FLY II, it's probably because the 777 isn't 100% compatible with FLY! II. Please be aware that there is a difference between FLY!2K and FLY! II. I'm sorry that I can't be more help - but I quit using FLY! II many months ago.Regards,Marc

Share this post


Link to post
Share on other sites

You're not right Marc. There is a PMDG B777 for FlyII only, it was released around April 2001. And there is a B757 for FlyII which was released a couple of weeks ago.I fly 'em both in FlyII.Cheers,Michael

Share this post


Link to post
Share on other sites

I am flying with the B777 for Fly!2. The version is 2.11f.-DK----Fly! II v230Dell 8200 P4/1.8G, 512MB RAM, Nvidia GF4 Ti4600 v28.83, WinXP Home Edition.CH Pro Pedals and Yoke USB.

Share this post


Link to post
Share on other sites

Arrghhh,You are correct - I need to quit posting before I'm actually awake :-). The FLY!II 777 was actually released around August 2001 - FLY!II was released in April. Anyway, I was involved in testing that aircraft - and never experienced any problems (except I never had a chance to implement the new callsigns). Anyway, back when this forum was considerably busier, the winrun.cpp error was a hot topic for discussion. Some people had the problem, many others did not - it seemed to be system-dependent. I can tell you that I'm 99.9% sure it is not related to Flyscripts! because many people who reported the error were not even using Flyscripts! Again, I'm sorry that I can't be of more help.Regards,Marc

Share this post


Link to post
Share on other sites

Good morning all:I am reading these "Winrun.cpp" postings with great interest, in hopes that someone will come up with a solution to the problem!!!!Myself and many others are having the same problems. My unit specs are: Fly!II built to v230, Dell unit, P3/733, 256MB RAM, Nvidia GF4 Ti4400, v28.83, Win'98SE, with C4TO and Flyscript installed.For the past two weeks, (every evening including weekends) I have not been able to make an approach and land any of the aircraft that I am flying at that moment! No matter what the distance or duration of the flight, my unit will crash to the desktop and give me the dreaded "Winrun.cpp error". It always happens prior to completing the flight. VERY FRUSTRATING WHEN JUST AS YOU HAVE THE AIRPORT IN SIGHT, ALIGNED WITH THE RUNWAY, THEN................nothing but desktop.I have deleted all *.hjst and *.sit files as the majority in the Forum have advised but to no avail!!I wish that I could offer a solution but I can't, other than to start all over again. With all of the add-ons, what a pain that would be. I must say thought that the one who solves this "Winrun.cpp" problem will make a lot of people happy. He (she) will become KING OR QUEEN FOR A DAY AND KING OR QUEEN OF THE HILL!!!!!!!!Curtis

Share this post


Link to post
Share on other sites

Curtis:Try running without initializing the C4TO script. I find that Fly runs fine if I run without C4TO. Please try this a few times and report back. If we can isolate it to C4TO, then perhaps we can figure out what's causing it.Interesting, by the way, that you are running a Dell. I wonder if there's something loading from Dell that is conflicting with C4TO.-DK----Fly! II v230Dell 8200 P4/1.8G, 512MB RAM, Nvidia GF4 Ti4600 v28.83, WinXP Home Edition.CH Pro Pedals and Yoke USB.

Share this post


Link to post
Share on other sites

Hello DK:I will try Fly!II without initializing C4TO as you suggested. I never thought of trying that. C4TO in itself is a good program. I rely on it a lot. But of course, I will do anything I can to help solve this problem. I'll let you know how I make out!!Thanks for the suggestion!Curtis

Share this post


Link to post
Share on other sites

I think C4TO is a GREAT program. I much prefer flying with it over the default ATC. But I am certain that C4TO and PMDG's Boeing 777 are conflicting somehow on my PC. C4TO runs fine on all other aircraft, by the way. But it consistently crashes Fly when I fly the B777. And as with you, I tend to have a desktop-crash in flight, although not always on approach.-DK----Fly! II v230Dell 8200 P4/1.8G, 512MB RAM, Nvidia GF4 Ti4600 v28.83, WinXP Home Edition.CH Pro Pedals and Yoke USB.

Share this post


Link to post
Share on other sites

DK:I neglected to tell you that I don't have the 777 yet. Therefore that can'te the conflict on my unit. My crashes occur no matter what a/c I fly! I agree that "C4TO IS A GREAT PROGRAM". I don't know what I will do if C4TO turns out to be the problem. If it is, I'm sure that a solution will be found! Now that I have it in use, I can't imagine flying without it. I have had more successfull landings with its use than when using the standard ATC program! I think that we should all hang in there until a solution is found!Curtis

Share this post


Link to post
Share on other sites

DK,Do you crash approaching ALL airports with the B777? Or...is this happening over and over at a particular airport or two?

Share this post


Link to post
Share on other sites

This is a consistent problem when I have "loaded" C4TO and am flying any one of the B777 liveries. It occurs sometime during flight, including when on the ground taxiing to takeoff, in the air, or on approach. I've not once, though made it through a B777 flight in full from takeoff to landing.I've had the problem in different parts of the world (thus eliminating the possibility that this "bug" happens only in areas where there is custom TerraScenery). It happens with TerraModels buildings in "view" and in the air with no models in view. It happens with clouds and without.I had thought it was occuring with other aircraft, but that might just have been a one-off bad coincidence (that is to say, I had a Winrun.cpp error while flying the Hawker, but I've since flown it and nearly all other aircraft with C4TO and no trouble).So conclusion - Whenever I choose a PMDG 777 plane and load C4TO, sometime during the flight, Fly!2 will crash to desktop with a Winrun.cpp error.I wish I could isolate it more.-DK----Fly! II v230Dell 8200 P4/1.8G, 512MB RAM, Nvidia GF4 Ti4600 v28.83, WinXP Home Edition.CH Pro Pedals and Yoke USB.

Share this post


Link to post
Share on other sites

Good morning DK: :-) :-)I did as you suggested last evening. I started up Fly!II, without initiating C4TO, (used default ATC), and flew for approximately 2 1/2 hours "WITHOUT ANY PROBLEMS"!!! :-yellow1 :-yellow1 :-yellow1 However, I don't think that a 2 1/2 hour flight is a sufficient test, so I will try a longer flight tonight, again without the use of C4TO (boy that hurts) when I get home from work. While flying around last evening, I felt lost without the use of C4TO!! :'(I hate to admit it but I think that you are correct in your assumptions; Winrun.cpp error may have something to do with loading up C4TO. :'( Looks as though you are getting closer and closer to isolating the problem. Boy, I sure hope so!! A lot of people would be happy if you did! :-)Maybe the author of C4TO should be made aware of the problem, (if he hasen't been made aware already). I'm sure he would be more than willing to help from his end! C4TO is such a great program. :-beerchug I would hate to have to give it up. I get better results flying with the use of C4TO.Good luck!! I'll let you know tomorrow how I make out this evening. Anything else you would like me to try?Curtis

Share this post


Link to post
Share on other sites

Curtis,There are many things that can cause a Winrun type error. Was this flight with the B777? I have never had the problems mentioned here with C4TO. Though I have purchased the B777, I haven't had time to install and fly it yet, so maybe there is some compatibility problem.Some other things to consider - C4TO is not a program, but a script designed to run within the Flyscripts! program. Maybe the conflict is coming from Flyscripts! Also - are you running any other scripts besides C4TO?You may want to contact the author of Flyscripts!, Anthony Merton, and see if he can shed any light on this.

Share this post


Link to post
Share on other sites

Randall:As I understand it, if the FlyScripts.dll file is in the proper directory under Fly!2, it will be "loaded" in the background upon Fly's startup. In fact, in checking loaded processes (I forget the keystroke, but there is way to bring up a window that shows all loaded DLL's), I know that FlyScripts is loaded. So when flying, FlyScripts is in the background at all times. I've had a few Winrun.cpp errors here or there since I installed patch v230 - before I ever used FlyScripts and even now. But they are few and far between. However, when initializing C4TO (using ALT-F12), the Winrun.cpp errors happen all the time with the Boeing 777. I do get them occassionally with other planes, but I'm not convinced its caused by something conflicting with C4TO, because I can run all other planes without the CPP error.The only time its 100% is when I use the B777 and C4TO has been initialized. That is why I'm begining to conclude that there is a conflict with something in my desktop configuration and C4TO. I want to reiterate - C4TO is one of my favorite Fly!2 add-ons. I too am dissappointed that I cannot run C4TO with the 777. I am very hopeful that we can isolate the problem and get it fixed. Hope this helps.-DK----Fly! II v230Dell 8200 P4/1.8G, 512MB RAM, Nvidia GF4 Ti4600 v28.83, WinXP Home Edition.CH Pro Pedals and Yoke USB.

Share this post


Link to post
Share on other sites

Ignore this post. I am posting a "top level" message to reset the window size for future replies. Please reply to this message for continued discussion on this thread.-DK----Fly! II v230Dell 8200 P4/1.8G, 512MB RAM, Nvidia GF4 Ti4600 v28.83, WinXP Home Edition.CH Pro Pedals and Yoke USB.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this