| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5464.1 | We have problems with it | EIGER::SCHNEIDERR | | Wed Aug 11 1993 08:24 | 19 |
| Hello Birgit,
I don't know if it is supported or not, but we have some experience with useing
PC X-WINDOW applications with DECmcc.
A customer tried EXCURSION. It didn't work with MCC V1.2 and V1.3. Always we
saw that the window on the PC died or locked after a view operations. We saw a
meassage like "insufficent recoures at system".
Now this Customer uses DW DOS on the PC and it works very well !!!!
An other customer uses XVISION on the PC and TCP/IP as transport. This is even
worser that EXCURSION. MCC crashes, lot of errormessages, the window dies ...
There is a patch arround to fix some Iconic MAP (X-Windows) problems, but this
didn't help with the XVISION. We didn't try on the EXCURSION system.
Regards Roland
|
| 5464.2 | re .0 | TRKWSH::COMFORT | Here beside the rising tide | Wed Aug 11 1993 11:25 | 17 |
|
My customer has been using eXcursion for a couple years now with MCC
with varied success. Indeed eXcursion V1.0 had some problems with MCC
V1.1 and V1.2. Most problems occur with respect to the PC running out
of memory resource. Other problems involve leaving "ghost" DECnet
links up that ultimately cause DECmcc to experience startup problems.
The customer and I obtained information that V1.1c or greater will
function better. The customer installed V1.1c shortly after I upgraded
a test MCC system to V1.3. The eXcursion window has been pretty
heavily tested and so far with DECmcc V1.3, DECW$MOTIF V1.1 and
eXcursion V1.1c, the problems seem to have gone away. I suspect that
sooner or later we will hit the memory resource problem again, but the
issue has been reduced so much that X-displays are now considered a
viable implementation for remote DECmcc displays.
Dave
|
| 5464.3 | Thanks | MUNICH::FERSTL | | Wed Aug 11 1993 12:04 | 23 |
| Re .1, .2
Thank you for your answers.
I was asking, because my customer is often having problems when the
PC crashes.
The DECnet link then is in a "closed" state and the Client-process
on the MCC-system (PCX$SERVER process running the MCC_MAIN.EXE)
is still alive.
In this situation it isn't possible to create a new display (you
just see the copyright window and then it hangs) on a
PC or a Workstation until the old PCX$SERVER process is killed.
I could reproduce it in my office with DECmcc V1.3 and Excursion
V1.1g.
I was asking if Excursions is supported, because I'd like to know if I
should escalate the problem or just tell the customer that he can be
happy that he is having no other problems (like resource problems)
than the "MCC hanging" problem.
Thanks for you quick help
Birgit
|
| 5464.4 | Same in batch | TRKWSH::COMFORT | Here beside the rising tide | Wed Aug 11 1993 15:35 | 13 |
|
I don't know that this is relevant, but maybe the question is why
doesn't MCC exit properly under certain circumstances. I have seen
this type of situation when running MCC maps from a batch file, the
DECnet link is hosed up and the batch is just sitting there, but there is
no display on the VMS workstation (or PC) and like your situation, one
cannot start a new X-session to the target workstation without killing
the orphaned process that MCC is running in.
No answers, just more questions.
Dave
|