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

Conference iosg::all-in-1_v30

Title:	OLD ALL-IN-1 (tm) Support Conference
Notice:	Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:	IOSG::PYE

Created:	Thu Jan 30 1992
Last Modified:	Tue Jan 23 1996
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4343
Total number of notes:	18308

3580.0. "PS output from Scratchpad print?" by KERNEL::LOAT (Stop throwing those bloody spears!) Wed Nov 24 1993 19:15

    
    VMS 5.5-2 ALL-IN-1 3.0
    
    
    A customer has found a bit of a problem with their copy of the PS
    printer destination/printer tables when printing from the scratch-pad,
    or corporate directory.
    
    
    They used WP PT option to make a copy of the PS.PRA file, and call it
    something different. They made some minor changes to the table, and
    they created a new printer destination to call their new printer table.
    
    Printing from the scratch-pad menu, if they use the printer type of PS,
    it works okay, printing to their PS generic queue. If they use their
    own PS printer type, they get an error. A closer look at the file
    reveals why.
    
    When they use the standard PS printer type, they get a Postscript file,
    as expected, but when they use their own PS printer type, they get a
    text file output, which is an exact copy of whats in the scratch pad,
    no PS code, not escape sequences, just normal text.
    
    I've reproduced this problem here, just by taking a copy of the PS.PRA
    file, and using that one, with absolutely no changes made to the .PRS
    file.
    
    Is there a problem with taking copies of the PS.PRA file, and using
    it in ALL-IN-1? Is it coded to look for PS.PRA?
    
    Thanx
    
    Steve.

T.R Title User Personal
Name Date Lines

3580.1 Known problem IOSG::NEWLAND Richard Newland, IOSG, REO2-G/L2 Wed Nov 24 1993 19:39 9

T.R	Title	User	Personal Name	Date	Lines
3580.1	Known problem	IOSG::NEWLAND	Richard Newland, IOSG, REO2-G/L2	`Wed Nov 24 1993 19:39`	9
	This is a known problem. It is caused by the print sub-system not properly distinguishing between the name of the Print Style and the name of the WPS-PLUS Printer Table during the special checks for formatting to PostScript. The Print Style and WPS-PLUS Printer Table both have to be called 'PS' for everything to work correctly. Richard

This is a known problem.  It is caused by the print sub-system not properly
distinguishing between the name of the Print Style and the name of the
WPS-PLUS Printer Table during the special checks for formatting to
PostScript.  The Print Style and WPS-PLUS Printer Table both have to be
called 'PS' for everything to work correctly.


Richard