[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | POLYCENTER Console Manager |
Notice: | Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS: |
Moderator: | CSC32::BUTTERWORTH |
|
Created: | Thu Aug 06 1992 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 1541 |
Total number of notes: | 6564 |
1184.0. "Wheird phantom lines in C3." by 54687::WIJKAMP (One day, you won't drink beer, you'll drink GROLSCH) Tue Feb 06 1996 11:09
Hello,
Customer reports the following strange happening.
He runs PCM V1.6-110 on a vaxstation 4090 VMS V6.1.
He display's his C3 on his collor VXT2000. He uses his own
copy of console$c3.dat in his sys$login directory.
Once in a while (� once a week) he all a sudden sees a line
drawn in his C3 window. It always starts at the left-top of
the screen, and runs in a different angle into the C3
display.
When he than give an exit from C3, than the file
console$c3.dat is update with the line info. It looks
somthing like:
64 LINE: 0,0,806,493,1,#000000000000
The first part is always "line: 0,0," but the other numbers
vary.
Further strange thing is, that the C3 is always in
interactive-mode, and not in edit-mode. Still the line is
created.
They never saw this happen on the console terminal from the
vaxstation with C3 from system.
Windows-motif and VXT are on the latest SW versions.
There is offcourse a simple workaround: when the line apears,
don't exit but do a QUIT, and the line will not be saved.
But the customer is wondering how this is possible.
I have been on location, and I'm convinced they are not
messing things up.
There are no motif applications running only decterms ect.
These line just show up once in a while.
Anybody ever seen this before???
Thanks for your answers in advance,
Ren� Wijkamp,
MCS, OSS The Netherlands.
T.R | Title | User | Personal Name | Date | Lines |
---|
1184.1 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Tue Feb 06 1996 17:59 | 7 |
| Rene,
Yep I've seen this one and it has been reported. The exact details of
how it gets there are escaping me but I beleive NSI has fixed this
problem and it will be in the upcoming ECO 2 kit.
Regs,
Dan
|