Xref: utzoo comp.windows.open-look:1147 comp.lang.postscript:8234 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!usc!snorkelwacker.mit.edu!mit-eddie!uw-beaver!stowe.cs.washington.edu!pauld From: pauld@stowe.cs.washington.edu (Paul Barton-Davis) Newsgroups: comp.windows.open-look,comp.lang.postscript Subject: Re: Update on SPARCprinter/NeWSprint resolution problem Message-ID: <1991Apr8.172751.6077@beaver.cs.washington.edu> Date: 8 Apr 91 17:27:51 GMT References: <41@ftms.UUCP> Sender: news@beaver.cs.washington.edu (USENET News System) Reply-To: pauld@cs.washington.edu (Paul Barton-Davis) Organization: Computer Science & Engineering, U. of Washington, Seattle Lines: 24 In article <41@ftms.UUCP> brown@ftms.UUCP (Vidiot) writes: > >Having a SPARCprinter verses a PostScript printer engine will allow for >improvements without having to change the hardware. I do like the idea >of having the PostScript being software driven instead of hardware driven >and look forward to the improvements. one nit-picking detail - all PostScript systems thus far are software driven. The only different about the Sun system is that the software runs on the host, rather than on a processor installed in the laser engine. If you were using 386/AT systems, there are and have been for some time, a number of these type of systems available. How well they work depends on what you wanted to do with them, but its worth noting that some of the faster PostScript implementations are still done in this way (Birmy, and the YARC/Pipeline implementations being two cases in point). Paul Barton-Davis UW Computer Science Lab ``to shatter tradition makes us feel free'' -- Paul Barton-Davis UW Computer Science Lab ``to shatter tradition makes us feel free''