I recently took part in a Fiat 500 Fun Run. I haven’t taken part in one of these kinds of events since I was really young, so I couldn’t quite remember how it would turn out. The event mainly involved following a set of clues, which would lead you around the picturesque roads of the Isle of Wight. All done, of course, in a Fiat 500! All of the cars then assembled at the endpoint, which was an excellent sight.
As I bought myself a Fiat 500 last year from the dealer that organised the event (Harwoods), I was invited along, although the event was open to all Fiat 500 owners. It was even attended by a couple of original Fiat 500’s. I’ve uploaded a few photos from the day in the ‘Photos’ section. More photos to come soon.
It was absolutely fantastic event, superbly organised, and as our team won, it was even better! ;o)
I have a small low-power x86 machine at home running Debian 5.0. I regularly check for updates to any of the packages I have installed on it, and for a while its been offering an upgrade to MySQL. I dont use MySQL much at home, so I havent been too bothered about keeping that up to date. However, I got fed up of it nagging me, so I decided to proceed with the update. The following is what happened:
Preparing to replace mysql-server 5.0.51a-24 (using .../mysql-server_5.1.34-0.dotdeb.1_all.deb) ...
Unpacking replacement mysql-server ...
(Reading database ... 120744 files and directories currently installed.)
Removing mysql-server-5.0 ...
Stopping MySQL database server: mysqld.
Removing mysql-client-5.0 ...
Processing triggers for man-db ...
Selecting previously deselected package mysql-client-5.1.
(Reading database ... 118764 files and directories currently installed.)
Unpacking mysql-client-5.1 (from .../mysql-client-5.1_5.1.34-0.dotdeb.1_i386.deb) ...
Selecting previously deselected package mysql-server-5.1.
Unpacking mysql-server-5.1 (from .../mysql-server-5.1_5.1.34-0.dotdeb.1_i386.deb) ...
Processing triggers for man-db ...
Processing triggers for menu ...
Setting up mysql-client-5.1 (5.1.34-0.dotdeb.1) ...
Setting up mysql-server-5.1 (5.1.34-0.dotdeb.1) ...
Installing new version of config file /etc/init.d/mysql ...
Stopping MySQL database server: mysqld.
Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed!
Continue reading 'Upgrading MySQL 5.0 to 5.1 on Debian 5.0'»
I was experiencing some issues whilst restoring some backups made with Vizioncore vRanger Pro. I’m currently using version 3.2.5.6, which is well over a year old. The obvious first step is to update the software to the latest version. At the time of writing, vRanger Pro is at version 3.2.9.7, but version 4 is on the horizon. Upgrading something as crucial as backup software makes me a little twitchy. Its important to know that you’ll still be able to take backups successfully once the upgrade is complete, and that you’ll be able to restore backups you’ve previously made. I had a good look around Vizioncore’s website for some information on the recommended upgrade procedure. Aside from a vague posting on their support forum, there was no official procedure that I could find. Should you really have to place a support call for something like this? Anyway, I managed to get the answers I was looking for, so thought I’d post them here:
Firstly, and it’s a biggie: You cannot ‘upgrade’ using the installation executable. You must first uninstall the old product.
What about configuration settings? – I was assured by Vizioncore support that after the uninstall, all configuration settings, license files, logs, etc, are all left behind. Once you install the new version, it will pick up all of your previous configuration settings from these files.
If, like me, you want to be extra sure that you wont lose your configuration, make a copy of *.dat, *.mdb and *.lic files from your vRanger installation folder before the uninstall. You may also wish to backup your log files, etc.
Then just execute the .msi that you downloaded from the Vizioncore website, and follow the prompts.
Your scheduled tasks should also be unaffected, and will run as before using the newly installed vRanger executable.
I recently bought an O2 Mobile Broadband ‘Pay & Go’ dongle. The Huawei E160 variety. Its a neat little dongle, which also has a slot for a MicroSD card.
A colleague of mine wanted to get some kind of mobile broadband solution for his netbook – an Acer Aspire One. Brilliant little machine. I fancy a Samsung NC10 myself, or maybe an Asus 1008HA Seashell.
Anyway, he’s running the standard Acer OS – Linpus. He already had the ‘Mobile Partner’ application installed, which is required if you want to connect using a Huawei modem. We plugged the dongle in, and it was recognised by the software within a few seconds, albeit as a Huawei E220 (technically identical to the E160). It picked up a perfectly reasonable O2 3G signal considering we were indoors. Next came the creation of a ‘profile’ for the connection. We set up a new one, called it ‘O2′, and attempted to enter the settings. Continue reading 'O2 3G Mobile Broadband on Acer Aspire One Netbook'»
Comments (0) 
WordPress Themes