Tue, 03 Nov 2009 10:06:44 GMT
I love the potential of the RollTop concept PC from Orkin Design. Out of the box thinking like this opens the door for some really great new ways to work.
Tue, 18 Aug 2009 12:22:06 GMT
Nick took the I’m a Tablet PC logo I created earlier this year and created a Twibbon – which overlays the logo in the bottom right of your Twitter profile picture. Here’s what mine is looking like now:
So Tablet Tweeps – show your support for the wonderful Tablet PC platform – join the Twibbon now.(image)
Sun, 09 Aug 2009 11:17:22 GMT
The Outlook Team has an excellent drill down into what is quickly becoming my favourite feature in Outlook 2010 – Quick Steps.
Well worth a read, but in short Quick Steps are a productivity boon.(image)
Thu, 02 Jul 2009 12:02:48 GMTSeveral people have asked for me to post more detail about the CMD scripts that I wrote to get the Cisco VPN client working on my 64-bit Win 7 machine using Virtual XP . Basically I have written two scripts. One adds routes to the subnets I need at work and the other deletes them. So – what are routes? Basically they are the directions that computers use to send communications to the right place. The first thing you need to do is identify what network addresses are in use on your work network. Fortunately the Cisco client makes this fairly easy for you. Once the Cisco VPN client is installed in the virtual XP environment, connect the VPN and then Select the Statistics option from the Status menu in the VPN client window. This will list the subnets on your remote network as shown below: I created a text file where each line in the file was a remote subnet and subnet mask, separated by a semicolon. For example if your remote network used three networks: 192.168.1.0/24, 192.168.2.0/24 and 192.168.3.0/24 then your text file would look like this: 192.168.1.0;255.255.255.0 192.168.2.0;255.255.255.0 192.168.3.0;255.255.255.0 Save this text file to your hard drive. I saved mine in c:\utils\addroutes.txt In a nutshell when I am connected to the VPN I run AddRoutes.cmd script and it helps the Windows 7 machine identify the traffic intended for my work network. In the example above it would need to know to send any traffic for the above three networks to the Loopback adaptor of the host as discussed in my previous post. Here is what is in the AddRoutes.cmd script: @Echo Off Set GW=192.168.233.1 Echo Setting Up Routes: for /F "delims=; tokens=1-2" %%i in (c:\utils\vpnroutes.txt) Do route add %%i Mask %%j %GW% metric 1>NUL Echo Done! (note that “for” through to NUL is all one line) What does this do? The first line tells the script not to show the commands as it runs them. The next line creates a variable called GW and sets it to the IP Address of the loopback adaptor. The third line just provides some visual feedback and tells you that it is about to add the routes. Line 4 is the workhorse. I’m not going to go into the nuts and bolts of the “for” command, but it is very powerful. If you want to know more, you can type “for /?” at the command line. In a nutshell what line 4 says is: In C:\utils\vpnroutes.txt each line is a list of values seperated by semicolons. For each line run the following command with the first two values: route add Value1 mask Value2 GW Where GW is the address of the gateway we set in line 2. That’s it – you are online and know how to talk to your VPN network. Now when you disconnect you don’t need those routes anymore, and if you leave them there they may cause issues. So DeleteRoutes.cmd removes them again. Here is what is in DelRoutes.cmd: @Echo Off Echo Deleteing Routes... for /F "delims=; tokens=1" %%i in (c:\utils\vpnroutes.txt) Do route delete %%i>NUL Echo Done! This is very similar to the first script – For each line in the vpnroutes.txt file it runs a command to remove the route again. There is one last thing you may need to make everything work as expected and that is name resolution. This one is easy to fix. If you know the address of your DNS server on your remote network add it as the DNS server on the properties of the loopback adaptor. This won’t cause any issues if you leave it there full time. Hope that helps everyone. I will admit it is a bit of a nasty work around but it does work. [...]
Tue, 23 Jun 2009 13:10:11 GMTThis just cropped up in one of my Twitter searches and it really caught my eye. A 9” netbook with a touchscreen and a removable keyboard? Could it be that someone has finally caught on to the fact that the HP TC1100 was a really good idea and would be excellent if refreshed with current technology? Weighing less than 2 pounds and sporting a [8.9] inch screen, the Touch Book has moved away from the world of the Intel Atom CPU and delved into the mobile power of the ARM processor from Texas Instruments, and with its custom designed battery, the Touch Book runs for up to 15 hours unplugged. The key design feature of the Touch Book is its ability to completely separate the screen from the keyboard, allowing the screen to be used as a standalone tablet. Furthermore, the screen is magnetic and can easily be mounted on any metal surfaces. How cool is that – 15 hours battery life and you can stick it to the fridge! The bad news is that it is not shipping yet but pre-orders are being taken. Well the touch book certainly looks like an interesting device and I would love to get my hands on one to see how well the concept is implemented. It looks like it is running its own OS and the ARM processor is usually associated with phones and PDAs but it could be a good step in the right direction. Vital statistics from the website: Key Specifications 9.4″ x 7″ x 1.4″ for 2 lbs (with keyboard) ARM Texas Instruments OMAP3 chip 1024×600 8.9” screen Storage: 8GB micro SD card Wifi 802.11b/g/n and Bluetooth 3-dimensional accelerometer Speakers, micro and headphone 6 USB 2.0 (3 internal, 2 external, 1 mini) 10h to 15 hours of battery life [...]
Mon, 25 May 2009 11:44:26 GMT
In the comments of that post yaz points out that NCP has a Beta Client that works on 64-bit clients – and that includes Windows 7. It also supports 3rd party VPNs and that includes Cisco.
The NCP beta client is available via this page. Install was simple and there is even a UI to import your existing Cisco VPN profile.
It appears to be a 30 day trial – which is a bit odd for a beta product. It does appear to work though. I’ll give it a good work out over the next couple of days and report back.(image)
Mon, 11 May 2009 12:24:13 GMT
A couple weeks ago the OS informed me that the extended battery for my Motion LS800 had issues and should be replaced. Not really surprising as the battery is 3 or 4 years old and has been heavily used.
I swapped back to the standard battery and now woe is me – it too tells me that it needs to be replaced. This battery is actually even older than the Extended battery.
This could spell the end for my much loved Motion LS800, which is a real shame. Worse than that it is my only tablet that is a slate. And if I were to replace it – what would I replace it with?
Motion seem to have focused on vertical markets and as such all the new devices they are releasing are ruggudised, specialised or both. Who makes a nice corporate Slate these days?
Electrovaya and the Scribbler SC 4000 still seem to be around, but they have never made it downunder AFAIK.
The Tablet Kiosk Sahara range is probably the most comprehensive, but there has been little development in the year or so since I looked at it last.
Fujitsu have had an on again, off again affair with the slate form factor.
Why isn’t anyone building cool new slates these days? Do you think we’ll see any new slates hitting the market when Windows 7 ships?(image)
Mon, 11 May 2009 11:30:46 GMT
Previously I blogged about an issue I first encountered with the Windows 7 M3 build (the one that was released at PDC) and my hosted Exchange provider.(image)
In short when running the M3 build and the public beta I was unable to authenticate to my hosted Exchange provider using my email address and password. Instead I had to find out the domain name and enter credentials in the format DOMAIN\username in order for outlook to connect to Exchange. This was a bit of a pain.
The good news is that the Windows 7 Release Candidate resolves this issue and I can now authenticate with my email address as I could under Windows Vista.(image)
Sun, 10 May 2009 12:16:04 GMTFor reasons that escape me Cisco have chosen not to release a 64-bit version of the IPSec Cisco VPN Client. This is a problem for me since I installed the 64-bit version of Windows 7 RC on my Toshiba M750. To get around this without rebuilding with the 32-bit version I employed Windows 7’s new XP Mode – aka Virtual XP. First I followed the steps on the download page: Enabled virtualisation extensions in the BIOS. Download and install the Virtual PC Beta. Download Windows XP Mode. That done I fired up the Virtual Windows XP from my Start Menu: This loaded up a Virtual Machine already running Windows XP. I installed the Cisco VPN Client and verified that it could connect to the VPN. This is where it gets a little tricky. At this point I have my Toshiba, which is the host and an XP machine which is a guest. The XP Guest has a virtual adaptor that leverages the host’s network adaptor and can connect to the remote network. But the host has not way to connect through the guest to get to the remote network. For initial testing I created a static route for one of the subnets and pointed it to the IP Address of the guest. This worked, but it is a bit fiddly as the guest IP address is assigned by DHCP and as such will change depending on where I am. I wanted something that required a little less work to get connected. To achieve this I needed to create a virtual adaptor on the Host. This is done by adding a loopback adapter to the host. Adding a Loopback Adapter to the Host In Device Manager right click the root node and select Add Legacy Hardware On the welcome screen click Next. Then select Install the hardware that I manually select from a list (Advanced) and then click Next Scroll down and select Network Adapters and then click Next Then select Microsoft as the Manufacturer and Microsoft Loopback Adapter and then click Next On the confirmation screen click Next. Then when the installation finishes click Finish. Once this has completed you will find a new network adapter in the Network Connections. I configured this adapter with a private IP address in a range that I don’t use at home or work. Next I added a second Virtual Adapter to the Virtual Windows XP machine and bound this to the new Loopback Adapter. I assigned a static address to this in the same range as the Loopback adapter. Because the network I am connecting to uses a number of subnets I wrote two quick CMD scripts. One adds the routes on the host, the other removes them. Virtual PC also creates shortcuts for applications installed in the guest on the Start Menu of the host. To connect to my VPN I can run this and it hides Virtual Machine’s desktop and the VPN client looks like it is running on the Windows 7 machine. I then run my script to create the routes and I can work away. When I disconnect the VPN I run another script to delete the routes again. Of course I can add shortcuts to all three actions to my desktop to ease the process. Not quite as clean as installing the client direc[...]
Sun, 26 Apr 2009 12:22:14 GMT
There is a new user group coming to town and starting the right way – with touch related demos and fresh Windows 7 goodness.
The aim of the SWUG is to support and provide advice to consumers, power users and small business in regards to the Microsoft Windows Operating System and related products. The user group will showcase the Windows Operating System and provide demonstrations of key components of Windows can be used both at home and in your business.
The User Group will also focus on related Microsoft Products including Windows Mobile, Windows Home Server, Microsoft Office, Windows Live and XBOX 360 and how they can be used to enhance the Windows user experience.
The first meeting will be at Microsoft in Sydney on the 13th of May, 2009. Here’s the details.
Date: Wednesday 13th May 2009
Time: 6pm – 9pm
6:00pm – Introduction
6:10pm – News with Q&A session
6:30pm – Windows 7 RC Demonstration
7:20pm – Break
7:40pm – Windows Touch including a demonstration on the HP Touchsmart PC
8:20pm – Close
If you can make it to the first meeting, please RSVP to email@example.com
I’ve already put it in my calendar so if you can make it I’ll be seeing you there. You may also want to add the RSS Feed from the SWUG blog to your feed reader, so you can keep tabs on future meetings.(image)
Thu, 16 Apr 2009 10:29:42 GMT
Previously I blogged about an issue I was having on one of my PCs with Live Mesh. The problem was that Moe.exe (the process behind Live Mesh) was consuming excessive CPU when ever it was running. This has obvious ill effects on the battery life and overall system performance.
I was hoping that the recent update to Live Mesh would of fixed it. Unfortunately this was not the case. However since I was only experiencing this issue on one of my machines I decided to see if I could find a fix. I did.
What I did was remove my problematic machine from my Mesh. I then copied the contents of the synchronised folder to another location on my hard drive (as a precaution) and deleted everything in the target folder. I then re-added my machine to my Mesh and set up synchronisation for that folder again.
In the Before shot below the yellow line shows the percentage of the CPU that Moe.exe was using.
After the fix it consistently looks more like this:
A vast improvement and suddenly Live Mesh is useful to me again.(image)