Slashdot Mirror
Making Linux Printing as Easy as in Windows
Jonny5 writes: "In preparation for the transition from windows to a Linux based workstation, the main focus is that of peripheral compatibility. Sure Linux is rock solid stable, and has an almost totally customizable GUI, but dammit, if my hardware won't work, what's the point? ...After hearing about TurboPrint, and their claim to provide 'Printer set-up and configuration is as simple as on Windows or MacOS,' I had to rise to the challenge. LinuxLookup.com has done a full review of TurboPrint For Linux."
I use KPrint (part of KDE infrastructure) with CUPS... I dont think I could ask for much more, though admittedly I think you still have to set the thing up via the CUPS web interface.
Still, it's better than using lpr/lpq and wondering what bit of the pipeline ate your document =)
.. is some kind of wine-driven printer emulation layer, that would let you use windows printer driver sin Linux. Why? Because I have a printer that I have had for 4 years now, and is still nowhere near a Linux solution. Is this idea even possible? I think it would be great if it were, since I could finally use my printer!
Cons:
limited printer support
tarball install
missing dependencies
Pros (or why should I use this over standard KDE print config/RedHat printer filters/anything else):
Perhaps your obscure WinPrinter is supported
Nice effort guys, but there's no real value here.
I want to delete my account but Slashdot doesn't allow it.
I guess the real question is how well it can handle some of the cheap Windows-only printers that are given away for $99 that don't have Linux drivers available anywhere.
t -that-of-the-cartidges-themselves printers is interesting, what about just general SOHO or regular home printer support?
It's not just the cheap printers that are sometimes windows only... I have a xerox laser printer without linux driver support and it's a few years old. So, yes, a test of those almost-throw-away-printers-as-their-cost-is-almos
Wheeeee
As easy as windows? Does that mean it's going to ask to be rebooted three times, crap out because it can't find the files it needs on the install disk, then (after I manually find the files) install the same printer device twice, in such a way that neither of them works? Uninstall, reboot, reinstall, reboot, repeat until device works.
I'm sure there's an o/s easier to configure than linux, but, good lord, it isn't Windows.
When users of an open source operating system are all but forced to rely on commercial products just to install a simple printer driver, there's something amiss. Does anybody know of an open source project to provide similar support?
Have you ever tried to set up a shared printer on a windows box attached to a LocalTalk network (Mac)? This is NOT easy :-(
Granted that is not the most popular case, but you've got to admit that MS didn't make that option too obvious. Those bastards. My HP 2000NT is still printing 2 pages of PS crap at the end of each printing session ONLY from the windows box (with latest drivers and 4 days watch in hand with MS/HP tech support.)
PPA -- the girl next door.
-- I feel better now. Thanks for asking.
This is one of the core problems with Linux. Someone comes out charging money so we can do something as menial as print documents, and we actually have to take it seriously.
It's part of the basic problem with the degree of modularization (a supposed "Good Thing") that we have, I guess. Still, it'd be nice if we could have all this sort of basic admin stuff thrown into a central location with other peripherals, instead of one for the OS, one for the GUI, etc.
IMO, this is something Windows did right. I've been working with Linux for a long time so this isn't a surprise to me, but I can just imagine the look I'd get from newbies I'm trying to win over to our side when I try to give reasons for why Linux doesn't have a true equivalent for the Control Panel.
-------------------------------------------------
charlton heston is more of a man than yo
What's wrong with this picture?
Printer set-up and configuration is as simple as on Windows or MacOS
TurboPrint for Linux comes as a tarball containing 'install' and 'uninstall' shell scripts, installation instructions, and all the binary software.
Yes, it's a command-line installer!
The default printing would be in black and white, and when I want to print in colour, I can just change the print command used by the program from 'lpr' to something like 'lpt -Ptp0'.
Yes, you have to give command line options to set printing modes every time you print with a different mode!
And yet this gets an 18 out of 20 in the review. It's amazing to me that this late in the game, there are still so many Linux-heads who just don't get it. This is not just inferior to Mac and Windows -- it's a giant quantum leap backward from where Mac has been for seventeen years and Windows for six. Real end users don't memorize command languages.
Tim
I use cups and it does all I need to do and more.
It's almost completely manageable via a web interface (the only thing I know of that isn't is setting the default printer). It integrates very nicely with samba. It uses gimpprint drivers to create nice output on newer printers.
The reviews indicates that it can use cups, but I don't yet understand what this gives me that cups doesn't do already.
Slashdot? Oh, I just read it for the articles.
And why do you think that is ? also, why do you think Linux (and most Unices) are more secure on a network than Windows ?
I agree that the Linux kernel is better designed (although to be honest I know next to nothing about the newer Windows kernels, and some supposedly knowledgeable people told me they were actually pretty good). But the biggest reason why Linux is more stable and more secure is because you, the computer-savvy user, took time to configure everything right and install servers right.
Now, if you want to make a Linux-based system that your grandma can use, you'll have to mask the concept of users vs. root with some suid installation utils, you'll have to allow everybody and their dogs to install any piece of software and insmod any driver from any vendor, you might have to slap in the equivalent of a registry to alleviate the current mess of etc files in a typical Linux fs, ...etc...
If you do all that, if you make Linux user-friendly like Windows is (supposedly, I can't even begin to comprehend its organization), then I guarantee you the resulting system will be less stable and less secure than a standard Linux distro.
The real reason why Windows is shitty is because it's designed to be used by computer idiots. I believe that if computer users were required to learn basic computer sanity, and Windows didn't have the convenience/security/stability tradeoffs it has today to make up for computer idiocy, Windows would kick any OS' butt any day. And "basic computer sanity" doesn't mean the user has to learn how to install daemons, it means "don't run executables from Joe_Sixpack@hotmail.com", just like "don't stick candy bars in the toaster" in real life : if people had that basic good sense, there would be no auto execution in Outlook, because people would find that crazy.
The next problem after printing is ironed out is the lack of a single, easy to use tool to add, temporarily disable, manage and remove fonts in any Linux setup, that makes one set of fonts (both ttf and Type 1) in a single directory available to all applications system wide, in the way that Adobe Type Manager does.
We then need CMYK capability in The Gimp. After these are in place, it will be possible to assemble a desktop publishing suite that will have mass appeal, because anyone will be able to design and publish to QuarkXpress/Photoshop/Illustrator quality, and print the results, all in a rock solid, free alternative to Windoze and OSX, without any pain.
ATH0 Bitcoin: 1DnwFLXczVZV8kLJbMYoheUrpqHesjxrSi
UNIX apps don't send GDI commands - they usually send postscript commands.
So unless someone wants to write a postscript to GDI filter, that approach won't work.
Oh, and things that need to communicate directly with your hardware (like this printer driver) may not be able to run in wine anyway.
I use Cups on my ML 8.1 box and have never had a problem with it and my Canon BJC-2100. This whole thing just seems like hogwash. And in response to the comment about cheap printers for less than 99$. My Canon cost about 49$ after a 20$ rebate. Its a fine printer and its USB. Just be careful what you buy.
-
It doesnt support any of the "free", usually giveaway, lexmark, etc printers.
/www.turboprint.de/printers.html</a>
<A href = "http://www.turboprint.de/printers.html">http:/
what is the point? that list is so short...and there are free printing infastructures for them already. so why would we pay $19 for this product!?
these are all fairly expensive hardware printers...not the kind most joe schmucks will have.
Even on Debian, it was pretty much point-and-click for me...fire up a web browser, point it at http://localhost:631, click on "Manage Printers", click "Add Printer," enter a superuser name and password, and follow the steps from then on.
It really is that simple, unless you've got a distro that has a weird installation of CUPS.
Heck, on Mandrake boxes, one can often have the printer autodetected, and the installer can often (in my experience) choose the correct driver.
Stating on Slashdot that I like cheese since 1997.
With other hardware networorking under Linux seems to have been the biggest win-win. Many network cards are supported under Linux now as well. So are many sound cards.
Support comes slower under Linux, but it does seem to come. More and more larger companies are supporting LInux and with the way that windows XP is moving I am wondering how many people will really want to stay with windows. Since companies like IBM and other large companies are beginning to back linux it may only be a matter of time before the smaller companies and companies that promise Linux support actually do.
Personally I think it would be nice the be able to buy hardware for Linux and have it come with open source drivers and software. Or atleast instructions on what software you need to have on the machine and kernel drivers. Soon I hope...
Only 'flamers' flame!
One part of the solution is simple: buy only PostScript printers. PostScript printer support is quite mature in all UNIX-like operating systems.
The hard part: Under X11, there is no default mapping from screen fonts to printer fonts (which can have completely different metrics). That's why printing with non-standard fonts is often problematic if you don't use proven tools such as TeX or roff.
Sure Linux is rock solid stable, and has an almost totally customizable GUI, but dammit, if my hardware won't work, what's the point?
... and then we find out that most of their software WILL NOT RUN under XP (yes even by using compatibility mode) and that they will have had to have gotten a new scanner and printer because they wont work either.
I set up a windows xp box for someone the other day. It was QUITE an upgrade from their old 133 mhz computer -- they were excited that all their programs will run SUPER FAST and that their printers/scanners/etc will be OH SO nice...
Now I'm sure that windows xp has changed QUITE a few things but come on... they have used winxp for a bit now to see if they can put up with it.. they now want me to install windows 98 on there... quite an upgrade (if you ask me)...
Now before you say "Put them on Linux!" -- get real.. would you put your mother-in-law on linux --> knowing you dont want to put up with her "Whats this? BASH? Is this a joke??"... feh on them all..
hehe, good one. An operating system as big as Windows XP that is vulerable out of the box with the default setup is unacceptable to me. Many people that have already purchased this operating system will not patch this hole. We'll be seeing Code Red II pretty soon.
Is RH 7 vulnerable OOTB with the default installation, no. Some services such as wuftpd are vulnerable to a remote exploit, but the user must turn those on manually. It is then assumed that the user knows what he or she is doing and then secures the service by updating the RPMs. In the XP case, the user just has to take the computer home from Best Buy and plug the thing into the cable modem and it's vulnerable.
In my experience, Lexmark has wonderful Linux support for its products. $79 at Best Buy got me a very high quality 1200dpi inkjet printer (the Lexmark Z23) with both Windows and Linux support. The Linux side actually works better than its Windows counterpart, oddly enough. It runs as a daemon process, does PostScript exactly the way it should, and the fact that its a USB printer doesn't complicate the situation either. It all just plain works, out of the box. Even has a nice graphical config utility
Kudos to Lexmark for doing it right!
Bowie J. Poag
Well, Linux is the type of operating system where you are EXPECTED to go under the hood (as the mechanics would say..*grin*). It's part of the challenge. Initially I had problems with printing on my Slackware 7.1 box. So I installed a script called apsfilter (which came along with the distribution and is available at freshmeat.net or tucows). This little beauty did everything needed to be done for my printer setup, including editing the /etc/printcap file. In my four years of running Linux, I have yet to find anything that there wasn't software regularly available on the net, and print tools such as apsfilter is just one example
My two bits
Clive DaSilva Email: clive.dasilva@gmail.com Ubuntu 18.10 Kernel 4.18
I've recently rediscovered cups. For my printing needs, mixed unix and some windows it beats everything else hands down. It provides easy web based administration or if you're fimilar with the bsd or sysv (big bonus for me since i primarly use solaris) style command line tools it has those as well. But the number one thing that makes me choose cups overy anything else is its support for using PPD drivers. Need a driver for that freaky printer, Xerox DocuCenter 332ST in our case? Download the PPD stick it in /usr/share/cups/model and off you go. Now i can use all the features of the printer. Not just simply print to it. Eg. now i can colate, staple, duplex print etc. Couple this with kups or xpp which are "print setup" like programs that let you adjust your print settings and its almost as easy as on a mac. So aside from support for "winprinters" how is turbo print different from cups?
This is, in my opinion, one of the areas that will continue to limit the ability of Linux to be used on the desktop. The printing process is simple and flexible for a hacker, if it is a supported printer, but fails the mom test miserably.
What is really needed is an organization with some clout to get behind an API that can be integrated into applications, with a standard, integrated menu selected printer control. Just like the Macs have had for 17 years and Windoze has had for 10? years. There have been a couple of attempts in this direction, which seem to have mostly fizzled. That is why heavyweight clout will be required to make such a thing work.
CUPS is an improvement and a little easier to use for the printer driver installation and setup. But this does not address the user interface. This is something that perhaps Redhat, on the Gnome side, and perhaps some other organization on the KDE side, should have handled years ago. I think this is far more important than having a Gnome/KDE office suite.
The fundamentals should be the first priority, and in an office, printing is absolutely fundamental and critical. A big enough busines can perhaps afford to hire a Linux guru to set up printing, but that should not be required and will remain a roadblock. In fairness, Windoze printer installation and setup is often no picnic either, but that is no excuse for Linux being so lame in this area.
Im curious though, will win2k drivers work under XP? That's a possible solution if the manufacturer hasnt put out their XP drivers.
-
"My side" wrt Linux is a place where things really ARE modular and logical. Where, if you have an extraordinary knowledge of systems and computer science as a whole, you can enjoy your time in it. Where, if something isn't working, you can change and recompile it within hours.
Your "our side" seems to be that awful "I want Linux to be a better Windows than Windows!" garbage. Here's some advice: Linux is not Windows, and Linux will never be Windows. It will never be worse than Windows; it will never be better than Windows -- IT WILL NEVER BE COMPARABLE TO WINDOWS. If you want something like Windows, use Windows. If you want something kind of like Windows but different, use Windows. If you want something better than Windows -- sorry to say it -- you're going to have to live with Windows. LINUX IS NOT WINDOWS.
And why on Earth would you be trying to "win over" someone to "your side"?! Can you even THINK of anything more dishonest? Linux is not Britney Spears; it is not a Happy Meal. If people use it, it's because they want a free Unix-like operating systems, they've done their research, and they WANT to use it. It's not because they've been tricked into something (sorry -- "won over"), so that when they finally do try out Linux, they're horribly disappointed at how un-Windows-like it is, and hold some kind of great resentment towards it.
Look around the web. How many "Linux sucks" posts and websites do you find? A LOT. Is it because Linux actually sucks? Not likely. It's because some "helpful" friend tried to "win them over". They probably said something like "if you're tired of Windows crashing all the time, try this other operating system called Linux". They try Linux, expecting it to be better than Windows, and SURPRISE SURPRISE find out that it "sucks". If you use Linux expecting it to be Windows, guess it, it sucks donkey balls. Not just any donkey balls either -- big ones. LINUX IS NOT WINDOWS. DON'T PRETEND IT IS. AND FOR THE LOVE OF GOD, FOR THE GOOD OF HUMANITY AND COMPUTER USERS EVERYWHERE, DO NOT "WIN OVER" SOMEONE EVER AGAIN.
Loaded up printerdrake in my Mandrake 8.1 installation.
2 minutes later, I run upstairs to find see the printer goin to work on a perfect test page!
Mandrake rules, kids. No need to spend 20 dollars on anything else.
Berto
I recently tired TurboPrint and was impressed. There is a free version that works surprisingly well. The thing I really liked was the quality of the printer drivers. Graphic print outs on my HP inkjet printer are dramtically better than the RedHat/Ghostscript drivers that I was using before. This is the real value added of the product. The configuration tool is nice, but is not the real value added of the product.
and this will unfortunatly probably never happen. Linux people (myself included) are generally gung ho about having multiple apis for everything. while this is good in some ways, it's awful in others. we have X, with no kind of gui standard. theres pdq (what i use), lpr (lousy imho), cups (gonna give it a spin in a bit), and this. for sound, there was oss, which i used for ever, programmed for, and everything, and now alsa, which absolutly rocks (featurewise). and these are for common, user side things. people continue to speculate what linux needs to 'win the desktop,' and the list is generally something like : apps, ms office, games.
while these would help, it'd be more helpful to people writing those if they had a standard api to write for, rather than trying to accomodate all of them. but as soon as you say 'one standard' you get the general 'one world, one os' reply. its unfortunate, really, despite how helpful it really would be.
theres nothing wrong with progress, but some coherence would provide worlds of help to developers.
just my 2 cents
All thats lacking for linux printing is the knowledge of whats avaliable, check out linuxprinting.org As a summary if you use Redhat use printtool, suse have there own setup in yast, Mandrake probably have something too, for debian or most other distributions use aps though as with most setups you need ghostscript(for postscript conversion) and a printer spooler such as lpd or lprng. Never used it but CUPS is supposed to be easy to use and of course you could just buy a postscript printer. I don't see why this commercial program is needed, use whats out there and free as in beer and speech!
Also, make sure there are no spaces after the 'No's. The first time I tried configuring this, I had a space after the word and the braindead parser couldn't recognize the option because of it(not sure if they've fixed it in the newer versions or not)...so I swore for a couple hours before actually checking my syslog as to why the damned thing kept ignoring the option :)
The GUI should let you purge completed jobs, IMNSHO. For a basically single-user system, it's best to just disable those two options, unless you are into checking your /var/spool/cups directory on a regular basis (I have better things to do with my time)
My perception is that most people have problems not with printing, but with their printer. People buy printers that only work with oddball command languages or expect the host CPU to do absolutely everything and send them raster lines. Whem I am asked about these marginal printers at LUG meetings and installfests, I advise people to get postscript or pcl/hpgl printers. These are standard printer languages. I have never seen a printing situation that postcript couldn't handle.
But people still buy these cheapo printers and when they find out that Linux mostly supports elegant, standard printer interfaces they jump directly into "Linux sucks" rants.
One way to convince these people to buy "real" printers is to point out that a printer with some specialized driver might not be supported in the future. Suppose the manufacturer made a driver for printer yzx-ii for Windows 3.11. They discontinued the printer in 1994 but they still released a driver for Win95. They updated their driver for Win98, but they never did bother porting it to WinNT. Now they don't support Windows 2000 or XP, and you can't expect them to keep writing drivers for printers they last sold eight years ago.
Now look at the alternative case. Instead of yzx-ii you layed out a little more cash for a postscript printer. This printer is going to work with any past, present, or future operating system until the hardware falls to pieces. The buyer of a postscript (or pcl) printer never has to worry about printer drivers. He's got a postscript printer! It's just like HTML, TeX, and so on: the standard is out there, you can't kill it, and it will be supported for eternity.
My printer is an Apple LaserWriter II NTR, which I found in the trash. It has a postscript processor, so I can use it with Linux and like operatings systems, Windows [3,95,NT,XP], OS/2, and vintage of MacOS, and so forth. This printer was introduced in 1992 and it still works great, without software problems of any kind. I'll never need a new "driver" for it because I already have the postscript printer description file and I don't believe the hardware is changing! If I had paid money for this printer, I would consider it a wonderful purchase.
(end of rant)
Since you missed it: he said Windows is more insecure than *nix because it's meant to be used by idiots; make it less idiot-proof and many of the recurring problems would disappear.
-Legion
I used to maintain printer drivers for Windows and OS/2, and the implementation of the print subsystem on those operating systems is one of the very few areas where I've thought the design was more elegant than any UNIX solution I've seen. I suspect this is due to the modular nature of UNIX, which in this case turns out to be a weakness.
In a nutshell, the OS/2 and Windows kernels export an interface that you write functions to when you're writing a driver. This interface covers page rendering as well as printer set-up and configuration. That means anyone who wants to render a page need only call those functions and doesn't need to worry about what printer he's sending to. Integration of feature selection into your application program is also much simpler and takes advantage of the code written by the printer driver programmer.
The down side to all this of course, that since the GUI subsystems of OS/2 and Windows ran in kernel space, a poorly written printer driver can easily crash your entire system.
Only recently have efforts been made to address the rendering side of the problem with the Xprt extension to XF86 and the toolbox-level gnome-print library (I assume the KDE people have something similar as well.) While these efforts are good, a printer manufacturer is not likely to put the effort into supporting all of them. This means that we will continue to write our own rendering code to render into PostScript.
Ghostscript seems to have become the de-facto printer driver for Linux and the only real complaints I have about it are that it's much harder to integrate printer features into your program when Ghostscript is in use. I ended up trying to get around these problems by writing an incomplete PPD parser for the printers I was working with. This parser generated information files about the printer features and a lpr replacement program would present these features to the user. We did a pretty good job of making a GUI installer and front-end for printer feature selection, but it only supported our printers.
Technically it wouldn't be a very difficult problem to address these issues and make everything seamless for the programmer and the users. Politically it's rather more difficult though. This is one area where you're going to need a single standard if you want the printer manufacturers to write drivers for you. There needs to be one render interface, ideally at the X level so the toolkits can make use of it and one feature communication interface so that various programs can query for printer features. Queueing and spooling is already pretty well addressed.
I'm trying to teach myself to set people on fire with my mind... Is it hot in here?
While CUPS makes life easier, I still have a lot of problems with Linux. I run SuSE Linux 7.3 and have an Epson Stylus Color 800 printer connected to a networked print server (Netgear PS104). While Linux talks to the print server just fine, no matter what I try Linux takes 2 sheets of paper per page (yes, I have it configured for Letter and tried the inkjet letter settings). What is worse, however, is I get random horizontal lines on the page. Note that the output is going through Ghostscript.
Now, with the same setup, print server, etc. I have no problems when printing from OS/2 or Windows. Furthermore I do not get the horizontal lines (so it's not a cabling problem or a problem with the print server).
Now the Epson is a fairly common printer with well-documented control codes. I guess the only way to print properly in Linux is with a Postscript printer.
This post is encrypted twice with ROT-13. Documenting or attempting to crack this encryption is illegal.
The real problem and reason why printing in Linux, esp. from the GUI, is a pain in the behind is that no distribution has a working system-wide font configuration mechanism where X and gs can painlessly access the same fonts (Recently I stated that Debian does, but it still has problems with font names with spaces in them, rendering it practically useless because many common truetype fonts have spaces in them) and the lack of a working printing toolkit. I don't know about libgnomeprint, but Qt/KDE's printing is horribly, horribly broken.
This leads to the dilemma that GUI application developers not only have to write routines to display their data on screen, but also ones to bring everything to Postscript. Web browsers are a prime example where the screen display is complex enough so that there's no more resources left to reinvent the wheel in Postscript, leading to Mozilla's broken printing.
The final problem is the lack of Unicode support in the ancient Postscript/Type 1 font standard. The introduction of the Euro made this painfully obvious for European Linux users.
Before we look at the hardware, we need a reliable printing library that surpasses Postscript's stone-age encoding, rendering out every single character. I believe libgnomeprint wants to do that, but I haven't been tracking it. We need a printing system that does not rely on printer drivers that are compiled into the PS rasterizer (lpr, ugh!) or has other quirks (cups is a step forward with its modularity and two behind with its own rasterizing program, effectively introducing a separate app for PS->screen and PS->printer). The hardware support is already here, but what use is a fast car if you can't get the door open? (Don't you just love metaphors?)
Well, Linux is the type of operating system where you are EXPECTED to go under the hood (as the mechanics would say..*grin*).
No the "mechanic" (system administrator) is ment to do this. This need not be the same person as the "driver" (end user).
With Windows the engine compartment is sealed, but a whole bunch of controls for fuel air mix, engine timing, etc are placed on the dash. (A few of them might not actually be on the dash, but are adjusted by using the steering wheel whilst holding down various buttons on the radio...)
The Linux way of doing things appears more complex where the same person is expected to both use and administer the machine. The Windows way of doing things is an utter disaster where the user and administrator are different people. Because it is quite easy for the end user to mess things up and the admin cannot easily do any work on a machine whilst it is being used.
I just installed Turboprint, and it's definitively a nice product.
My HPDJ970C is supposed to work with cups and lpd, but I only had it work with text documents so far. Printing photographs worked, but the result was very ugly (not something that you can call a photograph) .
Turboprint seems to print photographs as well as windows, and that's something I've been waiting for a long time.
Plus it has a "printer toolbox" to align and clean printing heads. No more need for a Windows partition any more.
Just one thing : what's the best piece of Linux software to use in order to properly scale photographs before printing them?
{{.sig}}
The first is Windows plug and play printer capabillity. Plug a printer into the parallel port and chances are high that Windows will detect, identify and install the drivers for the printer. Linux has nothing like this.
How often do you connect printers to computers though. This is a variation on the "easier to install" theme...
But, the second advantage that Windows has is probably it's greatest advantage. That is point and print. This is the abillity of NT/2000 to allow the user to browse available printers on the network. Then, when the user clicks on the printer, the correct driver is automatically downloaded and installed. No configuration is required by the user.
Actually 9X can also do this. But one possible result is piles of stuff being sent to a printer which the end user does not know the location of. Also Windows workstations don't cope well with SAMBA shared printers restricting access by IP address (probably because NT servers can't do this). Possibly XP has had this fixed...
This one isn't. I installed CUPS on my network, had absolutely no problems. All done in the CUPS web based GUI - no problems whatsoever.
AFAIK, you can use KDE applications without using KDE as your window manager. I used KMail when I was using Enlightenment as my window manager.
Yes, that's what I want, but that doesn't work, not with a novell network anyways. dragging the icon to the printer results in lots of pages with postscript command's :)
Luckily, we have sun boxen at school too
Um, did you read the installation instructions? I read the CUPS documentation, followed the instructions, and my Epson 600 worked perfectly first time.
That stuff is patented and thus illegal.
Instead of complaining to developers complain to your congressman because they are the only people that can change it.
Open Source advocates assume that Open software will always be better, in every sense, than Closed, because so many people are examining the source code. It's true that objective source code scrutiny does make better source code. But there's more to good software than absence of code errors. You need testing. Regression testing, usability testing, stress testing... MS can pay for all this because of their huge revenue stream. Development models that attempt to compete with Microsoft's closed model forget this at their peril.
It doesn't really get much better if the "linux-heads" try to put a GUI front-end on things. Widget layouts are often poorly thought out and often covey contradictory or ambiguous choices for configuration. These sad attempts at usability are even praised more highly than the supposedly "easy" command line stuff. The real problem is that the linux hackers designing interfaces in the linux community get sugar-coated reviews of their stuff by other linux hackers who are far too eager to say something is usable out of their ignorance of user interface design and out of their belief that anything under GPL is inherently superior to anything proprietary, interface or otherwise. As a personal experience, I once talked to a person who created a linux installer for a very prominent linux distribution and I mentioned a few of the dozens of confusing or ambiguous or inconsistent things I found in its interface. He couldn't understand what the problem was: he thought I thought that it "wasn't pretty enough". And yet die-hard linux zealots who remember vi commands before they remember their wife's anniversary claim that this interface is perfectly easy and that this installer is perfectly ready for the desktop.
The few people with interface design knowledge who point out these problems are usually called "whiners", and are told to shut up and code their own improvements.
Putting it bluntly, the linux development community is doing more to kill linux on the desktop than Bill Gates ever could. Microsoft realizes this, and that's they have never considered linux on the desktop a threat.
I'm running RH 7.1, which has LPR with Printtool by default, but after many wasted hours trying to get it to print reasonably well with any of my three printers, I finally found a solution that works.
The solution? CUPS with XPP. This basically gets me all the functionality I need, with compatibility in most apps. All of my KDE apps use CUPS's LPR emulation to print. StarOffice, Mozilla, and other X apps use XPP, in which the program sends the postscript data to XPP and XPP lets me select a printer, printing options, and sends it to cupsd. If any console apps want to print, they just use CUPS's LPR emulation. Samba also integrates with CUPS, letting me share my printers.
Setting up my printers was also a piece of cake. Downloaded & extracted the CUPS printer definitions from the website. Went to my nice CUPS admin page (http://localhost:631/) and went through the setup under "Add Printer." No config files to mess with or anything...
The only thing I could wish for is for RedHat to use CUPS as the default printing system, as other distros like Mandrake have done. It was really a pain to rip out printtool and all the crap it leaves behind.
Michael F. Robbins
Hi Tim,
I didn't intend my diary entry to be a negative review of Argyll at all. In fact, I am very impressed with the software.
The problem with Argyll at present is that nobody has (yet) integrated all the pieces in such a way that your average graphic artist can make high quality profiles. The pieces are there, and they're of quite high quality. But (at present) you have to have some serious color science knowledge to ensure that you get good results.
My latest attempt at a profile on Argyll produces breathtaking clarity, but I'm still dealing with a purple hue shift for deep blues, which I'm pretty sure is caused by my use of CIE La*b* as the interim color space for gamut compression rather than CIECAM97. Argyll has support for the latter, it's just not what I used.
So I'm very hopeful that Argyll will serve as the engine for truly topnotch color management in the free software world. I'm not going to say anything about how long that will take, though. Right now, I'm not getting all that much encouragement from the user community, who seems to vastly prefer whining on Slashdot about how the current state of affairs is inadequate, rather than rolling up their sleeves, learning some color theory, building profiles, and helping develop the solution.
There, I've just whined on Slashdot myself. Thanks, I feel better now.
LILO boot: linux init=/usr/bin/emacs
Well, that's because you use Slackware.
I have nothing against it, I even have no experience with it.
But it's well known that it's the more do-it-yourself distro is.
Then telling you don have the ambition to do-it-yourself sounds to me like you chose the wrong distro.
Maybe a better option for you is to insert a Mandrake cd into your cdrom, turn on your printer and print a testpage from Mandrake's installer.
It just works.
Well, don't worry about that. We can get you back before you leave. (Dr. Who)
Well, Linux is the type of operating system where you are EXPECTED to go under the hood (as the mechanics would say..*grin*).
And as such, all hopes about Linux becoming a dominant desktop OS can be safely ignored.
I have the Docuprint P8 (not the P8e since as you said the p8e is post script and we all know that's easy to get working). I shall try the HP4 driver for it and interestingly enough I've had that tip suggest for my other laser printer that seems less than supported - the Sharp UX-3600M - that thing I less than 3 years old and Sharp doesn't even list it as ever having existed on their website and they have no intentions themselves of making XP drivers... Sigh... I have the worst luck at picking printers.
Wheeeee