[27264] in Athena Bugs
Re: hexagons go awry on w20color
daemon@ATHENA.MIT.EDU (John Hawkinson)
Tue Dec 16 22:24:35 2008
Date: Tue, 16 Dec 2008 22:24:20 -0500
From: John Hawkinson <jhawk@mit.edu>
To: Jonathan Reed <jdreed@mit.edu>
Message-ID: <20081217032420.GV29687@multics.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <AFD2D0C4-8F79-428E-96B3-1AAE32E548FC@mit.edu>
X-Spam-Flag: NO
X-Spam-Score: 0.00
Cc: bugs@mit.edu
Errors-To: bugs-bounces@mit.edu
Jonathan Reed <jdreed@MIT.EDU> wrote on Tue, 16 Dec 2008
at 19:11:33 -0500 in <AFD2D0C4-8F79-428E-96B3-1AAE32E548FC@mit.edu>:
> [bug-print dropped, because I sent them mail about this last week]
the hexagons, or w20color in general?
> The other major problem I discovered was that PDFs submitted from Acroread
> to the queue w20color2 only print the header page, and nothing else. (The
> printer insists that that it has nothing left to print.)
Wow. I did see someone who had this problem, and we printed it from
one of Copytech's Macs. Surprisingly, the copytech staff woman
(Danita) assured me that this was not ok and a serious breach of the
Athena rules to print from a non-athena machine to the athena
printer. I had a call into John Guy to ask what was up with that,
haven't heard back from him. [any clue what this is about?]
But we just saved as a postcript from Adobe Reader and spooled it
using the printer's web interface.
Oh wait, actually, ours failed on the regular queue, not the duplex queue.
Did you try that? (Also, did you try -Zduplex?)
> However, prepending the following PostScript to the file:
>
> %%BeginFeature *Duplex True
> << /Duplex true >> setpagedevice
> %%EndFeature
>
> And sending it directly to raw@w20color.mit.edu works just fine. I found
> this baffling, as I thought that's what the duplex queues did.
Well, it's missing a %!PS-Adobe-3.0... actually, I'd tend to think
the duplex queues use the postscript level 2 syntax (they're
old enough). Maybe
true statusdict /setduplexmode get exec
or something?
> I suspect the printer has far more problems with PostScript. Perhaps
> someone who speaks PostScript would be willing to craft a test document or
> a series of test documents to attempt to figure out what works and what
> doesn't.
Huh. I must say, I've only had good things to say about it previously.
It gives pretty nice quality printouts, it's nice and speedy, has great
front-panel help, and I had no trouble correcting a clogged jet by
following the front-panel instructions. The only thing I didn't
like is the front-panel warning light isn't visible from across the room.
I'll see what I can do next week.
--jhawk