Picasa Web Album Download Foo

I must admit, I don’t use Picasa. I actually don’t like all these image organization and album programs. But somebody shared a Picasa Web Album with me that had some really nice pictures of my niece’s wedding.

These were nice pictures and I wanted them on my machine. So, lets get on it and download them. This is not so easy, if you are not using Picasa. And that is not so easy on Linux. And the album had way too many pictures to download them manually.

The Firefox extension, or add-on DownThemAll! and it’s companion DownThemAll! AntiContainer are your friends when it comes to Web Album downloads from Picasa.

Once you installed everything DownThemAll! offers you a plethora of download options. For Picasa’s Web Album you choose the RSS feed link from the sidebar. Right click on it and select “Save Link with DownThemAll!” or go to the “Tools” menu and select in the “DownThemAll!” menu the entry “DownThemAll!…”.

The latter gives you a little bit more control over what is downloaded. For instance, you can select just image files or JPEG images. Either way, select a destination folder and click the “Start!” button. Sit back and watch it download.

The only downside is the image quality. I have not found any way to get a higher resolution image. The Flash or Shockwave based viewer shows beautiful HiRes pictures. But what I downloaded is much worse. Not really bad. But everything but good.

So, if anybody out there has an idea how to download the original resolution image in a shared Picasa Web Album, then let me know. I am all ears.

But until then, happy downloading.

npm “error parsing json” Foo

I finally got a chance to update my test installation of Ghost. But as usual Mr. Murphy thought it would be a good day to say hello.

When running the installation using npm I got a ton of errors. Here an excerpt:

...
npm http 500 https://registry.npmjs.org/commander/1.3.2
npm ERR! registry error parsing json
npm http 500 https://registry.npmjs.org/methods/0.1.0
npm ERR! registry error parsing json
npm http 500 https://registry.npmjs.org/range-parser/0.0.4
npm ERR! registry error parsing json
npm http 500 https://registry.npmjs.org/buffer-crc32/0.2.1
npm ERR! registry error parsing json
...

As usual, I checked first if the problem was on my end. Of course it wasn’t. This was just an issue with npm and switching to a different server (in npm speak a registry) solved the problem. In my case the European server worked. Here the call to install Ghost using the European registry:

npm --registry http://registry.npmjs.eu install --production

Happy haunting.

Netgear PS121v2 Print Server Linux Foo

It is always fun to re-activate some old hardware. We had this HP laser printer sitting there with a Netgear PS121 (v2!) and it was just begging me to use it. So I thought, that is a quick and easy set up. Well it would’ve been if it didn’t have some nice surprises for me.

We had some other machines using that printer and it was an easy thing to get the configuration details from Windows. They all printed to a raw queue on port 9100. That sounds great. So I quickly set up the printer in a similar way using the PCL3 driver for the good old HP. The printer received data and started printing the test page. And it did a good job in starting it, but it printed only half the page. Afterwards the printer seemed dead. When I took a look at the print server I could see that it was switched off. Which is odd, because the print server does not have a power switch.

Anywhoo, I tried it again after restarting the print server. And I got the same result: Half a page printed and a switched off print server. A little bit digging on the internet revealed that I am not alone with that problem and that nobody knows how to fix it.

So I went with plan B and checked what ports are open so that I can try other options. Here is what nmap gave me:

Host is up (0.0078s latency).
Not shown: 993 closed ports
PORT     STATE SERVICE
21/tcp   open  ftp
23/tcp   open  telnet
80/tcp   open  http
139/tcp  open  netbios-ssn
515/tcp  open  printer
631/tcp  open  ipp
9100/tcp open  jetdirect

Nmap done: 1 IP address (1 host up) scanned in 0.17 seconds

That looked promising and seeing ports 631 and 515 made me happy. But I knew out of experience that IPP will be most likely a pain in the behind to set up. So I went with LPD, but I needed the queue. So lets get into the web interface and read the queue information.

If I would’ve remembered the password for the print server web interface this would’ve been an easy task. Brute force password guessing gave me, after a lot of swearing, finally access to the server’s interface.

In the Server Status page you can find the queue name in the field Default Name in the form of PS******. Now comes the part that is important to know. You have to add a _P1, the port number, at the end in order to get the full queue name. This is of course not mentioned anywhere in the user manual and without it, it won’t print.

So your URI for the print server will look something like this:

lpd://host.domain.or.ip/PS******_P1

Happy printing and don’t forget this applies only to v2 of the print server. The older v1 is supposedly a different piece of hardware with most likely different problems.

Ubuntu Sleep Foo Resolved… Finally…

The deed is done!

Finally!

If you don’t know what I am talking about, please read here, here and here.

I finally had the time to get down and dirty (literally!) and change the power supply. Well, the old one died on me and I had to replace it. Now the old 650W rests in peace while a brand new 850W does the job. And guess what, I was right. Replacing the power supply solved the “random” sleep problems of my server.

Finally I can watch TV, leave the office and do other stuff without having to fear that my server is in stand by.

And now to the next step. Get the OS moved to the new SSD. Not only a non-sleeping server, but also a fast one.

Although… my wife most likely to first clean the carpet…