It was just over a year ago that I gave Linux a go after Windows XP gave me a torrid time of it. Since then, I have been able to work more than happily with it and have picked a few new and useful tricks along the way too. All in all, it has been a good experience and I have been able to resolve most of the issues that I have seen. The various Ubuntu upgrades along the way have been taken in their stride too. Version 7.04 was the first one with 7.10 following on immediately afterwards. 8.04 went in equally seamlessly as did 8.10. Some may decry what they might perceive as the glacial nature of any changes but the flip-side is that change can cause disruption so my vote is for the more gradual approach, whatever others might think. In line with this, I haven’t noticed too many changes in Ubuntu’s latest release and any that I have seen have been of the pleasant kind. Saying that, it’s so much better than the contortions surrounding Windows upgrades. All in all, Linux is being kind to me and I hope that it stays that way.
Archive for the ' Windows XP' Tag
On Photoshop Elements 7
In recent days, I have been playing around with Photoshop Elements 7, doing the same sort of things that I have been doing with Elements 5. Reassuringly, I can still find my way around, even if the screen furniture has been moved about a little. My Pentax K10D is recognised and I am able to set white balance to get sensible results. On the images that I was testing, things started to look too warm in the Cloudy and Shade settings but that’s all part and parcel of processing photos taken in early November. The results of my exertions look decent enough and you can see them in a post on my hillwalking blog.
I realise that Adobe has been promoting the ability to easily airbrush unwanted objects from images and enhance blue skies but there’s no point having all of that if functionality available in previous versions does not work as expected. Thankfully, this is largely the case but there are a few niggles. I have working the new Elements on a Windows XP SP3 virtual machine running in VirtualBox 2.04 on Ubuntu 8.10 so I don’t know if that contributed in any way to what I encountered. One gigabyte of memory is allocated to the VM. The files were stored in the Ubuntu file system and accessed using VirtualBox’s functionality for connecting through to the host file system. File access was fine but I was unable to directly open a file for full editing from the Organiser, something that I have doing very happily with Elements 5. I also noted a certain instability in the application and using the hand tool to get to the top left hand corner of an image sent the thing into a loop, again something that Elements 5 never does. Otherwise, things work as they should but what I saw points to the need for an update to correct any glitches like these and I hope that there is one. For now, I will persevere and see if I can make use of any additional functionality along the way.
Alt-Click problems in Ubuntu-hosted VirtualBox Windows guests
The Alt-Click keyboard.mouse combination is a very common way of working with various flavours of Adobe Photoshop. So it was with some frustration that I couldn’t use it while working in Photoshop Elements (still on version 5, by the way; the temptation of newer versions has not struck) on a Windows XP guest in VirtualBox on my main Ubuntu system. A quick google later and a proposed solution was for me a surprising one: going to System->Preferences->Windows on the host OS and changing the setting of the Movement Key from Alt to Super (Windows key on many keyboards). That was enough to set all in order. It seems that a setting on the host operating system was preventing a piece of software running on the guest from behaving as expected. That’s all in the past now that I have got my clone brush functionality back and can work as normal again.
Getting VirtualBox 2.02 working on Ubuntu 8.04
Having run VirtualBox OSE (1.5.6) for a while now, I succumbed to the idea of grabbing the latest version from the VirtualBox website and putting it on my main Linux box. The idea of having 64-bit support proved irresistible and I did get OpenSolaris to start, even if its being a VMware VM meant that it stalled along the way.
To do this, I needed to rid my system of all traces of the old version before 2.02 would install with a system reboot being needed before the process of installation fully completed. Then, I fired up a Windows XP virtual machine only for it to completely freeze. The hint as to the cause came when I opened up the VM’s settings for the following message to greet me:
Could not load the Host USB Proxy Service (VERR_FILE_NOT_FOUND). The service might be not installed on the host computer.
While it didn’t stop things in their tracks when it came to accessing and changing those settings, it was a vital hint for working out what was happening. It now seems that a problem with USB port support was the cause. The fact that issuing the following command got things going for me appeared to confirm the prognosis.
sudo mount -t usbfs /sys/bus/usb /proc/bus/usb/
Of course, not wanting to have to issue the same command over and over again, I was after a more permanent solution. That involved adding the following lines to /etc/fstab:
#usbfs
none /proc/bus/usb usbfs devgid=46,devmode=664 0 0
A reboot later. that change apparently was enough to settle the matter and I am now able to run VM’s as before. Seamless application mode is going well (the host key - right Ctrl by default - + L key combination is sufficient to toggle the setting on and off), even if it has a few quirks. Two that I have spotted include the usual Ubuntu screen furniture disappearing when maximised windows are displayed and the Windows taskbar appearing when two or more applications are running. That last one may be just as well because individual applications don’t get an Ubuntu taskbar icon each, which is perhaps an idea for a future enhancement. Updating Guest Additions in a VM’s doesn’t seem to change the behaviour but any imperfections are curiosities rather than complaints given how well things run anyway, unless you decide to confound matters by closing and minimising windows but resolving that is just a toggle away. It’s all looking good so far…
Things that I like about VirtualBox OSE
Now that VirtualBox 2.0 is out with its 64 bit operating system support among other things, the version included in Ubuntu 8.04, OSE 1.56, is looking that bit older. Nevertheless, there remains a lot to like about the version that I have been using.
For one thing, its shared folders functionality doesn’t trip up Photoshop Elements like VMware does. VMware so hobbled Photoshop’s ability to save back to the Linux file system that it had me looking at the WINE route and I got to using GIMP for a while. VirtualBox brought me back into the Photoshop fold and I seem to like the results that I can get with Elements better than those from GIMP.
Another nicety is the way that guest OS desktops can be resized to fit in a maximised VM window. For this to work, you need VirtualBox Guest Additions in place in the virtual machine but it works very well when all is in place; my experience is with Windows XP. Full screen is on tap too once you use the Host+F combination; the right hand control key is usually the Host key by default. If there is any criticism at all, it might be that seamless application windows are not available in OSE 1.5.6.
Linux kernel changes can upset things but drivers don’t take too long to appear and you can always take matters into your own hands anyway. It’s a far cry from the blithe indifference of VMware and the need to resort to vmware-any-any patching to get things under way again.
All in all, VirtualBox OSE treats me very well. Guest operating systems may seem sluggish at times but it’s never enough to annoy or seriously impede usage. It’ll be interesting to see if a newer version of VirtualBox makes it into Ubuntu 8.10.
Disk corruption can be virtual too
It’s the sort of sight that causes you to fear the worst, an unchanging black screen with a flashing cursor. That was what started greet me in recent days when I tried to fire up a Windows XP guest in VMware Workstation. The cause was the corruption of a virtual disk, an ominous thing that affected a supplemental virtual hard drive that I had added to the virtual machine rather than its main one. There might have been some data on there but it was nothing that I didn’t have elsewhere anyway. Removing the broken disk from the XP VM returned the situation to fuller health and I simply tried creating a new one again. So far, this seems to be working fine but I’ll be keeping a watchful eye on things.
I have no idea why the corruption happened but the broken disk files were created without a VMDK extension so that might indicate that something was amiss with the process that created them. It would be better if VMware highlighted the state of its virtual disks but it was when I tried opening the trashed disk with VirtualBox that a warning was given and VMware did the same when I tried I tried it with that afterwards (opening VMware virtual disks with VirtualBox is possible but you need to ensure that no attempt at importation is made or you could end up with a breakage). I may have discovered the fault in a roundabout manner but it’s better to know what’s gone wrong than not to know at all.
Tags
Adobe Blog Blogging Books Canon Command Line CSS DSLR Firefox Google Hardware HTML IE7 Installation Internet Explorer JavaScript Linux Microsoft MySQL openSUSE Opera Operating System Oracle Perl Photoshop Photoshop Elements PHP Safari SAS SQL Ubuntu UNIX VirtualBox Virtualisation Virtual Machine Vista VMware Web Browsers Windows Windows XP WordPress WordPress.com WordPress plugins XHTML XP
Monthly Archives
-
Photo Gallery
Here are a few teaser photos from my online photo gallery.




