Startup / Shutdown computers
DESCRIPTION
In a homecockpit one can find usually 3 to 4 computers to all of the hardware with software to send and to function properly.
To all software to start up and to close off we are for a while ...
To this startup/shutdownprocessen to simplify, we can make use of a few handy tools that be provided for free, and all are present in our cockpitsoftware.
It is intended to with one press of a button, all programs, one behind the other to start, and after the flight the programs to close, and then the ‘shutdown’ of all computers.
So, Full Automatic. This we can all with FSUIPC ...
Here we go !
FSUIPC
Meanwhile, we already know that FSUIPC (with WideFS) an entire change has brought about in the world of flightsimmers, and this especially for the ‘clients’ or cockpitbouwers.
I dare myself to say that FSUIPC the main program is after FS (FS9, FSX, FSX-SE and P3D).
The possibilities of FSUIPC are very extensive and, for many, is still unknown. Therefore, it is very interesting to the user manuals of FSUIPC. It brings you up to ideas and solutions ...
Wideserver and Wideclient (WideFS)
In general terms, we know that FSUIPC is built with a server (Wideserver/FSUIPC4) and for the ‘remote’ pc's client software (WideFS or Wideclient).
The Wideserver/FSUIPC4 is located in the FS-folder ‘Modules’. The Wideclient is located on the remote pc's any place where the folder with Wideclient (WideFS).
The INI-files
To various actions to be performed by FSUIPC have the necessary commands or parameters are entered in the appropriate ini-files (Wideserver.ini, FSUIPC4.ini and Wideclient.ini)).
- WideServer.ini is used by FS9 (FS2004);
- FSUIPC.ini is used by FS9 (FS2004);
- FSUIPC4.ini is used by FSX (P3D) with an integrated [WideServer] section;
- WideClient.ini is used by all Clients (WideFS or WideClient).
Important ! Here we must state clearly that the appropriate and most preferably the last versions are going to use (download) depending on which flightsim you use (FS2004, FSX, FSX-SE, P3D).
This is both for FSUIPC, as well as corresponding WideFS! We'll also assume that we work with a registered version ...
These versions can be found at the following link : http://www.schiratti.com/dowson.html
FS9/FS2004
CONFIGURATION FSUIPC.INI (Modules Folder FS9)
In the section [Programs]
[Programs]
Run1=READY,CLOSE,D:\Prosim737\ProsimMCP\ProsimMCP.exe (Startup of the program in the path after Wideserver is started and is closed after the Wideserver is closed, i.e. after the startup/shutdown of FS since the Wideserver in the folder ‘Modules’ of FS. The startup/shutdown proceeds in the order of Run1, Run2 ...)
Run2=READY,CLOSE,D:\Prosim737\ProsimDisplay\ProsimDisplay.exe
Run3=READY,CLOSE,D:\Prosim737\Prosim737\Prosim737.exe
CONFIGURATION WIDESEVER.INI (Modules Folder FS9)
In the section [User]
Log=Errors+
WideFSenabled=YES
AllowShutdown=YES (Admission to the FS pc to shut down)
AutoShutdown=YES (Admission to the Wideserver automatically shut down all Client pc's after FS is closed)
ShutDownHotKey=69,11 (Hotkey format is the same as ‘Shift+Ctrl+E’ – if ‘shutdown’ command for all client pc's and also FS-pc – accordance with the ‘AllowShutdown’ parameter)
******************************
FSX/FSX-SE/P3D
CONFIGURATION FSUIPC4.INI (Modules Folder FSX)
In the parts [Programs] and [Wideserver]
[Programs]
Run1=READY,CLOSE,D:\Prosim737\ProsimMCP\ProsimMCP.exe (Startup of the program in the path after Wideserver is started and is closed after the Wideserver is closed, i.e. after the startup/shutdown of FS since the Wideserver in the folder ‘Modules’ of FS. The startup/shutdown proceeds in the order of Run1, Run2 ...)
Run2=READY,CLOSE,D:\Prosim737\ProsimDisplay\ProsimDisplay.exe
Run3=READY,CLOSE,D:\Prosim737\Prosim737\Prosim737.exe
[WideServer]
WideFSenabled=YES
AdvertiseService=1
ProtocolPreffered=UDP
BroadcastMode=YES
Port=8002
Port2=9002
AllowShutdown=YES (Admission to the FS pc to shut down)
AutoShutdown=YES (Admission to the Wideserver automatically shut down all Client pc's after FS is closed)
ShutDownHotKey=69,11(Hotkey format is the same as ‘Shift+Ctrl+E’ – if ‘shutdown’ command for all client pc's and also for the FS-pc – accordance with the ‘AllowShutdown’ parameter)
******************************
FS9/FS2004 and FSX/FSX-SE/P3D
CONFIGURATION WIDECLIENT.INI On all WideFS pcs –FS9/FSX)
In the section [User]
[User]
Log=Errors+
RunReady1=C:\Prosim737\ProsimDisplay\ProsimDisplay.exe (The question to Wideclient to run the program in the path to start up after connection of Wideclient with the Wideserver – after the startup of FS since the Wideserver in the folder ‘Modules’ of FS. The startup proceeds according to the sequence 1, 2, 3 ...)
RunReady2=C:\Prosim737\ProsimAudio\ProsimAudio.exe
RunReady3=C:\Prosim737\ProsimCDU1\ProsimCDU.exe
CloseReady1=YES (The ask Wideclient to run the program that is started up by the " RunReady’ when Wideclient itself closes)
CloseReady2=YES
CloseReady3=YES
AllowShutdown=YES (Admission to the Client pc to shut down)
******************************
THE FOLDER ‘STARTUP’
One can at the startup of the computer is already a number of programs automatically start via Windows the shortcuts of these programs in the folder "Startup".
These programs are e.g. : Flight Sim, WideClient.exe ...
This folder "Boot" is to be found at the following location :
Open the “run” window with the keyboard shortcut CTRL+R, enter the command “AppData” and press “OK”. You get an explorer window opens, in which you successively the following folders click on: Roaming, Microsoft, Windows, Start Menu, Programs (the folder, not the shortcut), and finally “Startup”.
Place shortcuts to the programs that should start up with Windows.
IN PRACTICE
- After the startup of all the client pcs are all Wideclient.exe automatically started by Windows (Startup folder);
- After the startup of the Server-pc (Flight Sim) is Flight Sim will be started automatically by Windows (Startup folder);
- After the startup of Flight Sim are automatically all programs are started, which are listed in the Wideserver (FSUIPC4.ini) (e.g. Prosim737, ProsimMCP, ProsimCDU, ProsimDisplay, ProsimAudio, SIOC);
- After the startup of Flight Sim (Wideserver) all of the programs on the client pc’s started which are listed in WideFS (Wideclient.ini) (e.g. ProsimDisplay, ProsimAudio, AFAS, PSU, IVAP User Interface, ASN, etc);
- All pc's, monitors, and programs in the cockpit to check through InputDirector (one keyboard and one mouse);
- Or via a remote the ‘remote’ pc (e.g. Dispatch/Instructor Station/Flightplannings-pc) can be Teamviewer at a distance and without in the cockpit rather than to take all of the cockpit-the pc's manage;
- After the flight one can all calls via Shift+Ctrl+E’ (Hotkey). This key combination can be via an interface board to program an available button in the cockpit (e.g. the button of the wipers in the FWD OVH). This is all of the programs on the client pc and server pc is shut down, and culminated in the ‘shutdown’ of all the pc's.
Here again the useful assistants mention that we can use in our cockpitomgeving :
INPUT DIRECTOR
On this website, I have already explained about Input Director and I want to again mention the benefits this program can bring to many cockpitbouwer.
In a cockpit, we have +- 4 computers i.e. 4 keyboards and 4 mice. In practice, not to do ...
With Input Director this past time. You use only one keyboard and one mouse for the whole ‘bunch’ of computers. With the mouse you can slide simply over from one screen to the other. You click in the screen, and at the moment this screen (and pc) is active for the keyboard.
And a small mini-keyboard and mini-mouse is easy to integrate into a cockpit ... Some people swear by a cockpit without mouse and keyboard but I can both not to be missed.
It is possible without, but I still prefer a ‘backup’ to have here and there something to restart. You never know ...
Therefore, the utility ‘Input Director’ the way to go !
TEAMVIEWER
Teamviewer here we have in the past also been raised. A zèèèèèr useful tool to use in a cockpitsetup.
Through Teamviewer you can remotely (e.g. via the Instructor station pc) all computers to be monitored. All the screens of all pc's are visible and accessible via Teamviewer.
It is the same as for the corresponding display in the cockpit.
Once all the computers are booted, you can so all the programs on remote booting via Teamviewer ... but that does not because of FSUIPC is this job done :-).
With Teamviewer you can avoid just you in your cockpit should be steps to one or the other in order to make regards the software. All software work is centralised on one remote the ‘remote’ computer.
It cannot be easier, right ?
Translated by Yandex.Translate and Global Translator