Help needed with aircraft install

**c_brookhart** · 08-03-2005, 11:39 PM

I have downloaded a 737-700 aircraft that has two models. I also downloaded a fictional Southwest livery that uses the 737-700 model. The instructions said to extract the contents of the zip file into the FS9 directory, which I did. I used winzip and selected the option to use folder names. I've never quite been able to get that feature to work for me because it will sometimes not files where they need to go. In this instance though, I believe that all files went where they needed to go. Here is how it looks in the FS9 director. There is a folder called Kittyhawk 737-700. Inside that folder is the Kittyhawk Productions 737-700 folder. Inside that folder are folders for sound, panel, model, and texture. The fictional livery is also in there in a folder called Eagle One. Also included in the Kittyhawk 737-700 folder is the air and cfg files. I have looked at the aircraft.cfg file and it shows UI manufacturer=Boeing and model=737-700. There is a Boeing entry in the aircraft list, but only a 737, 747, and 777 all of which are the default aircraft (orbit, landmark, etc.). I can't figure out why the 737-700 aircraft won't show up. Are the necessary files stored too deep in the folder tree for FS9 to see them?

**drobson** · 08-03-2005, 11:43 PM

Without having that aircraft, I can't be sure. But, I think you need to move the second folder, (the Kittyhawk Productions 737-700) into your Aircraft folder.

Darrell

**c_brookhart** · 08-04-2005, 12:03 AM

Another problem I am now encountering is a Microsoft Management Console crash. For some reason, accessing folders inside the Kittyhawk Productions 737-700 folder seems to generate this error report followed by memory access errors in explorer.exe.

The path for the folder looks like this:
\FS9\Aircraft\Kittyhawk 737-700\Kittyhawk Productions 737-700\aircraft.air or aircraft.cfg .

**c_brookhart** · 08-04-2005, 12:47 AM

Moving the second folder into the fs9\aircraft folder fixed the problem.

Now to figure out what is causing the second problem--Microsoft Management Console Crash and memory access errors when viewing files associated with this aircraft.