- Thu Feb 10, 2011 9:49 am
Below are the steps. The installations worked perfectly the first time each time:
1.Installed Flight Simulator then installed the appropriate service pack for the Flight Simulator version (FS9.1, FSX/SP1, FSX/SP2) on a fresh system.Flight Simulator is already installed, so I don't think I need to do that.
2. Installed FSCopilot 1.7 and FSinn 1.3. Run FSInnUI once from the Start menu to update .ocx registration. (Important to click Start -> FSFDT -> FSInnUI -> Chat).
(During the install, I didn't make any changes or type anything in any of the fields. I just clicked Next or ENTER, for both packages. )Installed FSCopilot 1.7 and then FSInn 1.3, making no changes or typing anything into any of the fields.
2a. Vista (and Windows 7) Specific
Important Specifically for Vista (and Windows 7):
I right clicked on the FSX.exe (or FS9.exe) program and set the compatible mode to Run as Administrator (by putting a check mark in the "Run as Administrator" option). Very Important: Don’t put any check marks in any of the FSInn modules.
(You can find Flight Simulator's install directory with FindFS.)FS2002 is already setup to run as administrator. (I learned about that with Microsoft Train Simulator.)
Also, right click on the FSInnUI (the Inn Control Panel) from the start menu. Click on Run As Administrator, then Click on Chat.Ran FSInnUI once from the start menu as an administrator, clicked on the chat button.
For Windows 7 the system has to be run from an account that is Administrator type (a Standard user will not work properly) This is changed from the Control Panel -> User Accounts - Change Your Account Type.
3.Started Flight Simlator, clicked on Add-on, Clicked on Inn Control Panel -> Set -> General -> Basic (Filled in my Call Sign, First Name, Last Name and Homebase Airport. Then Clicked Network -> VATSIM (typed in my UserID, Password and a current server from the link [Vatsim Current List of Servers]). The default installed IP is obsolete.Started Flight Simulator 2002, started a flight at Meigs with the default C172. I then clicked on CoPilot, then FSInn Control Panel. Then I click on Set - General - Basic, then filled in my Call Sign, First and Last names, and home base airport (KOKM). Afterwards I clicked on Network - VATSIM, and typed in my UserID, Password, and the IP Address for the VATSIM server in Ohio.
FSInn manual instructions for connecting with FS2002:
With FS2004, FSInn then starts a multiplayer session automatically. The process is
the same as if you connect the session in the FS9 menu: ‘Flight/Multiplayer/Connect’.
With FS 2002, you must make the multiplayer connection manually,
‘Flights/Multiplayer/Connect’ and enter the IP address 127.0.0.1 or localhost.So, I click on Flights/Multiplayer/Connect and enter 127.0.0.1 under IP address, and then I click on search. After a few seconds, FWInn appears under sessions, I select it, and then click join. After I click join, FS2002 thinks for a few seconds, but does nothing. I try again, only changing 127.0.0.1 to localhost, but the result is the same.