Several users of the HP TouchSmart software suite have reported that they are unable to create certain kinds of notes in the HP TouchSmart notes program. I had an opportunity to investigate this issue today on an actual customer unit. The investigation details, while quite interesting to some, shall remain for some future post, perhaps. Here’s the conclusion:

If the user account you’ve created contains the ampersand character (aka. “and” symbol: &), the Notes application can’t save the “sticky” note kind. To-Do list notes are not affected by this problem.

The symptom is that you draw on the sticky note and then tap the Done button. Now the Done button will gray out, but the note won’t be saved and the creation surface won’t disappear. Only a tap on the Cancel button will make the creation surface go away (and without saving the note).

A workaround, if you want to use that Note feature, is to create a new user account that does not contain the ampersand (&) symbol. Renaming the user account is not enough, since the initial creation sets up certain things that can’t be changed later on. (After creating the new account, most of the user data needs to be copied from the old account to the new account so documents, pictures, etc. are available under the new account. For example everything from “c:\users\old&problem” needs to go to “c:\users\new-no-problem”.)

Until a proper fix can be developed and published, this is the only known workaround, unfortunately.

Categories: HP TouchSmart, Software, Vista
No Comments »

I had a very unpleasant experience today. My wife is trying to deal with pain in her arms and hands from too much typing by using Vista’s speech recognition feature along with Word 2007. She was writing a final paper for a college class and had just finished the last four of nine pages. That’s when she noticed an extra word in her paper, right at the end: “document”. It didn’t belong there, so she did what you’d do naturally and said “delete document”.

THAT’S WHEN BAD THINGS HAPPENED. Apparently the speech recognition software turned that phrase into a command and proceeded to empty the nine page paper of all content without hesitation. On top of that, the undo feature of Word seemed to not have noticed the command (or been bypassed somehow), so she couldn’t get the document back via undo either!

This all happened while I was in a meeting at work right before lunch. When I got back to my desk I had several panicked voice messages. Luckily, five pages from the day before could be salvaged because my wife had the presence of mind to close the document without saving, which let her recover all but the about four hours of work that had gone in before the disaster struck.

I went home over lunch to see if I could salvage any more. I decided that I needed support from Microsoft. Well, the call with Microsoft Product Support was less than pleasant (as support calls usually are) and didn’t get us the four pages back, either. Best I could tell nobody had ever reported such an issue before.

I’m surprised this glaring problem escaped all testing at Microsoft. One of the cardinal rules of software development was violated in this case: “Never, EVER, lose the user’s data.” I can’t believe there was no prompt to confirm if she really intended to delete everything in response to the phrase “delete document”. I can’t believe there was no undo possible.

I just can’t believe it. Yet, it’s true.

Categories: Microsoft, Personal, Software, Vista
No Comments »

Lots of people find that once they’re outside the touch optimized environment that the HP TouchSmart software provides, things in Vista are not all that easy to use with touch.

This is something we addressed with what we called a “Touch Optimizer” on the IQ770 (our first TouchSmart series). On the IQ500 series we initially left this program out of the factory configuration (the reasons would bore you, trust me.) Now we’ve brought it back as an update that you can get at the HP Support website: http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=pv-66423-1&lc=en&dlc=en&cc=us&lang=en&os=2100&product=3752240

This utility will increase several “non-client metrics”, as they’re called in Windows developer lingo, to sizes that make things easier to hit with your finger. If I remember correctly, the tool increases scrollbar, close/minimize/maximize buttons and taskbar quicklaunch icon sizes. It also turns on single click for desktop icons so you don’t have to double-tap to launch programs from the desktop anymore.

Until Windows 7 arrives with better integrated touch in the whole OS, try this tool and see if it doesn’t get you 60% of the way there. Maybe even 80%.

Categories: HP TouchSmart, Software, Vista
2 Comments »

One thing I haven’t written about yet is my impression of a few moments in Steven Sinofsky’s PDC 2008 keynote. It was when he talked about User Account Control. UAC was not well received when it was put in Vista, to put it mildly.

At around 45 minutes in the keynote, Steven mentions UAC and, as far as I can tell, pauses deliberately for a second or two to get an audience reaction. If you weren’t in the room at the time, it’s hard to tell, but there was a collective groan and some chuckling at that point.

I think it’s the closest attempt at trying to apologize for a design blunder I’ve ever seen Microsoft make, albeit without words. I found it to be a brave move for someone like Steven to make, and I wager that it put a more human face on the large, often faceless corporation that is Microsoft. It certainly did for me.

If nothing else it gave me the impression that there is someone at the helm of Windows development who is not afraid of acknowledging when things go wrong and who will try to make up for it. I find that very refreshing.

Categories: Opinion, Software, Vista
No Comments »

This is part 4 of the mini-series on the HP SmartCenter software. Hear about the team’s reaction to the Engadget leak and the launch plans at CES 2007. If you missed the first three parts, they are here, here and here.

—

One of the really unsettling events before the launch of the TouchSmart PC was that Engadget somehow got a hold of some pictures that had been prepared for the launch in early 2007 at the Consumer Electronics Show. It was billed in the first sentence as “AMD’s sweet new rig”, which was a little bit of a slap in the face, since most of the real work fell outside of AMDs realm. I remember the team meeting when our program manager came in and told us about the “leak”. He had heard it from Microsoft just a few moments before joining the meeting. The mood in the room instantly turned. People started feeling both mad at the leaked information (and the leaker) and depressed about the potential impact this would have on our launch at CES. Microsoft especially was disappointed, since the TouchSmart PC represented a big investment on their part, carrying some of the Vista messaging. The TouchSmart PC was to be billed as one of a few “dream” PCs at CES. Having gone through an experience like that, I now always think about how the people involved must feel when I see “leaked” information about upcoming products. It’s not fun to have it happen to you.

On a happier note, the TouchSmart PC seemed to make quite a splash at CES. At the last minute I was asked to attend the show to help with technical support on the show floor. This was my first time attending CES and going to Las Vegas, and I quite enjoyed the experience. I ran into quite a few of the people that had worked with us on the project, and it was fun to see the crowds milling about the TouchSmart PCs at the HP and Microsoft booths. Having backstage access was a unique thing, but it involved a lot of walking around, helping the people doing demos by making sure the software was installed properly.

Since then, the HP TouchSmart PC has received numerous awards (including spot number seven on PC World’s list of most innovative products of 2007) and for a short while even had a fan website, the HP TouchSmart Owner’s Club.

—

This is the tentative end of the series. If you’re curious about other aspects, let me know, and if I can talk about it, I’ll see if I can accommodate your curiosity.

Categories: Personal, Software, Vista, WPF
22 Comments »

Welcome to part 3 of this mini-series. Last time around you heard a little bit about the early prototypes and how things progressed from there. This time I’ll talk a bit more about some of the functionality in HP SmartCenter and some of the things we were not able to address before having to ship.

—

The guiding principles for HP SmartCenter and the other touch-optimized applications were to provide quick, “transactional” experiences, to have the applications be as intuitive as possible to use, and have them look polished and clean. HP SmartCenter was to be the “home page” for touch-based interactions with the PC. It had to easily give the user access to key Media Center experiences (TV, music, games) as well as two other touch-optimized programs HP was developing (HP SmartCalendar and HP Photosmart Touch). Finally the user had to have the ability to add access to a certain number of programs of their choice.

To enable some of the quick, “transactional” experiences using a touch screen, HP SmartCenter had to have large “target” areas that are easy to hit using a finger. This requirement helped making decisions about the layout of the “tiles” that the user touches to “launch” something.

We wanted to highlight a few of the key features of the TouchSmart suite of software. We decided that three tiles would be larger than the remaining ones, and that those three would be able to show more details from the underlying program than the smaller tiles. The calendar tile, for example, will pull three upcoming events out of the calendar program and display key information about those events right within the calendar tile. The Photosmart Touch tile will look for pictures in the My Pictures folder and display five of those in a rotation. The weather tile will display high and low temperatures expected for the day as well as the current temperature as reported by the weather service. The analog and digital clock tiles will display two additional clocks (probably configured for different time zones) in text form, in addition to the main clock, which is shown in a larger, graphical look.

The three user configurable tiles would be able to either start a program on the system or a web page, using Internet Explorer. We settled on only having three configurable items, since there was an overall limit in the graphical design at nine small tiles plus three large tiles, and we wanted to encourage people to stick with tiles that didn’t take you out of a touch-optimized / touch oriented environment.

Beyond picking a software development technology (WPF), our other challenges were the many changes in both Windows Vista and WPF as both matured. WPF introduced “breaking changes” several times in our short cycle, and we discovered numerous problems with the integration of WPF and Windows Media Center. We worked closely with Microsoft to get these addressed. But a few problems remained, one of which is that every time you start one of the programs we developed, the computer screen will go black for a few seconds. It gives you the unsettling feeling that something went wrong, but it’s actually a consequence of the interactions between certain software components that are controlling the graphics card (DirectX, WPF and Media Center). As much as we didn’t like it, we were out of time to address these problems by the time our shipping date came.

—

That’s a wrap for part 3. Next time you’ll hear about the reactions from the team when information about the TouchSmart PC was leaked to Engadget way before the actual launch event, and I’ll also talk a little about the launch at CES 2007.

Update (2008-04-30): Part four is now posted.

Categories: Personal, Software, Vista, WPF
No Comments »

In the first part of this mini-series, I introduced you to the early planning stages of HP SmartCenter. This time you’ll get a little more information on the early development, including a few screenshots of prototpyes.

—

I hacked together a very simple first version of HP SmartCenter (then codenamed LaunchPad, which still is the name of the executable, incidentally) in HTML and my colleague Maguy added some rough graphical elements to give our design firm an idea of what we were looking for.

My quick HTML mockup

Improved graphics

From about February 2006 until April 2006 we then iterated with our design firm on the GUI and user experience design. Towards the end of May 2006 we took final delivery of the work from them. I was to turn their beautiful work into a living application with page navigation, drag-and-drop functionality, configuration options, and settings persistence. They had provided a solid foundation to build on, including well thought out namespaces, classes, animations and navigation design.

But there was still a lot of work to be done during the next three to four months. In addition to the application itself I was also responsible for delivering an installer, a supporting “touch optimization” program, and integration with our factory PC build process, including dealing with the “sealing” process that prepares the master hard drive for replication.

We participated in Microsoft’s early adopter program for Windows Presentation Foundation and Windows Vista, which gave us access to builds of the WPF bits, with a seemingly never-ending stream of Community Technology Preview versions. Windows Vista was in a similar state of flux, and I had my hands full, wiping out and reinstalling test machines and updating my developer machine to keep up with the changes.

At the same time I climbed the learning curve for WPF (which Simon Middlemiss once described as more of a cliff), trying to figure out how to get the mostly fixed-content XAML pages that the design company had delivered turned into malleable components and re-configurable layouts.

The initial design from the outside company included two components that pull information from the web: weather and stocks. We had to drop the stocks piece for business reasons early on, and had big challenges working out the business issues for the weather feed integration. We wanted our own high-quality images to illustrate the weather conditions and had to get approval from the owner of the feed data. I thought several times that the weather feature was dead, but stubbornness overcame pessimism, and we pulled all the right people from several companies together to get our images approved within 24 hours before the final code submittal deadline. I remember pulling a work-at-home weekend to fine-tune the weather feature where I had to stop working because I was hit with the flu. I was out for three days. After something like that happens you don’t give up a feature without a fight.

One benefit of being part of the early adopter program for WPF and Vista was that Microsoft arranged for training and troubleshooting sessions. I made two trips to Redmond under this program, once to get more in-depth training on WPF and Vista, and once to get help with troubleshooting performance issues we had run into. That’s when I learned that there is such a thing as a “managed memory leak“, which can be introduced in WPF without the programmer necessarily realizing it. Towards the end of the program three of my colleagues and I got to spend a couple of days with Microsoft again, this time at their Platform Adoption lab (Building 20), going over some last minute design and performance questions with their WPF developers one-on-one. This especially helped with getting HP Photosmart Touch into better shape for final release. We got a lot of tips and strategies for dealing with images, collections and containers in these sessions.

—

That’s it for part 2. Next time I’ll dig a little more into the guiding principles that were used for the implementation of HP SmartCenter, as well as some of the challenges and problems I encountered on the way.

Update (2008-04-30): Parts three and four are now posted.

Categories: Personal, Software, Vista, WPF
2 Comments »

I thought some people might enjoy reading a little “behind the scenes” story about the most high-profile piece of software I’ve been involved with so far. I feel pretty lucky to have had the chance to work on a unique product and to have what I helped work on be so central to the user experience as it is on the HP TouchSmart PC. You may interpret this post as highly egotistical and self-centered, and I suppose it is. But I feel like telling a story. My story. I will go over most of the non-confidential details of the events as I remember them. Since there’s a lot to talk about, I’ve decided to split the story into a mini-series. This is part one. Here we go.

My involvement with the HP TouchSmart PC began in about December of 2005. The decision was made to invest in software that would be best suited for the touchscreen that the unit would have. One of the results is HP SmartCenter as seen here (screenshot from my developer machine, not necessarily representative of the final product):

We had tight deadlines. Our final bits would be due in about six months, around June / July 2006. Our product marketing folks decided they wanted the touch application to provide quick access to TV and music as primary features. Windows Media Center was our software of choice for delivering TV and music experiences, and so we made HP SmartCenter run within Windows Media Center. This helped to avoid waiting for Media Center to start up when the user wants to watch TV or listen to music. In other areas the choice created lots of challenges. The initial one was picking a software development technology.

I had just attended PDC05 and was pretty excited about Windows Presentation Foundation (WPF) and the speed I could sense it would give developers and designers for rapidly creating exciting software. I had learned that Media Center in Windows Vista would support WPF, and my recommendation to use it for our apps to make the deadlines while delivering a polished user interface was accepted.

An interface developed in HTML would not have had the same quality (read: look-and-feel). Using the Media Center Markup Language (MCML / SplashFX) was not an option, since that was not going to be revealed in any useful detail until about March 2006, way too late for us to learn how to use it and produce a product.

At PDC05, it had been mentioned that a well-know design company had worked on some XAML styles for the show. We approached them to help out with the application design and asked them to deliver their stuff as working XAML / WPF code. They were pretty excited about the idea and signed on.

—

That’s it for now. Check back soon for the next installment of this mini-series, where I’ll show you a few screenshots of very early prototypes.

Update (2008-04-30): Parts two, three and four are now posted.

Categories: Personal, Software, Vista, WPF
9 Comments »

[Update 2008-07-24: This is now one of the most popular posts on my blog. Seems to me that a lot of people are having issues like this. Unfortunately there only seems to be a solution for Sony systems; look through the comments to see it .]

[Update 2008-11-29: I've looked around a bit more. The chipset used in the HP laptop is of the "Waikiki" Conexant HD audio variety, according to this forum post. Apparently there is an online petition, asking for HP  to release an appropriate driver, since some of the notebooks that use this chipset were marketed as "Vista Capable". The "Venice" chipset variant, apparently, is covered by updated drivers.]

[Update 2 2008-11-29: I think I may have found a package that solves my particular problem. I've put the computer to sleep several times now, and each time sound came back properly after waking it up again. The thing that seems to have done it is something called a UAA Bus driver. I got it directly from the HP FTP site here: ftp://ftp.hp.com/pub/softpaq/sp33501-34000/sp33867.exe There's also an article around the SP file here: http://h10025.www1.hp.com/ewfrf/wc/genericSoftwareDownloadIndex?softwareitem=ob-47284-1&cc=us&lc=en&dlc=en. I'm not sure this will help your situation, but it helped mine (so far, keeping my fingers crossed, maybe I'll run into other issues with it.) The article says it's for XP, but it seems to have worked on Vista SP1 as well.]

I have a laptop that has an issue with properly restarting the sound subsystem after Vista resumes from sleep. Microsoft brought out a hotfix about 6 months ago that supposedly fixed issues like this. On my system, the problem persists, even after installing Service Pack 1! I let the computer go to sleep, and when I wake it up again, there’s no sound. The sound device is listed in Device Manager as “High Definition Audio Device” and has the following Hardware IDs:

HDAUDIO\FUNC_01&VEN_14F1&DEV_5047&SUBSYS_103C30A5&REV_1000
HDAUDIO\FUNC_01&VEN_14F1&DEV_5047&SUBSYS_103C30A5

I’ve tried just restarting the sound services (as admin: net stop “Windows Audio”, net stop “Windows Audio Endpoint Builder”, net start “Windows Audio Endpoint Builder”, net start “Windows Audio”), but that doesn’t work. Restarting the computer works, obviously, but is too slow to be a proper solution.

One thing I can to do to get sound back without restarting is remove the “High Definition Audio Device” from Device Manager and then Scan for Harware Changes. But it’s still annoying to have to do this. Since there’s no crash involved (no Windows Error Reporting possible) and no “yellow bangs” in Device Manager, I’m not sure how I would report this to Microsoft. They probably wouldn’t do anything about it anyway. They’d say it’s a driver issue. Talk to the driver vendor. Nice idea. Trouble is the laptop is older (it scores a 3.2 Windows Experience Index, not half bad) , and the vendor probably won’t bring out Vista drivers for it. So it looks like I’m stuck with a broken package.

Maybe a kind soul (at Microsoft?) will read this at some point and get in touch to help me troubleshoot the issue.

Oh well. Feels good to get it off my chest, though.

Categories: Software, Vista
38 Comments »

Vista Service Pack 1 is in the can. It’s no coincidence that Vista SP1 and Server 2008 are “here” at the same time. They’re one and the same apart from the differences in “configuration”, i.e. Client vs. Server stuff. Server 2008 is the product that should have been released in a “Client” version under the Vista branding, but Microsoft caved to enormous pressure from the market and released it a little over a year too early.

Microsoft undoubtedly knew they could never afford to release a Server version in the state the code was in at Vista release. Corporations running mission critical things on Server would never adopt anything not rock solid. So Microsoft took the time they should have put into the “Client” version to finish things off properly for Server. Hindsight 20/20 and all that.

What can be expected of Windows “7″ after this? My guess is Microsoft will cave to market pressure again and release something not quite ready for the consumer market. With Vista, part of the reason for releasing too early was that Windows XP seemed to be getting too old. For Windows “7″ part of the reason will likely be a perceived need to catch up with Apple’s OS X.

With Vista, Microsoft was incredibly open about providing early builds to lots of people in order to get the quality right. And yet it wasn’t enough. It also seems that the biggest “achievement” that came from the openness was that people weren’t much impressed when the final product came out. In my view that’s a bit of a shame, because there are lots of truly great innovations in Vista (one of which is WPF). Microsoft will probably be more tight-lipped about Windows “7″ as a result. They might take a more Apple-like approach and keep things secret until the last minute. Surprise the world when they release Vista’s successor.

The problem is that Microsoft doesn’t seem to understand what it is about Apple’s offer that makes it so compelling. It’s not OS X. It’s not iLife or iWork. It’s how it’s all wrapped up in an end-to-end package. Beautiful, well performing hardware; good OS; good everyday software with features that people find useable and useful, integrated with revenue generating .Mac Internet services. And all because Apple has control of the entire chain, from hardware to software and services. Heck, they even control the retail experience.

Microsoft doesn’t have an answer for that. They play a different game. They play in many arenas and with many, many different partners. The ecosystem Microsoft provides the basis for is much, much bigger than Apple’s. Microsoft can never be Apple. And I don’t think they should even try to be.

I’m hoping that Microsoft will not cave in to market pressure but chart their own course for Windows “7″. Perhaps kick off work for another “NT” project (from the Dave Cutler/NT 3.x days) and focus on creating an operating system that is focused on the total consumer experience. Throw away all backwards compatibility in the consumer market, if needed (ironically, sort of like Apple did for OS X.) Provide backwards compatibility through virtualization or by keeping a separate line for corporate mission-critical applications. But mainly chart a course that doesn’t look too much at Apple or Linux or anything else, but follows new visions for what can be done with software running on ever more capable hardware. They have enough smart people to lead the way. There’s no need to follow anyone.

Categories: Opinion, Vista
2 Comments »