My HP LaserJet P1606dn stopped printing duplex—here’s how I fixed it

HP LaserJet Professional P1606dn
HP LaserJet Professional P1606dn

I have an HP LaserJet Professional P1606dn, which has been great. It prints double-sided (duplex) — that’s the ‘d’ in P1606dn — and it connects to the network — that’s the ‘n’ allowing Jane to print wirelessly from her laptop.

The problem

But today… for some reason my P1606dn stopped printing double-sided. The option was still there in the printer properties—on the Device Settings tab, under Duplex Mode both “Allow Automatic Duplexing” and “Allow Manual Duplexing” were both ticked.

Hmm…

I tried changing various settings but nothing seemed to fix it. I checked if the driver had been updated. I rebooted the PC. Again, no improvement.

How I fixed it

I was actually in the process of trying to downloading the HP Smart Install software when I stumbled upon the answer.

If you have this printer, you’ll know that you can also connect to a configuration screen via the network. All you need is the printer’s IP address. Mine is at 192.168.1.73 on my local area network.

Tip: To find your printer’s IP address, press and hold the button with an icon of a sheet of paper with a down arrow on it. This will print the “Self Test / Device Configuration” sheet which shows under “Network information” the “IPv4 Address”.

Next, enter that IP address in a web browser address bar and hit enter to take you to the HP LaserJet Professional P1606dn network settings page.

Well, lo and behold, under the Settings tab there is a section called Paper Handling, and the Duplex option was set to Off. Changing it back to On fixed things for me.

HP P1606dn network settings
HP P1606dn network settings

At least, it did for the first document. I then discovered that (again for another mysterious reason) the next document’s paper settings were blank. Setting it to A4 restored the option to print double-sided.

So, in summary:

  • Check settings (Control Panel > Devices and Printers > Right-click the printer and select Printer Properties > Device Settings tab).
  • Connect to the printer settings via the network.
  • Make sure the print dialog shows the correct paper size.

At least, that’s what fixed it for me.

Update 1

Sunday 24 July 2016

I’ve come across the same issue today, but this time I’m not connected to a network, the printer is connected via USB.

To resolve this — I had a couple of Word documents that would only offer the ability to print duplex (double-sided) manually — I changed the page size to anything and then back to A4 and then made sure the margins were set to normal or wide, as I noticed that the document margins were oddly small.

Sunday 31 January 2021

Following kind feedback from a visitor, I have added information about how to find your printer’s IP address and then use that IP address in a web browser to access the printer’s network settings.

Update 2

Tuesday 7 November 2023

I’ve come across the same issue again today, but this time, I went into Printer Properties in the Word print preview dialog and under “Finishing” I noticed that the “Print On Both Sides” checkbox had been unchecked.

Checking the “Print On Both Sides” checkbox resolved this for me.

Backpack hack

Cabin Max Tallinn
Cabin Max Tallinn – Flight Approved Backpack for EasyJet & BA hand luggage

About a year ago I bought myself a new backpack, the Cabin Max Tallinn, for about £25. The reviews were favourable (average of 4/5 stars) and when it arrived I was delighted with it: mainly because it was more compact than the large rucksack that I bought for a trip to California about a decade ago.

I packed it and headed off to Glasgow and then London to seek my fame and fortune attend the first NYCGB Alumni choir singing day. It was a timely opportunity to road test the bag.

That four day trip identified two main issues. This wasn’t quite the bag that I thought it was.

However, I don’t like throwing stuff away, and I don’t like sending stuff back because it’s not 100% what I want it to be. This bag was about 95% the way there. I like the whole computer hacker culture (not to be confused with the illegal ‘cracker’) so…

Open zipped pocket

Zipped pocket that I've now sewn up
Zipped pocket that I’ve now sewn up

The first issue was that in the middle compartment there was a small, meshed pocket with a zip. I looked at that and thought it was the perfect size to store a passport, for example.

There was one small snag: the top of the zip wasn’t sewn down. So even when the zip was closed you could still slide items into the meshed pocket beneath the zip.

Who designed that?! It was like a shirt pocket with a redundant zip sewn into the top seam.

I wrote to Cabin Max and asked if this was a fault or a feature. It turned out to be a feature. I told them this was ridiculous and whoever it was I corresponded with agreed and said that she would pass on my feedback.

So I got my sewing kit out and completed the job: I sewed the zip down so that when the zip was closed it was… well, closed.

No inner straps

Cabin Max Tallinn inner straps
Cabin Max Tallinn inner straps

It wasn’t until a later trip last year that I realised there was another problem: if I didn’t pack the back completely full (as I had done for the London trip) then my clothes and whatever else I put in the large, main compartment just rattles around in there.

What this bag was missing, that every other rucksack or suitcase I own has, were straps inside that would allow me to tie down whatever I place into the main compartment.

So today I added my own. Having bought a couple of quick release tie-down straps online last week—the kind that people use for strapping things to their golf caddies (I believe)—this evening I measured them up (using the straps in my giant rucksack as a template) glued them in and sewed them down. Job done.

This weekend I’m heading to Sheffield for the second NYCGB alumni concert. I’ll report back how I get on with my two alterations to my bag.

Migration complete… but where are the images?

Trello board tracking the migration of my websites
Trello board tracking the migration of my websites

For much of the last two weeks I’ve focussed on two things:

  1. Redesign my website (garethjmsaunders.co.uk)
  2. Migrate that site, this blog, my SEC digital calendar site, and the NYCGB alumni website to a new web host (SiteGround).

I’ve managed to complete the project three days early… well, kind of.

WordPress… we have a problem

One unforeseen snag has been to do with the media (images, PDFs, zip files, etc.) on this blog.

I’ve been using WordPress since version 0.7 in 2003. During that time I’ve been uploading image after image, and as WordPress changed the way that it stored images I’ve experimented with different ways of organising it—even simply uploading the images to my server via FTP. I must have tried about four or five different arrangements.

For the most part, though, I’ve been uploading files directly into /wp-content. Occasionally I’d switch on the “organise my uploads into month- and year-based folders” option.

In short the organisation of media on this blog has been a mess, and I’ve always shied away from addressing it because… well, it worked.

When I came to consider migrating this blog from Heart Internet to SiteGround I did think about the media: would it be a problem if I simply transferred everything over as is and sort it out there.

I was a fairly tight schedule (it had to be completed by 20 January so that my Heart Internet hosting account wasn’t renewed) and I reckoned that since it worked fine at Heart Internet then it should work at SiteGround.

I was wrong.

cPanel and the mystery of the 1,998 files

SiteGround uses cPanel. As Wikipedia explains, “cPanel is a Linux-based web hosting control panel that provides a graphical interface and automation tools designed to simplify the process of hosting a web site.”

cPanel uses Pure-FTPd, a free (BSD licence) FTP server which by default shows up to 2,000 files in each folder. I found that out after the event tucked away in the cPanel documentation.

I had 3,688 files plus 10 directories in my /wp-content folder and I couldn’t figure out why it would only display 1,998 files and the previously  visible directories, such as /plugins and /themes had disappeared.

So…

I am manually working my way through the media library. Uploading files into the appropriate /wp-content/uploads/<year>/<month> directories and updating the database to tell WordPress where the files are.

For those files that were uploaded before there was such a good media library I’m using the Add From Server plugin to quickly import media into the WordPress uploads manager.

This is going to take a while, so please bear with me.

Update

Monday 19 January 2015

I’m making good progress already. I’ve fixed 360/700 images in the media library. That’s 51%, just over the halfway mark.

I’m finding it strangely satisfying getting this sorted out. A bit of website gardening.

The cobbler’s shoes, pt. 2

Back in April I wrote a post called the cobbler’s shoes in which I made the poor excuse that I hadn’t redesigned my website for 11 years because I had been too busy building sites for other people.

We also had three children in that time who turned out to be somewhat time-consuming, and they didn’t simply auto-upgrade on a one-click four month roadmap like WordPress.

The plan

I concluded with the following (slightly amended) plan:

  • Move to a new host.
  • Standardise URLs, which will also mean that after 11 years on a sub-domain this blog will move to www.garethjmsaunders.co.uk/shed/. (See update below)
  • Mobile-friendly sub-sites.
  • Use a content management system or two.
  • Delete a lot of content.

Of course, if you were to visit garethjmsaunders.co.uk right now you might just notice the tiny detail that erm… in the last eight months I’ve not quite managed to do any of the above.

The truth is that I delayed my plans for two reasons:

  1. My web hosting with Heart Internet wasn’t going to expire until mid-January 2015, they don’t offer pro-rata refunds, and I didn’t fancy having to buy hosting twice in a year; and
  2. the little matter of me getting viral meningitis in July in which I lost my sight for a couple of months. It turns out that I often relied on my eyesight for building websites.

So, this is it. Over the next month I’m planning to go through with what I’d sketched out in April.

Everything must go…

One of the things that I realise that I’ve dithered about while planning this is the “delete a lot of content” bit. I’ve got a lot of content on my site that hasn’t been updated in a long, long time (sorry). Some of it is out of date, but a lot of it isn’t but currently it’s too much for me to migrate neatly.

A lot has changed in the lasts 11 years. I no longer use a Psion (although I do still rather enjoy people emailing me about them) and I haven’t written a line of code for one for the last decade. Sadly I haven’t played mahjong much (except on the computer) in the last six years, since writing a book on it and, oh, our oldest children have just turned six—do you see a connection? And nobody really needs to read my poetry from the mid-90s, or essays I wrote at theological college, do they?

So it’s all going. Except this blog, and a few other bits and pieces. Some of it may make a reappearance at some point in the future, in a different format, but for now I need to clear the decks and give myself the space to focus on the projects I want to pursue next year, which is mostly writing. And getting well.

I just want to take this opportunity to especially thank the Psion and mahjong communities for your support over the years. I’m sorry I’m bailing out at this point but my priorities are currently different.

See you on the other side, which will now be at www.garethjmsaunders.co.uk/shed/ rather than on the ‘blog’ subdomain.

Update

Thursday 8 January 2015

After much deliberation I have eventually decided to retain my www.garethjmsaunders.co.uk subdomain. For a number of reasons:

  1. I was never really happy with my blog moving to www.garethjmsaunders.co.uk/shed/. If anything I’d want www.garethjmsaunders.co.uk/blog/ but that’s not possible in WordPress multisite other than importing the blog into the root site, and I wasn’t happy with that because…
  2. I want to keep the designs of my website and my blog different.
  3. I realised that my website and my blog serve two very different purposes and therefore I wouldn’t necessary want to tie both to the same content management system.
  4. My blog has been on the ‘blog’ subdomain since 2004, according to the WayBack Machine. If I moved the blog from that subdomain it would adversely affect search results and existing links to my blog. (I could of course use an .htaccess file to redirect traffic, but… it just seems unnecessary.)
  5. I visited a couple of other sites today who had their blogs on a blog subdomain and I thought that looked cool.

And so there you have it, for now it is settled. This blog isn’t moving… except, of course, it is. Because I’m going to move it very shortly to another server.

See you on the other side…

The sunk cost fallacy in action

Man sitting on a pound sign submerged in water, surrounded by sharks.
Source: iStock

Earlier this year I started to plan a major redesign for my website garethjmsaunders.co.uk — most of it hasn’t had a redesign since about 2003; it’s still built around a table layout!

In the process of redesigning the site I learned a really important lesson that in the long run has saved me hours and hours of development. It’s to do with the sunk cost fallacy.

A bridge too far

I’ve completed plenty of site designs in both my personal and professional lives. This was going to be no different. I did some initial research, sketched out the layout and features that I’d like and then looked around for a suitable premium WordPress theme that I could use. I settled on Bridge by Qode, which cost me US $58 (approx. GBP £35).

Bridge seemed to offer the features and flexibility that I was looking for in a theme. But once I had downloaded and installed it on a test site on my local development server I discovered just how complex it was.

At the time it offered around 10 demonstration sites to help you get to grips with all the possible permutations. It now boasts 42 ready-to-use demos.

I spent a good two to three weeks just installing demo sites and trying to reconcile what I was learning hands-on with the documentation. And at the end of that period, to be honest, I really didn’t feel that I was anywhere closer to understanding how I might use the theme. Bridge is a hugely capable theme, however, it simply offered too much for my requirements.

But I felt that I had to persevere, I had spent both time and money on it, after all. Surely it had to get easier if I installed another demo site, and read the documentation just one more time, and… presumably spent another 2–3 weeks trying to understand the minutiae of this theme.

Sunk cost fallacy

It was at that point I realised that I was falling into the ‘sunk cost fallacy’.

In economics, a sunk cost is any cost that has already been paid and cannot now be recovered. So in this example, I had already bought the Bridge theme. I had spent £35 and wouldn’t be able to get a refund.

The fallacy that I was falling into was that I was making decisions about the future of my site based on past expenses. Or as You Are Not So Smart puts it

[y]our decisions are tainted by the emotional investments you accumulate, and the more you invest in something the harder it becomes to abandon it.

I felt that because I had spent money on something, even though I was finding it too complex and not entirely suitable for the purpose I’d bought it — despite all that — I still felt that I ought to persevere and try to make it fit my needs.

What a divvy!

Divi

Freed by my decision to simply let go of using Bridge for this project, I went shopping again.

When I’d been looking around for themes to start with, I had narrowed it down to two: Bridge and Divi by Elegant Themes. So I bought Divi (USD $89 per year / approx. GBP £55).

In the long run that mistake has cost me money, but the time that it has saved me is immeasurable (or rather, I haven’t actually measured it).

The theme does exactly what I need and in a fraction of the time. I find the theme’s interface really intuitive, and the restrictions it puts on me (by not trying to do everything in every possible way) challenges me to be more creative with what I’ve got. Too much choice is a bad thing, remember.

Conclusion

The sunk cost paradox is certainly something to bear in mind the next time you need to make a decision: don’t necessary let past costs (time or money) influence your decisions about the future.

Lifehack has an interesting article about how the sunk cost fallacy makes you act stupid.