This is odd. I have recently moved to Bangkok from London for work. I shipped my FS PC here - it had a couple of bits jolted loose inside, but I fixed that without any problem. Hardware's one thing, but I can't see how shipping the PC would cause a software problem... Whatever, I didn't have this issue in the UK: when I start up FS9 (via the fs9.exe file, or any link to it, like a .flt file), I get a little rotating Win7 'thinking about it' icon, then nothing. In Task Manager FS9.exe *32 is there OK as a running process, but FS never starts up - the CPU value in the Task Manager is zero. If I double-click the fs9.exe file again, then I get two FS9.exe processes in Task Manager - and FS9 then starts up, but painfully slowly (to be expected). So to run FS9 now, I have to click the exe file, go into Task Manager and stop the FS9 process - after which, FS9 starts as normal when I click on the exe file, or any file that opens with FS9 (like a .flt file). Any ideas what is going on? Never had this problem before. Input appreciated! Thanks, Martin

This seems to have cleared itself.... Working now. Strange. M..

Probably just jet lag. Long flight, different time zones, bound to have an effect. Glad you're fixed though :-)