*start*
00365 00024 US
Date: 5 Jan. 1981 11:14 am PST (Monday)
From: Pier.PA
Subject: Re: DORADO TROUBLE REPORTS
In-reply-to: Sosinski's message of 31 Dec. 1980 11:38 am PST (Wednesday)
To: Sosinski, Yeary
cc: DoradoSupport
I'm impressed by the diversity of adversity you guys are managing. Heat may
kill, but experience apparently pays off. Hang in there.
Ken
*start*
00787 00024 US
Date: 5 Jan. 1981 12:45 pm PST (Monday)
From: Rovner
Subject: Proposal for the Dorado Pilot Partition
To: DoradoUsers↑, Taylor
The proposal is to have Lisp and Smalltalk share a partition. The total residual
file space is small enough to fit easily. The "hold down S or L and three-boot"
procedure to load the specified microcode will be changed to boot the common
(Smalltalk/Lisp) partition. We intend to use the current Smalltalk partition for
this purpose and convert the current Lisp partition to Pilot. PEOPLE CAN
CONTINUE TO USE EITHER LISP OR SMALLTALK ON ANY DORADO.
Please respond to this message if you know of a problem with this idea. If there
are no showstoppers, a message will follow in a day or so announcing when the
Deed will be Done.
Paul
*start*
01898 00024 US
Date: 6 Jan. 1981 12:29 pm PST (Tuesday)
From: Rovner
Subject: A Better Proposal for the Dorado Pilot Partition
To: DoradoUsers↑
cc: Taylor
Several people have pointed out that there is not enough disk space on a 14
sector double model 44 to support the merger of Lisp and Smalltalk on one
partition.
After some conversations with several of you I have the following alternate
proposal, which I think is better, even.
Partition 1 will be used for the Pilot partition on every Dorado. The following
people who have their private partitions on a partition 1 will move them via
copydisk as follows:
McDaniel: from Par 1 of Dorado #3 to Par 5 of Dorado #4 (formerly
Satterthwaite's).
Pier, McGregor, Paxton: from Par 1 of Dorado #5 to Par 5 of Dorado #11
(formerly mine).
When the above moves are complete, Ed Taft will install Pilot on every Dorado
EXCEPT #4 and #12. Partitions 1 on these two are being used by Alan Wells
and John Maxwell, respectively. Both Alan and John will be done using them
by mid-February, at which time Pilot will be installed thereon.
When Ed does the Pilot installation, he will change the 3-boot conventions as
follows:
Holding down S or L will continue to boot appropriate microcode to the
Smalltalk or Lisp partitions, respectively (i.e. NO CHANGE).
Holding down C (or no key at all) will boot Mesa microcode to partition 4,
which will continue to be a public Alto Mesa 6 partition.
Holding down P will boot Pilot microcode to the Pilot partition (which will
occupy the same space on the disk as partition 1 does now).
Once again, please respond to this message if you know of a problem with this
proposal. If there are no showstoppers, a message will follow announcing when
the Deed will be Done.
(Gene and Ken: I'll contact you in a day or so if the green light remains on to
ask you to copy your disks).
Paul
*start*
00695 00024 US
Date: 6 JAN 1981 1436-PST
From: MCDANIEL
Subject: packpannel change for Dorado
To: Dorado Core Group:
If you have objections to the following change to the Dorado, please let me
know about them:
I want to connect Dwatch to EventE ([186] to [178]). There are several
Dorados around that have this connection jumpered. It has no known effect upon
running midas or using dwatch. It has the advantage that running programs
can set dwatch and then use the Ifu's event counters to count and then read
the number of times the signal on Dwatch was true. Had we realized how useful
this idea is, we would have specified this when we designed the
IFU board.
Gene
-------
*start*
00229 00024 US
From: pier.pa
Date: 6-Jan-81 19:19:15 PST
Subject: Lexington Display Gefuckt
To: DoradoSupport
Lex's display went batshit. I think its a connector/cable problem,
since wiggling seemed to affect it.
Ken
*start*
00721 00024 US
Date: 6 Jan. 1981 8:16 pm PST (Tuesday)
From: Taft.PA
Subject: Dorado Pilot performance improvement
To: DoradoUsers↑
Reply-To: Taft
A new version of the Dorado Pilot microcode and germ are released, effecting a
very substantial improvement in the speed of booting and of world-swapping
between client and CoPilot (the latter is now under 4 seconds for a 512K Dorado).
Part of this improvement required a change in the Pilot disk format, so existing
Pilot partitions (if there are any) must be rebuilt. I don't think there are yet any
existing Dorado Pilot partitions that anyone cares about, but if you have one
then send me a message and I will tell you how to bail existing files off of it.
*start*
01020 00024 US
Date: 9 Jan. 1981 7:21 pm PST (Friday)
From: Taft.PA
Subject: Dorado Mesa microcode release
To: DoradoUsers↑, CedarImplementors↑
Reply-To: Taft
A new version of the Dorado Mesa microcode is released, incorporating the
following change in booting conventions: the default disk partition is now 4 for
both the "Mesa" microcode (boot with all keys up) and the "Cedar" microcode
(boot with "C" pressed down). This is in preparation for converting many
Dorados' partition 1 to Pilot.
Of course, after booting you may change disk partitions by means of the
Executive's or NetExec's "Partition" command.
The following wrinkle is of interest to CedarImplementors only: the "Mesa" (all
keys up) and "Cedar" ("C" pressed down) microcode are now different and
incompatible. The "Mesa" microcode incorporates the old Cedar allocator and
garbage collector primitives; the "Cedar" microcode implements the new ones
required by the version of Cedar that was released today (see Morris's earlier
message).
*start*
00517 00024 US
Date: 11 Jan. 1981 1:16 pm PST (Sunday)
From: Taft.PA
Subject: Dorado Pilot documentation and germ
To: DoradoUsers↑
Reply-To: Taft
The memo "Setting up Pilot on a Dolphin or Dorado" has been further revised. It
has been moved to [Ivy]<Pilot>Doc>SettingUpPilot.press, which is more logical
than its former location.
A new version of the Dorado Germ is released, fixing a bug that caused
occasional page faults during world-swaps. Perform step L3 in the
above-mentioned memo to install it.
*start*
00299 00024 US
Date: 12 Jan. 1981 9:20 am PST (Monday)
From: Laaser
Subject: Kitty Hawk down
To: DoradoSupport
cc: Laaser
Sorry to bother you again, but we seem to be having more problems with our
Dorado. I came in this morning found that a baseboard boot leaves the screen
black.
Bill
*start*
00436 00024 US
Date: 13 Jan. 1981 1:05 pm PST (Tuesday)
From: Willie-Sue.PA
Subject: Dorado microcode release
To: DoradoUsers↑, CedarImplementors↑
Reply-To: Willie-Sue
A new version of the Dorado Cedar microcode has been released, fixing the
problems encountered with the release on Friday, and also fixing a bug found
subsequently.
There is also new Dorado Smalltalk microcode. No changes should be noticed.
Willie-Sue
*start*
00621 00024 US
Date: 14 Jan. 1981 3:33 pm PST (Wednesday)
From: Diebert.PA
Subject: FYI
To: D1Docs
cc:
You see it here. Please do it with 30awg wirewrap to all future delivered chassis.
Tim
---------------------------
Date: 14 JAN 1981 1451-PST
From: MCDANIEL
Subject: pack pannel change for Dorados
To: diebert
cc: mcdaniel
I've received no contrary messages regarding the proposed
backpannel change. Please have the garage permanently
connect EventE ([178]) to Dwatch ([186]) on the IFU
section of the backpannel.
Thanks,
Gene
------
------------------------------------------------------------
*start*
02293 00024 US
Date: 15 Jan. 1981 5:39 pm PST (Thursday)
From: Ornstein
Subject: Temporary move of Dorados to Purple Lab
To: DoradoSupport
cc: Taylor, Geschke, Ornstein, Taft, Overton, Strollo
It looks as though we won't get the Maxc room ready for more Dorados for at
least a couple of months and the ones in APC's on the second floor are giving
considerable trouble because they are simply too hot. I am therefore negotiating
with Lee to get him to fix up the Purple Lab with enough power (30 amp
breakers and proper plugs) to be able to handle up to half a dozen Dorados on a
temporary basis. He and Verne are going to check it out on Monday and try to
accomodate us. This is orthogonal to the longer range plans for the Purple lab. It
is my understanding (from talking to Geschke) that we are welcome to put pretty
much as many Dorados there for pretty much as long as we like. We presently
have three user machines I'd like to put there ASAP and I believe a fourth won't
be far behind. I am guessing that six will more than hold us until the Maxc room
is ready.
Part of the present trouble is the un-cooled environment and the Purple Lab's
cooling will fix that. But the APC's themselves cause some of the trouble - in
attempting to deaden the noise they reduce the efficiency of the fans. So in
addition to moving the machines, I would like, if possible, to start putting them
into racks. That will make the room noisy and means that the "terminals" should
go somewhere else - nearby. (I don't want to get into big cable stringing
exercises for short term arrangements).
My questions are:
1. Everybody - is this plan generally OK? In lieu of objections I will
proceed.
2. Mike - do we have racks or parts thereof so we could soon
rack-mount some machines?
3. Chuck/Ted - will the noise be a problem for reasons I don't know?
4. Chuck/Ted - can we identify someplace(s) near the Purple Lab
where the "terminals" can be located where users can work?
It is my understanding (unless I hear differently from Taylor) that these
machines will remain under CSL control and the same sign-up procedures will
obtain as at present - the quid-pro-quo for the temporary loan of space being
simply their greater proximity (convenience) to ISL.
Comments? Answers?
Cheers,
S.
*start*
00475 00024 US
Date: 15 Jan. 1981 6:48 pm PST (Thursday)
From: Geschke.PA
Subject: Re: Temporary move of Dorados to Purple Lab
In-reply-to: Ornstein's message of 15 Jan. 1981 5:39 pm PST (Thursday)
To: Ornstein
cc: DoradoSupport, Taylor, Geschke, Taft, Overton, Strollo
3. I know of no noise problem.
4. I have two offices on the nothermost corridor of ISL already set aside as Dorado
terminal rooms. (See the map sson to appear in your "paper" mailbox.)
Chuck
*start*
00747 00024 US
Date: 16 Jan. 1981 11:27 am PST (Friday)
From: Pier.PA
Subject: Re: Temporary move of Dorados to Purple Lab
In-reply-to: Ornstein's message of 15 Jan. 1981 5:39 pm PST (Thursday)
To: Ornstein
cc: DoradoSupport, Taylor, Geschke, Taft, Overton, Strollo
Sounds OK. There is no need for rack mounting- just open up the APC at both
ends and remove the baffles to get the cooling. Also, since Paxton, McGregor,
Wyatt, Stone, and I are using a lot of Dorado time now, we will love to have the
machines nearby, and should shuffle our partitions onto proximate machines
when they arrive. Sign up sheets for the purple lab machines can be in the
central ISL area, which is convenient to CSL as well, or can remain where they
are.
*start*
01206 00024 US
Date: 16 Jan. 1981 3:21 pm PST (Friday)
From: ornstein
Subject: More on the Purple Lab Dorado Deal
To: Taylor, Geschke, Ornstein, Taft, Overton, Yeary, Sosinski, DoradoSupport
We are going to try an experiment to see how well using the Polos terminal
distribution network might be made to work for terminal access to Dorados living
in the Purple Lab. There are some problems:
1. The office connectors are, naturally, the wrong type
2. The patch panel arrangements are considerably more baroque
and less flexible than you might think
3. Presently the only power outlet capable of powering a Dorado in
the vicinity of the Purple Lab is the one being used by the SSL
Dorado debuggers
4. The SSL technicians report that because the cable in the walls
consists of eight UNSHIELDED twisted-pairs (one pair is used as a
common ground, the other seven for the seven wire interface), they
had trouble going even modest distances with their D0's.
Mike is nonetheless arranging to do some experimenting - the primary purpose of
which is to test the usability of the in-wall wiring. If THAT works, the klutzy
office connectors and patch panel arrangements could be fixed.
S.
*start*
00944 00024 US
Date: 21 Jan. 1981 10:16 am PST (Wednesday)
From: Sosinski
Subject: DORADO TROUBLE REPORT
To: DoradoSupport
Date: 12-31-80
Time:
Reporter's Name:
Machine ID: Bon Homme Richard (#20)
Location: PARC Place
Hardware: YES
Microcode:
Software:
Misunderstanding:
Number of hours to get machine going: 1.5 Hrs.
Number of hours spent later in fixing broken item(s): 1.0 Hrs.
Total number of hours spent on problem: 2.5 Hrs.
Broken component(s): Slow chip i13 on ProcL #315.
Board Type: ProcL #315
Disk:
Power supply:
Cable:
Other (specify):
Was "help" needed: NO
Comments: Diagnostics and all emulators run except for Smalltalk "80". It
fails with T PE's (8-15). Since slowing clock to 35ns would cure the problem,
traced failure to a slow chip in tasking and T addressing area of ProcL.
*start*
00810 00024 US
Date: 21 Jan. 1981 10:23 am PST (Wednesday)
From: Sosinski
Subject: DORADO TROUBLE REPORT
To: DoradoSupport
Date: 1-5-81
Time:
Reporter's Name:
Machine ID: Bunker Hill #5
Location: CSL
Hardware: YES
Microcode:
Software:
Misunderstanding:
Number of hours to get machine going: 1.0 Hrs.
Number of hours spent later in fixing broken item(s): 0.5 Hrs.
Total number of hours spent on problem: 1.5 Hrs.
Broken component(s): Bad Map chip a5 on MemX #302
Board Type: MemX #302
Disk:
Power supply:
Cable:
Other (specify):
Was "help" needed: NO
Comments: Intermittent LISP failures. MemA fails with XRPIPEERR,
dropping 40000 Bit. Replaced bad Map chip a5.
*start*
00947 00024 US
Date: 21 Jan. 1981 10:49 am PST (Wednesday)
From: Sosinski
Subject: DORADO TROUBLE REPORT
To: DoradoSupport
Date: 1-7-81
Time:
Reporter's Name:
Machine ID: Lexington (#6)
Location: CSL
Hardware: Unknown
Microcode: Possibly
Software:
Misunderstanding:
Number of hours to get machine going: 1.0 Hrs.
Number of hours spent later in fixing broken item(s):
Total number of hours spent on problem: 1.0 Hrs.
Broken component(s): None
Board Type:
Disk:
Power supply:
Cable:
Other (specify):
Was "help" needed: NO
Comments: Display seems to be captive in an uninhabited area. Neither
Baseboard booting nor powering down sequence would free the Display. Loading
the emulator thru Midas finally freed the Display. Tried running various
programs and was unable to produce more failures.
*start*
00815 00024 US
Date: 21 Jan. 1981 10:56 am PST (Wednesday)
From: Sosinski
Subject: DORADO TROUBLE REPORT
To: DoradoSupport
Date: 1-9-81
Time:
Reporter's Name:
Machine ID: Princeton (#4)
Location: CSL
Hardware: YES
Microcode:
Software:
Misunderstanding:
Number of hours to get machine going: 1.0 Hrs.
Number of hours spent later in fixing broken item(s):
Total number of hours spent on problem: 1.0 Hrs.
Broken component(s): None
Board Type: Dsketh
Disk:
Power supply:
Cable:
Other (specify): Possible connector problem
Was "help" needed: NO
Comments: Fails to boot Disk or Ethernet. All diagnostic run. Reseating
Dsketh Board apparently corrected the problem.
*start*
00762 00024 US
Date: 21 Jan. 1981 11:20 am PST (Wednesday)
From: Sosinski
Subject: DORADO TROUBLE REPORT
To: DoradoSupport
Date: 1-9-81
Time:
Reporter's Name:
Machine ID: Enterprise (#7)
Location: CSL
Hardware: YES
Microcode:
Software:
Misunderstanding:
Number of hours to get machine going: 0.5 Hrs.
Number of hours spent later in fixing broken item(s): 0.5 Hrs.
Total number of hours spent on problem: 1.0 Hrs.
Broken component(s): i16 on ContB
Board Type: ContB
Disk:
Power supply:
Cable:
Other (specify):
Was "help" needed: NO
Comments: FTP fails on occasion. Found bad jcn7 bit on ContB.
Replaced i16.
*start*
01005 00024 US
Date: 21 Jan. 1981 2:18 pm PST (Wednesday)
From: Sosinski
Subject: DORADO TROUBLE REPORT
To: DoradoSupport
Date: 1-12-81
Time:
Reporter's Name:
Machine ID: LEXINGTON (#6)
Location: CSL
Hardware: YES
Microcode:
Software:
Misunderstanding:
Number of hours to get machine going: 1.5 Hrs.
Number of hours spent later in fixing broken item(s): 2.0 Hrs.
Total number of hours spent on problem: 3.5 Hrs.
Broken component(s): Bad SIP k52 on ContA #314
Board Type: ContA #314, ProcH #311
Disk:
Power supply:
Cable:
Other (specify): Connector Problem at ProcH.
Was "help" needed: No
Comments: Machine will not boot, emulator causes IMPE's. Kernel fails
with APLUSB4 error. Microcode is not jumping by the rules. Found an open
terminator for Longjumpc on ContA.
Kernel still failing with carryyes+3 error. Reseating ProcH #311 cleared that
problem.
*start*
01011 00024 US
Date: 21 Jan. 1981 2:37 pm PST (Wednesday)
From: Sosinski
Subject: DORADO TROUBLE REPORT
To: DoradoSupport
Date: 1-12-81
Time:
Reporter's Name:
Machine ID: KITTY HAWK (#17)
Location: SDD Bldg 96
Hardware: YES
Microcode:
Software:
Misunderstanding:
Number of hours to get machine going: 1.5 Hrs.
Number of hours spent later in fixing broken item(s): 1.0 Hrs.
Total number of hours spent on problem: 2.5 Hrs.
Broken component(s): Open signal path on MemX #301
Board Type: MemX #301
Disk:
Power supply:
Cable:
Other (specify):
Was "help" needed: No
Comments: Machine will not boot, getting PE's from ST and very mixed
up data. Found open clock (STclk'0Ba) from i6.12 to i5.9 on MemX.
We (the maintenance personnel) have recommended to SDD (Ron Cude and
Ralph Kimball) that they move the Kitty Hawk to a cooler location away from
the Dover printer.
*start*
00859 00024 US
Date: 21 Jan. 1981 2:45 pm PST (Wednesday)
From: Sosinski
Subject: DORADO TROUBLE REPORT
To: DoradoSupport
Date: 1-14-81
Time:
Reporter's Name:
Machine ID: HORNET (#10)
Location: CSL
Hardware: YES
Microcode:
Software:
Misunderstanding:
Number of hours to get machine going: 1.0 Hrs.
Number of hours spent later in fixing broken item(s):
Total number of hours spent on problem: 1.0 Hrs.
Broken component(s): Connector Problem at ProcL location
Board Type:
Disk:
Power supply:
Cable:
Other (specify): Connector Problem at ProcL location
Was "help" needed: No
Comments: Machine dies in Smalltalk. Kernel fails at AMINUSBG+4 on
the 3rd iteration?? Reseating ProcL apparently corrected problem.
*start*
00824 00024 US
Date: 21 Jan. 1981 2:49 pm PST (Wednesday)
From: Sosinski
Subject: DORADO TROUBLE REPORT
To: DoradoSupport
Date: 1-14-81
Time:
Reporter's Name:
Machine ID: PRINCETON (#4)
Location: CSL
Hardware: YES
Microcode:
Software:
Misunderstanding:
Number of hours to get machine going: 0.5 Hrs.
Number of hours spent later in fixing broken item(s): 1.5 Hrs.
Total number of hours spent on problem: 2.0 Hrs.
Broken component(s): Bad capacitor in Display.
Board Type:
Disk:
Power supply:
Cable:
Other (specify): Bad capacitor in Display.
Was "help" needed: No
Comments: Display has no Raster. Found problem to be sweep failure
due to bad capacitor c135 in the Display.
*start*
00289 00024 US
Date: 22 Jan. 1981 11:11 am PST (Thursday)
From: Sosinski.PA
Subject: Wide-Body Dorado
To: Doradousers↑
cc: Overton
The Yorktown has become the first Dorado to utilize 64K rams in its storage
module boosting its available storage to 1 Megaword.
The dorado crew
*start*
01207 00024 US
Date: 22 Jan. 1981 12:48 pm PST (Thursday)
From: Ornstein.PA
Subject: Dorado Lore
To: DoradoUsers↑
In watching various messages fly around about Dorados I notice that people seem
sometimes to fall into holes recently vacated by others. For this reason I
suggested that we consider building some depository of Dorado lore that a novice
could dip into before starting to discover matters for himself. Gene rightly
responded as follows:
"I don't think it is worth any effort. Most of the Dorado lore of value to
people is associated with software rather than hardware. If we really want
to stay out of the maintenance business, let them (Dorado users)
generate their own sources of folk lore. Many of them know strange
facts about the hardware, and once they develop some mechanism
for distributing the information, hardware lore will begin to appear there."
This makes eminent sense to me and I'm therefore passing this suggestion along.
It's up to someone out there who thinks it would be a good idea and is good
citizen enough to set up some DoradoLore system that people could dump hints,
warnings, etc. into and that DoradoUsers, especially new ones, could access.
S.
*start*
00697 00024 US
Date: 22 Jan. 1981 1:55 pm PST (Thursday)
From: Diebert.PA
Subject: Re: Dorado Lore
In-reply-to: Ornstein's message of 22 Jan. 1981 12:48 pm PST (Thursday)
To: Ornstein
cc: DoradoUsers↑
Severo:
I would propose the implementation of a Laurel mailbox named DoradoLore to
which users could submit thier little tidbits of Dorado lore that they feel would
be of interest to other users. About once a day/week/month I would read and
edit the mail into a Laurel mail file and place it in a well known IVY/Juniper
directory. Users could then retrieve the mail file and brouse it using Laurel in a
similar way the Help.Mail file works for persons not familiar with Laurel.
Tim
*start*
00431 00024 US
Date: 23 Jan. 1981 9:17 am PST (Friday)
From: Rovner.PA
Subject: Installing Pilot on CSL Dorados
To: DoradoUsers↑
Reply-To: Rovner
All Dorados EXCEPT #12 (Nursery, MIDWAY) now have partition 1 cleared for
Pilot. This Dorado will not have a public pilot partition.
Users can feel free to install Pilot on partition 1 of any other CSL Dorado. See
[Ivy]<Pilot>Doc>SettingUpPilot.press for the recipe.
Paul
*start*
00618 00024 US
Date: 23 Jan. 1981 12:54 pm PST (Friday)
From: Ornstein.PA
Subject: Dorado Lore
To: DoradoUsers↑
I think Tim's idea of a special mailbox which could receive some of the msgs
directed to DoradoUsers↑ and which would be periodically "archived" to a more
permanent file is fine. However I think most of the content will concern software
and it should therefore be up to someone who is a major software user/developer
to pick up the chore rather than Tim. If no-one in this category is interested
enough to set it up and do the work, then I give up, there isn't a sufficient
clientelle.
Severo
*start*
00231 00024 US
Date: 26 Jan. 1981 4:45 pm PST (Monday)
From: Sosinski.PA
Subject: New Dorado
To: Doradousers↑
The Forrestal has arrived. It replaces the Saratoga which has been temporarily
reassigned.
The dorado crew
*start*
00413 00024 US
Date: 27 Jan. 1981 10:37 am PST (Tuesday)
From: Taft.PA
Subject: New Othello: multi-partition file systems
To: DoradoUsers↑
Reply-To: Taft
A new version of Othello is released, capable of building Pilot file systems that
span multiple Dorado disk partitions.
For details, read the revised version of "Setting up Pilot on a Dolphin or Dorado",
file [Ivy]<Pilot>Doc>SettingUpPilot.press.
*start*
00337 00024 US
Date: 27 Jan. 1981 7:32 pm PST (Tuesday)
From: McKeeman.PA
Subject: Sickie
To: DoradoSupport
Reply-To: McKeeman
Princeton consistently died after:
triple boot C
@GETCEDAR
which called Bringover
Then it wouldn't even single boot.
I tried Scavenger and a fresh copy of [Ivy]CedarLib>dffiles>Bringover.bcd
....
*start*
01562 00024 US
Date: 30 Jan. 1981 6:32 pm PST (Friday)
From: Rovner.PA
Subject: Bigger Pilot on Dorados
To: DoradoUsers↑
Reply-To: Rovner
Except for one Dorado (the one in the nursery, #12, Midway), partition 1 on
any CSL Dorado is fair game for installation of a public Pilot world.
Here's the plan for accommodating Pilot systems that require more than 1 Dorado
partition.
When one of you feels the need for another public Dorado Pilot with more than
one partition, come see me. I will select one of the CSL Dorados that still has both
Lisp and Smalltalk partitions and snarf partition 2 (presently the Smalltalk one)
for Pilot. That Dorado will then have both partition 1 and partition 2 assigned to
Pilot, and Lisp and Smalltalk users will share partition 3 (it is better for Pilot to
have a contiguous disk region, hence partition 2 is the Chosen One). We will
re-evaluate this plan when more than (say) 4 CSL Dorados lose their partitions 2.
"But how will I get Smalltalk microcode loaded on fat Pilot Dorados?"
Ed Taft will soon release a new Dorado system that leaves you on partition 3 and
loads Lisp (or Smalltalk) microcode if you hold down the L (or S) key when
3-booting. You can move to a different partition WITHOUT CHANGING THE
MICROCODE, of course, by using the "partition" command to the Alto exec. This
will be mildly inconvenient for Smalltalk usage on Dorados which have both
Lisp and Smalltalk partitions, but it is the best we can do without a lot of work.
Ed will send around a message when he has made his release.
Paul
*start*
00181 00024 US
Date: 2 Feb. 1981 11:30 am PST (Monday)
From: anderson.PA
Subject: Saratoga
To: csl↑, isl↑, Doradocore↑
Saratoga is up and running in room 2031 bldg. 35.
*start*
00335 00024 US
Date: 2 FEB 1981 1431-PST
From: KAEHLER
Subject: Dorado #10, Hornet
To: DoradoSupport
I can't get the disk to spin up, even after going downstairs and pressing the
little white button. (Miracle cure advertised for pressing the little white button ...). Just thought you'd like to know, Ted.
------
*start*
00625 00024 US
Date: 3 Feb. 1981 10:27 am PST (Tuesday)
From: Willie-Sue.PA
Subject: Fat Pilot Dorados
To: DoradoUsers↑
Reply-To: Willie-Sue
Later today (Tuesday), I will be releasing new Smalltalk microcode that
leaves users of the S boot on partition 3 (the traditional Lisp partition). To get to
the Smalltalk disk, type Partition 2 to the alto exec. In the immediate future,
only Dorado #5, BunkerHill (across from Mark Brown's office) will have a fat
Pilot partition, and hence have Lisp and Smalltalk sharing partition 3. It is up to
the Lisp and Smalltalk users to establish peaceful co-existence rules.
*start*
00600 00024 US
Date: 3 Feb. 1981 4:21 pm PST (Tuesday)
From: Taft.PA
Subject: 64K Rams in the map?
To: DoradoCore↑
cc: CedarImplementors↑, Taft
The Rubicon release of Pilot, due sometime in March, is expected to be able to
deal with a 2↑24 word virtual address space; current Pilot is limited to 2↑22. As
it happens, the Dorado virtual address space is presently 2↑22 anyway, because
16K Ram chips are installed in the Map.
Now that 64K Rams seem to be readily available, how about installing some in
the maps of all existing Dorados? I believe each machine requires only about 20.
Ed
*start*
00549 00024 US
Date: 3 Feb. 1981 4:34 pm PST (Tuesday)
From: Pier.PA
Subject: Re: 64K Rams in the map?
In-reply-to: Taft's message of 3 Feb. 1981 4:21 pm PST (Tuesday)
To: Taft
cc: DoradoCore↑
Each machine requires 21 RAMs. We probably need the 200 nsec versions,
although we might squeak by with 250 nsec (the kind we have). The 200 nsec
versions are about 15-20% more expensive than the 250s, and should cost today,
from Fujitsu, about $23. Joe Patti knows how to get them. Is a change to the
diagnostics required to test larger RAMs??
*start*
00298 00024 US
Date: 3 Feb. 1981 5:33 pm PST (Tuesday)
From: Sosinski
Subject: Re: 64K Rams in the map?
In-reply-to: Taft's message of 3 Feb. 1981 4:21 pm PST (Tuesday)
To: Taft
cc: DoradoCore↑
There are 2 Dorados with old Rev Cc MemX boards, that cannot handle the 64K
Rams in the map.
*start*
00410 00024 US
Date: 4 Feb. 1981 12:05 pm EST (Wednesday)
From: Lampson.PA
Subject: Re: 64K Rams in the map?
In-reply-to: Sosinski's message of 3 Feb. 1981 5:33 pm PST (Tuesday)
To: Sosinski
cc: Taft, DoradoCore↑
Are these SW boards or MW. If the former, how about updating them. If the
latter, we had better get two new ones -- in the long run all machines will have
to have 64k RAMs in the map.
*start*
00293 00024 US
Date: 7 Feb. 1981 12:08 pm PST (Saturday)
From: Rovner.PA
Subject: CSL and ISL Dorados
To: DoradoUsers↑
Reply-To: Rovner
The latest summary of locations, names, numbers, sizes, and partition
assignments is to be found on [ivy]<Rovner>Dorados.press and .bravo.
Paul
*start*
00271 00024 US
Date: 7 Feb. 1981 11:35 am PST (Saturday)
From: Taft.PA
Subject: Forrestal monitor
To: DoradoSupport
The picture on Forrestal's monitor (outside Andrew Birrell's office) is a bit too
high -- the top of the picture is hidden under the bezel.
Ed
*start*
00578 00024 US
Date: 8 FEB 1981 1655-PST
From: MCDANIEL
Subject: MIDWAY broken: don't send to SDD!
To: doradosupport
cc: overton
Midway has just broken on me. Complained about
current power problem. I managed to reboot and to
try to save my state. Then the mesa emulator broke.
Loading the microcode symbols into midas showed that
it was in some portion of the emulator that I don't
recognize at a breakpoint. Something like UnNorm1Gr40 or
suchlike. I powered-down the machine.
I would like to retrieve my files,too! I was not able to
do it.
Gene
------
*start*
00618 00024 US
Date: 9 Feb. 1981 2:31 pm PST (Monday)
From: Deutsch.PA
Subject: New release of Micro
To: Micro↑
A new release of Micro is now on [Maxc2]<Alto>. It has much more assembly
space than all previous versions, resulting from internal improvements in the
format of macro storage. It is source- and output-compatible with previous
versions; however, it is not compatible with existing .ST files. Therefore, if you
have .ST files you will have to regenerate them from their sources. Until this
happens you can continue to use the previous version of Micro, which is on
[Maxc2]<Alto>OLDMICRO.RUN.