alexis@panix.uucp (Alexis Rosen) (03/28/91)
Well, I promised a major tirade about the 2.0.1 installer, the last time
I posted. Matthias seems to have done a pretty good job of covering the
salient points (though he didn't mention the crazy format of the floppies,
or... no, I won't do it...).
One thing- it took four days to install 2.0.1 properly. In that time, I
installed 2.0 and 2.0.1 a total of 13 times. While I don't know for sure
what caused all our grief, I can only think of one thing that was different
between all the times that the install failed, and when it finally succeeded.
We had two disks. The boot disk had A/UX 2.0.1 Startup and bin folders, and
the other one had 2.0 startup and bin. We used the 2.0 startup on the non-
boot disk to first launch A/UX when we were trying to upgrade. The time I
finally succeeded in installing A/UX, I first deleted the 2.0.1 bin folder
on the boot drive.
This leads me to speculate wildly- perhaps sash is looking for the bin folder
on the boot drive before it looks on the current drive. If so, it would have
found the 2.0.1 bin folder on my system, and used it. If sash 2.0.0 is highly
incompatible with the 2.0.1 bin folder, that might explain what happened.
I know this is all rather improbable, but... after four days, I threw out
one folder, and suddenly everything went like a charm. If that's _not_ it,
Murphy can certainly pat himself on the back for this one...
---
Alexis Rosen
Owner/Sysadmin, PANIX Public Access Unix, NY
{cmcl2,apple}!panix!alexis