Kernel 2.6.17.13

First download HPLIP current version for Slackware hplip-1.6.9-i486-1 from here

http://packages.slackware.it/package...p-1.6.9-i486-1

Download to /home/username

Now to get this to work hpijs has to be removed to do this open a terminal and su to root

at the prompt Type

# removepkg hpijs

Once this is complete and you have the prompt type

# installpkg /home/username/hplip-1.6.9-i486-1.tgz

Next you have to start hplip before cups to do this at the prompt type

# /etc/rc.d/rc.cups stop

# /etc/rc.d/rc.hplip restart

# /etc/rc.d/rc.cups start

Install your printer using localhost:631 in your web browser or if you use Kde you can use the printer install wizard, you will need to use the PSC 1600 foomatic/hpijs driver (part of the HPLIP package and reinstalled with that package, if the hpijs drivers are not removed prior to install of HPLIP the scanner will not work.).

After installing and testing the printer, use kmenu run and open xsane, the HP PSC 1600 Hundred should be in the title bar, test your scanner using either the preview or scan button, either should work.

If you wish you can also add xsane to kmenu. To do this right click on the kfor kmenu and select Menu Editor, in here right click on Graphics, or Menu Heading of your choice, select new item, name 'xsane', in the right panel click on the icon button and select the xsane icon. Next in the command box type /usr/bin/xsane then save.

In Kmenu Utilities you will find HP Device Manager, you will be able to configure scanner and printer, view ink usage and access photo cards.

Have fun :-D

Buggy KDE apps.

I followed your instructions and installed my HP Deskjet 920C,
then printed an email message to test it.

Then I opened that HP Device Manager and it says "No Installed
HP Devices Found."

This is my usual experience with KDE; which is why I usually mess
with this buggy software for a few days, then go back to Fluxbox.

KDE reminds me so much of Windoze.

Thnak you, for your post...it works great.

I contacted the HPLIP Help mailing list, and the reply
from HP said to upgrade to HPLIP 1.6.10. I did that, and
used "hp-setup" and now HP Device Manager works.

How did you make him work, because hplip 1.6.10 doesn't work to me...it sais that hpiod or something like that cannot start...when I type the commands
#/etc/rc.d/rc.hplip restart it fails on hpiod...how can I make him work...or should I compile him from sources...I've tried...but I use slackware...and it seems to work only with hplip-1.6.9

Thank You.

Previously I installed hplip-1.6.9-i486-1 from the /testing
directory of Slackware 11.0.

To upgrade I used the hplip.SlackBuild script from Slackware-11.0
and made the following changes from the old SlackBuild script
to build 1.6.10.
I got the hplip-1.6.10 source from SourceForge.

If you don't understand, post back and I'll help you more.

Then I upgraded packages with the command:
"upgradepkg hplip-1.6.10-i486-2.tgz"
and It Just Works (TM).

Thank you...it works...I just make as u said...upgrade from hplip-1.6.9 to 1.6.10...

Thank you very much.

You're welcome. It's nice to see the ink levels while running
a Linux distro. And it would be even nicer if HP would include
Resolution Enhancement Technology (closed source imaging code).
With it in Windoze mine prints 4800 dpi, but in Linux it
only does 1200 dpi; and that's running it from CLI. Printing
through apps, such as GIMP, is still only 600x600 dpi.

You are both welcome am happy to have been of some assistance

You, sir have removed one of the last stumbling blocks from my getting my wife using Slackware 11.0 on her computer. The pclos has served its purpose, but it's time for it to go.

Thank you!

Blackhawk you are and your lady wife are most welcome
enjoy Slackware and all things Linux.

Linux Not just an Operating system, a way of Life.

All of the info available via the hp-toolbox is also available from the command line, just in case the toolbox won't launch. If you type 'hp-levels' for example it will give you the ink level. They're listed under /usr/share/hplip.

I'm not clear why I need to remove hpijs as hplip should sit happily with it.

Simcox1, I can only guess the reason behind it, however I know from experience that if you do not remove the installed hpijs first, the scanner will not work at all.

So removing hpijs first will save you a lot of trouble. It is possable that the version of hpijs that comes with HPLIP may differ enough to cause a conflict with the installed version. How this affects the scanner side of things is beyond me.

I understand running the command to upgrade, but the changing and running the Slackbuild script is just a bit over my head. Could you go through the steps for that part and explain a little what that does?
Thanks so much for your help.
Bert (newbie)

Slackware packages are built using s Slackbuild script. If you look in the sources directory of a Slackware mirror, every package has a build directory, in which are all the necessary files to build the package. These files will include the *.tar.gz (or *.tar.bz) and the SlackBuild script. Once you have all the required files in a single place, you make the SlackBuild script executeable and run it. The post above is showing the differences between the old script and the new one. So the version number has been changed from 1.6.9 to 1.6.10 etc. So to upgrade the hplip package from 1.6.9 to 1.6.10, you need to go to a slackware mirror and and copy everything contained in the /testing/source/hplip directory, replace the hplip-1.6.9.tar.gz with the new one (1.6.10), and then edit the SlackBuild script accordingly. Then run the script with ./hplip.SlackBuild