spirittoo

Well sir ... I got it together!   

It was the Kensington adapter driver that was the problem.  I had installed the wrong driver .... I had the driver for the 3.0 USB when the adapter I have is 2.0 USB ....

Called Kensington tech support.  He showed me what to do and where to get the correct driver and how to set up the adapter ...

I had to unhook the adapter and uninstalled all its software.  Then I had to reinstall the correct software and then restart the computer.  Once booted up again.  I hooked up the adapter.  I was able to use the extend option and I had my three screens.  

All I had to do is go into windows display properties identify the screens made the middle my main screen and got them in order for the mouse to move back and forth between screens and that's it.

Thanks for reading my post. :mellow:

Well sir ... I got it together ... my instructor showed me how to get the three screens going.  First of all I didn't need to go into full screen mode like I saw on youtube.  I had to hit the [ key and right click on the new window and clicked undock window in the menu.  Then I dragged the new window over to my left, then right screen using the same procedure.  Then I had to right click on each window on the sides and choose V cockpit, then used my POV on my stick to turn the view to the side.  I lined every thing up with my POV, then saved the flight.  So I have my three screens for the sim and the 4th for the map on line. B)

I can now connect to FSInn ... it appears the problem wasn't FS9 or FSInn ... I found a super geek and he help me find out what the problem was.  He had me run the DXDiag ... when into the networks tap and ask it to do a direct play test ... the result showed it was not working because it could not complete the test which indicated the problem was not with FS9 or FSInn ...  I had recently hooked up a wireless router so we when to the ip address the router was located ... when into the admin section and had it disable the UPnp after that I was able to connect.  Problem solved.

I don't know what happen but  ... I decided to try and install it again and this time I looked in the drive I want it to go and am seeing the drive being filled. Looks like I'm in for another 4 hours install ... but I think it will be okay this time ... I am seeing the global folder now in the drive.  Thanks for reading my post. B)

Alrighty then ... I got it together .... I was in the wrong camera config file.  I went to the one in the program files ...  Here is what I did ...
 
[CameraDefinition.003]
Title = Fixed Spot //Locked Spot
Guid = {BCA3FDD1-FB83-4BBA-8407-4922A7F0D00C}
Description = This is the description of the fixed spot view.
Origin = Center
SnapPbhAdjust = Ordinal //Swivel
SnapPbhReturn = False
PanPbhAdjust = Swivel
PanPbhReturn = False
Track = FixedChase //FlatChaseLocked
ShowAxis = No
AllowZoom = Yes
InitialZoom = 1.0
SmoothZoomTime = 2.0
ShowWeather = Yes
XyzAdjust = FALSE
Transition = Yes
ShowLensFlare=TRUE
Category = Outside
ClipMode = Spot
PitchPanRate=30
HeadingPanRate=75
PanAcceleratorTime=1

[CameraDefinition.004]
Title = Locked Spot
Guid = {BCA3FDD1-FB83-4BBA-8407-4922A7F0D00D}
Description = This is the description of the spot view.
Origin = Center
SnapPbhAdjust = Swivel
SnapPbhReturn = False
PanPbhAdjust = Swivel
PanPbhReturn = False
Track = FlatChaseLocked // FlatChaseLocked//
ShowAxis = No
AllowZoom = Yes
InitialZoom = 1.0
SmoothZoomTime = 2.0
ShowWeather = Yes
XyzAdjust = FALSE
Transition = Yes
ShowLensFlare=TRUE
Category = Outside
ClipMode = Spot
PitchPanRate=30
HeadingPanRate=75
PanAcceleratorTime=0
HotKeySelect=3
 
It is a bit jerky ... can I do something to smooth it out otherwise it's great.

Well yes indeed ... going into the control panel to the sound and telling it to do nothing did the trick ... thank you so much for your help.  Problem Solved! :lol:

:lol: Well alrighty then!! Well sir ... I figured out what you did and added those codes from the scenery into the world airport.  That worked fine, but the training helipads were not there at the KMSO airport as they should be.  So I went to the Missoula V2 and saw BGL files for KMSO ... I copied those files and put them in the V4 files because they were not there ... after that I saw the pads at KMSO, but they were all white ... so I went to the texture folder in the Missoula V2 files and copied the training pad textures ... they were easy to locate because it was in picture form.  Once I did that ... Problem Solved ... Thanks so much for your help. :wub:

Well allrighty then!!  I got it together.  I poster gave me a link to this website and I followed the instructions on this page ... and I was all set.  I was doing it all wrong,  Just follow the instructions like I did and you will have FSInn working too.
 
 
PROBLEM SOLVED