MaW’s Blog

Wednesday, 10th January 2007

It died…

Filed under: Hardware — MaW @ 19:53

My graphics card has died.

Well, not entirely, but various issues with 3D rendering led me to contact both the manufacturer and the supplier. The supplier eventually got back to me with an RMA, so I posted it to them for replacement.

When I got back from the Post Office, there was an email from the manufacturer, saying could I perhaps try this BIOS upgrade for the card? Well, the answer is really no, because:

1) I’ve not got the card anymore
2) The BIOS update requires me to make a DOS boot disc. I don’t have a floppy drive, or DOS

Grrrr.

In other news, my sofa is much nicer to lounge about on now that it has a nice soft throw covering its sub-standard upholstery.

Tuesday, 26th April 2005

Of Windows XP, SATA Hard Drives and LEGO Star Wars

Filed under: Games, Hardware — MaW @ 8:31

So what have I been doing during my latest absence from blogging? Well, as might not be surprising to most of you, I’ve been playing City of Heroes. Finally got Nettle to level 36, got picked up by a very good random group (apart from the defender’s tendency to try and snipe things and get killed, which is totally not necessary when there are other snipers on the team) and did the second respec trial. Dead easy really - must get round to doing the first one some time!

At the weekend I installed my new hard drive. It’s a 200GB SATA drive (Seagate and very quiet) exactly the same as my existing 200GB SATA drive. It replaces two IDE drives (noisy), one of which was starting to get unreliable. All is well of course until one gets around to installing Windows XP Home on it (Linux was already on the existing SATA drive; Windows was on the dodgy 40GB IDE which is now headed for oblivion). In theory of course, one should be able to load the SATA drivers at boot time, because the XP installer doesn’t have SATA drivers in it (this is the SP2 version, couldn’t they have bundled a few?). So then comes the first big shock: Windows XP is incapable of loading drivers from a CD at boot time. After I stopped swearing about this, I found that my motherboard comes with a couple of floppies specifically so that you can install Windows XP on SATA drives using its on-board SATA controller. The trouble is, I have no floppy drive in my computer.

A few minutes with a screwdriver and mum and dad’s PC corrected that.

Unfortunately, loading drivers from both disks didn’t help Windows see the drives. Ho hum. Check the motherboard manual just in case it says something. Why so it does, here’s a clue - there are only drivers for the SATA controller which is linked to the RAID chips, not the normal one which the disks were plugged into. How very odd. Plug the disks into the other one, Windows sees them, installs onto the new one just fine.

The trouble is, Linux doesn’t like the RAID controller and I never did put any effort into getting it to boot off it. So now I need to get Windows liking the normal SATA controller enough so that I can swap both disks back to it. As it turned out, that was pretty easy, because the motherboard driver CD has those drivers on it. Tip for Microsoft: when Longhorn comes out, I know you’ll have put SATA drivers in the install kernel by then, but could you please allow extra drivers to be read from arbitrary locations in an ISO9660 filesystem? Thanks.

Then I had to get the Linux bootloader (GNU Grub) installed on the new disk so that Linux could be booted again. Stick in AMD64 Gentoo 2004.2 LiveCD, boot off it (non-framebuffer kernel, for some reason the framebuffer on the CD doesn’t work for me). It comes up with both disks visible, so I mount / and /boot and chroot into the installed system, run grub, some panic with the config file and disk designations, forgot the root= line, haven’t got the pretty pictures woring yet, but it does boot and work fine.

So that’s all over and done with. Except that my music is mysteriously missing - will have to stick the 120GB IDE drive back in at some point and copy it over again.

Anyway, last night I got my hands on LEGO Star Wars, which is to be perfectly frank an extremely silly game. Short in story terms - it only took me a few hours to play through the entirety of Episode I - but lots of fun. It’s not often a game has me laughing out loud. Seeing little LEGO men fighting with lightsabers is just too good. It also looks beautiful. They recommend nVidia cards as they use Shader Model 3.0 and nVidia’s fancy shadow technology, and I’m sure it looks excellent on those, but it’s jaw-dropping enough on my Radeon 9800 Pro. Since I’m intending to get an nVidia card next time, I should get to see it in even more glory soon (the shadows are a bit lax, I must admit).

So it won’t take me long to finish Episode III (not too much of a spoiler for the movie actually, as there’s hardly any explanation of what’s going on beyond a brief bit of text at the start of the level, this is probably why it was allowed to be released before the movie comes out), so what then? Free play mode of course! In keeping with the general silliness of the entire game, you can go back and play any level you have completed with any character you’ve unlocked, in order to find all the secrets, get more money, and buy more silly accessories. Which include moustaches for your LEGO characters. Since it’s impossible to find half this stuff using the characters you’re given in story mode (I’ve already run into a few places I need people who can jump higher - why Jar Jar Binks can jump higher than a Jedi I do not know, but I suppose they had to give him something to do) this should prove interesting. Or at least highly amusing.

Definitely the best Star Wars game I’ve heard of since Jedi Academy.

Sunday, 6th March 2005

The Powerbook Lives!

Filed under: Hardware — MaW @ 20:04

Well, thanks to Andi for lending me the appropriately-sized and -shaped screwdriver (I had the right size but it was not the right shape) to replace the hard drive in my Powerbook. It all seems to be running fine and dandy now — and it’s got 20GB more space in it. I shall now mollycoddle it excessively so that it lasts long enough for me to be able to afford whatever the next-generation Powerbook turns out to be, whenever it might be announced.

In other news, I’m feeling a little angsty and on edge tonight. I haven’t figured out why yet.

Monday, 14th February 2005

My Powerbook is ill

Filed under: Hardware — MaW @ 9:21

It has been a sad weekend. My Powerbook’s hard drive is ailing, spawning bad blocks and bits of lost filesystem all over the place. Thankfully I’ve got most of the data from it, but it seems that it’s been doing this for a while and I hadn’t noticed. Why hadn’t I noticed? I put the effects of the I/O errors down to various other things which I shouldn’t have. It was only when my iTunes library started getting corrupted and it gave me an error message which indicated the actual problem that I realised what was going on. Booting from the OS X install CD, Disk Utility is unable to repair the filesystem and suggests that I try backing up and reformatting it to isolate the bad blocks.

So I currently have four options:

1. Send it to Apple to have the hard drive replaced, probably costing an obscene amount of money
2. Buy a new hard drive and attempt to replace it myself, probably ending up with a few screws left over (the previous Powerbook models had easy to replace drives, the AlBooks don’t)
3. Reformat and reinstall the drive and hope that it’s capable of keeping the corruption confined to its current extents
4. Buy a new Powerbook

Of course, option 4 doesn’t really leave me a way to sell the current Powerbook, which is otherwise fine. I’m currently trying option 3, because it doesn’t require any money spending on it. Option 2 is quite realistic but very scary. I’m tempted to take this as a sign from on high (or somewhere, possibly from inside my head) that I should buy a new Powerbook, but I’d like to pass on one that’s in reasonable working order if at all possible.

We shall see how things go. The procedure for dismantling the thing is rather involved and involves lots of little screws of different sizes, so I’m not particularly hot on doing it myself. It’s a nervous time here at my desk at the moment.

Sunday, 3rd October 2004

Computer Upgrades

Filed under: Hardware — MaW @ 10:46

Money was burning a hole in my bank account - specifically, the money which I won’t be spending on LASIK. So I succumbed to the itch and got some computer upgrades… after a Saturday of intense installation effort, I now have:

  • MSI Neo Platinum K8T motherboard (SATA, RAID, socket 754)
  • AMD Athlon 64 3200+ (socket 754 - would have got socket 939, but the price premium is way too high. Also didn’t want to pay £60 extra for the 3400+, didn’t seem worth it to me)
  • 1GB PC3200 (yes I know, that’s actually a downgrade from the 1.5GB on my old mobo, but easy enough to add another 1GB stick when I feel like it)
  • 200GB Seagate Barracuda SATA drive
  • LG dual layer DVD writer (supports just about every writeable DVD format out there, plus CDs and it reads them too!)

This replaces the obvious bits of my old hardware, except for the hard drives, I still have my two IDE drives. Gradually I’ll migrate my entire Linux setup onto the SATA disk and then reinstall Windows so that I can ditch the 40GB IDE drive. If the SATA seems to go well, I may ditch the 120GB IDE drive as well, and get another 200GB SATA. It’s certainly very quiet…

Had some stress installing Gentoo Linux, I eventually got my old Linux system to boot happily (after some SATA misconfiguration problems, largely centred around an argument of Linux vs the RAID controller), added in the driver for the onboard Ethernet so Linux is now up and running and happy, but I wanted an AMD64 compiled system as well, so that’s what’s been installed on the SATA drive. Being Gentoo it’ll take me a while to compile everything, but there’s no hurry as I have a fully-working system available for when I need it.

Excuse me, it’s now time to play games. I wouldn’t really have thought it, but they’re much improved over the XP2100 even with the same graphics card. I guess there was more bottleneck in the CPU and memory bandwidth than I had previously thought.

Powered by WordPress