Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3E10155F.6010106@doe.carleton.ca> Date: Mon, 30 Dec 2002 13:43:59 +0400 From: f User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin AT cygwin DOT com CC: fma AT doe DOT carleton DOT ca Subject: ps2epsi problem Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hello, I'm having trouble using ps2epsi on a PS file that is one page in a multipage PDF file. Works fine if I use ps2epsi on a PS of the whole document, but that creates a single EPS with material from all the pages piled on top of each other. If I use the -sOutputFile=SomeName%d.epsi, it generates the individual pages as EPS but no tiff preview. To get ps2epsi working with the 1-page PS, I did the fix in http://sources.redhat.com/ml/cygwin/2001-08/msg01003.html but it still complains with the same error: > %%[ Error: invalidaccess; OffendingCommand: put ]%% > GNU Ghostscript 7.05: Unrecoverable error, exit code 1 The script differs from the one our solaris 8, since cygwin's gs is 7.05 while our solaris version is 5.10. I tried printing the 1-page PS file on solaris, which works well with ps2epsi on solaris. I downloaded the 1-page PS to cygwin, but it causes > Error: /invalidaccess in --put-- and regurgitates the stack. I even downloaded the ps2epsi script from solaris (it had minor differences), but got the same error. I would like to avoid using the our solaris ps2epsi because it doesn't seem to respect the -sOutputFile=SomeName%d.epsi. So it would be great if I could get this to work on cygwin. Thanks for any suggestions. Fred fma AT doe DOT carleton DOT ca -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/