[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

912.0. "V2.4D upgrade breaks LN03Rs: "REAR" papertray" by SHALOT::LANPHEAR (Test the water or turn the tide?) Tue Jun 23 1992 02:42

    Also in the V2.4D upgrade, the LN03.PRA (printer attribute file) now
    contains a control sequence to select the REAR feeder tray.  If you
    happen to have REAR selected (how does that happen, anyway?) and you try
    to print to an LN03R, it generates a nasty PostScriptish error about
    the tray, and doesn't print the document.  Again, the customer didn't
    see this problem in V2.4, but now 'lots' of documents won't print...
    
    Any idea why this changed, and why it wasn't documented?  (or where it
    was documented if it is?)
    
    					Thanks in advance, Dan'l
    
    I'm beginning to think that not very many sites upgraded to V2.4D...
T.RTitleUserPersonal
Name
DateLines
912.1Ask in the WPS-PLUS conferenceIOSG::NEWLANDRichard Newland, IOSG, REO1-D/4ATue Jun 23 1992 04:0410
Questions about WPS-PLUS LN03 Printer Table are best asked in the WPS-PLUS 
conference because the WPS-PLUS developers don't actively follow this 
conference.

If WPS-PLUS documents are being created with a tray setting of REAR this is
probably caused by a user's default WPS-PLUS Print Settings (saved settings
#0) having a tray setting of REAR. 


Richard
912.2Yes, I know, "it's a WPS-PLUS problem".SHALOT::LANPHEARTest the water or turn the tide?Tue Jun 23 1992 19:4815
    Hi Richard,
    
      Thanks for your replies, and yes, I understand you only 'bolt on'
    what they give you, but it's still frustrating when our customer's
    users can't get their work done because our uprgrade has 'helped' them.
    
      I recall the SS 0 fix for this seemingly _same_ problem from the V2.3
    upgrade, but it's still not the right answer.  Upgrades are not
    supposed to break things, or at least not without letting us know first :-).
    
    These notes are more rhetorical, and in warning in case other
    specs run up against the same problems, and don't happen to look in the
    WPS-PLUS conference.
    
    						Regards, Dan'l