曝光臺(tái) 注意防騙 網(wǎng)曝天貓店富美金盛家居專營(yíng)店坑蒙拐騙欺詐消費(fèi)者

A typical network layout comprises of one Server
computer (usually the most powerful) and several Clients
as illustrated.
Project Magenta Revision: 26-May-07
7
In the schematics, you can see how each client is connected together via a switch/hub to the Server. Each
client has a VGA output to drive respective flight displays. Note how (in this example) pmSystems and the
MCP has been left out of the loop, this is simply because you can choose where to run these (as with any
of the other pm software), like pmSounds, – etc. Generally, the rule of thumb is, if you eventually won’t
need to actually see the software graphic (as you will have hardware as the main input / output device)
then that particular control program can run minimized. You may choose in this example to run the MCP on
the Server, or perhaps the EICAS computer. With the CDU program, you still need to see the output of the
screen, so if you have CDU hardware then we have an option so that just the full screen output of the CDU
is shown.
You should build a schematic of your set-up, the schematic shown here is merely one example. As a further
note, with a program like pmSystems, whilst it will control you’re a/c systems in a minimized state (so you
don’t have to see it) it will be a requirement to see
it full screen during the test phases of your set-up
as you connect your hardware (if used in this
fashion). Thus you might choose to run it on a
laptop or spare PC. Conversely, it may be used as
software alone without hardware, then of course
you will need a screen to see it.
A Note about Multi-Monitor
Because multi-monitor is entirely dependent on
what particular video hardware you have on your
system, we cannot support this type of
application. Experimentation is required on your
behalf to achieve this. Generally we only
recommend networked solutions and thus we can be of little assistance in software set-up in environments
that we don’t fully support. This applies to all PM programs. You can not run MSFS on one screen and a PM
program on another. Generally, this won’t work because only one program can be the “active” program at
one time and thus graphics acceleration is limited to the active program.
Project Magenta Revision: 26-May-07
8
Step 2. Installation of WideFS and FSUIPC
To connect MSFS and Project Magenta programs together, across a computer network, you need an
intermediary program called WideFS. Full docs are enclosed with these programs and are the most up-todate
and thorough source of information. Below is really just a quick start summary.
A registered version of FSUIPC must be installed in your MSFS Modules folder.
A registered version of WideFS is also required for network communications and the installation is as
follows.
WideFS is split into two main components as illustrated above.
The Wideserver component (Wideserver.dll and Wideserver.ini) are placed in your MSFS Modules folder.
That is all you need to do for the Sever component installation.
The Wideclient component (Wideclient.exe and Wideclient.ini) are placed on your client computers
(computer that you wish to connect to MSFS). You can create a folder perhaps called “WideClient” or copy
them into the PM main program folders – it actually does not matter. Each time you want communication
across the network with MSFS, Wideclient.exe must be running.
Step 3 Setting Server Name or Static IP
WideFS can use either the IPX network protocol for communication or TCP/IP. TCP/IP is now the standard
and we recommend its use on most systems. For IPX usage, please refer to Peter Dowson’s documentation
included with the WideFS package. There is also a new protocol in use called UDP. This is a faster protocol
but there is no error checking. It is purely system dependent as to whether this can be used. As a general
rule, most computer systems will run well using TCP/IP.
Generally, after installation (as above) of the various files included in WideFS, as a basic rule you should
not actually have to do anything more but we also like to at least edit the wideserver.ini file, use a text
editor like Windows Notepad. Add the following entries in the first Section of the Wideserver.ini file:
ServerName= (your Server’s Name)
Or
ServerIPAddr= (your Server’s IP address)
You only need to set either the ServerIPAddr or ServerName (not both). It is recommended that you use
the ServerName option. Then add to the same ini file ProtocolPreferred=TCP (or whatever protocol you
prefer) we recommend TCP at least to start with.
Project Magenta Revision: 26-May-07
9
If you do not know how to find your ServerName or IP address, please contact Project Magenta support or
　
中國(guó)航空網(wǎng) www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：航空資料12(90)