Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker.mit.edu!apple!agate!shelby!msi.umn.edu!noc.MR.NET!gacvx2.gac.edu!scott From: scott@mcs-server.gac.edu (Scott Hess) Newsgroups: comp.sys.next Subject: Re: Next docs, printing, nonsense Message-ID: Date: 10 Dec 90 06:16:16 GMT References: <1990Dec10.022935.20133@utstat.uucp> Distribution: na Organization: Gustavus Adolphus College Lines: 33 Nntp-Posting-Host: mcs-server.gac.edu In-reply-to: philip@utstat.uucp's message of 10 Dec 90 02:29:35 GMTLines: 33 In article <1990Dec10.022935.20133@utstat.uucp> philip@utstat.uucp (Philip McDunnough) writes: On another note, does anyone know of a printer driver to any of the HP inkjet printers, especially the Painjet. Printing to an Apple ImageWriter is not my idea of anything wothwhile. Where are the drivers? Right now, you cannot legally print raster images to a printer with more than 150 dpi from a NeXT - it's in the legalize in the license. With NextStep2.0, this limit has been raised to _900_ dpi (really, seriously), so expect those drivers to start appearing soon after 2.0 hits the streets . . . (where soon==(when EricPScott || RobertLin get 2.0 :-)). Also, I really have this beef about the documentation which comes with the NeXT. Or perhaps I should say lack of documentation. I'm not a computer guru, but I didn't appreciate having to rebuild a 330meg HD in a mad quest to try to get rid of a demo program( FrameMaker) after I had installed the version I bought. I have to agree. The 2.0 docs are supposed to be much better than the 1.0 ones - they are supposed to be finished 2.0 docs, not just finished 1.0 docs with unfinished 2.0 extensions. patience to become a systems' programmer. Either this thing turns into a more user friendly system soon( am still waiting for 2.0, 040, floppy) or it'll be sold. How much? Naw, just kidding . . . -- scott hess scott@gac.edu Independent NeXT Developer (Stuart) GAC Undergrad (Horrid. Simply Horrid. I mean the work!) Tried anarchy, once. Found it had too many constraints . . .