Bad EPS file with Word for Windows version 6.0a???

Thread View: comp.lang.postscript

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by kaikow Thu, 21 Apr 1994 11:12

#9303

Author: kaikow
Date: Thu, 21 Apr 1994 11:12

91 lines
3646 bytes

I have encountered a problem with postscript files generated by version 6.0a
of Word for Windows (WFW). It is reproducible for ALL attempts to COPY an
EPS file to my NEC Silentwriter 95, if the EPS file was created by version
6.0a of WFW.

The problem is that the EPS file prints correctly, however, it is followed
by a blank page, then a page containing only

Offending Command = timeout
Error = nametype:timeout

Stack =

I happened to have an EPS file that I created on 13 Feb 1994 using version
6.0 of WFW that prints correctly without the 2 extra pages. However, when
generating an EPS, using the same source file, with version 6.0a of WFW, 
the 2
extra pages are output.

I have loaded the latest Microsoft postscript driver from ftp.microsoft.com.
Today, I restored the version of epsimp.flt that I was using on 13 Feb 1994,
but it compared (using FC) byte for byte with the version 6.0a epsimp.flt.

Below is the result of FC for the 2 EPS files. IS13346A.EPS is the
13 Feb 1994 file that prints without the extra 2 pages (it was created using
version 6.0 of WFW). ZZZ.EPS is the version that prints the extra 2 pages
(it was created using version 6.0a of WFW).

Note that CHANGE1.DOC And IS13346A.DOC are names for the same file.

Further, I tried wiping out all of version 6.0 and 6.0a and reinstalling
just version 6.0 of WFW. That didn't fix the problem as the installation of
WFW puts files in all sorts of different directories that are shared by
applications so it is not so easy to get a clean version 6.0 WFW to
reproduce the good result of 13 Feb 1994 (of course, I could restore it from
a backup tape, but that has to be a last resort as I then would not have the
benefit of  the bug fixes in version 6.0a and any added bugs in version 
6.0a).

Any ideas on why the error occurs?

Comparing files IS13346A.EPS and \ZZZ.EPS
***** IS13346A.EPS
%%Creator: Windows PSCRIPT
%%Title: Microsoft Word - CHANGES1.DOC
%%BoundingBox: 11 12 600 780
***** \ZZZ.EPS
%%Creator: Windows PSCRIPT
%%Title: Microsoft Word - IS13346A.CHG
%%BoundingBox: 11 12 600 780
***** 

***** IS13346A.EPS
%%EndResource
/SVDoc save def
%%EndProlog
***** \ZZZ.EPS
%%EndResource
%%EndProlog
***** 

***** IS13346A.EPS
ErrHandler
%%EndSetup
***** \ZZZ.EPS
ErrHandler
/fPP true def
%%EndSetup
***** 

***** IS13346A.EPS
%%Trailer
SVDoc restore
end
***** \ZZZ.EPS
%%Trailer
end
***** 

***** IS13346A.EPS
% TrueType font name key:
%    MSTT31c175 = 2c8fDTimes New RomanF0000002a000001900000
%    MSTT31c18e = 2c8fDSymbolF0000002a000001900000
%%DocumentSuppliedResources: procset Win35Dict 3 1
***** \ZZZ.EPS
% TrueType font name key:
%    MSTT31c181 = 3467DTimes New RomanF0000002a000001900000
%    MSTT31c18e = 3467DSymbolF0000002a000001900000
%%DocumentSuppliedResources: procset Win35Dict 3 1
*****

Re: Bad EPS file with Word for Windows version 6.0a???

#9304

Author: Andrew Klossner
Date: Thu, 21 Apr 1994 15:04

36 lines
2488 bytes

	"I have encountered a problem with postscript files generated
	by version 6.0a of Word for Windows (WFW). It is reproducible
	for ALL attempts to COPY an EPS file to my NEC Silentwriter 95,
	if the EPS file was created by version 6.0a of WFW."

Note that EPS files are meant to be included within PostScript files.
They are not themselves meant to be printable.  Sometimes they are,
sometimes they aren't.  Output from a Windows ap, sent via the
PostScript driver with "print to EPS file" checked, generally is.

	"The problem is that the EPS file prints correctly, however, it
	is followed by a blank page, then a page containing only
	Offending Command = timeout
	Error = nametype:timeout
	Stack ="

When you send a PostScript file to a printer over a serial or parallel
(Centronic) line, you must follow that file with control-D.  If you
don't, the printer has no way of knowing that the job has finished.
Eventually it declares an "iotimeout" (too much time has passed since
the last byte of input) and terminates the job with an error.  Because
your printer has enabled an error handler, you get the page you
describe.

This doesn't explain why your old EPS file didn't cause the error.
Your diff's show nothing that would account for this.  My guesses are
that either you printed the old EPS with the error handler disabled, or
there's a control-D lurking somewhere.

I don't think that reverting to the previous version of WfW is
necessary.  Just append control-D when you print the file: make a file
containing that single byte, and

	COPY/B myfile.EPS+CTLD.EPS LPT1:

  -=- Andrew Klossner  (andrew@frip.wv.tek.com)

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads