Date: 23 July 1982 6:39 pm PDT (Friday)
Sender: Levin.PA
Subject: Cedar 3.2 release (part 1 of 2)
From: Release Master
To: CedarUsers^, CedarImplementors^
cc: CedarCoordinators^
Reply-To: Levin

Cedar 3.2 is released.

This release contains a large number of significant changes visible at both the
user and programming interfaces.  All clients must be recompiled, even if the
interfaces they depend upon have not changed.

There will soon be substantial introductory documentation for this release. 
Subsequent messages will announce its availability.  As in the past, many release
components include documentation, which is identified in the descriptions of the
individual components below.

This release is stored exclusively on subdirectories of [Indigo]<Cedar>.  Other
directories (e.g., CedarLang, CedarLib) are NOT part of the release and their
contents should be treated with suspicion.  In general, users should access release
components using BringOver and the appropriate DF files; retrieving files with
the FileTool is likely to lead to version mismatches and confusion.  For this
release, all top-level DF files for release components that users are likely to need
are stored on [Indigo]<Cedar>Top>. 

This release announcement consists of four parts:

  Installation Procedure
  Known Problems
  List of System Components
  Summary of Release Component Changes since Cedar 3.1

This message contains the first two sections; a subsequent message holds the
second two (which are quite long). 


Installation Procedure
---------------------

This procedure assumes you have a machine with Cedar 3.1 installed.  (Note to
alpha-testers of Cedar 3.2:  this procedure works for you also.  Don't attempt any
shortcuts.).  Otherwise, refer to the "Setting Up Your Disk" section of

     [Indigo]<CedarDocs>Release>Introduction.press

for further information.  (Within a week or so this document will be available on
[Indigo]<Cedar>Documentation>.)

  0)  The Client volume must be erased before Cedar 3.2 is installed.  Failure
      to do so can result in peculiar failures at unpredictable times, for which the
      only cure is erasing the disk.  If there are any files on the Client volume
      that you wish to save, save them before proceeding.  You may wish to use
      DFDisk (see documentation of DFFiles component).

  1)  Get to Othello through the MesaNetExec.  DO NOT use the Othello on your
      Othello volume.

  2)  Type Erase<CR> to Othello.  You will be prompted for the volume
      name, type Client<CR>.  Confirm as necessary.

  3)  Type @<CR> to Othello.  You will be prompted for a command file
      name.  Type either
	[Indigo]<Cedar>Init>DoradoRelease.cm          or
	[Indigo]<Cedar>Init>D0Release.cm
      as appropriate.  New boot files will be fetched for all volumes, as well as
      new microcode and germ files.

  4)  On Dorados, Cedar will automatically be booted upon completion of the
      command file.  (Actually, the CoPilot volume will first be booted, after
      then a physical volume boot will occur, causing Cedar to be booted.  Be
      patient.)  On Dolphins, the Alto partition will be booted; hold down
      the "P" key and press the boot button to boot Cedar.

  5)  The installation dialogue has changed somewhat since Cedar 3.1, but the
      questions should be self-explanatory (if you need more information, consult
      the introductory document cited above).  WARNING:  Don't use a personal
      DF file to bring over a personalized user profile, since a profile acceptable
      to Cedar 3.1 will almost certainly be unacceptable for Cedar 3.2.  Consult the
      documentation (see description of the IO component) for changes in the
      content of the user profile.  After installing Cedar 3.2 with the default
      user profile, you can edit your personal profile suitably and the changes
      will be noticed automatically.

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

	BringOver /a CedarClientFat.df    (Note:  NOT /p)

to the UserExec.  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 probably shouldn't do this.

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

Known Problems
----------------

The following problems/glitches are known to exist in Cedar 3.2.

1. Double-clicking Blue in a typescript viewer which has the selection causes a
crash.

2. Several serious problems with the Watch tool have been observed.  Since it
wasn't possible to correct these problems before the release, it is recommended
that the Watch tool not be used.  A repaired version may be released soon.

3. There may be a long delay (several minutes) during initial booting after the
screen has turned gray but before any viewers have appeared.  Don't panic; files
are being retrieved from (busy) file servers.

4. Many of the source files in this release contain Tioga formatting.  Beware of
printing such files with Print; it will typically produce pages and pages of
garbage at the end.  Use TSetter to print such files.


The Release Master