Networking with FSC 9.x


gbThe following situation is the starting point of a successful networking between FSX or P3D  (we call it here: Server PC) and FSC 9.xx (WideFS Client PC):
1. Hardware OK? (Check Network card, UTP cables, wireless connections)
2. Software OK? (Check the drivers of your network card)
3. Installation of FSCommander 9.x on the WideFS Client PC
4. Installation of WideFS  on the WideFS Client PC

When running FSCommander on the WideFS Client PC it needs access to the Server PC when:
a. updating the information from the FSX or P3D scenery files;
b. saving a PDMG  flight-plan (requires both read and write access);
c. saving a flight-plan to e.g. C:/Users/yourname/My documents/Flight Simulator X Files/; therefor this folder needs to be “shared”.
d. saving a flight-plan to e.g. C:/Users/yourname/My documents/Prepar3D Files/; therefor this folder needs to be “shared”.

Setting up the Server PC
Basically the Server PC needs access to the Client PC; therefore you need to share both the folder of FSX or P3D and the folder in which FSX or P3D saves its flight-plans; these are:
a. C:/Program Files (x86/Microsoft Games/Microsoft Flight Simulator X/
b. C:/Users/your_username/My documents/Prepar3D Files/

Setting up the FSC Client PC
In most of the cases you run FSCommander on an “old” XP+SP3 Client PC.   So first go to your Client PC, right click My Computer, Select Properties and then tab Computer Name.
In the field Computer Description you have identified this Client PC with a name: e.g. Jan’s Laptop Xp SP3;

The full computer name is the text that appears later on (on your Server PC) when you start selecting a shared network folder; so

  • Click the Change button and rename the computer name into e.g.: FSC Client PC.
  • Check the name of the workgroup, that should be the same as on the Server PC.
  • Click OK and restart the Client PC to activate the changes.

Read the full story in the C:/FSC/DOCS location and look for FSC.pdf
The last page describes how to arrange your network.