+---------------------------------------------------------------------------+
|              SCHIRATTI COMMANDER: HOW TO CONFIGURE PC FOR IPX             |
+---------------------------------------------------------------------------+

This is a "how to" Guide for the IPX Ethernet connection of:

        1. Schiratti Commander (SC) to Microsoft Flight Simulator 5.1 (FS)
        2. FS to another FS (Multi-Monitor)
        3. FMS (Flight Management System) to FS

+------------------+
| THE NETWORK CARD |
+------------------+

First, you need to put in your network card... there are a lot of cheap 
ones around that should work properly for this purpose.
We recommend to use a network card 100% compatible with NE2000.

A network card is much like any other card you can put into your PC. 
If you have experience in doing that, it shouldn't be a problem. If you 
have not inserted a card into a PC before, please ask for advices to your 
favourite store or to a friend.

A network card usually comes with a diskette... we shall need it later on.

One network card is needed for each PC.

+----------------+
| NETWORK CABLES |
+----------------+

You also need network cables, one T connector for each card and terminators. 
Ideally you should ask for Ethernet COAX cable (for the desired length) 
and TWO terminators.

+--------------+
| WHAT IS IPX? |
+--------------+

Now, forget everything you have heard about networks before.

We are *not* talking about a Client/Server system, you will only need one 
computer for each SC, FS and/or FMS. All in all, is a simple collection of 
cables, network cards and the minimum software which allows us to get data 
from one computer to another.

IPX is something similar to the lowest lifeform on a network system. It 
assures that the network has resources at its disposal. This can be compared 
to what a naked PC is like... without any operating system. 
Somehow, a hard drive has to be accessed, a screen has to be driven (etc.): 
the operating system needs "something" to do that. IPX is the "something" 
needed for a network. It is very widespread and available for many different 
operating systems.

IPX is a resource that SC uses to retrive data from your PC: position, 
altitude, heading etc... and we would like it to work correctly. 
Please use the checklist below to prepare for the setup.

-----------------------------------------------------------------------------
NOTE: do not worry about data security. You are NOT connected to a file 
network, with only IPX installed, it is NOT possible to get any files or 
data from your PC.
-----------------------------------------------------------------------------

+-----------+
| IPX SETUP |
+-----------+

This text describes the installaton of IPX under DOS, under Windows, you
should be able to make IPX available to the system by following the
procedures described in the Windows 95 manual or the Windows 95 Help.

Should you experience any problems, please follow the DOS procedure, and run
the IPX.BAT within a DOS window before starting either FS, SC or the FMS.

You do not need to be connected to a network to test the correct installation 
of the IPX drivers. This test can be done as soon as you have installed the 
network card.

You need two .COM programs for this, LSL.COM and IPXODI.COM, as well as a 
configuration file, NET.CFG. For your convenience we have added a batch file, 
IPX.BAT, to simplify your job. 

The IPX drivers (.COM) MUST BE SUPPLIED with the network cards.

First you should setup your card for the connection. This can be accomplished
either with modifying the position of some switches on the board (for the 
older models) or using a configuration program to configure board settings 
(IRQ, port, etc.).

Then, search in the diskette that came with the card for the card driver. 
Usually it is located in a subdirectory called \IPX or \ODI or \DOSODI. 
Generally, look for those words as well as NETWARE, NOVELL etc.

Popular drivers will be NE1000, NE2000 (Novell), EXP16ODI (Intel).

Let us suppose that this driver is called NE2000.COM for the Novell NE2000 
card.

Edit NET.CFG:

++++++++++++++++++++++++++++++++ example
# Setup the NE2000 card
Link driver NE2000
    INT 5
        PORT 300
        FRAME ETHERNET_802.3
        PROTOCOL IPX
++++++++++++++++++++++++++++++++ example

Change the settings as needed... use the Interrupt and Port address you have 
set with your card (either moving switches or defined with the configuration 
program). Good settings usually are Interrupt 5 (LPT2, often is not present 
on a PC) and Port addresses 300, 320 or 340. This should avoid conflicts 
with sound cards etc.

In our example, we should use INT 5 and PORT 340, as well as change all 
NE2000 to NE1000:

++++++++++++++++++++++++++++++++ example
# Setup the NE1000 card
Link driver NE1000
    INT 5
        PORT 340
        FRAME ETHERNET_802.3
        PROTOCOL IPX
++++++++++++++++++++++++++++++++ example

-----------------------------------------------------------------------------
NOTE: In most cases, the setting of the INT and PORT is done via hardware. 
Please make sure that the hardware settings and the data in NET.CFG are 
exactly the same!!!
-----------------------------------------------------------------------------

Now edit also IPX.BAT:

++++++++++++++++++++++++++++++++ example
LSL.COM
@echo ----------------------------
@echo insert your driver here!!!!!
@echo ----------------------------IPXODI.COM
++++++++++++++++++++++++++++++++ example

Remove the "@ECHO" lines and insert the filename of the card driver between
LSL and IPXODI:

++++++++++++++++++++++++++++++++ example
LSL.COM
NE1000.COM
IPXODI.COM
++++++++++++++++++++++++++++++++ example

After saving the file, run IPX.BAT.

All drivers have to report successfully. If there is any problem, please 
check the following list:

        - Is the network card firmly installed inside the PC?
        - Are the IRQ and PORT settings identical with the entries of
          NET.CFG?
        - Is the card driver (e.g. NE1000) reporting the correct INT and
          PORT?
        - Which messages do you get on the screen?

Now run MSD (Microsoft Diagnostics) which is usually supplied with MS-DOS. 
Go to the point called "Network", something should be reported there. Access 
the point and check for the following entries:

        - Network Detected: Yes
        - IPX Installed: Yes
        - ODI/LSL Installed: Yes

Repeat installation and test on each PC that has to be used for the 
connection.

If you have passed this, then everything should work properly.

+----------+
| FS SETUP |
+----------+

In order to setup an IPX network you also have to copy master/slaves drivers 
supplied in the SC CD-ROM. 
Deciding which drivers copy and where to put them depends on the kind of 
connection you want to create. Here follows an example of different kind of
connections.

ONE SC TO ONE FS:
If you use two PCs, one running SC and the other running FS, you only need 
to copy the MASTER1.FSO driver in the FS directory.

ONE SC TO TWO FSs:
If you want to link two PCs running FS with one running SC, you will have to
copy MASTER1.FSO in the FS directory of the first PC and MASTER2.FSO in the 
FS directory of the second one.
As we have supplied four different MASTER drivers you will be able to connect
up to five PCs: one running SC and the other four running FS.

ONE FS TO ONE FS:
If you use two PCs, both running FS you need to copy the MASTER1.FSO driver 
in the FS directory of the master PC and the SLAVE1.FSO driver in the FS 
directory of the slave PC.

ONE SC TO MORE FSs:
If you want to link three or more PCs running FS, you will have to copy 
the MASTER1.FSO in the FS directory of each master PC and SLAVE1.FSO in the 
FS directories of all the slaves(s) PCs related to that master.

This way you will be able to create a network with an UNLIMITED number of 
PCs!!!!! The configuration may reflect the following scheme:

             +-----+     +-----+     +-----+     +-----+         
             |FS M1|-----|FS M2|-----|FS M3|-----|FS M4|
             +-----+     +-----+     +-----+     +-----+         
                |           |           |           |
              +---+       +---+       +---+       +---+         
              |SC |       |SC |       |SC |       |SC |
              +---+       +---+       +---+       +---+         
                |           |           |           |
              +---+       +---+       +---+       +---+         
              |FMS|       |FMS|       |FMS|       |FMS|
              +---+       +---+       +---+       +---+         
                |           |           |           |
             +-----+     +-----+     +-----+     +-----+         
             |FS S1|     |FS S2|     |FS S3|     |FS S4|
             +-----+     +-----+     +-----+     +-----+         
                |           |           |           |
             +-----+     +-----+     +-----+     +-----+         
             |FS S1|     |FS S2|     |FS S3|     |FS S4|
             +-----+     +-----+     +-----+     +-----+         
                |           |           |           |
               ...         ...         ...         ...
               ...         ...         ...         ...
                |           |           |           |
             +-----+     +-----+     +-----+     +-----+         
             |FS S1|     |FS S2|     |FS S3|     |FS S4|
             +-----+     +-----+     +-----+     +-----+         

Where "SC" are the PCs running SC; "FMS" are the PCs running FMS (see also
the \FMSDEMO directory in the SC distribution CD-ROM); "FS Mx" are the PCs 
running FS with the MASTERx drivers and "FS Sx" are the PCs running FS with 
the SLAVEx drivers.

+---------------------------+
| CONNECTING SC-FS WITH IPX |
+---------------------------+

Now you *have* to be connected to a network to test the correct operation 
of the IPX drivers. Connect at least two PCs with network cards using a 
cable and terminators on both ends. You do not need any server.

-----------------------------------------------------------------------------
NOTE: When making tests, remember to always run the IPX.BAT file first.
-----------------------------------------------------------------------------

Run IPX.BAT, make sure it has installed all drivers successfully.

Copy MASTER1.FSO into your FS directory.

Edit FS5.INI and add the following line at the bottom of the file:

DEVICE=MASTER1.FSO

Save the file and load FS. 

On the other PC load the SC's SETUP program and set the "IPX Network" 
option to ON, then load SC and press "0". 

Usually, FS position data should appear on the SC screen when it has 
finished to load and shows up on Meigs (or any other airport that has been 
specified in the startup situation).

If this does not work, please check the following list:

        - Are the cables firmly connected?
        - Do the cables have terminators?
        - Did you run IPX.BAT and are the drivers correctly installed?
          (use MSD or MEM /C to check)
        - Did you include DEVICE=MASTER1.FSO in the FS5.INI file?

+-------------------------------------------+
| CONNECTING FS MASTER-FS SLAVE(S) WITH IPX |
+-------------------------------------------+

Again, you *have* to be connected to a network to test the correct operation 
of the IPX drivers together with our master/slave drivers. 
Connect at least two PCs with network cards using a cable and terminators on 
both ends. You do not need any server of any kind.

-----------------------------------------------------------------------------
NOTE: When making tests, remember to always run the IPX.BAT file first.
-----------------------------------------------------------------------------

Run IPX.BAT, make sure it has installed all drivers successfully.

Install FS on every PC that is connected. Then define which PC is the Master
and which ones are the Slaves.

-----------------------------------------------------------------------------
DEFINITIONS:

        MASTER PC: is the main PC you will use to fly with FS and is 
                   responsible for sending the data to one or more SLAVE PCs. 
                   
        SLAVE PC : receives and displays data that receives from the MASTER 
                   in the net. 

Copy MASTER1.FSO into the FS directory of the Master PC.
Copy SLAVE1.FSO into the FS directory of the Slave(s).

Edit Master FS5.INI to add the following line at the bottom of the file: 

DEVICE=MASTER1.FSO

Save the file. 

Edit FS5.INI to add the following line at the bottom of the file found 
in EACH Slave PC(s):

DEVICE=SLAVE1.FSO

Note: use SLAVE1.FSO on all Slave(s).

Save the file(s). 

Start FS on all PCs. The sequence is not important. Once FS is running on
ALL PCs, there should be the same outside view, the cockpit, on each PC. 

Put all the Slave(s) in "SLEW" mode (pressing "Y").

Disactivate the outside view on the Master, and the Instrument Panel on the 
Slaves (menu "Views", "View 1" then "Instrument Panels").

Fly around with the Master. The outside view on all the Slaves screens 
should follow the movement of the Master airplane.

If this does not work, please check the following list:

        - Are the cables firmly connected?
        - Do the cables have terminators?
        - Did you run IPX.BAT and are the drivers correctly installed?
          (use MSD or MEM /C to check)
        - Did you include DEVICE=MASTER1.FSO in the FS5.INI file of the
          Master?
        - Did you include DEVICE=SLAVE1.FSO in the FS5.INI file of each
          Slave(s)?
        - Is there only one Master in the net? There should be only one!

If everything succeeded as planned enjoy your network!

Should you have any questions or doubts, feel free to contact us 
(e-mail ONLY) at the following address: 100411.3660@compuserve.com

All Rights reserved.
(c) 1995,1996 Enrico Schiratti, LAGO
Scenery MAKER is (c) 1995,1996 Simula FlightWare, LAGO. 
Network drivers are (c) 1995,1996 Simon Hradecky, NOMISSOFT. 
Scenery Budapest and Scenery Delhi are (c) 1995,1996 Andras Kozma, LAGO. 
Microsoft,MS-DOS and Windows are either registered trademarks or trademarks 
of Microsoft Corporation in the United States and/or other countries. 
Flight Simulator is a trademark of Bruce A. Artwick. 
All other products and brands are trademarks or registered trademarks of 
their respective owners.
-----------------------------------------------------------------------------
Written by Enrico Schiratti
*** END OF DOCUMENT ***
-----------------------------------------------------------------------------
