T.R | Title | User | Personal Name | Date | Lines |
---|
1899.1 | /display=decwindows | CGOOA::OWONG | SKIWI in Canada (VAO) | Sat Apr 05 1997 03:29 | 36 |
| From $ HELP LSE - I think the qualifier you need is /DISPLAY=DECWINDOWS
Owen.
====================================================================
LSEDIT
/DISPLAY
/DISPLAY=CHARACTER_CELL (D)
/DISPLAY=DECWINDOWS
/DISPLAY=display-filespec
/NODISPLAY
Specifies which screen manager you want to run.
The /DISPLAY command qualifier is optional. By default, LSE uses
the
character-cell screen manager. As an alternative to the
/DISPLAY
qualifier, you can define a logical name LSE$DISPLAY_MANAGER
as
DECWINDOWS, CHARACTER_CELL, or as a screen manager file
specification.
If you specify /DISPLAY=CHARACTER_CELL, LSE uses the
character-cell
screen manager, which runs in a DECterm (or VWS) terminal emulator
or
on a physical ANSI terminal.
If you specify /DISPLAY=DECWINDOWS, LSE uses the DECwindows
screen
manager, which create a DECwindows window in which to run LSE.
|
1899.2 | guess I should x-post in xcursion | DONVAN::WETZEL | | Mon Apr 07 1997 09:01 | 11 |
| Thanks for your reply. I've tried all of the different combinations
of qualifyers that I can think of. No luck. I think the problem
could be around the transport protocol(s) being used. It's TCP/IP.
Notes works this way (a decwindow application?). I don't know why
LSE won't work.
Same thing happens when I try to launch it no matter what
qualifyers I use. A ucx process kicks off and pegs the cpu. The
only way to stop it is from VMS.
I'm going to see if the xcursion folks can shead some light.
Thanks again,
Phil
|
1899.3 | it should work | EDSDS6::TOWNSEND | Paul - DECset Engineering | Mon Apr 07 1997 10:22 | 7 |
| Hi Phil,
This should work, all I had to do was set the display:
set display/create/node=<pc-address>/trans=tcpip
-Paul
|
1899.4 | Still no go... | DONVAN::WETZEL | | Wed Apr 09 1997 14:37 | 30 |
| Thanks for the info Paul. It's very encouraging to hear that
this does work. I've got some personal problem still though.
I had doing the set display only using my pc's name instead
of address. Using the address yeilds same thing. CPU usage
goes to 80%+ and nothing shows up.
Let me step back...
PC is on my desk with fixed TCPIP address connected via DE203.
I run excursion 2.1 and creat a decterm.
Decterm logs into a Vax running VMS and UCX. From DECterm I
type creat/display/node=<pc's tcpip address>/trans=tcpip
I've tryed creating icons within xcursion two ways...
(two different vms commands).
$LSEDIT/interface=decwindows
and
$spawn LSEDIT/interface=decwindows (also tried /display=decwindows)
Should work right? I mean I'm typing this note using the decwindows
notes interface on my PC, through excursion. Anyone thing of
some little thing I'm overlooking? Or how to debug it?
Thanks in advance,
Phil
|
1899.5 | | DONVAN::WETZEL | | Wed Apr 09 1997 14:45 | 25 |
|
Process UCX$REXE_BG5102 13:37:50
State COM Working set 3674
Cur/base priority 4/4 Virtual pages 14649
Current PC 0031D7BC CPU time 000:00:02:05.09
Current PSL 03C00000 Direct I/O 113
Current user SP 7FE3035C Buffered I/O 208
PID 22A2A323 Page faults 4747
UIC [SAP,WETZEL] Event flags 61000001
98000000
$41$DUA0:[SYS0.SYSCOMMON.][SYSEXE]LSEDIT.EXE
Does this help? The state flips between COM and CUR. PC is indicating a
very tight loop. Notice cpu time. I probably had it going for 2:04.30ish.
|
1899.6 | not that this helps but TPU does the same thing | HNDYMN::MCCARTHY | A Quinn Martin Production | Wed Apr 09 1997 22:39 | 6 |
| As expected, TPU (ie edit/tpu/inter=decw) does the same thing.
It is hung deep in the bowls of some scheduler routine according to SDA. I
don't have my SDA cheat sheet at home so I can't figure out the exact
image (I didn't even see 80081B38 listed when I did an show image!).
Brian J.
|
1899.7 | | EDSDS6::TOWNSEND | Paul - DECset Engineering | Fri Apr 11 1997 10:15 | 10 |
| Hi,
Sorry for not replying more quickly but I don't get a chance to read notes
as often as I used to. Anyway...
I can't try this again just yet, but I'll make time next week. I'm
fairly sure I've seen this work.
-Paul
|
1899.8 | | 63101::GLEASON | Daryl Gleason, DECset Engineering | Tue Apr 15 1997 15:23 | 23 |
| Hi Phil,
I just tried this on a PC here, and the LSE window displayed on the PC
just fine. I too used the same form of SET DISPLAY that you did. The PC
is configured to use DHCP, so I had to get its address from the WinS
manager on the NT server.
You said you're using eXcursion V2.1. The version on the PC I used
identifies itself as V2.1.309. I ran it from Windows 95 connected to an
Alpha running VMS V6.1 and UCX V4.1; Motif version appears to be V1.1:
DSASRA> @sys$update:decw$versions x
DECwindows ident is DW V1.1-921024
DECwindows server ident is DW X2.0-940825
DECwindows transport ident is DW V6.1-940402
DECwindows xlib ident is DW V1.1-921024
DECwindows motif toolkit ident is DW V1.1-921024
DECwindows apps ident is DW V1.1-921024
DECwindows programming ident is DW V1.1-921024
What versions are you using?
-- Daryl
|
1899.9 | my hanging version | HNDYMN::MCCARTHY | A Quinn Martin Production | Tue Apr 15 1997 20:35 | 5 |
| I have Excursion 3. something. I was coming in over a SLIP connection when
it was locked up. The VMS system was OpenVMS Alpha V6.1 with UCX 4.1, Motif
1.2-3 with an ECO or two.
bjm
|
1899.10 | Versions.... | DONVAN::WETZEL | | Wed Apr 16 1997 16:03 | 72 |
| I'm on a VAX running OpenVMS v7.0 and UCX 4.1-2.
DONVAN> @sys$update:decw$versions x
DECwindows ident is DW V1.2-4960311
DECwindows server ident is DW V7.0-951107
DECwindows transport ident is DW V7.0-951127
DECwindows xlib ident is DW V1.2-4960311
DECwindows OSF/Motif Toolkit ident is DW V1.2-4960311
DECwindows apps ident is DW V1.2-4960312
DECwindows programming ident is DW V1.2-4960311
DONVAN>
By any chance are you using a DE203? I found a VERY close
match to my problem on noted::excurion note 2393.
He had a DE203, and I have a DE203. I don't know what he's
talking about with the logging. I doesn't seem to me that
he's talking about the excursion logging. haven't figured out
how to do the -trap thing either. Here's note 0
<<< NOTED::NOTES$7:[NOTES$LIBRARY]EXCURSION.NOTE;3 >>>
-< note 3 has pointer to current kit >-
================================================================================
Note 2393.0 Excursion 1.2-c, Winnt35, Lse Editor 2 replies
ALFAXP::RETTERER 45 lines 19-MAY-1995 10:39
--------------------------------------------------------------------------------
Today is the day for bizarre behavior...
I have a customer that is using a DEC P90 system with Windows NT 3.5 workstation
and Service Pak2 installed.
He is using Pathworks v4.1b, Decnet along with a DE203-ab Ethernet card.
He has installed v2.30 of the Etherworks3 network drivers along with this card.
Excursion v1.2c is installed on the system and he is able to run any
Xapplication from his OpenVMS AXP system (6.1 Motif 1.2-3).
There is one exception to this, if he tries to bring up the LSE Editor using the
command:
$ lsedit/interface=decwin
Lse appears to start but it never gets displayed to the PC.
Lse thinks its running, however, the window is never mapped to the display.
It will run in a decterm if we type in: lse/interface=char, but even from the
decterm using the /interface=decwin, it will not display.
Changing video resolution, running the remote window manager, renaming all of
the resource files for LSE does not help.
OK, here is the Bizarre part!
I had him enable message logging, both the general message logging as well as
Xprotocol message logging. We issued the command to crank up the Lse editor
with /interface=decwin and the bloody thing comes up.
I had him turn off message logging and we go back to bring it back and again it
will not start. Turn message logging back on and up it comes ;^(
Just for grins, we set up the control panel to create a trap file using the
-trap=c:\trap.out in the command line for the control panel. LSE WORKS!!!
The behavior is specific to this machine only. Any user account on this system
exhibits the same outcome.
Any clues to what could be causing the behavior would be appreciated.
Rick Retterer
Atlanta-CSC
|
1899.11 | Daryl is out and back tomorrow | 63101::WANG | James - DECset Engineering | Thu Apr 17 1997 11:59 | 1 |
|
|
1899.12 | DE205 | 63101::GLEASON | Daryl Gleason, DECset Engineering | Tue Apr 22 1997 15:20 | 5 |
| The PC I use has a DE205. I'll do some more testing and see what I can
find, but we have a rather limited number of permutations that we can
try here.
-- Daryl
|
1899.13 | | 63101::GLEASON | Daryl Gleason, DECset Engineering | Tue Apr 22 1997 16:17 | 18 |
| The only other system on which I could create a DECterm via eXcursion
was a VAX with VMS V6.0 running UCX V3.3 and DECwindows V1.1 (same PC
as before).
EDSDS2> @sys$update:decw$versions x
DECwindows ident is DW V1.1-920519
DECwindows server ident is DW V6.0-930414
DECwindows transport ident is DW V6.0-930414
DECwindows xlib ident is DW V1.1-920519
DECwindows motif toolkit ident is DW V1.1-920519
DECwindows apps ident is DW V1.1-920519
DECwindows programming ident is DW V1.1-920519
LSE successfully created a display on my PC from that machine as well.
I may be able to do some more testing if I can juggle software versions
a bit, but for the moment, this is all I can offer.
-- Daryl
|