Flight V2.2 Installation Notes 1. FLIGHT V2.2 is a DECwindows application. It requires SDC VMS V5.1 or greater. If you have a version of VMS prior to SDC V5.1, you will get the following message when attempting to invoke the simulator: %DCL,error activating image DECW$XLIBSHR -CLI, image file $100$DUA0:[SYS1.SYSCOMMON.][SYSLIB]DECW$XLIBSHR.EXE -SYSTEM, ident mismatch with shareable image 2. Flight creates a network object entry in your system's NCP database. If you have modified your system configuration away from the standard DECnet account configuration, you must perform the same system management actions on the Flight network object as you would with any other network object (such as MAIL or PHONE). 3. You should add the following line to your system startup command procedure in SYS$MANAGER: $ @SYS$MANAGER:FLT$STARTUP If you do not, the next time your system reboots, the FLIGHT server installed on your system will not activate correctly when a simulator attempts to connect to it. 4. A sample installation dialog using VMSINSTAL follows. A quick review of it may make your installation go smoother. In this installation, all defaults are accepted, causing installation of the full kit with the exception of the example sources. $ @vmsinstal flight022 VAX/VMS Software Product Installation Procedure V5.1 It is 14-JAN-1989 at 19:44. Enter a question mark (?) at any time for help. %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account. %VMSINSTAL-W-DECNET, Your DECnet network is up and running. * Do you want to continue anyway [NO]? y * Are you satisfied with the backup of your system disk [YES]? y The following products will be processed: FLIGHT V2.2 Beginning installation of FLIGHT V2.2 at 19:45 %VMSINSTAL-I-RESTORE, Restoring product saveset A ... %VMSINSTAL-I-RELMOVED , The product's release notes have been successfully moved to SYS$HELP. * Do you want to purge files replaced by this installation [YES]? You have three options available to you for installation of the two major components of FLIGHT - the interactive simulator and the distributed server. The options are; 1. Install both the simulator and the distributed server. This allows you to run the simulator on the local node. It also allows you to 'host' other nodes wishing to simulate together in one world. 2. Install only the simulator. This allows you to run the simulator, but only if you have access to a node on which the server has been installed. Use the logical name FLT$SERVER to indicate the server node you want to access. 3. Install only the distributed server. This allows you to 'host' other nodes wishing to simulate together in one world. It does not allow you to run the simulator on this node. * Which option do you want [1]: Pre-compiled hangars are provided with the simulator. There are nine hangars with a total of approximately 30 aircraft in them. The hangars require a total of 7500 blocks of disk space. * Do you want all the hangars [YES]? You have selected the following hangars: Civilian aircraft World War I aircraft World War II aircraft Modern military aircraft VTOL aircraft Fictional aircraft Stationary objects Ground vehicles * Is this OK [YES]? %FLIGHT-I-DEFAULTHANGAR, the default hangar file on your system will be SYS$LIBRARY:FLT$CIVILIAN.HANGAR To change the default hangar file on your system, edit the file SYS$MANAGER:FLT$STARTUP.COM. Pre-compiled worlds are provided with the simulator. The two worlds provided require a total of 500 blocks of disk space. * Do you want all the worlds [YES]? You have selected the following worlds: Pacific Islands Eastern Massachusetts * Is this OK [YES]? %FLIGHT-I-DEFAULTWORLD, the default world file on your system will be SYS$LIBRARY:PACIFIC.WORLD To change the default world file on your system, edit the file SYS$MANAGER:FLT$STARTUP.COM. This kit comes with the source description of the A/V8-B Harrier II, the Pacific and Massachusetts worlds and all instrument definitions for all aircraft in the provided hangars. The FLIGHT hangar editor may be used to obtain the sources to the weapons and aircaft of the hangars placed on your system. The example files require approximately 1000 blocks of disk space. * Do you want to place the example files on your system [NO]? %FLIGHT-I-NOEXAMPLE, The FLIGHT example files will not be placed on your system All questions required for installation of FLIGHT have been answered. Installation will take up to 10 more minutes based on the installation options you have selected. %VMSINSTAL-I-RESTORE, Restoring product saveset B ... %FLIGHT-I-SIMULATOR, simulator files being placed on your system %VMSINSTAL-I-RESTORE, Restoring product saveset C ... %FLIGHT-I-SERVER, server files being placed on your system %FLIGHT-I-OBJECT, defining network object for your system Your VMS system will now be updated to include the following new and modified files: SYS$MANAGER:FLT$STARTUP.COM [new] SYS$SYSTEM:FLT$SERVER.EXE [new] SYS$SYSTEM:FLT$SERVER.COM [new] SYS$LIBRARY:PACIFIC.WORLD [new] SYS$LIBRARY:MASSACHUSETTS.WORLD [new] SYS$SYSTEM:FLT$SIMULATOR.EXE [new] SYS$SYSTEM:FLT$HANGAR_COMPILER.EXE [new] SYS$SYSTEM:FLT$HANGAR_EDITOR.EXE [new] SYS$SYSTEM:FLT$WORLD_COMPILER.EXE [new] SYS$SYSTEM:FLT$WORLD_PREVIEWER.EXE [new] SYS$LIBRARY:FLT$KEYMAP.DAT [new] SYS$LIBRARY:FLT$UID.UID [new] SYS$LIBRARY:FLT$CIVILIAN.HANGAR [new] SYS$LIBRARY:FLT$WW1.HANGAR [new] SYS$LIBRARY:FLT$WW2.HANGAR [new] SYS$LIBRARY:FLT$MODERN_JET1.HANGAR [new] SYS$LIBRARY:FLT$MODERN_JET2.HANGAR [new] SYS$LIBRARY:FLT$VTOL.HANGAR [new] SYS$LIBRARY:FLT$FICTION.HANGAR [new] SYS$LIBRARY:FLT$STATIONARY.HANGAR [new] SYS$LIBRARY:FLT$VEHICLES.HANGAR [new] SYS$LIBRARY:DCLTABLES.EXE [modified] SYS$HELP:HELPLIB.HLB [modified] This is not a Digital product DIGITAL INTERNAL USE ONLY %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of FLIGHT V2.2 completed at 19:48 VMSINSTAL procedure done at 19:48 $