| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 193.1 | me, too | POBOX::MAMMEN | | Tue Feb 14 1989 23:27 | 5 |
| I am experiencing a similar problem with a 3100, 8 meg, VMS 5.1
FT3 and DECwindows. Printing to a LAT que ANSI2.
|
| 193.2 | Same thing here | SYSENG::COULSON | Roger Coulson DTN 223-6158 | Wed Feb 15 1989 08:30 | 27 |
|
RE: .0 and .1
Being new to this workstation stuff I just got around to trying
the print screen function. I have a VS2000 with VMS V5.1 and
DECwindows SDC version. The same thing happened to me. My whole
session went away and I had to log in again. I saved the SM log
below.
File - DECW$SM.LOG
%SET-I-NEWLIMS, new working set: Limit = 200 Quota = 200 Extent = 7200
%DCL-S-SPAWNED, process Clock spawned
%DCL-S-SPAWNED, process Calendar spawned
Session Message: Started DECterm controller
Session Error: %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=01FFFFFE, PC=0005
XIO: non-translatable vms error code: 0x2DBA002, vms message:
%decw-e-cnxabort, connection aborted
XIO: non-translatable vms error code: 0x2DBA002, vms message:
%decw-e-cnxabort, connection aborted
%XLIB-F-IOERROR, xlib io error
%XLIB-F-IOERROR, xlib io error
COULSON logged out at 14-FEB-1989 15:47:01.05
|
| 193.3 | there is a workaround | CSSE32::MERMELL | Window Pain | Wed Feb 15 1989 09:34 | 13 |
| This problem was, I think, explained in the previous version
of the DECwindows notes file (the one that wasn't backed up).
It was a problem that was QAR'ed in FT2. The QAR was marked
"fixed in V1" but the fix apparently slipped through the
cracks.
I think it's actually a problem with the print widget, which
explains why this workaround works: Use "capture" to
a file instead of "print." Then just print the file from
DCL or VUE. You have a choice of handy DDIF or POSTSCRIPT
formats.
|
| 193.4 | | LESLIE::LESLIE | Introducing Roy Rogers on Trigger | Wed Feb 15 1989 11:39 | 5 |
| re: .3
This note is available in the newly rebuilt version of DECWINDOWS_OLD
on BULOVA:: - #1719 as I recall :-)
|
| 193.5 | oh, you want to PRINT something? | 20998::CLEGG | Wrong the RIGHT way. | Thu Apr 27 1989 17:03 | 15 |
|
Actaully, on our systems, ALL of the print options kill your process. Printing
the screen, portion of a screen, the print menu in the fileview, and even
the print menu in DECwrite. (which used to work)
I don't know if these are related problems or not, but it looks kind of
suspicious. Does anyone know if the VMS 5.2 field test has fixed any of these
bugs? Is there anything I should look for on my end as a possible cause of the
problem? (the environment is a mixed interconnect cluster, with VS2000s and an
8700)
Chris Clegg
|
| 193.6 | | LESLIE::LESLIE | Andy ��� Leslie, CSSE/Europe | Thu Apr 27 1989 18:58 | 2 |
| Please submit a QAR.
|
| 193.7 | | CSSE32::MERMELL | Window Pain | Thu Apr 27 1989 20:23 | 8 |
| It's already been QARed. It's a problem with the Print Widget.
The workaround is to "capture" screen or portion thereof,
then submit the file to a queue.
By the way, the QAR was closed in field test saying it was
fixed in the SDC version, but it wasn't. The QAR has been
reopened.
|
| 193.8 | | LESLIE::LESLIE | Andy ��� Leslie, CSSE/Europe | Fri Apr 28 1989 04:44 | 4 |
| Thanks Andy.
Andy#2.
|