[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

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

1800.0. "Print Screen under VMS 5.2" by FRSTSC::ERLEMANN () Tue Nov 28 1989 08:56

Hi everybody,

don't know how often this problem has already been discussed,
but there's no topic where to get a definite solution.

My (and many customers') problem is that PRINT SCREEN blows
the whole DECW session away. This is a known problem for version
5.1 and there have been many official voices who promised that
'This problem has been corrected in VMS V5.2.  This is documented in           
section 2.3.5 of the "VMS Version 5.2 Release Notes", June 1989,              
(AA-LB22B-TE).' {official article from STARS database}

Many of my customers (especially a large banking project in Germany)
reclaimed this problem to me, and what did I? I promised them as well
that their problem would have been gone after upgrading to VMS 5.2.

Now, after doing this upgrade the same customers phoned me and told
me about the exactly same problem!!!

I am very disappointed about the "official information" read in STARS
and the least what I have learned about that, is never more to promise
anything more.


But now: IS THERE ANY CONVENIENT PATCH/WORKAROUND/SOLUTION...???

All customers work with a 8MB V3100, V5.1/5.2 and the problem occurs
after issuing a 'printscreen/print(portion) of screen' the sessions
aborts at once.


I am very helpless

	Armin Erlemann, Digital Service Center Frankfurt
T.RTitleUserPersonal
Name		DateLines
1800.1JAMMER::JACKMarty JackTue Nov 28 1989 10:361
    This is why we were taught never to promise fixes in a specific version.
1800.2It works..EVTIS2::HOANGTue Nov 28 1989 10:388
    
    	It works for me on the same workstation VS3100/8mb.
    	The OS i have is VMS 5.2-1
    
    	Could you check the use of Dynamic memory (PAGEDYN & NPAGEDYN)?
    
    				Dung HOANG
    				TSC EVRY FRANCE
1800.3Can anyone help with this?DWOVAX::YOUNGHistory punishes the late - MGWed Nov 29 1989 16:4010
    I am having the same problems, especially with some workstations still
    running 5.1-B.  (They cannot upgrade yet because of 3rd party software
    compatibilty).
    
    Does ANYONE have ANY patchs for the Printscreen function? Please?  We
    are using some of these systems for demos and the workaround (capture
    screen, then print file) is really hurting us.  Customers are always
    commenting about the user-Unfriendliness of this.
    
    --  Barry
1800.4STAR::ORGOVANVince OrgovanFri Dec 01 1989 18:089
    There is indeed a printscreen problem in VMS V5.1 that causes the
    session manager to abort with an access violation. When the session
    manager exits, it takes all of the running DECwindows applications
    with it and restarts the session.
    
    There was a problem isolated and fixed in VMS V5.2 that prevented
    an access violation. At the time that V5.2 shipped, it was believed
    that this was the only problem, hence the release note statements
    to that effect. However, it wasn't the only cause of the problem.
1800.5ANY patches for 5.1 ??DWOVAX::YOUNGHistory punishes the late - MGTue Dec 05 1989 00:244
    Yeah, but does anyone have *any* patches for v5.1 ???
    
    I will accept patches of almost any quality (I'll test them first,
    don't worry).
1800.6one way to do it ...MIZZOU::SHERMANECADSR::SHERMAN 235-8176, 223-3326Fri Dec 22 1989 16:1742
I have a GPX running VMS 5.1 with an LA75 attached.  I like printing screens
and ran into the window crashing problem.  I realize that the following does 
not solve the problem, nor is it clever.  But, it makes things a bit easier
and may save somebody some time.

First, I select SIXEL output format from the Session Manager -> Customize -> 
Print Screen ...  menu.  I save the current settings from the Session Manager 
-> Customize -> Save Current Settings option.  Next, I define a command in my 
login.com that can be run from an account on my workstation:

	prsc:==@my_login_disk:[my_login_directory]prsc.com

Then, I include this command file at that location:

	$ print my_login_disk:[my_login_directory]decw$capture.tmp
	$ print my_login_disk:[my_login_directory]clear_printer.fil
	$ pu my_login_disk:[my_login_directory]

Now, when I print screen I do a regular screen capture, then go to any window 
logged into my system and enter:

$ prsc

The screen is dumped to my LA75 without crashing my windows.  This provides 
a quick print of the screen with about four button clicks and a command entry.

The file clear_printer.fil contains the escape sequence "ESC c" which resets
the LA75 to its initial state (see page 112 of the LA75 Companion Printer
Programmer Reference Manual).  (I found that print screen can mess up the
setup of the printer.)  You can create this by using decimal 27 with the 
SpecIns function of EDT or TPU or whatever, followed by "c".  These
two characters in sequence in clear_printer.fil will reset the printer when
clear_printer.fil is printed.

For those that can get it, I have included a form feed at the end of this
note which is followed by the two characters.


Steve

c