| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 509.1 | R U using the original FT kit? | VAXUUM::KOHLBRENNER | | Mon Jun 15 1987 09:50 | 18 |
| I think you are trying to install DOCUMENT and also install LN03
support (one of the optional features) at the same time. If you
are installing the original Field Test Kit, (which we call Base
Level 7) then the release notes warn you not to do this. You
have to install DOCUMENT by itself (with just the LINE PRINTER
support, if you want that). Then you repeat the installation
procedure, and at the point where it asks you whether you want
a full or partial installation, you say NO (that is, you do NOT
want a full installation). Then you select LN03 support.
If you are installing the Field Test update kit, which we call
Base Level 9, you should not encounter this problem - you can
do it all in one installation (except that you have to install
the font files part of LN03 support from a separate kit).
---------------
bill
|
| 509.2 | It's the latest kit... | DRCS::GODWIN | | Mon Jun 15 1987 10:35 | 10 |
| Yes I know you can only install support for one device at a time
with the BL7 kit - but here I'm trying to install the T1.0 Field
Test Update kit referred to in note 1.8!
I've tried various installation permutations (including installing
just LSE and LINE support) but the process always fails at the same
point.
Peter
|
| 509.3 | | MARTY::FRIEDMAN | | Mon Jun 15 1987 15:15 | 4 |
| Just for clarity-- Bill, if the original was BL7 and the update
is BL9, then what was BL8?
Marty
|
| 509.4 | update = bl8 | CLOSET::ANKLAM | | Mon Jun 15 1987 15:31 | 5 |
|
the update was BL8. Bill's working on getting the BL9 kit together
these days, so he's probably got bl9 on his brain.
|
| 509.5 | Try recopying the kit | PROSE::SYSTEM | | Mon Jun 15 1987 16:12 | 4 |
| We encountered the exact same problem when trying to install
base level 8. It turned out that the version of saveset B
we had copied was corrupted - we had to recopy the kit and
reinstall. Everything went Ok the 2nd time.
|
| 509.6 | BL9 is not released to anyone yet. | VAXUUM::KOHLBRENNER | | Mon Jun 15 1987 16:26 | 7 |
| The original field test was BL7.
The field test update was BL8. (mid-May)
BL9 is the name that we use to describe the kits
that we are now building and testing for the SDC
kit. ---
|
| 509.7 | Mission: Impoosible self-destructing savesets? | FNYFS::WYNFORD | The Rented Loony | Wed Jun 17 1987 05:32 | 22 |
| Don't want to worry you folks but we've had the same thing twice
so far on different machines! We upgrading from BL7 to BL8 in both
cases.
The first time we had copied the savesets over and had to recopy
saveset B after which it went OK.
Last night, using the savesets on the first machine, we tried and
it bombed at the same place!
We are recopying from VAXUUM/CLOSET but it is very slow. As we have
three other machines to upgrade we are wondering if the same is
going to happen again!
Additionally, the installation procedure leaves the place in a mess
after the bomb and fails to restore the situation to what it was
before the error. This leaves users unable to use DOCUMENT. Is this
normal? (It would fail our Support Acceptance criteria on this point,
by the way, were it a Ferney product. :-) ) If not, how do we get
users going again on BL7?
Gavin
|
| 509.8 | cleaning up the mess | VAXUUM::KOHLBRENNER | | Wed Jun 17 1987 09:19 | 30 |
| BL8 (the field test update kit) installs into a tree whose
top directory is [DOC$TOOLS] and BL7 installed into a tree
whose top directory was [DOCTOOLS], so they should not
interfere with each other.
I suspect that the "mess" that is left from the failed install
of BL8 is due to the redefinition of logical names. The failure
that you described came while the savesets were being restored into
VMSINSTAL's working subdirectory (before any files have actually
been moved to the target tree), and VMSINSTAL is supposed to
recover cleanly from a failure at this point.
The problem is that KITINSTAL.COM has already executed a new
DOC$STARTUP.COM, which has already changed all the logical names
so that when it comes time to do the IVP, the logical names will
be set up correctly. The new DOC$STARTUP.COM is not yet in the
SYS$MANAGER directory, however.
So, after the failed installation, if you execute
$ @SYS$MANAGER:DOC$STARTUP
you should be back in business with BL7, since the BL7 version of
DOC$STARTUP.COM is still there.
bill
(The installation failure that you report implies that some part
(or all) of the BL7 saveset is being included in the BL8 saveset.
I can't imagine how COPY or FTSV can do that...)
|
| 509.9 | Ta. | FNYFS::WYNFORD | The Rented Loony | Wed Jun 17 1987 10:32 | 6 |
| Many thanks for the info - we'll have everyone back in business
in no time!
If it happens next time I'll send you a log directly.
Gavin
|
| 509.10 | Kit in European loc. | CLOSET::ANKLAM | | Wed Jun 17 1987 10:32 | 9 |
|
There is now a copy of the kit in the Netherlands, at
- IJSAPL::$1$DJA19:[KIT.DOC]
Has anyone installed from this kit, either successfully or not ?
|
| 509.11 | A few kilometers away | TALE::ZGRAGGEN | Searching for infinity... | Wed Jun 17 1987 12:28 | 9 |
| Gavin
You can also get the kit in Geneva (just across the border) from
SHIRE::DOC$ROOT:[LOCAL.KIT]
It worked once...
Peter
|