NetNews Usenet Archive 1992 #30/NN_1992_30.iso/spool/comp/os/mswindo/misc/5624

Text File | 1992-12-21 | 1.7 KB | 39 lines

Newsgroups: comp.os.ms-windows.misc
Path: sparky!uunet!usc!elroy.jpl.nasa.gov!decwrl!deccrl!news.crl.dec.com!dbased.nuo.dec.com!nntpd.lkg.dec.com!nntpd2.cxo.dec.com!nuts2u.enet.dec.com!little
From: [e-mail] (Todd Little)
Subject: Printing a Postscript file
Message-ID: <[e-mail]>
Keywords: Postscript Errors Printing
Sender: [e-mail] (USENET News System)
Organization: Digital Equipment Corporation
Date: Sat, 19 Dec 1992 06:21:06 GMT
Lines: 27


Perhaps some of you more experienced Windows users out there can help
me with a couple of problems I'm having with Windows.  My setup is a
DECpc 433ST running Windows 3.1.

My first problem is I'd like to figure out a way to be able to print
an existing Postscript file without having to leave Windows.  My
printer is an LN03R ScriptPrinter connected to COM2 at 19,200 and uses
XON/XOFF flow control.  I've tried nearly everything from copying to
COM2 using File Manager to the copy and print commands in a virtual
DOS machine window.  If I go through a Windows application, the text
of the Postscript program gets printed.  If I go through anything
else, I either can't get the baud rate right, or I can't get XON/XOFF
flow control working, or both.  Has anyone gotten this to work?

My second problem stems from my using COM1 to be dialed up to systems
much of the time.  What happens is that certain Windows application's
file requestors spit out the following text on COM1:

Return from GetDriveType for drive 3 is
Return from GetDriveType for drive 4 is

Which needless to say is a royal pain.  How do I get rid of these silly
messages from the file requestors for NotePad, Write, CardFile, etc.?

Thanks,
Todd