Technology Tales

Adventures & experiences in contemporary technology

On Photoshop Elements 7

10th November 2008

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.

Getting VirtualBox 2.02 working on Ubuntu 8.04

10th October 2008

Seamless VirtualBox VM Application Windows on Ubuntu

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 accomplish 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

6th September 2008

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.

Windows XP running on VirtualBox OSE

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 use 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.

Getting VirtualBox working on Ubuntu after a kernel upgrade

27th July 2008

In previous posts, I have talked about getting VMware Workstation back on its feet again after a kernel upgrade. It also seems that VirtualBox is prone to the same sort of affliction. However, while VMware Workstation fails to start at all, VirtualBox at least starts itself even if it cannot get a virtual machine going and generates errors instead.

My usual course of action is to fire up Synaptic and install the drivers for the relevant kernel. Looking for virtualbox-ose-modules-[kernel version and type] and installing that usually resolves the problem. For example, at the time of writing, the latest file available for my system would be virtualbox-ose-modules-2.6.24-19-generic.  If you are a command line fan, the command for this would be:

sudo apt-get install virtualbox-ose-modules-2.6.24-19-generic

The next thing to do would be to issue the command to start the vboxdrv service and you’d be all set:

sudo /etc/init.d/vboxdrv start

There is one point of weakness (an Achilles heal, if you like) with all of this: the relevant modules need to be available in the first place and I hit a glitch after updating the kernel to 2.6.24-20 when they weren’t; I do wonder why Canonical fail to keep both in step with one another and why the new kernel modules don’t come through the updates automatically either. However, there is a way around this too. That means installing virtualbox-ose-source via either Synaptic or the command line:

sudo apt-get install virtualbox-ose-source

The subsequent steps involve issuing more commands to perform a reinstallation from the source code:

sudo m-a prepare

sudo m-a auto-install virtualbox-ose

Once these are complete, the next is to start the vbox drv as described earlier and to add yourself to vboxusers group if you’re still having trouble:

sudo adduser [your username] vboxusers

The source code installation option certainly got me up and running again and I’ll be keeping it on hand for use should the situation raise its head again.

A first look at Ubuntu 8.10

20th July 2008

I must admit that my curiosity got the better of me when screenshots of Ubuntu’s 8.10, otherwise known as Intrepid Ibex, started to make their appearance. It is only at alpha2 stage so it’s definitely a no-no for production systems. However, it does run surprisingly smoothly even at this stage. Yes, I have seen rough edges and the biggest of them all has made me install it onto my spare PC; there is certainly tendency for systems to hang when you try running 8.10 in virtual machines, my preferred method for these kinds of explorations. Try it in VirtualBox and kernel panic messages ensue while you can log in on VMware Workstation only for the desktop never to load. Those could be major deficiencies for some but they have both been reported with the former being seen by many and the latter being flagged by my own self.

Because I was using a version with the alternate installer, the usual slickness that we expect of Ubuntu installations wasn’t apparent. I am sure that will change in time for the final release but I didn’t find it too taxing to get things going with this means. Nevertheless, I reckon that we will see the usual feel return in later development versions and very much in time for the final release. Because I was installing over the top of a previous Ubuntu installation, I didn’t want to lose everything but I needed to leave it wipe out the previous root system partition for it to continue without freezing. Because my home area is on a separate partition, there was no problem and it picked up settings like desktop backgrounds without a fuss. One thing that might annoy some is that all this takes manual intervention; you don’t get the sort of non-destructive and seamless upgrade capability that openSUSE 11 gives.

What you get when the installation is completed is a Linux desktop that won’t look too different from what we are used to using. Of course, we get the New Human theme with its tasteful chocolate tones in place of the previous default orangey browns. They need to sort out a bug (another of my reports)  where black text is being displayed on dark backgrounds on the default display of drop down menus in Firefox and maybe look into why changing the level of enhancements from Compiz Fusion messes up the display of the workspace switcher in the task bar but it’s fine apart from this.

Otherwise, it’s a case of steady as she goes with OpenOffice 2.4, Firefox 3 and so on. That may change as time goes on OpenOffice 3 looming in the horizon. For some, all this continuity is all well and good but I could foresee comments front some parts that nothing dramatic is happening and that Ubuntu cannot afford to stand still with the advances of Fedora, openSUSE, Mandriva and so on. Saying that, I personally like the continuity because it doesn’t mean that my apple cart is going to get overthrown now and again. Indeed, you could say that the whole Linux distribution market has matured very nicely with evolution being the order of the day and I suppose that Ubuntu needs to be seen to be evolving more than perhaps it has been doing.

In summary, it’s early days for Intrepid Ibex but it works well even at this stage. In fact, it is running sufficiently so that I am writing this very post in a Firefox session running on the thing.  It’ll be interesting to see how it goes from here and if any more pleasant surprises are visited upon us. After the “safety first” approach of Hardy Heron, I suppose that Canonical can feel a little more adventurous so we’ll see what comes. In the meantime, Here are a few screenshots below for your perusal:

Disk corruption can be virtual too

16th July 2008

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.

Watch where you store your virtual machines when using VMware on Linux

12th July 2008

My experience is with Ubuntu on this one but I have found that you need to be careful as regards the file system used by the drive where you keep your virtual machines. If it is NTFS, VMware can fail to start a VM because it cannot create a virtual memory file while it presents as physical memory to a guest operating system. Use ext2 or ext3 and there should be no problem, even if that means formatting a drive to fulfill the need. That’s what I did and all was well thereafter.

VMware going amuck…

4th February 2008

Over the last week, I have had VMware misreport the speed of my CPU and have virtual machines like they’re on speed. To cure it, I tried restarting the PC a few times but that yield no joy, even if it did work the last time that VMware did this on me. Following some instructions from the Ubuntu forums set things back onto an even keel again. The commands required follow:

sudo apt-get install linux-headers-$(uname -r) build-essential gcc-3.4

tar xzf VMware-workstation-6.0.2-59824.x86_64.tar.gz

export CC=/usr/bin/gcc-3.4 && cd vmware-distrib && sudo ./vmware-install.pl

The first of these adds in a specific version of the GNU C compiler while also adding kernel headers; the latter weren’t needed on my system since I already had them. The second extracts files from the tarball while the last performs the required installation rites.

Setting up openSUSE in VMware Workstation

12th November 2007

It should have been as straightforward as following the instructions on the openSUSE website but a bug in VMware Tools derailed things on me. The usual procedure would have you starting by selecting Install VMware Tools from the VM menu before popping into the virtual machine to do the rest. Once binutils, gcc, gcc-c++, kernel-source and make are in place, next steps should involve using YaST to install the RPM for you to run the vmware-config-tools.pl script from the terminal.

However, a bug in compat_slab.h puts a stop to any hopes of installing the vmhgfs component. That’s needed if you want to enable the shared folders feature; looking in /mnt/hgfs then would get you to any shared folders Everything else will be there but why miss out on one piece of functionality when it come in useful?

Having found a useful thread on the subject, here’s my way forward: it is as the expected procedure up to the point of installing the RPM. With VMware Tool installation on a Linux guest, you have two options: use RPM as described or use the compressed tarball. The latter seems the better course. Extract the contents into a folder and navigate to that folder. When there go into vmware-tools-distrib/lib/modules/source and extract the file vmhgfs.tar. Proceed into the resulting vmhgfs-only contained wherever you put it and perform the following edit of compat_slab.h:

Change

#if LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 22) || defined(VMW_KMEMCR_HAS_DTOR)

to

#if LINUX_VERSION_CODE <= KERNEL_VERSION(2, 6, 22) || defined(VMW_KMEMCR_HAS_DTOR)

After that, recreate and replace vmhgfs.tar before issuing the following command in the terminal window while in the vmware-tools-distrib directory: ./vmware-config-tools.pl (anything prefixed with "./" picks up the file from the current working directory rather than where system binaries are stored). A kernel compilation will be involved but all of the defaults should be sensible. Hopefully, all will work well after this.

Update: I am left with a number of outstanding issues that I need to resolve. Lack of internet access from the VM is one of them and a constant forgetfulness regarding the nationality of my keyboard (it’s British) might be another. In the interim, I have removed VMware tools until I can spend some time setting these to rights. Internet access has returned and British keyboard layout is being interpreted correctly in the meantime…

Choices, choices…

10th November 2007

Choice is a very good thing but too much of it can be confusing and the world of Linux is a one very full of decisions. The first of these centres around the distro to use when taking the plunge and there can be quite a lot to it. In fact, it is a little like buying your first SLR/DSLR or your first car: you only really know what you are doing after your first one. Putting it another way, you only how to get a house built after you have done.

With that in mind, it is probably best to play a little on the fringes of the Linux world before committing yourself. It used to be that you had two main choices for your dabbling:

  • using a spare PC
  • dual booting with Windows by either partitioning a hard drive or dedicating one for your Linux needs.

In these times, innovations such as Live CD distributions and virtualisation technology keep you away from such measures. In fact, I would suggest starting with the former and progressing to the latter for more detailed perusal; it’s always easy to wipe and restore virtual machines anyway and you can evaluate several distros at the same time if you have the hard drive space. It also a great way to decide which desktop environment you like. Otherwise, terms like KDE, GNOME, XFCE, etc. might not mean much.

The mention of desktop environments brings me to software choices because they do drive what software is available to you. For instance, the Outlook lookalike that is Evolution is more likely to appear where GNOME is installed than where you have KDE. The opposite applies to the music player Amarok. Nevertheless, you do find certain stalwarts making a regular appearance; Firefox, OpenOffice and the GIMP all fall into this category.

The nice thing about Linux is that distros more often than not contain all of the software that you are likely to need. However, that doesn’t mean that its all on the disk and that you have to select what you need during the installation. There might have been a time when it might have felt like that but my recent experience has been that a minimum installation is set in place that does all of the basics and you easily can add the extras later on an as needed basis. I have also found that online updates are a strong feature too.

Picking up what you need when you need it has major advantages, the big one being that Linux grows with you. You can add items like Apache, PHP and MySQL when you know what they are and why you need them. It’s a long way from picking applications of which you know very little at installation time and with the suspicion that any future installation might land you in dependency hell while performing compilation of application source code; the temptation to install everything that you saw was a strong one. The learn before you use approach favoured by the ways that things are done nowadays is an excellent one.

Even if life is easier in the Linux camp these days, there is no harm in sketching out your software needs. Any distribution should be able to fulfill most if not all of them. As it happened, the only third party application that I have needed to install on Ubuntu without recourse to Synaptic was VMware Workstation and that procedure thankfully turned out to be pretty painless.

  • All the views that you find expressed on here in postings and articles are mine alone and not those of any organisation with which I have any association, through work or otherwise. As regards editorial policy, whatever appears here is entirely of my own choice and not that of any other person or organisation.

  • Please note that everything you find here is copyrighted material. The content may be available to read without charge and without advertising but it is not to be reproduced without attribution. As it happens, a number of the images are sourced from stock libraries like iStockPhoto so they certainly are not for abstraction.

  • With regards to any comments left on the site, I expect them to be civil in tone of voice and reserve the right to reject any that are either inappropriate or irrelevant. Comment review is subject to automated processing as well as manual inspection but whatever is said is the sole responsibility of the individual contributor.