| Title: | DOCUMENT T1.0 |
| Notice: | **New notesfile (DOCUMENT.NOTE) now available (see note 897)** |
| Moderator: | CLOSET::ADLER |
| Created: | Mon Feb 09 1987 |
| Last Modified: | Thu Oct 31 1991 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 897 |
| Total number of notes: | 4397 |
Well, I finally got DOC010 installed, after only minor problems
(like inadvertently typing <CR> for additional destination/queue
names, or losing the PostScript IVP output).
Now, in trying to install DOCLN03010, the IVP seems to be blowing
up during the TEX processing. I'm currently trying the installation
without running the IVP, but the fact that the IVP blew up makes
me nervous. The specific error messages were something like this:
(VMSINSTAL doesn't let me assign SYS$ERROR: to a file)
[T e x t F o r m a t t i n g]
%TEX-I-IDENT, T1.0-005
%RMS-E-FNF, file not found
-SYSTEM-W-NOSUCHFILE, no such file
-TEX-I-FILENAME, 'DOC$ROOT:[TEX.LN03.FONTS]DECLOGO.TFM;'
%TEX-I-SHOWCONTEXT, ' {'
%TEX-I-SHOWCONTEXT, '...ee 'readfont \logo {declogo} {'
%TEX-I-SHOWCONTEXT, '
har 34 \ch...'
%TEX-I-SHOWCONTEXT, '->'vbox {\kern -24pt\declogo '
%TEX-I-SHOWCONTEXT, '
%TEX-I-SHOWCONTEXT, '...ox {\setuptablecolhsize \tempcsB
%TEX-I-SHOWCONTEXT, '
revdepth }...'
%TEX-I-SHOWCONTEXT, '->\body '
%TEX-I-SHOWCONTEXT, ' \let \next \iterate \el
fi \next
%TEX-I-SHOWCONTEXT, '...artfalse \fi \settablerowbox '
%TEX-I-SHOWCONTEXT, '
exttablero...'
%TEX-I-SHOWCONTEXT, '...{\kern -24pt\declogo }}'
%TEX-I-SHOWCONTEXT, '
%TEX-I-LINE, Error occurred on or around line number: 21
%TEX-I-SHOWCONTEXT, '\copyrightline{1987}{0}'
%TEX-I-SHOWCONTEXT, ' '
%TEX-I-FILENAME, 'doc$sample'
-TEX-I-ONPAGE, on page [ii]
%TEX-I-PAGESOUT, 10 pages written.
-TEX-I-OUTFILENAME, 'vmi$root:[sysupd.docln03010]DOC$SAMPLE
%DOC-E-ERROR_FORMATTER, Errors found by the Text Formatter
%DOCLN03-I-IVP_FAILURE, VAX DOCUMENT LN03 FONT FILES T1.0
IVP failed.
%VMSINSTAL-E-IVPFAIL, The IVP for DOCLN03 V1.0 has failed.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 401.1 | check DOC$LOCAL_ELEMENTS | CLOSET::ANKLAM | Wed May 20 1987 17:07 | 22 | |
It looks like the IVP is failing because it's looking for
a definition of \declogo on the copyright page.
This would probably happen if you
have the logical name DOC$LOCAL_ELEMENTS defined and pointing
to a base-level 7 version of CUP$LOCAL_ELEMENTS.TEX. If you
follow the steps in the installation guide, namely:
1. rename doc$root:[local.formats]cup$designs.dat to
doc$designs.dat
2. change DOC$STARTUP.COM to define
DOC$LOCAL_ELEMENTS as DOC$ROOT:[LOCAL.FORMATS]CUP$LOCAL_ELEMENTS.TEX
( both of the above DOC$ROOT's are BL8 !!!)
3. Remove from your LOGIN execution path any command files that
define DOC$LOCAL_ELEMENTS to be anything else.
-patti
| |||||
| 401.2 | So what ARE local elements? | PDVAX::P_DAVIS | Peter Davis (aka SARAH::P_DAVIS) | Wed May 20 1987 17:21 | 19 |
Thanks. Please note that I haven't even installed the DOCINT010
kit yet. Isn't there where all the local formats are? It seems
a bad idea to make the IVP depend on prior installation of DOCINT010,
particularly since customers may not install DOCINT010 at all.
I seem to be having a similar problem with with generating contents
for a report. I'm getting messages like:
%RMS-E-DNF, directory not found
-NONAME-W-NOMSG, Message number 00000000
-SYSTEM-W-NOSUCHFILE, no such file
-TEX-I-FILENAME, 'DUA1:[DOCTOOLS.LOCAL.FORMATS]CUP$LOCAL_...
I presume this is also because DOC$LOCAL_ELEMENTS is incorrectly
defined. My question is, "Why is this using local elements at all?"
I thought local elements were for DEC internal use.
Thanks.
-pd
| |||||
| 401.3 | internal things | CLOSET::ANKLAM | Wed May 20 1987 17:28 | 28 | |
It's not that the installation relies on the internal software
being there, it's the way that DOCUMENT is set up to accommodate
local customs, etc:
1. When the text processor starts up, we load a file called
DOC$LOCAL_ELEMENTS. It's default is NL:, that is, no file. But
if the logical name is defined, it is read in. In Bl7 and below,
the logical name was made on a process-basis, through execution
of local DOC$STARTUP.COM files. In Bl8, it's made system-wide
and the IVP normally doesn't look for it.
2. One of the things that is in CUP$LOCAL_ELEMENTS, which we
distribute, is a bunch of things that get printed by default
on copyright pages (the famous "we don't promise to be perfect"
paragraphs, and the list of trademarks, including the dec logo).
3. In BL7 and below, there was a font that contained the characters
for the declogo. We removed this from the external kit, and put
it, and appropriate pointers to it, in new versions of
CUP$LOCAL_ELEMENTS, but since you are getting some of the previous
definitions, you are getting the error.
I suspect that we haven't heard more about this is that most
installations are done from system manager's accounts, and they
didn't have any of the old COM files set up.
| |||||
| 401.4 | Some questions | 51336::LITBY | P-O Litby, TSSC Stockholm/Sweden | Fri May 22 1987 08:48 | 12 |
I have a couple of questions regarding the baselevel 8 kit:
1) What is DOCINT010? In BL7, there were six savesets
DOC010.A - DOC010.F. There was no need to install anything
called DOCINT.
2) The kit directory on VAXUUM seems to contain four savesets
only, DOC010.A through DOC010.D. Is this the way it should
be?
-- POL
| |||||
| 401.5 | diff between 7 and 8 ? | DELNI::COLELLO | Fri May 22 1987 09:27 | 1 | |
so what's the difference between bl07 and bl08? | |||||
| 401.6 | SHIRE::ZGRAGGEN | Searching for infinity... | Fri May 22 1987 12:51 | 1 | |
The release notes and installation guide tell all. | |||||
| 401.7 | 3 kits | CLOSET::ANKLAM | Fri May 22 1987 13:28 | 18 | |
For base level 8, we decided to keep Digital internal doctypes and
special definitions in a separate kit. DOC010.A through .D are
the standard DOCUMENT kit, exactly what we send to customer field
test sites.
The second kit, DOCLN03010, contains LN03 support. For royalty
purposes, this has to be a separate kit.
DOCINT010 contains the Digital-internal use only document types
and copyright page definitions.
Base Level 8 consists of bug fixes and support for items that weren't
completed for Base Level 7. As Peter notes, the release notes
tell all.
patti
| |||||