Getting the Dell Laser printer C1760nw working on 64 bit Debian

I've just taken delivery of a Dell C1760nw from Amazon for just over £100 to replace the knackered inkjet which went before it.  As expected, getting the drivers working wasn't plain sailing, so for everyone else's benefit, here's what worked for me:

1) Download the 32 bit deb from here: http://www.support.xerox.com/support/phaser-6000/downloads/engb.html?operatingSystem=linux&fileLanguage=en_GB
2) Open a terminal as root
3) dpkg --add-architecture i386
4) apt-get update
5) apt-get install libcupsimage2:i386
6) dpkg -i xerox-phaser-6000-6010_1.0-1_i386.deb

7) /etc/init.d/cups restart

8) Navigate to http://localhost:631

9) Add a printer (Xerox Phaser 6000B v1.0)

10) Print test page

11) Celebrate.

Windows 8 developer preview - first impressions

Now I know why I bought a quad core CPU and 8 GB of RAM - to play around with fun new things, using the fantastic VirtualBox.

So I started downloading the Windows 8 Developer Preview from Microsoft onto my NAS box, and several hours later (yes, my broadband is rubbish), it had finished.  I gave my VM a couple of CPU cores, 3.5 GB of RAM and a 30GB hard disk, but you could get away with much less than that.

My first attempt to start the VM gave me a "failed to start 0xc0000225" error, so after a bit of searching I found I needed the "Enable IO APIC" Virtualbox option turned on.  I also needed to change the default network card emulation to an Intel Pro/1000 card as Windows didn't detect the default one VirtualBox chooses.

First impressions are quite good, although some screens seem to give you no obvious way of getting back to where you came from (until you realise you can move your mouse to the bottom left corner to get a menu).  Apart from the new Metro UI it looks very much like Windows 7 underneath, and the new Visual Studio looks identical to 2010 except for a new project types.  I look forward to playing with .NET 4.5 at work though, as the change list looks interesting.

I like the new settings pane which pops out on the right hand side and gives you context aware settings, and overall it seems quite smooth in operation, although some things didn't work on my machines, like the news app, and the designer for a new Metro Visual Studio application wouldn't load - but overall not bad for a developer preview.

I can't see it tempting me away from my GNU/Linux system though, due to the breadth of choice that a Linux system gives you, my idealistic views on software freedoms and because Microsoft will expect you to pay for it :-)

The Prey anti-theft system

After many mentions on LifeHacker and at work (thanks Mike!) I've decided to set up all my systems with the Prey project

This website and open source application allows you to register up to three devices for free, which check in to the website at regular intervals to verify they're still where they should be.  The moment you notice them missing (or stolen) you can mark that device as missing, and then the next time prey checks in, it'll be activated.

Prey can be configured to send emails, take screenshots, lock your system, and best of all, use nearby WiFi and geolocation to work out its location.  Read How I got my stolen laptop back within 24 hours to see it in action.

The free version offers support for three devices, which is just right for me (desktop, netbook and android phone) and supports most common operating systems, including (crucially for me) Linux.  You can pay for more devices and more features if you need to.

Set up on Android was dead easy, just download it from the market and enter your Prey username and password.  My two Debian Linux machines were slightly more tricky.

I run Debian testing on my desktop machine, and prey was in the repositories (apt-get install prey), but it seems to install it in /usr/lib rather than /usr/share (as the website says).  It also doesn't automatically set up the cron job that checks in every 20 mins.  My Crunchbang (Debian based) EEEPC netbook didn't have it the repos, so I had to download it from the website and unzip it to /usr/share/prey.

The command to install the cron job is in the README file (which I didn't read first), however everywhere in the documentation and the website seems to talk about an "installer".  I'm guessing that the installer is in the windows version (and possibly MacOS and Ubuntu) but I certainly can't find it in the vanilla Linux installer.  You therefore have to figure out what to put in /usr/share/prey/config and then ignore the warnings and create the device manually in the control panel on the website.

The API Key is (fairly) easy to find under the "Account" section of the website, but it took me a while to figure out that the Device Key is the bit in the url (e.g. the abcd12 in http://panel.preyproject.com/devices/abcd12) and NOT the name that you give the device when you set it up.  I'm sure if I was able to find the GUI installer that'd all be set up for me, but it's a shame that the instructions on the site seem to depend on this being there and they seem to ignore the manual set up route.

I'm still not sure if I've got all the config right, but at least the devices are reporting OK on the website and there's no errors in the logs.  Some more testing is needed to make sure it'll all work if I pretend it's been stolen.

So, I've spent a few hours setting up something I hope never to have to use, but I think it's worth it for the peace of mind.