Thursday, February 26, 2009
Touch the Snake...
Of course, it could end up being pants, but the concept is quite tantalising.
Monday, February 16, 2009
I just can't help myself...
After doing all that, I decided to start on a few iTunes files to make sure they were organised sensibly too - particularly the ones that I've bought from the iTMS store. I cannot stand it when things are all categorised using different conventions - it makes things really untidy. Again, iTunes itself does a pretty good job of organising things for you but occasionally it does things wrong. Well, maybe not "wrong" per se, but certainly not the way I'd do it. Particularly the way it handles compilation albums does my head it, so I take matters into my own hands for those.
Whilst going through, I then noticed that virtually every track you buy on iTunes has different metadata embedded in it - I think it depends on the record label, but some tracks have the bare minimum, some are stuffed to the gunnels with irrelevant bits and pieces. So, me being me, I've had to go through and standardise things a bit. You'd think this was easy wouldn't you? But I've come up against all sorts of headaches - there's a lot of hidden data in some of those files and it's a bitch to get to. But eventually I've managed to go through and wipe a lot of the unnecessary stuff, and then complete the more important bits.
A few weeks back, when Apple announced that they were making the entire iTunes Music Store 256kbps non-DRM files, they offered the option of upgrading your existing purchases for 20p a track to change them from 128kbps DRM-protected tracks to the new non-DRM higher bit rate ones. I was quite pleased about this (I hated the 5-burn limit on those tracks more than anything) so I duly clicked the "upgrade" button and prepared to take a hit for about a tenner's worth of non-DRM goodness. However, things are never that simple. Seven of my purchased tracks are not yet available in the new format, so they're still the 128kbps versions. That's annoying me immensely, as you can imagine. Apple reckon they'll soon be available to upgrade too, but I don't know when.
This has presented me with another issue though. Now I have these new shiny versions in 256kbps, but I've ripped the rest of my library as 128kbps and that means THEY NO LONGER MATCH.
I'm quite convinced I can't/won't hear the difference between the two bit rates, but knowing that they ARE different makes me uneasy. I'm seriously considering reripping my CDs at 256kbps now. You see, this is why I'd never be able to get rid of my CD collection in favour of digital versions - there's too much to go wrong in the virtual world. One day, (Apple heresy coming up here...) there will be no iTunes. Then what will we all do?
And then I got to thinking - why am I bothering with all this? Why don't I just leave stuff alone? I've come to the conclusion that I have some kind of computer-related OCD. I need help. Seriously.
Friday, February 6, 2009
Download gMail Mobile app v2.0 for Nokia/Symbian

And whilst I'm dispensing advice, I've just discovered Foxmarks, a Firefox add-on which keeps your bookmarks synced across multiple machines. Just what I've been looking for! And if you want to try it out, they've just released betas for Internet Explorer (why would you be using that?!) and Safari too.
Wednesday, February 4, 2009
Thanks for the memory
This morning, I received the 2GB RAM kit that I ordered, and I've just installed it in my iMac. Now - those of you that have been around for a while (you know who you are) - will remember back in 2005 when I got myself worked up into a frenzy the last time I installed new RAM into my machine. I did have just the 512MB that came pre-installed, so when I found out that optimal performance was to be gained from having two matching RAM modules I bought another one to boost things to 1GB and hopefully unlock the wonders of the mythical "128-bit pipeline".
Now when I had just 512MB, Terminal reported this:
phil-laceys-imac-g5:~ Phil$ ioreg -p IODeviceTree -n memory -S | grep ram-
| "ram-layout-architecture" = <00000002>
| "ram-bus-width" = <00000040>
Then, when I went up to 1GB, I got this:
phil-laceys-imac-g5:~ Phil$ ioreg -p IODeviceTree -n memory -S | grep ram-
| "ram-layout-architecture" = <00000002>
| "ram-bus-width" = <00000080>
At the time, I really couldn't work out whether this meant I was using the 128-bit pipe or not - the bus width had changed, but not the architecture value. But more RAM is always good regardless, so I was happy. Things nipped along quite nicely.
So, for the sake of consistency, I tried the terminal report again now I have two matched 1GB sticks in the iMac - just to see what it would say. So we now have:
phil-laceys-imac-g5:~ Phil$ ioreg -p IODeviceTree -n memory -S | grep ram-
| "ram-layout-architecture" = <00000001>
| "ram-bus-width" = <00000080>
Which is different yet again. However, this Apple knowledgebase article would seem to suggest I am now at the very pinnacle of G5 iMac memory nirvana - 2GB of RAM, in a perfectly matched pair, running on the 128-bit pipeline.
That, my friends, is as good as it gets.
Sunday, February 1, 2009
Backup your backup
Before I saw the Apple Mac light, I was quite invested in PCs. After getting my first one (a 386) as a hand-me-down in my university years, I then bought a brand new Pentium model in 1998. Since then, I've gone through numerous hardware iterations to the cheap and cheerful Dell machine we have now.
I've always been quite thorough with my data backups, and have been very glad of that fact on more than one occasion in the past. However, a peculiar situation reared its head yesterday - and, I hate to say, it was all of my own doing.
Both my Mac and my PC have external hard drives which I use for backups. I tend to keep my old backups, and just create new ones each time until I run out of space and then start deleting the oldest ones to make some room. There were about 4 years' worth of files on my PC backup drive, and I decided that I wanted to copy some of them over to my Mac. They were too big for a memory stick, and the PC doesn't have a DVD writer, so I decided that I'd move the drive from the PC to the Mac and plug it in directly. Both drives have the same power connector and both use USB 2.0, so to save time I left all the cables in situ and just moved the drive.
I unplugged the power supply and USB cable from the Mac backup drive and then set about reconnecting them to the PC drive. I switched the drive on, and then... nothing. Apart from a strange electrical burning smell. Where on earth was that coming from? And why wasn't the drive spinning up?
Now when I said that both drives have the same power connector, that much was indeed true. What I neglected to appreciate was that they use rather diffferent amounts of current. Only 0.2 amps difference, but when a hard drive uses just milliamps that's enough to fry the circuitry.
Needless to say, I was a bit annoyed with myself. But then I started thinking. Exactly what was on that fried drive? Was there anything that I didn't have a copy of somewhere else? Had I inadvertently created a situation where I had forgotten to backup my backup?
Now I knew there was a lot of stuff on there, but it was difficult to remember exactly what. I decided that if it was possible, I'd need to get the drive working again - if only so I could reassure myself that there was nothing on it that I needed.
So, as always, I asked the internet - and found a YouTube video from some dude who had a very similar problem to my own. He had managed to fix his drive by swapping the logic board from his fried hard disk with one from an old drive he had kicking about.
Unconvinced, I went hunting through all my old computer spares, and found an old Maxtor drive that had been sitting gathering dust. Same make as my crispy drive, but a different model. Still, the logic boards looked similar - despite the differing names printed on some of the chips. I thought it'd be worth a crack.
I carefully removed the board from the knackered disk (which still smelt a bit toasty) and screwed on the (hopefully fully functional) one from my old drive. I then fitted it back into its enclosure and prepared to plug it back in. Click. Whirr. Well, at least it was spinning up now. But would it mount? A few seconds of trepidation... and there it was - F: Backup. Success!
I decided to work quickly as I was certain there was no way my fortune would last long. I quickly scanned through all the files, and established exactly what was there. I picked out a few essentials that I wasn't sure I had elsewhere and copied them over to the main hard disk and out of harm's way. The more files I copied, the more the drive sounded unhealthy, making all sorts of deathly grinding noises and rattles. Clearly, it didn't like my Frankenstein approach to hard drive surgery. Eventually, it gave up entirely and refused to do anything else. But at least I had copied a good chunk of data back to my PC to peruse at my leisure.
And this, in turn, got me thinking. Those backups - made incrementally, every two or three months - represented little snapshots of my life. This website for example. It has been going, in one form or another, for over five years now. Every time I redesigned the site, there would be a new "index.html" file containing the latest idea I'd had, and overwriting the old one. But there, on that hard disk, were versions of the site long since gone from the realms of the internet. I'd kind of forgotten about them entirely. And the same with my backups of email messages. Sure, the version I have here and now contains everything I deem to be worth keeping, but the backups have all those messages that I've consigned to the great trash can in the ether.
Anyway, the upshot is that the drive actually contained nothing really important that I didn't have saved elsewhere - but I did manage to salvage some little bits of history.