| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 729.1 | Try this | ZENDIA::DBIGELOW | Innovate, Integrate, Evaporate | Mon May 15 1995 16:18 | 15 |
| Jim,
Here's something to try.
1. Shutdown PCM
2. Delete all the files in Console$tmp
(i.e. Delete console$tmp:*.*;*)
3. Restart PCM
4. Retry the C3.
Dave
|
| 729.2 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Tue May 16 1995 23:19 | 7 |
| Jim,
I thought we had decided to move *all* systems into groups as it was
going to make your display much more manageable and hopefully perform
better?
Regs,
Dan
|
| 729.3 | More on Characteristics of Problem | BSS::LIND | Jim Lind; 592-4099 CX03-1/N14 CNMC-West | Wed May 17 1995 00:05 | 40 |
| R.E. 1.
Shutdown console, deleted all files in CONSOLE$TMP, restarted PCM but
no improvements in slowness of writing the C3 display.
There are several issues at play here:
(1) Customers should not be required to reconfigure there C3 display
as a result of the upgrade. This will be a very unpopular
"feature" in many cases. There should be a request of some sort
during the upgrade to see if that is desired.
(2) As a test, all GROUPS were deleted from the database, and the
display came up looking the same as before the upgrade, just REAL
slow in complete display paint.
(3) Performance in "painting" the system ICONS and nomenclature/lines
appears OK - the same as before. However, the display appears to
hang before painting the scroll bars or new widgets at the bottom
of the dipslay. It takes about 1-2 minutes to complete painting
of that portion of the display.
During the time of the "hang", the entire workstation is tied up, not
allowing selection of any other windows. Clicking on the "iconize"
button (upper right) will eventually result in iconizing the display
after about a 15 second delay. However, the display will still usually
not be completed in painting, it just takes that long to interrupt the
process.
We can move all CLUSTERS to groups, and we can cluster all other types
of systems (like network devices). However, I believe this should be
optional to the end user, not required for performance. There seems
to be something else going on here.
It is not clear that placing all systems in GROUPS will improve
performance, it is just a "hunch" that it will do so. I believe that
since the drawing of the icons (and labels) is fast, that there is some
other problem at play here.
Jim Lind
|
| 729.4 | BadDrawable Errors in C3 Create | 29633::LIND | Jim Lind; 592-4099 CX03-1/N14 CNMC-West | Mon Jun 19 1995 19:41 | 25 |
| Subj: cx3pcm c3 errors
After upgrade to V1.6 (FT), for some users/workstations, we received
the following types of errors when starting the C3 display:
BadAlloc (insufficient resources for operation)
BadDrawable (invalid Pixmap or Window parameter)
BadDrawable (invalid Pixmap or Window parameter)
BadDrawable (invalid Pixmap or Window parameter)
BadDrawable (invalid Pixmap or Window parameter)
BadDrawable (invalid Pixmap or Window parameter)
BadDrawable (invalid Pixmap or Window parameter)
BadDrawable (invalid Pixmap or Window parameter)
ixmap (invalid Pixmap parameter)
The CONSOEL$C3.DAT file was still in the OLD (pre 1.6) format.
WORKAROUND:
Enter the c3 display, perform some small EDIT to change the display,
EXIT (which converts to the NEW V1.6 format for the CONSOLE$C3.DAT) and
execute the CONSOLE C3 command once again. You should no longer have
these types of errors.
JIm Lind
|
| 729.5 | | ZENDIA::DBIGELOW | Innovate, Integrate, Evaporate | Mon Jun 19 1995 21:44 | 21 |
| Jim,
Can you enable debugging on the C3? This is done by executing the
following command:
$ define CONSOLE$DEBUG C3
Hopefully, this will isolate the problem.
I also assume that you are making reference to the latest release (31).
I remember seeing this problem a few weeks ago and had fixed it prior to
this release.
Thanks,
Dave
|