I've asked this a couple of times before without getting any suggestions but I'll give it one more shot!When I try to install the 1.52 to 2.10 patch for Fly!II I get an error message saying that "Old file not found. However, a file of the same name was found. No update done since file contents do not match". And then the patching process quits. At that point it seems like it's the ntpath.pyc file that it tries to patch.Has anyone else had this problem and found a remedy? I get the error having done a fresh install of Fly!II (and not installed on the computer before). I also tried downloading the patch again and running it but to no avail. Strange thing is that I used to run Fly!II on another computer without this problem. Then all the sudden it popped up and now also on this computer?!?/Krister

I don`t know why this happens and won`t try to find out either. But I have some experience with this: If I choose "Custom Install" I get this message every time. I solve it by choosing default install instead. If I get this message between the patches, I do a disk cleanup and delete everyhing in WindowsTemp between each patch. Sometimes programs leaves crap in this folder, maybe the "old" file. This has also been solving problems with many other programs.

G'day Krister,This used to be the hottest topic on the forum in the early days.The RT patch process that Tri uses is strictly a memory dump patch and is not finding the correct info so it comes up with the "old file not found error .... but file ".Make sure that you start with a clean machine. ie all previous fly!II files removed.Make sure that you have no TSR'S running, especially virus checkers or any web security programs.disable sound in windows.now load the Fly!II off the CDThen apply patches in order.DO NOT run Fly!II between patch installations.after patching re-enable sound in windows.Some people were plagued by this problem but most managed to finally get up and running. Hope this helps.Cheers,Roger @YSSY

Andrew and Roger,thank you very much for your advice guys. Actually Andrew's tip worked since I always use to choose the custom install (don't know why really) so it's patched now!! Time to bring out the 777 and 757 from the hangar then! :)/Krister

Well, now I have the old aquintance winrun.cpp after having installed the 757 from PMDG. This should be fixable though .... knock on wood.../Krister