Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!ut-emx!dll From: dll@ut-emx.uucp (Don Loflin) Newsgroups: comp.windows.ms Subject: Re: Printing PostScript to a File: ^D problem? Message-ID: <43757@ut-emx.uucp> Date: 5 Feb 91 17:19:20 GMT References: <1991Jan21.181243.6378@amd.com> <1991Jan31.172019.4248@csc.anu.edu.au> Organization: The University of Texas at Austin; Austin, Texas Lines: 36 In article <1991Jan31.172019.4248@csc.anu.edu.au> pwo900@csc.anu.edu.au writes: >In article <1991Jan21.181243.6378@amd.com>, indra@brahms.amd.com (Indra Singhal) writes: >> I normally print my documents to a file, carry the floppy to work and >> shoot the postscript out to a printer. >> >> All documents that I generate postscript for from Windows, has a leading >> Ctrl-D character. This 1st character blows away the printers I sent the >> file to with the: binary file encountered error. >> >> So far I have editted the file to delete the 1st character and then all >> works well... anyone outthere who has a better solution? > >I have a similar problem. I have even tried the PSCRIPT.DRV upgrade available >through cica.cica.indiana.edu, but with the same results. > >Does anyone know of a patch to remove the troublesome ^D?> > There is a way around the Ctrl-D problem, which will also let you send jobs directly to a PostScript printer on an 'unsupported' (by Windows) network. Go into Printer Setup, select your postscript printer, then click on Options. In the "Print To" box, select Encapsulated PostScript. For the file, use \dev\lpt1 (or whatever lpt port you're using). The \dev part is DOS's pseudo-directory for devices. Windows will use DOS to send the job, and there will be no ^D's since it's EPS. I use this trick to spool jobs to our LW ntx over LocalTalk from WfW. Of course, you could always save to a file, then 'copy file lpt1', if you are bringing a disk from home. The main thing is to use EPS, not the 'FILE:' device. ------- Don Loflin dll@emx.utexas.edu Microcomputer Technologies Computation Center UT Austin