OK – here’s the scenario.  You work for company that has a few thousand employees.  The standard desktop currently has Windows XP on it.  And you wonder – should I start migrating to Vista now, or should I just wait until Windows 7 is released and deploy that?  After all, Vista got slated in the press but Windows 7 is getting rave reviews – surely that is a better move?

For my money no.  The short answer I give customers today is to ensure that they are buying Software Assurance so they are licensed for Windows 7 when it releases, but start deploying Vista where it adds value today.

There are two may reasons advice.

1. There are features in Vista that some of your users would benefit from today.  Starting your deployment with these low hanging fruit adds immediate value.
2. Your transition to Windows 7 will be eased significantly if you have already rolled out at least some Vista machines.

Lets look at those in more detail.

Add Value for the Low Hanging Fruit

Firstly – let me be clear.  Being a low hanging fruit is in no way a bad thing.  In our company I’m one!  What I mean by this is that there are some features in Vista that add immediate value to some users in most organisations.  For example I am a highly mobile tablet user with some commercially sensitive data on my machine.  As such the improved power management, fast sleep and resume, much improve handwriting recognition and BitLocker are quick wins for users like me in most organisations.

Easing Your Transition to Windows 7

The transition to Windows 7 will be easier from Vista than for Windows XP. Under the hood there was a significant change between Windows XP and Windows Vista.  The change between Windows Vista and Windows 7, however is relatively minor. 

Architectural changes in the operating system lead to driver and application issues.  As the architectural changes are cumulative the jump from XP to Windows 7 is slightly larger than from XP to Vista.  But if you start the transition to Windows Vista now, you can address the application compatibility, driver and hardware issues you will probably have now.  If you get all your applications running on Windows Vista then for the most part they will also run on Windows 7.  With a few exceptions if there is a Vista driver for your hardware it will work on Windows 7.  If your hardware will run Windows Vista it will run Windows 7.

The last point to note is that if you are planning for a Windows 7 deployment you can put  in place Microsoft Deployment Toolkit environment based on the MDT 2010 beta to deploy Vista and use this same infrastructure to deploy Windows 7 when it releases. This would allow you to build the skills to create, maintain and deploy standard builds and these skills would be transferable to your Windows 7 deployment

In Conclusion

Don’t wait.  If you are on Windows XP now, start deploying Vista to those who will benefit most.  This will add immediate value to your business and ease your transition to Windows 7 when it is released.

While I was pleased to see that there was, after a fashion, native ISO support in Windows 7 as I’ve previously noted it does not go far enough.  I have been seeing in my blog’s logs lots of referrers coming from searches for the likes of “Mount ISO in Windows 7”.

Here’s the bad news – Natively, you can’t. 

Here’s the good news – the key word there was natively.  You can mount ISOs in Windows 7 and previous versions of the OS, you just need to use a third party tool to do so.

My ISO Mounting tool of choice is Virtual Clone Drive by SlySoft.  I like it because it is light weight and easy to use. It is also free – but that is not a reflection on quality.  It is an excellent advert for SlySoft’s paid offerings like CloneDVD.

After downloading and installing Virtual Clone Drive (and I find rebooting is a good idea) you will find that you can mount an ISO file just by double clicking it (if nothing else is associated with ISO files) or by right clicking it and selecting Open With > Mount file with Virtual Clone Drive.

Once mounted the ISO will show up as another DVD drive in Explorer.  If autorun is enabled this does, of course work as well.

There is also a management application where you can add additional virtual drives or change the UI language.

Don’t ask me what the Virtual Sheep do – but it is a checkbox I’m sure some of my Aussie mates would tick ;)

According to the website Virtual Clone Drive supports the following Operating Systems:

Windows 98/98SE/ME/2000/XP/XP64/VISTA/VISTA64

I have found it runs fine on Windows 7 build 7000.

As I previously mentioned I am putting together a Microsoft Deployment Toolkit (MDT) environment to enable me to rebuild my Vista machines at will. 

I now have  a Windows 2008 Server machine running inside of Virtual PC that is a self contained MDT environment.

To do this I had to configure the Server with the following services.

• Active Directory - I promoted it to a domain controller in its own domain.
• DNS - required by AD
• DHCP - to give out addresses, required by WDS.
• Windows Deployment Services (WDS) - this is an optional Windows Component you can add on Windows Server.  WDS responds to network boot PXE requests from clients and sends them a Windows Pre-installation Environment (PE) boot image.
• MDT.

There are a number of other components that MDT needs to be able to deploy anything, but it is ridiculously easy to add these in.  The main management console of MDT is the Deployment Workbench, which contains a node in the navigation pane called components.  Clicking on that shows the current install status of the various things you need and you can download and install them inside the Deployment Workbench.  Click the image below to see what this looks like.

Once all the required software is in place it is a matter of creating a distribution share, adding the OS images (which you can do by right clicking Operating Systems and selecting New..  You then just pop in the CD and follow the prompts in the wizard.) and creating a build.

Another cool thing with MDT is you can import drivers in much the same way as operating systems.  These can be added to the build so that they are inject into the image before the hardware detection takes place, so if you have more recent drivers than those included with Vista you can insert them and it will never load the older driver.  Much cleaner.

To do this you right click on the Out-of-Box drivers node in the Deployment Workbench and select New...  This will launch a driver import wizard.

You fill in a path and optionally assign one or more groups that the drivers will belong to and then click Finish.  MDT will search the directory and any sub directories and import any drivers it finds.  Also by default, when you build your boot image it will include all Network and Storage drivers so that you should have the bare requirements to perform a network install once the Windows PE image boots.

I've got my build going on the Acer laptop I've been testing against to the base OS level with no input required from me beyond pressing F12 to initiate the network boot.  Now it is time to start working on the applications.

The MDT Team has a blog - so if you want to find out more that might be a good place to start.

Two of my machines are in desperate need of a rebuild.  Because it has been on my to-do list for a while I am going to look at Microsoft's updated desktop deployment solution accelerator - the Microsoft Deployment Toolkit (MDT).

I have used the previous solution (BDD 2007) to automate Vista builds in the past.  The constraint with BDD was that it could only do the desktop OS. 

MDT is an updated version of BDD that can deploy desktop and server operating systems.  There was a wealth of information in BDD, so I am looking forward to getting hands on with MDT to see what is there.  From the overview blurb:

Microsoft Deployment provides proven tools and practices with which IT professionals can:

• Create a software and hardware inventory to assist in deployment planning.

• Test applications for compatibility with Windows operating systems and mitigate compatibility issues discovered during the process.

• Set up an initial lab environment with imaging and deployment servers.

• Customize, package, and deploy applications.

• Automate image creation and deployment.

• Manage processes and technologies to produce comprehensive and integrated Lite Touch Installation (LTI) and Zero Touch Installation (ZTI) deployments.

• During deployment, migrate users’ documents and settings to their new computer configurations.

• During deployment, Microsoft Deployment supports the installation of all Roles such as Active Directory® Domain Services (AD DS), Domain Name System (DNS) server, Dynamic Host Configuration Protocol (DHCP) server, Microsoft Internet Information Services (IIS), Windows Deployment Services, Windows SharePoint® Services, Windows Internet Naming Service (WINS) server, and Windows Server® 2003 Terminal Services. Additionally, Microsoft Deployment supports the configuration of the AD DS role.

• Ensure that computers are hardened to improve security within the environment.

Microsoft Deployment brings together time-honored and proven practices in addition to the following Microsoft technologies:

• Application Compatibility Toolkit (ACT) 5.0 for gathering application inventory and for testing and mitigating application-compatibility issues

• Windows User State Migration Tool (USMT) for migrating user settings and data

• Windows Automated Installation Kit (Windows AIK) for configuring unattended Setup answer files (Unattend.xml) and capturing images

• Windows Deployment Services for starting Windows Preinstallation Environment (Windows PE) on target computers across the network

• Windows PE 2.0 for starting computers

As I write this I have a new Windows Server 2008 Standard virtual machine installing in Virtual PC that I plan to use as the deployment server.  After that is installed I'll be installing MDT.  Stay tuned.

For my money UAC is a good thing Or rather it is a painful and annoying intrusion, but there is a good reason it is there. It helps to address a very real threat. But, I've often thought that it should have a way to mark an app as trusted, so it always runs as admin without prompting. Thankfully the how-to geek has a way.

Create Administrator Mode Shortcuts Without UAC Prompts in Windows Vista
One of the most talked about annoyances in Windows Vista are the UAC prompts that constantly pop up when you are trying to make system changes. It's especially irritating when you often need to run a particular tool that requires administrator mode in order to run. Thankfully there's a simple hack that you can do to create an administrator mode shortcut that doesn't prompt for UAC.

Read More...

Great tip!

This morning I was fortunate enough to have a one-on-one chat with Motion Computing's President and CEO, Scott Eckert.  Thanks for all those who posted comments and questions on my blog and on GottaBeMobile.  Rather than pose every question directly (as there were quite a few) I looked for the common themes in the comments and constructed questions from those. 

I met Scott in the foyer lounge of a Sydney Hotel.  We chatted for a couple of minutes about Sydney, the appalling weather and work, then got down to business.  He was pleased that I was taking notes on my LS800 at the meeting and allowed that he used one himself for two years.  This led nicely into my first question.  What follows is summary of my discussion with Scott.  This is not a verbatim transcript as I did not record the conversation.

--

Of the 12 comments posted on the two blogs (excluding the one about taking Scott hostage until he included ice cube makers - which we both took as a joke) fully 4 of them mentioned the LS800 directly and two others mentioned a desire for a smaller tablet.  When the LS range was dropped there were a lot of people who were very disappointed, myself included.  In my view Motion created and owned the Ultra Mobile category before the UMPC label even existed.   Given that there is an apparent market for these devices and that they were, and still are,  a device that really turned heads and got people interested in Tablets - why was it dropped?

In response Scott was pleased that I was crediting them with creating a category.  Their goal was to create a truly enterprise class UMPC and he felt that they had done well with that.  He also indicated that while the LS800 did enjoy some success in certain areas that it did not achieve the volumes needed to sustain it as an additional range.  That said the market for this type of device is still there and Motion is keeping an eye on it, there is ongoing R&D and as pen, touch and other technologies mature it is an area that they may re-enter.

Next I said that to me it seemed that sometimes Motion was focusing more on winning new customers than looking after their existing customer base.  Two examples I held up to support this.  The first was the inability to migrate accessories between ranges - such as the M-series range and the LE-series range.  The second was the relatively poor upgrade experience that Motion users had going to Vista. 

On the first point Scott pointed out that their ranges are expected to exist for about 3 years before being replaced by a new range.  They try to ensure consistency in the range, but in order to take advantage of rapidly advancing technology they won't necessarily have compatibility of peripherals between ranges. 

I suppose that this helps Motion evolve their products more quickly as they are not constraining a new range with the limitations of the old. 

Scott also pointed out that while accessories for previous ranges are not necessarily compatible, they are supported and spares are available long after the range stops shipping, which also helps to mitigate the issue for their enterprise customers.

On the second point Scott acknowledged that the Vista upgrade experience had not been all that smooth for end users.  They have learned from the feedback and hope to do it better next time.  He also pointed out that many of their enterprise accounts are still deploying XP based images on their Motion tablets.

There seems to be an increasing focus on verticals with the specialized range expanding and what I consider to be the general use/corporate range shrinking.  Is this going to be a trend that continues?

Motion are really highly focused on the verticals.  In fact when I was chatting to Scott this was very apparent long before I asked this question.  Scott told me that the way Motion look at it is that they have two primary verticals and three product ranges.  The vertical markets they are focused on are healthcare and field automation and the three product ranges can be applied to both of those.

This is not to say that there are not other niches and verticals that don't suit the Motion tablets.  Indeed some of the successful markets have come as something of a surprise to Motion.  The LS800 enjoyed quite a bit of success in the aviation market, and this was largely driven by a software partner who married up his software, the LS800 and a mounting solution and sold this as a bundle.

What other verticals interest you?

Motion's primary focus has always been people who need to use a computer while standing and walking. 

One of the questions that came up was around a slate for artists - any plans to enter that market?

Scott thought that the artist market was pretty well served today by the likes of the Wacom Cintiq which is not mobile, but it provides a much higher resolution and a better digitizer than what is available today in mobile devices.  There may not be too many mobile artists, but many of the ones that are out there are using the LE range devices today with success.

There were a couple of questions around multi-touch.  Motion was leading the market there - what happened?

The technology was very new and Motion just struggled to get it commercialized.  Touch, and the combination of touch and an active digitizer, is and will continue to be an important technology for future ranges.

(reading between the lines I take it there won't be one in the LE range, though I could be wrong.)

Motion also feels that for touch to really succeed it is critical that the applications are designed for and work well with touch.  This led nicely to my next question.

Again - from the questions posted is there any thought of entering the software market to help bring that about?

The short answer is that Motion is not looking to become a software house.  However Motion are already active in that space and they currently work with about 150 software partners in the vertical markets to help them write better applications.  It is better for Motion to have more partners and to work with them rather than compete against them.

This is where Scott talked about the aviation example and how a partner created a market for the LS800 and did really well in it.  Naturally Motion would like to find more partners like that, so for those of you reading this that write software - keep that in mind!

There are some general issues that most mobile users face, such as battery life and heat.  There are also some technologies that seem to be taking a long time to come to market, such as hybrid drives or that still carry a significant premium like solid state drives.  What do you see as the most important technologies coming.

Battery technology is really a chemical process, which means that adding capacity to batteries is not easy.  Motion have found it more fruitful to reduce the power consumption of the device and this is where they are investing.  This means both engineering better, more efficient hardware, adding technologies such as LED backlit displays and working with application developers to make the applications more efficient.

--

Some closing thoughts from me.  Scott is a genuinely nice guy and I really enjoyed my chat with him.  He is astute, passionate about his products and focused on the vertical markets and the Motion vision.  Motion are not merely aware of the bloggers, readers and commentors that make up the blogosphere.  They are not just listening to the conversations.  They are actively reaching out and engaging and I think that is a really good thing.  Thanks to Scott for taking the time to talk to me.

I have been living with the fact that SD Card reader on the LS800 does not work under Vista since I installed Vista last year.  However I recently had a conversation with a Motion Computing employee in which he indicated that he thought that issue had been solved.

Full of hope I rushed off to check the knowledge base article on the Motion site that documented the issue to see if it had been updated...

There is no SD card reader driver available for Windows Vista on the LS800/LE1600 at the time of this writing (1/29/2007).  Motion is working to provide this driver as soon as possible.  This knowledge base article will be updated at the time of the driver update.

Hmmm, still no joy.  However - while I was on the site I thought that I might as well see if there were any driver updates available.  Why OEMs don't put an RSS feed on their drivers page is beyond me.

While poking around I realise that there have been two BIOS revisions released since my version.  I'm was running A09 and A14 and A15 are on the site.  What happened to A10-A13 I wonder?

Nevermind.  I check the release notes for the two new BIOS releases.  Low an behold the Release Notes for A14 state:

What's New In This Release

· Support for Intel 1.1GHz processor

· Support for SD card reader in Vista

I check the release notes for A15 as well, nothing major in that one except one fix.  However BIOSes are cumulative, so A15 includes everything A14 had.  To avoid having to do two upgrades I flash the BIOS with the A15 version.

After a reboot I can see that the SDA Host Controller is listed in Device Manager without the little yellow exclaimation point it had before!

Full of anticipation I break out a SD card and slot it in.  **Poof**  Bluescreen of death.  Interesting.  I reboot and try it again.  **Poof** again.  Well at least the fault is repeatable...

Time to break out the Windows Debugging Tools to analyse the crash dump.  Not for the faint of heart.

After repeating this a few times and analysing three dumps I see the debugger pointing to three different drivers. None of which are the SD Card driver.  Given the highly repeatable nature of the fault I think it is clear that it is related to the SD Card Driver, so my guess is that the SD Card driver is corrupting bits of memory, which causes an exception when some innocent driver wanders along and falls into the whole.  Believe it or not - this is progress.

I have come across a command line tool in Vista that has some potential in the fight against the dreaded Vista Insomnia issue.

The tool is called powercfg.exe and there is a TechNet article about it here.

Running powercfg /? provides the following usage information.

POWERCFG <command line options>
Description:
  This command line tool enables users to control the power settings
  on a system.

Parameter List:
  -LIST, -L   Lists all power schemes in the current user's environment.

              Usage: POWERCFG -LIST

  -QUERY, -Q  Displays the contents of the specified power scheme.

              Usage: POWERCFG -QUERY <SCHEME_GUID> <SUB_GUID>

              <SCHEME_GUID>  (optional) Specifies the GUID of the power scheme
                             to display, can be obtained by using powercfg -l.
              <SUB_GUID>     (optional) Specifies the GUID of the subgroup
                             to display.  Requires a SCHEME_GUID to be provided.

              If neither SCHEME_GUID or SUB_GUID are provided, the settings
              of the current user's active power scheme are displayed.
              If SUB_GUID is not specified, all settings in the specified
              power scheme are displayed.

  -CHANGE, -X Modifies a setting value in the current power scheme.

              Usage: POWERCFG -X <SETTING> <VALUE>

              <SETTING>   Specifies one of the following options:
                          -monitor-timeout-ac <minutes>
                          -monitor-timeout-dc <minutes>
                          -disk-timeout-ac <minutes>
                          -disk-timeout-dc <minutes>
                          -standby-timeout-ac <minutes>
                          -standby-timeout-dc <minutes>
                          -hibernate-timeout-ac <minutes>
                          -hibernate-timeout-dc <minutes>

              Example:
                  POWERCFG -Change -monitor-timeout-ac 5

              This would set the monitor idle timeout value to 5 minutes
              when on AC power.

  -CHANGENAME Modifies the name of a power scheme and optionally it's
              description.

              Usage: POWERCFG -CHANGENAME <GUID> <name> <scheme description>

              If the description is omitted only the name will be changed.

  -DUPLICATESCHEME
              Duplicates the specified power scheme.  The resulting
              GUID which represents the new scheme will be displayed.

              Usage: POWERCFG -DUPLICATESCHEME <GUID> <destination GUID>

              <GUID>  Specifies a scheme GUID obtained by using the powercfg -l.

              If <destination GUID> is omitted, a new GUID will be
              created for the duplicated scheme.

  -DELETE, -D Deletes the power scheme with the specified GUID.

              Usage: POWERCFG -DELETE <GUID>

              <GUID>  obtained by using the LIST parameter.

  -DELETESETTING
              Deletes a power setting.

              Usage: POWERCFG -DELETESETTING <SUB_GUID> <SETTING_GUID>

              <SUB_GUID>      Specifies the subgroup GUID.
              <SETTING_GUID>  Specifies the power setting guid.

  -SETACTIVE, -S
              Makes the specified power scheme active on the system.

              Usage: POWERCFG -SETACTIVE <SCHEME_GUID>

              <SCHEME_GUID>  Specifies the scheme guid.

  -GETACTIVESCHEME
              Retrieve the currently active power scheme.

              Usage: POWERCFG -GETACTIVESCHEME

  -SETACVALUEINDEX
              Sets a value associated with a specified power setting
              while the system is powered by AC power.

              Usage: POWERCFG -SETACVALUEINDEX <SCHEME_GUID> <SUB_GUID>
                                               <SETTING_GUID> <SettingIndex>

              <SCHEME_GUID>   Specifies a power scheme GUID and may be
                              obtained by using PowerCfg /L.
              <SUB_GUID>      Specifies a subgroup of power setting GUID and may
                              be obtained by using "PowerCfg /Q."
              <SETTING_GUID>  Specifies an individual power setting GUID and may
                              be obtained by using "PowerCfg /Q".
              <SettingIndex>  Specifies which of the list of of possible values
                              this power setting will be set to.

              Example:
                  POWERCFG -SetAcValueIndex <GUID> <GUID> <GUID> 5
                  This would set the power setting's AC value to the 5th entry
                  in the list of possible values for this power setting.
  -SETDCVALUEINDEX
              Sets a value associated with a specified power setting
              while the system is powered by DC power.

              Usage: POWERCFG -SETDCVALUEINDEX <SCHEME_GUID> <SUB_GUID>
                                               <SETTING_GUID> <SettingIndex>
              <SCHEME_GUID>   Specifies a power scheme GUID and may be
                              obtained by using PowerCfg /L.
              <SUB_GUID>      Specifies a subgroup of power setting GUID and may
                              be obtained by using "PowerCfg /Q."
              <SETTING_GUID>  Specifies an individual power setting GUID and may
                              be obtained by using "PowerCfg /Q".
              <SettingIndex>  Specifies which of the list of possible values
                              this setting will be set to.

              Example:
                  POWERCFG -SetDcValueIndex <GUID> <GUID> <GUID> 5
                  This would set the power setting's DC value to the 5th entry
                  in the list of possible values for this power setting.

  -HIBERNATE, -H  <ON|OFF>
              Enables-Disables the hibernate feature.  Hibernate timeout is not
              supported on all systems.

              Usage: POWERCFG -H <ON|OFF>

  -AVAILABLESLEEPSTATES, -A 
              Reports the sleep states available on the system
              Attempts to report reasons why sleep states are unavailable.

  -DEVICEQUERY
              Return a list of devices that meet the specified criteria.

              Usage: POWERCFG -DEVICEQUERY <queryflags>

              <queryflags>  Secifies one of the following criteria:

              wake_from_S1_supported  Return all devices that support waking the
                                      system from a light sleep state.
              wake_from_S2_supported  Return all devices that support waking the
                                      system from a deeper sleep state.
              wake_from_S3_supported  Return all devices that support waking the
                                      system from the deepest sleep state.
              wake_from_any           Return all devices that support waking the
                                      system from any sleep state.
              S1_supported            List devices supporting light sleep.
              S2_supported            List devices supporting deeper sleep.
              S3_supported            List devices supporting deepest sleep.
              S4_supported            List devices supporting hibernation.
              wake_programmable       List devices that are user-configurable
                                      to wake the system from a sleep state.
              wake_armed              List devices that are currently configured
                                      to wake the system from any sleep state.
              all_devices             Return all devices present in the system.
              all_devices_verbose     Return verbose list of devices.
              Example:
                  POWERCFG -DEVICEQUERY wake_armed

  -DEVICEENABLEWAKE
              Enable the device to wake the system from a sleep state.

              Usage: POWERCFG -DEVICEENABLEWAKE <devicename>

              <devicename>  Specifies a device retrieved using
                            "PowerCfg -DEVICEQUERY wake_programmable".

              Example:
                  POWERCFG -DEVICEENABLEWAKE "Microsoft USB IntelliMouse Explorer"

  -DEVICEDISABLEWAKE <devicename> disable the device from waking the system
              Disable the device from waking the system from a sleep state

              Usage: POWERCFG -DEVICEDISABLEWAKE

              <devicename>  Specifies a device retrieved using
                            "PowerCfg -DEVICEQUERY wake_armed".

  -IMPORT     Imports all power settings from the specified file.

              Usage: POWERCFG -IMPORT <filename> <GUID>

              <filename>  Specifiy a fully-qualified path to a file generated by
                          using "PowerCfg -EXPORT parameter".
              <GUID>      (optional) The settings are loaded into a power scheme
                          represented by this GUID. If not supplied, powercfg
                          will generate and use a new GUID

              Example:
                  POWERCFG -IMPORT c:\scheme.pow
  -EXPORT     Exports power scheme, represented by the specified GUID, to the
              specified file.

              Usage: POWERCFG -EXPORT <filename> <GUID>

              <filename>  Specify a fully-qualified path to a destination file.
              <GUID>      specifies a power scheme GUID and may be obtained by
                          using "PowerCfg /L"

              Example:
                  POWERCFG -EXPORT c:\scheme.pow 381b4222-f694-41f0-9685-ff5bb260df2e
  -LASTWAKE   Reports information about what woke the system from the last
              sleep transition

  -HELP, -?   Displays information on command-line parameters.

  -ALIASES    Displays all aliases and their corresponding GUIDs.
              The user may use these aliases in place of any GUID on
              the commandline.

  -SETSECURITYDESCRIPTOR
              Sets a security descriptor associated with a specified
              power setting, power scheme, or action.

              Usage: POWERCFG -SETSECURITYDESCRIPTOR <GUID|ACTION> <SDDL>

              <GUID>       Specifies a power scheme or a power setting GUID.
              <ACTION>     Can be one of the following strings:
                           ActionSetActive, ActionCreate, ActionDefault
              <SDDL>       Specifies a valid security descriptor string in SDDL
                           format. Call POWERCFG -GETSECURITYDESCRIPTOR to see
                           an example SDDL STRING.

  -GETSECURITYDESCRIPTOR
              Gets a security descriptor associated with a specified
              power setting, power scheme, or action.

              Usage: POWERCFG -GETSECURITYDESCRIPTOR <GUID|ACTION>
              <GUID>       Specifies a power scheme or a power setting GUID.
              <ACTION>     Can be one of the following strings:
                           ActionSetActive, ActionCreate, ActionDefault

Some useful things in there for looking into the Vista Insomnia issue are the following commands:

powercfg -lastwake

returns the name of the last device that woke the system.  Here's a screenshot of the output from one of my machines:

As you can see in this case the machine was woken up by the USB hub (in this case this is an expected resume - not a random one)

You can also enumerate the devices that can wake the machine with the following command:

powercfg -DEVICEQUERY wake_from_any

If you think that you have found the culprate then you can disable the device with the following command:

powercfg -DEVICEDISABLEWAKE <devicename>

you can then reverse that with

powercfg -DEVICEENABLEWAKE <devicename>

As you can see there is lots more you can do with powercfg, including tuning, exporting and importing power schemes; enabling and disabling hibernate and finding out what sleep states your device supports.  All told a very useful and very well kept secret.

I had high hopes that one of the fixes listed in the changelog for Vista SP1 might address the dreaded Vista insomnia issue.

l installed this on my Acer Ferrari which is constantly coming out of sleep mode. unfortunately this has rot resolved the issue. The Acer is still an insomniac.

I just blogged about an issue whereby Vista machines come out of sleep all on their own.  Then I was reviewing in more detail Long Zheng's list of changes in Vista SP1 and I spotted this item:

• Addresses the problem of the Video chipset (VSync interrupt) not allowing the system to stay asleep.

Could this be the fix to Vista Insomnia?  The problem occurs most frequently on my Acer, so I'll install the RC on that and report back here after some monitoring.

I previously posted about a work around I have used to get around the Sleep of Death issue on my LS800.  Unfortunately the same fix has not worked for for other LS800 users - there must be more variables.

However - as annoying as the sleep of death is it is not dangerous.  There is another issue I think is much worse.  Vista Insomnia.

I have 4 Vista machines that I have been using for a while.  These are:

• The Motion LS800
• An Acer Ferrari 1000
• A Samsung Q1P
• A custom built Media Centre

All of these machines have suffered from insomnia.  What I mean by this is I put a Vista PC into sleep mode and some time later it resumes by itself.  The reason I think this is worse than the sleep of death is that a Mobile PC coming out of sleep at the wrong time could be dangerous.  As an example I was using my LS800 to check some emails and feeds at the airport a while ago.  I used right up to the boarding line.  As I approached the counter I hit the power button to put the device to sleep - watched it go down because of sleep of death - and then dropped it into my carry-on bag to board the plane.  When we reached out cruising altitude I opened my bag to read my synced feeds and the bag was roasting hot.  The LS800 was awake again!

Now as bad as that is - it gets worse.  What happens to your hardware if you hit both problems?  If you put you device to sleep and it wakes itself up - what happens if you hit the sleep of death issue and it does not come all the way our of sleep?  Is the OS running?  If the OS has not resumed properly can it shut itself down if it gets too hot?   The night my LS800 died it was plugged in and lying flat on the desk.  The next morning it would not boot.  When I opened it up there was evidence of extreme heat damage and both the motherboard and hard drive were toast.  I can't prove it but I think the combination of these two Vista issues killed my device.  At any rate I have always been careful since to charge the LS800 in it's bumpcase so I can prop it up since then.

Warner Crocker points out some of the highlights in Vista SP1 for mobile users.

  As Microsoft prepares to roll out the Release Candidate of this to users soon, it might be worth taking a look. Some highlights that might be of interest to mobile users:

• Improves the effectiveness of a Windows ReadyBoost™ device in reducing the time to resume from standby and hibernate by increasing the amount of data stored in the ReadyBoost device that can be used during a resume cycle.

• Includes improvements to Windows Superfetch™ that help to further improve resume times, in many environments.

• Improves the time to resume from standby for a certain class of USB Hubs by approximately 18%.

• SP1 reduces the number of UAC (User Account Control) prompts from 4 to 1 when creating or renaming a folder at a protected location.

• SP1 addresses issues many of the most common causes of crashes and hangs in Windows Vista, as reported by Windows Error Reporting. These include issues relating to Windows Calendar, Windows Media Player, and a number of drivers included with Windows Vista.

• Improves power consumption when the display is not changing by allowing the processor to remain in its sleep state which consumes less energy.

Long Zheng of istartedsomething has posted an extensive list of fixes and it is on view here.  Worth checking out, methinks.

Several people have asked about the inking experience on the Shift in comments on my previous posts about the Shift. 1, 2, 3 & 4

The Shift has many good points. Inking is not one of them.  Like many UMPCs the Shift is fairly uncomfortable to write on.  If you do try it out you will find that you need to hold you hand up off the screen, otherwise the ink will jump between the point of the stylus and the heel of your palm.  This is because the Shift does not have any palm rejection technology.

In short, the Shift offers a much better touch experience than the inking experience.

One of the comments on my post about the HTC Shift's two operating systems has led me to a pretty interesting discovery.  There's a GPS in there!

In the screenshots of the tools in the HTC Debug Tools folder there is an icon called HTCGPSTool.

This led Hugo to ask if there was in fact a GPS in the device.

I had investigated this tool breifly over the weekend but it seemed a pretty basic tool and I had assumed that it was there to test an external GPS such as a bluetooth unit.  The comment got my interest up and I had some time on the train on the way to work, so I decided to investigate further. 

I started up the debugging tool.  There is a dropdown box with Com Ports listed.  By default it was on COM4.  I clicked on Open and low and behold I started seeing GPS strings in the output window.  I changed it to a different COM port and clicked open - and I got an error saying it could not find a GPS device.  Clearly the tool actually thinks there is a GPS in there.

I swapped back to COM4 and opened the port.  There are a number of tabs that show GPS information if you have a fix (which I didn't) and another radar display that shows the satellites that the device can see.  Initially there weren't any (hey I was on a train) but suddenly I saw one pop up.  It dropped off again a minute later.  I kept the GPSTool running when I got off the train.  As soon as I got out of the station and into some fairly open ground I got a satellite again.  Within 100m I had three more and even (breifly) got a fix.  Not bad in the middle of the CBD as the valleys between the buildings play hell with a GPS.  At my desk I can see one satellite - so I recorded a short video of the tool and clicked through the tabs before I had to give the device back.

So it would seem that the device does have a functioning GPS internally that is accessible inside of the Windows Mobile OS.  There is not, however, any software installed to actually use the GPS in Windows Mobile.

But - as I mentioned in my previous post is is possible to connect the Windows Mobile OS and the Windows Vista OS via Windows Mobile Device Centre over a "virtual" USB connection.  This means that it may be possible to install moving map software such as TomTom onto the Windows Mobile OS from Vista.

I could not find a way to access the GPS device from the Vista OS, nor could I see it listed in device manager.

Since HTC announced the Shift there has been some confusion about how the two operating systems on the device play together.  What can you do in each one?  Do they talk?

Well I have to preface this whole section by stating that as far as I know the software on the unit I had to evaluate is not the final version that will be on the devices when they ship.

In Windows Mobile...

The WM6 installation on the Shift has been stripped down and customized.  It is important to note that even though the device includes the 3G radio there is no phone application.  The Shift is not a voice device.  When you access the WM interface you are presented with a heavily customized Today screen.

This gives you access to your next couple of appointments, the date, time and calendar.  There are also buttons to access your full calendar, email, SMS, contacts, weather information and some settings.

The weather interface is quite nice - cool thunder storms tomorrow :)

The settings button takes you into an explorer view that gives you access:

Notice there are a bunch of things that are usually in WM6 that are missing?  Most of the settings interfaces have been replaced.  Don't expect to add too many applications either.  There is no programs folder so you would have to launch them through the file explorer.  And there is not much memory for running applications either.

The HTC Debug Tools folder in the settings folder gives you a bunch of little utils.  I don't know if this is going to be the same in the released version.

The bottom most icon in that - oops name was cut off - is called USBTool.  This offers a menu with two options - cable in and cable out.  When you select cable in with Vista running it creates a virtual USB connection between the two personalities of the HTC Shift.  This allows you to run up Mobile Device Center and explore the WM OS from Vista.  This makes it easier to set up things like Exchange ActiveSync.

The Windows Mobile OS stays running even when the Vista OS is sleeping or powered off.  If you configure it to use Direct Push you can receive your Exchange email even when Vista is off.  If you prefer or if you don't have an email account with Direct Push, you can use the virtual USB cable described above to sync directly with the local copy of Outlook in the Vista environment.  Of course in this configuration you will only see in WM a copy of what is in Vista.  You will not receive new emails while Vista is not running.

In Vista...

In Vista there is also a Connection Manager type of application that is called - for reasons that escape me - The Shag Control!  This is a fairly clean interface that gives you access to connection management, power management and other settings.  There is a gem buried in there - here's a tour:

Opinion

Given how stripped down the WM OS is I almost wondered why they bothered doing it that way.  I'm not saying that it is not useful - far from it - but I would almost rather that the second OS was implemented as a sideshow host rather than a WM environment.  You would not be able to do the push email, but you could access the data from the local instance of Outlook...  and potentially do a bunch of other cool things.  Food for thought.

In my previous post I gave a tour of the HTC Shift.  I promised to explore, among other things, what it is like to actually use the device.

One thing I quite like about the HTC Shift is that it is designed in such a way that it is very flexible.  There are three main ways in which you can use this device. 

Firstly you can use it as a slate.  Like most slates this has the advantage of actually being usable while you are standing up and moving around. 

The next option is to slide the screen up to expose the keyboard and use it as a thumb board.  This is a little cumbersome compared to other thumb boards, but it is usable. 

The third option is to put the device on a hard service and tilt the screen up, making it more like a laptop.

The video below explores these three modes.

Some questions I have had sent through about usage are below - with my answers in blue:

What is the screen like compared to the Q1 Ultra (or even the Q1)?

Similar - the screen is clear and viewable indoors.  The screen is not an outdoor viewable one, and the screen is hard to read in direct sunlight.

How long does the battery last under normal conditions?  In Vista? in WM6?

My experimentation here has been limited due to the short time I've had the device.  I've not tweaked the power settings at all, but at default it gets about 2 hours when using Vista for browsing and feed reading over wi-fi.  When I hibernated Windows Vista and left the device with Windows Mobile and push email the battery only lost 4% points of charge over 6 hours.  This leads me to believe that the battery life if you use Windows mobile exclusively will be measured in days.

How solid is the keyboard/screen mechanism?

It is easy enough to use but firm enough to support the weight of the screen at any viewing angle you should choose.

How useful is the touchpad?

It works well enough, but I don't tend to use it much.  I personally find it easier to just touch the screen.  One thing I did find odd is that it does not work in the Windows Mobile OS.  This seems a waste as WM does support using a mouse.

How useful is the WM6 component in reality?

I'll talk about this more in my next post.

How well will it work with voice applications such as Skype?

I did not try it, but I recorded a screencast on the device and the audio from the microphone seemed fairly good.  I would think that it would work well, though bear in mind that cellular networks such as HSDPA are usually quite latent and this can impact your voice experience.

I'll be interested in how the battery life is as well as the ease of text entry if you are holding it with both hands.

Battery life as above.  Yes you can use it holding it in two hands - using the keyboard like a thumb board.  As thumb boards go it is a fairly sizable one - and that can make text entry a bit cumbersome.

...the biggest question I have is regarding the battery life as I am considering a shift to replace my laptop. I have a desktop computer at work but regularly leave the office, travelling the country a fair bit and would like to know if the Shift could really satisfy my mobile needs?

It would depend on what you are wanting to do with it.  If you are primarily thinking of email then using Windows Mobile the battery life is stunning.  If you are wanting to use Vista for extended periods then the battery life could be an issue.  It is worth noting here that the power brick is quite small.

My Conclusions

The Shift is designed as a secondary device - to be used in conjunction with a "real computer".  At this it excels because you are actually getting a secondary device and a tertiary device in the one package.  I often say that mobility is all about having options.  Therefore a good mobile device needs to be a multi-tool.  Your Leatherman is not likely to be the best pair of pliers, knife or corkscrew you could own, but the fact that you have more than one tool in the same compact package is useful in and of itself. 

The Shift is the same deal.  The screen is ok for reading emails and browsing the web, but it can be a bit small for working on a large document, video or images.  There is of course a VGA port so you can always plug in a monitor.  Similarly the keyboard is neither a great keyboard or a great thumb board - but it can be used as either and that is powerful.  And of course there is a USB port - so you can plug stuff in.

I've now had some time with the HTC Shift and I'm getting to know it a lot better.  I've already had some questions posted in response to my earlier post - but I'll repeat the call.  I only have this device for the weekend so if there is anything you want me to investigate then post a comment and I'll do my best.

One of the first questions I had was from Chippy at UMPC Portal- is this unit the retail version?  The answer is no.  I understand the hardware is final, but the it does not have the final version of the system software installed on it.  This is an important caveat when I am talking about the software features of the Shift - they are not yet carved in stone.

I thought I would start with a tour of the physical device.  I'll follow up with posts about the software, usage and the interplay between the two operating systems.

In slate mode the Shift is small, thin and light.  On the front bezel there are a number of features worth noting.

In the top left corner there is a web camera.  In the top right there is an ambient light sensor. 

The two hardware buttons below the light sensor are function buttons.  When in Windows Mobile mode they don't do anything.  In Windows Vista the top button launches the Shift Control center.  The button below that toggles the screen resolution between 800x480 and 1024x768.

The black square below the two function buttons is a touch pad that allows you to control the mouse pointer in Windows Vista.  The left and right mouse buttons are the two buttons below the web camera on the left.  There are also two black oval slots.  These are the speakers.  Below the right speaker is the fingerprint reader.  Below the left speaker is the hardware button that toggles between Windows Mobile and Windows Vista.  Along the bottom of the screen (under my thumb) there are a number of indicator lights, including power, battery indicator, caps lock indicator, HDD activity, wireless indicator, 3g indicator and alert light.

On the right edge there is the power button, one USB port, the power input and an SD Card slot.

The silver power button is a soft switch.  Sliding this to the right toggles the power switch.  If you slide the switch to the left it locks in place and this disables all the buttons and the touch screen.

On the left side of the unit is the headphone jack.  This is on the left of the picture below.  Just visible on the right of the photo below is the inbuilt microphone.  There is also another hole on the front edge of the same corner.  Roughly in the middle is the slot for the stylus.  The stylus is ejected by pressing the end in, it then pops out.  When slotted in place it locks in positively.

On the top edge, when in slate mode, is a VGA output.

Sliding the screen upwards reveals a qwerty keyboard.  The screen slides up quite easily.  You can use the device quite comfortably in this mode while sitting or standing and using the keyboard as a thumb-board.

You can also convert the device into laptop mode.  The hinge is fairly stiff - this allows you to position the screen at any angle that suits you.  It does mean that you need a fair bit of leverage to pull it up.  You can achieve this one handed if you place your thumb at the base of the screen and pull up on the top edge with your fingers.

In order to use the onboard HSPDA you need to insert a SIM card.  To do this you need to remove the battery.  This is done by removing a cover on the back of the unit to expose the battery.  You then slide back two red clips that hold the battery in place.

Once you remove the battery you can see the SIM card slot. 

The only other points of interest on the back of the unit are three vents that let out heat and four rubber feel.  The rubber feet provide good grip on smooth surfaces - which is important when you have such a smooth finish on the unit.

Overall it is a good looking unit and feels well made.  Stay tuned for more on what you get when you fire it up.

Because I have a HTC Shift in my hot little hands for the weekend.

I'm really excited to have this opportunity. I think the Shift is an incredible and innovative device. Packed into it's tony frame are two operating systems - Windows Vista and Windows Mobile. It has embedded 3G wireless. There is a lot to play with.

Unfortunatly there is also a lot of confusion in the market about it as well. I aim to try and help clear someof that up. If there is something about the Shift you want me to check out while I have it leave a comment.

There is an issue that many mobile and tablet users have encountered with Windows Vista, myself included.  Warner Crocker also has encountered this issue and describes it thus:

I’m still frustrated with Vista on one front here and that is putting the Tablet PC to sleep. 3 times out of 4 everything will work as advertised. Close the lid, unit goes to sleep, open the lid, unit returns. But occasionally the OS just goes off into its own world without sleeping, or after a successful sleep, not returning. Occasionally it will return from sleep but the screen will stay dark.

I personally believe that this issue is not a Vista issue per se, but rather a driver issue.  I think that some drivers are poorly written and interfere with the sleep and resume process.  I also think that this issue is much more serious than it initially appears.  I have come to refer to it as the sleep of death.  But that I'll leave for another post. 

For Warner it seems his issues are related to when he is using Wi-fi.  For me it was BlueTooth.  Either way it points at drivers.

I’m beginning to think (this seems to be somewhat reproducible here) that these issues have something to do with being connected or disconnected to our WiFi network. Here’s what I’m experiencing and maybe someone smarter than me can help out here with some thoughts.

What worked for me was to disable the Power Management features for the affected driver.  For a wireless driver you would do this by going into Device Manager, right clicking on the relevant device and selecting Properties.

You may then see a Power Management tab.  Not all device or drivers implement this interface, so if yours does not you will not see the tab.

If there is one select that tab and then clear both of the checkboxes shown in the screenshot below. 

I have done this for my LS800 and it has all but eliminated the dreaded sleep of death issue.  I use to encounter this several times a week and now I get it less than once a month. 

The new software update for my first generation Zune has finally addressed one of the gripes I've always had with the Zune.  Namely the complete lack of integration with my Windows Vista Media Centre.  Because there was no support for recorded TV I never installed the Zune software on the Media Centre.  Since the new update supports this I installed it and set about syncing my Music, Pictures and Recorded TV to the Zune.  It took an age and I held my breath and navigated to the Videos folder on my Zune.  I played an episode of Futurama...  I marvelled at the spectacular picture - crystal!  Only then did I start to wonder why I could not hear anything...

As it turns out none of my recorded TV had audio.  I did some investigating and found that this was because all of my recorded TV was recorded from HD channels.  It is not that the Zune does not support HD, per se, but it does not support Dolby Digital audio that inherent in the HD stream.

As an experiment I recorded a movie off a channel that is not HD and lo and behold it plays fine.  This at least gives me a work around.   All of the channels that are available in HD are also available in standard format.  Now I can semi easily get my recorded TV on the train.

After a litany of supply problems I won't recount here "new" but "end-of-life" tablet arrived. It is a Lenovo X60. (I will say that the issues were internal and were not due to Lenovo.)

Since we are only allowed to connect certified hardware to the corporate LAN I have been working with two devices and synchronisation strategy that would challenge most people for the last 6 months.

Now I have the X60 life just got a whole lot simpler.

My only gripe -and it is a big one- is that the standard image is XP Tablet Edition. More on that later.

The Mobile Tech Roundup team and Warner Crocker over at GBM are asking where the slates have gone.

Its true. Relative to the whole tablet market, there are fewer slates around now than there were. When I say "relative to the whole market" I am referring to the new form factors such is UMPCs and the new entrants such as Dell.

But why are the slates disappearing?

More accurately what is preventing slate adoption growing as rapidly as their keyboarded cousins?

I'd put the answer in three parts.

1. Fear. People are use to having a keyboard and giving one up (albeit part-time) scares some fairly savvy users.
2. Pen-abled applications - or more accurately a lack of. We need more applications that either expose more functionality when run on a tablet or are written explicitly for the tablet.
3. Natural language Input is just not there yet. Many working age people can type faster thanthey can write.  And that percentage is only increasing. Speech is a good alternative and works well, but it is fairly resource intensive, and many smaller devices such as UMPCs just can't hack it. Not to mention it is simply not possible to dictate to your PC in many situations. I'm inking this post on the train, can you imagine the irritated looks I would be getting if I were talking to myself?

That may sound pretty dire, but does it mean that slates will only be a niche player? I think not.

Why? Because the first two of those points are addressable now.

The fear factor can be addressed by education. Teach the market that you can use a computer without a keyboard. Teach them that if you dock a slate it works just like a "normal" PC. We call this education of the market "marketing" and it has been sorely lacking since the tablet was launched in 2002. It is time for Microsoft and OEMs, especially slate specialists like Motion, Tablet Kiosk and Electrovaya to lift their game.

On the second point there are some really good pen-abled apps out there, but we need to see more marketing from the companies that develop that software. It's a differentiator, promote that fact. But we need more, too, so as a community we need to educate developers and most importantly demand pen features in the apps we use now.

The third point will be eased as hardware performance improves, but will not be eliminated (lMO) any time soon. We need at least the next version of the Windows OS. We can't write off Apple here, either. Now that we have all seen the i-phone you can imagine that a Mac tablet would challenge the UI paradigms we operate in.

Check out this very short video of me with the Motion LE1700, filmed the night before I had to send it back.

It shows the auto-rotate feature, where the tablet uses an accelerometer to determine its orientation and rotates the display accordingly.  This actually works at a very shallow angle, or even when flat on the table it you give it a bit of a flick.

I've been luck enough to have a Motion LE1700 in the house for a while but I have not had the time to really explore it.  I had just started having a real look at it when low and behold Motion needed it back.  C'est la vie.  I snapped a few photos before I sent it back so I could post this mini-review.  Click on any of the photos in this post for a larger image.  Motion have promised to send a unit with the WWAN module in it, so I'll do a full review then. 

I've had a couple of Motion slates in the past, including the LS800 I still use on a daily basis.  I have always found them to be well designed and with quality construction.  The LE1700 is no exception.  It has a very functional design and the silver and black finish is striking.  The unit is very comfortable to hold in either portrait or landscape mode, because it is very well balanced.

Here's a tour:

The tablet buttons are similar in design to previous Motion tablets.  There is a directional pad with enter in the middle, surrounded by four buttons.  On one side you have the programmable buttons, on the other you have an Esc button and a function button, which alters the action associated with the other buttons if you press it before another one of the buttons.

On the side below these buttons are the infrared port and the PCMCIA slot.  There is also a SD-card reader, but that is just out of the shot above - you can see it better below.

On the other end of the same side is the stylus and the antenna for the embedded WWAN module.  This particular unit did not actually have the WWAN module so I can't report on that, but you can see how the antenna can be raised up as shown or lowered so that it sits flush with the front of the tablet. 

The antenna is designed to snap on and snap off, so that if it takes a hard knock while raised it will snap off rather than breaking or transmitting any force into the body of the tablet.

Here's the antenna sitting flush.  Just below the antenna you can see one of the three microphones on the outer bezel of the tablet.  The other two are in the bezel as well, but in the bottom left and bottom right (when the unit is in landscape mode).

On the side below the screen (when the tablet is in landscape mode) is a Motion accessory port and (under the cover) a connector for when the tablet is used with either the convertible keyboard or the FexiDock.

On the left side of the tablet (when it is in landscape mode) you will find the following up the top on the front.  Two indicator lights - one for power and one for charge.  The fingerprint reader and the Windows Security button (pressing that is like pressing Ctrl-Alt-Del on a keyboard).  Notice there is no HDD activity light.  I've had another tablet without a disk activity light and it was a minor annoyance.  However the version of the Motion Dashboard that comes with the LE1700 puts an icon in the system tray.  This can optionally be configured to blink on disk activity - nice touch.

On the side of the unit below the activity lights are a hardware switch for the wireless, the power switch and two USB ports.  A couple of points worth mentioning here - the power switch is on the opposite side on this tablet than it is on my LS800 - though the units are otherwise laid out pretty similarly.  This is not a problem, but it does take a little getting use to.  However that is always the way with a new unit.

The other difference between the layout on the LE1700 and my beloved LS800 is that on the LS800 the USB ports are upside down - in that the top of most USB devices ends up facing towards the back of the tablet.  I'm pleased to report that this has been corrected on the LE1700.

In the middle of the left side there are microphone and headphone jacks; next to that is a DVI-D output, below which is a SIM card slot for the WWAN.  On the right of the photo below is a VGA output.

On the bottom left corner there is an RJ-45 Gigabit Ethernet port and a laptop lock slot.  On the front bezel you can see another of the array microphones and the ambient light sensor.

Last but not least - on the back you will find three covers held in place with screws.  The top left one covers the WLAN and WWAN modules, the bottom left exposes the HDD and the third cover exposes the two RAM slots.  Very easy to service.  The sliding cover you can see exposes the extended battery connector.  One of the great features of the LE series tablets is the shape of the back - note how there is a slight inset about an inch below the top of the tablet?  This is so that when you fit the extended battery to the unit it sits quite flush.  Because the battery is rectangular and flat the additional weight is evenly distributed and the unit is still easy to use for extended periods when you are moving about.

Using the LE1700 is a joy.  I've had 12 inch slates before and I've had tablets with SXGA screens before (which gives you a native resolution of 1400x1050) but to have both really is having your cake and eating it, too.  The unit I had did not have the ViewAnywhere display option - having had that on my LS800 I would highly recommend it.  The unit I had was the Core 2 Duo model and the performance was fantastic.  It came with XP Tablet edition pre-installed, but with Motion's permission I rebuilt it with Vista.  The Vista experience is flawless.

Overall a great experience.

I was cleaning out my digital video camera today and found a quick video review of the Sahara i440d slate from TabletKiosk (available in Australia from Tegatech).  I had recorded the video literally just before I had to step out the door to drive across town to return the unit to Hugo Ortega.  I went straight from there to the airport to pick up my wife and daughter who were returning from a quick break in New Zealand.  I got a bit sidetracked and never posted the video!

Overall I thought it was a good device - though not the prettiest.  It is white and fairly blocky, which is not a particularly corporate look.  However as I say in the video it does not actually feel blocky, it is quite comfortable to hold.  Certainly worth a look so check out the video.  (sorry - I never grabbed the screenshot or the photos I mentioned in the video.  I finished recording and had a "oh (*#& - need to leave now" moment)

I've seen the U1010 briefly a couple of times, but tonight I've got one in my hot little hands for the whole night.  And that is long enough to do a quick review with lots of photos. Click on any of the photos for a larger version of it.

The U1010 is a very exciting device.  Personally I think it is the most compelling UMPC sized device I have yet seen.  Fujitsu have packed an incredible amount into a really tiny package.  The photo below - that's a Zune next to it!

In laptop mode the Fujitsu U1010 offers a usable keyboard.  Fujitsu have maximised what they have squeezed into the device by giving a lot of the keys a secondary function (which is accessed by pressing the Fn key followed by the key with the function you want).  This has allowed them to do away with the traditional F1-F12 keys, thereby doing away with an entire row of the keyboard. 

The external styling of the U1010 is nice - you can see why some people have dubbed it "The Stormtrooper".  Overall the unit is white with black trim.  The "Fujitsu" and "Lifebook" logos on the back of the lid are in silver.

The U1010 is well designed to be used in slate mode, too.  The screen is offset away from the hinge, giving you a space to hold onto without obscuring the screen.  This is an important usability consideration for an ultra-portable device, but one that some vendors seem to forget.  In addition all of the hardware buttons are accessible when you are in slate mode, which is of course when you need them most.

The screen is crystal clear.  The native resolution is 1024x600 so you get a fair bit on that little screen.  Naturally on a small screen there is not much room to write, but if you do try it you will find that the U1010 offers a surprisingly good ink experience for a touchscreen.

Now a quick visual tour...

On the front right corner (when in laptop mode) there are the usual indicator lights.  From left to right power in indicator, battery level indicator (goes from green, to orange to red), disk activity and wireless network activity.

On the right side there is a compact flash slot, the power switch and a USB port that is hidden under a little white rubber flap.  The latter two are white on white, so are a little hard to see in the photo below.

Ah.. there's that USB...

There is nothing across the back, just the battery.

On the other side there is a wireless hardware switch by the power connector (again, white on white so hard to see), an SD Card reader (which unfortunately I could not get to work with ReadyBoost), volume up and down controls, headphone jack and microphone jack.

On the front edge there is a connector for a dongle that gives you both an ethernet port and a VGA out.

There is also a mouse of sorts.   To the right of the hinge (in laptop mode) there is a little joystick pointer.  Also just above that on the screen bevel you can see the Ctrl-Alt-Del button and the bottom edge of the fingerprint reader.

On the other side of the hinge there are the left and right mouse buttons.  Yes it really does run Vista!

There are a number of other handy hardware controls.  Next to the mouse thumbstick there is a function button and a scroll up and scroll down button.  The function button alters the action of the other hardware buttons.  For instance function scroll up or scroll down = page up or page down.

Directly above the hinge there are two programmable hardware buttons and a screen rotate button.

By default one of the programmable buttons turns on the head lights.  This is a handy little feature that illuminates the keyboard so you can type in the dark.

Another handy feature is the integrated web camera on the top edge of the screen. 

Another good design feature is the stylus.  It has been designed to telescope out so that it fits into the device but is still big enough to be usable when extended.

Before...

After...

Over all the U1010 is a very usable device.  There is a lot packed into this tiny package and every aspect of the design shows that it has been carefully thought out.  The price is very reasonable and performance is surprisingly snappy.  All told a solid offering.

 James Kendrick has posted a great review of the HP 2710p he just purchased. James include what he bought, what he is running on it and his conclusions. a good read.

It is no doubt apparent that I am very pleased with what HP has brought to the tablet with the 2710p.  It is not only a great Tablet PC but also a stellar thin and light notebook computer, something that other OEMs have attempted to do but none as successfully as this in my book.  The hardware components are a decent compromise for providing great battery life while still providing very good performance, even under the resource hog that is Vista.  HP has done a good job making sure that the entire package works as flawlessly with Vista as anything I have seen yet.  The thin and light design is stellar at providing a great OOBE and daily usage. 

This is a post I have been meaning to write for a while. 

There has been a lot of discussion of late about Vista and its readiness - or lack of - for the public.  Lots of people have lamented that Vista is just not there yet.  That it came out too soon.  That it is a failure.  Some have even reverted back to Windows XP as they believe that it is more stable and performs better.

Lots of people have voiced opinions one way or the other.  James Kendrick was one of the first to speak out against Vista, and his post  included most of the key gripes.

First and foremost in the area of performance.  I have not seen adequate performance running Vista on anything less than a Core 2 Duo processor.  Those are only available in the larger Tablets so the UMPCs and smaller Tablets are out of luck.  Vista also needs 2 GB of memory to run well and the smaller mobile devices usually are only offered with 1 GB, which isn't enough. 

...

If you use Sleep and Resume you quickly fall victim to the dreaded Vista la-la land where the device fails to resume properly.  Sometimes the device comes back fine but without a screen which is oh so useful.  Other times it comes back but hangs the entire device up in just a few seconds. 

...

One of the most beneficial things you can do to improve the mobile device experience is use it with a dock.  Don't even get me started with how badly Vista handles docking and undocking of these mobile devices, especially if you hang an external monitor off the dock.

Other general concerns are performance, battery life and mysterious disk thrashing. These are all real and valid concerns.  However, they are not the end of the world and they are not unique to Vista.  In fact - I believe that many of them are not the fault of Vista at all. 

I disagree with those that say that Vista is a dog and I will not be going back to XP on any of my machines - ever.

The first point I will make in Vista's defense is to point out that not everything bad that happens in on a computer is the fault of the OS.  On every single computer there are hundreds of device drivers and bits of software that could be the culprit for some of the issues outlined above.  Specifically the resume from sleep and docking station issues described above are most likely driver issues.  XP has been around for a while and hardware manufacturers have had a lot of practice writing nice, stable and functional drivers for the XP platform.  Vista is both new and very different.  I am disappointed, but not very surprised, that driver support is not that great.

Secondly, none of this is new to Vista.  I am an IT consultant.  I worked on a very early Windows XP deployment for a government client in New Zealand.  And guess what?  Driver support was appalling across the board, but it was worse for mobile PCs.  Performance was a joke.  There was no way Windows XP could really run on a machine that just met the minimum specs.  Blue screens and hangs were common.   When XP shipped it was worse than my experience working on a project with Vista in the Technology Adoption Program using beta code.  The released code is far and away more stable than Windows XP was at the same time in the product lifecycle.  What is significantly different is that the flaming and debate happened in the newsgroups rather than on the blogs we have today, which was much more of a closed community.

When Microsoft ships a new OS they tend to lead the hardware.  By that I mean that it is the hardware that comes out 6 months after the OS that runs it really well.  I think this is probably intentional - perhaps because it then extends what they can include in the product at ship date, bearing in mind that it will need to be a viable product for a couple of years.  I suspect that this will be the same for future OS releases.

The short version of all of that is that the issues we are seeing today are normal for a new OS and they are much more complex than "Vista is Bad".  Some of the blame rests with application developers.  Some rests with hardware manufacturers and some rests with Microsoft, but it will all be fixed in the fullness of time.

Until then I won't go back - simply because the benefits out weigh the pain.  The tablet functionality is way better.  The networking is better.  The Mobility Center is better.  Presentation mode rocks.  All of that functionality is nothing compared to the security enhancements.  When XP shipped the world was a different place.  The general public knew about viruses but had never heard of root kits, malware or spyware.  The Internet was not the efficient distribution system of nasties that it is today.  User Access Control (UAC) and protected mode IE go a long way to preventing then initial infection and Windows Defender makes it easier clean up after the fact.

Vista is here to stay.  I'm not going back and the experience will get better as the hardware catches up.

At TechEd Australia in the Gold Coast I had the chance to talk tablet on camera for the Virtual TechEd crew. The only catch was I had to bring my own interviewer. No problem Lee Williams was at TechEd with me and stepped up to the plate.

We had a good fun chat. Check out the video here.

You can also check out the other Virtual TechEd videos here.

 Search is one of the really powerful and addictive features in Windows Vista. Over on Geekzone Mauricio has a great whitepaper available for download.

The Windows Search Technologies Overview for Business Customers is a XPS document written by Arvind Mishra, Product Manager for Search, covering search from an enterprise perspective, but with lots of insights that would be of interest for personal use and small business as well

This is a great whitepaper that is currently only available from Geekzone.

Now that I have posted the PressureLevels utility I thought that I should give some insight into how it works - in case any real developers want to look into something similar. :)

While it is trivial to collect ink on a tablet using the controls provided by the Tablet SDK if you want more direct, low level access to stylus information then you need to use the Real Time Stylus API.  This is a pretty bare bones API that provides a stream of packets as the stylus moves around.  As a developer you can create a plug in that basically filters this information to just what you are interested and executes code every time on of those "events" fires.

I found this CoDe Magazine article by Marcus Egger to be very well written and extremely useful.

I have a class that contains this plug in that looks roughly like this:

Imports Microsoft.StylusInput

Public Class SimpleStylus
    Implements IStylusSyncPlugin
    Dim iLastPressure As Integer = 0

    Public ReadOnly Property DataInterest() _
    As DataInterestMask _
    Implements IStylusSyncPlugin.DataInterest
        Get
            Return DataInterestMask.Packets _
                Or DataInterestMask.StylusDown _
                Or DataInterestMask.StylusUp
        End Get
    End Property
    Private attachedControl As Form
    Public Sub New(ByVal form As Form)
        Me.attachedControl = form

    End Sub
    Public Sub Packets(ByVal s As RealTimeStylus, _
    ByVal data As PluginData.PacketsData) _
    Implements IStylusSyncPlugin.Packets
        Dim g As Graphics = _
           Me.attachedControl.CreateGraphics()
        Dim packetCounter As Integer
        For packetCounter = 0 To _
        data.Count - data.PacketPropertyCount _
        Step data.PacketPropertyCount
            Dim iX As Integer
            Dim iY As Integer
            Dim iPressure As Integer = 10
            iX = g.DpiX * data(packetCounter) / 2540
            iY = g.DpiY * data(packetCounter + 1) / 2540

            If data.PacketPropertyCount > 2 Then
                iPressure = data(packetCounter + 2)
            End If
            Console.WriteLine("P: " & iPressure & ", LP: " & iLastPressure)
            If iPressure < iLastPressure Then
                g.Clear(Form.DefaultBackColor)
            End If
            g.FillEllipse(Brushes.Black, _
                iX - iPressure, iY - iPressure, _
                iPressure * 2, iPressure * 2)
            iLastPressure = iPressure

        Next
    End Sub

    Public Sub StylusDown(ByVal sender As RealTimeStylus, _
    ByVal data As PluginData.StylusDownData) _
    Implements IStylusSyncPlugin.StylusDown
        Console.WriteLine("Stylus Down")
    End Sub

    Public Sub StylusUp(ByVal sender As RealTimeStylus, _
    ByVal data As PluginData.StylusUpData) _
    Implements IStylusSyncPlugin.StylusUp
        Console.WriteLine("Stylus Up")
        Dim g As Graphics = _
           Me.attachedControl.CreateGraphics()
        g.Clear(Form.DefaultBackColor)

    End Sub

    Public Sub CustomStylusDataAdded( _
    ByVal sender As RealTimeStylus, _
    ByVal data As PluginData.CustomStylusData) _
    Implements IStylusSyncPlugin.CustomStylusDataAdded
    End Sub

    Public Sub [Error](ByVal sender As RealTimeStylus, _
    ByVal data As PluginData.ErrorData) _
    Implements IStylusSyncPlugin.Error
    End Sub

    Public Sub InAirPackets(ByVal sender As RealTimeStylus, _
    ByVal data As PluginData.InAirPacketsData) _
    Implements IStylusSyncPlugin.InAirPackets
    End Sub
    Public Sub RealTimeStylusDisabled( _
ByVal sender As RealTimeStylus, _
ByVal data As PluginData.RealTimeStylusDisabledData) _
Implements IStylusSyncPlugin.RealTimeStylusDisabled
    End Sub
    Public Sub RealTimeStylusEnabled( _
ByVal sender As RealTimeStylus, _
ByVal data As PluginData.RealTimeStylusEnabledData) _
Implements IStylusSyncPlugin.RealTimeStylusEnabled
    End Sub

    Public Sub StylusButtonDown( _
    ByVal sender As RealTimeStylus, _
    ByVal data As PluginData.StylusButtonDownData) _
    Implements IStylusSyncPlugin.StylusButtonDown
    End Sub

    Public Sub StylusButtonUp(ByVal sender As RealTimeStylus, _
    ByVal data As PluginData.StylusButtonUpData) _
    Implements IStylusSyncPlugin.StylusButtonUp
    End Sub
    Public Sub StylusInRange(ByVal sender As RealTimeStylus, _
ByVal data As PluginData.StylusInRangeData) _
Implements IStylusSyncPlugin.StylusInRange
    End Sub

    Public Sub StylusOutOfRange(ByVal sender As RealTimeStylus, _
    ByVal data As PluginData.StylusOutOfRangeData) _
    Implements IStylusSyncPlugin.StylusOutOfRange
    End Sub
    Public Sub SystemGesture(ByVal sender As RealTimeStylus, _
ByVal data As PluginData.SystemGestureData) _
Implements IStylusSyncPlugin.SystemGesture
    End Sub
    Public Sub TabletAdded(ByVal sender As RealTimeStylus, _
ByVal data As PluginData.TabletAddedData) _
Implements IStylusSyncPlugin.TabletAdded
    End Sub

    Public Sub TabletRemoved(ByVal sender As RealTimeStylus, _
    ByVal data As PluginData.TabletRemovedData) _
    Implements IStylusSyncPlugin.TabletRemoved
    End Sub
End Class

In the data interest mask I state that I am interested in StylusDown, StylusUp and Packets events.   This means that every time the stylus comes into contact with the screen or is lifted from the screen the StylusDown and StylusUp subroutines respectively will run.  I use the Stylus up event to clear the drawing so that when you lift the pen you get a clean slate ('scuse the pun).

The workhorse is the packets subroutine. A packet is generated every time there is new data to send.  This will include at least an x and y coordinate and may include a pressure level.  What this routine does is convert the X and Y coordinates to screen coordinates (the digitizer has a much higher resolution than the display), and if there is a pressure level it converts that to the radius and draws a circle on the attached control (which is the main form you see when you run the app.

The other subroutines are just stubs that could be used if you edited the data interest mask.

On the main form I just use the load event to instantiate a RealTimeStylus object then add the SimpleStylus plugin in the class above and pass it the form itself as the attached control.  Here's the code for the main form.

Imports Microsoft.StylusInput

Public Class Form1
    Inherits System.Windows.Forms.Form
    Private rts As RealTimeStylus

    Private Sub Form1_Load _
             (ByVal sender As System.Object, ByVal e As System.EventArgs) _
             Handles MyBase.Load
        Me.rts = New RealTimeStylus(Me)
        Dim plugIn As New SimpleStylus(Me)
        Me.rts.SyncPluginCollection.Add(plugIn)
        Me.rts.Enabled = True
    End Sub
End Class

And that is really all there is to it.  Pretty cool that you can get access to such low-level information so fast, eh?

One of the cool thingsabout active digitizersis that they arepressure aware. Thedigitizers in most Tablet PCs can detect256 levels of pressure,whereas some of theeternal ones artists usecan detect 512.

While I was at TechEd Australia I had a cool sideline conversation with a chap from Wacom. My colleague Lee was with me at the time and be asked this guy if they had any little utils that could be used to show off pressure awareness in tablets. The answer was no, but we all agreed that it was a cool idea. I foolishly opined that it would be easy to make one, hence volunteering.

I'm still tinkering and will release code soon, but I'm using the real the stylus API to detect the pressure levels and render a circle where the radius is relative to file pressure applied.

Still a bit rough but the Gif below might give you an idea of what it looks like.

I've finally gotten around to applying the two performance & compatibility patches that were recently released.

The patches are:

Compatibility and reliability update - KB938194

Performance and reliability update - KB938979

These were released while I was a TechEd Australia, but I have learned from past experience never to patch just before you present! So I put them on mg LS800 on Friday and my Acer notebook on Saturday. So far everything has been peachy so I'll do the media centre soon, too.

The new version of OmniPass for Windows Vista seems to have a few issues with IE7.  My friend Lee identified this issue and - having just rebuilt my LS800 I installed OmniPass to see if I could reproduce the issue.  I can, and not just with IE.

When secureapp.exe (the OmniPass tray icon application) is running then whenever IE has the focus iexplore.exe hammers the processor.  The same thing happens with Windows Live Writer and Feed Deamon - when they have the focus then they hammer the CPU.  If secureapp.exe is not running then they don't.

With both apps running, but with IE minimised task manager looks something like this:

The CPU is pretty idle at 13% and secureapp is there, but idle.

Maximising IE cause the CPU to get hammered until IE is minimised again.  It looks like this:

If you kill off the secureapp.exe process after you log in then this does not happen.  The down side is that you cannot store application passwords in OmniPass and authenticate with fingerprints without this process running.  You can, however, still log on and unlock you machine using fingerprints without the secureapp.exe process running.

In Windows Defender you can prevent the secureapp.exe process from running at start up, which will save you killing it off manually.  In the Control Panel click on the Change startup programs link under Programs.

In the Windows Defender dialog click on the Show for all users button to enable the disabled controls.

Once you have confirmed for UAC that you want to allow this you will be able to select the Softex OmniPass item and then click the disable button.

With a Windows Mobile 5 device, once it was paired with your Tablet you could create a dial up connection on your computer that would connect to the Internet via whatever data protocol your device uses (e.g. EVDO, GPRS or HSDPA).

With Windows Mobile 6 you can still connect to the Internet using your SmartPhone as a modem, but the process is slightly different and requires you to complete steps on both the device and on your tablet.  The following steps outline the process.  This assumes you have already paired your phone with the tablet.

1) On the Windows Mobile 6 device select Internet Connection Sharing

2) Next click the Connect button.  This establishes the connection to the Internet and readies the device to accept a connection from your tablet.

Now that the mobile device is ready to accept the connection you need to go to the tablet to establish the connection. 

3) On the tablet right click the Bluetooth icon in the system tray and select join a personal area network.

4) In the Bluetooth Personal Area Network Devices dialog select your phone in the Access Points area and then click connect.

Viola - you are online!

After getting my LS800 back I started the long process of rebuilding.

Today I layered on more apps including:

• Zune software
• Windows Mobile Device Centre
• Techsmith SnagIt
• Techsmith Camtasia Studio

Still more to go...

Like I posted yesterday every Vista form that does not wilt not resize and fit into 600 pixels wide is a failure.

Here's another I stumbled across today.

 Both this one and yesterday's dialog are forms in control panel applets that only apply to Tablets. What's with that?

One thing that really irks me is some bits of Vista just don't fit on a 800x600 screen in portrait mode.

See how the right side of the dialog is off the screen?

This is just poor design. The minimum supported resolution for Vista is 800x600. Vista includes tablet functionality. Tablet screens rotate.

If you are building Vista apps assume that screen resolutions will vary and make sure they are still readable at 600 wide. Good design would have the above form resize.

In the process of installing all my software and I just came across something strange.  

Vista popped up one of its little problems and solutions dialog and informed me that there were new solutions for some of the issues found on my computer.  Clicking through I see three new solutions listed - which are all driver updates.  These included the Authentic AES2501 Finger Print reader, the Infinion TPM and the Motion Button Driver.  Since I knew I did not have a driver for the fingerprint reader yet I click on that to view the solution.  What I got was this message saying that I need to install the driver from the manufacturer's website.

Why is this weird?  Well clicking on the link takes me to a page on HP's website, not Authentic's.  On that page there is a driver for the fingerprint reader, but it also relies on HP's security suite, so I'm not going to grab it.  But very stange...

Hello Kettle?  This is Pot...  You're black!

When I read comments by Acer president Gianfranco Lanci stating that the PC industry is 'disappointed' with Vista I openly scoffed. 

I have worked with Vista since about November 2005.  Given how long partner organisations - including OEMs - had access to prerelease code before it shipped I was pretty disappointed with the availability of drivers and supporting applications when Vista shipped.

In fact around about launch time I was one of the group of MVPs and bloggers that received an Acer Ferrari to test Vista on.  A beautiful 64-bit laptop.  One of issues I have with that device is that the driver support is crap and the all the supporting applications (such as the Voice Call Manager) are 32-bit.  Hey Acer - is your software mature?  Get your own house in order before attacking other. 

In truth I think much of the onus for Vista's initial luke warm reception lies with the hardware vendors.  There has been quite poor support for existing models - I point to the likes of the Motion's still absent driver for the SD card reader on the LS800 (hello?  it has been 7 months since you guys updated your KB article?!?!) and the madness of vendors like Creative charging for Vista driver.  The cynic in me thinks that most vendors are more interested in trying to get you to buy new hardware than in supporting the user base they have.  I think this is short sighted and basically sends your customer out to market again with a negative impression of your products.

The last couple of weeks have been a bit intense.  I had a major customer presentation that ate about a week.  And I have about a million unread feeds.  Here are some links that are worth looking at that I've just caught up with.

On GottabeMobile.com

• Warner Crocker points to a cool add-inthat makes sending to OneNote mobile a bit easier.
• Warner also reviews his first week with the Lenovo X61
• Motion Computing get FCC approval for HSDPA in the LE1700.  I understand this is also underway in Australia.
• Please don't wear a OQO Model 02 on your belt.  Here here.
• Demo of touch screen pen flicks.  I love pen flicks...
• Creative charging for Vista drivers!  Dispicable - my advice is vote with your feet and buy something else.
• Interactive Whiteboards vs. Tablet PCs
• Hugo gets his hands on the Raon Everun
• Frank Garcia becomes a tablet MVP, as does Matt Faulkner.  Great stuff guys!
• MS are going to address a flaw in ReadyBoost in SP1 for Vista.
• Dell to release a UMPC?

On jkontherun.com

• Beautiful beer girls with Tablets.  Am I dreaming?  Actually - if I was dreaming it would not be an American beer!
• Samsung are getting ready to release a 64GB SSD - now we are talking!
• Tweak OneNote for a little bit more battery life.  Who'd of thunk it...
• Read your feeds faster on a UMPC - I need to be doing this!
• Touchscreens with hover are on the brink - using projected capacitive touch.  In other words it can tell when your finger is almost touching the screen - how cool!
• Intel and MS teaming up on a new slate platform called the "Edy Personal Computer" platform - will be watching to see where this goes.
• Use your smartphone as a bluetooth webcam.  Groovy Baby (sorry - Austin Powers is on in the back ground.  Britney Speirs just exploded.  Good job...

That's about half my unread items.  I'm off to bed...

Woe is me!  My much loved little LS800 is down and out.  After using it for a couple of days with its 2GB RAM upgrade I grabbed it off the desk and headed out. On the train on the way into work I pulled it out of my bag and flicked the switch.  The power light came on and nothing else happened.  Uh-oh.  We have a problem. 

Naturally because the RAM had just been upgraded I suspected the new RAM as the issue.  I swapped out the new RAM and replaced the old, but to no avail. 

When I opened the LS800 to swap back the RAM there were some indications that make me think the unit may have gotten very hot.  I think that this is the root cause of the problem.  While I can't prove it I have a theory about what happened. 

I have my tablets configured to sleep when I hit the power button.  On occasion since upgrading to Vista the LS has failed to sleep properly when I hit the switch.  When this happens you need to force the unit off by holding the switch down.  When in this insomniac state the unit will not go into shutdown to protect itself if it gets to hot.  I know this as I had this happen to me once before when I flicked the power switch and chucked the LS800 into my bag to change location.  When I pulled it out again it was in this hung state and stinking hot.

The other time the LS gets hot is when it is on power.  This is where I think I went wrong.  It was late and I was tired.  I'd been running off battery for several hours so the charge level was low.  I flicked the switch to send the LS to sleep, plugged in the power and went to bed.  I left the LS flat on the desk, not propped up as I would if I was leaving it plugged in and on.  I don't recall watching it to make sure it did actually sleep.

While I don't believe that putting 2GB of RAM in the LS800 caused the issue I hasten to point out that I don't believe a 2GB upgrade to the LS800 is not supported or recommended by Motion.  It is certainly not supported by me - so if you are looking at that upgrade be aware that it is at your own risk.

I'm hoping to get the LS800 fixed, but in the interim I'm using my Samsung Q1P as my main tablet.  This is an interesting and very different experience and I am sure I'll have much to blog about from this unintentional experiment.

I stopped by to see Hugo Ortega on the way home this afternoon to help him restore a Vista Complete PC backup onto one of his many devices.

While I was there I caught the bug that has been afflicting Hugo recently and cracked open my LS800 and put in a 2GB DIMM just to see what would happen.  What happened is it just worked like a charm.  Since I was unwilling to then part with said RAM I told Hugo to get TegaTech to invoice me for it.

Now the LS800 is running really well.  It really needs a rebuild as I have been installing and uninstalling a bunch of software I have been evaluating recently and much of that has been pre-release.  However even in it's sub-optimal and in need of a rebuild state it is noticeably faster now. 

Hugo snapped a sneaky snap of my beautiful LS with her clothes off - which he is going to send me later to post.  I'm sure it will end up on his blog as well.

Yesterday I posted about entering text with the Tablet Input Panel. Once you have mastered text entry with the TIPI recommend you look of some of the options you can tweak to change the way the TIP works. The TIP is actually quite flexible and you can adjust it to suit how you work.

To get started click on the Tools drop down in the TIP's menu bar and select Options, as shown below.

This will bring up the options dialog, which will be similar to the one shown sow. I'm gathering screenshots on Vista. for the most port the options available on XP are the same, but there may be some that are missing in XP Tablet Edition.

One of the important things to note we is the Restore button in the Restore default settings area. Don't be afraid to experiment as you can always get back to the original settings.

On the Settings tab you can tweak where the TIP icon appears. you can also change the insert buttons behavior so that hovering the point over the insert button will insert the current text (without tapping the button). I find this a great time saver but I do know other people who find it annoying.

The AutoComplete function is only available in Vista. It is on by default and I, personally, would leave it that way. I posted about autocomplete a while ago in this post.

On the Opening tab you can control how you launch the TIP.

Similar to tweaking the insert buttons you configure the tip to launch when you point at the TIP tab or the TIP icon.

On machines with lower end graphics you might want to consider clearing the checkbox that says Show the Input Panel sliding open from the tab.

Also, if you find the TIP tab gets in the way of what you are working on then you can clear the Show the Input Panel tab when the per is out of range checkbox.

Lastly on the Writing Pad and Character Pad tabs I like reducing the thickness of the ink to Extra Fine Point, which gives me more room when writing in the TIP.

There are more settings there that I have not covered. Experiment to find the settings that work best for you.

 if you one running Vista ultimate on a system that supports Dreamscene then you need eye candy! Checkout Background Motion. Darryl Burling provides more info...

What is it?

Backgroundmotion.com is two things. 

Firstly it is a community website to allow you to share backgrounds and background video for the DreamScene features of Windows Vista Ultimate.

Secondly it is a great example of a modern web application built on .Net 2.0.  When I say example, I also mean sample - the source code for the site is available on codeplex for you to download and pull it apart. 

There is also a "Code" tab on the site to help you get up and running with the source code.  The developer section of the site includes sample code, short introduction videos and resources to lower the bar to use these technologies.

Technologies used

One of the things that the guys did was to build in all the latest technologies and making the code available means that you can go and see how they did it.  Specifically, the technologies and tools they used include:

• .Net Framework 2.0
• .Net Framework 3.0
• ASP.Net 2.0
• ASP.Net AJAX 1.0
• Silverlight
• NUnit
• LINQ (May CTP)
• Web Client Software Factory (Composite Web Block)
• Lucene.Net
• RSS Toolkit (which was extended for the solution)
• Virtual Earth
• Sidebar Gadgets

Background Motion - now live!

Very cool. Well done guys!

While I was at TechEd in Orlando I sat in on a great session by  Dr Neil Roodyn on developing sidebar gadgets.  In his session Dr Neil reminded us all that SideBar gadgets are just mini HTML applications.  I had the thought that now that we have Siverlight with great ink support we could probably knock together some pretty cool gadgets that leverage Silverlight to provide ink functionality.

Now Gavin Gear not only confirms that this is so - he provides and example.  Pretty cool.

In this post, I’ll show you how to use Silverlight to create an inkable surface on a sidebar gadget.

Here’s the example running on my desktop:

 

Check out the full post here.

At TechEd, as you might imagine, there is a lot of wireless noise. There is the conference wi-fi, but there are also a bunch of ad-hoc or computer to computer networks with remarkably similar names. In the wireless list infrastructure and ad-hoc networks have different icons.

You have to question the motives of people trying to fists for wi-fi users like that. while I know better than to go connecting to ad-hoc networks willy nilly, I wanted to remove the risk of accidentally connecting to one with the same name.

In Vista you can, via the command line, filter the list of available wireless networks. To filter out ad-hoc networks run the following from a command line (running as admin, all on one line)

netsh wlan add filter permission=denyall networktype=adhoc

to reverse this again run the following:

netsh wlan del filter permission=denyall networktype=adhoc

I'm trying out a Vodafone 3G Connect HSDPA modem for work. I found the 32-bit Vista driver on the Vodafone Australia website. Install under Vista took ages, but it was well worth it. I'm browsing my feeds and so far it has not missed a beat. Very cool. I'll do a proper speed test later today but for browsing at least it is quite snappy.

My friend Lee's long wait is almost over - his new LS800 is on the way.  He asked me today what he should do with his new tablet when he gets it.  There are tons of things you can do with your tablet and discovering those things is one of the joys of tablet ownership. 

That said here are 10 tips - things you can do with your new tablet to get you started.

1. Install Vista
   There is a lot to love in Windows Vista if you are a tablet or mobile user.  The Snipping Tool (which is available for XP tablet users in the free Tablet Experience Pack from Microsoft), Pen Flicks, multiple selections in Windows Explorer, Internet Explorer's panning tool, autocomplete for URLs and email addresses, an updated Tablet Input Panel and handwriting personalisation make Vista a compelling offering for tablet users.  You can read more about all of these in this post I did way back in April last year, during the beta.  There are some more mobile friendly features outlined here as well.
2. Make a Mind Map
   Mind mapping is a great way to plan things out or get your creative juices flowing.  I use Mind Jet's MindManager 6 - but there is a new version coming out soon, so that will be well worth checking out.  If you are running it on a small screen tablet, check out my optimization tips.
3. Ink on a PDF.  Tablet users delight in freaking people out.  A great way to do that is to return a PDF form that has been emailed to you by emailing it back within minutes all filled out.  I use PDF Annotator to do this.  Apart from being very efficient it is good fun.
4. Take some notes.  Note taking is where a tablet comes into its own.  If you have OneNote installed you can use that, but if not all tablets (Vista or XP) come with Windows Journal.
5. Do some drawing.  Drawing is great on a tablet.  For the best tablet experience you want something that is aware of the different pressure levels that are reported by an active digitizer.  My favorite is NZ grown ArtRage - even my daughter loves it.  Another good option is the free photo editor Paint.NET.
6. Read a book.  In slate mode a tablet makes a great platform for reading eBooks.  I've used both Microsoft's Reader and Palm Digital Media's eReader and they are both good.
7. Ink in Word - You can use ink in Word to markup documents or to insert ink comments.  If you are using Word as your editor in Outlook 2003 or if you are using Outlook 2007 then you can also ink email messages.
8. Ink on PowerPoint Slides - Another great way to show off in front of the ink challenged masses.  More on that here.
9. Ink Instant Messages - If you use Windows Live Messenger then you can chat in ink.  Great if you happen to be having an IM conversation while on the train (I've done that!)
10. Most importantly of all - Have fun!

Not for show on any of the stands but when I saw Hugo he gave me a quick look at the OQO 02.

The unit he was sporting had the extended battery fitted and this gives it ~5 hours battery life. The display is a bright, clear and readable 5" with 800x480 native resolution.  It was the model with the 1.5GHz processor and was running Windows XP Tablet Edition.  The same unit is also available with Windows Vista pre-installed.

The slide out thumb board is quite usable.

Another cool feature is the two scroll bars on the edge of the screen.

Dragging on these will scroll the active window.

Quite a functional little device.