Sign in to follow this  
Guest danc444

757 Load Editor

Recommended Posts

After manually installing the 757 per John's instructions everything worked except the load manager. Something about not being able to find the installation path to fs9. I searched for a solution to this and found the john's registry fix, which I tried. Now I get the following error message: 757 load editor.exe has stopped working.As I'm not experienced with rwriting to the registry, I wonder if I did something wrong.This is the load_edit_fix.reg file I ran:Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator][HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.0]"EXE Path"="C:\\Program Files(x86)\\Microsoft Games\\Flight Simulator 9" Please help.Thanks.

Share this post


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

After manually installing the 757 per John's instructions everything worked except the load manager. Something about not being able to find the installation path to fs9. I searched for a solution to this and found the john's registry fix, which I tried. Now I get the following error message: 757 load editor.exe has stopped working.As I'm not experienced with rwriting to the registry, I wonder if I did something wrong.This is the load_edit_fix.reg file I ran:Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator][HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.0]"EXE Path"="C:\\Program Files(x86)\\Microsoft Games\\Flight Simulator 9" Please help.Thanks.
Please sign your name - its - nice to konw who we are talking to.There are two diferent reg fixes for two separate issues with 777/757 and you may have mixed things up. For your "installation path" error, we recommended using the Flight One registry repair tool. Go to the Flight 1 software web site to the Free File Library and download and run the FSX/FS9 Registry Repair Tool. That should drop in the correct installation path.Any problems,do post back here.RegardsJohn

Share this post


Link to post
Share on other sites

My name is Dan and thanks again.Did I screw anything up by running the file I did?Meantime, I'll try the Flight1 solution.

Please sign your name - its - nice to konw who we are talking to.There are two diferent reg fixes for two separate issues with 777/757 and you may have mixed things up. For your "installation path" error, we recommended using the Flight One registry repair tool. Go to the Flight 1 software web site to the Free File Library and download and run the FSX/FS9 Registry Repair Tool. That should drop in the correct installation path.Any problems,do post back here.RegardsJohn

Share this post


Link to post
Share on other sites

Ok, I ran the flight1 fix and still get the following message: "757 load editor.exe has stopped working""A probem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."So I took another copy of the load editor. exe from my other machine (that is working fine) and copied it to the pss folder and I still get the same message. So it doesn't appear that file corruption is the problem.Any ideas?

Please sign your name - its - nice to konw who we are talking to.There are two diferent reg fixes for two separate issues with 777/757 and you may have mixed things up. For your "installation path" error, we recommended using the Flight One registry repair tool. Go to the Flight 1 software web site to the Free File Library and download and run the FSX/FS9 Registry Repair Tool. That should drop in the correct installation path.Any problems,do post back here.RegardsJohn

Share this post


Link to post
Share on other sites
Ok, I ran the flight1 fix and still get the following message: "757 load editor.exe has stopped working""A probem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."So I took another copy of the load editor. exe from my other machine (that is working fine) and copied it to the pss folder and I still get the same message. So it doesn't appear that file corruption is the problem.Any ideas?
Dan, I have never seen the message"757 load editor.exe has stopped working" before suspect its something between the LE exe file and the PSS files. Referring to your previous post, what file did you "run"? Also, did you make a registry back up before you ran the file {just in case}? Let me know and I will try and work out what happened.John

Share this post


Link to post
Share on other sites

This is the load_edit_fix.reg file I ran:Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator][HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.0]"EXE Path"="C:\\Program Files(x86)\\Microsoft Games\\Flight Simulator 9" And sadly, I didn,t make I didn't make a registry backup. Not sure how, frankly.

Share this post


Link to post
Share on other sites
This is the load_edit_fix.reg file I ran:Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator][HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.0]"EXE Path"="C:\\Program Files(x86)\\Microsoft Games\\Flight Simulator 9" And sadly, I didn,t make I didn't make a registry backup. Not sure how, frankly.

Share this post


Link to post
Share on other sites

Dan,Thanks - that programme is our old friend REGEDIT for manually changing the registry (and for backing up - go FILE - EXPORT).Firstly, I have assumed that you are on Win Xp. If not, ignore everything I say below and we will start again if you are Vista.Some thoughts if you are XP:1. Was the entry you modified {at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.0} the only change that you made?2. If so, look at the value that you quote:"EXE Path"="C:\\Program Files(x86)\\Microsoft Games\\Flight Simulator 9" Check that your C:\programme files folder is actually named "Programme files (x86)? Also that the main FS9 folderis within this folder and is named "Flight Simulator 9"?Also, why the double backslash (\\) in the value. I do not have that in mine and have never seen it before. That said, I have changed mine and it made no difference!Finally, have you considered a system restore to before you changed the registry but do a quick back up first.John

Share this post


Link to post
Share on other sites

Fortunatley, Santa brought me a new powerful machine. Unfortunately, it was riddled with Vista instead of XP. I don't think I'd be having any of these issues with XP.As far as the double backslash, they were the result of my trying to follow your instructions to a StevenP in a trhread that began on July 17, 2008 entitles "757 load manager problem". The specific reply from you was posted on July 23rd.With respect to your other observations, I'll wait and see if they still apply now that you know I'm running Vista 64.Thanks,Dan

Dan,Thanks - that programme is our old friend REGEDIT for manually changing the registry (and for backing up - go FILE - EXPORT).Firstly, I have assumed that you are on Win Xp. If not, ignore everything I say below and we will start again if you are Vista.Some thoughts if you are XP:1. Was the entry you modified {at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.0} the only change that you made?2. If so, look at the value that you quote:"EXE Path"="C:\\Program Files(x86)\\Microsoft Games\\Flight Simulator 9" Check that your C:\programme files folder is actually named "Programme files (x86)? Also that the main FS9 folderis within this folder and is named "Flight Simulator 9"?Also, why the double backslash (\\) in the value. I do not have that in mine and have never seen it before. That said, I have changed mine and it made no difference!Finally, have you considered a system restore to before you changed the registry but do a quick back up first.John

Share this post


Link to post
Share on other sites
Fortunatley, Santa brought me a new powerful machine. Unfortunately, it was riddled with Vista instead of XP. I don't think I'd be having any of these issues with XP.As far as the double backslash, they were the result of my trying to follow your instructions to a StevenP in a trhread that began on July 17, 2008 entitles "757 load manager problem". The specific reply from you was posted on July 23rd.With respect to your other observations, I'll wait and see if they still apply now that you know I'm running Vista 64.Thanks,Dan
Dan,Ah ......... Sorry. I f you look carefully at that thread, you will see that I was merely copying the solution from another post I have never had Vista, let alone the 64 bit version.I guess that you diidn't first use the the TweakFS tool as suggested in para 1 of the post?I wonder if you can get back to the original state as per XP - is there system rstore facility in Vista?John

Share this post


Link to post
Share on other sites
Dan,Ah ......... Sorry. I f you look carefully at that thread, you will see that I was merely copying the solution from another post I have never had Vista, let alone the 64 bit version.I guess that you diidn't first use the the TweakFS tool as suggested in para 1 of the post?I wonder if you can get back to the original state as per XP - is there system rstore facility in Vista?John
Dan,Also remembered this:You get this error if one of the 757 aircraft folders is misnamed or missing. Check that you have all 6 757 aircraft folders and that they correctly named. John

Share this post


Link to post
Share on other sites

Yeah there is a system restore feature in Vista 64 I ran it and seem to be back to the beginning. So let me ask you this question: Under the assumption the load manger can't find the path again after I install the 757, should I run the TweakFS or the Flight1 version? And where do I find the Tweak, in these libraries?ThanksDan

Share this post


Link to post
Share on other sites
Yeah there is a system restore feature in Vista 64 I ran it and seem to be back to the beginning. So let me ask you this question: Under the assumption the load manger can't find the path again after I install the 757, should I run the TweakFS or the Flight1 version? And where do I find the Tweak, in these libraries?ThanksDan
Dan,Good - we're on the way. Sounds as though you are right back to the begining and have to re-install the 757 - don't forget the file voronoi.dat and the PSS fonts.The TweakFS and Flight1 utilities should do the same thing but you can get the former from here:http://www.tweakfs.com/store/free_tools.phpas that has been shown to work with Vista I should give it a go.Good LuckJohn

Share this post


Link to post
Share on other sites

John,I followed the Tweak link and saw it was for tweakfs for fsx. Since I run both fsx and fs9 should I look for an fs9 version as well and install both?Thanks.Dan

Share this post


Link to post
Share on other sites
John,I followed the Tweak link and saw it was for tweakfs for fsx. Since I run both fsx and fs9 should I look for an fs9 version as well and install both?Thanks.Dan
Just scroll down the page to the FS9 utilities and download that one!John

Share this post


Link to post
Share on other sites

OK. Here's where we are. I reinstalled the 757 and all works perfectly except, of course, the load editor. It can't find the FS9 installation path, still. I ran first the Tweak, then the Flight1 utility and no luck. In fact the Tweak utility does tell me that the path to fs9 was found under HKEY local machine, but with no furthur breakdown of its location.Those are the facts, now I'll go out on a limb. I believe that the load editor is looking for the path under HKEY local machine\Software\Microsoft\MicrosoftGames\FS9, because that's where it used to be under XP. Using regedit I find this path does not exist. In fact, there's no HKEY local machine\Software\Microsoft\MicrosoftGames at all.The path lies instead in HKEY local machine\Software\Wow6432Node\Microsoft\MicrosoftGames\FS9.My guess is that this is why load editor can't find the path.Also, this seems like the issue you were trying to address in the July thread I referred to earlier.Let me know if you have any thoughts. Thanks.Dan

Just scroll down the page to the FS9 utilities and download that one!John

Share this post


Link to post
Share on other sites
OK. Here's where we are. I reinstalled the 757 and all works perfectly except, of course, the load editor. It can't find the FS9 installation path, still. I ran first the Tweak, then the Flight1 utility and no luck. In fact the Tweak utility does tell me that the path to fs9 was found under HKEY local machine, but with no furthur breakdown of its location.Those are the facts, now I'll go out on a limb. I believe that the load editor is looking for the path under HKEY local machine\Software\Microsoft\MicrosoftGames\FS9, because that's where it used to be under XP. Using regedit I find this path does not exist. In fact, there's no HKEY local machine\Software\Microsoft\MicrosoftGames at all.The path lies instead in HKEY local machine\Software\Wow6432Node\Microsoft\MicrosoftGames\FS9.My guess is that this is why load editor can't find the path.Also, this seems like the issue you were trying to address in the July thread I referred to earlier.Let me know if you have any thoughts. Thanks.Dan
I think that we might be on the wrong track; We have to try a process of elimination - as above, just confirm that you have given the .exe file Vista administrator rights {see the PMDG ref I gave}.JohnJohn

Share this post


Link to post
Share on other sites

Yes I did. Even turned UAC off.

I think that we might be on the wrong track; We have to try a process of elimination - as above, just confirm that you have given the .exe file Vista administrator rights {see the PMDG ref I gave}.JohnJohn

Share this post


Link to post
Share on other sites

Dan,Does the 757 fuel planner work for you?What version of Net Framework do you have installed?John

Share this post


Link to post
Share on other sites

Further - can you set the load edit .exe file to run in a compatibility mode for XP??I also have another lead I am investigating at the moment.John

Share this post


Link to post
Share on other sites

The fuel planned does work. I have both 1.1 and 3.5 installed.

Share this post


Link to post
Share on other sites

Dan,"Those are the facts, now I'll go out on a limb. I believe that the load editor is looking for the path under HKEY local machine\Software\Microsoft\MicrosoftGames\FS9, because that's where it used to be under XP. Using regedit I find this path does not exist. In fact, there's no HKEY local machine\Software\Microsoft\MicrosoftGames at all.The path lies instead in HKEY local machine\Software\Wow6432Node\Microsoft\MicrosoftGames\FS9.My guess is that this is why load editor can't find the path."Looking further into the PMDG forums, I found a thread in which a Vista user confirmed that he had to manually insert the relevant EXE entry into this branch:HKey_Local_Machine\Software\Microsoft\Microsoft Games\Flight Simulator\9.0because the tweakFS/Flight1 utilities had not worked. He did not say whether he initially had the basic HKEY local machine\software\ etc branch or not. Notice no mention of the Wow6432Node entry.However, checking a Vista help site confirmed that HKEY_LOCAL_MACHINE should exist in a Vista installation.Therefore, manually inserting a:\Software\Microsoft\MicrosoftGames\FS9entry without the Wow6432node folder might be the answer.It is easy to use REGEDIT to insert this entry but I must give a HEALTH WARNING. I do not have Vista and have gleaned the above from other forums and web sites so I cannot confirm that this works or how it might affect your individual machine. If you try it, ensure you have backed up the registry and have a restore point set.Post if you have any questionsJohn

Share this post


Link to post
Share on other sites

I agree with your assessment and advice. As I stated earlier, I tried tat once, and it did seem to solve the path problem, but the it said the load editor was not working and needs to be shut down.I think I made a mistake in editing the registry and I wonder if you or any of your sources can take me through it.Thanks.

Dan,"Those are the facts, now I'll go out on a limb. I believe that the load editor is looking for the path under HKEY local machine\Software\Microsoft\MicrosoftGames\FS9, because that's where it used to be under XP. Using regedit I find this path does not exist. In fact, there's no HKEY local machine\Software\Microsoft\MicrosoftGames at all.The path lies instead in HKEY local machine\Software\Wow6432Node\Microsoft\MicrosoftGames\FS9.My guess is that this is why load editor can't find the path."Looking further into the PMDG forums, I found a thread in which a Vista user confirmed that he had to manually insert the relevant EXE entry into this branch:HKey_Local_Machine\Software\Microsoft\Microsoft Games\Flight Simulator\9.0because the tweakFS/Flight1 utilities had not worked. He did not say whether he initially had the basic HKEY local machine\software\ etc branch or not. Notice no mention of the Wow6432Node entry.However, checking a Vista help site confirmed that HKEY_LOCAL_MACHINE should exist in a Vista installation.Therefore, manually inserting a:\Software\Microsoft\MicrosoftGames\FS9entry without the Wow6432node folder might be the answer.It is easy to use REGEDIT to insert this entry but I must give a HEALTH WARNING. I do not have Vista and have gleaned the above from other forums and web sites so I cannot confirm that this works or how it might affect your individual machine. If you try it, ensure you have backed up the registry and have a restore point set.Post if you have any questionsJohn

Share this post


Link to post
Share on other sites
I agree with your assessment and advice. As I stated earlier, I tried tat once, and it did seem to solve the path problem, but the it said the load editor was not working and needs to be shut down.I think I made a mistake in editing the registry and I wonder if you or any of your sources can take me through it.Thanks.
Dan,I don't think you have tried what I suggested. But I am very happy tp take you through it step by step. Two questions:1. Where are you - I am in UK on ZULU time and we need to coordinate when we can be on line together?2. Do you have access to another computer so that we can chat whilst you try something?John

Share this post


Link to post
Share on other sites
Sign in to follow this