Installing Cedar during the PreRelease phase requires a certain amount of care and typing. This is because the installation programs use defaults that refer to the current release rather than the prerelease (some day we may improve on this). This installation procedure is only for personal machines; public machines will be converted at the official release time.
Preparation
First, save the files you want to survive the boot. This is not
really necessary if you are not going to erase your Cedar volume, but it is a good idea (keep your bags packed, folks, since your disk may go West any time). To find these files, use the command
List -u ///*!h
(usually you do not need to save *.tipC and *.log files)
Next, make a new user profile for yourself, and store it so that it will be found by the new Cedar release. For example, if the prerelease is for Cedar 6.0, and your registered name is Tirebiter.pa, your profile should be stored as [Ivy]<Tirebiter>6.0>Tirebiter.profile. Any references to old releases (like Cedar5.2) should be converted to the new release. It is a good idea to use the prerelease version of [Indigo]<Cedar6.0>Top>User.profile as a starting point since there are changes in the user profile conventions.
To get to Cedar 6.0 Iago from Cedar 5.2
We will assume that you have a Cedar 5.2 world that you are willing to completely convert to Cedar 6.0. We also assume that you do not want to change the number of Alto partitions. Certain changes in the file system preclude moving from Cedar 6.0 to Cedar 5.2 once multi-page header files have been created (unless you erase your volume(s)).
First, get to Cedar 5.2 Iago by booting with the L switch (a normal boot will do, provided that you hold down the L key between maintenance panel codes 812 and 845). Once there, install the boot file for Cedar 6.0 using the "
Install Boot File" command. Note that the default file name in Cedar 5.2 Iago will be wrong, since it refers to Cedar 5.2. Instead, you want your boot file to come from
[Indigo]<Cedar6.0>Top>BasicCedarDorado.boot
In response to "Do you want to use this file when you boot the physical volume?" you should type Y. Typing the DEL key will cancel any command. Then boot the Cedar volume using the "Boot Logical Volume" command in Iago (with the L switch).
In Cedar 6.0 Iago
{Optional} If you are in doubt about whether you have a Debugger volume, use the "Describe Logical Volumes" command. If you have a Debugger volume and want to get rid of it, use the "Create Physical Volume" command. If you are doubt about the number of Alto partitions, you can infer them from the difference between the ending point of the highest logical volume and the end of the physical volume (via the "Describe Physical Volumes" command and the knowledge that an Alto partiion is roughly 22000 pages). If you still in doubt, then skip this step or consult an expert.
{Optional} Using the "Create Logical Volume" command, make a new Cedar volume. In most cases, you no longer need a Debugger volume (Dorados with large disks can afford the space, but most other machines can't). This step is not necessary if your logical volume structure already suits you. However, if you have more than 1 Mword of physical memory and only 80 Mbytes (or less) of disk, then you do not want to have a Debugger volume, since it will occupy excessive space. Warning: this step will destroy all files on the local disk!
{Optional} Using the "Erase Logical Volume" command, erase your Cedar volume and, if present, your Debugger volume. This step is optional for installing Cedar 6.0, but it is highly recommended. It is necessary if you used the "Create Logical Volume" command. Warning: this step will destroy all files on the local disk!
{Optional} If you are not running at PARC, you may wish to indicate where your local servers are. These names are used as logical names so that Cedar can be (more or less) location independent. Use the "
Set Pseudo Server" command to setup the following pseudo-servers:
Cedar
writeServer readServer optionalReadServer
The pseudo-server for Cedar6.0 and CedarChest6.0 files
User
writeServer readServer optionalReadServer
The pseudo-server for personal files (especially profiles)
Fonts
writeServer readServer optionalReadServer
The pseudo-server for fonts files
If you want to make some of these pseudo-servers read-only, use "$" for the writeServer name. For now, assume that the files are not replicated.
Using the "Install Initial Microcode" command, install initial microcode. You should use the same file name as presented.
Using the "Install Cedar Microcode" command, install Cedar microcode on the Cedar volume. You should use the same file name as presented.
Using the "Install Germ" command, install the Cedar germ on the Cedar volume. You should use the same file name as presented.
Using the "Install Boot File" command, install the Cedar 6.0 boot file on the Cedar volume. You should use the same file name as presented.
{Only if your volumes have been erased} Using the "
Create VM Backing File" command, create a VM backing file your Cedar volume and, if present, your Debugger volume. The following numbers are recommended:
16000 pages for machines with < 1 Mword of physical memory
20000 pages for machines with 1 Mword of physical memory
24000 pages for machines with 2 Mword of physical memory
24000 pages for machines with 4 Mword and small disks
32000 pages for machines with 4 Mword and large disks
Now you have to full boot. For Cedar 6.0 there have been no microcode changes, so you can use the "Boot Logical Volume" command in Iago (with the F switch).
After the Cedar volume finishes booting you can make a checkpoint, then boot your Debugger volume (if any).