jdb%arbortext@UMIX.CC.UMICH.EDU (09/17/87)
> We have two programs which send output to LaserWriter via PC Network. > Specifically, Microsoft Word, and Dvilaser from Textset (now a > different name?) Yes -- the name is now ArborText, Inc. The street address has also changed to: 535 West William, Ann Arbor, MI 48103. We can still be reached at (313) 996--3566, and ``PO BOX 7993 / 48107'' is the same as well. > Both store permanent changes into virtual memory which stay until > power-down. ... The VM of the original LaserWriter is too small > for keeping both in memory without ``VMerror''. > ... is there any way to flush VM ... without losing control ? I think your best bet is to reconfigure MS Word and DVILASER so that they can coexist without causing the ``VMerror''. If you can download both the Microsoft prolog file as well as ours without an error (ie, the VMerror occurs only when an actual document comes through), you can set the ``memoryavailable'' option in file ...\dvilaser\dvips.opt to a lower value. This should allow you to print TeX documents even if Microsoft's stuff is loaded. If you get the VMerror message when trying to preload both prolog files simultaneously, or you still can't get MS Word documents to print using the above method, you still have some recourse. First of all, create a file called ``vmstatus.ps'' containing this: %! vmstatus.ps: useful for determinig available PostScript memory /tempstr 64 string def /PrintInt {tempstr cvs print} def /PrintLn {(\n) print flush} def (Current VM status - ) print vmstatus 3 copy PrintInt (\(total\), ) print PrintInt (\(used\), ) print pop exch sub PrintInt (\(remaining\), ) print PrintInt (\(level\)) print PrintLn ^D If you send this file to the printer with the SPR program, you should be able to determine just how much memory you have available. Edit the file ...\dvips\psload.tex and configure it to load fewer fonts than it normally does -- these fonts are also saved in permanent memory. Run it through TeX and DVILASER/PS, using the option ``download all permanent prolog''. This will make the prolog file (ie, psload.ps) smaller. See if this helps. (Don't forget to change ...\dvilaser\dvips.fnt so it matches whatever configuration you install in ...\dvips\psload.tex). Finally, it is possible to use DVILASER/PS without having the prolog file downloaded. (Note: our prolog file contains both macros and fonts). Use must use a special option when running DVILASER/PS, which can be put into the file ...\dvilaser\dvips.opt file: ``download all prolog'' Try this and see what happens. John Buhrer ArborText customer support staff uunet!umix!arbortext!tech_support