but you can still get it working…

Why do I care about this very old printer?: I really like this printer, I would never exchange it with another one.
I printed a shitload of paper using this piece of plastic… never had a problem… and not only that: printing with this printer is so fucking cheap!
(This printer support black & white printing using ONLY the black cartridge… it even works without the color cartridge in place! )

Windows Vista fully supported it and the vista drivers works perfectly on windows 7 too…

This trick works with many other peripherals that were supported by Vista but dropped on Seven…

What you’ll need:

• Windows vista dvd ISO (I used it_windows_vista_x64_dvd_X12-61200.iso)
• 7-zip ( http://www.7-zip.org/ )
• 1gb disk space

Ho to do it:

• open the ISO with 7-zip
• browse into the directory \sources\
• double click on the file install.wim
• browse into the \1\Windows\System32\ directory
• extract drivers and DriverStore directories somewhere
• connect the printer, when windows asks about drivers: point it to the directory where you have previously extracted the vista drivers
• done ^^

At this point you will have your PSC 2110 working on windows 7 (both printing and scanning are perfectly working)

PS: for even more cheap printing check out Cartucce HP PSC 2110

phpipblocker (last version 0.99j)
phpipblocker archive

php2dns (last version 0.91beta)
php2dns archive

nothing more, nothing less…

Valid alternatives: http://free-av.com/

If that can be done directly with a bash script it’s better

There’s a nice script to do it directly, it just need a little modification to run on CentOS:
http://jenders.vox.com/library/post/rtorrent-and-ssl-certificates-under-gentoo-linux.html

The first thing we need is openssl perl package (the one that have c_rehash in it)… you can get it with the command:

yum install openssl-perl

and then, just create the script:

nano -w import.cert.sh

1
2
3
4
5
6
7
8

#!/bin/sh
SITE=somesite.tld
 
openssl s_client -connect $SITE:443 < /dev/null 2>/dev/null | sed -n '/BEGIN CERTIFICATE/,/END CERTIFICATE/p' >> /etc/pki/tls/certs/$SITE.crt
openssl x509 -in /etc/pki/tls/certs/$SITE.crt -out /etc/pki/tls/certs/$SITE.der -outform DER
openssl x509 -in /etc/pki/tls/certs/$SITE.der -inform DER -out /etc/pki/tls/certs/$SITE.pem -outform PEM
c_rehash
unset SITE

make it executable:

chmod +x import.cert.sh

run it:

./import.cert.sh

and you are done, now you can eventually point your application to that certificate repository in case your app didn’t find it itself

for example you should run curl in this way:

curl -I --capath /etc/pki/tls/certs/ https://somesite.tld

With “crappy” I mean: broken/modifed images…

The worst example I had the opportunity to try was OVH.
OVH is in general a very good dedicated hosting provider offering very nice services at an impressive low price… but they have the bad attitude to install custom operating systems that many times cannot be reverted back to the original kernels

One of them is their CentOS 5 install… Lucky for us it’s not a big problem as, most times, it’s possible to do a clean CentOS install

This is a simple procedure to do an official, clean install from the genuine CentOS disks

1. Install CentOS from the OVH manager with the default partitioning proposed by OVH
   (this procedure will work with whatever operating system you want… i suggested centos so it will report “centos” also in the ovh manger make sure you are able to get grub working on the os you want to use )
2. once everything is done log into the box via ssh as root
3. issue these commands:

   1 2 3 4 5 6

   mkdir /centos_install cd /centos_install wget http://ftp.hosteurope.de/mirror/centos.org/5/os/i386/images/pxeboot/initrd.img wget http://ftp.hosteurope.de/mirror/centos.org/5/os/i386/images/pxeboot/vmlinuz cp vmlinuz /boot/vmlinuz.cent.pxe cp initrd.img /boot/initrd.img.cent.pxe

4. If you are not running grub (like all the OVH boxes) you need to install it:

   yum install grub

5. Add to/Edit the grub menu.lst entry to load the pxe kernel (note: if you were already using grub you do not need to type again the first 2 lines )

   nano -w /boot/grub/menu.lst

   in that file paste:

   1 2 3 4 5 6

   default 0 timeout 5 title Centos Install (PXE) root (hd0,0) kernel /boot/vmlinuz.cent.pxe vnc vncpassword=YOURPSW headless ip=YOURIP netmask=255.255.255.0 gateway=GATEWAYIP dns=8.8.8.8 ksdevice=eth0 method=http://ftp.hosteurope.de/mirror/centos.org/5/os/i386/ lang=en_US keymap=us initrd /boot/initrd.img.cent.pxe

   
   replace

   • YOURPSW with the VNC password you want setup
   • YOURIP with the ip of the box…
   • GATEWAYIP with the gateway assigned to your box

     Hint: you can see the gateway ip by issuing

     route -n | grep UG

   once you have done this, press ctrl +x, and save the file

6. again: this step should be done only if you were not previosly using grub!

   1 2	grub-install /dev/sda grub-install --recheck /dev/sda

   (adjust sda if you are booting on another device… all the OVH boxes I tried used SDA )

7. reboot

After issuing the reboot ping the box (should take max 2minutes to take up the network)… 30seconds (or more… depending how fast your box is) after it starts replying to the ping open a vnc client (on windows i suggest ultravnc) and connect to

YOURIP:1

put as password the one you placed as YOURPSW …

install CentOS

Tested on:

Success

• OVH kimsufi reloaded (Intel Celeron 220)
• OVH kimsufi reloaded xl (Intel e2180, Asus P5VD2-VM)
• OVH kimsufi reloaded xxl (Intel e7200, Intel DG31PR)
• OVH SP BestOF (Intel e6750)
• Keyweb KM 4400 DC (Intel e4500, Ati chipset IIRC)
• Intel i5 / p55 / e1000e eth
• OVH kimsufi Q-1T
• OVH kimsufi i7-2T (pxe kernel modification required: instructions, needs the eth attansic module)
• Dell R200
• Dell R410

Known problems

• If you didn’t follow exactly the how-to and did a custom partioning with /boot/ partition on it’s own you will have to take away the /boot/ path from the menu.lst …
• OVH netboot kernels might no more be able to boot into your box (even without LVM… dunno… maybe I did a too “base” install…)
• keep a vnc password short… most clients cannot auth with long passwords
• some ISPs may block incoming vnc traffic in that case consider to use the vncconnect=host:port (instead of vnc) trigger to have the server connecting to your PC (documentation: vncconnect )
• I had big trouble with certain servers not being able to run the CentOS 5.5 pxe install… on those I had to fall-back using the 5.4 install.. in case you want to use them you can find everything in here: http://vault.centos.org/5.4/: make sure to adjust also the mirror in the grub config file!

If not working

• If the box do not come up (ping) after the reboot… do a reimage and try over… double check the settings… expecially network settings.
• If the box does not works (not ping reply) and you are sure networking is set correctly try to boot vkvm to see if the PXE kernel is loaded properly to exclude any problem with the bootloader.

Random things

• http://dcantrel.fedorapeople.org/doc/vnc/VNC_Whitepaper-vnc-modes-in-anaconda.html
• http://fedoraproject.org/wiki/Anaconda/Options
• in this example I used the 32bit image… 64bit is exactly the same, just change the image you fetch at the beginning from the CentOS mirror and the mirror path into the grub config
• if you are running grub2 (like ubuntu 9.10) this is an example on how to set it up:

  sudo chmod +x /etc/grub.d/40_custom
  sudo nano /etc/grub.d/40_custom

  place in there something like:

  menuentry "centos.pxe" {
  set root=(md0)
  kernel /boot/vmlinuz.cent.pxe vnc vncpassword=YOURPSW headless ip=YOURIP netmask=255.255.255.0 gateway=GATEWAYIP dns=8.8.8.8 ksdevice=eth0 method=http://ftp.hosteurope.de/mirror/centos.org/5/os/i386/ lang=en_US keymap=us
  initrd /boot/initrd.img.cent.pxe
  }

  save and issue:

  sudo update-grub2