From: CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 25-JUL-1989 02:48 To: MRGATE::"ARISIA::EVERHART" Subj: Re: local prntrs, WordPerf queues, & Moria Received: From KL.SRI.COM by CRVAX.SRI.COM with TCP; Mon, 24 JUL 89 22:36:56 PDT Received: from ucbvax.Berkeley.EDU by KL.SRI.COM with TCP; Mon, 24 Jul 89 22:08:18 PDT Received: by ucbvax.Berkeley.EDU (5.61/1.37) id AA29870; Mon, 24 Jul 89 22:03:15 -0700 Received: from USENET by ucbvax.Berkeley.EDU with netnews for info-vax@kl.sri.com (info-vax@kl.sri.com) (contact usenet@ucbvax.Berkeley.EDU if you have questions) Date: 24 Jul 89 14:46:05 GMT From: uhccux!munnari.oz.au!comp.vuw.ac.nz!dsiramd!windy!gpwd!gpwrmdh@ames.arc.nasa.gov (Martin D. Hunt) Organization: Government Printing Office, Wellington, New Zealand Subject: Re: local prntrs, WordPerf queues, & Moria Message-Id: <62@gp.govt.nz> References: <89Jul5.141317edt.5594@gpu.utcs.utoronto.ca> Sender: info-vax-request@kl.sri.com To: info-vax@kl.sri.com In article <89Jul5.141317edt.5594@gpu.utcs.utoronto.ca>, CAMPBELL@UTOROCI.BITNET writes: >> Don Stokes (Government Printing Office) Wrote: >>WordPerfect does have it's own symbiont - a fact that is not outlined >>adequately in the installation notes, and caused no little grief when it >>didn't install properly. Rather than just having a new symbiont, it >>sets up a logical name in LNM$GROUP_000001 called SMBSRVSHR, which points >>to WP's own version of the print symbiont shareable image - behaviour >>which in my opinion is quite anti-social, as most print symbionts use >>that image (ie DEC's *and* third-party symbionts). > > Now, I'm getting downright enlighted by the comments on WordPerfect's sharable > symbiont image. Is THAT how they use /char=127 to trick my symbionts into > doing wordperfect document formatting? We've been surmising that the queue > /char stuff was some kind of semi-supported call-out hook. It would be > interesting to see a description of how it failed to install, and what you > learnt fixing it. > The original posting was some time ago, but I notice Don's comments in amongst the message. The following should clarify things: The default word perfect action is to use its own symbiont - a fact which rather shocked us when we found out. It was quite a nuisance having to always make sure that characteristic 127 was set on the Wordperfect queues. We want our print queues to be general purpose, and not just dedicated to WordPerfect. What appears to happen is that the symbiont checks to see if char 127 was set when the print job was submitted, and if so does the necessary code translations. I.e., the original raw word processing file is submitted to the queue, and the symbiont actually does the translation, rather than translating the document before submitting it to the queue. The anti-social behaviour was noticed next reboot because of a bug in our system startup procedure. The logical pointing to the WP directory was missing, so the print symbiont sharable could not be found - it took a while to track down the problem because of the anti-social way it had substituted its own symbiont. Fortunately, this behaviour can be over-ridden. First, when installing the product, tell it that you do NOT want symbiont integration. Alternatively, edit SYS$MANAGER:WPCORP_QUEUE_STARTUP.COM and put an EXIT near the top of it. Modify all your queue definitions using WPC/PMU so that all queues are set up as "Non-WP VMS Queues" rather than "VMS Queue" - this causes the translation from WP to printer format to be performed BEFORE they are printed to the queue. In the queue definition listing this will show as "Spool Image File" rather than "Queue" - you will need to look at each individual queue to find this. Hope the above helps. -- -------------------------------------------------------------------------------- Martin D. Hunt Government Printing Office Wellington New Zealand USEnet address : MARTINH@GP.GOVT.NZ PSI address : PSI%0530147000028::MARTINH --------------------------------------------------------------------------------