Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!epb6!envbvs
From: envbvs@epb6.lbl.gov (Brian V. Smith)
Newsgroups: comp.windows.x
Subject: Re: Xqvss, Xwd, Xpr, & pbm problem
Keywords: Xqvss Xwd Xpr pbm
Message-ID: <2116@helios.ee.lbl.gov>
Date: 15 Mar 89 22:37:44 GMT
References: <1824@gmu90x.UUCP>
Sender: usenet@helios.ee.lbl.gov
Reply-To: envbvs@epb6 (Brian V. Smith)
Distribution: na
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 32

In article <1824@gmu90x.UUCP> rauletta@gmu90x.UUCP ( ) writes:
	>I have recently built the R3 release of X11
	>and am having extensive problems with getting Xwd dump
	>files to print using either Xpr or pbm and I was wondering
	>if there was a known solution to this problem.
	>
	>My impression at this point is that the problem may be
	>with Xwd and machine dependencies with the qvss server,
	>though this is only a wild guess on my part, as both
	>parts of Xpr and pbm fail to properly read the dump files.
	>
	>Suggestions, solutions would be most appreciated.
	>For reference I'm running on a diskless Vaxstation 2000
	>with a monochrome VR260 display running Ultrix 2.2.
	>

I noticed the same thing; namely, that xipr, which is a shell
script that just does an 'xwd' into 'bitimp' fails to work.

bitimp complains that "window dump file is in bad format".

I wouldn't think that the problem is any machine dependency with the
qvss server, but a more general bug.

Any help out there?

I have a Vaxstation II running Ultrix 2.3 (monochrome Xqvss).
It also gives the same error message on our 4-plane color vaxstation 2000
running Ultrix 3.0 (Xqdss server).

Brian Smith
bvsmith@lbl.gov