Almut Behrens wrote:
OK, seriously, I'm getting the impression that, for whatever reason,
your printer somehow got inadvertendly misconfigured to no longer use
ESP technology.
This impression of yours turns out to be the entire solution to the
problem. Somehow the setting had been changed. I
On Sat, Jun 11, 2005 at 08:12:36PM -0500, Jim Hall wrote:
> Almut Behrens wrote:
> >On Fri, Jun 10, 2005 at 10:47:14PM -0500, Jim Hall wrote:
> >><>setpagedevice
> >>%!PS-Adobe-3.0
> >>%%Pages: (atend)
> >>%%BoundingB
> >
> >That "<>setpagedevice" is not supposed to occur
> >in that position, i.e.
Almut Behrens wrote:
On Fri, Jun 10, 2005 at 10:47:14PM -0500, Jim Hall wrote:
No matter what I do, this prints on the first page. Each line starts at
the end of the previous one (meaning they're staggered).
<>setpagedevice
%!PS-Adobe-3.0
%%Pages: (atend)
%%BoundingB
That "<>setpagedevice"
On Fri, Jun 10, 2005 at 10:47:14PM -0500, Jim Hall wrote:
>
> No matter what I do, this prints on the first page. Each line starts at
> the end of the previous one (meaning they're staggered).
>
> <>setpagedevice
> %!PS-Adobe-3.0
> %%Pages: (atend)
> %%BoundingB
That "<>setpagedevice" is not su
Nicos Gollan wrote:
On Wednesday June 8 2005 20:50, Jim Hall wrote:
Because printing in Linux and I are not on the best of terms, I sort of
expected to see something more CUPS related. I say that because in the
CUPS setup I've done so far I didn't see any lpr commands.
So there we have a(not
>>What's next?
> Almut Behrens wrote:
Personally, I'd make Firefox "print to file", and then take a closer
look at the resulting PostScript file. First thing to check is whether
you can view that file using gs or gv. In case that works, the problem
might be with some incorrect device specific
On Wednesday June 8 2005 20:50, Jim Hall wrote:
> Because printing in Linux and I are not on the best of terms, I sort of
> expected to see something more CUPS related. I say that because in the
> CUPS setup I've done so far I didn't see any lpr commands.
So there we have a(nother) potential culpr
On Wed, Jun 08, 2005 at 01:50:57PM -0500, Jim Hall wrote:
> Per the above info I removed xprint, which also took xprt-xprintorg,
> xprint-common, and x-window-system. Nothing seems to have blown up. :)
>
> Still have the same error at the printer. In Firefox, the only printer
> listed is now "Po
Nicos Gollan wrote:
On Saturday June 4 2005 03:28, Jim Hall wrote:
Results of suggestions.
Tried the Postscript entry; same bad result.
Looked for all pkgs related to xprint. Found: xprt-xprintorg, xprint,
xprint-common. When I tried to remove them, that would also remove
x-window-system! That
On Saturday June 4 2005 03:28, Jim Hall wrote:
> Results of suggestions.
> Tried the Postscript entry; same bad result.
> Looked for all pkgs related to xprint. Found: xprt-xprintorg, xprint,
> xprint-common. When I tried to remove them, that would also remove
> x-window-system! That seems like xpr
Nicos Gollan wrote:
On Friday June 3 2005 04:40, Jim Hall wrote:
Web site page in Firefox. Go to File -> Print -> dialog box. Click
"print" button: page is sent to printer, first page is a PS error, lots
of blank pages follow.
The printer is listed as: QMS 1660@:64.
This looks like you're us
On Friday June 3 2005 04:40, Jim Hall wrote:
> Web site page in Firefox. Go to File -> Print -> dialog box. Click
> "print" button: page is sent to printer, first page is a PS error, lots
> of blank pages follow.
> The printer is listed as: QMS 1660@:64.
This looks like you're using xprint to prin
Sarge system running samba and cups. All computers in lab print to a
printer attached to a Windoze 98 system.
All print test pages print as expected.
Gedit document. Go to File -> Print -> dialog box. Click "print" button:
document prints as expected.
The printer is listed as: QMS 1660.
Web
13 matches
Mail list logo