Given the existence of improved packages on <PostCedar>, users should be warned that installation of Cedar 4.4 may acquire elderly versions of components from Cedar. The file Init.log records what was acquired during installation. Walnut, in particular, has a much better version on <PostCedar> than <Cedar>. If the release installation acquires some elderly files from Cedar, you should simply get the more recent files from PostCedar after installation. If it were easy to avoid this problem, we would. The following commands can be used to restore PostCedar files that the Cedar release will overwrite:

A machine already running Cedar 4.2 should upgrade to Cedar 4.4 with little problem. Although we recommend erasing your Client and Debugger volumes before installing, there is no unusual risk associated with using your current volumes if you follow the instructions below.

A machine running the prerelease of Cedar 4.4 needs the additional step of having the file named Cedar.version deleted from the disk before installing Cedar 4.2. Avoiding this step will cause trouble for you when PreCedar is erased.

For any user, to erase all files on your Client and Debugger volumes, boot the Othello volume, and type

confirming as necessary. Then you can execute the appropriate installation command file for your machine (see below).

To install Cedar on a Dorado (whether or not you choose to erase volumes), boot the Othello volume, and type

To install Cedar on a Dolphin (whether or not you choose to erase volumes), boot the Othello volume, and type

To install Cedar on a Dandelion, consult an expert. To install Cedar on a public machine (an unusual case for most people), use PublicDoradoRelease.cm or PublicD0Release.cm.

As with previous releases, once the automatic installation procedure completes, you may then optionally acquire many potentially useful files by typing

to the UserExec or CommandTool. This will fetch the exported contents of most of the major packages, whether released as part of the boot file or as separate BCDs. Users with limited disk space should not do this. Even users with lots of disk space may find the clutter irksome.

Again - Given the existence of improved packages on <PostCedar>, users should be careful that installation of Cedar 4.4 does not acquire elderly versions of components from Cedar. The file Init.log records what was acquired during installation. Walnut, in particular, has a much better version on <PostCedar> than <Cedar>. Use the commands in Known Problems to restore more recent packages from PostCedar.

Once you have brought over all the desired files, you may wish to make a checkpoint, using the guarded button Checkpoint at the top of the screen.

Before beginning to use this release, you should read the remaining sections of this message.

This section documents important changes in the user interface or major components and briefly describes significant new components. The descriptions here are incomplete and intended only to provide sufficient information to avoid surprises and confusion. Users should consult the more complete descriptions in the "Changed Release Components" section of this release announcement.

The following is a complete list of the system components included in this release. Details about the relationship of each component to the previous release and pointers to documentation and DF files appear in the "Summary of Release Components" section, below.

The field after the package name indicates what has changed. It can take the following values:

Note: In the descriptions that follow the DF file or files for a component are located on [Indigo]<Cedar>Top> unless otherwise specified. If the documentation file name is not a path, it is assumed to be accessible using the DF file name and BringOver, i.e.,

In general, documentation is stored on

but there are occasional exceptions. For brevity, we do not list Component.Press if Component.Tioga exists, and we do not include [Indigo]<Cedar>Documentation> in the file name if that is the prefix. If not specified, the host is assumed to be [Indigo].

Components are listed below only if there has been a change for this release. Unless otherwise indicated, questions about changes in individual components should be addressed to their implementors.