| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 256.1 | | LESLIE::LESLIE | Andy ��� Leslie | Mon Feb 20 1989 16:21 | 2 |
| sho log decw*
|
| 256.2 | | SEAN::DAVIDSON | | Tue Feb 21 1989 08:37 | 3 |
| Also sho log/table=* decw* or read through SYS$STARTUP:DECW$STARTUP.COM and
associated files.
|
| 256.3 | Not the complete answer... | VINO::WITHROW | Robert Withrow | Tue Feb 21 1989 10:13 | 4 |
| RE: .1 .2, Those suggestions only show what logicals *are defined*, I'd
be interrested what logicalse *can be defined*. I assume that the first
set is a subset of the second one.
|
| 256.4 | An evil competitor made me do it | YGDRSL::SANTIAGO | Drinking deeply of the Pierian spring | Tue Feb 21 1989 12:20 | 7 |
| You can define *anything*! I just successfully managed to define DECW$FOO!
Actually, I suspect you'll find DECwindows to be not quite as
logical-name-intensive as VWS. Use menus when you want to customize
something in a supported way, resources when you want a more useful
way. The logicals that are there are for the most part pretty boring.
|
| 256.5 | | VWSENG::KLEINSORGE | Toys 'R' Us | Tue Feb 21 1989 13:44 | 11 |
| re: .4
Not really if you are comparing the base system logical names.
DECwindows just managed to hide the names a little better in
logical name tables, like all the server parameters.
VWS has no policy for where applications get their startup information,
which is where DECwindows has application 'resource' files.
|
| 256.6 | VUE Application Logicals? | MARMAT::JERRY | Perfessor Quintessence | Tue Feb 21 1989 14:34 | 7 |
| I was looking for some of the possible logicals for the startup of
applications under VUE, and etc.
Tried defining DECW$CARDFILER to a group cardfile but no luck...
Jerry
|
| 256.7 | FileView logicals | STAR::BENSON | | Wed Feb 22 1989 11:43 | 36 |
| There are no logicals that cause applications to start up under
FileView. The logicals that FileView uses are:
VUE$LIBRARY
This is where VUE looks for the VUE$*.COM files that implement
the verbs on its menus. It also looks here for the system and
public profile files if VUE$SYSTEM_PROFILE and/or VUE$PUBLIC_PROFILE
are not defined. This logical is normally defined in the
DECW$LOGICAL_NAMES table to point to the search list
SYS$COMMON:[VUE$LIBRARY.USER], SYS$COMMON:[VUE$LIBRARY.SYSTEM].
VUE$PROFILE
The name of your private profile file. If not defined, FileView
looks for DECW$USER_DEFAULTS:VUE$PROFILE.VUE$DAT.
VUE$PUBLIC_PROFILE
The name(s) of shared public profile file(s) containing definitions
of verbs, menus, and saved views you want included in your
FileView window. If not defined, FileView uses VUE$LIBRARY:*.VUE$DAT.
VUE$SYSTEM_PROFILE
The name of the system profile file. If not defined, FileView
uses VUE$LIBRARY:VUE$SYSTEM_PROFILE.VUE$DAT, which is the
profile shipped with FileView.
The way to get applications to start 'automatically' is to start them
from your DECW$LOGIN.COM command file (except for FileView and DECterm,
which the Session Manager will start for you). We're looking at ways of
improving this in the future...
Tom
|