hjwalter

Hi guys,

First of all, the basic problem, which I have had for about a year but only recently really began to take notice of it because of seemingly lower frame rates.

Double clicking on my FS9 shortcut icon or on the FS9.exe itself, only produces the Win7 colored circle for a few seconds and then stops. No splash screeen, no nothing.

Only after double clicking a second time does my FS9 seem to start up normally but then ........ please read on ...... and I thank you in advance for the trouble taken.

Processor: i7-3930K @ 3.2 - 3.8 GHz

Memory: 32 Gb. Yes, this is far too much because only a relatively small poprtion of it seems to actually be used.

Windows7 Professional 64 bit, running on two SSDs in RAID zero setup. Original version, now six years old and taken from the originally purchased DVD. There have never been any Win7 updates because my machine has never been connected to the internet.

Program files + FS9 (129 Gb) on a single SSD of 1 Tb.

I've been running FS9 + update + no CD "crack" with great pleasure more or less ever since it first became available and even better on this latest machine.

After the first double click my Task Manager shows, amongst others, two new processes: "fs9.exe *32" with "00" in the CPU colom and "rundll32.exe *32" with "08" in the CPU colom. Nothing under the Applications tab. However, under the "Performance" tab and "Resource Monitor" button, at least one of my other CPU cores shows a constant usage of about 90%, ranging from between zero and 100% ??? Other cores are spiking as well but on average, far less.

After the second double click on my FS9 shortcut icon, my FS9 seems to start up normally, a second Task Manager "fs9.exe *32" process now appears together with the correct "MS Century of Flight" etc. application name ("running") under the "Applications" tab. My FS9 can now be used normally .... but .... because of the still ongoing high load on one of the other CPU cores, with somewhat less frame rates.

Under the "Processes" tab I can now terminate/remove the initial "rundll32.exe *32" (with the "08" in the CPU colom) and this then automatically also terminates/removes the initial "fs9.exe *32". This also brings peace and quiet back to my other CPU core load(s) and I can now begin using my FS9 and any of my supporting software without these CPU core loads in the background.

The end result in my Task Manager is a.o. a single "fs9.exe *32" process and the correctly named "Century of ...." Application.

I have the strong feeling that the problem is caused by some kind of internet access being directly called up by my initial FS9 "double click" and which then goes into a loop, possibly because my machine has no internet connection. I also believe strongly that the Windows "rundll32.dll" files are somehow involved, together with "Gameux.dll" files, each of which can be found in both the Windows "SysWOW64" and "System32" folders.

I've spent many hours in trying to decipher the "Sysinternals Process Monitor" listing but have not been able to find anything meaningful in the very many FS9.exe entries, which appear after the first double click. What should I be looking for in this huge listing, if my problem does somehow concern a loop.

My burning question is therefore: What could be trying to access the internet as the single and direct result of the initial double click, even before my FS9 actually starts up. Does any of you experts out there know of a way of somehow being able to find this hidden culprit so that I can get rid of it.

HELP !!

Hans

Andy,

The first thing you need to do is to install FS9 as a "custom" install, preferably into a partition other than the one in which your Win10 lives. Not only that but you need to designate the same FS9 main folder name as the one used in your backup. E.g. If your backed up main FS9 folder name is "FS2004" then you must specify this name during your new FS9 installation from the CDs.

When this is all done, delete .. do not uninstall .. the complete contents of you newly installed "FS2004" folder and then copy/paste the complete contents of your backup "FS2004" folder into the now empty new FS2004 folder.

Only in this way will the necessary folder structure remain intact as was setup during the new install from the CDs. Only the file sizes will be different.

I've already done this a few times without problems but I must admit that it was in WinXP and Win7 environments. However, I cannot think of any real reason why this should not work with Win10.

Good luck.

Hans