It's not often that I have to post up for help with a technical issue, but this one has me really stumped!At some point yesterday I noticed that upon running the fs9.exe, the program never actually ran. Checking the processes list, it showed fs9.exe as running but using only a few megabytes of memory (far lower than it should be if actually running in memory). I eventually figured out that the only way to get fs9 to run is to run the exe a second time, whilst the first instance of the process is already running! The first process can then be killed once the program is running. Strange.I've tried to run with a new fs9.cfg as well as using a backup scenery.cfg and also the original, and new copy of the exe itself. None of these help unfortunately. Not a huge problem but it's slightly annoying to have to remember to close the first process every time I want to start FS now!Never seen or heard of something like this before so any suggestions are welcome.

Hello,I'm not in your machine But .....

At some point yesterday I noticed that upon running the fs9.exe

so .. it's yesterday you noticed .. blah blah ..I assume FS2004 was running fine before.So it's some change somewhere before yesterday or after the last time FS2004 was running fine.Find what was (you ? ) changed in your system ... and correct if necessary ...Regards.Gus.

It's not often that I have to post up for help with a technical issue, but this one has me really stumped!At some point yesterday I noticed that upon running the fs9.exe, the program never actually ran. Checking the processes list, it showed fs9.exe as running but using only a few megabytes of memory (far lower than it should be if actually running in memory). I eventually figured out that the only way to get fs9 to run is to run the exe a second time, whilst the first instance of the process is already running! The first process can then be killed once the program is running. Strange.I've tried to run with a new fs9.cfg as well as using a backup scenery.cfg and also the original, and new copy of the exe itself. None of these help unfortunately. Not a huge problem but it's slightly annoying to have to remember to close the first process every time I want to start FS now!Never seen or heard of something like this before so any suggestions are welcome.

That is very strange as i was about to post the same thing, i double click the desktop icon and nothing, i doublr click again and it starts, when i close the sim and shut down the computer i have to force shutdown as it is still running. Help is needed guys please. BTW it was a fresh install yesterday.Regards

Gus,That was my first port of call. The only thing I changed yesterday was to install the UK2000 demo for EGGD, which was then removed. I've manually removed all files from the scenery as well as the scenery.cfg and reg entries. It's extremely strange as I don't think it's anything to do with any scenery/addon core files as the .exe simply doesn't even attempt to run itself, demonstrated by the fact that when I removed the fs9.cfg, it didn't even try to build a new one after running the .exe.....something that is normally done straight away. The first instance in the process list sits at 1-3Mb memorey usage, whereas a normal execution continues running into a 100+Mb's.The problem also occurs on the first run of FS after turning the comp on, so it's not a case of a process being left open (yet hidden from the process list) after previously closing FS.Anyway, not the end of the world in terms of FS problems! I'm probably about due a clean install soon anyway so will no doubt sort it out then.

Hello,Sorry to back to my initial feeling .. but it's no invisible ghosts acting in a PC :( But .. it's sometime malicious gremlins and those are reals and visible They can be installed in the PC by the user (with his knowledge or not) or by a external actor (automatic update ... malicious datas .. etc..) or the user changed something in the PC system (again knowing it or not)So .. I feel it's a gremlin(s) or a change somewhere ....Regards.Gus.

My comp started doing the same thing...I had installed MS off 2010 and did some automatic updates...running Windows 7 (64 bit)...