home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.ms-windows.misc:2277 comp.periphs.printers:2449
- Newsgroups: comp.os.ms-windows.misc,comp.periphs.printers
- Path: sparky!uunet!wupost!sdd.hp.com!usc!sol.ctr.columbia.edu!destroyer!ubc-cs!unixg.ubc.ca!kakwa.ucs.ualberta.ca!acs.ucalgary.ca!honte.uleth.ca!hg.uleth.ca!BUCHIGNANI
- From: buchignani@hg.uleth.ca
- Subject: Re: Problem with Postscript Driver (Win 3.1)
- Message-ID: <1992Aug23.195335.16080@honte.uleth.ca>
- Sender: news@honte.uleth.ca (News System)
- Reply-To: buchignani@hg.uleth.ca
- Organization: University of Lethbridge
- References: <BtAAJx.G0D@knot.ccs.queensu.ca>
- Date: Sun, 23 Aug 1992 19:53:35 GMT
- Lines: 12
-
- Didn't a specific printer definition come with your NEC printer?
-
- Did you try the suggested test to make sure that the printer
- and computer were actually talking to each other, windows notwithstanding?
-
- I have an NEC Model 95 Silentwriter (also postscript), and it
- runs fine under windows--both in postscript and HP mode.
-
- On windows, check which port you are connected to. Check that
- the timeout on the printer is not too short. The standard
- postscript driver that comes with windows should in fact work
- fine.
-