Sign in to follow this  
Guest

Boeing 307 EXE.

Recommended Posts

I usally dont like EXE installers so I usually run them to a temp folder then manually install the files,I ran into something odd the other day after I ran the boeing 307 EXE to a temp folder.Everything worked fine till I fired up the reality xp gps, it could not locate the data files(GPSDATA.BIN)in the fs2002 root directory, A search through the registry revealed that after I ran the boeing 307 to a temp folder it change the path in -HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft GamesFlightSimulator8.0 and the key in there "EXE PATH" The EXE path(string) changed from c;program filesmicrosoft gamesfs2002 to the temp folder location I ran the 307 EXE to.I have never seen an auto installer do this, so its something to be aware of, I now export a copy of my registry prior to running any EXE file, for me anyway I am always reluctant to run any EXE unless I know exactly what its going to do, it would be nice to have developers give you an option of using an EXE or a zip file, or at least explain in detail which files its going to write to ,especially the registry. For anyone who has run the boeing 307 EXE to a temp directory you may want to run regedit and check your EXE path.

Share this post


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

This happens with a number of self-installers, or at least those I have used. That's one reason why I'm not keen on them; particularly, if the developer does not tell you exactly in a INSTALL file where everything is going to go.Other reasons: overwriting of gauges with older versions (common) older versions of modules dlls, automatic updating of SCENERY.CFG files (very dangerous, when like me you're at the limit!) overwriting of critical bgls and texture files in main and SCENEDB folders .... need I go on. What's more, my START/PROGRAM FILES list is now unusable. It runs off the screen to somewhere near Timbuktoo.No, give us a good old zip everytime. With my own uploads, I simply suggest unzipping straight to FS2002 for those who wish to do it that way (having checked my file integrity for about a week first) or doing it manually if you prefer. Which I, for one, do.Mark "Dark Moment" Beaumonthttp://www.swiremariners.com/newlogo.jpg

Share this post


Link to post
Share on other sites

So basically what you are saying is that you did not follow the instructions and chose to do things your own way, then hit on a problem. Instructions are given to users so as these things do not happen and had you followed the instructions properly you would not have needed to make a registry change. I completely fail to see the purpose of your post other than to point out to others that if you choose not to do things as per the instructions you are on your own and any problems encountered are therefore entirely of your own making."....it would be nice to have developers give you an option of using an EXE or a zip file, or at least explain in detail which files its going to write to ,especially the registry....."Is it not enough that someone has gone to the trouble of creating an aircraft package for you for free? Most people would also be thankful that they also went to the trouble of creating an installer for you too. You can obviously take the time to post on avsim's forum so I would suggest the next time you require the above information or want to put suggestion to a developer that you take the time to email that developer directly.

Share this post


Link to post
Share on other sites

Sigh! obviouslyHere it is again for you in plain english If you chose not t

Share this post


Link to post
Share on other sites

> It runs off >the screen to somewhere near Timbuktoo. This is one of the main reasons I also prefer to run an exe file to a temp folder first before manually installing the files. I have hundreds of addon aircraft - so why would I want a small number to be showing up in my start menu ?? :) But I have noticed one curious/possibly alarming thing with some of these EXE files -- When I run them to a temp folder , I examine the content of the temp folder and copy everything to where it should go in the FS2002 aircraft folder and generally everything works fine. Now here is the rub -- I then go to the start menu file and click the "uninstall" item -- and guess what , some of these uninstall programmes not only uninstall the content of the temp folder but actually also delete the actual temp folder itself!!! So I can't help but wonder what would happen if you did install the exe file as per the instructions straight into the FS2002 folder , what would happen to the FS2002 folder if you , at some later point, unistalled said aircraft???Barry

Share this post


Link to post
Share on other sites

Ninguna marca,I apesadumbrada no hablo una palabra del enlish llano

Share this post


Link to post
Share on other sites

Marky, I must respectfully completely disagree with you.While you are correct in stating that had the installation procedure been followed to the letter there would have been no issues, the procedure undertaken by the installer is completely flawed and should not have been released in it's current state.I also develop freeware add-ons, and fully and completely appreciate the effort that has been put into the B307 package. I think it is a FANTASTIC freeware release, and worthy of merit and credit. This is not a post attacking the value of the add-on... only of it's installation procedure.The reason I state that the installer should not have been released is because it makes a completely UNNECESSARY change to your system registry. There is no valid REASON for the installer to modify any part of the registry that is associated with FS2002.The freeware addon does not depend on the FS2002 path registry key even being there to operate... thus, it's modification by the installer is purely an installer issue, not the add-on itself.At most, the installer could check the registry for the path, but under no circumstances modify it. I too installed it to a TEMP folder (like I do all my add-ons), and checked my registry as soon as I had manually transferred the add-on and unistalled the TEMP install.Sure enough, the path which used to point to my FS2002 installation now pointed to my TEMP folder. This is inexcusable. That path is used by other add-ons, and to modify it, without necessity, and without warning whatsoever (neither during the install procedure, nor the documentation), should not be standard operating procedure for any freeware (or payware) add-on that does not depend on registry values.Those are the facts, and they are undisputed.

Share this post


Link to post
Share on other sites

Hi Mark,I can't recall currently... what's the limit on scenery files in scenery.cfg? I don't think I've gotten near it before, so I'm also wondering... what happens when you exceed that limit? These aren't idle questions, as I'm working on creating some installers right now, and I'd like to make sure they're as bulletproof as possible. Before anyone jumps on me, what I'm trying to do is make an installer that is super easy to use, but provides the power user with a full accounting of where files are being placed, NEVER writes anything to the registry, and can be configured NOT to automatically install easily as well. I want to get it right! I understand that some people just want to unzip and install the scenery/aircraft themselves, and I'm not looking to block that. But you'd be surprised at the positive feedback from some less experienced users that I've gotten from previous installers.thanks,

Share this post


Link to post
Share on other sites

Lets see if we can put this to rest. The installer was made with a program called Install Maker.It uses a registry key to determine where to install The aircraft, and should not modify the Registry. I have found after reading this post that for some reason it does change the location in the registry entry. I have e-mailed the maker of the Program to determine why this has happened. It obviously is a mistake in the installer. However to the question how could this be released in this state... When I test installed, and unistalled the aircraft several times to make sure that not only did it work, but that it Copied, and erased only files within itself. I never had a problem. The reason I had no problems is that I never tried to install it to a diffferent folder other than my Fs2002 folder. It is not possible for any developer to test every single aspect of their product, resulting in the occasional error. I am sorry if this has caused anyone problems, but as stated above if installed correctly there whould be no problems. If the issue can be resolved it will be. ThanksAl

Share this post


Link to post
Share on other sites

>What's more, my START/PROGRAM FILES list is now unusable. It runs off the screen to somewhere near Timbuktoo.Sounds like it's time for some housekeeping!Mike :-wave

Share this post


Link to post
Share on other sites

I installed the B307 Stratoliner this afternoon (UK) using the exe file and no problems were encountered. The only change I had to make during the install process was to change the drive destination (FS2k2 is on my D drive). Like Al says, providing you accept the default installation path to YOUR FS2002 folder all should be well.I checked my registry and can confirm that no changes have been made. Perhaps we need to have a little more faith with installer executables. I very much doubt whether a 3rd Party author would risk the wrath of the community without thoroughly testing an archived executable installer prior to uploading to a file library. I have NEVER encountered a problem of this nature.Having said all that, like many I do prefer to unzip archives to a temp folder so that I can control the installation thereafter. I've encountered many zip files that leave files in subfolders so you may end up with, for example, missing gauges simply because the extraction has left them in a subfolder called gauges under the main gauges folder.Mike :-wave

Share this post


Link to post
Share on other sites

<<<>>The initial point may have got lost in the chain of posts, Mike. Al's installer will not change the registry if you install to the location of your FS2002 as he suggests. It will only do so (and, as you'll read, he's aware of the issue) if people change the path to go to a temp folder. This is the same, if I recall, with ISD's Italy scenery, RS' Marchetti (I may be wrong, can't remember) and several others. <<<>>No developer WANTS to do this, of course. But my points above stand: that unless you know EXACTLY what is going into your system, you run a risk. I'd say on average that about 50% of the self-installers I have bypassed would have overwritten newer gauges on my system. People forget that not everyone has the same rig as their own, particularly when one has made personal modifications to panels, gauges and other files, for example.Mark "Dark Moment" Beaumonthttp://www.swiremariners.com/newlogo.jpg

Share this post


Link to post
Share on other sites

>50% of the self-installers I have bypassed would have overwritten newer gaugesYou may be right but so far I haven't encountered any problems as a consequence. Maybe I've just been lucky!While cutting and pasting unzipped files, like you, I prefer to monitor the transfer of each file. Often when I'm asked whether I wish to overwrite an existing/'newer' file I note that the difference is only with the date stamp and not the size of the file. Generally my response in this situation would be 'No'. On the other hand if the 'new' file has a more recent date stamp I will allow the overwrite, but I often wonder whether this is really necessary since both files are likely to be identical.Mike

Share this post


Link to post
Share on other sites

Al, thanks for chiming in on this thread.As I already stated in my previous post, your addon is a truly superb effort, and I am enjoying it immensely.This thread has served its intended purpose. To make others (and yourself) aware of a potential problem that COULD arise from the use of the installer (if not used exactly as stated in your directions).Like you have stated, there was no possible way you could have foreseen the trouble as you did not test the install procedure to a TEMP folder. And to be honest, I would not have tested that either if it were my release. I would have done exactly what you did, and that is to simply check that my install directions and the installer worked as I expected it to, and to expect the installer to be free of any bugs or complications.I very much hope that the programmer(s) of the installer maker fix this, IMHO, very serious bug in their product. The ball is definately in their court.Again Al, thanks for your input, and your fabulous add-on! (It REALLY is good, I mean... REALLY!) :-)

Share this post


Link to post
Share on other sites

With all the recent bashing of auto-installers, I'd have to say there are 2 options available that "should" please everybody.1)Make 2 seperate downloads available. A .exe auto-installer version for the novices that don't like following long lists of instructions, and a .zip version for those who prefer the manual method.-or-2)Code the auto-installer such that we get a choice: a) Install the aircraft/scenery/whatever directly to FS (the novice method)or :( Install a .zip file to a specified temporary directory, which has the instructions for manual installation.Obviously, option 2 would pretty much double the download size, so the only real method of satisfying everyone is to make 2 download versions available, an auto-installer for novices and .zip for everyone else.

Share this post


Link to post
Share on other sites

Al ,I am by no means knocking the 307 itself ,its beautiful to say the least, I just have an issue with some installers, I have seen them do some bizzare things. As a side note , I work for the big B here at KBFI and , have been checking in on the restoration process on the 307 , and its comming along fine, alot of my x co-workers are on the restore team.

Share this post


Link to post
Share on other sites

>Obviously, option 2 would pretty much double the download >size, so the only real method of satisfying everyone is to >make 2 download versions available, an auto-installer for >novices and .zip for everyone else. I don't see why it would double the size. Just some extra options in your installer.For our scenery we have also made an installer. For some people a manual install is just to difficult and that means a lot of complains, although I know some people (including myself) prefer a manual install.But our installer is made in such a way that it is an exe, when you run it normal it works as an auto installer. But when you open the exe with WinZip you can extract it like any other zip file (and no, it's not a autoextracting zip file).This way you can do the good old manual install if you want to (or if the installer fails to run on your PC) and for the others users there is the full auto install.Arno


Member Netherlands 2000 Scenery Team[link:home.wanadoo.nl/arno.gerretsen]Arno's FlightSim World for scenery design hints, tips and other tricks...

Share this post


Link to post
Share on other sites

This post rang a bell. Since the last few days, I suddenly had AFCAD and AFInstaller ask me the FS2002 path every time I launch them and I couldn't understand why it suddenly did so.Now I know : I installed the B307 in a temp folder.Like many other people here, I never install anything directly to FS2002. It's way too dangerous when you have multiple addons. You can be pretty sure that installing one will kill or corrupt another one. Also, I don't want tens of useless entries in my add/remove software list, nor in my startup menu.Usually, I install to a temp folder, then duplicate the folder, then uninstall automatically, then move the files manually from the duplicated folder to where they belong in FS2002.Some installer ask for FS2002 path and refuse to run if they don't find FS2002.exe (or some other file like scenery.cfg...). For these, I rename my original FS2002 folder and create a new empty FS2002. Sometimes, you have to run the installer, select the FS2002 original folder, then switch to an explorer to rename to xFS2002 and create a new FS2002, then switch back to installer and continue.Eric.

Share this post


Link to post
Share on other sites

Eric,This rang an alarm bell with me too as I have been frantically searching for reasons why my AI Traffic Mover aircraft editor and Active Camera mouse pan control stopped working. Now it seems to coincide with the install of the Boeing 307. I'm desperate to find out how to fix this problem, if you could help tell me what to do I'd really appreciate it. Thank you, Tom

Share this post


Link to post
Share on other sites

To restore the registry entry, you can do either of the following:1) if you know how to use Regedit, simply run it and modify the entry specified in the first post to make it point to your FS2002 folder2) if you don't know how to use Regedit, you could simply reinstall B307, but this time do it in the real FS2002 folder. There is no reason it won't overwrite the entry with the right value. In order to not really install into FS2002, rename your FS2002 folder and create a new empty FS2002 folder.3) as a last resort, you can rename your FS2002 folder, reinstall FS2002, then put the newly installed FS2002 to the trash and set back the original name to your FS2002 folder.Eric.PS : or, someone here can post a .reg file that will restore the entry to the right value (I'm sorry, I can't do that right now).

Share this post


Link to post
Share on other sites

EEmer, do this- click on start click on run, type regedit in the run box hit enter, the reg editor will open. Now under the file tree open this file HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft GamesFlightSimulator8.0 and the key in there ("EXE PATH") Open up the exe path and chose to modify. now type the correct path to your fs2002 install ,the default is something like this C:program filesmicrosoft gamesfs2002, but before you do this in case you make a mistake, export the the registry to a temp location on your hard drive so you can restore it in the event something goes wrong.

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