Successor to apsfilter.
jo...@wexfordpress.com
programs I use regularly, including Kmail, did not communicate
properly with Cups. So a went back to
lprng.
This caused a further problem. I have two printers, both parallel port
type, that work through
an A/B switch. The Ricoh printer, a Postscript 3 compatible laser, is
not a problem. But
The Epson Stylus Color 880 ink jet needs a special driver. I turned
to apsfilter to configure this printer. The current driver pips/sc880
doesn't work and the Apsfilter project seems to be moribund. There are
no posts in the archives there since 2004.
I need a way to configure something, Cups or Lprng or a player to be
named later, so that I can use both printers and use them with all or
most all of my programs.
John Culleton
Dan C
Haven't we already been through this, ad nauseum?
Use CUPS. Install the proper PPD file for your printer. Done.
--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
"Bother!" said Pooh, as he garotted another passing Liberal.
Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/
jo...@wexfordpress.com
The proper ppd file won't help with the fact that Cups won't work with
Kmail.
JC
Aaron W. Hsu
>The proper ppd file won't help with the fact that Cups won't work with
>Kmail.
If KMail can support lpr, then there is no reason why it can't support
Cups. It might not support it in the normal way that most applications
do, but you should be able to print via a command such as lpr, which is
what you end up doing with lprng. That should work fine.
Aaron W. Hsu
Res
On Sun, 15 Nov 2009, jo...@wexfordpress.com wrote:
> The proper ppd file won't help with the fact that Cups won't work with
> Kmail.
--
Res
"What does Windows have that Linux doesn't?" - One hell of a lot of bugs!
Peter Chant
>> The proper ppd file won't help with the fact that Cups won't work with
>> Kmail.
>
Replying the Res's post as John hits my kill filter for some reason.
Kmail works fine here with cups with no special effort. In what way does it
not work?
Lew Pitcher
>> When I changed to Slack 13 I first installed Cups. However
>> several programs I use regularly, including Kmail, did not
>> communicate properly with Cups. So a went back to lprng.
Linux is, just as unix always was, a complete failure when it comes
to printers. You can easily spend more time fidding with printer
settings than everything else combined, and, at the end of the day,
you're still going to fail because half of the printers out there,
including ALL the economical printers, will never work with linux.
The drivers just don't exist, and never will exist, so you are
kicking a dead horse.
Always have a windows standalone, or a dual boot system, because the
printer will ALWAYS work automagically on a windows installation.
Always. And if it doesn't work on Windows, it's your fault.
What's more, the graphics programs and wordprocessors available to
windows are vastly superior to anything that will ever be available
to linux/unix.
Gimp? Openoffice.org?
Don't make me puke.
Linux is based on a hopelessly archaic principle of piping ascii
text.
Pull your heads out of your asses. Pull them out now and wipe the
shit off your mouths.
Lew Pitcher
--
Master Codewright & JOAT-in-training | Former Linux User
Official Website -->> http://lewpitcher.ca/
Something to look at: -->> http://www.emusclemag.com/
Lonely in Brampton? -->> http://gaypros.meetup.com/cities/ca/on/brampton/
Peel HIV/AIDS Network -->> http://www.phan.ca/home.html
Lew Pitcher
> Res wrote:
>
>>> The proper ppd file won't help with the fact that Cups won't work with
>>> Kmail.
>>
>
> Replying the Res's post as John hits my kill filter for some reason.
>
> Kmail works fine here with cups with no special effort. In what way does it
> not work?
You are a liar and a zealot and as such, the very worst enemy that
linux has.
Little shits like you, who pretend everything is rosy, should be
dangled off the top of a high-rise somewhere so that the shit will
run down over your face before you are let go.
Res
keeps on crying coz u lost your domain because you by your own admission
ya fucked up, nobody cares about you, or is that it? you are so distressed
that nobody has taken pity on you or gives a fuck whether you breathe the
same air as us or not (however preferably the later)
--
Joost Kremers
> Use CUPS. Install the proper PPD file for your printer. Done.
not necessarily. my printer (samsung ml-2510) doesn't work with the ppd file
cups suggests. i have to install some additional piece of software (splix) to
get it to work with cups.
--
Joost Kremers joostk...@yahoo.com
Selbst in die Unterwelt dringt durch Spalten Licht
EN:SiS(9)
Lew Pitcher
Lew Pitcher
(jo...@wexfordpress.com) wrote:
> When I changed to Slack 13 I first installed Cups. However several
> programs I use regularly, including Kmail, did not communicate
> properly with Cups.
I don't know about Slackware 13 (which uses the much-rewritten KDE 4), but
in Slackware 12.* with KDE 3, kmail works properly with CUPS. I can't see
the KDE development team (or Pat V, for that matter) releasing software
that doesn't work at it's basic functionality; are you sure that you've
properly configured cups and kmail?
> So a went back to lprng.
>
> This caused a further problem. I have two printers, both parallel port
> type, that work through
> an A/B switch.
Ewe! 2ndary printer port cards only cost about $10. Buy one and install
it. /Forget/ the A/B switch; it only confuses everything.
> The Ricoh printer, a Postscript 3 compatible laser, is not a problem. But
> The Epson Stylus Color 880 ink jet needs a special driver. I turned
> to apsfilter to configure this printer. The current driver pips/sc880
> doesn't work and the Apsfilter project seems to be moribund. There are
> no posts in the archives there since 2004.
Which explains why Slackware deprecates apsfilter.
> I need a way to configure something, Cups or Lprng or a player to be
> named later, so that I can use both printers and use them with all or
> most all of my programs.
As I said, install a printer port card ($10) and lose the A/B switch.
That'll give you /both/ printers available all the time.
Properly install CUPS (remove lprng, and don't reinstall it), and get the
proper PPD files for your two printers. A generic postscript PPD should
work for the Ricoh printer, and GIMP-PRINT will do the task for the Epson
Stylus Color 880 (see
http://www.openprinting.org/show_printer.cgi?recnum=Epson-Stylus_Color_880)
Ensure that your KDE environment is set up properly. Check the KDE printer
configuration and management tool for the proper setup. Make sure that your
user permissions are set properly (i.e. both printers are owned by the 'lp'
group).
That should be it.
--
Lew Pitcher
Master Codewright & JOAT-in-training | Registered Linux User #112576
Me: http://pitcher.digitalfreehold.ca/ | Just Linux: http://justlinux.ca/
---------- Slackware - Because I know what I'm doing. ------
Aaron W. Hsu
>The drivers just don't exist, and never will exist, so you are
>kicking a dead horse.
>Always have a windows standalone, or a dual boot system, because the
>printer will ALWAYS work automagically on a windows installation.
Oh please. What utter nonsense.
Aaron W. Hsu
Martin Schmitz
>> Kmail works fine here with cups with no special effort. In what way
>> does it not work?
>
> You are a liar and a zealot and as such, the very worst enemy that
> linux has.
KMail works perfektly well with cups with no special effort.
Martin
Sylvain Robitaille
obvious attempt to misrepresent Lew Pitcher, wrote:
> Linux is, just as unix always was, a complete failure when it comes
> to printers. ...
Not that it matters to this discussion, but I've managed printing with
both commercial Unix (DEC/Compaq/HP/OSF-1/Tru64-Unix) and with Linux,
collectively now for about 12 years. I won't claim that it's always
been the easist aspect of system administration, but it has definitely
improved, and most certainly has not been a "complete failure" at any
time. One person's inability to work with specific software does not
necessarily reflect on the quality of said software.
> ... half of the printers out there, including ALL the economical
> printers, will never work with linux.
This definitely has not been my experience, though I've mostly used HP
printers with Linux (and a very portable Canon inkjet, with pretty much
no trouble). What's mostly lacking is vendor support and appropriate
documentation, but this should not be misinterpretted to mean the
functionality "can not" or "will never" work. The number of printer
models I've tried is relatively small, but in practice it comes down to
locating suitable support files for those models, and configuring the
printer server software to use those.
> ...the printer will ALWAYS work automagically on a windows
> installation.
As a matter of fact, this also turns out to be incorrect, as setting up
a printer in Windows almost always requires installing vendor-supplied
software ("driver") for the printer. That isn't automagic, and the only
real difference from Linux is that the printer vendors are prepared to
provide that software for Windows but not for Linux.
> ... Former Linux User
Oh good; so you won't be bothering us any longer ...
--
----------------------------------------------------------------------
Sylvain Robitaille s...@encs.concordia.ca
Systems analyst / AITS Concordia University
Faculty of Engineering and Computer Science Montreal, Quebec, Canada
----------------------------------------------------------------------
Sylvain Robitaille
> When I changed to Slack 13 I first installed Cups. However several
> programs I use regularly, including Kmail, did not communicate
> properly with Cups. So a went back to lprng.
I think that you've gotten some very good advice for this, that you
should try:
- remove lprng and reinstall CUPS (note that lprng is also reasonably
good software; I met the author way back when it was still new, and
based on that meeting I'm inclined to believe it's well written and
likely works well in most basic environments; I also found that it's
much more complicated to setup than it likely needs to be, but I came
at it from a BSD lpr background; my sense then was that sysadmins
coming from a System-V printing background likely found lprng to be
a notable improvement). The point here is not to criticize lprng,
but rather to emphasize that you'll likely reach the goal you're
after more easily with CUPS (and that includes being able to print
from your mail software as easily as any other software).
- eliminate, by whatever means you can, the hardware printer switch.
That's very likely part of the problem you're having, since you now
have a printer daemon expecting two different printers to be attached
to the same hardware port simultaneously. Linux isn't DOS. With DOS
this sort of thing worked because each application was configured
with appropriate printer drivers and you told the application which
driver to use at print time. In Linux (as in other modern operating
systems), the system is managing the printer(s), as a resource, to be
used by any application. You really should have one printer attached
to any single hardware port. That means you might have a printer on
each of two computers, or obtain an add-on parallel port card for your
system to attach the other printer to. Go with which ever approach
you think will work best, then see what you can get on eBay for the
A/B switch (but don't use it to switch between printers anymore).
- your difficulty to print via CUPS from Kmail is a separate issue;
Deal with that in a separate thread where you clearly describe the
problem and symptoms. Folks will certainly provide help with that,
but there's value in separating the general "printing to one of two
printers" issue from the specific "printing from Kmail is failing"
issue.
I would add:
- be patient, both with these issues, and with people's responses.
Don't try to resolve things too quickly. Work on one problem at
a time and work through suggestions in your mind and be sure you
understand them before you attempt them on your computer.
I hope this helps ...
Lew Pitcher
>
> I don't know about Slackware 13
There is an understatement.
Could you please stop posting under "Lew Pitcher?"
Thanks.
LewPi...@LewPitcher.ca
--
Lew Pitcher
> Lew Pitcher <lewpi...@lewpitcher.ca> writes:
>>Always have a windows standalone, or a dual boot system, because the
>>printer will ALWAYS work automagically on a windows installation.
> Oh please. What utter nonsense.
?!?
If you check the windows newsgroups you will see that very few
people have problems getting a printer to work in windows.
But that's a fact, and since you're a linux zealot...well, let's not
get confused by facts...
Lew Pitcher
> lewpitcher@lewpitcher wrote:
>
>> Linux is, just as unix always was, a complete failure when it comes
>> to printers. ...
>
> Not that it matters to this discussion, but I've managed printing with
> both commercial Unix (DEC/Compaq/HP/OSF-1/Tru64-Unix) and with Linux,
> collectively now for about 12 years. I won't claim that it's always
> been the easist aspect of system administration, but it has definitely
> improved, and most certainly has not been a "complete failure" at any
> time. One person's inability to work with specific software does not
> necessarily reflect on the quality of said software.
One person's inability?
_One_ person?
HAHAAHAHAHAHaHAHAHAHAHAHAHAHAHAHAHAHAH!!!!!!!!!!!!!!!!!!!
>> ... half of the printers out there, including ALL the economical
>> printers, will never work with linux.
> This definitely has not been my experience, though I've mostly
> used HP printers with Linux (and a very portable Canon inkjet,
> with pretty much no trouble).
How do the Dell (lexmark) printers work?
Hmm?
Not at all?
> What's mostly lacking is vendor support and appropriate
> documentation, but this should not be misinterpretted to mean the
> functionality "can not" or "will never" work. The number of printer
> models I've tried is relatively small, but in practice it comes down to
> locating suitable support files for those models, and configuring the
> printer server software to use those.
Locating? Locating? Do you mean that process that windows uses
when it automagically locates and invisibly installs the drivers
that are almost always a part of the OS?
Or do you mean doing endless google searches to locate, download,
and mechanically install, a linux driver, and usually a deb or rpm
at that?
>> ...the printer will ALWAYS work automagically on a windows
>> installation.
> As a matter of fact, this also turns out to be incorrect, as setting up
> a printer in Windows almost always requires installing vendor-supplied
> software ("driver") for the printer. That isn't automagic, and the only
> real difference from Linux is that the printer vendors are prepared to
> provide that software for Windows but not for Linux.
The _ONLY_ time you have to use vendor supplied printer software to
install a windows printer is when your version of windows predates
the printer.
>> ... Former Linux User
>
> Oh good; so you won't be bothering us any longer ...
Bothering? Moi?
Peter Chant
>> Kmail works fine here with cups with no special effort. In what way does
>> it not work?
>
> You are a liar and a zealot and as such, the very worst enemy that
> linux has.
You are so transparent.
Cordially as always.
Pete
Dan C
Nonsense. Of course it will.
Dan C
> Res <r...@ausics.net> trolled:
>
> top-posting deleted, unread.
Jesus, now 'rm' is starting to sound like Alan Connor. A new low.
Sylvain Robitaille
misrepresent Lew Pitcher, wrote:
> How do the Dell (lexmark) printers work?
> Not at all?
If that's the case, perhaps those models should simply be avoided then.
The (non-Dell/Lexmark) models I've tried haven't been difficult to use
with Linux.
> Locating? Locating? Do you mean that process that windows uses
> when it automagically locates and invisibly installs the drivers
> that are almost always a part of the OS?
In the case of recent versions (>= 10.0; this may also have been true
at 9.x, but I really don't recall) of Slackware (which is the system on
which I have the most experience with this), "locating" has amounted
to finding the right file in the /usr/share/cups/model directory, and
copying it, uncompressed into /etc/cups/ppd, and pointing CUPS to that.
Prior to that I was using bsdlpr and a much simpler printer.
A Guy Called Tyketto
Hash: SHA1
Sylvain Robitaille <s...@alcor.concordia.ca> wrote:
> On Mon, 16 Nov 2009, Roger Maynard, in a blatantly obvious attempt to
> misrepresent Lew Pitcher, wrote:
>
>> when it automagically locates and invisibly installs the drivers
>> that are almost always a part of the OS?
>
> In the case of recent versions (>= 10.0; this may also have been true
> at 9.x, but I really don't recall) of Slackware (which is the system on
> which I have the most experience with this), "locating" has amounted
> to finding the right file in the /usr/share/cups/model directory, and
> copying it, uncompressed into /etc/cups/ppd, and pointing CUPS to that.
> Prior to that I was using bsdlpr and a much simpler printer.
>
Sylvain,
Like I've mentioned in this group before, save your breath and
don't argue with this idiot. It isn't worth it. Besides, he'll do his
best to drop you down to their level, then beat you with experience.
It isn't worth it.
BL.
- --
Brad Littlejohn | Email: tyk...@sbcglobal.net
Unix Systems Administrator, | tyk...@ozemail.com.au
Web + NewsMaster, BOFH.. Smeghead! :) | http://www.wizard.com/~tyketto
PGP: 1024D/E319F0BF 6980 AAD6 7329 E9E6 D569 F620 C819 199A E319 F0BF
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iD8DBQFLAieKyBkZmuMZ8L8RAi++AJ9UEUjm0dkLntpXPOkWOJkdRf5wEACfX1JK
tuiE4uS286pAlVBGfa9WbEY=
=P1/D
-----END PGP SIGNATURE-----
Lew Pitcher
> On Mon, 16 Nov 2009, LewPitcher.ca wrote:
> In the case of recent versions (>= 10.0; this may also have been
> true at 9.x, but I really don't recall) of Slackware (which is the
> system on which I have the most experience with this), "locating"
> has amounted to finding the right file in the
> /usr/share/cups/model directory, and copying it, uncompressed into
> /etc/cups/ppd, and pointing CUPS to that. Prior to that I was
> using bsdlpr and a much simpler printer.
We gave up on trying to get scanners and printers and, especially,
all-in-ones, to work with linux years ago. It was simply much
easier to use a Windows PC, and especially, applications written for
Windows. The best affordable graphics and word-processing software
is exclusively windows. Of course, there is high end graphics and
animations stuff written for unix/linux that relies more heavily on
multi-user/multi-tasking environments but that stuff is not relevant
to this discussion.
If you are a hobbyist, then by all means, fiddle about with linux.
That's what linux, and especially slackware, is meant for. But if
you're a pro, the computer is a tool, and you just want to get stuff
done either buy a Mac or install windows.
LewPi...@LewPitcher.ca
Lew Pitcher
pgp trash troll delete
Unlike you, I actually have something to add to the debate.
LewPi...@LewPitcher.ca
Res
--
Res
filters
--
Sylvain Robitaille
misrepresent Lew Pitcher wrote:
> If you are a hobbyist, then by all means, fiddle about with linux.
> That's what linux, and especially slackware, is meant for. ...
Now you're just trolling for its own sake ...
Dan C
> On Tue, 17 Nov 2009, Roger Maynard, in a blatantly obvious attempt to
> misrepresent Lew Pitcher wrote:
>
>> If you are a hobbyist, then by all means, fiddle about with linux.
>> That's what linux, and especially slackware, is meant for. ...
>
> Now you're just trolling for its own sake ...
That's all the rm-troll has *ever* done.
Eef Hartman
> The proper ppd file won't help with the fact that Cups won't work with
> Kmail.
Slackware 10.0 which came out in 2003) and we've always been able
to print FROM it.
As I said before, the problem is not in kmail, but in "kprinter",
which must be setup to use the "cups" printing system.
--
*******************************************************************
** Eef Hartman, Delft University of Technology, dept. SSC/ICT **
** e-mail: E.J.M....@tudelft.nl - phone: +31-15-278 82525 **
*******************************************************************
Loki Harfagr
> jo...@wexfordpress.com <jo...@wexfordpress.com> wrote:
>> The proper ppd file won't help with the fact that Cups won't work with
>> Kmail.
> We have been using kmail and cups for the last 6 years (ever since
> Slackware 10.0 which came out in 2003) and we've always been able to
> print FROM it.
> As I said before, the problem is not in kmail, but in "kprinter", which
> must be setup to use the "cups" printing system.
That's correct, the KDE devs may bortch a few steps sometimes but
at least (unlike their G challenger) they tend to limit the funk
from kde into kde.
Besides, please note that printing an email
always has seemed monstruously nonsensical to me ,-)
Aaron W. Hsu
>Besides, please note that printing an email
>always has seemed monstruously nonsensical to me ,-)
I would agree with the many very small, almost useless emails that many
people seem to send today. However, sometimes someone writes a real
message that actually has paragraphs, and who knows, maybe even
chapters! That's nice, and also worth printing out.
Aaron W. Hsu