[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

1484.0. "Mail postscript file from v3.0 to v2.4 and printin under v2.4" by SNOC01::IPSSG_JW () Wed Sep 23 1992 06:52

    In SNO our current version of ALL-IN-1 is V2.4. We have a user whom
    operates his ALL-IN-1 account from a windows terminal. Recently that
    user has received from a V3.0 ALL-IN-1 user a postscript file .
    
    The user under the EDT editor reads the mail message, and if sent from
    a V2.4 user would see postcript commands after the ALL-IN-1 header.
    
    But the V2.4 user trying to read the mail sent from the V3.0 user get
    the message "text not supported by this terminal type !".
    
    Filling the attachment and printing to a postscript queue within
    ALL-IN-1 (If received postscript file from another V2.4 user) prints ok, 
    but the V3.0 file received failed to print.	
    
    If the document is sent to VMS and printed all is OK !
    
    We have users locked to a menu system and subsequently cannot get DCL
    access. Consequently they will be sent postscript files from V2.4 and 
    V3.0 and will require them to be printed.
    
    Could anyone please advise how a postscript file sent from V3.0 to V2.4
    ALL-IN-1 be filled and printed within V2.4 ???
    
    Thanks in advance !
    Jeff
    IS Support Group.

T.R	Title	User	Personal Name	Date	Lines
1484.1	hah	BIGUN::ANDERSON	The Unbearable Fuzziness of Marketing	`Wed Sep 23 1992 08:47`	5
	jeff I logged a workbuster a few months ago (that I NEVER got a reply on) to modify ALL-IN-1 to make postscript document handling really work. I wonder if ALL-IN-1 will ever have an object-oriented filing cabinet...
1484.2	Update handling	IOSG::NEWLAND	Richard Newland, IOSG, REO1-D/4A	`Wed Sep 23 1992 10:37`	9
	-------------------------------------------------------------------------------- If you select one of these messages on the V2.4 system and do FULLDB what are DSAB and Handling fields set to? If the Handling is not 'PS' try changing it to 'PS'. Richard
1484.3	Have Tried XXXX.2 ?	SNOC01::IPSSG_JW		`Thu Sep 24 1992 03:52`	38
	Re the last entry ! Under the EDT editor environment I pulled up the document in question and typed in the FULLDB and got the following, Folder: TEST (Number: 043589) File: [.MSG]ZUIKI5COM.FGN DSAB: FOREIGN Title: assist overview (PS) Type: DOCUMENT Author: John ONeill Handling: PS Keywords: Created: 24-Sep-1992 12:42pm Modified: 24-Sep-1992 12:42pm Enter new values and press RETURN I then tried to print the message to a known postscript printer and got the following message , S Send Messages %OA-I-LASTLINE, Printer destination SNO_LPS40_1 PS can not print a PostScri pt document Anybodys constructive advise would be greatly appreciated in assisting with the problem mentioned. Jeff IP SUpport Group
1484.4	Printing Mailed Postscript Files from within ALL-IN-1	SNOC01::IPSSG_JW		`Thu Sep 24 1992 07:39`	31
	Thanks for the constructive help in XXXX.2 above but research has found a solution. For the curious. Firstly see note 487.* and 722.*, Further to these notes please print of the following two illuminating TIMA articles, "'Unsupported Text' Message When Printing POSTSCRIPT Attachement Sent Remote" & "How to Setup Printer in ALL-IN-1 to print DDIF and Postscript Documents in V2.4" The summary is as follows. The V2.4 Message router sometimes treats the attached postscript files as foreign and changes the file extension to '.FGN' and the DSAB field to foreign. These are unknown to ALL-IN-1 and the first article shows how to reset the DSAB field to PS and enable printing from within ALL-IN-1. The second TIMA article assists in confirming printer set up to enable printing from within ALL-IN-1. Note .2 does not help unfortunately, thanks for your assistance anyway. I hope this helps someone out there in the ether ! Regards Jeff IS Support Group
1484.5	Re: .3	IOSG::NEWLAND	Richard Newland, IOSG, REO1-D/4A	`Thu Sep 24 1992 10:14`	17
	Re: .3 > I then tried to print the message to a known postscript printer and got > the following message , > > %OA-I-LASTLINE, Printer destination SNO_LPS40_1 PS can not print a > PostScript document The error message suggests that the document has been recognised as PostScript but the SNO_LPS40_1 PS Printer destination has not been defined to ALL-IN-1 as being able to handle PostScript. What is the Site Printer information for the SNO_LPS40_1 PS destination? Richard
1484.6	hah?	IOSG::SHOVE	Dave Shove -- REO-D/3C	`Thu Sep 24 1992 11:02`	10
	RE: .1 What's a "workbuster"? .0 refers to version 2.4 The current version is v3.0, in which PostScript handling is much improved (as longas PostScript printers are set up as such). Dave.
1484.7	Postscript Printing on V2.4 workaround	SNOC01::IPSSG_JW		`Thu Sep 24 1992 23:40`	14
	Re:.5 The printer definition was incorrect and modified and all prints out ok. Please see Tima articles mentioned in my previous note as they elaborate further. We will be going to V3.0 sometime early next year after a lot of planning, (a nontrivial upgrade !). In the interim thanks for everyones constructive suggestions. The problem has been solved ! Jeff IS Support Group.