Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
Moderator: | STAR::VATNE |
Created: | Mon Oct 30 1989 |
Last Modified: | Mon Dec 31 1990 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 3726 |
Total number of notes: | 19516 |
I'm having a problem when I try printing anything from a DECwindows application. The applications are on a VMS V5.1 cluster and I'm using my workstation as server. Whenever I try to print anything from either DECmail or DECwrite, the application hangs for a while and then crashes with an access violation. This doesn't happen for applications executed locally on my VAXstation. The versions are all V5.1. Is there something I should be looking at? Thanks, -Vijay Included below is the dump of what happens when I run DECW$MAIL, select a message and then hit print: delni> set displ/node=dsilva/creat delni> mc decw$mail (after 3-4 minutes) %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=4B4D5354, PC =80000010, PSL=03C00020 Improperly handled condition, image exit forced. Signal arguments Stack contents Number = 00000005 801BCA6E Name = 0000000C 00000002 00000001 7FEB7D60 4B4D5354 7FEB7D48 80000010 00000004 03C00020 7FEBAD3D 00000001 7FEBB771 7FEBAD17 03000001 Register dump R0 = 7FEBAD3D R1 = 4B4D5354 R2 = 00000072 R3 = 7FEBB5D4 R4 = 00303B20 R5 = 7FEBA8AC R6 = 00168504 R7 = 000E19B0 R8 = 00000000 R9 = 00000001 R10= 7FEBBA8C R11= 00168504 AP = 7FEB7CFC FP = 7FEB7CBC SP = 7FEB7D38 PC = 80000010 PSL= 03C00020
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
860.1 | RTL::GRASS | Steve Grass | Wed May 31 1989 16:06 | 5 | |
There's a bug in the current version of the print widget where it allows a maximum of 100 print queues and 100 print forms. Could this be your problem? steve | |||||
860.2 | Too many print/server queues? | NAC::DSILVA | Wed May 31 1989 17:48 | 14 | |
I counted the number of print queues & forms: 62 and ~25 respectively. There are also 61 server queues. Do you think that the print widget is trying to deal with both the printer and the server queues? That would total 123. Do you know of a way around this - apart from deleting the queues on the cluster which I would hardly mind but have no access to. Thanks for the reply. -Vijay | |||||
860.3 | Try something like this... | EZWIND::LEVY | Bound to cover just a little more ground | Thu Jun 01 1989 08:01 | 24 |
In order to get the print widget to deal with bunches of queues in a more efficient way, you might try something like this in your system startup (after DECwindows has been started). $@SYS$MANAGER:DECW$LOGICALS $ DECW$DEFINE DECW$PRINTER_FORMAT_TEXT "ADMIN,CST1,MED,MISQ,RPG,SYS$PRINT,YWO_LPS_ANSI" $ DECW$DEFINE DECW$PRINTER_FORMAT_LINE "ADMIN,CST1,MED,MISQ,RPG,SYS$PRINT,YWO_LPS_ANSI" $ DECW$DEFINE DECW$PRINTER_FORMAT_TERM "ADMIN,CST1,MED,MISQ,RPG,YWO_LPS_ANSI" $ DECW$DEFINE DECW$PRINTER_FORMAT_ANSI "ADMIN,CST1,MED,MISQ,RPG,YWO_LPS_ANSI" $ DECW$DEFINE DECW$PRINTER_FORMAT_ANSI2 "ADMIN,CST1,MED,MISQ,RPG,YWO_LPS_ANSI" $ DECW$DEFINE DECW$PRINTER_FORMAT_PS "YWO_LPS_POST" $ DECW$DEFINE DECW$PRINTER_FORMAT_REGIS "YWO_LPS_REGIS" $ DECW$DEFINE DECW$PRINTER_FORMAT_TEK "YWO_LPS_TEK4014" $ DECW$DEFINE DECW$PRINTER_FORMAT_DDIF "ADMIN,CST1,MED,MISQ,RPG,SYS$PRINT,YWO_LPS_ANSI" These logicals will go into the DECW$LOGICAL_NAMES table and will really help the performance of the print widget. Please note that for each printer format type, I am pointing the logicals at the GENERIC queues on the cluster (except for the LPS40 queues). Try it. You'll like it. - Dave |