Sign in to follow this  
crvm

Odd thing with the self-installing C-172 from Real Air

Recommended Posts

every shortcut and file on my desktop ended up in my c-172 folder...never have seen that before...

Share this post


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

That is one of the reasons that I dislike installers. I prefer to transfer the files myself, but for free I can't really complain.Tim13

Share this post


Link to post
Share on other sites

Whenever I try to install the file I get a "Run-Time Error '53' File Not Found" and the installation quits. Can anyone tell me what is happening please. Thanks in advance

Share this post


Link to post
Share on other sites

Using the RealAir C172 installer is about the simplest thing you'll ever do for FS. Just unzip the download to a temporary folder (not in FS2002, as stated in the installer readme) and make sure you leave the directory structure intact. Then click "Install_172.exe". It should put everything in its proper place in your FS2002 directory, and you should be good to go after that. And I promise that this installer is just a shortcut for a few minutes of hand-copy and pasting. It doesn't write anything to the registry, doesn't create an uninstall, and doesn't do anything other than copy to any file already in your FS2002 setup.If you do all of the above and still have problems, please post here and let me know precisely what steps you took that lead to the problem, and I'll make sure it gets straightened out. After all, it's the flying that should be taking up your time!thanks,

Share this post


Link to post
Share on other sites

That happened because you unzipped the installer files onto your desktop. To avoid it, just make a new folder and unzip it there to install. That way you'll only get what you want, and not all the other stuff.thanks,

Share this post


Link to post
Share on other sites

I download the zip to an "Aircraft" folder in the "My Documents" folder. I extract to the same folder and then choose the install icon. It opens the EULA and gives me the option to install to the FS2K2 folder. I click on the install button and then get the error. Hope this is helpfull.

Share this post


Link to post
Share on other sites

So in the source directory where you downloaded the 172, are there other files besides the 172? If so, make a new directory just for this plane and unzip/install them from there. The "53" error would indicate that a file isn't found, so make sure you unzip everything into this folder and don't rename anything.thanks,

Share this post


Link to post
Share on other sites

Ok I created this folder just for this plane and unzipped to it. Still get the same error. What now? I have never seen this one before.

Share this post


Link to post
Share on other sites

Did you look to see if the aircraft was properly installed? It might be an issue with the cleanup afterwards and not the install. If there is no "RealAir 172SP" folder in your FS2002 aircraft folder, then it didn't install. If there is a folder by that name, check to see if all the required files are in it. If so, just fly and forget about it. If not, let me know and I'll try and help out further. With a total of over 2100 downloads to date, this is the first indication of this problem, so I'm inclined to believe it's just a weird glitch, but I'd like to see you get flying properly.thanks,

Share this post


Link to post
Share on other sites

Yep, the folder was there, and inside that folder was everything else in the "My Directory" folder. I deleted that folder from the aircraft folder completely and reinstalled the C-172 from a directory dedicated to it. This in turn gave me the same error as before and then I looked in my FS2K2 aircraft folder and there it was again. When I select the plane in the aircraft select menu it won't come up. I get another error saying the model can't be displayed and then another saying that the aircraft can't be initialzed. ?Your guess is as good as mine.

Share this post


Link to post
Share on other sites

The installer is looking for a basic installation of the 172 - a default aircraft. If you have renamed .air or amended files the installation does not proceed - the `53` errror. I have been using the Ron Freimuth air and cfg files in place of default, with different sound files from Aaron Swindle. As a result of restoring the default aircraft to install this package I have now lost those files. Not clever when what I wanted was to compare the RF flight modelling with the new dynamics. Really Bill, I would have released this without the installer. If simmers are fussy enough to want realistic flight dynamics for their 172, they ought to be technically minded enough to be able to install the files manually, and as they choose. I also hate installers as they leave traces all over the Windows Registry, cause problems with non-standard installations (like here) and require as much if not more technical competence on the part of the user to install the way the installer wants it done, not the way YOU want it done. And in this case I was concentrating on meeting the requirement of the installer so much I lost files I would rather have kept.Anyone have a link for the RF files? ChasW

Share this post


Link to post
Share on other sites

I doubt you will find a link for Ron's files, I can send them along to you if you want, I have two versions: C-172SP and C-172N.

Share this post


Link to post
Share on other sites

Douglas, You're very kind:cward14@blueyonder.co.ukMany, many thanksChasW

Share this post


Link to post
Share on other sites

My original modified Ron Freimuth 172's are STILL very much intact. Flight characteristics are still the same, and the dates of all the files remain the same, without modification. I didn't rename files, but the orignals were changed with the Freimuth air.file.The self-install created a new file specifically for the RealAir 172 without error or problems.L.Adamson

Share this post


Link to post
Share on other sites

Just a suggestion, I never download anything to "My Documents". I've setup two folders "Downloads" nad "Unzipped" - everything I download today (31 March 2003)I will put into a "310303Mon" folder inside my "Downloads" folder and anything that has to be unzipped into a "whatever" folder in a "310303Monday" folder inside my "Unzipped" folder and install from there. I empty one or other or both of these folders, except for the last 3 months or so, from time to time. How long you keep them depends on your disk space. This makes it easy to go back to find that "thingo" you downloaded last week or two months ago and might help with your current problem. Tony

Share this post


Link to post
Share on other sites

I didn't bother running the installer, the new files (air,cfg,wav, and bmps) were unpacked when I extracted the zip and I just did a manual install.Kurt M

Share this post


Link to post
Share on other sites

Yes, that was how I did it in the end, having had the `53` error message, then a `Default aircraft not found Cessna 172` error on bootup after replacing the files with a default version from a clean install of FS2002 I have on another drive.Alternative install method: Unzip the Realair172 zip file to a temporary directory as directed.Open FS2002 folder - aircraft - highlight the C172 and `copy` to the same aircraft folder, creating a `copy of C172` folder. Now cut and paste all the files from the Real Air temp directory, overwriting when prompted. Finally, delete the installer .exe from the `Copy of C172` folder and rename the folder Real Air C172SP.Done.ChasW

Share this post


Link to post
Share on other sites

Chas,Okay, I can see now that a few more words of warning should have been put into the installer readme for those who had tweaked their default 172 installation. The only -- and I repeat ONLY -- thing that should have given this installer a problem is if you'd renamed the default 172's folder. Let me set the record straight on what this installer does:1. Looks for your default 172 folder and copies it to a new directory called "RealAir C172SP".2. Copies the files and folders for the RealAir version from the place you've unzipped them, overwriting any file that we're replacing such as the textures, sounds and aircraft.cfg files.3. Deletes it's own installer (install_172.exe) from the new RealAir 172SP folder. After all, you don't need this once you're done and it wouldn't work to run it from this new location anyway.I'd like to point out that nowhere in this process is anything written to the registry. Your system is not trashed up in any way by any of the above activities. Your default 172 is not touched. And if you were using other sounds for the 172, you can easily restore them by just copying the sound folder from your default 172 again.In fact, if you didn't want to use the installer and were technically adept and paying attention, you would see that all the files are resident in the zip to do a manual install without using the exe at all. If in the process of installing, you overwrote your default 172 with a rolled-back version, that's hardly the fault of the installer. I think some of you may be making this too difficult on yourselves.thanks,

Share this post


Link to post
Share on other sites

Hi Bill,This is not the right thread to get into the pro's and con's of auto-installers again :-) (allthough I have MY preference :-) ).Being a (freeware) developer myself, I just hope that every publisher of an FS addon package would follow your approach: make it possible for the user (depending on his capabilities/FS installation) to decide whether to install it manually or use the auto-installer.The only thing you could have done better IMO (and PLEASE read this as constructive comment) is if you had written the few lines of auto-installer explanation above in a Readme file. Which would have avoided the problem and the discussion :-).Best regards, RobPS: Great plane by the way !!

Share this post


Link to post
Share on other sites

Hi Bob,Yes, I quite agree. Fortunately, the installer doesn't seem to have presented a problem to very many, but it never hurts to have a little explanation. You can bet I'll be keeping it in mind the next time I release any bit of software! All this discussion has given me a couple of ideas for improvements to the installer, so it should be pretty tight next time.thanks,

Share this post


Link to post
Share on other sites

Bill, I unzipped the RealAir172 to C:...My DocumentsTemp Files as I do with all my downloads. I see a new folder created `Realair172sp`. I open that folder and double click on the .exe contained inside, after reading the readme. I get the `53` error message, then a ` default aircraft not found, reinstall flight simulator` message when attempting to open FS2002.Note: I have NEVER renamed the C172 folder, and the only difference from default was the replacement flight dynamics by Ron Freimuth (creating a different named air file - which is where the problem is I suspect) and an alternative sound file folder which I use for backing up the default aircraft sounds after replacing them with Aaron Swindles excellent replacements. These too, were lost in trying to install the Real Air modifications and that too, is simply not acceptable (although I do have those saved on CD). I am no greenhorn with FS installation, but I do not think it appropriate for an installer to only recognise a default, standard installation before proceeding. At the very least there should be manual instructions as an alternative. And if that isn't the correct procedure, then you need to re-write the installer, or abandon it altogether. I simply do not accept that I am in error. If I click on a self-installer, I shold expect that it will do what is supposed to do, and not harm my computer or its files. I only thank my foresight in having a second installation of FS2002 which enabled me to replace the damaged C172 folder saving me from a complete reinstallation of the product. By the way, the manual installation method I outlined above takes less than two minutes, including deleting the installer. exe from the hard drive. What's so difficult about that? Especially as it doens't harm my installation.ChasW

Share this post


Link to post
Share on other sites

After reading your message, I can confirm that one of the problems (as you correctly supposed) is that renamed air file. I assume you deleted or moved the default 172 air file from your original 172 installation -- yes? The installer wants to remove the default air file from the new RealAir 172 folder after the installation of the new one, and when it can't find a file it recognizes as the one to delete, it throws the error. One simple fix for this in future versions is just to not remove anything after install. I don't think it would have any adverse effect on the aircraft to have another air file in the folder so long as the correct one is called in the aircraft.cfg file. I'll definitely consider doing it that way in the next one.Unfortunately, I'm not at home right now (gotta work for a living at least part of the day ;-)) but when I get home tonight I'll look through the installer code and see where the problem might be with it not finding your default c172 folder. That's one part that should never give an error, and in our testing it never did. I assume the installer had the correct path to your root FS2002 in the path select box when the installer launched, yes? If so, and if the folder wasn't renamed, then it should have been, as we say, duck soup to find it.Regarding the Aaron Swindle sound files, I'm still a little foggy on what you are saying took place, so bear with me. Are you saying that the installer deleted or caused a problem with the sounds in the default 172 folder, or that the new RealAir 172 didn't have the right sounds? The problem is that Rob made a new sound.cfg file and added some tire/wind sounds, so the default sound.cfg gets overwritten in the new RealAir 172 folder with his files. There should be no reason why you couldn't just replace the whole RealAir sound folder with the one you've been using for your default 172 after the install is over.I'm a long, long way from considering abandoning this installer, as I feel that it's a huge time saver for the vast majority of simmers. There are a few issues to be resolved in order to make it bulletproof, but then that's the hardest part of FS development. Getting anything to run on everyone's computer is almost always an elusive goal. I appreciate the feedback you've already given, and I've provided a method in an earlier post in this thread for just installing the whole thing manually if you'd like to bow out of the conversation now and go flying. If you are intersted in sticking around and seeing this through, I'd be happy to continue tracking the installer problems down as soon as I can get to my FS computer. I can think of a couple of tweaks I could do to make it work more smoothly, and if you're interested I'll send you a new installer along with a list of changes I've made when I get done tweaking it. It shouldn't take more than an hour or so tonight.thanks,

Share this post


Link to post
Share on other sites

The only thing wrong with the installer programming is that it assumes that you have a completely standard C172 installation. If you don't have a standard installation then you will need to install by hand.For example, I have a non-standard C172 installation in that the name of the main folder is different (therefore the installer can't find my C172) and the sounds inside my sound folder are different to the standard C172 and my panel is not standard.If people have altered their standard C172 in any way, they need to be aware of this.Barry

Share this post


Link to post
Share on other sites

Bill,Thanks for replying and I hope this helps others from making a hash of their FS install - it will then save the copious e-mails that will inevitably turn up on the Real Air Sim doorstep.>I assume you deleted or moved the default 172 air file from your original 172 installation -- yes? The installer wants to remove the default air file from the new RealAir 172 folder after the installation of the new one, and when it can't find a file it recognizes as the one to delete, it throws the error. One simple fix for this in future versions is just to not remove anything after install.I don't think it would have any adverse effect on the aircraft to have another air file in the folder so long as the correct one is called in the aircraft.cfg file. I'll definitely consider doing it that way in the next one.Regarding the Aaron Swindle sound files, I'm still a little foggy on what you are saying took place, so bear with me. Are you saying that the installer deleted or caused a problem with the sounds in the default 172 folder, or that the new RealAir 172 didn't have the right sounds? I'm a long, long way from considering abandoning this installer, as I feel that it's a huge time saver for the vast majority of simmers.There are a few issues to be resolved in order to make it bulletproof, but then that's the hardest part of FS development. Getting anything to run on everyone's computer is almost always an elusive goal.

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