Yesterday, i had an abysmal user experience trying a book on usability in front of me. Since the write-up really was of most interest to the book store and the author of the book, i also informed them of what i'd gone through. In retrospect, i should also have included Adobe in the loop.

It didn't take long before i had a reply from Books-a-million's customer service saying they're sorry and they'd notified the ebook department and that i should be hearing from them soon.

[Update] The response was that yeah, they know these problems and they've written about them, and how to work-around them, in their FAQ. What about just fixing the problem? And since much of the problems stem from the Adobe's Digital Edidtions software, why not just scrap it and sell the book as unprotected PDF and ePub bundle? It's not like the customer automatically is a thief that you need to protect yourself from. [/Update]

The real honker was receiving a message from Mica Endsley himself (yup!), saying that they will take it up with the book store and that he would make sure i'd be getting a copy of the second edition, out this spring. Kudos to you, sir! While i'm still stuck with a fairly scruffy looking ebook, i feel that everything wrong is right again.

I bought an eBook today. It didn't go well. 

Ever since hearing a presentation mentioning a usability field i hadn't thought about, Situation Awareness, i've thunk about purchasing the book cited in the presentation: Designing for Situation Awareness by SA guru Mica Endsley. Turns out it is out of print, waiting for the second edition, and available at abything between US$50 + transport and the sky. The book is, however, available as an electronic book for the fairly decent price of seventeen bucks.

The page said it was a PDF, so technically i would be able to download the contents of the book and have it printed locally. Fair deal.

So i purchased my copy. The system said thanks, but was i sent a PDF? No. To access the book, i had to check my account in the bookstore and access the download link. While i appreciate the possibility to download a fresh copy in case i destroy mine, i would have liked to get something for my money. But OK, i got something, it was just hidden behind the bend.

I click the link, but is it for a PDF? No. The file is called URLLink.ascm and even Windows' file type "ask the web" magic wouldn't figure it out.

Turns out i need Adobe's ebook reader, Digital Editions. So i go to the download page. But do i find a download link there? No. But a flash application which warns me that downloading and installing stuff from the Internet can be bad for you. Still, i'm out to get myself the software so i ignore Adobe's warnings about its own software and press the OK-GO button. Twice.

But does that install the software? No. It downloads the installer. OK, fair enough. Let's have the installer. Launch it. Accept another responsibility so that Windows won't take the blame for irresponsible software installations. A Nullsoft based installer launches.

So i head for the command line to have a look at the mysterious .acsm file. Turns out it is an XML file with metadata about the ebook. And indeed there is a <src> tag in the file which points to a PDF file. Victory!

I open up Adobe reader and ask it to open the URL. Since the URL contains a fairly long GUID, it spans two lines, so i need to paste it into the File/Open dialog box in two rounds. After carefully checking out that i pasted the right URL, i click OK and Adobe Reader freezes.

I download GNU Wget to get the file locally; just the binary. It won't run on my box. I guess it wasn't compiled for Win7/x64 or i should take the full installer instead (18 megs of installer for a 187 kB utility?!).

So i ssh to a Linux box that does have wget, paste the URL again and download the file. Phew. I actually have the file even if it isn't on my computer. The file name includes the {fairly-long-GUID-string} so i rename it to Endsley.pdf and move it to that computer's ~/public_html and enter the URL from my web browser. 

Almost there.  

But does that get me the book? No. The browser considers the download for an unusually long time and finally greets me with information that i'm missing some security bit somewhere.

Next i tried with two PDF unlocking programs, GuaPDF and Parallel pdf password recovery to be able to actually read the file i've paid for. If i were in the States, i'd be violating the DCMA. Over here, i'm violating "Lex Nokia" which forbids me to transform the file from one format to another if i'm not supposed to. The first program told me that the PDF file uses 128 bit encryption so i should look at the latter. The latter is specifically a password crac... circumventing program and wouldn't even work without a password dictionary file. Not that it mattered, the file wasn't password protected. It was view-protected.

[Update - Whose victory?] In the end, i finally got Digital Editions installed. At the bottom of the Digital editions download page, there's a link suggesting that if installation fails, one should go and have a look. From there, there's actually an honest-to-Bob download link to the installer. I managed to fetch the installer. I ran it, as an Administrator. It installed. And instantly demanded to know my Adobe ID. To safeguard my library, i need to bless all the computers i intend to read Adobe-protected PDFs with or i can kiss my ebooks goodbye in case my computer blows up. Supposedly that means Adobe will kindly store a backup of the book on their servers. Or some signature allowing me to open up my own backups after the manure has hit the AC.

So i go and register for an Adobe ID which also fails because i've already got one. It used to be called Adobe Membership when i registered it a year and a half ago which explains why "adobe id" didn't turn up anything in my mailbox. It's not that Adobe told me that immediately either, it just said that the (optional) screen name "was taken" while registering. Would have been better just to check whether my registered email address was in their cold fusion database.

But i did get my Editions registered. And i looked very hard for a File -> Open feature to open my ebook. If you click on the menu button which really looks like a text label Library, a menu literally drops down with the option "Add Item to Library    Ctrl+O". So i do. 

But does that open my ebook? No.

I go back to the .acsm file that started it all. I click it. Nothing happens.

It is so hard to win.

[another update] Finally, after closing everything and clicking on the .acsm link, take a turn for the better. I do indeed get another error message, but after that, Digital Editions begin downloading the document. I still get error messages about some manifest XML and another Error that it cannot create a backup file (informs the dialog box, rounding it with an OK button. I ask what is it that is OK with the situation). Yet lo and behold i can in fact read the book! Only took me this many hours, this many fails and this many attempts.

What utter failage. I suppose i could count the fails here but it wouldn't make me any happier.

As long as the user experience for acquiring and reading a book is so abysmally miserable i just can't imagine paperless books ever taking over the world. I just hope the Kindle guys are doing this any better.

I should add that i bought another book from No Starch Press a few months back. It was also in PDF. And it opened without a hitch. And i even have a hardcopy version i had printed myself. I asked the guys at Nostarch first whether that was kosher and they said of course it was. I wholeheartedly recommend both No Starch and the book. I bought a "pure pdf" ebook on Cisco ASA configuration another while back. It opened and it printed and the author Harris Andrea even emailed me a month ago that he had an updated edition which i could download for free. So you can do this right. Or you can fail.

So down with formats that don't work. Down with copy protection that don't allow me to even read my book. And special reader software needed to read the file, software that doesn't even install. Come ePub and save the world. Come anyone and save us from this fail.

A tool i spend a lot of time with at work is Microsoft Outlook, as i guess it is with many of you as well. Often, i get mails that translate to initiating tasks. For that, Outlook can be used to create a Task, based on that mail, or set a follow-up flag on the mail, denoting that it's something to do. The vital difference here is that the flagged mail is the task, whereas a Task created from a mail is a copy of that mail. Finishing the Task will not have any input on the mail that was the source of the Task (before you get all weirded up, a Task is the Outlook-specific representation/implementation of a task, a Contact is a contact entity in Outlook. And so on).

Often, however, a single mail does not constitute the full communication and involvement of a task. The GTD school of thought calls any task with more than one action a project, which is fine by me. A project will usually include a minimum of two persons -- the requestor and i -- but more often have other stakeholders included. These stakeholders can be represented as Contacts in Outlook.

What i would really appreciate is to quickly and painlessly whip up a Project, which, if created from a mail, is tightly bound to the mail that the Project came from. A Project can have many tasks (or Tasks, if you will) and many Contacts. All communication, mail mostly, but could be IM as well, would be part of that Project.

I'm sure this could be done with existing tools -- OneNote or Groove perhaps -- but i don't know how. Do you? How do you manage your projects.. eh, Projects?

How do you map a network drive using Group Policy? You use Group Policy Preferences. No script required.

I got a pretty typical request from a client today. He'd hired a new employee, for whom i'd installed a computer a few days ago. One thing i hadn't done was to map to a network drive. Typical task, typical setting. I don't know why she (the new hire) didn't have the drive mapped but i promised him (my client) i'd fix it tonight. Which i did.

There are two ways to map a network drive:

1. the Stupid way, which is to log in on a computer as the user and map the network drive and set it to re-map between sessions (/persistent:yes)
2. the Ordinary way, which is to have a logon script run from the logon server, mandated by group policy.

There is also a New way offered on Windows Server 2008: Group Policy Preferences. Unlike Group Policy Settings, preferences are something that are suggested rather than mandated to the user, who may change the suggested preferences if so wanted. Another thing is that there are a bunch more preferences available than i'd found in GP Settings, and the one i was looking for was indeed the preference for drive maps.

For magic to happen, open the Group policy manager and create a new Group policy opject (GPO) where the users you want to target are. Call it Drive mappings. Go to User configuration -> Preferences -> Windows settings -> Drive maps. Right-click it and New -> Mapped drive. Set Action as Update (or Replace; see help file for info), fill in the UNC path (ie. \\server\sharename), give it a nifty Label and a Drive letter. And you're there. Repeat for other drive letters as necessary, creating other GPOs for other groups who have their own network drives. There's even variable substitution so you could probably map a drive for a group or a site or something equally local.

Given all this, drive letters are hopelessly outdated; it's just the fact that people are so used to them that it'll take a while for them to die out. And the same goes for home directories on the net. The Correct Way would be to have the venerable [My] Documents folder silently residing on the server and replicated for offline use (hint: use Folder Redirection), and any shared or common folders under the Libriaries meta-folder-thingy on the new and improved Windows 7 file explorer.

But that's for another time, when i've updated all their workstations to Windows 7.

These last five weeks i've been mosltly outside, and while i've been connected to the Internet, i haven't really been connected with it. And i could write more about it but as i'm still on vacation until the end of this week, i won't :)

No, wait, that's not right (except for the vacation bit, that one's true). It's true that i have not checked work email or been connected to the work network more than once, and i haven't spent vacation time tied do a desk. But i have used the 'net and in fact rather frequently. I've checked the weather on the road. I watched a classic sci-fi  flick from my TVkaista account in a hotel. I've spat out irrelevancies on Facebook and on Twitter. And i've observed that i've received mail and ignored most of it. I've played music with Spotify for my kids, watched some Manu Chao clips with my son on YouTube...

So yes, i have been connected with the Internet, even though it's been mostly as a consumer. But it's been good to have it around.

I wrote a generally applicable acceptable use policy for a computer environment for customers or companies that do not have one in place. What do you think of it? What should be added, removed, changed, fixed?

Version 0.1 DRAFT
This work is licensed under a Creative Commons Attribution-ShareAlike 1.0 Finland License

Written herein is some common sense on how you should be handling your computer and the environment in which it lives. Computers are fairly delicate tools and should be handled accordingly. Think of a lab, or a restaurant kitchen. You need to wash your hands, wear certain clothes and jump certain hoops to be allowed there, otherwise you're thrown out. But while this can seem obvious in environments like kitchens and labs, the corresponding may not hold true when it comes to computers and how to use them.

The most fundamental thing to have in mind is this: you at work is not you off-duty. When you can separate the work-you from the freetime-you, you've come a far way. If you want another parallel, think of your computer as a gun, or a fairly expensive car. Use it accordingly.

Your work computer is a tool for your work. Use it for work, only. Purchase a computer for you to toy with. It's fun and you can do whatever you want with it. So can your spouse and your children, who all should be kept at arms length from your work computer. Keep it clean. A contaminated computer can cause serious problems with business, which can be very expensive.

Use a hard-to-guess password. If your laptop gets stolen (yeah, it can happen, and not just to somebody else) make sure the bad guy only gets a chunk of fancy metal, not your company's trade secrets or a key to the back door of your office.

Your friendly IT support will worry about the well-being of your work computer. If you destroy it, contaminate it or do something foolish with it on purpose, negligence or stupidity, you will probably be frowned upon (if you wear a suit, you will be frowned upon after you leave), but you and your work computer will be taken care of. Your personal computer is off the IT support's radar and should be treated accordingly. Play with it to your heart's delight but don't call on your job's IT support to have it fixed.

Your work email address is for your work, only. Use a private email address for off-duty communications, when you don't represent your job. And should you change jobs, you'll still have your private email address. Do not forward "funny mails" from your job address within your organization (if you must, forward a link) and especially not out of it. It will make us look stupid and unprofessional.

Related to this, don't register to web sites or similar services with your work email address. Your work persona is not your off-duty persona and we have no intention making them one. And it's okay to surf porn, just don't do it on your work computer (piracy, on the other hand, is illegal). If you get a disease, at least you're not taking the whole company with you. Which, again, can be very, very expensive.

Your work's laptops, desktop computers, printers, servers (which you rarely see, but they do exist) and other things with blinking lights are connected together in a network. Simply put, what can be used on one computer on the network can be used on another computer, which is why not everybody needs a printer of their own, or an Internet connection. Since the network is a fairly intimate connection between computers, only work computers are allowed to connect to it. If the company's IT department can't carry the responsibility of its well-being, it shouldn't share the network with business critical data and applications. You wouldn't take a dog from the street into that lab or restaurant kitchen, right?

The same goes the other way. While you can VPN into the office, do that only with your work computer, never with an "unblessed" one. You can read your mail using webmail on any computer, though (remember to log off when you're done!).

All computers fail. It's not a question of if, but when. Laptops fail more frequently than servers. Thus, store all the important stuff you have on the server. Your computer may be set up so that your "Documents" folder really reside on the servers and a copy of them are invisibly made on your laptop. In that case, you're safe, as long as you save your documents into the "Documents" folder. If your computer gets driven over or falls from a high building (or a table) have things so that you can have a new computer and normality restored onto it.

That said, store only work documents on the server. Vacation pictures can be wonderful, but their place is not on company resources. Put them on a photo service on the web (Flickr, Picasa web, Photobucket), share and enjoy. Same goes for music files and, heaven forbid, videos. Your friendly IT support can open any file on the network (but won't -- they have ethics, and work to do).

As we share storage space on the server, we also share the Internet connection. If someboduy has a garguntian download or watch high definition video at work, others at work (who may want to do billable work) will have "a slower Internet".

If you blog or tweet, don't reveal your cards from work unless that is your job. Mentioning your work is okay, mentioning your work's particulars probably isn't. Mentioning your colleagues or your customers in bad light is definitely off the charts. If you feel iffy or unsure, it's probably in the not-okay-zone. The Internet has the memory of a herd of elephants.

And that's about the size of it. The Acceptable Use Policy can really be boiled down to "use common sense" and if you don't have enough of it, ask. "Stupid questions" are always better than ignorant behaviour.