| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2532.1 | | DECWIN::FISHER | Prune Juice: A Warrior's Drink! | Thu Mar 29 1990 17:43 | 4 |
| How does dw: get defined? You are running in the context of SYSTEM now, not
your own.
Burns
|
| 2532.2 | | SMAUG::MENDEL | In some strange power's employ | Fri Mar 30 1990 14:16 | 1 |
| Aha!
|
| 2532.3 | | SMAUG::MENDEL | In some strange power's employ | Fri Mar 30 1990 14:40 | 9 |
| Rats. Still No luck. Still no helpful message, either.
Can anyone confirm that XSETROOT can draw to the login window?
Or confirm that it can't?
Are there any other tools that can? I have a .DDIF and a .XBM
of the background I'd like to paste.
Kevin
|
| 2532.4 | XSETROOT works | ATLV5::DIAL_B | | Fri Mar 30 1990 15:28 | 7 |
| Yes XSETROOT can set the login screen background, I've used it. XPHOON
works as well. In my experience, the problem you describe is usually
due to a logical name problem. Try the command procedure while you a
logged in, if you haven't already. Does everything have the right
device name included?
Barry
|
| 2532.5 | | SMAUG::MENDEL | In some strange power's employ | Fri Mar 30 1990 16:45 | 15 |
| The command procedure SMAUG.COM is (now)
$ define sys$output wyrd$dua0:[mendel.com]smaug.log
$ mcr sys$sysdevice:[toolbox]xsetroot -
-bitmap wyrd$dua0:[mendel.decw]smaug.xbm -fg black -bg forestgreen
$ exit
I hope that SYS$SYSDEVICE, SYS$OUTPUT, and WYRD$DUA0 are valid in the
context that they are in.
And it works fine when I say @smaug.
Quota?
Kevin
|
| 2532.6 | | SMAUG::MENDEL | In some strange power's employ | Fri Mar 30 1990 17:38 | 11 |
| Ker ... Ker ... KerrACK! BOOOM!
Lightning Strikes.
I need to add a SET DISPLAY/CREATE/NODE=node !
Doy!
Bye, y'all.
Kevin
|
| 2532.7 | Not �Doy! at all... | DECWIN::FISHER | Prune Juice: A Warrior's Drink! | Mon Apr 02 1990 17:34 | 9 |
| Not doy at all. You should not have to do set displ (after all, in general,
you don't know what the display is!). And in fact, you don't. The display
is actually in SYS$OUTPUT, and in a little-known piece of code (even to us)
XLIB uses SYS$OUTPUT if it can't find it anywhere else. So the define sys$output
was what shot you in the foot.
Sadder but wiser,
Burns
|
| 2532.8 | | SMAUG::MENDEL | In some strange power's employ | Mon Apr 02 1990 18:12 | 12 |
| Ah, I see. So I stumbled on the solution purely by accident.
Well, its happened before. Thanks for all your help, everyone.
Defining sys$output was the only way I had of determining what
error I might have been getting. So, now knowing, I'll leave it
this way. (Finding error messages is a real pain in DECWINDOWS
sometimes, ain't it?)
And I *do* know what the display is: 0. What else could I want
in the context of DECW$LOGIN_BACKGROUND?
Kevin
|
| 2532.9 | | DECWIN::FISHER | Prune Juice: A Warrior's Drink! | Tue Apr 03 1990 15:29 | 4 |
| If you were creating a session on an X Terminal, it might well be somewhere
other than 0.
Burns
|
| 2532.10 | | SMAUG::MENDEL | In some strange power's employ | Wed Apr 04 1990 13:48 | 2 |
| Why would you / How could you paint a *_login_* background on another
node?
|
| 2532.11 | Lots of reasons! | DECWIN::FISHER | Prune Juice: A Warrior's Drink! | Thu Apr 05 1990 13:17 | 22 |
| > Why would you / How could you paint a *_login_* background on another
> node?
Why? Because you can't run DECwindows applications, including the session
manager, on a DECwindows terminal or on a PC. Thus, you start the entire
session remotely, and point the whole thing at the DWT or PC.
How...the only supported way is via the DWT software and/or PCSA. The
unsupported way is:
1. Set up authorization on server to accept connects from
client node, system account.
2. On the client:
SET DISP/CREATE/NODE=server
RUN SYS$SYSTEM:DECW$STARTLOGIN
Oh oh...now I've let the cat out of the bag. Actually, I'm sure this is
mentioned somewhere else in this conference too.
Burns
|