Conference bulova::decw_jan-89_to_nov-90

    Licensing problems prevent offical support under SDC V5.1.

    for unofficial and internal only use, check out the kit at
    RESOLV""::SYS$KITS:[PUBLIC]SDC_PSVIEWER.SAV, restore it in some directory
    and then execute some command procedure in there (sorry I forgot what
    it is, should be real obvious).

	I was running V5.1-1TA in an LAVc.  I installed the PSviewer kit
	pointed to by .2.  It installed just fine, and comes up on
	my workstation.  It kept dieing with XLIB-Insufficient Virtual Memory.	
	I upped CTLPAGES and that stopped the insufficient virtual memory
	aborts, but now my whole session hangs after I use it for a bit.
	All of the DECwindow processes are there, and the log files show
	nothing.  I've looked at quotas and don't see anything suspicious.

	Does anyone have any clues as how to fix this?

						-- Geoff

    Geoff
    	how much memory have you got?
    Andy

Re .4	24 Mb on a Mayfair GPX.

			-- Geoff

	P.S.  This problem is not specific to PSviewer.  It's just that PSviewer
	will kill it every time.  I regularly Autogen with feedback and have
	very little "garbage" in my MODPARAMS.DAT file.  Anything that's in
	the MODPARAMS.DAT file is MIN_xxx anyhow.
							-- Geoff

    Xlib insuffficient virtual memory errors occur when lib$get_vm
    returns LIB$_INSVIRMEM. Probably your system's VIRTUALPAGECNT sysgen
    parameter is too low.

               <<< Note 31.6 by STAR::ORGOVAN "Vince Orgovan" >>>

    Xlib insuffficient virtual memory errors occur when lib$get_vm
    returns LIB$_INSVIRMEM. Probably your system's VIRTUALPAGECNT sysgen
    parameter is too low.

Re .6	The problem isn't VIRTUALPAGECNT.  I changed it from 60000 to
	100000 without any change in behavior.  I could live with the
	insufficient virtual memory errors.  I can't live with the
	entire session hanging!  Several reboots a day isn't acceptable!

	Perhaps this note doesn't belong in the PSviewer note, but in
	a more generic DECwindow hang note.  It's just that I can cause
	the hang very easily with PSviewer, and I was hoping that someone
	has seen the same thing and had a fix.
							-- Geoff

    re: .7
>	The problem isn't VIRTUALPAGECNT.  I changed it from 60000 to
>	100000 without any change in behavior.  I could live with the
    
    
    	Did you also check PGFLQUOTA for that account with authorize.
    	Having large VIRTUALPAGECNT doesn't help if PGFLQUOTA isn't
    	also increased.

>          <<< Note 31.8 by PEKKA::PEURA "Pekka Peura, CSG-Helsinki" >>>

>    	Did you also check PGFLQUOTA for that account with authorize.
>    	Having large VIRTUALPAGECNT doesn't help if PGFLQUOTA isn't
>    	also increased.

	PGFLQuota is 1000000 for the account in question.  Of course,
	some of the DECwindow processes are started up using the PQL
	quotas.  Any more ideas?
						-- Geoff

>	some of the DECwindow processes are started up using the PQL
>	quotas.  Any more ideas?
    
    Sure.  (a) Actual pagefile space; (b) $ SET PROCESS/NORESOURCE_WAIT
    in a few judiciously-chosen startup files.
    
    Can you log in via SET HOST from a CCT when your system is "hung"?
    
      John

	The problem isn't physical page file space.  My page file is 100,000
	blocks, of which only 5,000 are in use and there are still 35,000
	reservable.  In general I will have 3,000 - 5,000 pages of physical
	memory free.

	I don't have any SET Process/NoResource_Wait statements in any command
	procedures that I've written.

	I can SET HOST to the system and execute anything that I want when my
	DECwindow session is hung.  That's how I've checked process quotas,
	which appear to be fine.  None of the processes are in resource wait
	states.
	
	I just have this gut feel that my SYSGEN parameters (set through
	Autogen) are at some boundry condition that the DECwindow software
	is tripping over.
								-- Geoff

	The problem is directly related to SYSGEN parameter settings.  I
	re-autogenned my system with a different feedback data file and
	the problem has goen away.
							-- Geoff

    Sorry if this is a dumb question, but what do I do to make the PSViewer
    start iconised?
    
    Also, is there a way to close a file once it has been viewed (other
    than by opening another). At the moment, I always have the last file
    viewed open.
    
    Thanks
    
    Keith

    RE: 13

    You can add the following line to SYS$LIBRARY:DECW$PSVIEWER.DAT to
    make it start up ICONized:

    	*initialState:        3

    Perhaps someone else could supply more of a resource name that would
    allow it to be put in the DECW$XDEFAULTS.DAT file.  I haven't had any
    luck along this line, which is why I put it in the SYS$LIBRARY file.

             Dave

    Hi,
    
    We are trying to read in .PS files processed with DOCUMENT that
    include .PS RAGS files.
    
    We get the following error message when it gets the page with the
    included figure:
    
    %%[ERROR:INVALIDRESTORE;OFFENDING COMMAND:RESTORE]%%
    %%[FLUSHING:REST OF JOB (TO END-OF-FILE) WILL BE IGNORED]%%
    
    this happens on a VAXstation II with 9 MB of memory and on a MICROvax
    3500 with 35 MB of memory. We increased WSEXTENT and that helped
    the memory error problem and the paging problem, but not the error
    above.
    
    Any ideas?
    
    Ruth-Ellen Burack

    I think you have to enable DOCUMENT Mode in order to read DOCUMENT
    files into the Previewer.  It's in one of the pulldowns -- it's been so
    many months since I ran the Previewer I can't remember which one.

    re 31.17
    
    I tried setting that switch and it still gives me the same error.
    I can't read .ps rags files that aren't part of a document file
    either.
    
    Ruth-Ellen

    Hi,
    
    So, I am still not able to read in .PS RAGS files into the Previewer.
    Any ideas... 
    
    Ruth-Ellen

I seem to recall that in DOCUMENT version V1.0 or less, there was a problem
with a pair of commands that surround the included image in the PS file that
DOCUMENT produces.  Although I don't remember the exact PostScript command
that were out of order, it went something like this...

...(DOCUMENT produced PostScript)...
SAVE
FOO
(Included image PostScript)
RESTORE
UNFOO
...(more DOCUMENT produced PostScript)...

The problem is that the two commands after the graphic had to be switched
around.  Sorry I can't be more specific.  If you need more info, try asking
in CLOSET::DOCUMENT.

-Mike

I got the following error when trying to us PSviewer on a .PS file that prints
without error on Printserver V2.1:

%%[ Error: undefined; OffendingCommand: lettertray ]%%
%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%

I tried DOCUMENT mode, and got the same error.

Suggestions?  Thanks,
tl

Funny, I just had the same problem this morning with
a file that would print on an LPS40 but not on an LN03R,
for the same reason.  Knowing virtually nothing about
Postscript except that it's a Forth-style programming
language and in ASCII, therefore editable, I edited
the file and searched for "lettertray".  From the
context it was clear that is was involved in selecting
a paper tray, which is irrelevant in the Viewer or an LN03R
with only 1 paper tray anyway.  I commented out the
offending command and the file then printed fine.  Here
is what it was in the document I was printing:

%      statusdict begin
%      pgs 1 eq { lettertray } if
%      pgs 2 eq { legaltray } if
%      pgs 3 eq { a4tray } if
%      pgs 4 eq { b5tray } if
%      pgs 8 eq { 11x17tray } if
%      end

I added the "%"'s which appear to be comment delimiters.

In the past I ran into a similar problem with a file produced
by Interleaf.  It had a similar workaround.

As an aside, it's a shame that we have s/w that produces postscript
files that will not print on "default" paper and work equally on LPS40's
and LN03R's.

Hmmm, couldn't the PSviewer and LN03R modules that create the bitmap from the 
PostScript be modified to ignore commands that can't be executed on that 
hardware type (e.g., set papertray)?

tl

    re .21-.23:
    
    Papertray is a device-specific extension to the PostScript language.
    Most frequently, these kinds of extensions are used only by the device
    handling routines.  In this case, stuff like the printer modules that
    get sent before the actual text of the document.
    
    Use of these extensions in regular text will prevent the system manager
    from doing stuff like sending certain jobs to alternate output trays.
    I don't remember whether you said where the text came from, but
    whatever generated it was not being a good citizen.
    
    As to .23 (wouldn't it be nice if they could ignore commands...). 
    The problem is that extensions might be anything.  We could, I presume,
    add in a few common cases, but in general, they are doing the right
    thing to burp on things that are not standard Postscript.  It is
    easy for you to MAKE them do that, however.  An initial line of
    something like
    
    /papertray {0 pop} def
    
    should do nicely.  (Maybe there is a better way...this one defines
    "papertray" to push 0 on the stack and pop it again.  There may be
    a better noop to use.)
    
    Burns
    

/papertray {} def

is a simpler NOP.  {} is the null executable string...

It wouldn't be reasonable for these things to be ignored.  They have effects
in addition to selecting paper.  (In other words, formally speaking NOP-ing
them is incorrect, though in 99% of the cases you wouldn't see any problem.)
Consider the effect of ignoring a command to select 11x17 paper on an LN03R...

It would be nice for the producer software either not to generate those 
commands, or to put code around them that deals gracefully with their
absence.  I'd offer the DVIPS utility as an example of one that does the latter.

	paul

    
    I don't believe this has been addressed.  How is PostScript
    Previewer accessed?  I'm backing up an individual who installed
    Previewer last week and I now have a user asking how to access
    this application.
    
    Thanks,
    
    Melinda Margetson

    This is an INTERNAL user, right?
    
    Good.
    
    MC DECW$PSVIEWER is the command, I seem to recall.
    
    ���

    
    Yes this is an INTERNAL user.
    
    Melinda
    

    My question is simple:
    
    Is the PostScript previewer going to return to DECwindows for customer
    usage sometime soon?  Are there any 3rd party products that would fit
    this customer requirement? 
    
    Martin
   

    1) No.
    
    2) We have in field test something that could be utilised to provide a
    postcscript viewer. No promises, wait and see. Don't know about 3rd
    party applications.
    
    - ���

    Re .30:
    
    (1)  What is the formal mechanism for us to raise this as a
    product/program issue?  We have a HUGE number of WS sales that are
    hostage to having a Postscipt preview capability.
    
    (2)  Who is the product manager/contact for this product?  If it is the
    "print-only" converter that I have seen references to, it is not going
    to adequate (for us).

	Send your mail to Paul STAR::STEEVES. He's the DECwindows Product 
	Manager..

							mike

    
    I've always wondered -- why was the PS previewer OK on ULTRIX, but
    nixed on VMS?   In a few instances, we've ended up selling ULTRIX
    to otherwise VMS-inclined customers that really wanted PostScript.
    
    		George
    

  I heard it had to do with disagreements over how licenses are tracked.
  Apparantly the way we track ULTRIX licenses met the requirements, while
  they way we track VMS licenses did not.  Of course, I could have heard 
  wrong, too - at least it sounds plausible.

RE: .34

The specific problem was VAXcluster licensing.

--PSW

    Ah -- something like wanting a separate licence for each node
    in the cluster??
    
    Adobe has always had some funky licensing ideas -- they used to
    licence their fonts on a per-physical-printer basis, so that if
    your printer died and was replaced (or if repairing it changed
    it's internal ID) then you needed to buy new fonts.  I *believe*
    this eventually got changed to something more reasonable.
    
    		George

   DECwrite was faced with the same problem, because they
   ship Adobe code with every kit. They've got a setup wherein you     
 can copy a netkit and order a VMS PAK from VTX.

   Could the PS viewer do the same thing?

RE: .37

The problem wasn't distribution of the PSviewer for DEC-internal use.  The
problem was getting agreement on how to do real, paying customer licenses.  I
don't know the details beyond the fact that VAXcluster licensing was a stumbling
block.

--PSW

	Another unsupported question on this viewer.  I am a new DECwindows
	users trying to get the viewer to work correctly.  When I call up 
	a B sized (11x17papertray or Ledger) file, the viewer shuts itself 
	off or logs out or whatever.  The windows go away.  The view will 
	display 8.5x11 files nicely.  The plots work just fine on LPS40.

	Where do I look for error reports?  Any other clues to debugging 
	this problem?

	Oh, this is on VMS 5.1-1, Decwindows version 1, I believe.  I know 
	that's old, but I am tied to it by vendor support (or lack of it) 
	for VMS 5.2.

	Thanks,

	Dave

RE: 31.2
>
>    for unofficial and internal only use, check out the kit at
>    RESOLV""::SYS$KITS:[PUBLIC]SDC_PSVIEWER.SAV, restore it in some directory
>    and then execute some command procedure in there (sorry I forgot what
>    it is, should be real obvious).
>
	The kit is no longer there.  Is it available somewhere else?

	Thanks,	
	Dave

	The CDA Viewer in VMS 5.4 reads and displays Postscript.

							mike