In Windows XP I used to be able to double-click on a shortcut to a saved flight (.flt file) and that would launch FS9 and open the flight at the airport.Now I have Windows 7 (the change may be coincidental to and not causing the problem) if I click on the same shortcuts I get an error message saying the file cannot be found or is corrupt. Clicking on OK closes FS9 at splash screen stage.Now the shortcuts definitely link to a valid .flt file in the My Documents/Flight Simulator Files folder (though my 'My Documents' folder is not in the default place - but then nor was it when I ran XP, so that's probably neither here nor there) - I can 'find the target' OK when I right-click on the shortcut. No idea why the file may be considered 'corrupt': if I start up FS9 via the FS9.exe file and then choose 'Select a Flight' and load the .flt file, it loads just fine. If the file were corrupt, I'd surely get the same error message.One other oddity - if I start FS9 via fs9.exe then double-click on one of my shortcuts to a flight (.flt) file, aflight does load - but always my default flight (Cessna at KSEA), never the flight contained in the .flt file. I'll add one simple flt file below, but I sort of know my way around these files by now and am pretty sure that there is nothing untoward in any of the data in it. Beside ALL of my .flt files produce the same result. If anyone has any ideas what might be going on I'd be interested to know. Thanks,Martin------------------------------------------------------------------------[Main]Title=Berlin to MunichDescription=AppVersion=9.1.40901FlightVersion=1[Tower]Latitude=N052° 21' 44.1954"Longitude=E013° 29' 57.3659"Altitude=+000350.00[Track]Latitude=N047° 25' 53.4256"Longitude=W122° 18' 28.7933"Altitude=+000432.00[Options]Titles=FalseSound=TruePause=TrueAxisIndicator=OffATC=FalseMoonlight=TrueSimSpeed=001.00ShowStars=TrueApproachLights=TrueFlightDisplay=OffSlewDisplay=Coordinates[EFIS]Active=FalseType=RectanglesDensity=ThinRange=ShortNavAid=VOR 1Altitude=0Flags=0[Avionics]LocalizerSelect=Auto SelectDMESelect=1[Kneeboard]PageId=0Visible=FalseLocation=665, 405Page0Scroll=0, 0Page1Scroll=0, 0Page2Scroll=0, 0Page3Scroll=0, 0Page4Scroll=0, 0Page5Scroll=0, 0[Panels]Panel.On=TrueHUD.On=False[Window.1]Order=0Active=TrueUndocked=FalseMaximized=FalseScreenUniCoords=0, 0, 8191, 2740UndocCoords=0, 0, 0, 0ViewMode=CockpitViewDir=ForwardCockpitZoom=000.75VirtualZoom=000.50TowerZoom=003.00TrackZoom=004.00SpotZoom=001.10MapZoom=011.00SpotDirection=113.54SpotDistance=+000349SpotTransitionType=RollSpotFastTransition=FalseSpotAltitude=+000060PanHeading=360.00PanPitch=360.00PanBank=360.00ChaseTarget=1SavedViewMode=Spot[ATC_AgentManager]NumberofAgents=0[ATC_Aircraft.0]ActiveFlightPlan=FalseRequestedFlightPlan=TrueAcState=ACSTATE_REQUEST_TAXI_CLEARANCE_OUT_VFR_ATISNumberofWaypoints=0ClearanceFlags=80CtCur=CLEARANCE_NONEWaypointNext=0AltCleared=-1HdgAssigned=-1SquawkAssigned=1816531456LandingSequence=LANDING_NONEDepartureRequest=DEPARTURE_VFR_REQUEST_NONEParkingRequest=PARKING_NAME_NONEPatternLeg=PATTERN_LEG_NONEApproachIndex=-1ApproachTransitionIndex=-1ApproachRequestIndex=-1ApproachTransitionRequestIndex=-1RunwayIndex=-1RunwayRequestIndex=-1ParkingIndex=-1FlightFollowing=FLIGHT_FOLLOWING_NOAirspaceTransition=AIRSPACE_TRANSITION_NONEBVAirspaceTransition=BV_TYPE_NONEBVAirspaceTransitionReq=BV_TYPE_NONETakeoffSequence=TAKEOFF_SEQUENCE_NONELandingSequenceNumber=-1TaxiRouteCurrent=-1CruisingAltitude=-1RequestedCruisingAltitude=-1ExpectedAltitude=-1AircraftSignature=1,0[ATC_RequestedFlightPlan.0]title=EDDB to EDDMdescription=EDDB, EDDMtype=EDDB, EDDMroutetype=1cruising_altitude=32000departure_id=EDDB, N52* 22.72', E13* 31.23', +000154.00departure_position=GATE 53destination_id=EDDM, N48* 21.20', E11* 47.16', +001486.00departure_name=Schonefelddestination_name=Munichwaypoint.0=, EDDB, , EDDB, A, N52* 22.72', E13* 31.23', +000154.00, waypoint.1=, , , KLF, V, N52* 1.18', E13* 33.83', +000000.00, waypoint.2=, , , ABDEX, I, N51* 44.48', E13* 36.98', +000000.00, waypoint.3=, , , OSKAN, I, N51* 25.65', E13* 40.48', +000000.00, waypoint.4=, , , BESIP, I, N50* 56.12', E13* 29.12', +000000.00, waypoint.5=, , , ABKIS, I, N50* 37.78', E13* 3.43', +000000.00, waypoint.6=, , , KILNU, I, N50* 28.62', E12* 54.70', +000000.00, waypoint.7=, , , AGNAV, I, N49* 34.03', E12* 36.81', +000000.00, waypoint.8=, , , RUDNO, I, N49* 20.15', E12* 32.48', +000000.00, waypoint.9=, , , MAMOR, I, N48* 53.15', E12* 13.33', +000000.00, waypoint.10=, , , ANKER, I, N48* 34.35', E12* 0.13', +000000.00, waypoint.11=, EDDM, , EDDM, A, N48* 21.20', E11* 47.16', +001486.00, [ATC_AircraftManager]NumberofAircraft=1[ATC_MessageSystem]FrequencyNodes=0[GPS_Engine]Filename=E:\My Documents\Flight Simulator Files\IFR Berlin to Munichposition=N52* 21.85', E13* 30.35', +000162.63Time=28520TimeWP=60641ArriveTime=2064CountWP=12NextWP=1PlaneStarted=FalseWpInfo0=451, 0, 46, 0, 0, 6316.3, 0.0, 0.0WpInfo1=451, 0, 2679, 0, 0, 0.0, 27.1, 0.0WpInfo2=451, 0, 4729, 0, 0, 0.0, 21.1, 0.0WpInfo3=451, 0, 7040, 0, 0, 0.0, 23.8, 0.0WpInfo4=451, 0, 9753, 0, 0, 0.0, 38.1, 0.0WpInfo5=451, 0, 9753, 0, 0, 0.0, 30.7, 0.0WpInfo6=451, 0, 9753, 0, 0, 0.0, 13.4, 0.0WpInfo7=451, 0, 9753, 0, 0, 0.0, 70.1, 0.0WpInfo8=451, 0, 8522, 0, 0, 0.0, 17.8, 0.0WpInfo9=451, 0, 4893, 0, 0, 0.0, 37.3, 0.0WpInfo10=451, 0, 2368, 0, 0, 0.0, 26.0, 0.0WpInfo11=451, 0, 452, 0, 0, 0.0, 19.7, 0.0CountFP=1FP0=2c65c11f,099aa9de,00000000,00000000,00000000,00000000,00000000,00000000[DateTimeSeason]Day=353Year=2010Hours=8Minutes=55Seconds=20Season=Fall[Panel.1]ScreenUniCoords=0, 0, 8192, 64UndocCoords=0, 0, 0, 0Visible=TrueUndocked=FalseHiddenOn=FalseID=0ViewsOn=1[Panel.2]ScreenUniCoords=0, 0, 8192, 6144UndocCoords=0, 0, 0, 0Visible=TrueUndocked=FalseHiddenOn=FalseID=20ViewsOn=1[Panel.3]ScreenUniCoords=0, 0, 8192, 6144UndocCoords=0, 0, 0, 0Visible=FalseUndocked=FalseHiddenOn=FalseID=21ViewsOn=0[Panel.4]ScreenUniCoords=0, 0, 0, 0UndocCoords=0, 0, 0, 0Visible=FalseUndocked=FalseHiddenOn=FalseID=22ViewsOn=0[Panel.5]ScreenUniCoords=0, 0, 0, 0UndocCoords=0, 0, 0, 0Visible=FalseUndocked=FalseHiddenOn=FalseID=23ViewsOn=0[Panel.6]ScreenUniCoords=0, 0, 8192, 6144UndocCoords=0, 0, 0, 0Visible=FalseUndocked=FalseHiddenOn=FalseID=24ViewsOn=0[Panel.7]ScreenUniCoords=0, 0, 0, 0UndocCoords=0, 0, 0, 0Visible=FalseUndocked=FalseHiddenOn=FalseID=10005ViewsOn=0[Panel.8]ScreenUniCoords=5160, 1536, 3072, 4608UndocCoords=0, 0, 0, 0Visible=FalseUndocked=FalseHiddenOn=FalseID=26ViewsOn=0[Panel.9]ScreenUniCoords=4192, 2304, 4000, 3840UndocCoords=0, 0, 0, 0Visible=FalseUndocked=FalseHiddenOn=FalseID=27ViewsOn=0[Panel.12]ScreenUniCoords=0, 0, 0, 0UndocCoords=0, 0, 0, 0Visible=FalseUndocked=FalseHiddenOn=FalseID=10301ViewsOn=0[Panel.13]ScreenUniCoords=0, 0, 0, 0UndocCoords=0, 0, 0, 0Visible=FalseUndocked=FalseHiddenOn=FalseID=10302ViewsOn=0[Panel.14]ScreenUniCoords=0, 0, 0, 0UndocCoords=0, 0, 0, 0Visible=FalseUndocked=FalseHiddenOn=FalseID=10303ViewsOn=0[Panel.15]ScreenUniCoords=0, 0, 0, 0UndocCoords=0, 0, 0, 0Visible=FalseUndocked=FalseHiddenOn=FalseID=-1ViewsOn=0[Panel.16]ScreenUniCoords=0, 0, 0, 0UndocCoords=0, 0, 0, 0Visible=FalseUndocked=FalseHiddenOn=FalseID=10304ViewsOn=0[Panel.17]ScreenUniCoords=0, 0, 0, 0UndocCoords=0, 0, 0, 0Visible=FalseUndocked=FalseHiddenOn=FalseID=28ViewsOn=0[Panel.18]ScreenUniCoords=0, 0, 1984, 3392UndocCoords=0, 0, 0, 0Visible=FalseUndocked=FalseHiddenOn=FalseID=25ViewsOn=0[Panel.19]ScreenUniCoords=0, 4142, 2176, 1935UndocCoords=0, 0, 0, 0Visible=FalseUndocked=FalseHiddenOn=FalseID=122757ViewsOn=0[Panel.20]ScreenUniCoords=0, 2211, 2048, 2150UndocCoords=0, 0, 0, 0Visible=TrueUndocked=FalseHiddenOn=FalseID=-1ViewsOn=1[Gauges]Airspeed=OperativeTurnCoordinator=OperativeDG=OperativeAltimeter=OperativeAI=OperativeVSI=OperativeComm=OperativeNav=OperativeTransponder=OperativeADF=OperativeCompass=OperativePitotSystem=OperativeVacuumSystem=OperativeFuel=OperativeEngine=OperativeElectrical=OperativePanelLights=False[slew.0]Active=False[Plane.0]Aircraft=PMDG B737-800W Air Berlin[simVars.0]Latitude=N052° 21' 51.2370"Longitude=E013° 30' 21.0320"Altitude=+000162.63Pitch=0.15875806530608785Bank=0Heading=68.001037240622892PVelBodyAxis=0BVelBodyAxis=0HVelBodyAxis=0XVelBodyAxis=0YVelBodyAxis=0ZVelBodyAxis=0DynPres=0AGL=7.6330503388751652SimOnGround=TruePAccBodyAxis=-0.0087769726346631043BAccBodyAxis=7.3780375468166084e-233HAccBodyAxis=-2.232321765586308e-235XAccBodyAxis=0YAccBodyAxis=-1.2504850634787736ZAccBodyAxis=0.0034649186638154306PVelWorld=0BVelWorld=0HVelWorld=0XVelWorld=0YVelWorld=0ZVelWorld=0IceAccum=0AutoFeatherSwitch=FalseMaximumGForce=1.0949196096851774MinimumGForce=0.42923598511682021[Engine Parameters.1.0]ThrottleLeverPct=0PropellerLeverPct=0MixtureLeverPct=1Pct Engine RPM=0MaxReachedEngineRPM=0LeftMagneto=FalseRightMagneto=FalseGeneratorSwitch=FalseCowlFlapPct=0FuelPumpSwitch=FalseCarbHeat/DeiceSwitch=FalseAfterburner=False[Engine Parameters.2.0]ThrottleLeverPct=0PropellerLeverPct=0MixtureLeverPct=1Pct Engine RPM=0MaxReachedEngineRPM=0LeftMagneto=FalseRightMagneto=FalseGeneratorSwitch=FalseCowlFlapPct=0FuelPumpSwitch=FalseCarbHeat/DeiceSwitch=FalseAfterburner=False[Fuel.0]TankSelector=LeftTankSelector1=AllCenter=89.999687070274149LeftMain=95.000973110608513RightMain=95.000973110608513LeftAux=50RightAux=50LeftTip=50RightTip=50Center 2=50Center 3=50External 1=100External 2=100[Controls.0]SpoilersHandle=000.00LeftSpoiler=000.00RightSpoiler=000.00FlapsHandle=000.00LeftFlap=000.00RightFlap=000.00GearsHandle=100.00Gear1=100.00Gear2=100.00Gear3=100.00YokeY=050.00YokeX=050.00Rudder=050.00LeftBrake=100.00RightBrake=100.00ParkingBrake=100.00ElevatorTrim=050.00RudderTrim=0AileronTrim=0[systems.0]BatterySwitch=FalseAvionicsSwitch=FalseStructuralDeiceSwitch=FalsePropDeiceSwitch=FalseAutobrakes=OffStandbyVacuum=FalsePropSync=FalseFlightDirector=False[Gauges.0]KollsmanSetting=29.919628143310547[switches.0]PitotHeat=FalseBeaconLights=FalseLandingLights=FalseLogoLights=FalseNavLights=FalsePanelLights=FalseRecognitionLights=FalseStrobeLights=FalseTaxiLights=FalseWingLights=FalseCabinLights=False[Avionics.0]Comm1Active=122.950Comm1Standby=118.000Comm2Active=119.900Comm2Standby=121.700Nav1Active=113.60Nav1Standby=110.60OBS1=360Nav2Active=115.30Nav2Standby=109.60OBS2=315Transponder=1200ADFActive=353ADF2Active=281ComTransmit=1ComReceiveBoth=FalseAudioNav1Listen=FalseAudioNav2Listen=FalseAudioMarkerListen=FalseAudioDmeListen=FalseAudioAdfListen=FalseAudioAdf2Listen=False[AutoPilot.0]MasterSwitch=FalseWingLeveler=FalseNav1Lock=FalseHeadingLock=FalseHeadingValue=340AltitudeLock=FalseAltitudeValue=0AttitudeHold=FalseAirspeedHold=FalseAirspeedValue=0MachHold=FalseMachValue=0VerticalSpeedHold=FalseVerticalSpeedValue=0RPMHold=FalseRPMValue=0GlideslopeHold=FalseApproachHold=FalseBackCourseHold=FalseYawDamper=FalseToGa=FalseAutoThrottleArm=FalseGPSdrivesNAV1=FalseIsUsedForLesson=False[Payload.0]PayloadList=-1[simScheduler]SimTime=958.00463881357825[Weather]WeatherType=2[Air Traffic Control]Undocked=FalseScreenUniCoords=0, 0, 2871, 1490UndocCoords=0, 0, 0, 0[Flying Tip]Undocked=FalseScreenUniCoords=500, 400, 7192, 650UndocCoords=0, 0, 0, 0

Hi MartinCan you try starting a flight on your win7 setup in something other than the default C172, save it, and see if the new file works as it should?

I don't have my Win 7 available right now, but if memory serves you do have to Right click on a FLT file and use the "open with" option on a FLT file one time and associate it with FS9.exeThen shortcuts to FLT files should work - at least they do for me in XP and I believe the setup process (above) should be the same in Win 7.

This may not be working due to permission issues, especially if your FS is installed inside the Program Files folder.Hope this helps,

If all else fails you can try adding a "switch". To do this, make a copy of your default FS9 desktop shortcut, rename it something unique, maybe use the name of the .FLT file you're trying to open. Now do "properties" on the new shortcut and in the "Target" field add one space after ...fs9.exe" and then the following switch:/FLT:"%USERPROFILE%\My Documents\Flight Simulator Files\Previous flight.FLT"Obviously you'll need to edit the filename of the .FLT to point to your desired flight. Leave all the quotes in place.Jim

Just check that the aircraft you use for that flight is installed exactly as it was before, same livery, same name in the aircraft.cfg etc.It's not a file association problem because FS9 does actually start up, then quits. It wouldn't start up if the association was wrong.The fact that it starts up and then crashes, and loads the C172 if done the alternative way, leads me to believe it can't find the correct aircraft for the saved flight.From the .flt file:Aircraft=PMDG B737-800W Air BerlinCheck that it has exactly the same name in aircraft.cfg

Thanks for the replies. Answers to various points:1. If I save a new flight in FS9 (with any a/c), and then create a shortcut to it, double-clicking the .flt.lnk results in the error message I described, as does double-clicking on the .flt file itself.2. Makes no difference if I right-click and choose 'open with' FS93. FS9 installed on a different hard drive from the O/S4. The information in the flt file is correct as per aircraft. As in 1. above, a completely new flt file causes the error message too.5. I did not have this problem, apart from a handful of isolated flt files (out of hundreds) in Windows XP.6. The 'target' and 'open in' boxes in the Properties window of the flt files' shortcuts shows correct informationHowever, re. 6 above, if for instance the target indicated in the Properties window is, say, "E:\My Documents\Flight Simulator Files\Marseille to Nice.FLT" the error window that comes up says "The requested flight file is corrupt or can't be found" : " Documents\Flight Simulator Files\Marseille to Nice.FLT" ... missing the first part of the location of the flt file. I am not sure if this is just a truncated version of the information as displayed in the error message, or if it is looking for the file in "Documents\..." instead of "E:\My Documents....".If I move a flt file to a root folder, say E:\ the error message then says " ... can't find .. (etc. etc.) : Marseille to Nice" .. again the first part of the full location address is missing. Not sure if that is significant or just Windows'/FS9's way of truncating the message.What does work is the switch you suggested Jim (obviously changed to take into account the location of my 'My Documents' folder), so many thanks for the idea: when I double-click on any of my shortcuts now, the flight opens just fine. The only question is whether I can edit so many shortcuts - turns out I have over 2000 of them! I do have a batch file that opens the shortcut (itself, not the file it links to) in Notepad (or other text editor) but the text that opens looks odd (of course, the .lnk file not being in text format) and editing the shortcut as a txt file and returning it to a .lnk file works only half the time (better than nothing). What would be REALLY useful is a tool that edits multiple shortcut properties, but Googling this has never come up with one unfortunately.Martin

I found this, but can't make it work properly:http://fcmsoft.narod.ru/products/LinkChanger/LinkChanger.zipI can change multiple work paths ("Start in"), which is good, but not the targets, which of course are all different. Don't know if anyone would have better luck. Potentially a pretty good freeware programme though.M.

Don't have an answer to the issue of dealing with large numbers of shortcuts, but that command will also work from a batch file so a person could conceivably do a "dir" on your Flight Simulator Files folder, set each flight's filename as an environment variable, and then make a "set menu" where you could scroll through your list of flights. 2000 flights would be a rediculous amount of scrolling however. Upon selecting a flight, the command would be run, inserting the variable (flight filename) into the switch like this: /FLT:"%USERPROFILE%\My Documents\Flight Simulator Files\%selected_flight%"I thought about trying to script something like this at one time, but batch files are archaic and somebody that knew what they were doing could probably write a windows app in 10 minutes that'd do a much better job.Just an FYI, there's also a more widely known switch that lets you specify a certain fs9.cfg on startup, which can be used in conjunction with the /FLT switch. This sort of gives you the ability to have different "profiles" associated with different flights, i.e lesser display quality for IFR flights in and out of complex airports, higher display quality for VFR flights low and slow in rural areas, maybe different control sensitivities for saved heli flights, etc. There's a little more info on these switches here:http://www.cat-tamer.com/flightsim/multiple_cfgs.htmlJim

Thanks for the information Jim. I tend to use batch files still to switch fs9.cfg file etc. - works fine, but not 'the latest technology', I know. I'll have a look at the link..I have all my flt file links in separate folders, arranged by country - it was quite a neat way of starting a saved flight. I also use 'Batchrun' to launch other operations as necessary. I think the easiet thing would be for me to edit the 2000+ onks manually - if I paste the information into the properties windows it won't be THAT bad a job, and a one-off. But I will look at the scripting options first..Martin

"onks" ?? I think it should have been 'links'!