Aerosoft FS Flight Keeper & WideFS - Assistance Please!

[draky]

Having purchased the registration for both FSUIPC and WideFS I was somewhat disappointed to find that FSNav would not work with WideFS to dispaly the moving map on my laptop. My fault and I should have done some more research before the outlay.

I then discovered the FS Flight Keeper and read of how this utility can run on a second computer with WideFS support. Plumped for the trial version of FSFK first to see if I could finally get a moving map functioning on the lap top whilst FS9 was running on my main simulator computer. All WideFS and FSUIPC are latest versions and so far I have yet to see anything appear on my laptop other than a large white WideClient screen.

FSFK is installed on the main computer that runs FS9. Every time I try to get FS Flight Keeper up and running on the WideFS all I get is an error message "WideClient could not run "\\Computername\Program Files\FS Flight Keeper\FLKeeper.exe" [Error 53].

I have shared the relevant folders over the network and firewalls are OFF but yet to see anything on the laptop screen in WideFS - all rather disappointing. I will gladly purchase FS Flight Keeper only IF I can get to see it functioning on the secondary laptop screen.

Should I have FS Flight Keeper installed on the laptop? - it is presently installed on my main computer that runs FS9. If I try and run FS Flight Keeper from the laptop (over the LAN) I get the startup but all closes down on the "reading configuration, please wait...." opening sequence.

Any offers of what I need to do or am doing wrongly? - thanks.

[Pete Dowson]

Having purchased the registration for both FSUIPC and WideFS I was somewhat disappointed to find that FSNav would not work with WideFS to dispaly the moving map on my laptop. My fault and I should have done some more research before the outlay.

Yes. I would be an avid FSNav user myself if it were possible to move onto another PC, but it not only is not a separate program (it's an internal FS DLL just like FSUIPC), but it doesn't even use FSUIPC at all.

I then discovered the FS Flight Keeper and read of how this utility can run on a second computer with WideFS support. Plumped for the trial version of FSFK first to see if I could finally get a moving map functioning on the lap top whilst FS9 was running on my main simulator computer.

I have the full version set up like that, and it works very well indeed. FSFK is a really good program, not just for its moving maps but its weather mapping, and especially its detailed logging functions.

All WideFS and FSUIPC are latest versions and so far I have yet to see anything appear on my laptop other than a large white WideClient screen.

You don't really want a WideClient screen at all. I'm pretty sure the default INI I supply does that. Have you stretched it or maximised it? Best set the option to minimise it or even hide it.

FSFK is installed on the main computer that runs FS9.

Well that's no use if you want to run it on the other PC! What's it doing there? You run FS9 on the main FS9 PC and client programs on the clients. That's the whole point. You'd not accomplish anything running it on the FS PC.

Should I have FS Flight Keeper installed on the laptop? - it is presently installed on my main computer that runs FS9. If I try and run FS Flight Keeper from the laptop (over the LAN) I get the startup but all closes down on the "reading configuration, please wait...." opening sequence.

It all worked fine here -- you have to have WideClient running on the client and FS9 with WideServer running on the FS PC, and I think there's some configuration you have to do in FlightKeeper to run it that way. It's all in the documentation. I just did what it said and it all worked.

If you have questions on FSFK you are best off dealing with their support. I remember doing it and it seemed easy enough but I cannot remember it exactly now to tell you, and it's a bit pointless me quoting documents at you.

Regards,

Pete

[draky]

Thanks Peter - I now have it all working fine, guess I should have realised that the client computer should have the program resident. Thanks for your time mate... Dave