|
Post by Al on Aug 6, 2015 18:00:04 GMT -5
So... just updated my Win7 platform after reading the other post here about others doing the same. FSX works fine as described by the other posters but I cannot get FS9 to launch. The problem I get is that I get the Yellow box (User Account Control) stating wanting permission to allow changes to be made by this program. I have compatibility modes set (XP sp3) and System Admin required set in the shortcut. My user account has Admin privileges but when I click yes program never launches. I have run compatibility test and I get FS9 not compatible. I also installed a fresh copy of FS9 on Windows 10 to test to make sure it wasn't in the conversion where my problem lay. The Fresh install doesn't launch either
Has anyone else updated to Windows 10 and running FS9 successfully? If so any advice on what else I can check.
Al
|
|
|
Post by aeroart on Aug 6, 2015 20:09:13 GMT -5
Al,
Have you tried installing FS9 in its own folder on your C: partition? For example, create a new folder called FltSim2004. When the installation location screen appears during the installation process, enter that folder name; eg: C:\FltSim2004 (not sure about whether it's a foward or backward slash).
If you have addons, such as weather programs, FSPanel Studio, etc., you will also have to change to that location in each apps preference setting.
Let us know how that works in Win10. I'll be upgrading, too.
Art
|
|
|
Post by Al on Aug 7, 2015 1:15:06 GMT -5
Hi Art,
Yes I have 3 copies of FS9 and they are all in C:/Microsoft Games/.... so that is not the issue. The problems lies in with FS9.exe. either its not compatible or there is some setting some where that will allow it to be compatible, otherwise I guess I will move back to Win7 because FS9 is my primary simulator, I only use FSX occasionally at this point because of its incompatibility with CC Environment.
|
|
|
Post by Pixel Pilot on Aug 7, 2015 10:13:56 GMT -5
Are you getting to the point that FS9 is looking for the 4th CD to authenticate? I've read on other forums that Win 10 does not understand what FS9 is doing at that point. You apparently need the FS9.exe that contains the no CD crack in order to run FS9 on Win 10. I haven't tested this myself it's just something that I saw.
Ed
|
|
|
Post by Al on Aug 7, 2015 15:14:26 GMT -5
Thanks Ed, That solved the problem Kind of. I loaded in the no cd on my modern version first as it uses the standard FS9.exe version 9.1 it loaded fine as far as I could tell. renamed the nocd.exe to FSCC.exe and replaced the original FSCC.exe from Tom and it now loads but I get the black screen. Since I know its name is different in order to run multiple volumes of FS without conflict but can I just rename the original and replace the FSCC version or is there something different about it. Also, as far as I remember I left the program in Window mode when I had last loaded it in Win7 so hopefully this isn't an issue of it attempting to display in full view mode.
|
|
|
Post by Al on Aug 7, 2015 16:07:33 GMT -5
Forget my last comment, went back and read tips for multi installs of FS9 and now remember how the setup works. Think I have it all solved now, just need to test in the Win10 environment. My first impressions is that it ran fast and smoother in Win7 but I have 30 days to decided whether to move back to Win7.
|
|
|
Post by Pixel Pilot on Aug 7, 2015 16:09:47 GMT -5
Al, You can try the advice given here for the black screen. Change in FS9.cfgHope this helps. Ed
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 8, 2015 3:29:24 GMT -5
I got this from the page give by Pixel Pilot, but here is a link to a very detailed list of suggestions by Microsoft about getting FS9 to work with Windows 10. They seem to think there is no essential incompatibility: support.microsoft.com/en-us/kb/837195Ken
|
|
|
Post by Tom/CalClassic on Aug 8, 2015 9:05:51 GMT -5
Just a heads up - that help article is from 2011 and is not specifically for Windows 10 (in fact it only mentions XP and Vista). But I agree that these are good things to try with any OS.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 8, 2015 10:32:15 GMT -5
My apologies, Tom. I should have looked at it more carefully.
|
|
|
Post by Al on Aug 8, 2015 16:20:39 GMT -5
Got back to testing some more and have all three installs running at this point. So was taking my Golden Wings for a spin and popped up the GPS and boom it crashed. reloaded and tried again at another airport and aircraft it also crashed. Tried it again in Classic and Modern installs, same thing, as soon you load the GPS it crashes. Anyone else seeing this problem and resolved it? Can any of you who have converted cal up the GPS with no problems?
I have also posted on Flightsim forum as well to see if anyone there has this issue.
Al
|
|
|
Post by Tom/CalClassic on Aug 8, 2015 17:37:10 GMT -5
Do you have any addon scenery? If so deactivate it and try again.
|
|
|
Post by Al on Aug 9, 2015 12:53:43 GMT -5
Thanks Tom but I still have the problem either selecting the GPS or selecting maps. So here is what I did based on your suggestion.
First I went back to my clean install updated it with FS9.1 and installed the noCD exe file. Fired it up chose standard default flight and selected GPS and it worked fine as did selecting maps. All three of my other installs crashed with the same selection.
So went to modern install (rarely used) unchecked all add on scenery even the addon Secnery file. Same problem. Replaced the Modules file with that from the clean install, reloaded and same problem still Replaced the Gauges file with that from the clean install, still did not fix problem Replaced The Scenery File with the clean install file, still same problem. Replaced the Scenery.cfg file with that from the clean install, still won't load GPS without crashing. Same with Terrain.cfg file, still crashes
So I am running low on ideas about what's different between my original install and my modern one after replacing most if not all files in the modern with those from the clean install especially that would only affect the GPS and Maps function. Since both installs are sharing the same FS9.cfg since they use the same FS9.exe and language file.
Any more ideas would be greatly appreciated. Meanwhile I will keep at it. I really don't want to tackle this by doing the opposite, load things into a fresh install until it exhibits the same problem as that is a lot of reloads and restarts.
Thanks in advance Al
PS. so much fun being out on the bleeding edge of new releases, somebody had to do it!
|
|
|
Post by Tom/CalClassic on Aug 9, 2015 17:40:40 GMT -5
Did you rename the fs9.exe files in the other installations? If so, perhaps that's the problem?
|
|
|
Post by Al on Aug 10, 2015 12:17:41 GMT -5
Hi Tom, not sure what you mean by renaming the other fs9.ex except to say that the noCD FS9.exe was renamed to FSGW.exe FSCC.exe and FS9.exe in there respective existing volumes. Each loaded correctly but each crashed when gps was selected. The clean volume was also contained the nocd FS9.exe but worked perfectly fine. So the problem to me after everything I tried had to be somewhere in the core DLL or core files that had changed over time in my system. So I took my own advice and made a copy of the clean volume and rebuilt my classic set by copying one thing at a time and testing in this order. Modules, Gauges, effects, Scenery, Textures (this test resulted in a crash on startup, copied original textures into the Texture file and it restarted fine) Addon Scenery directory & Scenery.cfg, and last the Aircraft directory. I now have a complete new classic system and gps and maps works fine. by the way, when I copied I always chose (with the exception of main Texture file) to not replace duplicates which of course kept the clean originals in place in each file.
Doing all this seemed to correct the problem. I guess this also means the issue may have been somewhat unique to my system and why others may not have had any issue once they go past the noCD exe issue and correctly setting up the Short cut launch correctly.
Of course I still have the Full Screen issues as others have reported but can live with that until hopefully a fix comes along.
So far the colors seem to look more life like than I remembered in my Win7 version, but I really don't perceive any FPS improvements so far.
Al
So far
|
|