|
If I remember correctly, during the installation I was told it's not
a must to include DECwindow device support if I only plan to be a user.
(that means another 3300 blocks!) I thought about I'm using
workstation, but that message shouldn't appear because DECwindow is
supposed to be designed for workstation. Am I right?
|
| Vivian,
You misunderstood the difference between client and user. You can skip
the device support if this is a client only machine (not a workstation).
Without device support, you must display across the net to a workstation
with device support.
The user part of the kit is the OOTB applications. You can skip those if
you are going to run them remotely to display here.
Dick
|
| Vivian,
Don't get me wrong... but an Rd54 has a wealth of space for DECWindows
and even given the mandatory 3300 blocks you need for the server
component, you should'nt worry about any aspect of disk space (assuming
that you can get beyond the first save set) requirements. In addition I
have the DECWINDOWS documentation, DECWrite, VWS and info installed on
my system disk (along with a wealthy page and swapfile), and have around
15000 blocks free. Finally the installation kit checks for the blocks as
you are answering questions as to what the requirement is for free
space. One of the other notes in this conference indicates that there
are less fortuate folks who have accomplished the trick on rd53s
(including vms no less), so 3300 blocks should be NO SWEAT.
I feel incredibly lucky to have an rd54, and the first time I go looking
for extra disk space (more than 3300 blocks) I'll go looking for the
language dependent linkage libraries in sys$library, like *.pli,*.bas,
etc...
Just as a rule of thumb when installing layered products which have
programming interfaces... There is typically a question which relates to
language dependant linkage libraries, and if you answer that you do not
desire to install all support; it will prompt you for each language
desired. If you are scrupulous about disk space this is the safest place
to trim at installation time (and possibly the most significant
savings).
Bottom line : if you have to be conservative at installation time I
would recommend you always do so at the possible expense of development
support (language dependent), and never for other components unless you
understand what you will lose in the process. DECWindows even installed
from disk on a 3500 is one of the most lengthy installations I've ever
been exposed to, so this particular problem will be a costly one for you
(in addition you will be without a windowing envirionment) as far as
time is concerned.
Hope this saves the time of reinstallations in the future.
regards,
mdw
|