Updated base package doco for 0.8

2002-09-08 03:51:05 +00:00 · 2002-09-08 03:51:05 +00:00 · b458095c18
commit b458095c18
parent 79c612a893
30 changed files with 6114 additions and 4540 deletions
--- a/Docs/FGShortRef.html
+++ b/Docs/FGShortRef.html
@ -6,7 +6,7 @@
 <meta name="generator" content="TeX4ht (http://www.cis.ohio-state.edu/~gurari/TeX4ht/mn.html)"> 
 <!-- html --> 
 <meta name="src" content="FGShortRef.tex"> 
-<meta name="date" content="2002-02-14 12:10:00"> 
+<meta name="date" content="2002-09-08 00:45:00"> 
 <link rel="stylesheet" type="text/css" href="FGShortRef.css"> 
 </head><body 
 >
@ -81,28 +81,28 @@ class="ptmr7t---70">Action                                     </span></td>
 class="hline"><td><hr></td><td><hr></td></tr><tr  
 valign="baseline" id="TBL-3-2-"><td  align="left" nowrap="nowrap" id="TBL-3-2-1"  
 class="td11"> <span 
-class="ptmr7t---70">Pg Up/Pg Dn                  </span></td><td  align="left" nowrap="nowrap" id="TBL-3-2-2"  
+class="ptmr7t---70">9/3 </span></td><td  align="left" nowrap="nowrap" id="TBL-3-2-2"  
 class="td11"> <span 
 class="ptmr7t---70">Throttle</span><a 
  name="dx1-2"></a>                                   </td>
 </tr><tr  
 valign="baseline" id="TBL-3-3-"><td  align="left" nowrap="nowrap" id="TBL-3-3-1"  
 class="td11"> <span 
-class="ptmr7t---70">Left Arrow/Right Arrow</span></td><td  align="left" nowrap="nowrap" id="TBL-3-3-2"  
+class="ptmr7t---70">4/6 </span></td><td  align="left" nowrap="nowrap" id="TBL-3-3-2"  
 class="td11"> <span 
 class="ptmr7t---70">Aileron</span><a 
  name="dx1-3"></a>                                    </td>
 </tr><tr  
 valign="baseline" id="TBL-3-4-"><td  align="left" nowrap="nowrap" id="TBL-3-4-1"  
 class="td11"> <span 
-class="ptmr7t---70">Up Arrow/Down Arrow </span></td><td  align="left" nowrap="nowrap" id="TBL-3-4-2"  
+class="ptmr7t---70">8/2 </span></td><td  align="left" nowrap="nowrap" id="TBL-3-4-2"  
 class="td11"> <span 
 class="ptmr7t---70">Elevator</span><a 
  name="dx1-4"></a>                                   </td>
 </tr><tr  
 valign="baseline" id="TBL-3-5-"><td  align="left" nowrap="nowrap" id="TBL-3-5-1"  
 class="td11"> <span 
-class="ptmr7t---70">Ins/Enter                         </span></td><td  align="left" nowrap="nowrap" id="TBL-3-5-2"  
+class="ptmr7t---70">0/,  </span></td><td  align="left" nowrap="nowrap" id="TBL-3-5-2"  
 class="td11"> <span 
 class="ptmr7t---70">Rudder</span><a 
  name="dx1-5"></a>                                    </td>
@ -115,7 +115,7 @@ class="ptmr7t---70">Center aileron/elevator/rudder</span></td>
 </tr><tr  
 valign="baseline" id="TBL-3-7-"><td  align="left" nowrap="nowrap" id="TBL-3-7-1"  
 class="td11"> <span 
-class="ptmr7t---70">Home/End                      </span></td><td  align="left" nowrap="nowrap" id="TBL-3-7-2"  
+class="ptmr7t---70">7/1 </span></td><td  align="left" nowrap="nowrap" id="TBL-3-7-2"  
 class="td11"> <span 
 class="ptmr7t---70">Elevator trim</span><a 
  name="dx1-6"></a>                           </td>
@ -225,53 +225,56 @@ class="ptmr7t---70">on/off                   </span></td>
 </tr><tr  
 valign="baseline" id="TBL-5-3-"><td  align="left" nowrap="nowrap" id="TBL-5-3-1"  
 class="td11"> <span 
-class="ptmr7t---70">s                 </span></td><td  align="left" nowrap="nowrap" id="TBL-5-3-2"  
+class="ptmr7t---70">c                 </span></td><td  align="left" nowrap="nowrap" id="TBL-5-3-2"  
 class="td11"> <span 
-class="ptmr7t---70">Cycle panel style full/mini                          </span></td>
+class="ptmr7t---70">Toggle3D/2D cockpit</span> <a 
  name="dx1-9"></a><span 
 class="ptmr7t---70">(if both are available)</span> <a 
  name="dx1-10"></a><a 
  name="dx1-11"></a></td>
 </tr><tr  
 valign="baseline" id="TBL-5-4-"><td  align="left" nowrap="nowrap" id="TBL-5-4-1"  
 class="td11"> <span 
-class="ptmr7t---70">Shift-F5/F6</span></td><td  align="left" nowrap="nowrap" id="TBL-5-4-2"  
+class="ptmr7t---70">s                 </span></td><td  align="left" nowrap="nowrap" id="TBL-5-4-2"  
 class="td11"> <span 
-class="ptmr7t---70">Shift the panel in y direction                       </span></td>
+class="ptmr7t---70">Cycle panel style full/mini                            </span></td>
 </tr><tr  
 valign="baseline" id="TBL-5-5-"><td  align="left" nowrap="nowrap" id="TBL-5-5-1"  
 class="td11"> <span 
-class="ptmr7t---70">Shift-F7/F8</span></td><td  align="left" nowrap="nowrap" id="TBL-5-5-2"  
+class="ptmr7t---70">Shift-F5/F6</span></td><td  align="left" nowrap="nowrap" id="TBL-5-5-2"  
 class="td11"> <span 
-class="ptmr7t---70">Shift the panel in x direction                       </span></td>
+class="ptmr7t---70">Shift the panel in y direction                         </span></td>
 </tr><tr  
 valign="baseline" id="TBL-5-6-"><td  align="left" nowrap="nowrap" id="TBL-5-6-1"  
 class="td11"> <span 
-class="ptmr7t---70">Shift-F3     </span></td><td  align="left" nowrap="nowrap" id="TBL-5-6-2"  
+class="ptmr7t---70">Shift-F7/F8</span></td><td  align="left" nowrap="nowrap" id="TBL-5-6-2"  
 class="td11"> <span 
-class="ptmr7t---70">Read a panel from a property list                </span></td>
+class="ptmr7t---70">Shift the panel in x direction                         </span></td>
 </tr><tr  
 valign="baseline" id="TBL-5-7-"><td  align="left" nowrap="nowrap" id="TBL-5-7-1"  
 class="td11"> <span 
-class="ptmr7t---70">i/I               </span></td><td  align="left" nowrap="nowrap" id="TBL-5-7-2"  
+class="ptmr7t---70">Shift-F3     </span></td><td  align="left" nowrap="nowrap" id="TBL-5-7-2"  
 class="td11"> <span 
-class="ptmr7t---70">Minimize/maximize HUD                          </span></td>
+class="ptmr7t---70">Read a panel from a property list                  </span></td>
 </tr><tr  
 valign="baseline" id="TBL-5-8-"><td  align="left" nowrap="nowrap" id="TBL-5-8-1"  
 class="td11"> <span 
-class="ptmr7t---70">h/H             </span></td><td  align="left" nowrap="nowrap" id="TBL-5-8-2"  
+class="ptmr7t---70">i/I               </span></td><td  align="left" nowrap="nowrap" id="TBL-5-8-2"  
 class="td11"> <span 
 class="ptmr7t---70">Minimize/maximize HUD                             </span></td>
 </tr><tr  
 valign="baseline" id="TBL-5-9-"><td  align="left" nowrap="nowrap" id="TBL-5-9-1"  
 class="td11"> <span 
 class="ptmr7t---70">h/H             </span></td><td  align="left" nowrap="nowrap" id="TBL-5-9-2"  
 class="td11"> <span 
 class="ptmr7t---70">Change color of HUD/toggle HUD off         </span></td>
 </tr><tr  
-valign="baseline" id="TBL-5-9-"><td  align="left" nowrap="nowrap" id="TBL-5-9-1"  
+valign="baseline" id="TBL-5-10-"><td  align="left" nowrap="nowrap" id="TBL-5-10-1"  
-class="td11">                    </td><td  align="left" nowrap="nowrap" id="TBL-5-9-2"  
+class="td11">                    </td><td  align="left" nowrap="nowrap" id="TBL-5-10-2"  
 class="td11"> <span 
 class="ptmr7t---70">forward/backward                                          </span></td>
 </tr><tr 
 class="hline"><td><hr></td><td><hr></td></tr><tr  
 valign="baseline" id="TBL-5-10-"><td  align="left" nowrap="nowrap" id="TBL-5-10-1"  
 class="td11"> <span 
 class="ptmr7t---70">Ctrl + O/P  </span></td><td  align="left" nowrap="nowrap" id="TBL-5-10-2"  
 class="td11"> <span 
 class="ptmr7t---70">Tilt view down/up</span> <a 
  name="dx1-9"></a>                                      </td>
 </tr><tr  
 valign="baseline" id="TBL-5-11-"><td  align="left" nowrap="nowrap" id="TBL-5-11-1"  
 class="td11"> <span 
 class="ptmr7t---70">x/X             </span></td><td  align="left" nowrap="nowrap" id="TBL-5-11-2"  
@ -283,7 +286,8 @@ class="td11"> <span
 class="ptmr7t---70">v                 </span></td><td  align="left" nowrap="nowrap" id="TBL-5-12-2"  
 class="td11"> <span 
 class="ptmr7t---70">Cycle view modes</span><a 
-  name="dx1-10"></a>                                       </td>
+  name="dx1-12"></a> <span 
 class="ptmr7t---70">(pilot, chase, tower)         </span></td>
 </tr><tr 
 class="hline"><td><hr></td><td><hr></td></tr><tr  
 valign="baseline" id="TBL-5-13-"><td  align="left" nowrap="nowrap" id="TBL-5-13-1"  
@ -291,7 +295,7 @@ class="td11"> <span
 class="ptmr7t---70">W               </span></td><td  align="left" nowrap="nowrap" id="TBL-5-13-2"  
 class="td11"> <span 
 class="ptmr7t---70">Toggle full screen mode</span><a 
-  name="dx1-11"></a> <span 
+  name="dx1-13"></a> <span 
 class="ptmr7t---70">on/off (3dfx only)   </span></td>
 </tr><tr  
 valign="baseline" id="TBL-5-14-"><td  align="left" nowrap="nowrap" id="TBL-5-14-1"  
@ -299,7 +303,7 @@ class="td11"> <span
 class="ptmr7t---70">z/Z             </span></td><td  align="left" nowrap="nowrap" id="TBL-5-14-2"  
 class="td11"> <span 
 class="ptmr7t---70">Change visibility</span><a 
-  name="dx1-12"></a> <span 
+  name="dx1-14"></a> <span 
 class="ptmr7t---70">(fog) forward/backward    </span></td>
 </tr><tr  
 valign="baseline" id="TBL-5-15-"><td  align="left" nowrap="nowrap" id="TBL-5-15-1"  
@ -337,10 +341,10 @@ valign="baseline" id="TBL-5-20-"><td  align="left" nowrap="nowrap" id="TBL-5-20-
 class="td11">                    </td>
   </tr><!--|l|l|--></table>
 </div>
-<!--l. 106--><p class="noindent">                                     <!--l. 109--><p class="noindent"><span 
+<!--l. 106--><p class="noindent">
 <!--l. 109--><p class="noindent"><span 
 class="ptmr7t---70">Tab. 4: </span><span 
-class="ptmri7t---70">Autopilot and related controls.</span>
+class="ptmri7t---70">Autopilot and related controls.</span>                 <!--l. 113--><p class="noindent"><!--tex4ht:inline--><div class="tabular"><table class="tabular" 
   <!--l. 113--><p class="noindent"><!--tex4ht:inline--><div class="tabular"><table class="tabular" 
 cellspacing="0pt" cellpadding="0" rules="groups" 
 frame="border" id="TBL-6-" ><colgroup id="TBL-6-1g"><col 
 id="TBL-6-1"></colgroup><colgroup id="TBL-6-2g"><col 
@ -358,7 +362,7 @@ class="td11"> <span
 class="ptmr7t---70">Ctrl + A</span></td><td  align="left" nowrap="nowrap" id="TBL-6-2-2"  
 class="td11"> <span 
 class="ptmr7t---70">Altitude hold</span><a 
-  name="dx1-13"></a> <span 
+  name="dx1-15"></a> <span 
 class="ptmr7t---70">toggle on/off                        </span></td>
 </tr><tr  
 valign="baseline" id="TBL-6-3-"><td  align="left" nowrap="nowrap" id="TBL-6-3-1"  
@ -372,7 +376,7 @@ class="td11"> <span
 class="ptmr7t---70">Ctrl + H</span></td><td  align="left" nowrap="nowrap" id="TBL-6-4-2"  
 class="td11"> <span 
 class="ptmr7t---70">Heading hold</span><a 
-  name="dx1-14"></a> <span 
+  name="dx1-16"></a> <span 
 class="ptmr7t---70">toggle on/off                        </span></td>
 </tr><tr  
 valign="baseline" id="TBL-6-5-"><td  align="left" nowrap="nowrap" id="TBL-6-5-1"  
@ -386,7 +390,7 @@ class="td11"> <span
 class="ptmr7t---70">Ctrl + S </span></td><td  align="left" nowrap="nowrap" id="TBL-6-6-2"  
 class="td11"> <span 
 class="ptmr7t---70">Autothrottle</span><a 
-  name="dx1-15"></a> <span 
+  name="dx1-17"></a> <span 
 class="ptmr7t---70">toggle on/off                          </span></td>
 </tr><tr  
 valign="baseline" id="TBL-6-7-"><td  align="left" nowrap="nowrap" id="TBL-6-7-1"  
@ -403,29 +407,35 @@ class="ptmr7t---70">Add 1000 ft. to your altitude (emergency)</span></td>
 </tr><tr  
 valign="baseline" id="TBL-6-9-"><td  align="left" nowrap="nowrap" id="TBL-6-9-1"  
 class="td11"> <span 
-class="ptmr7t---70">F6         </span></td><td  align="left" nowrap="nowrap" id="TBL-6-9-2"  
+class="ptmr7t---70">Enter     </span></td><td  align="left" nowrap="nowrap" id="TBL-6-9-2"  
 class="td11"> <span 
 class="ptmr7t---70">Increase autopilot heading                         </span></td>
 </tr><tr  
 valign="baseline" id="TBL-6-10-"><td  align="left" nowrap="nowrap" id="TBL-6-10-1"  
 class="td11"> <span 
 class="ptmr7t---70">F6         </span></td><td  align="left" nowrap="nowrap" id="TBL-6-10-2"  
 class="td11"> <span 
 class="ptmr7t---70">Toggle autopilot target:                             </span></td>
 </tr><tr  
-valign="baseline" id="TBL-6-10-"><td  align="left" nowrap="nowrap" id="TBL-6-10-1"  
+valign="baseline" id="TBL-6-11-"><td  align="left" nowrap="nowrap" id="TBL-6-11-1"  
-class="td11">              </td><td  align="left" nowrap="nowrap" id="TBL-6-10-2"  
+class="td11">              </td><td  align="left" nowrap="nowrap" id="TBL-6-11-2"  
 class="td11"> <span 
 class="ptmr7t---70">current heading/waypoint                          </span></td>
 </tr><tr  
-valign="baseline" id="TBL-6-11-"><td  align="left" nowrap="nowrap" id="TBL-6-11-1"  
+valign="baseline" id="TBL-6-12-"><td  align="left" nowrap="nowrap" id="TBL-6-12-1"  
 class="td11"> <span 
-class="ptmr7t---70">F11       </span></td><td  align="left" nowrap="nowrap" id="TBL-6-11-2"  
+class="ptmr7t---70">F11       </span></td><td  align="left" nowrap="nowrap" id="TBL-6-12-2"  
 class="td11"> <span 
 class="ptmr7t---70">Autopilot altitude dialog                            </span></td>
 </tr><tr  
-valign="baseline" id="TBL-6-12-"><td  align="left" nowrap="nowrap" id="TBL-6-12-1"  
+valign="baseline" id="TBL-6-13-"><td  align="left" nowrap="nowrap" id="TBL-6-13-1"  
 class="td11"> <span 
-class="ptmr7t---70">F12       </span></td><td  align="left" nowrap="nowrap" id="TBL-6-12-2"  
+class="ptmr7t---70">F12       </span></td><td  align="left" nowrap="nowrap" id="TBL-6-13-2"  
 class="td11"> <span 
 class="ptmr7t---70">Autopilot heading dialog                           </span></td>
 </tr><tr 
 class="hline"><td><hr></td><td><hr></td></tr><tr  
-valign="baseline" id="TBL-6-13-"><td  align="left" nowrap="nowrap" id="TBL-6-13-1"  
+valign="baseline" id="TBL-6-14-"><td  align="left" nowrap="nowrap" id="TBL-6-14-1"  
 class="td11">              </td> </tr><!--|l|l|--></table> </div>
   <!--l. 118--><p class="noindent"><span 
 class="ptmr7t---70">Tab. 5: </span><span 
@ -459,7 +469,7 @@ valign="baseline" id="TBL-7-4-"><td  align="left" nowrap="nowrap" id="TBL-7-4-1"
 class="td11"> <span 
 class="ptmr7t---70">9 / 3</span></td><td  align="left" nowrap="nowrap" id="TBL-7-4-2"  
 class="td11"> <span 
-class="ptmr7t---70">Auto Throttle adjust</span></td>
+class="ptmr7t---70">Autothrottle adjust</span></td>
 </tr><tr 
 class="hline"><td><hr></td><td><hr></td></tr><tr  
 valign="baseline" id="TBL-7-5-"><td  align="left" nowrap="nowrap" id="TBL-7-5-1"  
@ -552,8 +562,8 @@ class="td11"> <span
 class="ptmr7t---70">B             </span></td><td  align="left" nowrap="nowrap" id="TBL-9-2-2"  
 class="td11"> <span 
 class="ptmr7t---70">Toggle parking brake</span> <a 
-  name="dx1-16"></a><a 
+  name="dx1-18"></a><a 
-  name="dx1-17"></a> <span 
+  name="dx1-19"></a> <span 
 class="ptmr7t---70">on/off                                             </span></td>
 </tr><tr  
 valign="baseline" id="TBL-9-3-"><td  align="left" nowrap="nowrap" id="TBL-9-3-1"  
@ -561,22 +571,22 @@ class="td11"> <span
 class="ptmr7t---70">b             </span></td><td  align="left" nowrap="nowrap" id="TBL-9-3-2"  
 class="td11"> <span 
 class="ptmr7t---70">Apply/release all brakes</span><a 
-  name="dx1-18"></a>                                                     </td>
+  name="dx1-20"></a>                                                     </td>
 </tr><tr  
 valign="baseline" id="TBL-9-4-"><td  align="left" nowrap="nowrap" id="TBL-9-4-1"  
 class="td11"> <span 
 class="ptmr7t---70">g             </span></td><td  align="left" nowrap="nowrap" id="TBL-9-4-2"  
 class="td11"> <span 
 class="ptmr7t---70">Toggle landing gear down</span> <a 
-  name="dx1-19"></a><a 
+  name="dx1-21"></a><a 
-  name="dx1-20"></a>                                                 </td>
+  name="dx1-22"></a>                                                 </td>
 </tr><tr  
 valign="baseline" id="TBL-9-5-"><td  align="left" nowrap="nowrap" id="TBL-9-5-1"  
 class="td11"> <span 
 class="ptmr7t---70">,              </span></td><td  align="left" nowrap="nowrap" id="TBL-9-5-2"  
 class="td11"> <span 
 class="ptmr7t---70">Left gear brake (useful for differential braking</span><a 
-  name="dx1-21"></a><span 
+  name="dx1-23"></a><span 
 class="ptmr7t---70">)                </span></td>
 </tr><tr  
 valign="baseline" id="TBL-9-6-"><td  align="left" nowrap="nowrap" id="TBL-9-6-1"  
@ -584,91 +594,99 @@ class="td11"> <span
 class="ptmr7t---70">.              </span></td><td  align="left" nowrap="nowrap" id="TBL-9-6-2"  
 class="td11"> <span 
 class="ptmr7t---70">Right gear brake (useful for differential braking</span><a 
-  name="dx1-22"></a><span 
+  name="dx1-24"></a><span 
 class="ptmr7t---70">)              </span></td>
 </tr><tr  
 valign="baseline" id="TBL-9-7-"><td  align="left" nowrap="nowrap" id="TBL-9-7-1"  
 class="td11"> <span 
-class="cmr-7">]</span><span 
+class="ptmr7t---70">l              </span></td><td  align="left" nowrap="nowrap" id="TBL-9-7-2"  
 class="ptmr7t---70">/</span><span 
 class="cmr-7">[        </span></td><td  align="left" nowrap="nowrap" id="TBL-9-7-2"  
 class="td11"> <span 
-class="ptmr7t---70">Extend/Retract flaps</span><a 
+class="ptmr7t---70">Toggle tail-wheel lock</span><a 
-  name="dx1-23"></a>                                                           </td>
+  name="dx1-25"></a><span 
 class="ptmr7t---70">)                                                      </span></td>
 </tr><tr  
 class="hline"><td><hr></td><td><hr></td></tr><tr  
 valign="baseline" id="TBL-9-8-"><td  align="left" nowrap="nowrap" id="TBL-9-8-1"  
 class="td11"> <span 
-class="ptmr7t---70">p             </span></td><td  align="left" nowrap="nowrap" id="TBL-9-8-2"  
+class="cmr-7">]</span><span 
 class="ptmr7t---70">/</span><span 
 class="cmr-7">[        </span></td><td  align="left" nowrap="nowrap" id="TBL-9-8-2"  
 class="td11"> <span 
-class="ptmr7t---70">Toggle pause</span><a 
+class="ptmr7t---70">Extend/Retract flaps</span><a 
-  name="dx1-24"></a> <span 
+  name="dx1-26"></a>                                                           </td>
 class="ptmr7t---70">on/off                                                           </span></td>
 </tr><tr 
 class="hline"><td><hr></td><td><hr></td></tr><tr  
 valign="baseline" id="TBL-9-9-"><td  align="left" nowrap="nowrap" id="TBL-9-9-1"  
 class="td11"> <span 
-class="ptmr7t---70">a/A          </span></td><td  align="left" nowrap="nowrap" id="TBL-9-9-2"  
+class="ptmr7t---70">p             </span></td><td  align="left" nowrap="nowrap" id="TBL-9-9-2"  
 class="td11"> <span 
-class="ptmr7t---70">Speed up/slow down (time acceleration)                           </span></td>
+class="ptmr7t---70">Toggle pause</span><a 
  name="dx1-27"></a> <span 
 class="ptmr7t---70">on/off                                                           </span></td>
 </tr><tr  
 valign="baseline" id="TBL-9-10-"><td  align="left" nowrap="nowrap" id="TBL-9-10-1"  
 class="td11"> <span 
-class="ptmr7t---70">t/T           </span></td><td  align="left" nowrap="nowrap" id="TBL-9-10-2"  
+class="ptmr7t---70">a/A          </span></td><td  align="left" nowrap="nowrap" id="TBL-9-10-2"  
 class="td11"> <span 
-class="ptmr7t---70">Time speed up/slow down                                                 </span></td>
+class="ptmr7t---70">Speed up/slow down (time acceleration)                           </span></td>
 </tr><tr  
 valign="baseline" id="TBL-9-11-"><td  align="left" nowrap="nowrap" id="TBL-9-11-1"  
 class="td11"> <span 
-class="ptmr7t---70">m/M        </span></td><td  align="left" nowrap="nowrap" id="TBL-9-11-2"  
+class="ptmr7t---70">t/T           </span></td><td  align="left" nowrap="nowrap" id="TBL-9-11-2"  
 class="td11"> <span 
 class="ptmr7t---70">Time speed up/slow down                                                 </span></td>
 </tr><tr  
 valign="baseline" id="TBL-9-12-"><td  align="left" nowrap="nowrap" id="TBL-9-12-1"  
 class="td11"> <span 
 class="ptmr7t---70">m/M        </span></td><td  align="left" nowrap="nowrap" id="TBL-9-12-2"  
 class="td11"> <span 
 class="ptmr7t---70">Change time offset</span><a 
-  name="dx1-25"></a> <span 
+  name="dx1-28"></a> <span 
 class="ptmr7t---70">(warp) used by t/T forward/backward</span></td>
 </tr><tr 
 class="hline"><td><hr></td><td><hr></td></tr><tr  
-valign="baseline" id="TBL-9-12-"><td  align="left" nowrap="nowrap" id="TBL-9-12-1"  
+valign="baseline" id="TBL-9-13-"><td  align="left" nowrap="nowrap" id="TBL-9-13-1"  
 class="td11"> <span 
-class="ptmr7t---70">Shift-F2  </span></td><td  align="left" nowrap="nowrap" id="TBL-9-12-2"  
+class="ptmr7t---70">Shift-F2  </span></td><td  align="left" nowrap="nowrap" id="TBL-9-13-2"  
 class="td11"> <span 
 class="ptmr7t---70">Save current flight to </span><span 
 class="pcrr7t---70">fgfs.sav                </span></td>
 </tr><tr  
-valign="baseline" id="TBL-9-13-"><td  align="left" nowrap="nowrap" id="TBL-9-13-1"  
+valign="baseline" id="TBL-9-14-"><td  align="left" nowrap="nowrap" id="TBL-9-14-1"  
 class="td11"> <span 
-class="ptmr7t---70">Shift-F1  </span></td><td  align="left" nowrap="nowrap" id="TBL-9-13-2"  
+class="ptmr7t---70">Shift-F1  </span></td><td  align="left" nowrap="nowrap" id="TBL-9-14-2"  
 class="td11"> <span 
 class="ptmr7t---70">Restore flight from </span><span 
 class="pcrr7t---70">fgfs.sav                 </span></td>
 </tr><tr  
-valign="baseline" id="TBL-9-14-"><td  align="left" nowrap="nowrap" id="TBL-9-14-1"  
+valign="baseline" id="TBL-9-15-"><td  align="left" nowrap="nowrap" id="TBL-9-15-1"  
 class="td11"> <span 
-class="ptmr7t---70">F3           </span></td><td  align="left" nowrap="nowrap" id="TBL-9-14-2"  
+class="ptmr7t---70">F3           </span></td><td  align="left" nowrap="nowrap" id="TBL-9-15-2"  
 class="td11"> <span 
 class="ptmr7t---70">Save screen shot under </span><span 
 class="pcrr7t---70">fgfs-screen.ppm       </span></td>
 </tr><tr  
-valign="baseline" id="TBL-9-15-"><td  align="left" nowrap="nowrap" id="TBL-9-15-1"  
+valign="baseline" id="TBL-9-16-"><td  align="left" nowrap="nowrap" id="TBL-9-16-1"  
 class="td11"> <span 
-class="ptmr7t---70">Shift-F4  </span></td><td  align="left" nowrap="nowrap" id="TBL-9-15-2"  
+class="ptmr7t---70">Shift-F4  </span></td><td  align="left" nowrap="nowrap" id="TBL-9-16-2"  
 class="td11"> <span 
 class="ptmr7t---70">Re-read global preferences from </span><span 
 class="pcrr7t---70">preferences.xml </span></td>
 </tr><tr  
-valign="baseline" id="TBL-9-16-"><td  align="left" nowrap="nowrap" id="TBL-9-16-1"  
+valign="baseline" id="TBL-9-17-"><td  align="left" nowrap="nowrap" id="TBL-9-17-1"  
 class="td11"> <span 
-class="ptmr7t---70">Shift-F10</span></td><td  align="left" nowrap="nowrap" id="TBL-9-16-2"  
+class="ptmr7t---70">Shift-F10</span></td><td  align="left" nowrap="nowrap" id="TBL-9-17-2"  
 class="td11"> <span 
 class="ptmr7t---70">Toggle data logging of FDM on/off                                   </span></td>
 </tr><tr 
 class="hline"><td><hr></td><td><hr></td></tr><tr  
-valign="baseline" id="TBL-9-17-"><td  align="left" nowrap="nowrap" id="TBL-9-17-1"  
+valign="baseline" id="TBL-9-18-"><td  align="left" nowrap="nowrap" id="TBL-9-18-1"  
 class="td11"> <span 
-class="ptmr7t---70">ESC        </span></td><td  align="left" nowrap="nowrap" id="TBL-9-17-2"  
+class="ptmr7t---70">ESC        </span></td><td  align="left" nowrap="nowrap" id="TBL-9-18-2"  
 class="td11"> <span 
 class="ptmr7t---70">Exit program                                                                      </span></td>
 </tr><tr 
 class="hline"><td><hr></td><td><hr></td></tr><tr  
-valign="baseline" id="TBL-9-18-"><td  align="left" nowrap="nowrap" id="TBL-9-18-1"  
+valign="baseline" id="TBL-9-19-"><td  align="left" nowrap="nowrap" id="TBL-9-19-1"  
 class="td11">                </td> </tr><!--|l|l|--></table> </div>
 <!--l. 148--><p class="noindent"><span 
 class="ptmb7t---70">Mouse controlled functions: </span><span 
@ -697,7 +715,7 @@ class="ptmr7t---70">Right clicking the mouse once more resets it into the initia
 <!--l. 169--><p class="noindent"><span 
 class="ptmr7t---70">Short Reference by M. Basler (pmb@epost.de) for </span><span 
 class="ptmbi7t---70">FlightGear </span><span 
-class="ptmr7t---70">version 0.7.9.</span>
+class="ptmr7t---70">version 0.8.0.</span>
 <br class="newline"><span 
 class="ptmr7t---70">Published under the GPL (</span><a 
 href="http://www.gnu.org/copyleft/gpl.html" ><span 
--- a/Docs/FGShortRef.pdf
+++ b/Docs/FGShortRef.pdf
--- a/Docs/InstallGuide/html/getstart.html
+++ b/Docs/InstallGuide/html/getstart.html
@ -6,7 +6,7 @@
 <meta name="generator" content="TeX4ht (http://www.cis.ohio-state.edu/~gurari/TeX4ht/mn.html)"> 
 <!-- html,2,info,next,sections+ --> 
 <meta name="src" content="getstart.tex"> 
-<meta name="date" content="2002-02-16 19:41:00"> 
+<meta name="date" content="2002-09-08 00:44:00"> 
 <link rel="stylesheet" type="text/css" href="getstart.css"> 
 </head><body 
 >
@ -34,39 +34,46 @@ class="ptmr7t---120">)</span>
 <br>                          <span 
 class="ptmr7t---120">including contributions by</span>
 <br> <span 
-class="ptmr7t---120">Bernhard Buckel (</span><a 
+class="ptmr7t---120">Jon Berndt (</span><a 
 href="mailto:jsb@hal-pc.org" ><span 
 class="ptmr7t---120">jsb@hal-pc.org</span></a><span 
 class="ptmr7t---120">), Bernhard Buckel (</span><a 
 href="mailto:buckel@mail.uni-wuerzburg.de" ><span 
 class="ptmr7t---120">buckel@mail.uni-wuerzburg.de</span></a><span 
 class="ptmr7t---120">),</span>
 <br> <span 
-class="ptmr7t---120">Curt Olson (</span><a 
+class="ptmr7t---120">Cameron Moore (</span><a 
 href="mailto:cameron@unbeatenpath.net" ><span 
 class="ptmr7t---120">cameron@unbeatenpath.net</span></a><span 
 class="ptmr7t---120">), Curt Olson (</span><a 
 href="mailto:curt@flightgear.org" ><span 
 class="ptmr7t---120">curt@flightgear.org</span></a><span 
 class="ptmr7t---120">),</span>
 <br>   <span 
-class="ptmr7t---120">Jon Berndt (</span><a 
+class="ptmr7t---120">Dave Perry (</span><a 
-href="mailto:jsb@hal-pc.org" ><span 
+href="mailto:skidavem@mindspring.com" ><span 
-class="ptmr7t---120">jsb@hal-pc.org</span></a><span 
+class="ptmr7t---120">skidavem@mindspring.com</span></a><span 
 class="ptmr7t---120">), Michael Selig (</span><a 
 href="mailto:m-selig@uiuc.edu" ><span 
 class="ptmr7t---120">m-selig@uiuc.edu</span></a><span 
 class="ptmr7t---120">),</span>
 <br>                <span 
-class="ptmr7t---120">Darrell Walisser </span><a 
+class="ptmr7t---120">Darrell Walisser (</span><a 
-href="mailto:dwaliss1@purdue.edu" ><span 
+href="mailto:walisser@mac.com" ><span 
-class="ptmr7t---120">dwaliss1@purdue.edu</span></a><span 
+class="ptmr7t---120">walisser@mac.com</span></a><span 
-class="ptmr7t---120">,</span>
+class="ptmr7t---120">), and others</span>
 <br>                                  <span 
 class="ptmr7t---120">and others</span>
 <br>     <div align="center" 
 class="centerline"><img 
 src="getstart0x.gif" alt=""  class="fbox" > </div></div>
 <br>
 <div class="date" align="center"><span 
-class="ptmr7t---120">Getting Started version 0.51</span><br>
+class="ptmr7t---120">Getting Started Version 0.6</span><br>
 <span 
-class="ptmr7t---120">February, 16th, 2002</span><br>
+class="ptmr7t---120">September, 9th, 2002</span><br>
 <span 
-class="ptmr7t---120">This documentation was written for </span><span 
+class="ptmr7t---120">Manual was written for </span><span 
 class="ptmbi7t---120">FlightGear </span><span 
-class="ptmr7t---120">version 0.7.9.</span></div>
+class="ptmr7t---120">version 0.8.0.</span></div>
@ -85,121 +92,129 @@ href="getstartpa1.html#x4-3000I" name="QQ2-4-3">Installation</a></span>
 href="getstartch1.html#x5-40001" name="QQ2-5-4">Want to have a free flight? Take <span 
 class="ptmbi7t---109">FlightGear</span>!</a></span>
 <br>   &nbsp;<span class="sectionToc">1.1 <a 
-href="getstartch1.html#x5-50001.1" name="QQ2-5-5">Yet another Flight Simulator?</a></span>
+href="getstartch1.html#x5-50001.1" name="QQ2-5-5">Yet Another Flight Simulator?</a></span>
 <br>   &nbsp;<span class="sectionToc">1.2 <a 
-href="getstartch1.html#x5-60001.2" name="QQ2-5-6">System requirements</a></span>
+href="getstartch1.html#x5-60001.2" name="QQ2-5-6">System Requirements</a></span>
 <br>   &nbsp;<span class="sectionToc">1.3 <a 
-href="getstartch1.html#x5-70001.3" name="QQ2-5-7">Which version should I use?</a></span>
+href="getstartch1.html#x5-70001.3" name="QQ2-5-7">Choosing A Version</a></span>
 <br>   &nbsp;<span class="sectionToc">1.4 <a 
-href="getstartch1.html#x5-80001.4" name="QQ2-5-8">Flight models</a></span>
+href="getstartch1.html#x5-80001.4" name="QQ2-5-8">Flight Dynamics Models</a></span>
 <br>   &nbsp;<span class="sectionToc">1.5 <a 
-href="getstartch1.html#x5-90001.5" name="QQ2-5-9">To whom this guide is addressed and how it is organized</a></span>
+href="getstartch1.html#x5-90001.5" name="QQ2-5-9">About This Guide</a></span>
 <br>   <span class="chapterToc">2 <a 
 href="getstartch2.html#x6-100002" name="QQ2-6-10">Building the plane: Compiling the program</a></span>
 <br>   &nbsp;<span class="sectionToc">2.1 <a 
-href="getstartch2.html#x6-110002.1" name="QQ2-6-11">Getting a development environment under Windows</a></span>
+href="getstartch2.html#x6-110002.1" name="QQ2-6-11">Preparing the development environment under Windows</a></span>
 <br>   &nbsp;<span class="sectionToc">2.2 <a 
-href="getstartch2.html#x6-120002.2" name="QQ2-6-12">Compiling <span 
+href="getstartch2.html#x6-120002.2" name="QQ2-6-12">Preparing the development environment under Windows</a></span>
 class="ptmbi7t---109">FlightGear </span>under Linux/Windows </a></span>
 <br>   &nbsp;<span class="sectionToc">2.3 <a 
-href="getstartch2.html#x6-130002.3" name="QQ2-6-13">Compiling <span 
+href="getstartch2.html#x6-130002.3" name="QQ2-6-13">One-time preparations for Linux and Windows users</a></span>
 class="ptmbi7t---109">FlightGear </span>under Mac OS 10.1 </a></span>
 <br>   &nbsp;<span class="sectionToc">2.4 <a 
-href="getstartch2.html#x6-140002.4" name="QQ2-6-14">Compiling on other systems</a></span>
+href="getstartch2.html#x6-160002.4" name="QQ2-6-16">Compiling <span 
 class="ptmbi7t---109">FlightGear </span>under Linux/Windows </a></span>
 <br>   &nbsp;<span class="sectionToc">2.5 <a 
-href="getstartch2.html#x6-150002.5" name="QQ2-6-15">Installing the base package</a></span>
+href="getstartch2.html#x6-170002.5" name="QQ2-6-17">Compiling <span 
 class="ptmbi7t---109">FlightGear </span>under Mac OS X </a></span>
 <br>   &nbsp;<span class="sectionToc">2.6 <a 
-href="getstartch2.html#x6-160002.6" name="QQ2-6-16">For test pilots only: Building the CVS snapshots</a></span>
+href="getstartch2.html#x6-180002.6" name="QQ2-6-18">Compiling on other systems</a></span>
 <br>   &nbsp;<span class="sectionToc">2.7 <a 
 href="getstartch2.html#x6-190002.7" name="QQ2-6-19">Installing the base package</a></span>
 <br>   &nbsp;<span class="sectionToc">2.8 <a 
 href="getstartch2.html#x6-200002.8" name="QQ2-6-20">For test pilots only: Building the CVS snapshots</a></span>
 <br>   <span class="chapterToc">3 <a 
-href="getstartch3.html#x7-170003" name="QQ2-7-17">Preflight: Installing <span 
+href="getstartch3.html#x7-210003" name="QQ2-7-21">Preflight: Installing <span 
 class="ptmbi7t---109">FlightGear </span></a></span>
 <br>   &nbsp;<span class="sectionToc">3.1 <a 
-href="getstartch3.html#x7-180003.1" name="QQ2-7-18">Installing the binary distribution on a Windows system</a></span>
+href="getstartch3.html#x7-220003.1" name="QQ2-7-22">Installing the binary distribution on a Windows system</a></span>
 <br>   &nbsp;<span class="sectionToc">3.2 <a 
-href="getstartch3.html#x7-190003.2" name="QQ2-7-19">Installing the binary distribution on a Macintosh system</a></span>
+href="getstartch3.html#x7-230003.2" name="QQ2-7-23">Installing the binary distribution on a Macintosh system</a></span>
 <br>   &nbsp;<span class="sectionToc">3.3 <a 
-href="getstartch3.html#x7-200003.3" name="QQ2-7-20">Installing the binary distribution on a Debian Linux system</a></span>
+href="getstartch3.html#x7-240003.3" name="QQ2-7-24">Installing the binary distribution on a Debian Linux system</a></span>
 <br>   &nbsp;<span class="sectionToc">3.4 <a 
-href="getstartch3.html#x7-210003.4" name="QQ2-7-21">Installing the binary distribution on a SGI IRIX system</a></span>
+href="getstartch3.html#x7-250003.4" name="QQ2-7-25">Installing the binary distribution on a SGI IRIX system</a></span>
 <br>   &nbsp;<span class="sectionToc">3.5 <a 
-href="getstartch3.html#x7-220003.5" name="QQ2-7-22">Installing add-on scenery</a></span>
+href="getstartch3.html#x7-260003.5" name="QQ2-7-26">Installing add-on scenery</a></span>
 <br>   &nbsp;<span class="sectionToc">3.6 <a 
-href="getstartch3.html#x7-230003.6" name="QQ2-7-23">Installing documentation</a></span>
+href="getstartch3.html#x7-270003.6" name="QQ2-7-27">Installing documentation</a></span>
 <br>   <span class="partToc"><a 
-href="getstartpa2.html#x8-24000II" name="QQ2-8-24">Flying with <span 
+href="getstartpa2.html#x8-28000II" name="QQ2-8-28">Flying with <span 
 class="ptmbi7t---109">FlightGear</span></a></span>
 <br>   <span class="chapterToc">4 <a 
-href="getstartch4.html#x9-250004" name="QQ2-9-25">Takeoff: How to start the program</a></span>
+href="getstartch4.html#x9-290004" name="QQ2-9-29">Takeoff: How to start the program</a></span>
 <br>   &nbsp;<span class="sectionToc">4.1 <a 
-href="getstartch4.html#x9-260004.1" name="QQ2-9-26">Launching the simulator under Unix/Linux</a></span>
+href="getstartch4.html#x9-300004.1" name="QQ2-9-30">Launching the simulator under Unix/Linux</a></span>
 <br>   &nbsp;<span class="sectionToc">4.2 <a 
-href="getstartch4.html#x9-270004.2" name="QQ2-9-27">Launching the simulator under Windows</a></span>
+href="getstartch4.html#x9-310004.2" name="QQ2-9-31">Launching the simulator under Windows</a></span>
 <br>   &nbsp;<span class="sectionToc">4.3 <a 
-href="getstartch4.html#x9-280004.3" name="QQ2-9-28">Launching the simulator under Mac OS X</a></span>
+href="getstartch4.html#x9-320004.3" name="QQ2-9-32">Launching the simulator under Mac OS X</a></span>
 <br>   &nbsp;<span class="sectionToc">4.4 <a 
-href="getstartch4.html#x9-290004.4" name="QQ2-9-29">Command line parameters</a></span>
+href="getstartch4.html#x9-330004.4" name="QQ2-9-33">Command line parameters</a></span>
 <br>   &nbsp;<span class="sectionToc">4.5 <a 
 href="getstartch4.html#x9-460004.5" name="QQ2-9-46">Joystick support</a></span>
 <br>   &nbsp;<span class="sectionToc">4.6 <a 
 href="getstartch4.html#x9-560004.6" name="QQ2-9-56">A glance over our hangar</a></span>
 <br>   <span class="chapterToc">5 <a 
-href="getstartch5.html#x10-430005" name="QQ2-10-43">In-flight: All about instruments, keystrokes and menus</a></span>
+href="getstartch5.html#x10-570005" name="QQ2-10-57">In-flight: All about instruments, keystrokes and menus</a></span>
 <br>   &nbsp;<span class="sectionToc">5.1 <a 
-href="getstartch5.html#x10-440005.1" name="QQ2-10-44">Starting the engine</a></span>
+href="getstartch5.html#x10-580005.1" name="QQ2-10-58">Starting the engine</a></span>
 <br>   &nbsp;<span class="sectionToc">5.2 <a 
-href="getstartch5.html#x10-450005.2" name="QQ2-10-45">Keyboard controls</a></span>
+href="getstartch5.html#x10-590005.2" name="QQ2-10-59">Keyboard controls</a></span>
 <br>   &nbsp;<span class="sectionToc">5.3 <a 
-href="getstartch5.html#x10-460005.3" name="QQ2-10-46">Menu entries</a></span>
+href="getstartch5.html#x10-600005.3" name="QQ2-10-60">Menu entries</a></span>
 <br>   &nbsp;<span class="sectionToc">5.4 <a 
-href="getstartch5.html#x10-470005.4" name="QQ2-10-47">The Instrument Panel</a></span>
+href="getstartch5.html#x10-610005.4" name="QQ2-10-61">The Instrument Panel</a></span>
 <br>   &nbsp;<span class="sectionToc">5.5 <a 
-href="getstartch5.html#x10-480005.5" name="QQ2-10-48">The Head Up Display</a></span>
+href="getstartch5.html#x10-620005.5" name="QQ2-10-62">The Head Up Display</a></span>
 <br>   &nbsp;<span class="sectionToc">5.6 <a 
-href="getstartch5.html#x10-490005.6" name="QQ2-10-49">Mouse controlled actions</a></span>
+href="getstartch5.html#x10-630005.6" name="QQ2-10-63">Mouse controlled actions</a></span>
 <br>   &nbsp;<span class="sectionToc">5.7 <a 
-href="getstartch5.html#x10-500005.7" name="QQ2-10-50">Some further reading for pilot students</a></span>
+href="getstartch5.html#x10-640005.7" name="QQ2-10-64">Some further reading for student pilots</a></span>
 <br>   <span class="partToc"><a 
-href="getstartpa3.html#x11-51000III" name="QQ2-11-51">Appendices</a></span>
+href="getstartpa3.html#x11-65000III" name="QQ2-11-65">Appendices</a></span>
 <br>   <span class="appendixToc">A <a 
-href="getstartap1.html#x12-52000A" name="QQ2-12-52">Missed approach: If anything refuses to work</a></span>
+href="getstartap1.html#x12-66000A" name="QQ2-12-66">Missed approach: If anything refuses to work</a></span>
 <br>   &nbsp;<span class="sectionToc">A.1 <a 
-href="getstartap1.html#x12-53000A.1" name="QQ2-12-53">FlightGear Problem Reports</a></span>
+href="getstartap1.html#x12-67000A.1" name="QQ2-12-67">FlightGear Problem Reports</a></span>
 <br>   &nbsp;<span class="sectionToc">A.2 <a 
-href="getstartap1.html#x12-54000A.2" name="QQ2-12-54">General problems</a></span>
+href="getstartap1.html#x12-68000A.2" name="QQ2-12-68">General problems</a></span>
 <br>   &nbsp;<span class="sectionToc">A.3 <a 
-href="getstartap1.html#x12-55000A.3" name="QQ2-12-55">Potential problems under Linux</a></span>
+href="getstartap1.html#x12-69000A.3" name="QQ2-12-69">Potential problems under Linux</a></span>
 <br>   &nbsp;<span class="sectionToc">A.4 <a 
-href="getstartap1.html#x12-56000A.4" name="QQ2-12-56">Potential problems under Windows</a></span>
+href="getstartap1.html#x12-70000A.4" name="QQ2-12-70">Potential problems under Windows</a></span>
 <br>   <span class="appendixToc">B <a 
-href="getstartap2.html#x13-57000B" name="QQ2-13-57">Some words on OpenGL graphics drivers</a></span>
+href="getstartap2.html#x13-71000B" name="QQ2-13-71">Some words on OpenGL graphics drivers</a></span>
 <br>   &nbsp;<span class="sectionToc">B.1 <a 
-href="getstartap2.html#x13-58000B.1" name="QQ2-13-58">NVIDIA chip based cards under Linux</a></span>
+href="getstartap2.html#x13-72000B.1" name="QQ2-13-72">NVIDIA chip based cards under Linux</a></span>
 <br>   &nbsp;<span class="sectionToc">B.2 <a 
-href="getstartap2.html#x13-59000B.2" name="QQ2-13-59">NVIDIA chip based cards under Windows</a></span>
+href="getstartap2.html#x13-73000B.2" name="QQ2-13-73">NVIDIA chip based cards under Windows</a></span>
 <br>   &nbsp;<span class="sectionToc">B.3 <a 
-href="getstartap2.html#x13-60000B.3" name="QQ2-13-60">3DFX chip based cards under Windows</a></span>
+href="getstartap2.html#x13-74000B.3" name="QQ2-13-74">3DFX chip based cards under Windows</a></span>
 <br>   &nbsp;<span class="sectionToc">B.4 <a 
-href="getstartap2.html#x13-61000B.4" name="QQ2-13-61">An alternative approach for Windows users</a></span>
+href="getstartap2.html#x13-75000B.4" name="QQ2-13-75">An alternative approach for Windows users</a></span>
 <br>   &nbsp;<span class="sectionToc">B.5 <a 
-href="getstartap2.html#x13-62000B.5" name="QQ2-13-62">3DFX chip based cards under Linux</a></span>
+href="getstartap2.html#x13-76000B.5" name="QQ2-13-76">3DFX chip based cards under Linux</a></span>
 <br>   &nbsp;<span class="sectionToc">B.6 <a 
-href="getstartap2.html#x13-63000B.6" name="QQ2-13-63">ATI chip based cards under Linux</a></span>
+href="getstartap2.html#x13-77000B.6" name="QQ2-13-77">ATI chip based cards under Linux</a></span>
 <br>   &nbsp;<span class="sectionToc">B.7 <a 
-href="getstartap2.html#x13-64000B.7" name="QQ2-13-64">Building your own OpenGL support under Linux</a></span>
+href="getstartap2.html#x13-78000B.7" name="QQ2-13-78">Building your own OpenGL support under Linux</a></span>
 <br>   &nbsp;<span class="sectionToc">B.8 <a 
-href="getstartap2.html#x13-65000B.8" name="QQ2-13-65">OpenGL on MacIntosh</a></span>
+href="getstartap2.html#x13-79000B.8" name="QQ2-13-79">OpenGL on Macintosh</a></span>
 <br>   <span class="appendixToc">C <a 
-href="getstartap3.html#x14-66000C" name="QQ2-14-66">Landing: Some further thoughts before leaving the plane</a></span>
+href="getstartap3.html#x14-80000C" name="QQ2-14-80">Landing: Some further thoughts before leaving the plane</a></span>
 <br>   &nbsp;<span class="sectionToc">C.1 <a 
-href="getstartap3.html#x14-67000C.1" name="QQ2-14-67">A not so Short History of <span 
+href="getstartap3.html#x14-81000C.1" name="QQ2-14-81">A Sketch on the History of <span 
 class="ptmbi7t---109">FlightGear</span></a></span>
 <br>   &nbsp;<span class="sectionToc">C.2 <a 
-href="getstartap3.html#x14-68000C.2" name="QQ2-14-68">Those, who did the work</a></span>
+href="getstartap3.html#x14-86000C.2" name="QQ2-14-86">Those, who did the work</a></span>
 <br>   &nbsp;<span class="sectionToc">C.3 <a 
-href="getstartap3.html#x14-69000C.3" name="QQ2-14-69">What remains to be done</a></span>
+href="getstartap3.html#x14-87000C.3" name="QQ2-14-87">What remains to be done</a></span>
 <br>   <span class="chapterToc"> <a 
-href="getstartap3.html#Q1-14-71">Index</a></span>
+href="getstartap3.html#Q1-14-89">Index</a></span>
 <br>   <span class="likechapterToc"><a 
-href="getstartli3.html#x15-71000C.3" name="QQ2-15-72">Index</a></span>
+href="getstartli3.html#x15-89000C.3" name="QQ2-15-90">Index</a></span>
   </div>
--- a/Docs/InstallGuide/html/getstart0x.gif
+++ b/Docs/InstallGuide/html/getstart0x.gif
--- a/Docs/InstallGuide/html/getstart10x.gif
+++ b/Docs/InstallGuide/html/getstart10x.gif
--- a/Docs/InstallGuide/html/getstart11x.gif
+++ b/Docs/InstallGuide/html/getstart11x.gif
--- a/Docs/InstallGuide/html/getstart12x.gif
+++ b/Docs/InstallGuide/html/getstart12x.gif
--- a/Docs/InstallGuide/html/getstart3x.gif
+++ b/Docs/InstallGuide/html/getstart3x.gif
--- a/Docs/InstallGuide/html/getstart4x.gif
+++ b/Docs/InstallGuide/html/getstart4x.gif
--- a/Docs/InstallGuide/html/getstart5x.gif
+++ b/Docs/InstallGuide/html/getstart5x.gif
--- a/Docs/InstallGuide/html/getstart6x.gif
+++ b/Docs/InstallGuide/html/getstart6x.gif
--- a/Docs/InstallGuide/html/getstart7x.gif
+++ b/Docs/InstallGuide/html/getstart7x.gif
--- a/Docs/InstallGuide/html/getstart8x.gif
+++ b/Docs/InstallGuide/html/getstart8x.gif
--- a/Docs/InstallGuide/html/getstart9x.gif
+++ b/Docs/InstallGuide/html/getstart9x.gif
--- a/Docs/InstallGuide/html/getstartap1.html
+++ b/Docs/InstallGuide/html/getstartap1.html
@ -6,7 +6,7 @@
 <meta name="generator" content="TeX4ht (http://www.cis.ohio-state.edu/~gurari/TeX4ht/mn.html)"> 
 <!-- html,2,info,next,sections+ --> 
 <meta name="src" content="getstart.tex"> 
-<meta name="date" content="2002-02-16 19:41:00"> 
+<meta name="date" content="2002-09-08 00:44:00"> 
 <link rel="stylesheet" type="text/css" href="getstart.css"> 
 </head><body 
 >
@ -17,47 +17,46 @@ href="getstartpa3.html#tailgetstartpa3.html" >prev-tail</a>] [<a
 href="#tailgetstartap1.html">tail</a>] [<a 
 href="getstartpa3.html#getstartap1.html" >up</a>] </p></div>
   <h2 class="appendixHead"><span class="titlemark">Appendix&nbsp;A</span><br><a 
-href="getstart.html#QQ2-12-52" name="x12-52000A">Missed approach: If anything refuses to work</a></h2>
+href="getstart.html#QQ2-12-66" name="x12-66000A">Missed approach: If anything refuses to work</a></h2>
 <!--l. 33--><p class="noindent">In the following section, we tried to sort some problems<a 
-  name="dx12-52001"></a> according to operating
+  name="dx12-66001"></a> according to operating system,
-system, but if you encounter a problem, it may be a wise idea to look beyond
+but if you encounter a problem, it may be a wise idea to look beyond &#8221;your&#8221;
-&#8221;your&#8221; operating system - just in case. If you are experiencing problems, we
+operating system - just in case. If you are experiencing problems, we would
-would strongly advise you to first check the FAQ<a 
+strongly advise you to first check the FAQ<a 
-  name="dx12-52002"></a> maintained by Cameron Moore<a 
+  name="dx12-66002"></a> maintained by Cameron Moore<a 
-  name="dx12-52003"></a>
+  name="dx12-66003"></a> at
-at
+<!--l. 37--><p class="indent">   <a 
 <!--l. 36--><p class="indent">   <a 
 href="http://www.flightgear.org/Docs/FlightGear-FAQ.html" >http://www.flightgear.org/Docs/FlightGear-FAQ.html</a>.
-<!--l. 38--><p class="indent">   Moreover, the source code contains a directory <span 
+<!--l. 41--><p class="indent">   Moreover, the source code contains a directory <span 
 class="pcrr7t---109">docs-mini </span>containing numerous
 ideas on and solutions to special problems. This is also a good place to go for further
 reading.
   <h3 class="sectionHead"><span class="titlemark">A.1</span> <a 
-href="getstart.html#QQ2-12-53" name="x12-53000A.1">FlightGear Problem Reports</a></h3>
+href="getstart.html#QQ2-12-67" name="x12-67000A.1">FlightGear Problem Reports</a></h3>
 <a 
-  name="dx12-53001"></a>
+  name="dx12-67001"></a>
-<!--l. 45--><p class="noindent">The best place to look for help is generally the mailing lists<a 
+<!--l. 48--><p class="noindent">The best place to look for help is generally the mailing lists<a 
-  name="dx12-53002"></a>, specifically the
+  name="dx12-67002"></a>, specifically the
 <span 
 class="ptmb7t---109">[Flightgear-User] </span>mailing list. If you happen to be running a CVS version of
 <span 
 class="ptmbi7t---109">FlightGear</span>, you may want to subscribe to the <span 
 class="ptmb7t---109">[Flightgear-Devel] </span>list. Instructions for
 subscription can be found at
-<!--l. 49--><p class="indent">   <a 
+<!--l. 52--><p class="indent">   <a 
 href="http://www.flightgear.org/mail.html" >http://www.flightgear.org/mail.html</a>.
-<!--l. 52--><p class="noindent">It&#8217;s often the case that someone has already dealt with the issue you&#8217;re dealing with, so it
+<!--l. 55--><p class="noindent">It&#8217;s often the case that someone has already dealt with the issue you&#8217;re dealing with, so it
 may be worth your time to search the mailing list archives at
-<!--l. 56--><p class="indent">   http://www.mail-archive.com/flightgear-users%40flightgear.org/
+<!--l. 59--><p class="indent">   http://www.mail-archive.com/flightgear-users%40flightgear.org/
-<!--l. 58--><p class="indent">   http://www.mail-archive.com/flightgear-devel%40flightgear.org/.
+<!--l. 61--><p class="indent">   http://www.mail-archive.com/flightgear-devel%40flightgear.org/.
-<!--l. 61--><p class="noindent">There are numerous developers and users reading the lists, so questions are generally
+<!--l. 64--><p class="noindent">There are numerous developers and users reading the lists, so questions are generally
 answered. However, messages of the type
-<!--l. 64--><p class="indent">   <span 
+<!--l. 67--><p class="indent">   <span 
 class="ptmri7t---109">FlightGear does not compile on my system. What shall I do?</span>
-<!--l. 66--><p class="noindent">are hard to answer without any further detail given, aren&#8217;t they? Here are some things to
+<!--l. 69--><p class="noindent">are hard to answer without any further detail given, aren&#8217;t they? Here are some things to
 consider including in your message when you report a problem:
     <ul class="itemize1">
     <li class="itemize"><span 
@ -81,32 +80,41 @@ class="ptmb7t---109">Type of problem: </span>(Linker dies with message. . . )
     <li class="itemize"><span 
 class="ptmb7t---109">Steps to recreate the problem: </span>Start at KSFO, turn off brakes . . .
     </li></ul>
-<!--l. 87--><p class="indent">   <span 
+<!--l. 90--><p class="indent">   For getting a trace of the output which <span 
 class="ptmbi7t---109">FlightGear </span>produces, then following
 command may come in handy (may need to be modified on some OSs or may not work
 on others at all, though):
 <!--l. 93--><p class="indent">   <span 
 class="pcrr7t---109">%FG</span><span class="underline"><span 
 class="cmmi-10--109">&nbsp;</span><span 
 class="cmmi-10--109">&nbsp;</span></span><span 
 class="pcrr7t---109">ROOT/BIN/fgfs &gt;log.txt 2&gt;&amp;1</span>
 <!--l. 96--><p class="indent">   <span 
 class="ptmb7t---109">One final remark: </span>Please avoid posting binaries to these lists! List subscribers
 are widely distributed, and some users have low bandwidth and/or metered
-connections. Large messsages may be rejected by the mailing list administrator.
+connections. Large messages may be rejected by the mailing list administrator.
 Thanks.
   <h3 class="sectionHead"><span class="titlemark">A.2</span> <a 
-href="getstart.html#QQ2-12-54" name="x12-54000A.2">General problems</a></h3>
+href="getstart.html#QQ2-12-68" name="x12-68000A.2">General problems</a></h3>
 <a 
-  name="dx12-54001"></a>
+  name="dx12-68001"></a>
     <ul class="itemize1">
     <li class="itemize"><span 
 class="ptmbi7t---109">FlightGear </span>runs SOOO slow.
     <br class="newline">If <span 
 class="ptmbi7t---109">FlightGear </span>says it&#8217;s running with something like 1 fps (frame per second)
     or below you typically don&#8217;t have working hardware OpenGL<a 
-  name="dx12-54002"></a> support. There
+  name="dx12-68002"></a> support. There
     may be several reasons for this. First, there may be no OpenGL hardware
     drivers available for older cards. In this case it is highly recommended to get
     a new board.
-     <!--l. 101--><p class="noindent">Second,  check  if  your  drivers  are  properly  installed.  Several  cards  need
+     <!--l. 110--><p class="noindent">Second,  check  if  your  drivers  are  properly  installed.  Several  cards  need
     additional OpenGL support drivers besides the &#8221;native&#8221; windows ones. For
     more detail check Appendix <a 
-href="getstartap2.html#x13-57000B">B<!--tex4ht:ref: opengl--></a>.
+href="getstartap2.html#x13-71000B">B<!--tex4ht:ref: opengl--></a>.
     </li>
     <li class="itemize">Either <span 
 class="pcrr7t---109">configure </span>or <span 
@ -123,53 +131,53 @@ class="pcrr7t---109">libplibpu.a </span>should be under <span
 class="pcrr7t---109">/lib</span>. Double check
     there are no stray <span 
 class="ptmbi7t---109">PLIB </span>headers/libraries sitting elsewhere!
-     <!--l. 111--><p class="noindent">Besides check careful the error messages of <span 
+     <!--l. 120--><p class="noindent">Besides check careful the error messages of <span 
 class="pcrr7t---109">configure</span>. In several cases
     it says what is missing.</li></ul>
   <h3 class="sectionHead"><span class="titlemark">A.3</span> <a 
-href="getstart.html#QQ2-12-55" name="x12-55000A.3">Potential problems under Linux</a></h3>
+href="getstart.html#QQ2-12-69" name="x12-69000A.3">Potential problems under Linux</a></h3>
 <a 
-  name="dx12-55001"></a>
+  name="dx12-69001"></a>
-<!--l. 118--><p class="noindent">Since we don&#8217;t have access to all possible flavors of Linux distributions, here are some
+<!--l. 127--><p class="noindent">Since we don&#8217;t have access to all possible flavors of Linux distributions, here are some
 thoughts on possible causes of problems. (This Section includes contributions by Kai
 Troester.)<a 
-  name="dx12-55002"></a>
+  name="dx12-69002"></a>
     <ul class="itemize1">
     <li class="itemize">Wrong library versions
     <br class="newline">This is a rather common cause of grief especially when you prefer to install
     the libraries needed by <span 
 class="ptmbi7t---109">FlightGear </span>by hand. Be sure that especially the Mesa
     library contains support for the 3DFX<a 
-  name="dx12-55003"></a> board and that GLIDE<a 
+  name="dx12-69003"></a> board and that GLIDE<a 
-  name="dx12-55004"></a> libraries are
+  name="dx12-69004"></a> libraries are
     installed  and  can  be  found.  If  a  <span 
 class="pcrr7t---109">ldd `which fgfs` </span>complains about
     missing libraries you are in trouble.
-     <!--l. 132--><p class="noindent">You should also be sure to <span 
+     <!--l. 141--><p class="noindent">You should also be sure to <span 
 class="ptmri7t---109">always keep the </span>latest version of <span 
 class="ptmbi7t---109">PLIB </span>on your
     system.  Lots  of  people  have  failed  miserably  to  compile  <span 
 class="ptmbi7t---109">FlightGear  </span>just
     because of an outdated plib.
     </li>
     <li class="itemize">Missing permissions<a 
-  name="dx12-55005"></a>
+  name="dx12-69005"></a>
     <br class="newline">In case you are using XFree86<a 
-  name="dx12-55006"></a> before release 4.0 the <span 
+  name="dx12-69006"></a> before release 4.0 the <span 
 class="ptmbi7t---109">FlightGear </span>binary may
     need to be setuid root in order to be capable of accessing some accelerator
     boards (or a special kernel module as described earlier in this document)
     based on 3DFX chips. So you can either issue a
-     <!--l. 142--><p class="noindent"><span 
+     <!--l. 151--><p class="noindent"><span 
 class="pcrr7t---109">chown root.root /usr/local/bin/fgfs ;</span>
     <br class="newline"><span 
 class="pcrr7t---109">chmod 4755 /usr/local/bin/fgfs</span>
-     <!--l. 145--><p class="noindent">to give the <span 
+     <!--l. 154--><p class="noindent">to give the <span 
 class="ptmbi7t---109">FlightGear </span>binary the proper rights or install the 3DFX module.
-     The latter is the &#8220;clean&#8221; solution and strongly recommended!
+     The latter is the &#8221;clean&#8221; solution and strongly recommended!
     </li>
     <li class="itemize">Non-default install options
     <br class="newline"><span 
@ -191,17 +199,19 @@ class="ptmbi7t---109">FlightGear </span>as they
     </li>
     <li class="itemize">Problems with linking
     <br class="newline">There may be several reasons; however in case you get a message like
-     <!--l. 167--><p class="noindent"><span 
+     <!--l. 176--><p class="noindent"><span 
 class="pcrr7t---109">libmk4.so.0</span>: cannot open shared object file
-     <!--l. 169--><p class="noindent">the reason is a missing library package called Metakit. This is provided with
+                                                                     
-     Simgear in packed form. Unpack and install it first.</li></ul>
+
     <!--l. 178--><p class="noindent">the reason is a missing library package called Metakit. This is provided with
     <span 
 class="ptmbi7t---109">SimGear </span>in packed form. On its installation, see Sec. <a 
 href="getstartch2.html#x6-150002.3.2">2.3.2<!--tex4ht:ref: metakeitinstall--></a>.</li></ul>
   <h3 class="sectionHead"><span class="titlemark">A.4</span> <a 
-href="getstart.html#QQ2-12-56" name="x12-56000A.4">Potential problems under Windows</a></h3>
+href="getstart.html#QQ2-12-70" name="x12-70000A.4">Potential problems under Windows</a></h3>
 <a 
-  name="dx12-56001"></a>
+  name="dx12-70001"></a>
     <ul class="itemize1">
     <li class="itemize">The executable refuses to run.
     <br class="newline">You may have tried to start the executable directly either by double-clicking
@ -214,15 +224,15 @@ class="pcrr7t---109">ROOT </span>in <span
 class="pcrr7t---109">autoexec.bat </span>or otherwise). Rather
     double-click <span 
 class="pcrr7t---109">runfgfs.bat</span>. For more details, check Chapter <a 
-href="getstartch4.html#x9-250004">4<!--tex4ht:ref: takeoff--></a>.
+href="getstartch4.html#x9-290004">4<!--tex4ht:ref: takeoff--></a>.
-     <!--l. 184--><p class="noindent">Another cause of grief might be that you did not download the most recent
+     <!--l. 193--><p class="noindent">Another cause of grief might be that you did not download the most recent
     versions of the base package files required by <span 
 class="ptmbi7t---109">FlightGear</span>, or you did not
     download any of them at all. Have a close look at this, as the scenery/texture
     format  is  still  under  development  and  may  change  frequently.  For  more
     details, check Chapter <a 
-href="getstartch3.html#x7-170003">3<!--tex4ht:ref: prefligh--></a>.
+href="getstartch3.html#x7-210003">3<!--tex4ht:ref: prefligh--></a>.
-     <!--l. 190--><p class="noindent">Next,  if  you  run  into  trouble  at  runtime,  do  not  use  windows  utilities  for
+     <!--l. 199--><p class="noindent">Next,  if  you  run  into  trouble  at  runtime,  do  not  use  windows  utilities  for
     unpacking the <span 
 class="pcrr7t---109">.tar.gz</span>. If you did, try it in the Cygnus shell with <span 
 class="pcrr7t---109">tar</span>
@ -237,21 +247,24 @@ class="pcrr7t---109">runfgfs.bat</span>.
     </li>
     <li class="itemize">I am unable to build <span 
 class="ptmbi7t---109">FlightGear </span>under MSVC<a 
-  name="dx12-56002"></a>/MS DevStudio<a 
+  name="dx12-70002"></a>/MS DevStudio<a 
-  name="dx12-56003"></a>.
+  name="dx12-70003"></a>.
     <br class="newline">By default, <span 
 class="ptmbi7t---109">FlightGear </span>is build with GNU GCC. The Win32 port of GNU
     GCC is known as Cygwin<a 
-  name="dx12-56004"></a>. For hints on Makefiles required for MSVC for
+  name="dx12-70004"></a>. For hints on Makefiles required for MSVC for
     MSC DevStudio have a look into
-     <!--l. 205--><p class="noindent"><a 
+     <!--l. 214--><p class="noindent"><a 
 href="ftp://www.flightgear.org/pub/flightgear/Source/" >ftp://www.flightgear.org/pub/flightgear/Source/</a>.
-     <!--l. 208--><p class="noindent">In principle, it should be possible to compile <span 
+     <!--l. 217--><p class="noindent">In principle, it should be possible to compile <span 
 class="ptmbi7t---109">FlightGear </span>with the project
     files provided with the source code.
     </li>
     <li class="itemize">Compilation of <span 
 class="ptmbi7t---109">FlightGear </span>dies.
     <br class="newline">There may be several reasons for this, including true bugs. However, before
     trying to do anything else or report a problem, make sure you have the latest
     version of the <span 
--- a/Docs/InstallGuide/html/getstartap2.html
+++ b/Docs/InstallGuide/html/getstartap2.html
@ -6,7 +6,7 @@
 <meta name="generator" content="TeX4ht (http://www.cis.ohio-state.edu/~gurari/TeX4ht/mn.html)"> 
 <!-- html,2,info,next,sections+ --> 
 <meta name="src" content="getstart.tex"> 
-<meta name="date" content="2002-02-16 19:41:00"> 
+<meta name="date" content="2002-09-08 00:44:00"> 
 <link rel="stylesheet" type="text/css" href="getstart.css"> 
 </head><body 
 >
@ -17,21 +17,21 @@ href="getstartap1.html#tailgetstartap1.html" >prev-tail</a>] [<a
 href="#tailgetstartap2.html">tail</a>] [<a 
 href="getstartpa3.html#getstartap2.html" >up</a>] </p></div>
   <h2 class="appendixHead"><span class="titlemark">Appendix&nbsp;B</span><br><a 
-href="getstart.html#QQ2-13-57" name="x13-57000B">Some words on OpenGL graphics drivers</a></h2>
+href="getstart.html#QQ2-13-71" name="x13-71000B">Some words on OpenGL graphics drivers</a></h2>
 <!--l. 32--><p class="noindent"><span 
 class="ptmbi7t---109">FlightGear</span>&#8217;s graphics engine is based on a graphics library<a 
-  name="dx13-57001"></a> called OpenGL<a 
+  name="dx13-71001"></a> called OpenGL<a 
-  name="dx13-57002"></a>. Its primary
+  name="dx13-71002"></a>. Its primary
 advantage is its platform independence, i. e., programs written with OpenGL<a 
-  name="dx13-57003"></a> support can
+  name="dx13-71003"></a> support can
 be compiled and executed on several platforms, given the proper drivers having been
 installed in advance. Thus, independent of if you want to run the binaries only or if you
 want to compile the program yourself you must have some sort of OpenGL<a 
-  name="dx13-57004"></a> support
+  name="dx13-71004"></a> support
 installed for your video card<a 
-  name="dx13-57005"></a>.
+  name="dx13-71005"></a>.
 <!--l. 39--><p class="indent">   A good review on OpenGL drivers<a 
-  name="dx13-57006"></a> can be found at
+  name="dx13-71006"></a> can be found at
 <!--l. 42--><p class="indent">   <a 
 href="http://www.flightgear.org/Hardware" >http://www.flightgear.org/Hardware</a>.
 <!--l. 45--><p class="noindent">Specific information is collected for windows at
@ -43,7 +43,7 @@ href="http://www.x-plane.com/SYSREQ/v5mac.html" >http://www.x-plane.com/SYSREQ/v
 <!--l. 60--><p class="noindent">An excellent place to look for documentation about Linux and 3-D accelerators is the
 <span 
 class="ptmri7t---109">Linux Quake</span><a 
-  name="dx13-57007"></a> <span 
+  name="dx13-71007"></a> <span 
 class="ptmri7t---109">HOWTO </span>at
 <!--l. 65--><p class="indent">   <a 
 href="http://www.linuxquake.com" >http://www.linuxquake.com</a>.
@ -54,14 +54,14 @@ are unable to provide a complete description for all systems. Given the present
 dominance of NVIDIA combined with the fact that their chips have indeed been proven
 powerful for running <span 
 class="ptmbi7t---109">FlightGear</span>, we will concentrate on NVIDIA drivers<a 
-  name="dx13-57008"></a> in what
+  name="dx13-71008"></a> in what
 follows.
   <h3 class="sectionHead"><span class="titlemark">B.1</span> <a 
-href="getstart.html#QQ2-13-58" name="x13-58000B.1">NVIDIA chip based cards under Linux</a></h3>
+href="getstart.html#QQ2-13-72" name="x13-72000B.1">NVIDIA chip based cards under Linux</a></h3>
 <!--l. 80--><p class="noindent">Recent Linux<a 
-  name="dx13-58001"></a> distributions include and install anything needed to run OpenGL programs
+  name="dx13-72001"></a> distributions include and install anything needed to run OpenGL programs
 under Linux<a 
-  name="dx13-58002"></a>. Usually there is no need to install anything else.
+  name="dx13-72002"></a>. Usually there is no need to install anything else.
 <!--l. 83--><p class="indent">   If for whatever reason this does not work, you may try to download the most recent
 drivers from the NVIDIA site at
 <!--l. 87--><p class="indent">   <a 
@ -71,7 +71,7 @@ href="http://www.nvidia.com/Products/Drivers.nsf/Linux.html" >http://www.nvidia.
 <!--l. 90--><p class="noindent">At present, this page has drivers for all NVIDIA chips for the following Linux
 distributions:<a 
-  name="dx13-58003"></a> RedHat 7.1, Redhat 7.0, Redhat 6.2, Redhat 6.1, Mandrake 7.1, Mandrake
+  name="dx13-72003"></a> RedHat 7.1, Redhat 7.0, Redhat 6.2, Redhat 6.1, Mandrake 7.1, Mandrake
 7.2, SuSE 7.1, SuSE 7.0 in several formats (.rpm, .tar.gz). These drivers support OpenGL
 natively and do not need any additional stuff.
 <!--l. 96--><p class="indent">   The page named above contains a detailed <span 
@ -80,15 +80,15 @@ class="pcrr7t---109">README and Installation</span>
 class="pcrr7t---109">Guide </span>giving a step-by-step description, making it unnecessary to copy the material
 here.
   <h3 class="sectionHead"><span class="titlemark">B.2</span> <a 
-href="getstart.html#QQ2-13-59" name="x13-59000B.2">NVIDIA chip based cards under Windows</a></h3>
+href="getstart.html#QQ2-13-73" name="x13-73000B.2">NVIDIA chip based cards under Windows</a></h3>
 <!--l. 103--><p class="noindent">Again, you may first try the drivers coming with your graphics card. Usually they should
 include OpenGL<a 
-  name="dx13-59001"></a> support. If for whatever reason the maker of your board did not include
+  name="dx13-73001"></a> support. If for whatever reason the maker of your board did not include
 this feature into the driver, you should install the Detonator reference drivers<a 
-  name="dx13-59002"></a><a 
+  name="dx13-73002"></a><a 
-  name="dx13-59003"></a> made by
+  name="dx13-73003"></a> made by
 NVIDIA<a 
-  name="dx13-59004"></a> (which might be a good idea anyway). These are available in three
+  name="dx13-73004"></a> (which might be a good idea anyway). These are available in three
 different versions (Windows 95/98/ME, Windows 2000, Windows NT) from
 <!--l. 111--><p class="indent">   <a 
 href="http://www.nvidia.com/products.nsf/htmlmedia/detonator3.html" >http://www.nvidia.com/products.nsf/htmlmedia/detonator3.html</a>
@ -96,56 +96,58 @@ href="http://www.nvidia.com/products.nsf/htmlmedia/detonator3.html" >http://www.
 uninstall your present driver and install a standard VGA graphics adapter before
 switching to the new NVIDIA drivers first.
   <h3 class="sectionHead"><span class="titlemark">B.3</span> <a 
-href="getstart.html#QQ2-13-60" name="x13-60000B.3">3DFX chip based cards under Windows</a></h3>
+href="getstart.html#QQ2-13-74" name="x13-74000B.3">3DFX chip based cards under Windows</a></h3>
 <!--l. 124--><p class="noindent">With the Glide drivers no longer provided by 3DFX there seems to be little chance to
 get it running (except to find older OpenGL drivers somewhere on the net or
 privately). All pages which formerly provided official support or instructions for
 3DFX are gone now. For an alternative, you may want to check the next section,
 though.
   <h3 class="sectionHead"><span class="titlemark">B.4</span> <a 
-href="getstart.html#QQ2-13-61" name="x13-61000B.4">An alternative approach for Windows users</a></h3>
+href="getstart.html#QQ2-13-75" name="x13-75000B.4">An alternative approach for Windows users</a></h3>
 <!--l. 134--><p class="noindent">There is now an attempt to build a program which detects the graphics chip on your
 board and automatically installs the appropriate OpenGL drivers. This is called
 OpenGL Setup<a 
-  name="dx13-61001"></a> and is presently in beta stage. It&#8217;s home page can be found at
+  name="dx13-75001"></a> and is presently in beta stage. It&#8217;s home page can be found at
 <!--l. 139--><p class="indent">   <a 
 href="http://www.glsetup.com/" >http://www.glsetup.com/</a>.
-<!--l. 142--><p class="indent">   We did not try this ourselfes, but would suggest it for those completely
+<!--l. 142--><p class="indent">   We did not try this ourselves, but would suggest it for those completely
 lost.
   <h3 class="sectionHead"><span class="titlemark">B.5</span> <a 
-href="getstart.html#QQ2-13-62" name="x13-62000B.5">3DFX chip based cards under Linux</a></h3>
+href="getstart.html#QQ2-13-76" name="x13-76000B.5">3DFX chip based cards under Linux</a></h3>
 <!--l. 149--><p class="noindent">Notably, with 3DFX<a 
-  name="dx13-62001"></a> now having been taken over by NVIDIA<a 
+  name="dx13-76001"></a> now having been taken over by NVIDIA<a 
-  name="dx13-62002"></a>, manufacturer&#8217;s support
+  name="dx13-76002"></a>, manufacturer&#8217;s support
 already has disappeared. However with XFree86-4.x (with x at least being greater than 1)
-Voodoo3 cards are known to be pretty usable in 16 bit colour mode. Newer cards should
+Voodoo3 cards are known to be pretty usable in 16 bit color mode. Newer cards should
 work fine as well. If you are still running a version of Xfree86 3.X and run into problems,
 consider an upgrade. The recent distributions by Debian or SuSE have been reported to
 work well.
   <h3 class="sectionHead"><span class="titlemark">B.6</span> <a 
-href="getstart.html#QQ2-13-63" name="x13-63000B.6">ATI chip based cards under Linux</a></h3>
+href="getstart.html#QQ2-13-77" name="x13-77000B.6">ATI chip based cards under Linux</a></h3>
-<!--l. 160--><p class="noindent">There is excellent support for ATI<a 
+<!--l. 160--><p class="noindent">There is support for ATI<a 
-  name="dx13-63001"></a> chips in XFree86-4.1 and greater. Lots of AGP boards
+  name="dx13-77001"></a> chips in XFree86-4.1 and greater. Lots of AGP boards based on
-based on the Rage128 chip - from simple Rage128 board to ATI Xpert2000 - are pretty
+the Rage128 chip - from simple Rage128 board to ATI Xpert2000 - are mostly usable for
-usuable for FlightGear. Since XFree86-4.1 you can use early Radeon chips - up to
+FlightGear. Since XFree86-4.1 you can use early Radeon chips - up to Radeon7500 with
-Radeon7500 with XFree86-4.2.
+XFree86-4.2.
   <h3 class="sectionHead"><span class="titlemark">B.7</span> <a 
-href="getstart.html#QQ2-13-64" name="x13-64000B.7">Building your own OpenGL support under Linux</a></h3>
+href="getstart.html#QQ2-13-78" name="x13-78000B.7">Building your own OpenGL support under Linux</a></h3>
 <!--l. 169--><p class="noindent">Setting up proper OpenGL support<a 
-  name="dx13-64001"></a> with a recent Linux distribution should be pretty
+  name="dx13-78001"></a> with a recent Linux distribution should be pretty
 simple. As an example SuSE<a 
-  name="dx13-64002"></a> ships everything you need plus some small shell scripts to
+  name="dx13-78002"></a> ships everything you need plus some small shell scripts to
 adjust the missing bits automagically. If you just want to execute pre-built binaries of
-FlightGear, then you&#8217;re done by using the supplied FlightGear package plus the
+FlightGear, then you&#8217;re done by using the supplied <span 
 class="ptmbi7t---109">FlightGear </span>package plus the
 mandantory runtime libraries (and kernel modules). The package manager will tell you
 which ones to choose.
-<!--l. 176--><p class="indent">   In case you want to run a selfmade kernel, you want to compile FlightGear yourself,
+<!--l. 176--><p class="indent">   In case you want to run a self-made kernel, you want to compile <span 
-you&#8217;re tweaking your X server configuration file yourself or you even run a homebrewn
+class="ptmbi7t---109">FlightGear</span>
-Linux &#8221;distribution&#8221; (this means, you want to compile everything yourself), this chapter
+yourself, you&#8217;re tweaking your X server configuration file yourself or you even run a
-might be useful for you.
+homebrewed Linux &#8221;distribution&#8221; (this means, you want to compile everything yourself),
 this chapter might be useful for you.
 <!--l. 181--><p class="indent">   Now let&#8217;s have a look at the parts that build OpenGL support on Linux. First there&#8217;s a
 Linux kernel with support for your graphics adapter.
 <!--l. 184--><p class="indent">   Examples on which graphics hardware is supported natively by Open Source drivers
@ -154,11 +156,11 @@ are provided on
 href="http://dri.sourceforge.net/status.phtml" >http://dri.sourceforge.net/status.phtml</a>.
 <!--l. 192--><p class="indent">   There are a few graphics chip families that are not directly or no more than partly
 supported by XFree86<a 
-  name="dx13-64003"></a>, the X window implementation on Linux, because vendors don&#8217;t
+  name="dx13-78003"></a>, the X window implementation on Linux, because vendors don&#8217;t
 like to provide programming information on their chips. In these cases - notably
 IBM/DIAMOND/now: ATI<a 
-  name="dx13-64004"></a> FireGL graphics boards and NVIDIA<a 
+  name="dx13-78004"></a> FireGL graphics boards and NVIDIA<a 
-  name="dx13-64005"></a> GeForce based cards -
+  name="dx13-78005"></a> GeForce based cards -
 you depend on the manufacturers will to follow the ongoing development of the XFree86
@ -166,20 +168,21 @@ you depend on the manufacturers will to follow the ongoing development of the XF
 graphics display infrastructure. These boards might prove to deliver impressing
 performance but in many cases - considering the CPU&#8217;s speed you find in today&#8217;s
 PC&#8217;s - you have many choices which all lead to respectable performance of
-FlightGear.
+<span 
 class="ptmbi7t---109">FlightGear</span>.
 <!--l. 202--><p class="indent">   As long as you use a distribution provided kernel, you can expect to find all
-necessary kernel modules at the approriate location. If you compile the kernel yourself,
+necessary kernel modules at the appropriate location. If you compile the kernel yourself,
-then you have to take care of two submenues in the kernel configuration menue. You&#8217;ll
+then you have to take care of two sub-menus in the kernel configuration menu. You&#8217;ll
-find them in the &#8221;Character devices&#8221; menue. Please notice that AGP support is not
+find them in the &#8221;Character devices&#8221; menu. Please notice that AGP support is not
 compulsory for hardware accelerated OpenGL support on Linux. This also works quite
 fine with some PCI cards (3dfx<a 
-  name="dx13-64006"></a> Voodoo3 PCI for example, in case you still own one).
+  name="dx13-78006"></a> Voodoo3 PCI for example, in case you still own one).
 Although every modern PC graphics card utilizes the AGP &#8217;bus&#8217; for fast data
 transfer.
 <!--l. 211--><p class="indent">   Besides &#8221;AGP Support<a 
-  name="dx13-64007"></a>&#8221; for your chipset - you might want to ask your mainboard
+  name="dx13-78007"></a>&#8221; for your chipset - you might want to ask your mainboard
-manual which one is on - you defnitely want to activate &#8221;Direct Rendering Manager&#8221;
+manual which one is on - you definitely want to activate &#8221;Direct Rendering Manager&#8221;
-for your garphics board. Please note that recent releases of XFree86 - namely
+for your graphics board. Please note that recent releases of XFree86 - namely
 4.1.0 and higher might not be supported by the DRI included in older Linux
 kernels. Also newer 2.4.x kernels from 2.4.8 up to 2.4.17 do not support DRI in
 XFree86-4.0.x.
@ -201,12 +204,12 @@ class="pcrr7t---109">&gt; agpgart: AGP aperture is 64M @ 0xe4000000</span>
 missed the right chip set. Part one of activation hardware accelerated OpenGL support on
 your Linux system is now completed.
 <!--l. 237--><p class="indent">   The second part consists of configuring your X server<a 
-  name="dx13-64008"></a> for OpenGL. This is not a big
+  name="dx13-78008"></a> for OpenGL. This is not a big
 deal as it simply consists of to instructions to load the appropriate modules on startup of
 the X server. This is done by editing the configuration file <span 
 class="pcrr7t---109">/etc/X11/XF86Config</span>.
 Today&#8217;s Linux distributions are supposed to provide a tool that does this job
-for you on your demand. Please make shure there are these two instructions:
+for you on your demand. Please make sure there are these two instructions:
 <!--l. 246--><p class="indent">   <span 
 class="pcrr7t---109">Load ''glx''</span>
@ -215,7 +218,7 @@ class="pcrr7t---109">Load ''glx''</span>
 <!--l. 248--><p class="indent">   <span 
 class="pcrr7t---109">Load ''dri''</span>
 <!--l. 251--><p class="noindent">in the &#8221;Module&#8221; section your X server<a 
-  name="dx13-64009"></a> configuration file. If everything is right
+  name="dx13-78009"></a> configuration file. If everything is right
 the X server will take care of loading the appropriate Linux kernel module for
 DRI support of your graphics card. The right Linux kernel module name is
 determined by the &#8217;Driver&#8217; statement in the &#8221;Device&#8221; section of the XF86Config.
@ -274,9 +277,9 @@ class="pcrr7t---109">VendorName ''ATI''</span>
 class="pcrr7t---109">EndSection</span>
   By using the Option &#8221;AGPMode&#8221; you can tune AGP performance as long as the
 mainboard and the graphics card permit. The BusID on AGP<a 
-  name="dx13-64010"></a> systems should always be
+  name="dx13-78010"></a> systems should always be
 set to &#8221;1:0:0&#8221; - because you only have one AGP slot on your board - whereas the PCI<a 
-  name="dx13-64011"></a>
+  name="dx13-78011"></a>
 BusID differs with the slot your graphics card has been applied to. &#8217;lspci&#8217; might be your
@ -287,102 +290,106 @@ resides.
 <!--l. 334--><p class="indent">   This has been the second part of installing hardware accelerated OpenGL support on
 your Linux box.
 <!--l. 337--><p class="indent">   The third part carries two subparts: First there are the OpenGL runtime libraries,<a 
-  name="dx13-64012"></a>
+  name="dx13-78012"></a>
 sufficient to run existing appliactions. For compiling FlightGear you also need the suiting
-develoment headers. As compiling the whole X window system is not subject to this
+developmental headers. As compiling the whole X window system is not subject to this
 abstract we expect that your distribution ships the necessary libraries and headers. In case
 you told your package manager to install some sort of OpenGL support you are
 supposed to find some OpenGL test utilities, at least there should be &#8217;glxinfo&#8217; or
 &#8217;gl-info&#8217;.
-<!--l. 346--><p class="indent">   These commandline utilities are useful to say if the previous steps where successfull.
+<!--l. 345--><p class="indent">   These command-line utilities are useful to say if the previous steps where
-If they refuse to start, then your package manager missed something because he should
+successfull. If they refuse to start, then your package manager missed something because
-have known that these utilities usually depend on the existence of OpenGL runtime
+he should have known that these utilities usually depend on the existence of OpenGL
-libraries. If they start, then you&#8217;re one step ahead. Now watch the output of this tool and
+runtime libraries. If they start, then you&#8217;re one step ahead. Now watch the output of this
-and have a look at the line that starts with
+tool and and have a look at the line that starts with
-<!--l. 353--><p class="indent">   OpenGL renderer string<a 
+<!--l. 352--><p class="indent">   OpenGL renderer string<a 
-  name="dx13-64013"></a>:
+  name="dx13-78013"></a>:
-<!--l. 355--><p class="indent">   If you find something like
+<!--l. 354--><p class="indent">   If you find something like
-<!--l. 358--><p class="indent">   <span 
+<!--l. 357--><p class="indent">   <span 
 class="pcrr7t---109">OpenGL renderer string: FireGL2 / FireGL3 (Pentium3)</span>
-<!--l. 361--><p class="noindent">or
+<!--l. 360--><p class="noindent">or
-<!--l. 365--><p class="indent">   <span 
+<!--l. 364--><p class="indent">   <span 
 class="pcrr7t---109">OpenGL renderer string: Mesa DRI Voodoo3 20000224</span>
-<!--l. 368--><p class="noindent">or
+<!--l. 367--><p class="noindent">or
-<!--l. 372--><p class="indent">   <span 
+<!--l. 371--><p class="indent">   <span 
 class="pcrr7t---109">OpenGL renderer string: Mesa DRI Radeon 20010402</span>
-<!--l. 374--><p class="indent">   <span 
+<!--l. 373--><p class="indent">   <span 
 class="pcrr7t---109">AGP 4x x86</span>
-<!--l. 377--><p class="indent">   <span 
+<!--l. 376--><p class="indent">   <span 
 class="pcrr7t---109">OpenGL renderer string: Mesa GLX Indirect</span>
-<!--l. 380--><p class="noindent">mind the word &#8217;Indirect&#8217;, then it&#8217;s you who missed something, because OpenGL gets
+<!--l. 379--><p class="noindent">mind the word &#8217;Indirect&#8217;, then it&#8217;s you who missed something, because OpenGL gets
 dealt with in a software library running solely on your CPU. In this case you might want
-to have a closer look at the preceding paragraphs of this chapter. Now please make
+to have a closer look at the preceding paragraphs of this chapter. Now please
-shure all necessary libraries are at their proper location. You will need three
+make sure all necessary libraries are at their proper location. You will need three
-OpenGL libraries for running FlightGear. In most cases you will find them in
+OpenGL libraries for running <span 
 class="ptmbi7t---109">FlightGear</span>. In most cases you will find them in
 /usr/lib/:
-<!--l. 389--><p class="indent">   <span 
+<!--l. 388--><p class="indent">   <span 
 class="pcrr7t---109">/usr/lib/libGL.so.1</span>
-<!--l. 391--><p class="indent">   <span 
+<!--l. 390--><p class="indent">   <span 
 class="pcrr7t---109">/usr/lib/libGLU.so.1</span>
-<!--l. 393--><p class="indent">   <span 
+<!--l. 392--><p class="indent">   <span 
 class="pcrr7t---109">/usr/lib/libglut.so.3</span>
-<!--l. 395--><p class="indent">   These may be the libraries itself or symlinks to appropriate libraries located in some
+<!--l. 394--><p class="indent">   These may be the libraries itself or symlinks to appropriate libraries located in some
 other directories. Depending on the distribution you use these libraries might be shipped
 in different packages. SuSE<a 
-  name="dx13-64014"></a> for example ships libGL in package &#8217;xf86_glx&#8217;, libGLU in
+  name="dx13-78014"></a> for example ships libGL in package &#8217;xf86_glx&#8217;, libGLU in
-&#8217;xf86glu&#8217; and libglut in &#8217;mesaglut&#8217;. Additionally for FlightGear you need libplib which is
+&#8217;xf86glu&#8217; and libglut in &#8217;mesaglut&#8217;. Additionally for <span 
-part of the &#8217;plib&#8217; package.
+class="ptmbi7t---109">FlightGear </span>you need libplib which
-<!--l. 402--><p class="indent">   For compiling FlightGear yourself - as already mentioned - you need the appropriate
+is part of the &#8217;plib&#8217; package.
 <!--l. 401--><p class="indent">   For compiling <span 
 class="ptmbi7t---109">FlightGear </span>yourself - as already mentioned - you need the appropriate
 header files which often reside in /usr/include/GL/. Two are necessary for libGL and they
 come in - no, not &#8217;xf86glx-devel&#8217; (o.k., they do but they do not work correctly) but in
 &#8217;mesa-devel&#8217;:
-<!--l. 408--><p class="indent">   <span 
+<!--l. 407--><p class="indent">   <span 
 class="pcrr7t---109">/usr/include/GL/gl.h</span>
-<!--l. 410--><p class="indent">   <span 
+<!--l. 409--><p class="indent">   <span 
 class="pcrr7t---109">/usr/include/GL/glx.h</span>
-<!--l. 413--><p class="noindent">One comes with libGLU in &#8217;xf86glu-devel&#8217;:
+<!--l. 412--><p class="noindent">One comes with libGLU in &#8217;xf86glu-devel&#8217;:
-<!--l. 417--><p class="indent">   <span 
+<!--l. 416--><p class="indent">   <span 
 class="pcrr7t---109">/usr/include/GL/glu.h</span>
-<!--l. 420--><p class="indent">   and one with libglut in &#8217;mesaglut-devel&#8217;
+<!--l. 419--><p class="indent">   and one with libglut in &#8217;mesaglut-devel&#8217;
-<!--l. 423--><p class="indent">   <span 
+<!--l. 422--><p class="indent">   <span 
 class="pcrr7t---109">/usr/include/GL/glut.h</span>
-<!--l. 426--><p class="indent">   The &#8217;plib&#8217; package comes with some more libraries and headers that are too
+<!--l. 425--><p class="indent">   The &#8217;plib&#8217; package comes with some more libraries and headers that are too
 many to be mentioned here. If all this is present and you have a comfortable
-compiler environment, then you are ready to compile FlightGear and enjoy the
+compiler environment, then you are ready to compile <span 
 class="ptmbi7t---109">FlightGear </span>and enjoy the
 result.
-<!--l. 432--><p class="indent">   Further information on OpenGL<a 
+<!--l. 431--><p class="indent">   Further information on OpenGL<a 
-  name="dx13-64015"></a> issues of specific XFree86<a 
+  name="dx13-78015"></a> issues of specific XFree86<a 
-  name="dx13-64016"></a> releases is avaliable here:
+  name="dx13-78016"></a> releases is available here:
-<!--l. 436--><p class="indent">   <span class="underline">http://www.xfree86.org/<span 
+<!--l. 435--><p class="indent">   <span class="underline">http://www.xfree86.org/<span 
 class="cmmi-10--109">&lt;</span>RELEASE NUMBER<span 
 class="cmmi-10--109">&gt;</span>/DRI.html</span>
-<!--l. 440--><p class="noindent">Additional reading on DRI<a 
+<!--l. 439--><p class="noindent">Additional reading on DRI<a 
-  name="dx13-64017"></a>:
+  name="dx13-78017"></a>:
-<!--l. 444--><p class="indent">   <a 
+<!--l. 443--><p class="indent">   <a 
 href="http://www.precisioninsight.com/piinsights.html" >http://www.precisioninsight.com/piinsights.html</a>
-<!--l. 447--><p class="noindent">In case you are missing some &#8217;spare parts&#8217;:
+<!--l. 446--><p class="noindent">In case you are missing some &#8217;spare parts&#8217;:
-<!--l. 451--><p class="indent">   <a 
+<!--l. 450--><p class="indent">   <a 
 href="http://dri.sourceforge.net/res.phtml" >http://dri.sourceforge.net/res.phtml</a>
   <h3 class="sectionHead"><span class="titlemark">B.8</span> <a 
-href="getstart.html#QQ2-13-65" name="x13-65000B.8">OpenGL on MacIntosh</a></h3>
+href="getstart.html#QQ2-13-79" name="x13-79000B.8">OpenGL on Macintosh</a></h3>
 <a 
-  name="dx13-65001"></a>
+  name="dx13-79001"></a>
-<!--l. 458--><p class="noindent">OpenGL is pre-installed on Mac OS 9.x and later. You may find a newer version than the
+<!--l. 457--><p class="noindent">OpenGL is pre-installed on Mac OS 9.x and later. You may find a newer version than the
 one installed for Mac OS 9.x<a 
-  name="dx13-65002"></a> at
+  name="dx13-79002"></a> at
-<!--l. 461--><p class="indent">   <a 
+<!--l. 460--><p class="indent">   <a 
 href="http://www.apple.com/opengl" >http://www.apple.com/opengl</a>
-<!--l. 464--><p class="indent">   You should receive the updates automatically for Mac OX 10.x<a 
+<!--l. 463--><p class="indent">   You should receive the updates automatically for Mac OSX<a 
-  name="dx13-65003"></a>.
+  name="dx13-79003"></a>.
-<!--l. 467--><p class="noindent"><span 
+<!--l. 466--><p class="noindent"><span 
 class="ptmb7t---109">One final word: </span>We would recommend that you test your OpenGL<a 
-  name="dx13-65004"></a> support with one
+  name="dx13-79004"></a> support with one
 of the programs that accompany the drivers, to be absolutely confident that
 it is functioning well. There are also many little programs, often available as
 screen savers, that can be used for testing. It is important that you are confident
--- a/Docs/InstallGuide/html/getstartap3.html
+++ b/Docs/InstallGuide/html/getstartap3.html
--- a/Docs/InstallGuide/html/getstartch1.html
+++ b/Docs/InstallGuide/html/getstartch1.html
@ -6,7 +6,7 @@
 <meta name="generator" content="TeX4ht (http://www.cis.ohio-state.edu/~gurari/TeX4ht/mn.html)"> 
 <!-- html,2,info,next,sections+ --> 
 <meta name="src" content="getstart.tex"> 
-<meta name="date" content="2002-02-16 19:41:00"> 
+<meta name="date" content="2002-09-08 00:44:00"> 
 <link rel="stylesheet" type="text/css" href="getstart.css"> 
 </head><body 
 >
@ -20,228 +20,253 @@ href="getstartpa1.html#getstartch1.html" >up</a>] </p></div>
 href="getstart.html#QQ2-5-4" name="x5-40001">Want to have a free flight? Take <span 
 class="ptmbi7t---109">FlightGear</span>!</a></h2>
   <h3 class="sectionHead"><span class="titlemark">1.1</span> <a 
-href="getstart.html#QQ2-5-5" name="x5-50001.1">Yet another Flight Simulator?</a></h3>
+href="getstart.html#QQ2-5-5" name="x5-50001.1">Yet Another Flight Simulator?</a></h3>
-<!--l. 37--><p class="noindent">Did you ever want to fly a plane yourself, but lacked the money or ability to do so? Are
+<!--l. 37--><p class="noindent">Did you ever want to fly a plane yourself, but lacked the money or ability to
-you a real pilot looking to improve your skills without having to take off? Do you want to
+do so? Are you a real pilot looking to improve your skills without having to
-try some dangerous maneuvers without risking your life? Or do you just want to have fun
+take off? Do you want to try some dangerous maneuvers without risking your
-with a more serious game not killing any people? If any of these questions applies, PC
+life? Or do you just want to have fun with a more serious game without any
-flight simulators are just for you.
+violence? If any of these questions apply to you, PC flight simulators are just for
-<!--l. 43--><p class="indent">   You already may have some experience using Microsoft<a 
+you.
 <!--l. 43--><p class="indent">   You may already have some experience using Microsoft<a 
  name="dx5-5001"></a>&#8217;s &copy; Flight Simulator or any
 other of the commercially available PC flight simulators. As the price tag of those is
 usually within the $50 range buying one of them should not be a serious problem given
 that running any serious PC flight simulator requires a hardware within the $1500 range,
 despite dropping prices, at least.
-<!--l. 48--><p class="indent">   Why then that effort of spending hundreds or thousands of hours of programming to
+usually within the $50 range, buying one of them should not be a serious problem given
-build a free simulator? Obviously there must be good reason to do so:
+that running any serious PC flight simulator requires PC hardware within the $1500
 range, despite dropping prices.
 <!--l. 49--><p class="indent">   With so many commercially available flight simulators, why would we spend
 thousands of hours of programming and design work to build a free flight simulator?
 Well, there are many reasons, but here are the major ones:
     <ul class="itemize1">
-     <li class="itemize">All of the commercial programs have a serious drawback: They are made
+     <li class="itemize">All of the commercial simulators have a serious drawback: they are made
-     by a small group of developers defining their properties - often quite inert
+     by a small group of developers defining their properties according to what
-     and not listening too much to the customer. Anyone ever trying to contact
+     is important to them and providing limited interfaces to end users. Anyone
-     Microsoft<a 
+     who  has  ever  tried  to  contact  a  commercial  developer  would  agree  that
-  name="dx5-5002"></a> will immediately agree.
+     getting your voice heard in that environment is a major challenge. In contrast,
     </li>
     <li class="itemize">Commercial PC flight simulators usually try to cover a market segment as
     broad as possible. For obvious reason, most of them want to serve the serious
     pilot as well as the beginner and the gamer. The result is a compromise. As
     <span 
-class="ptmbi7t---109">FlightGear </span>is free, there is no need for such compromise; it just can be given
+class="ptmbi7t---109">FlightGear </span>is designed by the people and for the people with everything out
-     the properties its users want. It defines itself via building.
+     in the open.
     </li>
-     <li class="itemize">Building  a  flight  simulator  is  a  challenge  to  the  art  of  programming.
+     <li class="itemize">Commercial simulators are usually a compromise of features and usability.
-     Contributing  to  that  project  makes  you  belong  to  those  being  able  to
+     Most commercial developers want to be able to serve a broad segment of
-     contribute to serious, ambitious and advanced software projects.
+     the population, including serious pilots, beginners, and even casual gamers.
     In reality the result is always a compromise due to deadlines and funding.
     As <span 
 class="ptmbi7t---109">FlightGear </span>is free and open, there is no need for such a compromise.
     We have no publisher breathing down our necks, and we&#8217;re all volunteers
     that make our own deadlines. We are also at liberty to support markets that
     no commercial developer would consider viable, like the scientific research
     community.
     </li>
-     <li class="itemize">It is fun. Not only is it fun to write the code (. . . or documentation. . . ) but
+     <li class="itemize">Due to their closed-source nature, commercial simulators keep developers
-     also to belong to that - temporarily changing - club of clever people on the
+     with  excellent  ideas  and  skills  from  contributing  to  the  products.  With
     net having discussed, struggled and finally succeeded in creating that project.
     Even reading the <span 
 class="ptmbi7t---109">FlightGear </span>mailing lists is informative and fun for itself.</li></ul>
 <!--l. 75--><p class="noindent">The above-mentioned points make <span 
 class="ptmbi7t---109">FlightGear </span>superior to its competitors in several
 respect. <span 
 class="ptmbi7t---109">FlightGear </span>aims to be a civilian,<a 
  name="dx5-5003"></a> multi-platform,<a 
  name="dx5-5004"></a> open,<a 
  name="dx5-5005"></a> user-supported,<a 
  name="dx5-5006"></a>
 user-extensible<a 
  name="dx5-5007"></a> platform.
 <!--l. 84--><p class="indent">   <div align="center" 
 class="centerline"><img 
 src="getstart1x.gif" alt=""  class="fbox" > </div>
 <!--l. 87--><p class="noindent">Fig. 1: <span 
 class="ptmbi7t---109">FlightGear </span><span 
 class="ptmri7t---109">under UNIX: Bad approach to San Francisco International - by one of</span>
     <span 
-class="ptmri7t---109">the authors of this manual. . .</span>
+class="ptmbi7t---109">FlightGear</span>, developers of all skill levels and ideas have the potential to make
     a huge impact on the project. Contributing to a project as large and complex
     as <span 
 class="ptmbi7t---109">FlightGear </span>is very rewarding and provides the developers with a great
     deal of pride in knowing that we are shaping the future of a great simulator.
     </li>
     <li class="itemize">Beyond everything else, it&#8217;s just plain fun! I suppose you could compare us
     to real pilots that build kit-planes or scratch-builts. Sure, we can go out a
     buy a pre-built aircraft, but there&#8217;s just something special about building one
     yourself.</li></ul>
 <!--l. 83--><p class="noindent">The points mentioned above form the basis of why we created <span 
 class="ptmbi7t---109">FlightGear</span>. With those
 motivations in mind, we have set out to create a high-quality flight simulator that aims to
 be a civilian,<a 
  name="dx5-5002"></a> multi-platform,<a 
  name="dx5-5003"></a> open,<a 
  name="dx5-5004"></a> user-supported,<a 
  name="dx5-5005"></a> and user-extensible<a 
  name="dx5-5006"></a> platform. Let us
 take a closer look at each of these characteristics:
     <ul class="itemize1">
     <li class="itemize"><span 
 class="ptmb7t---109">Civilian:</span><a 
-  name="dx5-5008"></a>  The  project  is  primarily  aimed  at  civilian  flight  simulation.  It
+  name="dx5-5007"></a>  The  project  is  primarily  aimed  at  civilian  flight  simulation.  It
     should  be  appropriate  for  simulating  general  aviation  as  well  as  civilian
-     aircraft.  It  is  not  a  shoot&#8217;m-up  game.  However,  in  keeping  with  the  open
+     aircraft. Our long-term goal is to have <span 
-     concept of development, this naturally does not exclude someone taking the
+class="ptmbi7t---109">FlightGear </span>FAA-approved as a flight
-     code and integrating say weapon systems<a 
+     training  device.  To  the  disappointment  of  some  users,  it  is  currently  not
-  name="dx5-5009"></a>, for instance.
+     a  combat  simulator;  however,  these  features  are  not  explicitly  excluded.
     We just have not had a developer that was seriously interested in systems
     necessary for combat simulation.
     </li>
     <li class="itemize"><span 
 class="ptmb7t---109">Multi-platform:</span><a 
-  name="dx5-5010"></a> The developers are attempting to keep the code as
+  name="dx5-5008"></a> The developers are attempting to keep the code as
     platform-independent as possible. This is based on their observation that people
     interested in flight simulations run quite a variety of computer hardware and
     operating systems. The present code supports the following Operating
     Systems<a 
-  name="dx5-5011"></a>:
+  name="dx5-5009"></a>:
          <ul class="itemize2">
          <li class="itemize">Linux<a 
-  name="dx5-5012"></a> (any distribution and platform),
+  name="dx5-5010"></a> (any distribution and platform),
          </li>
          <li class="itemize">Windows NT/2000/XP<a 
-  name="dx5-5013"></a> (Intel/AMD platform),
+  name="dx5-5011"></a> (Intel/AMD platform),
          </li>
          <li class="itemize">Windows 95/98/ME<a 
-  name="dx5-5014"></a>,
+  name="dx5-5012"></a>,
          </li>
          <li class="itemize">BSD UNIX<a 
-  name="dx5-5015"></a>,
+  name="dx5-5013"></a>,
          </li>
          <li class="itemize">SGI IRIX<a 
-  name="dx5-5016"></a>,
+  name="dx5-5014"></a>,
          </li>
          <li class="itemize">Sun-OS<a 
-  name="dx5-5017"></a>,
+  name="dx5-5015"></a>,
          </li>
          <li class="itemize">Macintosh.</li></ul>
-     <!--l. 117--><p class="noindent">At present, there is no known flight simulator - commercial or free - supporting
+     <!--l. 115--><p class="noindent">At present, there is no known flight simulator - commercial or free - supporting
     such a broad range of platforms.
     </li>
     <li class="itemize"><span 
 class="ptmb7t---109">Open:</span><a 
-  name="dx5-5018"></a> The project is not restricted to a static or elite cadre of developers. Anyone
+  name="dx5-5016"></a> The project is not restricted to a static or elite cadre of developers. Anyone
-     who feels he or she is able to contribute is most welcome. The code (including
+     who feels they are able to contribute is most welcome. The code (including
-     documentation) is copyrighted under the terms of the GPL<a 
+                                                                     
-  name="dx5-5019"></a> (Gnu Public
+
-     License<a 
+                                                                     
-  name="dx5-5020"></a>).
+     documentation) is copyrighted under the terms of the GNU General Public License<a 
-     <!--l. 126--><p class="noindent">The GPL<a 
+  name="dx5-5017"></a>
-  name="dx5-5021"></a> is often misunderstood. In simple terms it states that you can copy and
+     (GPL<a 
-     freely distribute the program(s) so licensed. You can modify them if you like. You
+  name="dx5-5018"></a>).
-     are even allowed to charge as much money for the distribution of the modified or
+     <!--l. 123--><p class="noindent">The GPL<a 
-     original program as you want. However, you must distribute it complete with the
+  name="dx5-5019"></a> is often misunderstood. In simple terms it states that you can copy and
-     entire source code and it must retain the original copyrights. In short:
+     freely distribute the program(s) so licensed. You can modify them if you like and
-     <!--l. 134--><p class="noindent"><div align="center" 
+     even charge as much money as want to for the distribution of the modified or
     original program. However, you must freely provide the entire source code to
     anyone who wants it, and it must retain the original copyrights. In short:
     <!--l. 131--><p class="noindent"><div align="center" 
 class="centerline">             <span 
 class="ptmri7t---109">&#8221;You can do anything with the software except make it non-free&#8221;</span>.             </div>
-     <!--l. 136--><p class="noindent">The full text of the GPL<a 
+     <!--l. 133--><p class="noindent">The full text of the GPL<a 
-  name="dx5-5022"></a> can be obtained from
+  name="dx5-5020"></a> can be obtained from the <span 
-     <!--l. 139--><p class="noindent"><a 
+class="ptmbi7t---109">FlightGear </span>source code or from
     <!--l. 136--><p class="noindent"><a 
 href="http://www.gnu.org/copyleft/gpl.html" >http://www.gnu.org/copyleft/gpl.html</a>.
     </li>
     <li class="itemize"><span 
-class="ptmb7t---109">User-supported, user-extensible:</span><a 
+class="ptmb7t---109">User-supported and user-extensible:</span><a 
-  name="dx5-5023"></a> <a 
+  name="dx5-5021"></a> <a 
-  name="dx5-5024"></a>Contrary to various commercial simulators
+  name="dx5-5022"></a>Unlike most commercial simulators,
-     available, scenery and aircraft format, internal variables, etc. are user
+     <span 
-     accessible and documented from the beginning. Even without an explicit
+class="ptmbi7t---109">FlightGear</span>&#8221;s scenery and aircraft formats, internal variables, APIs, and everything
-     development documentation<a 
+     else are user accessible and documented from the beginning. Even without any
-  name="dx5-5025"></a> (which naturally has to be written at some
+     explicit development documentation<a 
-     point) this is guaranteed by supplying the source code<a 
+  name="dx5-5023"></a> (which naturally has to be written at
-  name="dx5-5026"></a>. It is the goal of the
+     some point), one can always go to the source code<a 
-     developers to build a basic engine to which scenery designers, panel engineers,
+  name="dx5-5024"></a> to see how something
-     maybe adventure or ATC routine writers, sound artists, and others can (and
+     works. It is the goal of the developers to build a basic engine to which
-                                                                     
+     scenery designers, panel engineers, maybe adventure or ATC routine
-
+     writers, sound artists, and others can build upon. It is our hope that the
-                                                                     
+     project, including the developers and end users, will benefit from the
     are solicited to) add. It is our hope, that the project will benefit from the
     creativity and ideas of the hundreds of talented &#8221;simmers&#8221; around the
     world.</li></ul>
-<!--l. 155--><p class="noindent">Without doubt, the success of the Linux<a 
+<!--l. 152--><p class="noindent">Without doubt, the success of the Linux<a 
-  name="dx5-5027"></a> project initiated by Linus Torvalds<a 
+  name="dx5-5025"></a> project, initiated by Linus Torvalds,<a 
-  name="dx5-5028"></a> inspired
+  name="dx5-5026"></a> inspired
-several of the developers. Not only has it shown that distributed development of even
+several of the developers. Not only has Linux<a 
-highly sophisticated software projects over the Internet is possible.
+  name="dx5-5027"></a> shown that distributed development of
 highly sophisticated software projects over the Internet is possible, it has also proven that
 such an effort can surpass the level of quality of competing commercial products.
 <!--l. 162--><p class="indent">   <div align="center" 
 class="centerline"><img 
 src="getstart1x.gif" alt=""  class="fbox" > </div>
 <!--l. 165--><p class="noindent">Fig. 1: <span 
 class="ptmbi7t---109">FlightGear </span><span 
 class="ptmri7t---109">under UNIX: Bad approach to San Francisco International - by one of</span>
 <span 
 class="ptmri7t---109">the authors of this manual. . .</span>
   <h3 class="sectionHead"><span class="titlemark">1.2</span> <a 
-href="getstart.html#QQ2-5-6" name="x5-60001.2">System requirements</a></h3>
+href="getstart.html#QQ2-5-6" name="x5-60001.2">System Requirements</a></h3>
 <a 
  name="dx5-6001"></a>
-<!--l. 164--><p class="noindent">In comparison to other recent flight simulators the system requirements<a 
+<!--l. 171--><p class="noindent">In comparison to other recent flight simulators, the system requirements<a 
  name="dx5-6002"></a> for <span 
 class="ptmbi7t---109">FlightGear</span>
-are not extravagant. A decent PII/400 or something in that range should be sufficient,
+are not extravagant. A decent PIII/800, or something in that range, should be
-given you have a proper 3-D graphics card<a 
+sufficient given you have a proper 3-D graphics card<a 
-  name="dx5-6003"></a>. On the other hand, any modern
+  name="dx5-6003"></a>. Additionally, any modern
 UNIX<a 
  name="dx5-6004"></a>-type workstation<a 
-  name="dx5-6005"></a> with a 3D graphics card will handle <span 
+  name="dx5-6005"></a> with a 3-D graphics card will handle <span 
 class="ptmbi7t---109">FlightGear </span>as
 well.
-<!--l. 170--><p class="indent">   One important prerequisite for running <span 
+<!--l. 177--><p class="indent">   One important prerequisite for running <span 
 class="ptmbi7t---109">FlightGear </span>is a graphics card whose driver
 supports OpenGL<a 
  name="dx5-6006"></a>. If you don&#8217;t know what OpenGL<a 
  name="dx5-6007"></a> is, the overview given at the
 OpenGL website
-<!--l. 174--><p class="indent">   <a 
+<!--l. 181--><p class="indent">   <a 
 href="http://www.opengl.org" >http://www.opengl.org</a>
-<!--l. 177--><p class="noindent">says it best: &#8221;Since its introduction in 1992, OpenGL has become the industry&#8217;s most
+<!--l. 184--><p class="noindent">says it best: &#8220;Since its introduction in 1992, OpenGL has become the industry&#8217;s most
 widely used and supported 2-D and 3-D graphics application programming interface
 (API)...&#8221;.
-<!--l. 182--><p class="indent">   <span 
+<!--l. 189--><p class="indent">   <span 
-class="ptmbi7t---109">FlightGear </span>does not run (and will never run) on a graphics board supporting
+class="ptmbi7t---109">FlightGear </span>does not run (and will never run) on a graphics board which only
-Direct3D<a 
+                                                                     
-  name="dx5-6008"></a> only. Contrary to openGL, Direct3D is a proprietary interface, being restricted
+
-to the Windows operating system.
+                                                                     
-<!--l. 184--><p class="indent">   You may be able to run <span 
+supports Direct3D<a 
  name="dx5-6008"></a>. Contrary to OpenGL, Direct3D is a proprietary interface, being
 restricted to the Windows operating system.
 <!--l. 193--><p class="indent">   You may be able to run <span 
 class="ptmbi7t---109">FlightGear </span>on a computer that features a 3-D video card
 not supporting hardware accelerated OpenGL<a 
  name="dx5-6009"></a> - and even on systems without
 3-D graphics hardware at all. However, the absence of hardware accelerated
-OpenGL support can force even the fastest machine to its knees. The typical
+OpenGL support can bring even the fastest machine to its knees. The typical
 signal for missing hardware acceleration are frame rate<a 
  name="dx5-6010"></a>s below 1 frame per
 second.
-<!--l. 190--><p class="indent">   Any more recent 3-D graphics featuring hardware OpenGL<a 
+<!--l. 198--><p class="indent">   Any modern 3-D graphics featuring OpenGL<a 
-  name="dx5-6011"></a> will do. For Windows<a 
+  name="dx5-6011"></a> support will do. For Windows<a 
-  name="dx5-6012"></a>
+  name="dx5-6012"></a> video
-video card drivers that support OpenGL, visit the home page of your video card
+card drivers that support OpenGL, visit the home page of your video card manufacturer.
-manufacturer. You should note, that sometimes OpenGL drivers<a 
+You should note that sometimes OpenGL drivers<a 
-  name="dx5-6013"></a> are provided by the
+  name="dx5-6013"></a> are provided by the manufacturers of
-manufacturers of the graphics chip instead of by the makers of the board. If you are
+the graphics chip instead of by the makers of the board. If you are going to buy a
-going to buy a graphics card for running <span 
+graphics card for running <span 
-class="ptmbi7t---109">FlightGear</span>, one based on a NVIDIA chip (TNT
+class="ptmbi7t---109">FlightGear</span>, one based on a NVIDIA chip (TNT X/Geforce X)
-X/Geforce X) might be a good choice.
+might be a good choice.
-                                                                     
+<!--l. 205--><p class="indent">   To install the executable and basic scenery, you will need around 50 MB of free disk
 <!--l. 197--><p class="indent">   To install the executable and basic scenery, you will need around 50 MB of free disk
 space<a 
-  name="dx5-6014"></a>. In case you want/have to to compile the program yourself you will need additional
+  name="dx5-6014"></a>. In case you want/have to to compile the program yourself you will need about an
-about 500 MB for the source code and for temporary files created during compilation.
+additional 500 MB for the source code and for temporary files created during
-This does not yet include the development environment, which possibly may have to be
+compilation. This does not include the development environment, which will vary in size
-installed under Windows yet, and which amounts to additional around 300 MB,
+depending on the operating system and environment being used. Windows users can
-depending on the installed packages.
+expect to need approximately 300 MB of additional disk space for the development
-<!--l. 202--><p class="indent">   For the sound effects<a 
+environment. Linux and other UNIX machines should have most of the development
-  name="dx5-6015"></a> any capable sound card<a 
+tools already installed, so there is likely to be little additional space needed on those
-  name="dx5-6016"></a> should suffice. Based on its flexible
+platforms.
-concept, <span 
+<!--l. 214--><p class="indent">   For the sound effects<a 
  name="dx5-6015"></a>, any capable sound card<a 
  name="dx5-6016"></a> should suffice. Due to its flexible
 design, <span 
 class="ptmbi7t---109">FlightGear </span>supports a wide range of joysticks<a 
-  name="dx5-6017"></a> or yokes<a 
+  name="dx5-6017"></a> and yokes<a 
-  name="dx5-6018"></a> as well esd rudder
+  name="dx5-6018"></a> as well as rudder pedals<a 
-pedals<a 
+  name="dx5-6019"></a>
-  name="dx5-6019"></a> under Linux<a 
+under Linux<a 
-  name="dx5-6020"></a> as well as under Windows<a 
+  name="dx5-6020"></a> and Windows<a 
-  name="dx5-6021"></a>.
+  name="dx5-6021"></a>. <span 
-<!--l. 205--><p class="indent">   <span 
+class="ptmbi7t---109">FlightGear </span>can also provide interfaces to full-motion flight
 chairs.
 <!--l. 219--><p class="indent">   <span 
 class="ptmbi7t---109">FlightGear </span>is being developed primarily under Linux<a 
  name="dx5-6022"></a>, a free UNIX clone (together
 with lots of GNU utilities) developed cooperatively over the Internet in much the same
@ -250,80 +275,85 @@ class="ptmbi7t---109">FlightGear </span>itself. <span
 class="ptmbi7t---109">FlightGear </span>also runs and is partly developed under several
 flavors of Windows<a 
  name="dx5-6023"></a>. Building <span 
-class="ptmbi7t---109">FlightGear </span>is possible on a Macintosh (OSX) and on
+class="ptmbi7t---109">FlightGear </span>is also possible on a Macintosh OSX and
-several UNIX/X11 workstations, as well. Given you have a proper compiler<a 
+several different UNIX/X11 workstations. Given you have a proper compiler<a 
  name="dx5-6024"></a> installed,
 <span 
-class="ptmbi7t---109">FlightGear </span>can be built under all of these platforms. The primary compiler
+class="ptmbi7t---109">FlightGear </span>can be built under all of these platforms. The primary compiler for all
-for all platforms is the free GNU C++<a 
+platforms is the free GNU C++<a 
  name="dx5-6025"></a> compiler (the Cygnus<a 
-  name="dx5-6026"></a>compiler under
+  name="dx5-6026"></a> Cygwin<a 
  name="dx5-6027"></a> compiler under
 Win32).
-<!--l. 212--><p class="indent">   If you want to run <span 
+<!--l. 227--><p class="indent">   If you want to run <span 
 class="ptmbi7t---109">FlightGear </span>under Mac OSX we suggest a Power PC G3 300 MHz
 or better. As a graphics card we would suggest an ATI Rage 128 based card as a
 minimum. Joysticks are supported under Mac OS 9.x only; there is no joystick support
-under Max OSX available (yet).
+under Max OSX at this time.
   <h3 class="sectionHead"><span class="titlemark">1.3</span> <a 
-href="getstart.html#QQ2-5-7" name="x5-70001.3">Which version should I use?</a></h3>
+href="getstart.html#QQ2-5-7" name="x5-70001.3">Choosing A Version</a></h3>
 <a 
  name="dx5-7001"></a>
-<!--l. 219--><p class="noindent">Concerning the <span 
+<!--l. 236--><p class="noindent">Concerning the <span 
-class="ptmbi7t---109">FlightGear </span>source code there exist two branches, a stable one and a
+class="ptmbi7t---109">FlightGear </span>source code there exist two branches, a stable branch and a
 developmental branch.<a 
  name="dx5-7002"></a><a 
  name="dx5-7003"></a> Even version numbers like 0.6, 0.8, and (someday hopefully) 1.0
 refer to stable releases, while odd numbers like 0.7, 0.9, and so on refer to developmental
 releases. The policy is to only do bug fixes in the even versions, while new features are
 generally added to odd-numbered versions which, after all things have stabilized, will
-become the next stable release with a version number calculated by adding 0.1.
+become the next stable release with a version number calculated by adding
-<!--l. 225--><p class="indent">   To add to the confusion, there usually are several versions of the &#8221;unstable&#8221; branch.
+0.1.
 <!--l. 244--><p class="indent">   To add to the confusion, there usually are several versions of the &#8221;unstable&#8221; branch.
 First, there is a &#8221;latest official release&#8221; which the pre-compiled binaries are based on. It is
 available from
-<!--l. 230--><p class="indent">   <a 
+<!--l. 249--><p class="indent">   <a 
-href="ftp://ftp.flightgear.org/pub/fgfs/Source/FlightGear-X.X.X.tar.gz" ></a>
+href="ftp://ftp.flightgear.org/pub/fgfs/Source/FlightGear-X.Y.Z.tar.gz" >ftp://ftp.flightgear.org/pub/fgfs/Source/FlightGear-X.Y.Z.tar.gz</a>
-<!--l. 232--><p class="indent">   For developers there exist CVS snapshots<a 
+<!--l. 252--><p class="indent">   For developers there exist CVS snapshots<a 
  name="dx5-7004"></a><a 
  name="dx5-7005"></a> of the source code, available from
-                                                                     
+<!--l. 256--><p class="indent">   <a 
 <!--l. 235--><p class="indent">   <a 
 href="ftp://www.flightgear.org/pub/flightgear/Devel/Snapshots/" >ftp://www.flightgear.org/pub/flightgear/Devel/Snapshots/</a>.
-<!--l. 238--><p class="noindent">While theses are quite recent, they may still be sometimes a few days back behind
+<!--l. 259--><p class="noindent">While theses are quite recent, they may still be sometimes a few days back behind
 development. Thus, if you really want to get the very latest and greatest (and, at
 times, buggiest) code, you can use a tool called anonymous cvs<a 
  name="dx5-7006"></a><a 
  name="dx5-7007"></a> available from
-<!--l. 245--><p class="indent">   <a 
+<!--l. 266--><p class="indent">   <a 
 href="http://www.cvshome.org/" >http://www.cvshome.org/</a>
-<!--l. 248--><p class="noindent">to get the recent code. A detailed description of how to set this up for <span 
+<!--l. 269--><p class="noindent">to get the recent code. A detailed description of how to set this up for <span 
 class="ptmbi7t---109">FlightGear </span>can be
 found at
-<!--l. 253--><p class="indent">   <a 
+<!--l. 274--><p class="indent">   <a 
 href="http://www.flightgear.org/cvsResources/" >http://www.flightgear.org/cvsResources/</a>.
-<!--l. 256--><p class="noindent">Unfortunately, the system implemented above does not really work as it should. As a
+<!--l. 277--><p class="noindent">Unfortunately, the system implemented above does not really work as it should. As a
 matter of fact, the stable version is usually so much outdated, that it does not at all reflect
-thee stated of development <span 
+the state of development <span 
 class="ptmbi7t---109">FlightGear </span>has reached. Given that the recent developmental
 versions on the other hands may contain bugs (. . . undocumented features), we
 recommend using the &#8221;latest official (unstable) release&#8221; for the average user. This is the
 latest version named at
-<!--l. 261--><p class="indent">   <a 
+<!--l. 284--><p class="indent">   <a 
 href="http://www.flightgear.org/News/" >http://www.flightgear.org/News/</a>;
-<!--l. 264--><p class="noindent">usually this is also the version which the binary distributions<a 
+<!--l. 287--><p class="noindent">usually this is also the version which the binary distributions<a 
  name="dx5-7008"></a> available at
-<!--l. 268--><p class="indent">   <a 
+<!--l. 292--><p class="indent">   <a 
 href="http://www.flightgear.org/Downloads/" >http://www.flightgear.org/Downloads/</a>
-<!--l. 271--><p class="noindent">are based on. If not otherwise stated, all procedures in this &#8221;Installation and Getting
+                                                                     
 <!--l. 295--><p class="noindent">are based on. If not otherwise stated, all procedures in this &#8220;Installation and Getting
 Started&#8221; will be based on these packages.
   <h3 class="sectionHead"><span class="titlemark">1.4</span> <a 
-href="getstart.html#QQ2-5-8" name="x5-80001.4">Flight models</a></h3>
+href="getstart.html#QQ2-5-8" name="x5-80001.4">Flight Dynamics Models</a></h3>
 <a 
  name="dx5-8001"></a>
 <a 
  name="dx5-8002"></a>
-<!--l. 278--><p class="noindent">Historically, <span 
+<!--l. 302--><p class="noindent">Historically, <span 
 class="ptmbi7t---109">FlightGear </span>has been based on a flight model it inherited (together with the
 Navion airplane) from LaRCsim. As this had several limitations (most important,
 many characteristics were hard wired in contrast to using configuration files),
@ -332,15 +362,12 @@ there were several attempts to develop or include alternative flight models<a
 result, <span 
 class="ptmbi7t---109">FlightGear </span>supports several different flight models, to be chosen from at
 runtime.
-<!--l. 284--><p class="indent">   The most important one is the JSB flight model developed by Jon Berndt. Actually,
+<!--l. 308--><p class="indent">   The most important one is the JSB flight model developed by Jon Berndt. Actually,
 the JSB flight model is part of a stand-alone project called <span 
 class="ptmbi7t---109">JSBSim</span>, having its home at
-<!--l. 288--><p class="indent">   <a 
+<!--l. 312--><p class="indent">   <a 
 href="http://jsbsim.sourceforge.net/" >http://jsbsim.sourceforge.net/</a>.
-                                                                     
+<!--l. 315--><p class="noindent">Concerning airplanes, the JSB flight model at present provides support for a Cessna 172<a 
 <!--l. 291--><p class="noindent">Concerning airplanes, the JSB flight model at present provides support for a Cessna 172<a 
  name="dx5-8004"></a>,
 a Cessna 182<a 
  name="dx5-8005"></a>, a Cessna 310<a 
@ -349,17 +376,17 @@ a Cessna 182<a
 are gearing towards a very accurate flight model, and the JSB model has become
 <span 
 class="ptmbi7t---109">FlightGear</span>&#8217;s default flight model.
-<!--l. 296--><p class="indent">   As an interesting alternative, Christian Mayer developed a flight model of a hot air
+<!--l. 321--><p class="indent">   As an interesting alternative, Christian Mayer developed a flight model of a hot air
-balloon. Moreover, Curt Olson integrated a special slew mode called Magic Carpet,
+balloon. Moreover, Curt Olson integrated a special &#8221;UFO&#8221; slew mode, which helps you
-which helps you to quickly fly from point A to point B.
+to quickly fly from point A to point B.
-<!--l. 300--><p class="indent">   Recently, Andrew Ross contributed another flight model called <span 
+<!--l. 325--><p class="indent">   Recently, Andrew Ross contributed another flight model called <span 
 class="ptmbi7t---109">YASim</span><a 
  name="dx5-8008"></a> for <span 
 class="ptmri7t---109">Yet</span>
 <span 
-class="ptmri7t---109">another simulator</span>. At present, it sports another Cessna 172<a 
+class="ptmri7t---109">Another Simulator</span>. At present, it sports another Cessna 172<a 
  name="dx5-8009"></a>, a Turbo 310<a 
-  name="dx5-8010"></a>, a fairly ggod
+  name="dx5-8010"></a>, a fairly good
 DC-3<a 
  name="dx5-8011"></a> model, along with a Boeing 747<a 
  name="dx5-8012"></a>, Harrier<a 
@ -367,74 +394,89 @@ DC-3<a
  name="dx5-8014"></a>. <span 
 class="ptmbi7t---109">YASim </span>takes a fundamentally
 different approach since it&#8217;s based on geometry information rather than aerodynamic
-coefficients. Where JSBSim will be exact for every situation that is known and flight
+coefficients. Where <span 
-tested, but may have odd and/or unrealistic behavior outside normal flight, YASim will
+class="ptmbi7t---109">JSBSim </span>will be exact for every situation that is known and flight
-be sensible and consistent in almost every flight situation, but is likely to differ in
+tested, but may have odd and/or unrealistic behavior outside normal flight, <span 
 class="ptmbi7t---109">YASim </span>will be
 sensible and consistent in almost every flight situation, but is likely to differ in
 performance numbers.
-<!--l. 302--><p class="indent">   As a further alternative, there is the UIUC flight model<a 
+<!--l. 331--><p class="indent">   As a further alternative, there is the UIUC flight model<a 
-  name="dx5-8015"></a>, developed by a team from the
+  name="dx5-8015"></a>, developed by a team at the
-University of Illinois, independently from <span 
+University of Illinois at Urbana-Champaign. This work was initially geared toward
-class="ptmbi7t---109">FlightGear </span>in the beginning (while now using
+modeling aircraft in icing conditions<a 
-it for their simulations). This project aims at studying the simulation of aircraft icing. Its
+  name="dx5-8016"></a> together with a smart icing system to better enable
-home is at
+pilots to fly safely in an icing encounter. While this research continues, the
-<!--l. 308--><p class="indent">   <a 
+project has expanded to include modeling &#8221;nonlinear&#8221; aerodynamics, which
-href="http://amber.aae.uiuc.edu/~jscott/sis/" >http://amber.aae.uiuc.edu/&nbsp;jscott/sis/</a>.
+result in more realism in extreme attitudes, such as stall and high angle of attack
-<!--l. 311--><p class="noindent">The UIUC provides a host of different aircraft including several Cessna C172<a 
+flight. Two good examples that illustrate this capability are the Airwave Xtreme
-  name="dx5-8016"></a>, a Learjet
+                                                                     
-24<a 
+
-  name="dx5-8017"></a>, a Twin Otter<a 
+                                                                     
-  name="dx5-8018"></a> and much more. To get an idea, you may check the folder
+150<a 
-<span 
+  name="dx5-8017"></a> hang glider<a 
-class="pcrr7t---109">Aircraft-UIUC </span>of the <span 
+  name="dx5-8018"></a> and the 1903 Wright Flyer<a 
-class="ptmbi7t---109">FlightGear </span>path.
+  name="dx5-8019"></a>. For the hang glider, throttle can
-<!--l. 316--><p class="indent">   Please note, that the UIUC models do <span 
+be use to fly to gliding altitude or Ctrl-U can be used to jump up in 1000-ft
-class="ptmb7t---109">not </span>have a working gear. So you might
+increments. Try your hand at the unstable Wright Flyer and don&#8217;t stall the canard!
-experience some difficulties when starting from a runway. At least the nose gear will be
+Considerable up elevator trim will be required for level flight. In general, the
-too weak and the airplane will fall on it&#8217;s nose. This can be circumvented by pulling the
+aerodynamics are probably very close to the original Wright Flyer as they are
-stick more than usual for a while.
+partly based on experimental data taken on a replica tested recently at the NASA
-<!--l. 318--><p class="indent">   It is even possible to drive FlightGear&#8217;s scene display using an external FDM<a 
+Ames Research Center. Also included are two more models, a Beech 99<a 
-  name="dx5-8019"></a> running
+  name="dx5-8020"></a> and
 Marchetti S-211<a 
  name="dx5-8021"></a> jet trainer, which are older generation UIUC/FGFS models
 and based on simpler &#8221;linear&#8221; aerodynamics. More details of the UIUC flight
 model and a list of aircraft soon to be upgraded can be found on their website at
 <!--l. 351--><p class="indent">   <a 
 href="http://amber.aae.uiuc.edu/~m-selig/apasim.html" >http://amber.aae.uiuc.edu/<img 
 src="getstart2x.gif" alt="~"  class="tilde" > m-selig/apasim.html</a>
 <!--l. 354--><p class="noindent">Note that the 3D models of the UIUC airplanes<a 
  name="dx5-8022"></a> can be downloaded from a site
 maintained by Wolfram Kuss
 <!--l. 358--><p class="indent">   <a 
 href="http://home.t-online.de/home/Wolfram.Kuss/" >http://home.t-online.de/home/Wolfram.Kuss/</a>
 <!--l. 361--><p class="indent">   It is even possible to drive FlightGear&#8217;s scene display using an external FDM<a 
  name="dx5-8023"></a> running
 on a different computer - although this might not be a setup recommended to people just
 getting in touch with <span 
 class="ptmbi7t---109">FlightGear</span>.
   <h3 class="sectionHead"><span class="titlemark">1.5</span> <a 
-href="getstart.html#QQ2-5-9" name="x5-90001.5">To whom this guide is addressed and how it is organized</a></h3>
+href="getstart.html#QQ2-5-9" name="x5-90001.5">About This Guide</a></h3>
-<!--l. 329--><p class="noindent">There is little, if any, material in this Guide that is presented here exclusively. You could
+<!--l. 371--><p class="noindent">There is little, if any, material in this Guide that is presented here exclusively. You could
 even say with Montaigne that we &#8221;merely gathered here a big bunch of other men&#8217;s
 flowers, having furnished nothing of my own but the strip to hold them together&#8221;. Most
-(but fortunately not all) of the information can as well be obtained from the <span 
+(but fortunately not all) of the information herein can also be obtained from the
-class="ptmbi7t---109">FlightGear</span>
+<span 
-web site<a 
+class="ptmbi7t---109">FlightGear </span>web site<a 
-  name="dx5-9001"></a> located at:
+  name="dx5-9001"></a> located at
-                                                                     
+<!--l. 378--><p class="indent">   <a 
 <!--l. 336--><p class="indent">   <a 
 href="http://www.flightgear.org/" >http://www.flightgear.org/</a>
-<!--l. 339--><p class="indent">   Please, keep in mind that there are several mirrors to all <span 
+<!--l. 381--><p class="indent">   Please, keep in mind that there are several mirrors of the <span 
-class="ptmbi7t---109">FlightGear </span>Web sites, being
+class="ptmbi7t---109">FlightGear </span>web sites, all
-listed on this page. Sometimes it is preferred to download from them than from the
+of which are linked to from the <span 
-original place.
+class="ptmbi7t---109">FlightGear </span>homepage listed above. You may
-<!--l. 341--><p class="noindent">However, a neatly printed manual is arguably preferable over loosely scattered <span 
+prefer to download <span 
-class="ptmri7t---109">Readme</span>
+class="ptmbi7t---109">FlightGear </span>from a mirror closer to you than from the main
-files by some people, and those people may acknowledge the effort.
+site.
-<!--l. 345--><p class="indent">   This <span 
+<!--l. 386--><p class="indent">   This <span 
 class="ptmbi7t---109">FlightGear </span><span 
 class="ptmri7t---109">Installation and Getting Started </span>manual is intended to be a first step
-towards a more complete <span 
+towards a complete <span 
 class="ptmbi7t---109">FlightGear </span>documentation<a 
-  name="dx5-9002"></a> (with the other parts, hopefully, to
+  name="dx5-9002"></a>. The target audience is the end-user who
-be written by others). The target audience is the end-user who is not interested in
+is not interested in the internal workings of OpenGL<a 
-the internal workings of OpenGL<a 
+  name="dx5-9003"></a> or in building his or her own
-  name="dx5-9003"></a> or in building his or her own scenery, for
+scenery. It is our hope, that someday there will be an accompanying <span 
 instance. It is our hope, that someday there will be an accompanying <span 
 class="ptmbi7t---109">FlightGear</span>
 <span 
 class="ptmri7t---109">Programmer&#8217;s Guide</span><a 
  name="dx5-9004"></a> (which could be based on some of the documentation found at
-<!--l. 354--><p class="indent">   <a 
+                                                                     
 <!--l. 395--><p class="indent">   <a 
 href="http://www.flightgear.org/Docs" >http://www.flightgear.org/Docs</a>;
-<!--l. 357--><p class="noindent">a <span 
+<!--l. 398--><p class="noindent">a <span 
 class="ptmbi7t---109">FlightGear </span><span 
 class="ptmri7t---109">Scenery Design Guide</span>,<a 
  name="dx5-9005"></a> describing the Scenery tools now packaged as
@ -442,18 +484,18 @@ class="ptmri7t---109">Scenery Design Guide</span>,<a
 class="ptmbi7t---109">TerraGear</span>; and a <span 
 class="ptmbi7t---109">FlightGear </span><span 
 class="ptmri7t---109">Flight School</span><a 
-  name="dx5-9006"></a>, at least.
+  name="dx5-9006"></a> package.
-<!--l. 363--><p class="indent">   As a supplement, we recommend reading the <span 
+<!--l. 404--><p class="indent">   As a supplement, we recommend reading the <span 
 class="ptmbi7t---109">FlightGear </span>FAQ to be found
 at
-<!--l. 365--><p class="indent">   <a 
+<!--l. 406--><p class="indent">   <a 
 href="http://www.flightgear.org/Docs/FlightGear-FAQ.html" >http://www.flightgear.org/Docs/FlightGear-FAQ.html</a>
-<!--l. 367--><p class="indent">   which has a lot of supplementary information to (and, at times, more recent than) the
+<!--l. 408--><p class="indent">   which has a lot of supplementary information that may not be included in this
-present document.
+manual.
-<!--l. 374--><p class="indent">   <span 
+<!--l. 414--><p class="indent">   <span 
-class="ptmb7t---109">We kindly ask you to help me refine this document by submitting corrections,</span>
+class="ptmb7t---109">We kindly ask you to help us refine this document by submitting corrections,</span>
 <span 
-class="ptmb7t---109">improvements, and more. Any user is invited to contribute descriptions of</span>
+class="ptmb7t---109">improvements, and suggestions. All users is invited to contribute descriptions of</span>
 <span 
 class="ptmb7t---109">alternative setups (graphics cards, operating systems etc.). We will be more than</span>
 <span 
@ -462,11 +504,13 @@ class="ptmbi7t---109">Installation and Getting Started </span><span
 class="ptmb7t---109">(of</span>
 <span 
 class="ptmb7t---109">course not without giving credit to the authors).</span>
-<!--l. 376--><p class="indent">   While we intend to continuously update this document at least for the foreseeable
+<!--l. 416--><p class="indent">   While we intend to continuously update this document, we may not be able to
-future, supposedly we will not be able to produce a new one for any single release of
+produce a new version for every single release of <span 
-<span 
+class="ptmbi7t---109">FlightGear</span>. To do so would require
-class="ptmbi7t---109">FlightGear</span>. While we are watching the mailing lists, it would help if developers adding
+more manpower that we have now, so please feel free to jump in and help out. We
-new functionality would send us a short note.
+hope to produce documentation that measures up to the quality of <span 
 class="ptmbi7t---109">FlightGear</span>
 itself.
--- a/Docs/InstallGuide/html/getstartch2.html
+++ b/Docs/InstallGuide/html/getstartch2.html
@ -6,7 +6,7 @@
 <meta name="generator" content="TeX4ht (http://www.cis.ohio-state.edu/~gurari/TeX4ht/mn.html)"> 
 <!-- html,2,info,next,sections+ --> 
 <meta name="src" content="getstart.tex"> 
-<meta name="date" content="2002-02-16 19:41:00"> 
+<meta name="date" content="2002-09-08 00:44:00"> 
 <link rel="stylesheet" type="text/css" href="getstart.css"> 
 </head><body 
 >
@ -70,11 +70,11 @@ class="ptmbi7t---109">FlightGear </span>on. Other compilers
     <li class="itemize">The GNU compiler is free in the same sense of the GPL as <span 
 class="ptmbi7t---109">FlightGear </span>is.</li></ul>
 <!--l. 70--><p class="noindent">You might want to check Section <a 
-href="getstartap1.html#x12-52000A">A<!--tex4ht:ref: missed--></a>, <span 
+href="getstartap1.html#x12-66000A">A<!--tex4ht:ref: missed--></a>, <span 
 class="ptmri7t---109">Missed approach</span>, if anything fails during
 compilation. In case this does not help we recommend sending a note to one of the
 mailing lists (for hints on subscription see Chapter <a 
-href="getstartap3.html#x14-66000C">C<!--tex4ht:ref: landing--></a>).
+href="getstartap3.html#x14-80000C">C<!--tex4ht:ref: landing--></a>).
 <!--l. 73--><p class="indent">   There are several Linux distributions<a 
  name="dx6-10009"></a> on the market, and most of them should work.
 Some come even bundled with (often outdated) versions of <span 
@ -89,7 +89,7 @@ sense, before building the plane you will have to build the plant for building p
 This will be the topic of the following section, which can be omitted by Linux
 users.
   <h3 class="sectionHead"><span class="titlemark">2.1</span> <a 
-href="getstart.html#QQ2-6-11" name="x6-110002.1">Getting a development environment under Windows</a></h3>
+href="getstart.html#QQ2-6-11" name="x6-110002.1">Preparing the development environment under Windows</a></h3>
 <!--l. 86--><p class="noindent">There is a powerful development environment available for Windows and this
 even for free: The Cygnus development tools,<a 
  name="dx6-11001"></a> resp. <span 
@ -141,10 +141,79 @@ class="ptmbi7t---109">FlightGear </span>stuff lives under this directory. In add
 select
 <!--l. 125--><p class="indent">   <span 
 class="pcrr7t---109">Default text file type: Unix</span>
-<!--l. 127--><p class="indent">   You are free to install the compiler for all users or just for you.
+<!--l. 127--><p class="noindent">In addition, you have the choice to install the compiler for all users or just for
-<!--l. 129--><p class="indent">   As a final step you should include the binary directory<a 
+you.
-  name="dx6-11004"></a> (for instance:
+<!--l. 130--><p class="indent">   The final window before installation gives you a selection of packages to install. It is
-<span 
+hard, to provide a minimum selection of packages required for <span 
 class="ptmbi7t---109">FlightGear </span>and the
 accompanying libraries to install. We have observed the following (non minimum)
 combination to work:<a 
  name="dx6-11004"></a>
     <ul class="itemize1">
     <li class="itemize"><span 
 class="pcrr7t---109">Admin </span>skip
     </li>
     <li class="itemize"><span 
 class="pcrr7t---109">Archive </span>install
     </li>
     <li class="itemize"><span 
 class="pcrr7t---109">Base </span>install
     </li>
     <li class="itemize"><span 
 class="pcrr7t---109">Database </span>skip
     </li>
     <li class="itemize"><span 
 class="pcrr7t---109">Devel </span>install
     </li>
     <li class="itemize"><span 
 class="pcrr7t---109">Doc </span>install
     </li>
     <li class="itemize"><span 
 class="pcrr7t---109">Editors </span>skip
     </li>
     <li class="itemize"><span 
 class="pcrr7t---109">Graphics </span>install
     </li>
     <li class="itemize"><span 
 class="pcrr7t---109">Interpreters </span>install
     </li>
     <li class="itemize"><span 
 class="pcrr7t---109">Libs </span>install
     </li>
     <li class="itemize"><span 
 class="pcrr7t---109">Mail </span>skip
     </li>
     <li class="itemize"><span 
 class="pcrr7t---109">Net </span>skip
     </li>
     <li class="itemize"><span 
 class="pcrr7t---109">Shells </span>install
     </li>
     <li class="itemize"><span 
 class="pcrr7t---109">Text </span>install
     </li>
     <li class="itemize"><span 
 class="pcrr7t---109">Utils </span>install
     </li>
     <li class="itemize"><span 
 class="pcrr7t---109">Web </span>skip
     </li>
     <li class="itemize"><span 
 class="pcrr7t---109">XFree86 </span>do not install!</li></ul>
 <!--l. 152--><p class="noindent"><span 
 class="ptmb7t---109">Note </span>XFree86<a 
  name="dx6-11005"></a> must be not installed for building <span 
 class="ptmbi7t---109">FlightGear </span>and the accompanying
 libraries. If it is installed you have to deinstall it first. Otherwise <span 
 class="ptmbi7t---109">FlightGear</span>&#8217;s
 configuration scripts will detect the XFree86 OpenGL libraries and link to them, while
 the code is not prepared to do so.
 <!--l. 154--><p class="indent">   As a final step you should include the binary directory<a 
  name="dx6-11006"></a> (for instance:
 <br class="newline"><span 
 class="pcrr7t---109">c:/Cygwin/bin</span>) into your path by adding <span class="obeylines-h"><span 
 class="pcrr7t---109">path=c:\Cygwin\bin</span></span> in your
 <span 
@ -157,37 +226,126 @@ class="pcrr7t---109">control</span>
 class="pcrr7t---109">panel</span>. There you&#8217;ll find a button <span 
 class="pcrr7t---109">Environment variables</span>, where you can add
 the named directory.
-<!--l. 133--><p class="indent">   Now you are done. Fortunately, all this is required only once. At this point you have a
+<!--l. 158--><p class="indent">   Now you are done. Fortunately, all this is required only once. At this point you have a
 nearly UNIX-like (command line) development environment. Because of this, the
 following steps are nearly identical under Windows and Linux/Unix.
   <h3 class="sectionHead"><span class="titlemark">2.2</span> <a 
-href="getstart.html#QQ2-6-12" name="x6-120002.2">Compiling <span 
+href="getstart.html#QQ2-6-12" name="x6-120002.2">Preparing the development environment under Windows</a></h3>
-class="ptmbi7t---109">FlightGear </span>under Linux/Windows </a></h3>
+<!--l. 165--><p class="noindent">Linux, like any UNIX, usually comes with a compiler pre-installed. On the other hand,
-<!--l. 141--><p class="noindent">A preliminary remark: For UNIX, make sure you have all necessary OpenGL libraries
+you still have to make sure several required libraries being present.
-first. Fortunately on all recent Linux distributions (i.e. SuSE-7.1) these are already put on
+<!--l. 167--><p class="indent">   First, make sure you have all necessary OpenGL libraries. Fortunately, most of the
-the right place. Be sure to install the proper package. Besides the basic X11
+recent Linux distributions (i.e. SuSE-7.3) put these already into the right place. (There
 have been reports, though, that on Slackware you may have to copy the libraries to
 <span 
 class="pcrr7t---109">/usr/local/lib </span>and the headers to <span 
 class="pcrr7t---109">/usr/local/include </span>by hand after
 building <span 
 class="pcrr7t---109">glut-3.7</span>). Be sure to install the proper packages: Besides the basic X11
 stuff you want to have - SuSE as an example - the following packages: mesa,
 mesa-devel, mesasoft, xf86_glx, xf86glu, xf86glu-devel, mesaglut, mesaglut-devel and
 plib.
-<!--l. 147--><p class="indent">   Also you are expected to have a bunch of tools installed that are usually required to
+<!--l. 171--><p class="indent">   Also you are expected to have a bunch of tools installed that are usually required to
 compile the Linux kernel. So you may use the Linux kernel source package top
 determine the required dependencies. The following packages might prove to be useful
-when fiddling with the FlightGear sources: automake, autoconf, libtool, bison, flex and
+when fiddling with the <span 
 class="ptmbi7t---109">FlightGear </span>sources: automake, autoconf, libtool, bison, flex and
 some more, that are not required to build a Linux kernel.
-<!--l. 154--><p class="indent">   Please compare the release of the Plib library with the one that ships with your Linux
+<!--l. 178--><p class="indent">   <span 
-distribution. It might be the case that FlightGear requires a newer one that is not yet
+class="ptmb7t---109">Please compare the release of the Plib library with the one that ships with your</span>
-provided by your vendor.
+<span 
-<!--l. 158--><p class="indent">   Under Windows, the required libraries should have been installed with the <span 
+class="ptmb7t---109">Linux distribution. </span>It might be the case that <span 
-class="ptmbi7t---109">Cygwin</span>
+class="ptmbi7t---109">FlightGear </span>requires a newer one that is not
-installation above.
+yet provided by your vendor.
-<!--l. 160--><p class="indent">   The following steps are identical under Linux/Unix and under Windows with minor
+   <h3 class="sectionHead"><span class="titlemark">2.3</span> <a 
 href="getstart.html#QQ2-6-13" name="x6-130002.3">One-time preparations for Linux and Windows users</a></h3>
 <!--l. 186--><p class="noindent">There are a couple of 3rd party libraries which your Linux or Windows system may or
 may have not installed, i.e. the <span 
 class="ptmbi7t---109">ZLIB </span>library and the <span 
 class="ptmbi7t---109">Metakit </span>library. You can
 either check your list of installed packages or just try building <span 
 class="ptmbi7t---109">SimGear</span>: It
 should exit and spit an error message (observe this!) if one of these libraries is
 missing.
 <!--l. 188--><p class="indent">   If you make this observation, install the missing libraries, which only is required
 once (unless you don&#8217;t re-install you development environment).
 <!--l. 190--><p class="indent">   Both libraries come bundled with <span 
 class="ptmbi7t---109">SimGear</span>, which links to them, bus does not
 automatically install them. For installing either of them, get the most recent file
 <span 
 class="pcrr7t---109">SimGear-X.X.X.tar.gz</span><a 
  name="dx6-13001"></a> from
 <!--l. 193--><p class="indent">   <a 
 href="http://www.simgear.org/downloads.html" >http://www.simgear.org/downloads.html</a>
 <!--l. 196--><p class="noindent">Download it to <span 
 class="pcrr7t---109">/usr/local/source</span>. Change to that directory and unpack <span 
 class="ptmbi7t---109">SimGear</span>
 using
 <!--l. 200--><p class="indent">   <span 
 class="pcrr7t---109">tar xvfz SimGear-X.X.X.tar.gz</span>.
 <!--l. 202--><p class="indent">   You will observe a directory <span 
 class="pcrr7t---109">src-libs </span>which contains the two names
 libraries.
   <h4 class="subsectionHead"><span class="titlemark">2.3.1</span> <a 
 href="getstartli1.html#QQ2-6-14" name="x6-140002.3.1">Installation of <span 
 class="ptmbi7t---109">ZLIB</span></a></h4>
 <!--l. 206--><p class="noindent"><span 
 class="pcrr7t---109">cd </span>into <span 
 class="pcrr7t---109">SimGear-X.X.X/scr-libs </span>and unpack <span 
 class="ptmbi7t---109">ZLIB </span>using
 <!--l. 210--><p class="noindent"><span 
 class="pcrr7t---109">tar xvfz zlib-X.X.X.tar.gz</span>.
 <!--l. 214--><p class="noindent">Next, change to the newly created directory <span 
 class="pcrr7t---109">zlib-X.X.X </span>and type
 <!--l. 218--><p class="noindent"><span 
 class="pcrr7t---109">./configure</span>
 <br class="newline"><span 
 class="pcrr7t---109">make</span>
 <br class="newline"><span 
 class="pcrr7t---109">make install</span>
 <!--l. 224--><p class="noindent">Under Linux, you have to become root for being able to <span 
 class="pcrr7t---109">make install</span>, for instance
 via the <span 
 class="pcrr7t---109">su </span>command.
   <h4 class="subsectionHead"><span class="titlemark">2.3.2</span> <a 
 href="getstartli1.html#QQ2-6-15" name="x6-150002.3.2">Installation of <span 
 class="ptmbi7t---109">Metakit</span></a></h4>
 <!--l. 229--><p class="noindent"><span 
 class="pcrr7t---109">cd </span>into <span 
 class="pcrr7t---109">SimGear-X.X.X/scr-libs </span>and unpack <span 
 class="ptmbi7t---109">Metakit </span>using
 <!--l. 233--><p class="noindent"><span 
 class="pcrr7t---109">tar xvfz metakit-X.X.X.tar.gz</span>.
 <!--l. 237--><p class="noindent">Next, change to directory <span 
 class="pcrr7t---109">zlib-X.X.X/builds </span>(!) and type (where the
 configure option <span 
 class="pcrr7t---109">--with-tcl=no </span>is at least required on a Cygwin system):
 <!--l. 241--><p class="noindent"><span 
 class="pcrr7t---109">./configure --with-tcl=no</span>
 <br class="newline"><span 
 class="pcrr7t---109">make</span>
 <br class="newline"><span 
 class="pcrr7t---109">make install</span>
 <!--l. 247--><p class="noindent">Under Linux, you have to become root for being able to <span 
 class="pcrr7t---109">make install</span>, for instance
 via the <span 
 class="pcrr7t---109">su </span>command.
 <!--l. 250--><p class="indent">   You may want to consult the Readme files under <span 
 class="pcrr7t---109">SimGear-X.X.X/scr-libs </span>in
 case you run into trouble.
   <h3 class="sectionHead"><span class="titlemark">2.4</span> <a 
 href="getstart.html#QQ2-6-16" name="x6-160002.4">Compiling <span 
 class="ptmbi7t---109">FlightGear </span>under Linux/Windows </a></h3>
 <!--l. 256--><p class="noindent">The following steps are identical under Linux/Unix and under Windows with minor
 modifications. Under Windows, just open the <span 
 class="ptmbi7t---109">Cygwin </span>icon from the Start menu or from
 the desktop to get a command line.
-<!--l. 164--><p class="indent">   To begin with, the <span 
+<!--l. 260--><p class="indent">   To begin with, the <span 
 class="ptmbi7t---109">FlightGear </span>build process is based on four packages which you
 need to built and installed in this order:
     <ul class="itemize1">
@ -195,176 +353,204 @@ need to built and installed in this order:
     </li>
     <li class="itemize">SimGear
     </li>
-     <li class="itemize">FlightGear Program
+     <li class="itemize">FlightGear, program
     </li>
-     <li class="itemize">FlightGear base (data - no compilation required)</li></ul>
+     <li class="itemize">FlightGear, base (data - no compilation required)</li></ul>
     <ol type="1" class="enumerate1" start="1" 
 >
     <li class="enumerate"><a 
-  name="x6-12002x1"></a>First, choose an install directory<a 
+  name="x6-16002x1"></a>First, choose an install directory<a 
-  name="dx6-12003"></a> for FlightGear. This will not be the one your
+  name="dx6-16003"></a> for FlightGear. This will not be the one your
     binaries will live in but the one for your source code and compilation files.
     We suggest
-     <!--l. 176--><p class="noindent"><span 
+     <!--l. 272--><p class="noindent"><span 
 class="pcrr7t---109">cd:/usr/local/</span>
-     <!--l. 178--><p class="noindent"><span 
+     <!--l. 274--><p class="noindent"><span 
 class="pcrr7t---109">mkdir source</span>
     </li>
     <li class="enumerate"><a 
-  name="x6-12005x2"></a>Now, you have to install a support library <span 
+  name="x6-16005x2"></a>Now, you have to install a support library <span 
 class="ptmbi7t---109">PLIB</span><a 
-  name="dx6-12006"></a> which is absolutely essential
+  name="dx6-16006"></a> which is absolutely essential
     for the building process. <span 
 class="ptmbi7t---109">PLIB </span>contains most of the basic graphics rendering,
     audio,  and  joystick  routines.  Download  the  latest  stable  version  of  <span 
 class="ptmbi7t---109">PLIB</span><a 
-  name="dx6-12007"></a>
+  name="dx6-16007"></a>
     from
-     <!--l. 184--><p class="noindent"><a 
+     <!--l. 280--><p class="noindent"><a 
 href="http://plib.sourceforge.net/" >http://plib.sourceforge.net/</a>
-     <!--l. 187--><p class="noindent">to  <span 
+     <!--l. 283--><p class="noindent">to  <span 
 class="pcrr7t---109">/usr/local/source</span>.  Change  to  that  directory  and  unpack  <span 
 class="ptmbi7t---109">PLIB</span>
     using
-     <!--l. 190--><p class="noindent"><span 
+     <!--l. 286--><p class="noindent"><span 
 class="pcrr7t---109">tar xvfz plib-X.X.X.tar.gz</span>.
-     <!--l. 192--><p class="noindent"><span 
+     <!--l. 288--><p class="noindent"><span 
 class="pcrr7t---109">cd </span>into <span 
 class="pcrr7t---109">plib-X.X.X </span>and run
-     <!--l. 194--><p class="noindent"><span 
+     <!--l. 290--><p class="noindent"><span 
 class="pcrr7t---109">./configure</span>
     <br class="newline"><span 
 class="pcrr7t---109">make</span>
     <br class="newline"><span 
 class="pcrr7t---109">make install</span>.
-     <!--l. 198--><p class="noindent">Under Linux, you have to become root for being able to <span 
+     <!--l. 294--><p class="noindent">Under Linux, you have to become root for being able to <span 
 class="pcrr7t---109">make install</span>,
     for instance via the <span 
 class="pcrr7t---109">su </span>command.
-                                                                     
+     <!--l. 297--><p class="noindent">Confirm you now have <span 
     <!--l. 201--><p class="noindent">Confirm   you   now   have   <span 
 class="ptmbi7t---109">PLIB</span>&#8217;s header files<a 
-  name="dx6-12008"></a>   (as   <span 
+  name="dx6-16008"></a> (as <span 
 class="pcrr7t---109">ssg.h </span>etc.) under
-     <span 
+     <br class="newline"><span 
 class="pcrr7t---109">/usr/include/plib </span>(and nowhere else).
     </li>
     <li class="enumerate"><a 
-  name="x6-12010x3"></a>Next,  you  have  to  install  another  library  <span 
+  name="x6-16010x3"></a>Next,  you  have  to  install  another  library  <span 
 class="ptmbi7t---109">SimGear</span><a 
-  name="dx6-12011"></a>  containing  the  basic
+  name="dx6-16011"></a>  containing  the  basic
     simulation routines. Get the most recent file <span 
 class="pcrr7t---109">SimGear-X.X.X.tar.gz</span><a 
-  name="dx6-12012"></a>
+  name="dx6-16012"></a>
     from
-     <!--l. 207--><p class="noindent"><a 
+     <!--l. 302--><p class="noindent"><a 
-href="ftp://ftp.simgear.org/pub/simgear/Source/" >ftp://ftp.simgear.org/pub/simgear/Source/</a>
+href="http://www.simgear.org/downloads.html" >http://www.simgear.org/downloads.html</a>
-     <!--l. 210--><p class="noindent">Download  it  to  <span 
+     <!--l. 305--><p class="noindent">Download  it  to  <span 
 class="pcrr7t---109">/usr/local/source</span>.  Change  to  that  directory  and
     unpack <span 
 class="ptmbi7t---109">SimGear </span>using
-     <!--l. 214--><p class="noindent"><span 
+     <!--l. 309--><p class="noindent"><span 
 class="pcrr7t---109">tar xvfz SimGear-X.X.X.tar.gz</span>.
-     <!--l. 216--><p class="noindent"><span 
+     <!--l. 311--><p class="noindent"><span 
 class="pcrr7t---109">cd </span>into <span 
 class="pcrr7t---109">SimGear-X.X.X </span>and run
-     <!--l. 219--><p class="noindent"><span 
+                                                                     
     <!--l. 314--><p class="noindent"><span 
 class="pcrr7t---109">./configure</span>
     <br class="newline"><span 
 class="pcrr7t---109">make</span>
     <br class="newline"><span 
 class="pcrr7t---109">make install</span>
-     <!--l. 223--><p class="noindent">Again,  under  Linux,  you  have  to  become  root  for  being  able  to  <span 
+     <!--l. 318--><p class="noindent">Again,  under  Linux,  you  have  to  become  root  for  being  able  to  <span 
 class="pcrr7t---109">make</span>
     <span 
 class="pcrr7t---109">install</span>, for instance via the <span 
 class="pcrr7t---109">su </span>command.
     </li>
     <li class="enumerate"><a 
-  name="x6-12014x4"></a>Now,                             you&#8217;re                             prepared                             to
+  name="x6-16014x4"></a>Now, you&#8217;re prepared to build <span 
-     build <span 
+class="ptmbi7t---109">FlightGear </span>itself, finally. Get
-class="ptmbi7t---109">FlightGear </span>itself, finally. Get <span 
+     <br class="newline"><span 
 class="pcrr7t---109">FlightGear-X.X.X.tar.gz </span>from
-     <!--l. 231--><p class="noindent"><a 
+     <!--l. 326--><p class="noindent"><a 
-href="ftp://www.flightgear.org/pub/flightgear/Source/" >ftp://www.flightgear.org/pub/flightgear/Source/</a>
+href="http://www.flightgear.org/Downloads/" >http://www.flightgear.org/Downloads/</a>
-     <!--l. 234--><p class="noindent">and download it to <span 
+     <!--l. 329--><p class="noindent">and download it to <span 
 class="pcrr7t---109">/usr/local/source</span>. Unpack <span 
 class="ptmbi7t---109">FlightGear </span>using
-     <!--l. 238--><p class="noindent"><span 
+     <!--l. 333--><p class="noindent"><span 
 class="pcrr7t---109">tar xvfz FlightGear-X.X.X.tar.gz</span>.
-     <!--l. 241--><p class="noindent"><span 
+     <!--l. 336--><p class="noindent"><span 
 class="pcrr7t---109">cd </span>into <span 
 class="pcrr7t---109">FlightGear-X.X.X </span>and run
-     <!--l. 243--><p class="noindent"><span 
+     <!--l. 338--><p class="noindent"><span 
 class="pcrr7t---109">./configure</span>
-     <!--l. 246--><p class="noindent">configure<a 
+     <!--l. 341--><p class="noindent">configure<a 
-  name="dx6-12015"></a> knows about numerous options, <a 
+  name="dx6-16015"></a> knows about numerous options, <a 
-  name="dx6-12016"></a>with the more relevant ones to be
+  name="dx6-16016"></a>with the more relevant ones to be
     specified via switches as
          <ul class="itemize1">
          <li class="itemize"><span 
 class="pcrr7t---109">--with-network-olk</span>:    Include    Oliver    Delise&#8217;s    multi-pilot
          networking support<a 
-  name="dx6-12017"></a>,
+  name="dx6-16017"></a>,
          </li>
          <li class="itemize"><span 
-class="pcrr7t---109">--disable-network-olk</span>:  Disable  Oliver  Delise&#8217;s  multi-pilot
+class="pcrr7t---109">--with-new-environment</span>:      Include      new      experimental
-          networking support<a 
+          environment subsystem,
  name="dx6-12018"></a>,
          </li>
          <li class="itemize"><span 
-class="pcrr7t---109">--with-old-weather</span>:       Include       original/simple       weather
+class="pcrr7t---109">--with-weathercm</span>: Use WeatherCM instead of FGEnvironment,<a 
-          subsystem<a 
+  name="dx6-16018"></a>
  name="dx6-12019"></a>,
          </li>
          <li class="itemize"><span 
-class="pcrr7t---109">--with-x</span>: Use the X Window system (Linux only)
+class="pcrr7t---109">--with-plib=</span>PREFIX: Specify the prefix path to <span 
-          <br class="newline">
+class="ptmbi7t---109">PLIB</span>,
          </li>
          <li class="itemize"><span 
 class="pcrr7t---109">--with-metakit=</span>PREFIX: Specify the prefix path to <span 
 class="ptmbi7t---109">Metakit</span>,
          </li>
          <li class="itemize"><span 
 class="pcrr7t---109">--with-simgear=</span>PREFIX: Specify the prefix path to <span 
 class="ptmbi7t---109">SimGear</span>,
          </li>
          <li class="itemize"><span 
 class="pcrr7t---109">--prefix=/XXX</span>: Install <span 
 class="ptmbi7t---109">FlightGear </span>in the directory <span 
-class="pcrr7t---109">XXX</span>.</li></ul>
+class="pcrr7t---109">XXX</span>.
-     <!--l. 261--><p class="noindent">A good choice would be <span 
+                                                                     
          </li>
          <li class="itemize"><span 
 class="pcrr7t---109">--disable-jsbsim</span>: Disable <span 
 class="ptmbi7t---109">JSBSim</span>m FDM (in case of trouble
          compiling it).
          </li>
          <li class="itemize"><span 
 class="pcrr7t---109">--disable-yasim</span>:  Disable  <span 
 class="ptmbi7t---109">YASim  </span>FDM  (in  case  of  trouble
          compiling it).
          </li>
          <li class="itemize"><span 
 class="pcrr7t---109">--disable-larcsim</span>: Disable <span 
 class="ptmbi7t---109">LaRCsim </span>FDM (in case of trouble
          compiling it).
          </li>
          <li class="itemize"><span 
 class="pcrr7t---109">--disable-uiuc</span>:   Disable   UIUC   FDM   (in   case   of   trouble
          compiling it).</li></ul>
     <!--l. 368--><p class="noindent">A good choice would be <span 
 class="pcrr7t---109">--prefix=/usr/local/FlightGear</span>. In this case
     <span 
 class="ptmbi7t---109">FlightGear</span>&#8217;s binaries<a 
-  name="dx6-12020"></a> will live under <span 
+  name="dx6-16019"></a> will live under <span 
 class="pcrr7t---109">/usr/local/FlightGear/bin</span>. (If you
     don&#8217;t specify a <span 
 class="pcrr7t---109">--prefix </span>the binaries will go into <span 
 class="pcrr7t---109">/usr/local/bin </span>while
     the base package files are expected under <span 
 class="pcrr7t---109">/usr/local/lib/FlightGear</span>.)
-     <!--l. 265--><p class="noindent">Assuming <span 
+     <!--l. 372--><p class="noindent">Assuming <span 
 class="pcrr7t---109">configure </span>finished successfully, run
-     <!--l. 268--><p class="noindent"><span 
+     <!--l. 375--><p class="noindent"><span 
 class="pcrr7t---109">make</span>
     <br class="newline"><span 
 class="pcrr7t---109">make install</span>.
-     <!--l. 271--><p class="noindent">Again, under Linux, you have to become root for being able to <span 
+     <!--l. 378--><p class="noindent">Again, under Linux, you have to become root for being able to <span 
 class="pcrr7t---109">make install</span>,
     for instance via the <span 
 class="pcrr7t---109">su </span>command.
-     <!--l. 275--><p class="noindent">Note: You can save a significant amount of space by stripping all the debugging
+     <!--l. 382--><p class="noindent">Note: You can save a significant amount of space by stripping all the debugging
     symbols off the executable. To do this, make a
-     <!--l. 280--><p class="noindent"><span 
+     <!--l. 387--><p class="noindent"><span 
 class="pcrr7t---109">cd /usr/local/FlightGear/bin</span>
-     <!--l. 282--><p class="noindent">to the directory in the <span 
+     <!--l. 389--><p class="noindent">to the directory in the <span 
 class="pcrr7t---109">install tree </span>where your binaries live and run
-     <!--l. 286--><p class="noindent"><span 
+     <!--l. 393--><p class="noindent"><span 
 class="pcrr7t---109">strip *</span>.</li></ol>
-<!--l. 290--><p class="noindent">This completes building the executable and should result in a file <span 
+<!--l. 397--><p class="noindent">This completes building the executable and should result in a file <span 
 class="pcrr7t---109">fgfs </span>(Unix) or
 <span 
 class="pcrr7t---109">fgfs.exe </span>(Windows) under <span 
 class="pcrr7t---109">/usr/local/FlightGear/bin</span>
-<!--l. 293--><p class="indent">   <span 
+<!--l. 400--><p class="indent">   <span 
 class="ptmb7t---109">Note: </span>If for whatever reason you want to re-build the simulator, use the command <span 
 class="pcrr7t---109">make</span>
 <span 
@ -380,62 +566,102 @@ these same directories before.
-   <h3 class="sectionHead"><span class="titlemark">2.3</span> <a 
+   <h3 class="sectionHead"><span class="titlemark">2.5</span> <a 
-href="getstart.html#QQ2-6-13" name="x6-130002.3">Compiling <span 
+href="getstart.html#QQ2-6-17" name="x6-170002.5">Compiling <span 
-class="ptmbi7t---109">FlightGear </span>under Mac OS 10.1 </a></h3>
+class="ptmbi7t---109">FlightGear </span>under Mac OS X </a></h3>
-<!--l. 303--><p class="noindent">For compiling under Mac OS 10.1 you will need
+<!--l. 410--><p class="noindent">For compiling under Mac OS X you will need
     <ul class="itemize1">
-     <li class="itemize">Mac OS 10.1 with 10.1 developer tools installed.
+     <li class="itemize">Mac X OS 10.1+ with developer tools installed.
     </li>
-     <li class="itemize">500MB disk (conservative estimate, might be a little less).
+     <li class="itemize">500MB disk (minimum) free disk space.
     </li>
     <li class="itemize">Fearlessness of command line compiling.</li></ul>
-<!--l. 311--><p class="noindent">This will need a bit more bravery than building under Windows or Linux. First, there are
+<!--l. 418--><p class="noindent">This will need a bit more bravery than building under Windows or Linux. First, there are
 less people who tested it under sometimes strange configurations. Second, the
-process as described here itself nees a touch more experience by using CVS
+process as described here itself needs a touch more experience by using CVS
 repositories.
-<!--l. 314--><p class="indent">   First, download the development files. They are intended to simplify the build
+<!--l. 420--><p class="indent">   First, download the development files. They contain files that help simplify the build
-process as much as possible:
+process, and software for automake, autoconf, and plib:
-<!--l. 318--><p class="indent">   <a 
+<!--l. 424--><p class="indent">   <a 
-href="http://expert.cc.purdue.edu/~walisser/fg/fgdev.tar.gz" >http://expert.cc.purdue.edu/&nbsp;walisser/fg/fgdev.tar.gz</a>
+href="http://expert.cc.purdue.edu/~walisser/fg/fgdev.tar.gz" >http://expert.cc.purdue.edu/<img 
-<!--l. 321--><p class="indent">   Once you have this extracted, make sure you are using tcsh, since the setup script
+src="getstart3x.gif" alt="~"  class="tilde" > walisser/fg/fgdev.tar.gz</a>
-requires it.
+<!--l. 427--><p class="noindent">or
 <!--l. 431--><p class="indent">   <a 
 href="http://homepage.mac.com/walisser" >http://homepage.mac.com/walisser</a>
 <!--l. 434--><p class="noindent">Once you have this extracted, make sure you are using TCSH as your shell, since the
 setup script requires it.
 <!--l. 438--><p class="noindent"><span 
 class="ptmb7t---109">Important for Jaguar users:</span>
 <!--l. 441--><p class="indent">   If you run Mac OS X 10.2 or later, gcc 3.1 is the default compiler. However, only
 version 2.95 works with <span 
 class="ptmbi7t---109">FlightGear </span>as of this writing. To change the default compiler,
 run this command (as root). You&#8217;ll only have to do this once and it will have a global
 effect on the system.
 <!--l. 444--><p class="indent">   <span 
 class="pcrr7t---109">sudo gcc</span><span class="underline"><span 
 class="pcrr7t---109">&nbsp;</span></span><span 
 class="pcrr7t---109">select 2</span>
     <ol type="1" class="enumerate1" start="1" 
 >
     <li class="enumerate"><a 
-  name="x6-13002x1"></a>Setup the build environment:
+  name="x6-17002x1"></a>Setup the build environment:
     <br class="newline"><span 
 class="pcrr7t---109">cd fgdev</span>
     <br class="newline"><span 
 class="pcrr7t---109">source bin/prepare.csh</span>
     </li>
     <li class="enumerate"><a 
-  name="x6-13004x2"></a>Install automake/aclocal build tools
+  name="x6-17004x2"></a>Install the latest versions of the automake and autoconf build tools:
     <br class="newline"><span 
-class="pcrr7t---109">cd $BUILDDIR/src/automake-1.4-p4</span>
+class="pcrr7t---109">cd $BUILDDIR/src/automake-X.X.X</span>
     <br class="newline"><span 
 class="pcrr7t---109">./configure --prefix=$BUILDDIR</span>
     <br class="newline"><span 
 class="pcrr7t---109">make install</span>
     <br class="newline"><span 
 class="pcrr7t---109">rehash</span>
     <!--l. 457--><p class="noindent"><span 
 class="pcrr7t---109">cd $BUILDDIR/src/autoconf-X.XX</span>
     <br class="newline"><span 
 class="pcrr7t---109">./configure --prefix=$BUILDDIR</span>
     <br class="newline"><span 
-class="pcrr7t---109">make install rehash</span>
+class="pcrr7t---109">make install</span>
     <br class="newline"><span 
 class="pcrr7t---109">rehash</span>
     </li>
     <li class="enumerate"><a 
-  name="x6-13006x3"></a>Build PLIB
+  name="x6-17006x3"></a>Download PLIB
     <br class="newline"><span 
-class="pcrr7t---109">cd $BUILDDIR/src/plib-1.4.2</span>
+class="pcrr7t---109">cd $BUILDDIR/src</span>
     <br class="newline"><span 
-class="pcrr7t---109">aclocal</span>
+class="pcrr7t---109">setenv CVSROOT :pserver:anonymous@cvs.plib.sf.net:</span>
     <br class="newline"><span 
-class="pcrr7t---109">automake</span>
+class="pcrr7t---109">/cvsroot/plib </span>(one line!)
     <br class="newline"><span 
-class="pcrr7t---109">./configure --prefix=$BUILDDIR --with-GL=$BUILDDIR</span>
+class="pcrr7t---109">cvs login</span>
     <br class="newline">Press <span 
 class="cmmi-10--109">&lt;</span>enter<span 
 class="cmmi-10--109">&gt; </span>for password
     <br class="newline"><span 
 class="pcrr7t---109">cvs -z3 checkout plib</span>
     </li>
     <li class="enumerate"><a 
  name="x6-17008x4"></a>Build PLIB
     <br class="newline"><span 
 class="pcrr7t---109">cd $BUILDDIR/src/plib</span>
     <br class="newline"><span 
 class="pcrr7t---109">./autogen.sh</span>
     <br class="newline"><span 
 class="pcrr7t---109">./configure --prefix=$BUILDDIR</span>
     <br class="newline"><span 
 class="pcrr7t---109">make install</span>
     </li>
     <li class="enumerate"><a 
-  name="x6-13008x4"></a>Get the SimGear sources
+  name="x6-17010x5"></a>Get the <span 
 class="ptmbi7t---109">SimGear </span>sources
     <br class="newline"><span 
 class="pcrr7t---109">cd $BUILDDIR/src</span>
     <br class="newline"><span 
@ -444,70 +670,80 @@ class="pcrr7t---109">setenv CVSROOT :pserver:cvs@cvs.simgear.org:</span>
 class="pcrr7t---109">/var/cvs/SimGear-0.0 </span>(one line)
     <br class="newline"><span 
 class="pcrr7t---109">cvs login</span>
-     <br class="newline"># Enter &#8221;guest&#8221; for password
+     <br class="newline">Enter <span 
 class="cmmi-10--109">&lt;</span>guest<span 
 class="cmmi-10--109">&gt; </span>for password
     <br class="newline"><span 
 class="pcrr7t---109">cvs -z3 checkout SimGear</span>
     <br class="newline">
     </li>
     <li class="enumerate"><a 
-  name="x6-13010x5"></a>Build Metakit
+  name="x6-17012x6"></a>Build Metakit
     <br class="newline"><span 
-class="pcrr7t---109">cd $BUILDDIR/src/SimGear</span>
+class="pcrr7t---109">cd $BUILDDIR/src/SimGear/src-libs</span>
     <br class="newline"><span 
-class="pcrr7t---109">tar -zxvf metakit-X.X.X.tar.gz</span>
+class="pcrr7t---109">tar -zxvf metakit-X.X.X-32.tar.gz</span>
     <br class="newline"><span 
 class="pcrr7t---109">cd metakit-X.X.X/builds</span>
     <br class="newline"><span 
 class="pcrr7t---109">../unix/configure --prefix=&amp;BUILDDIR</span>
     <br class="newline"><span 
-class="pcrr7t---109">make</span>
+class="pcrr7t---109">--enable-static --disable-dynamic </span>(one line)
     <br class="newline"><span 
 class="pcrr7t---109">make install</span>
     <br class="newline">
     </li>
     <li class="enumerate"><a 
-  name="x6-13012x6"></a>Build SimGear
+  name="x6-17014x7"></a>Build <span 
 class="ptmbi7t---109">SimGear</span>
     <br class="newline"><span 
 class="pcrr7t---109">cd $BUILDDIR/src/SimGear</span>
     <br class="newline"><span 
 class="pcrr7t---109">./autogen.sh</span>
     <br class="newline"><span 
-class="pcrr7t---109">./configure --prefix=$BUILDDIR --host=powerpc</span>
+class="pcrr7t---109">./configure --prefix=$BUILDDIR</span>
     <br class="newline"><span 
 class="pcrr7t---109">make install</span>
     <br class="newline">
     </li>
     <li class="enumerate"><a 
-  name="x6-13014x7"></a>Get the FlightGear sources <span 
+  name="x6-17016x8"></a>Get the <span 
 class="ptmbi7t---109">FlightGear </span>sources
     <br class="newline"><span 
 class="pcrr7t---109">cd $BUILDDIR/src</span>
     <br class="newline"><span 
 class="pcrr7t---109">setenv CVSROOT :pserver:cvs@cvs.flightgear.org:</span>
     <br class="newline"><span 
-class="pcrr7t---109">/var/cvs/FlightGear-0.7 </span>(one line!)
+class="pcrr7t---109">/var/cvs/FlightGear-0.X </span>(one line!)
     <br class="newline"><span 
 class="pcrr7t---109">cvs login</span>
-     <br class="newline">#enter &#8221;guest&#8221; for password
+     <br class="newline">Enter <span 
 class="cmmi-10--109">&lt;</span>guest<span 
 class="cmmi-10--109">&gt; </span>for password
     <br class="newline"><span 
 class="pcrr7t---109">cvs -z3 checkout FlightGear</span>
     </li>
     <li class="enumerate"><a 
-  name="x6-13016x8"></a>Build FlightGear
+  name="x6-17018x9"></a>Build <span 
 class="ptmbi7t---109">FlightGear</span>
     <br class="newline"><span 
 class="pcrr7t---109">cd $BUILDDIR/src/FlightGear</span>
     <br class="newline"><span 
 class="pcrr7t---109">patch -p0 &lt; ../jsb.diff</span>
     <br class="newline"><span 
 class="pcrr7t---109">./autogen.sh</span>
     <br class="newline"><span 
-class="pcrr7t---109">./configure --prefix=$BUILDDIR --includedir=</span>
+class="pcrr7t---109">./configure --prefix=$BUILDDIR</span>
     <br class="newline"><span 
-class="pcrr7t---109">$BUILDDIR --with-threads --without-x </span>(one line)
+class="pcrr7t---109">--with-threads --without-x </span>(one line)
     <br class="newline"><span 
 class="pcrr7t---109">make install</span>
     </li>
     <li class="enumerate"><a 
-  name="x6-13018x9"></a>Get the base data files (if you don&#8217;t have them already)
+  name="x6-17020x10"></a>Get the base data files (if you don&#8217;t have them already)
     <br class="newline"><span 
 class="pcrr7t---109">cd $BUILDDIR</span>
     <br class="newline"><span 
@ -516,29 +752,34 @@ class="pcrr7t---109">setenv CVSROOT :pserver:cvsguest@rockfish.net:</span>
 class="pcrr7t---109">/home/cvsroot </span>(one line)
     <br class="newline"><span 
 class="pcrr7t---109">cvs login</span>
-     <br class="newline">#password is &#8221;cvsguest&#8221;
+     <br class="newline">Password is &#8221;cvsguest&#8221;
     <br class="newline"><span 
 class="pcrr7t---109">cvs -z3 checkout fgfsbase</span>
     </li>
     <li class="enumerate"><a 
-  name="x6-13020x10"></a>Move data files (if you have them already)
+  name="x6-17022x11"></a>Move data files (if you have them already)
     <br class="newline">just make a symlink or copy data files to &#8221;fgfsbase&#8221; in $BUILDDIR
     <br class="newline">alternatively adjust <span 
 class="pcrr7t---109">--fg-root=xxx </span>parameter appropriately
     </li>
     <li class="enumerate"><a 
-  name="x6-13022x11"></a>Run FlightGear
+  name="x6-17024x12"></a>Run FlightGear
     <br class="newline"><span 
 class="pcrr7t---109">cd $BUILDDIR</span>
     <br class="newline"><span 
 class="pcrr7t---109">src/FlightGear/src/Main/fgfs</span></li></ol>
-   <h3 class="sectionHead"><span class="titlemark">2.4</span> <a 
+   <h3 class="sectionHead"><span class="titlemark">2.6</span> <a 
-href="getstart.html#QQ2-6-14" name="x6-140002.4">Compiling on other systems</a></h3>
+href="getstart.html#QQ2-6-18" name="x6-180002.6">Compiling on other systems</a></h3>
-<!--l. 399--><p class="noindent">Compiling on other Unix<a 
+<!--l. 535--><p class="noindent">Compiling on other UNIX<a 
-  name="dx6-14001"></a> systems - at least on IRIX<a 
+  name="dx6-18001"></a> systems - at least on IRIX<a 
-  name="dx6-14002"></a> and on Solaris<a 
+  name="dx6-18002"></a> and on Solaris<a 
-  name="dx6-14003"></a>, is pretty similar to
+  name="dx6-18003"></a>, is pretty similar to
 the procedure on Linux - given the presence of a working GNU C compiler. Especially
 IRIX and also recent releases of Solaris come with the basic OpenGL libraries.<a 
-  name="dx6-14004"></a>
+  name="dx6-18004"></a>
 Unfortunately the &#8221;glut&#8221; libraries are mostly missing and have to be installed separately
 (see the introductory remark to this chapter). As compilation of the &#8221;glut&#8221; sources is not
 a trivial task to everyone, you might want to use a pre-built binary. Everything you need
@ -547,103 +788,104 @@ usable is to place them into <span
 class="pcrr7t---109">/usr/lib/ </span>and <span 
 class="pcrr7t---109">/usr/include/GL/</span>. In case you insist
 on building the library yourself, you might want to have a look at FreeGLUT<a 
-  name="dx6-14005"></a>
+  name="dx6-18005"></a>
-<!--l. 410--><p class="indent">   <a 
+<!--l. 546--><p class="indent">   <a 
 href="http://freeglut.sourceforge.net/" >http://freeglut.sourceforge.net/</a>
-<!--l. 413--><p class="noindent">which should compile with minor tweaks. Necessary patches might be found in
+<!--l. 549--><p class="noindent">which should compile with minor tweaks. Necessary patches might be found in
-<!--l. 417--><p class="indent">   <a 
+<!--l. 553--><p class="indent">   <a 
 href="ftp://ftp.uni-duisburg.de/X11/OpenGL/freeglut_portable.patch" >ftp://ftp.uni-duisburg.de/X11/OpenGL/freeglut_portable.patch</a>
-                                                                     
+<!--l. 556--><p class="noindent">Please note that you do <span 
 <!--l. 420--><p class="noindent">Please note that you do <span 
 class="ptmb7t---109">not </span>want to create 64 bit binaries in IRIX with GCC (even if your
 CPU is a R10/12/14k) because GCC produces a broken &#8221;fgfs&#8221; binary (in case the
-compiler does&#8217;nt stop with &#8221;internal compiler error&#8221;). Things might look better if Eric
+compiler doesn&#8217;t stop with &#8221;internal compiler error&#8221;). Things might look better if Eric
 Hofman<a 
-  name="dx6-14006"></a> manages to tweak the FlightGear sources for proper compiling with MIPSPro
+  name="dx6-18006"></a> manages to tweak the <span 
 class="ptmbi7t---109">FlightGear </span>sources for proper compiling with MIPSPro
 compiler (it&#8217;s already mostly done).
-<!--l. 427--><p class="indent">   There should be a workplace for Microsoft Visual C++<a 
+<!--l. 563--><p class="indent">   There should be a workplace for Microsoft Visual C++<a 
-  name="dx6-14007"></a> (MSVC6) included in the
+  name="dx6-18007"></a> (MSVC6) included in the
 official <span 
 class="ptmbi7t---109">FlightGear </span>distribution. Macintosh<a 
-  name="dx6-14008"></a> users find the required CodeWarrior<a 
+  name="dx6-18008"></a> users find the required CodeWarrior<a 
-  name="dx6-14009"></a> files as a
+  name="dx6-18009"></a> files as a
 <span 
 class="pcrr7t---109">.bin </span>archive at
-<!--l. 432--><p class="indent">   <a 
+<!--l. 568--><p class="indent">   <a 
 href="http://icdweb.cc.purdue.edu/~walisser/fg/" >http://icdweb.cc.purdue.edu/<img 
-src="getstart2x.gif" alt="~"  class="tilde" > walisser/fg/</a>.
+src="getstart4x.gif" alt="~"  class="tilde" > walisser/fg/</a>.
-<!--l. 434--><p class="indent">   Numerous (although outdated, at times) hints on compiling on different systems are
+<!--l. 570--><p class="indent">   Numerous (although outdated, at times) hints on compiling on different systems are
 included in the source code under <span 
 class="pcrr7t---109">docs-mini</span>.
-   <h3 class="sectionHead"><span class="titlemark">2.5</span> <a 
+   <h3 class="sectionHead"><span class="titlemark">2.7</span> <a 
-href="getstart.html#QQ2-6-15" name="x6-150002.5">Installing the base package</a></h3>
+href="getstart.html#QQ2-6-19" name="x6-190002.7">Installing the base package</a></h3>
-<!--l. 440--><p class="noindent">If you succeeded in performing the steps named above, you will have a directory holding
+                                                                     
 <!--l. 576--><p class="noindent">If you succeeded in performing the steps named above, you will have a directory holding
 the executables for <span 
 class="ptmbi7t---109">FlightGear</span>. This is not yet sufficient for performing <span 
 class="ptmbi7t---109">FlightGear</span>,
 though. Besides those, you will need a collection of support data files (scenery,
 aircraft, sound) collected in the so-called base package. In case you compiled
 the latest official release, the accompanying base package is available from
-<!--l. 447--><p class="indent">   <a 
+<!--l. 583--><p class="indent">   <a 
 href="ftp://www.flightgear.org/pub/flightgear/Shared/fgfs-base-X.X.X.tar.gz" >ftp://www.flightgear.org/pub/flightgear/Shared/fgfs-base-X.X.X.tar.gz</a>.
-<!--l. 449--><p class="indent">   This package<a 
+<!--l. 585--><p class="indent">   This package<a 
-  name="dx6-15001"></a> is usually quite large (around 25 MB), but must be installed for
+  name="dx6-19001"></a> is usually quite large (around 25 MB), but must be installed for
 <span 
 class="ptmbi7t---109">FlightGear </span>to run. There is no compilation required for it. Just download it to
 <span 
 class="pcrr7t---109">/usr/local </span>and install it with
-<!--l. 453--><p class="indent">   <span 
+<!--l. 589--><p class="indent">   <span 
 class="pcrr7t---109">tar xvfz fgfs-base-X.X.X.tar.gz</span>.
-<!--l. 455--><p class="noindent">Now you should find all the <span 
+<!--l. 591--><p class="noindent">Now you should find all the <span 
 class="ptmbi7t---109">FlightGear </span>files under <span 
 class="pcrr7t---109">/usr/local/Flightgear </span>in the
 following directory structure:<a 
-  name="dx6-15002"></a><a 
+  name="dx6-19002"></a><a 
-  name="dx6-15003"></a>:
+  name="dx6-19003"></a>:
-<!--l. 461--><p class="indent">   <span 
+<!--l. 597--><p class="indent">   <span 
 class="pcrr7t---109">/usr/local/Flightgear</span>
-<!--l. 463--><p class="indent">   <span 
+<!--l. 599--><p class="indent">   <span 
 class="pcrr7t---109">/usr/local/Flightgear/Aircraft</span>
-<!--l. 465--><p class="indent">   <span 
+<!--l. 601--><p class="indent">   <span 
 class="pcrr7t---109">/usr/local/Flightgear/Aircraft-uiuc</span>
-<!--l. 467--><p class="indent">   . . .
+<!--l. 603--><p class="indent">   . . .
-<!--l. 469--><p class="indent">   <span 
+<!--l. 605--><p class="indent">   <span 
 class="pcrr7t---109">/usr/local/Flightgear/bin</span>
-<!--l. 471--><p class="indent">   . . .
+<!--l. 607--><p class="indent">   . . .
-<!--l. 473--><p class="indent">   <span 
+<!--l. 609--><p class="indent">   <span 
 class="pcrr7t---109">/usr/local/Flightgear/Weather</span>.
-   <h3 class="sectionHead"><span class="titlemark">2.6</span> <a 
+   <h3 class="sectionHead"><span class="titlemark">2.8</span> <a 
-href="getstart.html#QQ2-6-16" name="x6-160002.6">For test pilots only: Building the CVS snapshots</a></h3>
+href="getstart.html#QQ2-6-20" name="x6-200002.8">For test pilots only: Building the CVS snapshots</a></h3>
-                                                                     
+<!--l. 616--><p class="noindent">It you are into adventures or feel you&#8217;re an advanced user, you can try one of the recent
 <!--l. 480--><p class="noindent">It you are into adventures or feel you&#8217;re an advanced user, you can try one of the recent
 bleeding edge snapshots<a 
-  name="dx6-16001"></a><a 
+  name="dx6-20001"></a><a 
-  name="dx6-16002"></a> at
+  name="dx6-20002"></a> at
-<!--l. 483--><p class="indent">   <a 
+<!--l. 619--><p class="indent">   <a 
 href="http://www.flightgear.org/Downloads/" >http://www.flightgear.org/Downloads/</a>.
-<!--l. 486--><p class="noindent">In this case you have to get the most recent Snapshot from <span 
+<!--l. 622--><p class="noindent">In this case you have to get the most recent Snapshot from <span 
 class="ptmbi7t---109">SimGear </span>at
-<!--l. 490--><p class="indent">   <a 
+<!--l. 626--><p class="indent">   <a 
 href="http://www.simgear.org/downloads.html" >http://www.simgear.org/downloads.html</a>
-<!--l. 493--><p class="noindent">as well. But be prepared: These are for development and may (and often do) contain
+<!--l. 629--><p class="noindent">as well. But be prepared: These are for development and may (and often do) contain
 bugs.
-<!--l. 497--><p class="indent">   If you are using these CVS snapshots, the base package named above will usually not
+<!--l. 633--><p class="indent">   If you are using these CVS snapshots, the base package named above will usually not
 be in sync with the recent code and you have to download the most recent developer&#8217;s
 version from
-<!--l. 502--><p class="indent">   <a 
+<!--l. 638--><p class="indent">   <a 
 href="http://rockfish.net/fg/" >http://rockfish.net/fg/</a>.
-<!--l. 505--><p class="noindent">We suggest downloading this package <span 
+<!--l. 641--><p class="noindent">We suggest downloading this package <span 
 class="pcrr7t---109">fgfs</span>_<span 
 class="pcrr7t---109">base-snap.X.X.X.tar.gz </span>to a
 temporary directory. Now, decompress it using
-<!--l. 510--><p class="indent">   <span 
+                                                                     
 <!--l. 646--><p class="indent">   <span 
 class="pcrr7t---109">tar xvfz fgfs</span>_<span 
 class="pcrr7t---109">base-snap.X.X.X.tar.gz</span>.
-<!--l. 513--><p class="indent">   Finally, double-check you got the directory structure named above.
+<!--l. 649--><p class="indent">   Finally, double-check you got the directory structure named above.
--- a/Docs/InstallGuide/html/getstartch3.html
+++ b/Docs/InstallGuide/html/getstartch3.html
@ -6,7 +6,7 @@
 <meta name="generator" content="TeX4ht (http://www.cis.ohio-state.edu/~gurari/TeX4ht/mn.html)"> 
 <!-- html,2,info,next,sections+ --> 
 <meta name="src" content="getstart.tex"> 
-<meta name="date" content="2002-02-16 19:41:00"> 
+<meta name="date" content="2002-09-08 00:44:00"> 
 <link rel="stylesheet" type="text/css" href="getstart.css"> 
 </head><body 
 >
@ -17,13 +17,13 @@ href="getstartch2.html#tailgetstartch2.html" >prev-tail</a>] [<a
 href="#tailgetstartch3.html">tail</a>] [<a 
 href="getstartpa1.html#getstartch3.html" >up</a>] </p></div>
   <h2 class="chapterHead"><span class="titlemark">Chapter&nbsp;3</span><br><a 
-href="getstart.html#QQ2-7-17" name="x7-170003">Preflight: Installing <span 
+href="getstart.html#QQ2-7-21" name="x7-210003">Preflight: Installing <span 
 class="ptmbi7t---109">FlightGear </span></a></h2>
 <!--l. 33--><p class="noindent">You can skip this Section if you built <span 
 class="ptmbi7t---109">FlightGear </span>along the lines described in the
 previous Chapter. If you did not and you&#8217;re jumping in here, your first step will consist in
 installing the binaries. At present, there are pre-compiled binaries<a 
-  name="dx7-17001"></a> available
+  name="dx7-21001"></a> available
 for
     <ul class="itemize1">
     <li class="itemize">Windows (any flavor),
@ -34,11 +34,11 @@ for
     </li>
     <li class="itemize">SGI Irix.</li></ul>
   <h3 class="sectionHead"><span class="titlemark">3.1</span> <a 
-href="getstart.html#QQ2-7-18" name="x7-180003.1">Installing the binary distribution on a Windows system</a></h3>
+href="getstart.html#QQ2-7-22" name="x7-220003.1">Installing the binary distribution on a Windows system</a></h3>
 <a 
-  name="dx7-18001"></a>
+  name="dx7-22001"></a>
 <!--l. 49--><p class="noindent">The following supposes you are on a Windows (95/98/Me/NT/2000/XP) <a 
-  name="dx7-18002"></a>system.
+  name="dx7-22002"></a>system.
 Installing the binaries is quite simple. Go to
 <!--l. 53--><p class="indent">   <a 
 href="ftp://www.flightgear.org/pub/flightgear/Win32/" >ftp://www.flightgear.org/pub/flightgear/Win32/</a>
@ -69,58 +69,58 @@ simulator.
 chapter <a 
 href="getstartch2.html#x6-100002">2<!--tex4ht:ref: building--></a>.
   <h3 class="sectionHead"><span class="titlemark">3.2</span> <a 
-href="getstart.html#QQ2-7-19" name="x7-190003.2">Installing the binary distribution on a Macintosh system</a></h3>
+href="getstart.html#QQ2-7-23" name="x7-230003.2">Installing the binary distribution on a Macintosh system</a></h3>
 <a 
-  name="dx7-19001"></a>
+  name="dx7-23001"></a>
 <!--l. 89--><p class="noindent">If your Macintosh<a 
-  name="dx7-19002"></a> is running the conventional Mac OS 9<a 
+  name="dx7-23002"></a> is running the conventional Mac OS 9<a 
-  name="dx7-19003"></a> or earlier, there are versions up
+  name="dx7-23003"></a> or earlier, there are versions up
 to <span 
 class="ptmbi7t---109">FlightGear </span>0.7.6 available being provided courtesy Darrell Walisser)<a 
-  name="dx7-19004"></a>. Download the
+  name="dx7-23004"></a>. Download the
 file <span class="obeylines-h"><span 
 class="pcrr7t---109">FlightGear_Installer_0.X.X.sit</span></span> from the corresponding subdirectory
 under
-<!--l. 94--><p class="indent">   <a 
+<!--l. 93--><p class="indent">   <a 
 href="http://icdweb.cc.purdue.edu/~walisser/fg/" >http://icdweb.cc.purdue.edu/&nbsp;walisser/fg/</a>.
-<!--l. 97--><p class="noindent">This file contains the program as well as the required base package files (scenery etc.).
+<!--l. 96--><p class="noindent">This file contains the program as well as the required base package files (scenery etc.).
 For unpacking, use <span 
 class="pcrr7t---109">Stuffit Expander 5.0</span><a 
-  name="dx7-19005"></a> or later.
+  name="dx7-23005"></a> or later.
-<!--l. 101--><p class="indent">   The latest build available for Mac OS 9.x is 0.7.6, located in the same place.
+<!--l. 100--><p class="indent">   The latest build available for Mac OS 9.x is 0.7.6, located in the same place.
 The base package is part of the download for Mac OS 9.x, but not for Mac
 OSX.
-<!--l. 103--><p class="indent">   Alternatively, if you are running Mac OS X<a 
+<!--l. 102--><p class="indent">   Alternatively, if you are running Mac OS X<a 
-  name="dx7-19006"></a>, download <span 
+  name="dx7-23006"></a>, download <span 
 class="pcrr7t---109">fgfs-0.X.X.gz </span>from the
 same site named above. The Mac OS X builds are in a gzip file in the same
-directory. There is a readme file in the directory to help people identify what to
+directory. There is a Readme file in the directory to help people identify what to
 download.
-<!--l. 106--><p class="indent">   Mac OS X requires that you first download the base package. Then extract it
+<!--l. 105--><p class="indent">   Mac OS X requires that you first download the base package. Then extract it
 with
-<!--l. 108--><p class="noindent"><span 
+<!--l. 107--><p class="noindent"><span 
 class="pcrr7t---109">tar -zxvf fgfs-base-X.X.X.tar.gz</span>
 <br class="newline"><span 
 class="pcrr7t---109">gunzip fgfs-X.X.X.-date.gz</span>
-<!--l. 112--><p class="noindent">Note that there is no <span 
+<!--l. 111--><p class="noindent">Note that there is no <span 
 class="pcrr7t---109">runfgfs </span>script for Mac OS X yet.
   <h3 class="sectionHead"><span class="titlemark">3.3</span> <a 
-href="getstart.html#QQ2-7-20" name="x7-200003.3">Installing the binary distribution on a Debian Linux system</a></h3>
+href="getstart.html#QQ2-7-24" name="x7-240003.3">Installing the binary distribution on a Debian Linux system</a></h3>
 <a 
-  name="dx7-20001"></a>
+  name="dx7-24001"></a>
-<!--l. 119--><p class="noindent">Download the file <span class="obeylines-h"><span 
+<!--l. 118--><p class="noindent">Download the file <span class="obeylines-h"><span 
 class="pcrr7t---109">flightgear_0.7.6-6_i386.deb</span></span> (being provided courtesy Ove
 Kaaven)<a 
-  name="dx7-20002"></a> from any of the Debian<a 
+  name="dx7-24002"></a> from any of the Debian<a 
-  name="dx7-20003"></a> mirror sites listed at
+  name="dx7-24003"></a> mirror sites listed at
-<!--l. 123--><p class="indent">   <a 
+<!--l. 122--><p class="indent">   <a 
 href="http://packages.debian.org/unstable/games/flightgear.html" >http://packages.debian.org/unstable/games/flightgear.html</a>.
-<!--l. 126--><p class="noindent">Like any Debian package, this can be installed via
+<!--l. 125--><p class="noindent">Like any Debian package, this can be installed via
-<!--l. 130--><p class="indent">   <span class="obeylines-h"><span 
+<!--l. 129--><p class="indent">   <span class="obeylines-h"><span 
 class="pcrr7t---109">dpkg</span><span 
 class="pcrr7t---109">&nbsp;--install</span><span 
 class="pcrr7t---109">&nbsp;flightgear_0.7.6-6_i386.deb</span></span>.
-<!--l. 133--><p class="noindent">After installation, you will find the directory <span 
+<!--l. 132--><p class="noindent">After installation, you will find the directory <span 
 class="pcrr7t---109">/usr/local/Flightgear </span>containing
 the script <span 
 class="pcrr7t---109">runfgfs </span>to start the program.
@ -128,54 +128,73 @@ class="pcrr7t---109">runfgfs </span>to start the program.
   <h3 class="sectionHead"><span class="titlemark">3.4</span> <a 
-href="getstart.html#QQ2-7-21" name="x7-210003.4">Installing the binary distribution on a SGI IRIX system</a></h3>
+href="getstart.html#QQ2-7-25" name="x7-250003.4">Installing the binary distribution on a SGI IRIX system</a></h3>
 <a 
-  name="dx7-21001"></a>
+  name="dx7-25001"></a>
-<!--l. 142--><p class="noindent">If there are binaries available for SGI IRIX systems, download all the required files
+<!--l. 141--><p class="noindent">If there are binaries available for SGI IRIX systems, download all the required files
 (being provided courtesy Erik Hofman)<a 
-  name="dx7-21002"></a> from
+  name="dx7-25002"></a> from
-<!--l. 146--><p class="indent">   <a 
+<!--l. 145--><p class="indent">   <a 
 href="http://www.a1.nl/~ehofman/fgfs/" >http://www.a1.nl/&nbsp;ehofman/fgfs/</a>
-<!--l. 149--><p class="noindent">and install them. Now you can start <span 
+<!--l. 148--><p class="noindent">and install them. Now you can start <span 
 class="ptmbi7t---109">FlightGear </span>via running the script
 <br class="newline"><span 
 class="pcrr7t---109">/opt/bin/fgfs</span>.
   <h3 class="sectionHead"><span class="titlemark">3.5</span> <a 
-href="getstart.html#QQ2-7-22" name="x7-220003.5">Installing add-on scenery</a></h3>
+href="getstart.html#QQ2-7-26" name="x7-260003.5">Installing add-on scenery</a></h3>
 <a 
-  name="dx7-22001"></a>
+  name="dx7-26001"></a>
 <a 
-  name="dx7-22002"></a>
+  name="dx7-26002"></a>
-<!--l. 157--><p class="noindent">There is a complete set of scenery files worldwide available created by Curt Olson<a 
+<!--l. 156--><p class="noindent">There are two complete sets of scenery files with worldwide coverage available, now,
-  name="dx7-22003"></a> which
+being based on different source data. One data set was created by Curt Olson<a 
-can be downloaded via a clickable map at
+  name="dx7-26003"></a> and can be
-<!--l. 161--><p class="indent">   <a 
+downloaded via a clickable map<a 
  name="dx7-26004"></a> from
 <!--l. 159--><p class="indent">   <a 
 href="http://www.flightgear.org/Downloads/world-scenery.html" >http://www.flightgear.org/Downloads/world-scenery.html</a>
-<!--l. 164--><p class="noindent">Moreover, Curt provides the complete set of US Scenery on CD-ROM<a 
+<!--l. 162--><p class="noindent">Moreover, Curt provides the complete set of US Scenery on CD-ROM<a 
-  name="dx7-22004"></a> for those who
+  name="dx7-26005"></a> for those who
 really would like to fly over all of the USA. For more detail, check the remarks on the
 downloads page above.
-<!--l. 169--><p class="indent">   For installing these files, you have to unpack them under <span 
+<!--l. 167--><p class="indent">   An alternative data set was produced by William Riley<a 
-class="pcrr7t---109">/Flightgear/Scenery</span>.
+  name="dx7-26006"></a> and is available from
-Do not de-compress the numbered scenery files like 958402.gz! This will be done by
+<!--l. 170--><p class="indent">   <a 
 href="http://www.randdtechnologies.com/fgfs/newScenery/world-scenery.html" >http://www.randdtechnologies.com/fgfs/newScenery/world-scenery.html</a>
 <!--l. 173--><p class="noindent">again using a <a 
  name="dx7-26007"></a>.
 <!--l. 176--><p class="indent">   While the first data set is based on the USGS<a 
  name="dx7-26008"></a> data, the second one is based on the
 so-called VMap0<a 
  name="dx7-26009"></a> data set. While there may be more differences to discover, the first
 one has much better coast lines, while the latter sports world-wide coverage of
 streets, rivers, lakes, and more. Scenery provided in the base package is based
 on the second data set (though covering a small area around San Francisco,
 only).
 <!--l. 178--><p class="indent">   Installation of both data sets is identical. You have to unpack them under
 <span 
 class="pcrr7t---109">/Flightgear/Scenery</span>. Do not de-compress the numbered scenery files like
 958402.gz! This will be done by <span 
 class="ptmbi7t---109">FlightGear </span>on the fly.
-<!--l. 173--><p class="indent">   As an example, consider installation of the scenery package w120n30 containing the
+<!--l. 180--><p class="indent">   As an example, consider installation of the scenery package w120n30 containing the
 Grand Canyon Scenery.
-<!--l. 176--><p class="indent">   After having installed the base package<a 
+                                                                     
-  name="dx7-22005"></a>, you should have ended up with the following
+
 <!--l. 183--><p class="indent">   After having installed the base package<a 
  name="dx7-26010"></a>, you should have ended up with the following
 directory structure:
-<!--l. 179--><p class="noindent"><span 
+<!--l. 187--><p class="noindent"><span 
 class="pcrr7t---109">/usr/local/FlightGear/Scenery</span>
-<!--l. 182--><p class="noindent"><span 
+<!--l. 190--><p class="noindent"><span 
 class="pcrr7t---109">/usr/local/FlightGear/w130n30</span>
-<!--l. 185--><p class="noindent"><span 
+<!--l. 193--><p class="noindent"><span 
 class="pcrr7t---109">/usr/local/FlightGear/w130n30/w122n37</span>
 <br class="newline"><span 
 class="pcrr7t---109">/usr/local/FlightGear/Scenery/w130n30/w123n37</span>
-<!--l. 189--><p class="noindent">with the directories w122n37 and w123n37m, resp. containing numerous *.gz files.
+<!--l. 198--><p class="noindent">with the directories w122n37 and w123n37m, resp. containing numerous *.gz files.
 Installation of the Grand Canyon scenery adds to this the directories
-<!--l. 193--><p class="noindent"><span 
+<!--l. 203--><p class="noindent"><span 
 class="pcrr7t---109">/usr/local/FlightGear/w120n30/w112n30</span>
 <br class="newline"><span 
 class="pcrr7t---109">/usr/local/FlightGear/w120n30/w112n31</span>
@ -183,25 +202,27 @@ class="pcrr7t---109">/usr/local/FlightGear/w120n30/w112n31</span>
 class="pcrr7t---109">...</span>
 <br class="newline"><span 
 class="pcrr7t---109">/usr/local/FlightGear/w120n30/w120n39</span>.
-                                                                     
+<!--l. 210--><p class="indent">   You can exploit the <span 
-
+class="pcrr7t---109">--fg-scenery=</span><span 
-                                                                     
+class="ptmri7t---109">path </span>command line option, if you want to
 install different scenery sets in parallel or want to have scenery sitting in another
 place.
   <h3 class="sectionHead"><span class="titlemark">3.6</span> <a 
-href="getstart.html#QQ2-7-23" name="x7-230003.6">Installing documentation</a></h3>
+href="getstart.html#QQ2-7-27" name="x7-270003.6">Installing documentation</a></h3>
 <a 
-  name="dx7-23001"></a>
+  name="dx7-27001"></a>
-<!--l. 204--><p class="noindent">Most of the packages named above include the complete <span 
+<!--l. 216--><p class="noindent">Most of the packages named above include the complete <span 
 class="ptmbi7t---109">FlightGear </span>documentation
 including a .pdf version of this <span 
 class="ptmri7t---109">Installation and Getting Started </span>Guide intended for pretty
 printing using Adobe&#8217;s Acrobat Reader being available from
-<!--l. 209--><p class="indent">   <a 
+<!--l. 221--><p class="indent">   <a 
 href="http://www.adobe.com/acrobat" >http://www.adobe.com/acrobat</a>
-<!--l. 212--><p class="noindent">Moreover, if properly installed, the .html version can be accessed via <span 
+<!--l. 224--><p class="noindent">Moreover, if properly installed, the .html version can be accessed via <span 
 class="ptmbi7t---109">FlightGear</span>&#8217;s <span 
 class="pcrr7t---109">help</span>
 menu entry.
-<!--l. 216--><p class="indent">   Besides, the source code contains a directory <span 
+<!--l. 228--><p class="indent">   Besides, the source code contains a directory <span 
 class="pcrr7t---109">docs-mini </span>containing numerous
 ideas on and solutions to special problems. This is also a good place for further
 reading.
--- a/Docs/InstallGuide/html/getstartch4.html
+++ b/Docs/InstallGuide/html/getstartch4.html
--- a/Docs/InstallGuide/html/getstartch5.html
+++ b/Docs/InstallGuide/html/getstartch5.html
--- a/Docs/InstallGuide/html/getstartli1.html
+++ b/Docs/InstallGuide/html/getstartli1.html
@ -6,7 +6,7 @@
 <meta name="generator" content="TeX4ht (http://www.cis.ohio-state.edu/~gurari/TeX4ht/mn.html)"> 
 <!-- html,2,info,next,sections+ --> 
 <meta name="src" content="getstart.tex"> 
-<meta name="date" content="2002-02-16 19:41:00"> 
+<meta name="date" content="2002-09-08 00:44:00"> 
 <link rel="stylesheet" type="text/css" href="getstart.css"> 
 </head><body 
 >
@ -24,148 +24,170 @@ href="getstartpa1.html#x4-3000I" name="QQ2-4-3">Installation</a></span>
 href="getstartch1.html#x5-40001" name="QQ2-5-4">Want to have a free flight? Take <span 
 class="ptmbi7t---109">FlightGear</span>!</a></span>
 <br>   &nbsp;<span class="sectionToc">1.1 <a 
-href="getstartch1.html#x5-50001.1" name="QQ2-5-5">Yet another Flight Simulator?</a></span>
+href="getstartch1.html#x5-50001.1" name="QQ2-5-5">Yet Another Flight Simulator?</a></span>
 <br>   &nbsp;<span class="sectionToc">1.2 <a 
-href="getstartch1.html#x5-60001.2" name="QQ2-5-6">System requirements</a></span>
+href="getstartch1.html#x5-60001.2" name="QQ2-5-6">System Requirements</a></span>
 <br>   &nbsp;<span class="sectionToc">1.3 <a 
-href="getstartch1.html#x5-70001.3" name="QQ2-5-7">Which version should I use?</a></span>
+href="getstartch1.html#x5-70001.3" name="QQ2-5-7">Choosing A Version</a></span>
 <br>   &nbsp;<span class="sectionToc">1.4 <a 
-href="getstartch1.html#x5-80001.4" name="QQ2-5-8">Flight models</a></span>
+href="getstartch1.html#x5-80001.4" name="QQ2-5-8">Flight Dynamics Models</a></span>
 <br>   &nbsp;<span class="sectionToc">1.5 <a 
-href="getstartch1.html#x5-90001.5" name="QQ2-5-9">To whom this guide is addressed and how it is organized</a></span>
+href="getstartch1.html#x5-90001.5" name="QQ2-5-9">About This Guide</a></span>
 <br>   <span class="chapterToc">2 <a 
 href="getstartch2.html#x6-100002" name="QQ2-6-10">Building the plane: Compiling the program</a></span>
 <br>   &nbsp;<span class="sectionToc">2.1 <a 
-href="getstartch2.html#x6-110002.1" name="QQ2-6-11">Getting a development environment under Windows</a></span>
+href="getstartch2.html#x6-110002.1" name="QQ2-6-11">Preparing the development environment under Windows</a></span>
 <br>   &nbsp;<span class="sectionToc">2.2 <a 
-href="getstartch2.html#x6-120002.2" name="QQ2-6-12">Compiling <span 
+href="getstartch2.html#x6-120002.2" name="QQ2-6-12">Preparing the development environment under Windows</a></span>
 class="ptmbi7t---109">FlightGear </span>under Linux/Windows </a></span>
 <br>   &nbsp;<span class="sectionToc">2.3 <a 
-href="getstartch2.html#x6-130002.3" name="QQ2-6-13">Compiling <span 
+href="getstartch2.html#x6-130002.3" name="QQ2-6-13">One-time preparations for Linux and Windows users</a></span>
-class="ptmbi7t---109">FlightGear </span>under Mac OS 10.1 </a></span>
+<br>   &nbsp;&nbsp;<span class="subsectionToc">2.3.1 <a 
 href="getstartch2.html#x6-140002.3.1" name="QQ2-6-14">Installation of ZLIB</a></span>
 <br>   &nbsp;&nbsp;<span class="subsectionToc">2.3.2 <a 
 href="getstartch2.html#x6-150002.3.2" name="QQ2-6-15">Installation of Metakit</a></span>
 <br>   &nbsp;<span class="sectionToc">2.4 <a 
-href="getstartch2.html#x6-140002.4" name="QQ2-6-14">Compiling on other systems</a></span>
+href="getstartch2.html#x6-160002.4" name="QQ2-6-16">Compiling <span 
 class="ptmbi7t---109">FlightGear </span>under Linux/Windows </a></span>
 <br>   &nbsp;<span class="sectionToc">2.5 <a 
-href="getstartch2.html#x6-150002.5" name="QQ2-6-15">Installing the base package</a></span>
+href="getstartch2.html#x6-170002.5" name="QQ2-6-17">Compiling <span 
 class="ptmbi7t---109">FlightGear </span>under Mac OS X </a></span>
 <br>   &nbsp;<span class="sectionToc">2.6 <a 
-href="getstartch2.html#x6-160002.6" name="QQ2-6-16">For test pilots only: Building the CVS snapshots</a></span>
+href="getstartch2.html#x6-180002.6" name="QQ2-6-18">Compiling on other systems</a></span>
 <br>   &nbsp;<span class="sectionToc">2.7 <a 
 href="getstartch2.html#x6-190002.7" name="QQ2-6-19">Installing the base package</a></span>
 <br>   &nbsp;<span class="sectionToc">2.8 <a 
 href="getstartch2.html#x6-200002.8" name="QQ2-6-20">For test pilots only: Building the CVS snapshots</a></span>
 <br>   <span class="chapterToc">3 <a 
-href="getstartch3.html#x7-170003" name="QQ2-7-17">Preflight: Installing <span 
+href="getstartch3.html#x7-210003" name="QQ2-7-21">Preflight: Installing <span 
 class="ptmbi7t---109">FlightGear </span></a></span>
 <br>   &nbsp;<span class="sectionToc">3.1 <a 
-href="getstartch3.html#x7-180003.1" name="QQ2-7-18">Installing the binary distribution on a Windows system</a></span>
+href="getstartch3.html#x7-220003.1" name="QQ2-7-22">Installing the binary distribution on a Windows system</a></span>
 <br>   &nbsp;<span class="sectionToc">3.2 <a 
-href="getstartch3.html#x7-190003.2" name="QQ2-7-19">Installing the binary distribution on a Macintosh system</a></span>
+href="getstartch3.html#x7-230003.2" name="QQ2-7-23">Installing the binary distribution on a Macintosh system</a></span>
 <br>   &nbsp;<span class="sectionToc">3.3 <a 
-href="getstartch3.html#x7-200003.3" name="QQ2-7-20">Installing the binary distribution on a Debian Linux system</a></span>
+href="getstartch3.html#x7-240003.3" name="QQ2-7-24">Installing the binary distribution on a Debian Linux system</a></span>
 <br>   &nbsp;<span class="sectionToc">3.4 <a 
-href="getstartch3.html#x7-210003.4" name="QQ2-7-21">Installing the binary distribution on a SGI IRIX system</a></span>
+href="getstartch3.html#x7-250003.4" name="QQ2-7-25">Installing the binary distribution on a SGI IRIX system</a></span>
 <br>   &nbsp;<span class="sectionToc">3.5 <a 
-href="getstartch3.html#x7-220003.5" name="QQ2-7-22">Installing add-on scenery</a></span>
+href="getstartch3.html#x7-260003.5" name="QQ2-7-26">Installing add-on scenery</a></span>
 <br>   &nbsp;<span class="sectionToc">3.6 <a 
-href="getstartch3.html#x7-230003.6" name="QQ2-7-23">Installing documentation</a></span>
+href="getstartch3.html#x7-270003.6" name="QQ2-7-27">Installing documentation</a></span>
 <br>   <span class="partToc"><a 
-href="getstartpa2.html#x8-24000II" name="QQ2-8-24">Flying with <span 
+href="getstartpa2.html#x8-28000II" name="QQ2-8-28">Flying with <span 
 class="ptmbi7t---109">FlightGear</span></a></span>
 <br>   <span class="chapterToc">4 <a 
-href="getstartch4.html#x9-250004" name="QQ2-9-25">Takeoff: How to start the program</a></span>
+href="getstartch4.html#x9-290004" name="QQ2-9-29">Takeoff: How to start the program</a></span>
 <br>   &nbsp;<span class="sectionToc">4.1 <a 
-href="getstartch4.html#x9-260004.1" name="QQ2-9-26">Launching the simulator under Unix/Linux</a></span>
+href="getstartch4.html#x9-300004.1" name="QQ2-9-30">Launching the simulator under Unix/Linux</a></span>
 <br>   &nbsp;<span class="sectionToc">4.2 <a 
-href="getstartch4.html#x9-270004.2" name="QQ2-9-27">Launching the simulator under Windows</a></span>
+href="getstartch4.html#x9-310004.2" name="QQ2-9-31">Launching the simulator under Windows</a></span>
 <br>   &nbsp;<span class="sectionToc">4.3 <a 
-href="getstartch4.html#x9-280004.3" name="QQ2-9-28">Launching the simulator under Mac OS X</a></span>
+href="getstartch4.html#x9-320004.3" name="QQ2-9-32">Launching the simulator under Mac OS X</a></span>
 <br>   &nbsp;<span class="sectionToc">4.4 <a 
-href="getstartch4.html#x9-290004.4" name="QQ2-9-29">Command line parameters</a></span>
+href="getstartch4.html#x9-330004.4" name="QQ2-9-33">Command line parameters</a></span>
 <br>   &nbsp;&nbsp;<span class="subsectionToc">4.4.1 <a 
-href="getstartch4.html#x9-300004.4.1" name="QQ2-9-30">General Options</a></span>
+href="getstartch4.html#x9-340004.4.1" name="QQ2-9-34">General Options</a></span>
 <br>   &nbsp;&nbsp;<span class="subsectionToc">4.4.2 <a 
-href="getstartch4.html#x9-310004.4.2" name="QQ2-9-31">Features</a></span>
+href="getstartch4.html#x9-350004.4.2" name="QQ2-9-35">Features</a></span>
 <br>   &nbsp;&nbsp;<span class="subsectionToc">4.4.3 <a 
-href="getstartch4.html#x9-320004.4.3" name="QQ2-9-32">Flight model</a></span>
+href="getstartch4.html#x9-360004.4.3" name="QQ2-9-36">Aircraft</a></span>
 <br>   &nbsp;&nbsp;<span class="subsectionToc">4.4.4 <a 
-href="getstartch4.html#x9-330004.4.4" name="QQ2-9-33">Aircraft model directory (Only for the UIUC Flight Dynamics Model)</a></span>
+href="getstartch4.html#x9-370004.4.4" name="QQ2-9-37">Flight model</a></span>
 <br>   &nbsp;&nbsp;<span class="subsectionToc">4.4.5 <a 
-href="getstartch4.html#x9-340004.4.5" name="QQ2-9-34">Initial Position and Orientation</a></span>
+href="getstartch4.html#x9-380004.4.5" name="QQ2-9-38">Initial Position and Orientation</a></span>
 <br>   &nbsp;&nbsp;<span class="subsectionToc">4.4.6 <a 
-href="getstartch4.html#x9-350004.4.6" name="QQ2-9-35">Rendering Options</a></span>
+href="getstartch4.html#x9-390004.4.6" name="QQ2-9-39">Rendering Options</a></span>
 <br>   &nbsp;&nbsp;<span class="subsectionToc">4.4.7 <a 
-href="getstartch4.html#x9-360004.4.7" name="QQ2-9-36">HUD Options</a></span>
+href="getstartch4.html#x9-400004.4.7" name="QQ2-9-40">HUD Options</a></span>
 <br>   &nbsp;&nbsp;<span class="subsectionToc">4.4.8 <a 
-href="getstartch4.html#x9-370004.4.8" name="QQ2-9-37">Time Options</a></span>
+href="getstartch4.html#x9-410004.4.8" name="QQ2-9-41">Time Options</a></span>
 <br>   &nbsp;&nbsp;<span class="subsectionToc">4.4.9 <a 
-href="getstartch4.html#x9-380004.4.9" name="QQ2-9-38">Network Options</a></span>
+href="getstartch4.html#x9-420004.4.9" name="QQ2-9-42">Network Options</a></span>
 <br>   &nbsp;&nbsp;<span class="subsectionToc">4.4.10 <a 
-href="getstartch4.html#x9-390004.4.10" name="QQ2-9-39">Route/Waypoint Options</a></span>
+href="getstartch4.html#x9-430004.4.10" name="QQ2-9-43">Route/Waypoint Options</a></span>
 <br>   &nbsp;&nbsp;<span class="subsectionToc">4.4.11 <a 
-href="getstartch4.html#x9-400004.4.11" name="QQ2-9-40">IO Options</a></span>
+href="getstartch4.html#x9-440004.4.11" name="QQ2-9-44">IO Options</a></span>
 <br>   &nbsp;&nbsp;<span class="subsectionToc">4.4.12 <a 
-href="getstartch4.html#x9-410004.4.12" name="QQ2-9-41">Debugging options</a></span>
+href="getstartch4.html#x9-450004.4.12" name="QQ2-9-45">Debugging options</a></span>
-<br>   &nbsp;&nbsp;<span class="subsectionToc">4.4.13 <a 
+<br>   &nbsp;<span class="sectionToc">4.5 <a 
-href="getstartch4.html#x9-420004.4.13" name="QQ2-9-42">Joystick properties</a></span>
+href="getstartch4.html#x9-460004.5" name="QQ2-9-46">Joystick support</a></span>
 <br>   &nbsp;&nbsp;<span class="subsectionToc">4.5.1 <a 
 href="getstartch4.html#x9-470004.5.1" name="QQ2-9-47">Built-in joystick support</a></span>
 <br>   &nbsp;&nbsp;<span class="subsectionToc">4.5.2 <a 
 href="getstartch4.html#x9-550004.5.2" name="QQ2-9-55">Joystick support via .fgfsrc entries</a></span>
 <br>   &nbsp;<span class="sectionToc">4.6 <a 
 href="getstartch4.html#x9-560004.6" name="QQ2-9-56">A glance over our hangar</a></span>
 <br>   <span class="chapterToc">5 <a 
-href="getstartch5.html#x10-430005" name="QQ2-10-43">In-flight: All about instruments, keystrokes and menus</a></span>
+href="getstartch5.html#x10-570005" name="QQ2-10-57">In-flight: All about instruments, keystrokes and menus</a></span>
 <br>   &nbsp;<span class="sectionToc">5.1 <a 
-href="getstartch5.html#x10-440005.1" name="QQ2-10-44">Starting the engine</a></span>
+href="getstartch5.html#x10-580005.1" name="QQ2-10-58">Starting the engine</a></span>
 <br>   &nbsp;<span class="sectionToc">5.2 <a 
-href="getstartch5.html#x10-450005.2" name="QQ2-10-45">Keyboard controls</a></span>
+href="getstartch5.html#x10-590005.2" name="QQ2-10-59">Keyboard controls</a></span>
 <br>   &nbsp;<span class="sectionToc">5.3 <a 
-href="getstartch5.html#x10-460005.3" name="QQ2-10-46">Menu entries</a></span>
+href="getstartch5.html#x10-600005.3" name="QQ2-10-60">Menu entries</a></span>
 <br>   &nbsp;<span class="sectionToc">5.4 <a 
-href="getstartch5.html#x10-470005.4" name="QQ2-10-47">The Instrument Panel</a></span>
+href="getstartch5.html#x10-610005.4" name="QQ2-10-61">The Instrument Panel</a></span>
 <br>   &nbsp;<span class="sectionToc">5.5 <a 
-href="getstartch5.html#x10-480005.5" name="QQ2-10-48">The Head Up Display</a></span>
+href="getstartch5.html#x10-620005.5" name="QQ2-10-62">The Head Up Display</a></span>
 <br>   &nbsp;<span class="sectionToc">5.6 <a 
-href="getstartch5.html#x10-490005.6" name="QQ2-10-49">Mouse controlled actions</a></span>
+href="getstartch5.html#x10-630005.6" name="QQ2-10-63">Mouse controlled actions</a></span>
 <br>   &nbsp;<span class="sectionToc">5.7 <a 
-href="getstartch5.html#x10-500005.7" name="QQ2-10-50">Some further reading for pilot students</a></span>
+href="getstartch5.html#x10-640005.7" name="QQ2-10-64">Some further reading for student pilots</a></span>
 <br>   <span class="partToc"><a 
-href="getstartpa3.html#x11-51000III" name="QQ2-11-51">Appendices</a></span>
+href="getstartpa3.html#x11-65000III" name="QQ2-11-65">Appendices</a></span>
 <br>   <span class="appendixToc">A <a 
-href="getstartap1.html#x12-52000A" name="QQ2-12-52">Missed approach: If anything refuses to work</a></span>
+href="getstartap1.html#x12-66000A" name="QQ2-12-66">Missed approach: If anything refuses to work</a></span>
 <br>   &nbsp;<span class="sectionToc">A.1 <a 
-href="getstartap1.html#x12-53000A.1" name="QQ2-12-53">FlightGear Problem Reports</a></span>
+href="getstartap1.html#x12-67000A.1" name="QQ2-12-67">FlightGear Problem Reports</a></span>
 <br>   &nbsp;<span class="sectionToc">A.2 <a 
-href="getstartap1.html#x12-54000A.2" name="QQ2-12-54">General problems</a></span>
+href="getstartap1.html#x12-68000A.2" name="QQ2-12-68">General problems</a></span>
 <br>   &nbsp;<span class="sectionToc">A.3 <a 
-href="getstartap1.html#x12-55000A.3" name="QQ2-12-55">Potential problems under Linux</a></span>
+href="getstartap1.html#x12-69000A.3" name="QQ2-12-69">Potential problems under Linux</a></span>
 <br>   &nbsp;<span class="sectionToc">A.4 <a 
-href="getstartap1.html#x12-56000A.4" name="QQ2-12-56">Potential problems under Windows</a></span>
+href="getstartap1.html#x12-70000A.4" name="QQ2-12-70">Potential problems under Windows</a></span>
 <br>   <span class="appendixToc">B <a 
-href="getstartap2.html#x13-57000B" name="QQ2-13-57">Some words on OpenGL graphics drivers</a></span>
+href="getstartap2.html#x13-71000B" name="QQ2-13-71">Some words on OpenGL graphics drivers</a></span>
 <br>   &nbsp;<span class="sectionToc">B.1 <a 
-href="getstartap2.html#x13-58000B.1" name="QQ2-13-58">NVIDIA chip based cards under Linux</a></span>
+href="getstartap2.html#x13-72000B.1" name="QQ2-13-72">NVIDIA chip based cards under Linux</a></span>
 <br>   &nbsp;<span class="sectionToc">B.2 <a 
-href="getstartap2.html#x13-59000B.2" name="QQ2-13-59">NVIDIA chip based cards under Windows</a></span>
+href="getstartap2.html#x13-73000B.2" name="QQ2-13-73">NVIDIA chip based cards under Windows</a></span>
 <br>   &nbsp;<span class="sectionToc">B.3 <a 
-href="getstartap2.html#x13-60000B.3" name="QQ2-13-60">3DFX chip based cards under Windows</a></span>
+href="getstartap2.html#x13-74000B.3" name="QQ2-13-74">3DFX chip based cards under Windows</a></span>
 <br>   &nbsp;<span class="sectionToc">B.4 <a 
-href="getstartap2.html#x13-61000B.4" name="QQ2-13-61">An alternative approach for Windows users</a></span>
+href="getstartap2.html#x13-75000B.4" name="QQ2-13-75">An alternative approach for Windows users</a></span>
 <br>   &nbsp;<span class="sectionToc">B.5 <a 
-href="getstartap2.html#x13-62000B.5" name="QQ2-13-62">3DFX chip based cards under Linux</a></span>
+href="getstartap2.html#x13-76000B.5" name="QQ2-13-76">3DFX chip based cards under Linux</a></span>
 <br>   &nbsp;<span class="sectionToc">B.6 <a 
-href="getstartap2.html#x13-63000B.6" name="QQ2-13-63">ATI chip based cards under Linux</a></span>
+href="getstartap2.html#x13-77000B.6" name="QQ2-13-77">ATI chip based cards under Linux</a></span>
 <br>   &nbsp;<span class="sectionToc">B.7 <a 
-href="getstartap2.html#x13-64000B.7" name="QQ2-13-64">Building your own OpenGL support under Linux</a></span>
+href="getstartap2.html#x13-78000B.7" name="QQ2-13-78">Building your own OpenGL support under Linux</a></span>
 <br>   &nbsp;<span class="sectionToc">B.8 <a 
-href="getstartap2.html#x13-65000B.8" name="QQ2-13-65">OpenGL on MacIntosh</a></span>
+href="getstartap2.html#x13-79000B.8" name="QQ2-13-79">OpenGL on Macintosh</a></span>
 <br>   <span class="appendixToc">C <a 
-href="getstartap3.html#x14-66000C" name="QQ2-14-66">Landing: Some further thoughts before leaving the plane</a></span>
+href="getstartap3.html#x14-80000C" name="QQ2-14-80">Landing: Some further thoughts before leaving the plane</a></span>
 <br>   &nbsp;<span class="sectionToc">C.1 <a 
-href="getstartap3.html#x14-67000C.1" name="QQ2-14-67">A not so Short History of <span 
+href="getstartap3.html#x14-81000C.1" name="QQ2-14-81">A Sketch on the History of <span 
 class="ptmbi7t---109">FlightGear</span></a></span>
 <br>   &nbsp;&nbsp;<span class="subsectionToc">C.1.1 <a 
 href="getstartap3.html#x14-82000C.1.1" name="QQ2-14-82">Scenery</a></span>
 <br>   &nbsp;&nbsp;<span class="subsectionToc">C.1.2 <a 
 href="getstartap3.html#x14-83000C.1.2" name="QQ2-14-83">Aircraft</a></span>
 <br>   &nbsp;&nbsp;<span class="subsectionToc">C.1.3 <a 
 href="getstartap3.html#x14-84000C.1.3" name="QQ2-14-84">Environment</a></span>
 <br>   &nbsp;&nbsp;<span class="subsectionToc">C.1.4 <a 
 href="getstartap3.html#x14-85000C.1.4" name="QQ2-14-85">User Interface</a></span>
 <br>   &nbsp;<span class="sectionToc">C.2 <a 
-href="getstartap3.html#x14-68000C.2" name="QQ2-14-68">Those, who did the work</a></span>
+href="getstartap3.html#x14-86000C.2" name="QQ2-14-86">Those, who did the work</a></span>
 <br>   &nbsp;<span class="sectionToc">C.3 <a 
-href="getstartap3.html#x14-69000C.3" name="QQ2-14-69">What remains to be done</a></span>
+href="getstartap3.html#x14-87000C.3" name="QQ2-14-87">What remains to be done</a></span>
 <br>   <span class="chapterToc"> <a 
-href="getstartap3.html#Q1-14-71">Index</a></span>
+href="getstartap3.html#Q1-14-89">Index</a></span>
   </div>
--- a/Docs/InstallGuide/html/getstartli2.html
+++ b/Docs/InstallGuide/html/getstartli2.html
@ -6,7 +6,7 @@
 <meta name="generator" content="TeX4ht (http://www.cis.ohio-state.edu/~gurari/TeX4ht/mn.html)"> 
 <!-- html,2,info,next,sections+ --> 
 <meta name="src" content="getstart.tex"> 
-<meta name="date" content="2002-02-16 19:41:00"> 
+<meta name="date" content="2002-09-08 00:44:00"> 
 <link rel="stylesheet" type="text/css" href="getstart.css"> 
 </head><body 
 >
@ -46,7 +46,7 @@ Generally, there will be executable programs (binaries) available for several
 platforms. Those on such systems who want to take off immediately, without going
 through the potentially troublesome process of compiling, may skip this Chapter.
 <!--l. 59--><p class="noindent">In Chapter <a 
-href="getstartch3.html#x7-170003">3<!--tex4ht:ref: prefligh--></a>, <span 
+href="getstartch3.html#x7-210003">3<!--tex4ht:ref: prefligh--></a>, <span 
 class="ptmri7t---109">Preflight: Installing </span><span 
 class="ptmbi7t---109">FlightGear</span>, you will find instructions for installing the
 binaries<a 
@ -58,7 +58,7 @@ package<a
 class="ptmb7t---109">Part II: Flying with </span><span 
 class="ptmbi7t---109">FlightGear</span>
 <!--l. 70--><p class="noindent">The following Chapter <a 
-href="getstartch4.html#x9-250004">4<!--tex4ht:ref: takeoff--></a>, <span 
+href="getstartch4.html#x9-290004">4<!--tex4ht:ref: takeoff--></a>, <span 
 class="ptmri7t---109">Takeoff: How to start the program</span>, describes how to actually
 start the installed program. It includes an overview on the numerous command line
 options as well as configuration files.
@ -66,7 +66,7 @@ options as well as configuration files.
 <!--l. 75--><p class="noindent">Chapter <a 
-href="getstartch5.html#x10-430005">5<!--tex4ht:ref: flight--></a>, <span 
+href="getstartch5.html#x10-570005">5<!--tex4ht:ref: flight--></a>, <span 
 class="ptmri7t---109">In-flight: All about instruments, keystrokes and menus</span>, describes how to
 operate the program, i. e. how to actually fly with <span 
 class="ptmbi7t---109">FlightGear</span>. This includes a (hopefully)
@ -74,19 +74,19 @@ complete list of pre-defined keyboard commands, an overview on the menu entries,
 detailed descriptions on the instrument panel and HUD (head up display), as well as hints
 on using the mouse functions.
 <!--l. 83--><p class="noindent">In Appendix <a 
-href="getstartap1.html#x12-52000A">A<!--tex4ht:ref: missed--></a>, <span 
+href="getstartap1.html#x12-66000A">A<!--tex4ht:ref: missed--></a>, <span 
 class="ptmri7t---109">Missed approach: If anything refuses to work</span>, we try to help you work
 through some common problems faced when using <span 
 class="ptmbi7t---109">FlightGear</span>.
 <!--l. 88--><p class="noindent">The Appendix <a 
-href="getstartap2.html#x13-57000B">B<!--tex4ht:ref: opengl--></a>, <span 
+href="getstartap2.html#x13-71000B">B<!--tex4ht:ref: opengl--></a>, <span 
 class="ptmri7t---109">OpenGL graphics drivers</span>, describes some special problems you may
 encounter in case your system lacks support for the OpenGL graphics API OpenGL<a 
  name="dx3-2003"></a>
 which <span 
 class="ptmbi7t---109">FlightGear </span>is based on.
 <!--l. 92--><p class="noindent">In the final Appendix <a 
-href="getstartap3.html#x14-66000C">C<!--tex4ht:ref: landing--></a>, <span 
+href="getstartap3.html#x14-80000C">C<!--tex4ht:ref: landing--></a>, <span 
 class="ptmri7t---109">Landing: Some further thoughts before leaving the plane</span>, we
 would like to give credit to those who deserve it, sketch an overview on the development
 of <span 
@ -105,18 +105,18 @@ class="td11">        </td>
 valign="baseline" id="TBL-2-2-"><td  align="left" nowrap="nowrap" id="TBL-2-2-1"  
 class="td11"> Users of binary distributions (notably under Windows):</td><td  align="left" nowrap="nowrap" id="TBL-2-2-2"  
 class="td11"> <a 
-href="getstartch3.html#x7-170003">3<!--tex4ht:ref: prefligh--></a>     </td>
+href="getstartch3.html#x7-210003">3<!--tex4ht:ref: prefligh--></a>     </td>
 </tr><tr  
 valign="baseline" id="TBL-2-3-"><td  align="left" nowrap="nowrap" id="TBL-2-3-1"  
 class="td11"> Installation under Linux/UNIX:                                      </td><td  align="left" nowrap="nowrap" id="TBL-2-3-2"  
 class="td11"> <a 
 href="getstartch2.html#x6-100002">2<!--tex4ht:ref: building--></a>, <a 
-href="getstartch3.html#x7-170003">3<!--tex4ht:ref: prefligh--></a> </td>
+href="getstartch3.html#x7-210003">3<!--tex4ht:ref: prefligh--></a> </td>
 </tr><tr  
 valign="baseline" id="TBL-2-4-"><td  align="left" nowrap="nowrap" id="TBL-2-4-1"  
-class="td11"> Installation under MacIntosh:                                         </td><td  align="left" nowrap="nowrap" id="TBL-2-4-2"  
+class="td11"> Installation under Macintosh:                                         </td><td  align="left" nowrap="nowrap" id="TBL-2-4-2"  
 class="td11"> <a 
-href="getstartch3.html#x7-170003">3<!--tex4ht:ref: prefligh--></a>     </td>
+href="getstartch3.html#x7-210003">3<!--tex4ht:ref: prefligh--></a>     </td>
 </tr><tr  
 valign="baseline" id="TBL-2-5-"><td  align="left" nowrap="nowrap" id="TBL-2-5-1"  
 class="td11"> <span 
@ -126,12 +126,12 @@ class="td11">        </td>
 valign="baseline" id="TBL-2-6-"><td  align="left" nowrap="nowrap" id="TBL-2-6-1"  
 class="td11"> Program start (all users):                                                 </td><td  align="left" nowrap="nowrap" id="TBL-2-6-2"  
 class="td11"> <a 
-href="getstartch4.html#x9-250004">4<!--tex4ht:ref: takeoff--></a>     </td>
+href="getstartch4.html#x9-290004">4<!--tex4ht:ref: takeoff--></a>     </td>
 </tr><tr  
 valign="baseline" id="TBL-2-7-"><td  align="left" nowrap="nowrap" id="TBL-2-7-1"  
 class="td11"> Keycodes, Panel, Mouse. . . (all users):                           </td><td  align="left" nowrap="nowrap" id="TBL-2-7-2"  
 class="td11"> <a 
-href="getstartch5.html#x10-430005">5<!--tex4ht:ref: flight--></a>     </td>
+href="getstartch5.html#x10-570005">5<!--tex4ht:ref: flight--></a>     </td>
 </tr><tr  
 valign="baseline" id="TBL-2-8-"><td  align="left" nowrap="nowrap" id="TBL-2-8-1"  
 class="td11"> <span 
@ -141,19 +141,19 @@ class="td11">        </td>
 valign="baseline" id="TBL-2-9-"><td  align="left" nowrap="nowrap" id="TBL-2-9-1"  
 class="td11"> General issues:                                                                </td><td  align="left" nowrap="nowrap" id="TBL-2-9-2"  
 class="td11"> <a 
-href="getstartap1.html#x12-52000A">A<!--tex4ht:ref: missed--></a>    </td>
+href="getstartap1.html#x12-66000A">A<!--tex4ht:ref: missed--></a>    </td>
 </tr><tr  
 valign="baseline" id="TBL-2-10-"><td  align="left" nowrap="nowrap" id="TBL-2-10-1"  
 class="td11"> Graphics problems:                                                         </td><td  align="left" nowrap="nowrap" id="TBL-2-10-2"  
 class="td11"> <a 
-href="getstartap2.html#x13-57000B">B<!--tex4ht:ref: opengl--></a>    </td>
+href="getstartap2.html#x13-71000B">B<!--tex4ht:ref: opengl--></a>    </td>
 </tr><tr  
 valign="baseline" id="TBL-2-11-"><td  align="left" nowrap="nowrap" id="TBL-2-11-1"  
 class="td11"> <span 
 class="ptmb7t---109">Optionally                                                                      </span></td><td  align="left" nowrap="nowrap" id="TBL-2-11-2"  
 class="td11"> <a 
 href="getstartch1.html#x5-40001">1<!--tex4ht:ref: free--></a>, <a 
-href="getstartap3.html#x14-66000C">C<!--tex4ht:ref: landing--></a></td>
+href="getstartap3.html#x14-80000C">C<!--tex4ht:ref: landing--></a></td>
   </tr><!--ll--></table>
 </div>
 <!--l. 118--><p class="noindent">While this introductory guide is meant to be self contained, we strongly suggest having a
@ -217,7 +217,7 @@ class="pcrr7t---109">runfgfs </span>script or the batch file <span
 class="pcrr7t---109">runfgfs.bat</span>, respectively.
 <!--l. 165--><p class="indent">   There is no guarantee for this approach to work, though. If it doesn&#8217;t, don&#8217;t give up!
 Have a closer look through this guide notably Section <a 
-href="getstartch3.html#x7-170003">3<!--tex4ht:ref: prefligh--></a> and be sure to check out the
+href="getstartch3.html#x7-210003">3<!--tex4ht:ref: prefligh--></a> and be sure to check out the
 FAQ<a 
  name="dx3-2015"></a>.
--- a/Docs/InstallGuide/html/getstartli3.html
+++ b/Docs/InstallGuide/html/getstartli3.html
--- a/Docs/InstallGuide/html/getstartpa1.html
+++ b/Docs/InstallGuide/html/getstartpa1.html
@ -6,7 +6,7 @@
 <meta name="generator" content="TeX4ht (http://www.cis.ohio-state.edu/~gurari/TeX4ht/mn.html)"> 
 <!-- html,2,info,next,sections+ --> 
 <meta name="src" content="getstart.tex"> 
-<meta name="date" content="2002-02-16 19:41:00"> 
+<meta name="date" content="2002-09-08 00:44:00"> 
 <link rel="stylesheet" type="text/css" href="getstart.css"> 
 </head><body 
 >
@ -26,46 +26,50 @@ href="getstart.html#QQ2-4-3" name="x4-3000I">Installation</a></h1>
 href="getstartch1.html#x5-40001" name="QQ2-5-4">Want to have a free flight? Take <span 
 class="ptmbi7t---109">FlightGear</span>!</a></span>
 <br>   &nbsp;<span class="sectionToc">1.1 <a 
-href="getstartch1.html#x5-50001.1" name="QQ2-5-5">Yet another Flight Simulator?</a></span>
+href="getstartch1.html#x5-50001.1" name="QQ2-5-5">Yet Another Flight Simulator?</a></span>
 <br>   &nbsp;<span class="sectionToc">1.2 <a 
-href="getstartch1.html#x5-60001.2" name="QQ2-5-6">System requirements</a></span>
+href="getstartch1.html#x5-60001.2" name="QQ2-5-6">System Requirements</a></span>
 <br>   &nbsp;<span class="sectionToc">1.3 <a 
-href="getstartch1.html#x5-70001.3" name="QQ2-5-7">Which version should I use?</a></span>
+href="getstartch1.html#x5-70001.3" name="QQ2-5-7">Choosing A Version</a></span>
 <br>   &nbsp;<span class="sectionToc">1.4 <a 
-href="getstartch1.html#x5-80001.4" name="QQ2-5-8">Flight models</a></span>
+href="getstartch1.html#x5-80001.4" name="QQ2-5-8">Flight Dynamics Models</a></span>
 <br>   &nbsp;<span class="sectionToc">1.5 <a 
-href="getstartch1.html#x5-90001.5" name="QQ2-5-9">To whom this guide is addressed and how it is organized</a></span>
+href="getstartch1.html#x5-90001.5" name="QQ2-5-9">About This Guide</a></span>
 <br>   <span class="chapterToc">2 <a 
 href="getstartch2.html#x6-100002" name="QQ2-6-10">Building the plane: Compiling the program</a></span>
 <br>   &nbsp;<span class="sectionToc">2.1 <a 
-href="getstartch2.html#x6-110002.1" name="QQ2-6-11">Getting a development environment under Windows</a></span>
+href="getstartch2.html#x6-110002.1" name="QQ2-6-11">Preparing the development environment under Windows</a></span>
 <br>   &nbsp;<span class="sectionToc">2.2 <a 
-href="getstartch2.html#x6-120002.2" name="QQ2-6-12">Compiling <span 
+href="getstartch2.html#x6-120002.2" name="QQ2-6-12">Preparing the development environment under Windows</a></span>
 class="ptmbi7t---109">FlightGear </span>under Linux/Windows </a></span>
 <br>   &nbsp;<span class="sectionToc">2.3 <a 
-href="getstartch2.html#x6-130002.3" name="QQ2-6-13">Compiling <span 
+href="getstartch2.html#x6-130002.3" name="QQ2-6-13">One-time preparations for Linux and Windows users</a></span>
 class="ptmbi7t---109">FlightGear </span>under Mac OS 10.1 </a></span>
 <br>   &nbsp;<span class="sectionToc">2.4 <a 
-href="getstartch2.html#x6-140002.4" name="QQ2-6-14">Compiling on other systems</a></span>
+href="getstartch2.html#x6-160002.4" name="QQ2-6-16">Compiling <span 
 class="ptmbi7t---109">FlightGear </span>under Linux/Windows </a></span>
 <br>   &nbsp;<span class="sectionToc">2.5 <a 
-href="getstartch2.html#x6-150002.5" name="QQ2-6-15">Installing the base package</a></span>
+href="getstartch2.html#x6-170002.5" name="QQ2-6-17">Compiling <span 
 class="ptmbi7t---109">FlightGear </span>under Mac OS X </a></span>
 <br>   &nbsp;<span class="sectionToc">2.6 <a 
-href="getstartch2.html#x6-160002.6" name="QQ2-6-16">For test pilots only: Building the CVS snapshots</a></span>
+href="getstartch2.html#x6-180002.6" name="QQ2-6-18">Compiling on other systems</a></span>
 <br>   &nbsp;<span class="sectionToc">2.7 <a 
 href="getstartch2.html#x6-190002.7" name="QQ2-6-19">Installing the base package</a></span>
 <br>   &nbsp;<span class="sectionToc">2.8 <a 
 href="getstartch2.html#x6-200002.8" name="QQ2-6-20">For test pilots only: Building the CVS snapshots</a></span>
 <br>   <span class="chapterToc">3 <a 
-href="getstartch3.html#x7-170003" name="QQ2-7-17">Preflight: Installing <span 
+href="getstartch3.html#x7-210003" name="QQ2-7-21">Preflight: Installing <span 
 class="ptmbi7t---109">FlightGear </span></a></span>
 <br>   &nbsp;<span class="sectionToc">3.1 <a 
-href="getstartch3.html#x7-180003.1" name="QQ2-7-18">Installing the binary distribution on a Windows system</a></span>
+href="getstartch3.html#x7-220003.1" name="QQ2-7-22">Installing the binary distribution on a Windows system</a></span>
 <br>   &nbsp;<span class="sectionToc">3.2 <a 
-href="getstartch3.html#x7-190003.2" name="QQ2-7-19">Installing the binary distribution on a Macintosh system</a></span>
+href="getstartch3.html#x7-230003.2" name="QQ2-7-23">Installing the binary distribution on a Macintosh system</a></span>
 <br>   &nbsp;<span class="sectionToc">3.3 <a 
-href="getstartch3.html#x7-200003.3" name="QQ2-7-20">Installing the binary distribution on a Debian Linux system</a></span>
+href="getstartch3.html#x7-240003.3" name="QQ2-7-24">Installing the binary distribution on a Debian Linux system</a></span>
 <br>   &nbsp;<span class="sectionToc">3.4 <a 
-href="getstartch3.html#x7-210003.4" name="QQ2-7-21">Installing the binary distribution on a SGI IRIX system</a></span>
+href="getstartch3.html#x7-250003.4" name="QQ2-7-25">Installing the binary distribution on a SGI IRIX system</a></span>
 <br>   &nbsp;<span class="sectionToc">3.5 <a 
-href="getstartch3.html#x7-220003.5" name="QQ2-7-22">Installing add-on scenery</a></span>
+href="getstartch3.html#x7-260003.5" name="QQ2-7-26">Installing add-on scenery</a></span>
 <br>   &nbsp;<span class="sectionToc">3.6 <a 
-href="getstartch3.html#x7-230003.6" name="QQ2-7-23">Installing documentation</a></span>
+href="getstartch3.html#x7-270003.6" name="QQ2-7-27">Installing documentation</a></span>
   </div>
--- a/Docs/InstallGuide/html/getstartpa2.html
+++ b/Docs/InstallGuide/html/getstartpa2.html
@ -6,7 +6,7 @@
 <meta name="generator" content="TeX4ht (http://www.cis.ohio-state.edu/~gurari/TeX4ht/mn.html)"> 
 <!-- html,2,info,next,sections+ --> 
 <meta name="src" content="getstart.tex"> 
-<meta name="date" content="2002-02-16 19:41:00"> 
+<meta name="date" content="2002-09-08 00:44:00"> 
 <link rel="stylesheet" type="text/css" href="getstart.css"> 
 </head><body 
 >
@ -17,38 +17,42 @@ href="getstartch3.html#tailgetstartch3.html" >prev-tail</a>] [<a
 href="#tailgetstartpa2.html">tail</a>] [<a 
 href="getstart.html#getstartpa2.html" >up</a>] </p></div>
   <h1 class="partHead"><span class="titlemark">Part&nbsp;II<br></span><a 
-href="getstart.html#QQ2-8-24" name="x8-24000II">Flying with <span 
+href="getstart.html#QQ2-8-28" name="x8-28000II">Flying with <span 
 class="ptmbi7t---109">FlightGear</span></a></h1>
   <div class="chapterTOCS">
 <br>   <span class="chapterToc">4 <a 
-href="getstartch4.html#x9-250004" name="QQ2-9-25">Takeoff: How to start the program</a></span>
+href="getstartch4.html#x9-290004" name="QQ2-9-29">Takeoff: How to start the program</a></span>
 <br>   &nbsp;<span class="sectionToc">4.1 <a 
-href="getstartch4.html#x9-260004.1" name="QQ2-9-26">Launching the simulator under Unix/Linux</a></span>
+href="getstartch4.html#x9-300004.1" name="QQ2-9-30">Launching the simulator under Unix/Linux</a></span>
 <br>   &nbsp;<span class="sectionToc">4.2 <a 
-href="getstartch4.html#x9-270004.2" name="QQ2-9-27">Launching the simulator under Windows</a></span>
+href="getstartch4.html#x9-310004.2" name="QQ2-9-31">Launching the simulator under Windows</a></span>
 <br>   &nbsp;<span class="sectionToc">4.3 <a 
-href="getstartch4.html#x9-280004.3" name="QQ2-9-28">Launching the simulator under Mac OS X</a></span>
+href="getstartch4.html#x9-320004.3" name="QQ2-9-32">Launching the simulator under Mac OS X</a></span>
 <br>   &nbsp;<span class="sectionToc">4.4 <a 
-href="getstartch4.html#x9-290004.4" name="QQ2-9-29">Command line parameters</a></span>
+href="getstartch4.html#x9-330004.4" name="QQ2-9-33">Command line parameters</a></span>
 <br>   &nbsp;<span class="sectionToc">4.5 <a 
 href="getstartch4.html#x9-460004.5" name="QQ2-9-46">Joystick support</a></span>
 <br>   &nbsp;<span class="sectionToc">4.6 <a 
 href="getstartch4.html#x9-560004.6" name="QQ2-9-56">A glance over our hangar</a></span>
 <br>   <span class="chapterToc">5 <a 
-href="getstartch5.html#x10-430005" name="QQ2-10-43">In-flight: All about instruments, keystrokes and menus</a></span>
+href="getstartch5.html#x10-570005" name="QQ2-10-57">In-flight: All about instruments, keystrokes and menus</a></span>
 <br>   &nbsp;<span class="sectionToc">5.1 <a 
-href="getstartch5.html#x10-440005.1" name="QQ2-10-44">Starting the engine</a></span>
+href="getstartch5.html#x10-580005.1" name="QQ2-10-58">Starting the engine</a></span>
 <br>   &nbsp;<span class="sectionToc">5.2 <a 
-href="getstartch5.html#x10-450005.2" name="QQ2-10-45">Keyboard controls</a></span>
+href="getstartch5.html#x10-590005.2" name="QQ2-10-59">Keyboard controls</a></span>
 <br>   &nbsp;<span class="sectionToc">5.3 <a 
-href="getstartch5.html#x10-460005.3" name="QQ2-10-46">Menu entries</a></span>
+href="getstartch5.html#x10-600005.3" name="QQ2-10-60">Menu entries</a></span>
 <br>   &nbsp;<span class="sectionToc">5.4 <a 
-href="getstartch5.html#x10-470005.4" name="QQ2-10-47">The Instrument Panel</a></span>
+href="getstartch5.html#x10-610005.4" name="QQ2-10-61">The Instrument Panel</a></span>
 <br>   &nbsp;<span class="sectionToc">5.5 <a 
-href="getstartch5.html#x10-480005.5" name="QQ2-10-48">The Head Up Display</a></span>
+href="getstartch5.html#x10-620005.5" name="QQ2-10-62">The Head Up Display</a></span>
 <br>   &nbsp;<span class="sectionToc">5.6 <a 
-href="getstartch5.html#x10-490005.6" name="QQ2-10-49">Mouse controlled actions</a></span>
+href="getstartch5.html#x10-630005.6" name="QQ2-10-63">Mouse controlled actions</a></span>
 <br>   &nbsp;<span class="sectionToc">5.7 <a 
-href="getstartch5.html#x10-500005.7" name="QQ2-10-50">Some further reading for pilot students</a></span>
+href="getstartch5.html#x10-640005.7" name="QQ2-10-64">Some further reading for student pilots</a></span>
   </div>
--- a/Docs/InstallGuide/html/getstartpa3.html
+++ b/Docs/InstallGuide/html/getstartpa3.html
@ -6,7 +6,7 @@
 <meta name="generator" content="TeX4ht (http://www.cis.ohio-state.edu/~gurari/TeX4ht/mn.html)"> 
 <!-- html,2,info,next,sections+ --> 
 <meta name="src" content="getstart.tex"> 
-<meta name="date" content="2002-02-16 19:41:00"> 
+<meta name="date" content="2002-09-08 00:44:00"> 
 <link rel="stylesheet" type="text/css" href="getstart.css"> 
 </head><body 
 >
@ -17,65 +17,65 @@ href="getstartch5.html#tailgetstartch5.html" >prev-tail</a>] [<a
 href="#tailgetstartpa3.html">tail</a>] [<a 
 href="getstart.html#getstartpa3.html" >up</a>] </p></div>
   <h1 class="partHead"><span class="titlemark">Part&nbsp;III<br></span><a 
-href="getstart.html#QQ2-11-51" name="x11-51000III">Appendices</a></h1>
+href="getstart.html#QQ2-11-65" name="x11-65000III">Appendices</a></h1>
 <a 
-  name="x11-51001r43"></a>
+  name="x11-65001r57"></a>
   <div class="appendixTOCS">
 <br>   <span class="appendixToc">A <a 
-href="getstartap1.html#x12-52000A" name="QQ2-12-52">Missed approach: If anything refuses to work</a></span>
+href="getstartap1.html#x12-66000A" name="QQ2-12-66">Missed approach: If anything refuses to work</a></span>
 <br>   &nbsp;<span class="sectionToc">A.1 <a 
-href="getstartap1.html#x12-53000A.1" name="QQ2-12-53">FlightGear Problem Reports</a></span>
+href="getstartap1.html#x12-67000A.1" name="QQ2-12-67">FlightGear Problem Reports</a></span>
 <br>   &nbsp;<span class="sectionToc">A.2 <a 
-href="getstartap1.html#x12-54000A.2" name="QQ2-12-54">General problems</a></span>
+href="getstartap1.html#x12-68000A.2" name="QQ2-12-68">General problems</a></span>
 <br>   &nbsp;<span class="sectionToc">A.3 <a 
-href="getstartap1.html#x12-55000A.3" name="QQ2-12-55">Potential problems under Linux</a></span>
+href="getstartap1.html#x12-69000A.3" name="QQ2-12-69">Potential problems under Linux</a></span>
 <br>   &nbsp;<span class="sectionToc">A.4 <a 
-href="getstartap1.html#x12-56000A.4" name="QQ2-12-56">Potential problems under Windows</a></span>
+href="getstartap1.html#x12-70000A.4" name="QQ2-12-70">Potential problems under Windows</a></span>
 <br>   <span class="appendixToc">B <a 
-href="getstartap2.html#x13-57000B" name="QQ2-13-57">Some words on OpenGL graphics drivers</a></span>
+href="getstartap2.html#x13-71000B" name="QQ2-13-71">Some words on OpenGL graphics drivers</a></span>
 <br>   &nbsp;<span class="sectionToc">B.1 <a 
-href="getstartap2.html#x13-58000B.1" name="QQ2-13-58">NVIDIA chip based cards under Linux</a></span>
+href="getstartap2.html#x13-72000B.1" name="QQ2-13-72">NVIDIA chip based cards under Linux</a></span>
 <br>   &nbsp;<span class="sectionToc">B.2 <a 
-href="getstartap2.html#x13-59000B.2" name="QQ2-13-59">NVIDIA chip based cards under Windows</a></span>
+href="getstartap2.html#x13-73000B.2" name="QQ2-13-73">NVIDIA chip based cards under Windows</a></span>
 <br>   &nbsp;<span class="sectionToc">B.3 <a 
-href="getstartap2.html#x13-60000B.3" name="QQ2-13-60">3DFX chip based cards under Windows</a></span>
+href="getstartap2.html#x13-74000B.3" name="QQ2-13-74">3DFX chip based cards under Windows</a></span>
 <br>   &nbsp;<span class="sectionToc">B.4 <a 
-href="getstartap2.html#x13-61000B.4" name="QQ2-13-61">An alternative approach for Windows users</a></span>
+href="getstartap2.html#x13-75000B.4" name="QQ2-13-75">An alternative approach for Windows users</a></span>
 <br>   &nbsp;<span class="sectionToc">B.5 <a 
-href="getstartap2.html#x13-62000B.5" name="QQ2-13-62">3DFX chip based cards under Linux</a></span>
+href="getstartap2.html#x13-76000B.5" name="QQ2-13-76">3DFX chip based cards under Linux</a></span>
 <br>   &nbsp;<span class="sectionToc">B.6 <a 
-href="getstartap2.html#x13-63000B.6" name="QQ2-13-63">ATI chip based cards under Linux</a></span>
+href="getstartap2.html#x13-77000B.6" name="QQ2-13-77">ATI chip based cards under Linux</a></span>
 <br>   &nbsp;<span class="sectionToc">B.7 <a 
-href="getstartap2.html#x13-64000B.7" name="QQ2-13-64">Building your own OpenGL support under Linux</a></span>
+href="getstartap2.html#x13-78000B.7" name="QQ2-13-78">Building your own OpenGL support under Linux</a></span>
 <br>   &nbsp;<span class="sectionToc">B.8 <a 
-href="getstartap2.html#x13-65000B.8" name="QQ2-13-65">OpenGL on MacIntosh</a></span>
+href="getstartap2.html#x13-79000B.8" name="QQ2-13-79">OpenGL on Macintosh</a></span>
 <br>   <span class="appendixToc">C <a 
-href="getstartap3.html#x14-66000C" name="QQ2-14-66">Landing: Some further thoughts before leaving the plane</a></span>
+href="getstartap3.html#x14-80000C" name="QQ2-14-80">Landing: Some further thoughts before leaving the plane</a></span>
 <br>   &nbsp;<span class="sectionToc">C.1 <a 
-href="getstartap3.html#x14-67000C.1" name="QQ2-14-67">A not so Short History of <span 
+href="getstartap3.html#x14-81000C.1" name="QQ2-14-81">A Sketch on the History of <span 
 class="ptmbi7t---109">FlightGear</span></a></span>
 <br>   &nbsp;<span class="sectionToc">C.2 <a 
-href="getstartap3.html#x14-68000C.2" name="QQ2-14-68">Those, who did the work</a></span>
+href="getstartap3.html#x14-86000C.2" name="QQ2-14-86">Those, who did the work</a></span>
 <br>   &nbsp;<span class="sectionToc">C.3 <a 
-href="getstartap3.html#x14-69000C.3" name="QQ2-14-69">What remains to be done</a></span>
+href="getstartap3.html#x14-87000C.3" name="QQ2-14-87">What remains to be done</a></span>
 <br>   <span class="chapterToc"> <a 
-href="getstartap3.html#Q1-14-71">Index</a></span>
+href="getstartap3.html#Q1-14-89">Index</a></span>
 <br>   <span class="likechapterToc"><a 
-href="getstartli3.html#x15-71000C.3" name="QQ2-15-72">Index</a></span>
+href="getstartli3.html#x15-89000C.3" name="QQ2-15-90">Index</a></span>
   </div>
 <a 
-  name="x11-56005r43"></a>
+  name="x11-70005r57"></a>
 <a 
-  name="x11-65005r43"></a>
+  name="x11-79005r57"></a>
--- a/Docs/getstart.pdf
+++ b/Docs/getstart.pdf