Way back in the early turn of the century (probably about 2003) I had a Palm Treo phone, I believe it was a 180g, a monochrome device that was one of the earliest ‘smart phones’ around, although it wouldn’t look too smart now. I loved it, even though it was old technology even when I got it.
Around the same time a friend and work college of mine, John McDougall, purchased one of the early iPaq devices, a glorious device running a colour screen. It was amazing. Remember, the market at the time wasn’t concerned that these devices had no phone, phones were supposed to be separate from your PDA back then, despite the best efforts of a few manufacturers.
I remember one conversation where John derided my Treo (and I don’t mean that in a nasty way John) for running an OS which did not “properly” multi-task. “It’s a phone!” I told him, “Who cares?” “I can still have multiple applications running – or at least open, at the same time”. However his harsh words still lingered on toiling in the back of my mind...
Both our devices had hundreds of applications, both free and paid for, that we could source from a variety of locations on the web with little effort, and both were a joy to use in different ways.
That was about 8 years ago.
Soon after I bought an ordinary Nokia phone and an iPaq 4150, mainly as the Treo would often crash when answering an incoming call, and it was as uncomfortable as hell to hold against your ear for any length of time.
But that’s not the point I’m trying to make here.
This week Apple announced the iPad (apparently Version 2 will have wings!), a device running the iPhone OS. That means it currently doesn’t multi-task. That means it has no Flash support. That means you can only use Apple approved applications purchased via the App Store. That doesn’t mean rouge diallers and other nasties don’t already exist.
You may not even be able to buy ebooks for it in the UK (at least not initially). It hasn’t even got phone functionality (which would be odd I suppose), so in essence it’s an iPod touch with a very big screen. All this in a device that’s going to be “perceived” as a computer.
Don’t get me wrong, the iPad is a lovely piece of engineering from what I can tell, but it’s only an evolution in the hardware stakes. As far as the OS goes… well I didn’t want it on a phone, but on this, you’ve got to be kidding me! It is beautifully designed as far as presentation goes though, Very slick. However, I guess I’m not an average user. I think I’ll let Mr Stephen Fry buy, and keep, my one.
It’s not that I don’t even like this form factor, I really do. I loved my (now demised) HP Tablet PC (you know, one of those things that had a touch screen, a keyboard, and could be put into slate mode). This was however bulky to use and the battery life was only a couple of hours or so, 10 hours from this device will be very good and sets the benchmark for other devices to follow.
I think my ideal form factor could be something like the Apple iPad (and to me the big bezel around the screen could be a good thing) that slots into a keyboard or other portable type docking station to allow a real keyboard to be used (essentially like a laptop, plonk it into the bottom half of a laptop, with hinges and the additional ports!). How about if this was Bluetooth so I could use it or another keyboard wirelessly too?
It’s no secret that I’m a Windows man primarily, and in this rare case I actually feel a little pleased that the HP slate and others will be running Windows 7, you know, a real OS. Let’s hope the hardware measures up. If only Apple had seen fit to put OS X on the iPad. I still wouldn’t have got one, well, probably not, but I’d be more impressed.
Summary: Fail.
That’s possibly a bit harsh. Let’s just say it’s not what I’m looking for, it ticks the wrong boxes for me. It's a 'consumer device' not only in terms of market, but also in terms of functionality; it's designed more for consuming media than creating it. That's not what I'm after, but many will be, however even on this front I want to say "Must try harder".
Of course, Mr Fry and others will be snapping them up and I'm absolutely sure most people who do will be happy. It does look and will perform well, for what it does. It certainly doesn't deserve some of the accolades it's been getting, at least not in my eyes. Then again, some reviews have also been too harsh.
If you can’t wait to try one out I only have one suggestion to you. Get an iPod touch and put your face very close to it. It’s the next best thing to being there.
In the meantime if somebody brings out something similar, with the detachable wireless keyboard I mention above, and running Windows, well let’s just say I’m reaching for my wallet just at the thought.
Google is probably hoping the “Me Too” manufacturers will adopt either Android or Chrome, and I wonder where Windows Mobile 7 will fit into all of this. Any plans from Symbian in this arena, the last I heard the Nokia web device (MID, or whatever you call it) was running a variant on Linux, but at least this is a capable OS and can be made very pretty too. Not that Symbian isn't, in fact I do have a soft spot for Symbian as the underlying OS, but the UI plastered on top has let it down badly in the past.
I’d still prefer Windows 7 though, that’s where all my investment and knowledge is. Oh if only Windows 7 were multi-touch capable…. Hold on a moment ;-)
Sunday, 31 January 2010
Thursday, 28 January 2010
WHS: The Big Install (Part 2)
Well, I've got the remote access running now by manually configuring the ports on my router, including opening the required port for WebGuide to stream media.
Now that this is working I'm able to upload files to the home server via drag and drop in Internet Explorer, which will be useful, but not as useful as it was in the days prior to SkyDrive and Mesh. It's nice to know the only limits I'll have are my own disc space though.
And whilst I'm able to connect to the server via remote desktop, I'm not yet able to connect to any client machines. This is probably because I need to re-start, but unfortunately I didn't have time to test the laptop this morning, and the desktop machine is still less that 70% through its first backup at the time of writing (about 10:25), despite having kicked this off at about 20:30 last night (hopefully subsequent backups will be tiny, that's what you'd expect, if that's not the case I'm in trouble for disc space anyway).
One of the things I need to see after the desktop backup completes is if the media files get put into the media directories automatically. If not I'll be copying these with SyncToy periodically, but at least then I'll be able to remove them from the backup cycle, which to be fair is where most of the backup file size comes from.
The other feature I've made use of today is remote desktop via the Mesh client, which is really useful, but also incredibly slow (I guess the backup isn't helping). I've since opened up the required ports, but again I need to restart before these changes take place.
No doubt I'll elaborate in my next post.
Now that this is working I'm able to upload files to the home server via drag and drop in Internet Explorer, which will be useful, but not as useful as it was in the days prior to SkyDrive and Mesh. It's nice to know the only limits I'll have are my own disc space though.
And whilst I'm able to connect to the server via remote desktop, I'm not yet able to connect to any client machines. This is probably because I need to re-start, but unfortunately I didn't have time to test the laptop this morning, and the desktop machine is still less that 70% through its first backup at the time of writing (about 10:25), despite having kicked this off at about 20:30 last night (hopefully subsequent backups will be tiny, that's what you'd expect, if that's not the case I'm in trouble for disc space anyway).
One of the things I need to see after the desktop backup completes is if the media files get put into the media directories automatically. If not I'll be copying these with SyncToy periodically, but at least then I'll be able to remove them from the backup cycle, which to be fair is where most of the backup file size comes from.
The other feature I've made use of today is remote desktop via the Mesh client, which is really useful, but also incredibly slow (I guess the backup isn't helping). I've since opened up the required ports, but again I need to restart before these changes take place.
No doubt I'll elaborate in my next post.
Tuesday, 26 January 2010
WHS: The Big Install (Part 1)
As per my last entry, I gave up trying to recover the (many years worth of) data on my Linux HDD pair that was destroyed in the upgrade from Ubuntu 9.04 to 9.10, and have started the install of the new Windows Home Server machine.
I wanted to set the machine up as follows:
Primary Drive: SATA 1Tb (An old SATA 300 Samsung F1 from my desktop machine)
Second Drive: PATA 500Gb (The data drive from the old Ubuntu Box)
Third Drive: PATA 300Gb (The system drive from the old Ubuntu Box)
This was where I fell at the first hurdle however. I know the 1Tb SATA drive is working; however try as I may the BIOS could not detect it (the motherboard is a fairly old nForce 2 model in a Shuttle SN45 V3). After some time trying to work out what was going wrong, I substituted the 1Tb drive for an old 200Gb SATA 150 drive. This was recognised instantly and at a total of 1Tb unformatted storage, I decided to cut my losses and go with it, albeit with an already heavy heart.
So now my machine configuration is:
Primary Drive: PATA 500Gb (The data drive from the old Ubuntu Box)
Second Drive: PATA 300Gb (The system drive from the old Ubuntu Box)
Third Drive: SATA 200Gb (SATA 150)
All good, albeit not optimal, but then I can add more USB drives later, with an additional power cost.
The next step went relatively easily, if slowly, that was to install the Windows Home Server OS onto the machine. I left this running after I'd entered as much information as it required, and went to bed.
The following morning I went through the remainder of the configuration (setting Administrator password, etc.) and after eventually finding the drivers, installed the network card and connected to the network, then stepped through the Windows Update cycle via remote desktop until all updates were downloaded.
After this I hit the second hurdle; although I could connect via remote desktop, the WHS connector application kept telling me the password I was supplying was incorrect, which I knew for sure wasn't the case.
Later that day I Googled the answer which was that the server date and time was incorrect (I was even in the wrong Time Zone despite telling the installation to choose "English (United Kingdom)") and after adjusting these, the connector software did (connect, that is).
So I've now started to install some Add-ins which I'll probably continue doing over the coming weeks.
I also performed the first back-up of my (now only working) laptop, which I left running overnight and was reported as completed this morning.
I've now got to back-up the main desktop machine upstairs, which I'm worried may fill the HDD (so I've done some pruning and will be using that failed 1Tb Samsung F1 drive as a local backup store), and work out the best way of storing my media on the server so that it acts as a mini media hub.
The other task high on my list is to get the machine accessible from the outside world. I'll be referring to my book tonight and will probably be manually configuring the router to do this.
Naturally, I'll let you know how I get on here, but so far it's going fairly well.
Fingers crossed it stays that way.
I wanted to set the machine up as follows:
Primary Drive: SATA 1Tb (An old SATA 300 Samsung F1 from my desktop machine)
Second Drive: PATA 500Gb (The data drive from the old Ubuntu Box)
Third Drive: PATA 300Gb (The system drive from the old Ubuntu Box)
This was where I fell at the first hurdle however. I know the 1Tb SATA drive is working; however try as I may the BIOS could not detect it (the motherboard is a fairly old nForce 2 model in a Shuttle SN45 V3). After some time trying to work out what was going wrong, I substituted the 1Tb drive for an old 200Gb SATA 150 drive. This was recognised instantly and at a total of 1Tb unformatted storage, I decided to cut my losses and go with it, albeit with an already heavy heart.
So now my machine configuration is:
Primary Drive: PATA 500Gb (The data drive from the old Ubuntu Box)
Second Drive: PATA 300Gb (The system drive from the old Ubuntu Box)
Third Drive: SATA 200Gb (SATA 150)
All good, albeit not optimal, but then I can add more USB drives later, with an additional power cost.
The next step went relatively easily, if slowly, that was to install the Windows Home Server OS onto the machine. I left this running after I'd entered as much information as it required, and went to bed.
The following morning I went through the remainder of the configuration (setting Administrator password, etc.) and after eventually finding the drivers, installed the network card and connected to the network, then stepped through the Windows Update cycle via remote desktop until all updates were downloaded.
After this I hit the second hurdle; although I could connect via remote desktop, the WHS connector application kept telling me the password I was supplying was incorrect, which I knew for sure wasn't the case.
Later that day I Googled the answer which was that the server date and time was incorrect (I was even in the wrong Time Zone despite telling the installation to choose "English (United Kingdom)") and after adjusting these, the connector software did (connect, that is).
So I've now started to install some Add-ins which I'll probably continue doing over the coming weeks.
I also performed the first back-up of my (now only working) laptop, which I left running overnight and was reported as completed this morning.
I've now got to back-up the main desktop machine upstairs, which I'm worried may fill the HDD (so I've done some pruning and will be using that failed 1Tb Samsung F1 drive as a local backup store), and work out the best way of storing my media on the server so that it acts as a mini media hub.
The other task high on my list is to get the machine accessible from the outside world. I'll be referring to my book tonight and will probably be manually configuring the router to do this.
Naturally, I'll let you know how I get on here, but so far it's going fairly well.
Fingers crossed it stays that way.
Saturday, 23 January 2010
All Gone
It's final and official. The upgrade from Ubuntu 9.04 to 9.10 killed all the data on both my drives.
I have now officially given up trying to retrieve anything.
Let the Windows Home Server installation trials begin.
Watch this space.
I have now officially given up trying to retrieve anything.
Let the Windows Home Server installation trials begin.
Watch this space.
Saturday, 16 January 2010
Microsoft Virtual PC 2007
I've been a huge fan of running virtual machine since James introduced me to VMWare a couple of years ago, not only for running Linux distributions (usually Ubuntu) for trying stuff out, but also for testing installations in an easily recoverable 'Clean' environment where I would:
1. Create a Virtual Machine of the OS (Always XP, but could be any OS), ensure all the patches for this OS are applied.
2. Zip up the virtual machine image files and store them in a safe place.
3. Run all the tests etc. inside the VM we just created.
Then when you want to repeat the tests from scratch, it's simply a matter of unzipping the virtual machine image files over the top of the existing files and you're back to a clean machine next time you restart.
I know VMWare would allow you to do things like saving the virtual machine state at a moment in time so that this may not be necessary, but this was an approach I trusted 100% and which worked well for me on several occasions. Best of all you could zip or copy the VM image files at any time to save the machine in various states, allowing quicker testing from different start points or even running multiple simultaneous copies of identical virtual machines.
Recently I wanted to test a deployment against a clean XP machine for work. My immediate response was to download the latest version of VMWare Server and install this, however after the download stage I remembered that whilst installing "XP Mode" on my home PC I had noticed that the underlying Virtual Machine software, Microsoft Virtual PC 2007, was also able to run on windows XP (and all versions of Vista and Win7, not just the top editions), so I thought I'd give it a try.
I'm pleased to report it all just works, with no particular jumping through hoops. There is a Microsoft version of VMWare Tools (although I don't know if there will be a Linux compatible install yet) allowing such things as dragging of files from the host machine to the virtual machine, shared clipboard, and will even dynamically resize the screen resolution when running in a windowed mode, which is all highly useful.
It's all very slick, and allows the machine image files to be manipulated in a slightly easier way then VMWare (where you'd need to manually edit the files to rename them, with this you justload it up, it fails, you point it to the new file and it works).
And whilst it has some things I'd see as an advantage over VMWare such as not installing those nasty network drivers, it does only seem to allow the use of one processor (core) on the virtual machine, although I'm still investigating this.
Overall, Virtual PC feels more integrated than the VMWare equivalents, but somehow the simplicity makes it feel a little less configurable, but I'm still invetigating. Either way it looks like it could be a good choice for getting into running virtual machines. I'll post more if I find anything, either good or bad, worth noting.
1. Create a Virtual Machine of the OS (Always XP, but could be any OS), ensure all the patches for this OS are applied.
2. Zip up the virtual machine image files and store them in a safe place.
3. Run all the tests etc. inside the VM we just created.
Then when you want to repeat the tests from scratch, it's simply a matter of unzipping the virtual machine image files over the top of the existing files and you're back to a clean machine next time you restart.
I know VMWare would allow you to do things like saving the virtual machine state at a moment in time so that this may not be necessary, but this was an approach I trusted 100% and which worked well for me on several occasions. Best of all you could zip or copy the VM image files at any time to save the machine in various states, allowing quicker testing from different start points or even running multiple simultaneous copies of identical virtual machines.
Recently I wanted to test a deployment against a clean XP machine for work. My immediate response was to download the latest version of VMWare Server and install this, however after the download stage I remembered that whilst installing "XP Mode" on my home PC I had noticed that the underlying Virtual Machine software, Microsoft Virtual PC 2007, was also able to run on windows XP (and all versions of Vista and Win7, not just the top editions), so I thought I'd give it a try.
I'm pleased to report it all just works, with no particular jumping through hoops. There is a Microsoft version of VMWare Tools (although I don't know if there will be a Linux compatible install yet) allowing such things as dragging of files from the host machine to the virtual machine, shared clipboard, and will even dynamically resize the screen resolution when running in a windowed mode, which is all highly useful.
It's all very slick, and allows the machine image files to be manipulated in a slightly easier way then VMWare (where you'd need to manually edit the files to rename them, with this you justload it up, it fails, you point it to the new file and it works).
And whilst it has some things I'd see as an advantage over VMWare such as not installing those nasty network drivers, it does only seem to allow the use of one processor (core) on the virtual machine, although I'm still investigating this.
Overall, Virtual PC feels more integrated than the VMWare equivalents, but somehow the simplicity makes it feel a little less configurable, but I'm still invetigating. Either way it looks like it could be a good choice for getting into running virtual machines. I'll post more if I find anything, either good or bad, worth noting.
Subscribe to:
Posts (Atom)