Apologies to all those I’ve just affected, but due to the massive amounts of spam comments currently being submitted I’ve just beefed up our sign-up procedure as well as removing a tonne of users who seem to have submitted nothing (or nothing and spam).
If I accidentally deleted your account, or you’re legitimate and trying to sign up then I am really, truely sorry. Get in contact and we’ll sort it out
Well, Christmas time is nearly here, and as much as I hate all the adverts on telly, its a great time of year to get snowed in, crack out the old computer games and put your feet up on the computer for warmth. With this in mind, I’ve written a little guide for getting C&C The first Decade working on a modern Windows 7 system.
Command and Conquer; Tiberian Dawn came out in 1995 and was followed shortly after in 1996 with Red Alert. Hidden in the lounge at my friend Ian’s house with his mum upstairs asleep, his chronically underpowered 233mhz pentium computer wurring away I was absolutely amazed by the entire C&C experience. The installer was immensive and fell modern and damned cool, the video’s looked beautiful and like nothing else I’d experienced and the music track was fantastic. Many hours were lost.
So now, 15 years after the first game was released lets have a go at getting it all running in time for Christmas. After a couple of days of failure (and the need to multiplay with my brother) I gave up getting it running in WINE under Linux and cracked on with a Windows 7 install.
In 2006 Westwood packaged the first 8 years of gaming into one 8gb installer. Some of the games still work “out of the box”, others (like Generals; ironically the latest games) are a bit of a pig to get going; but they all will work!
Not that I’m advocating piracy at all, but the recent Ubisoft DRM Fails and the not so recent events that saw people who had bought a legitimate version of Spore downloading and installing cracked versions just to get it to work do make me think….
I’ve been using the g1 for a few months now on a daily basis, and for the most part I’ve been quite happy with the screen and have never had to change the brightness settings.
I was a little upset when trying to give directions earlier in bright sunlight, as I was squinting quite a lot.
My upset was quickly replaced by amazement as I realied ILd been running for 3 months with the screen brightness turned to 0%; change it to 30% and it was bright and readable again. Fantastic!
Truth be told, as screens go, its almost too bright, I keep finding myself reading in bed and wishing I could make the screen dimmer, but it looks like -15% screen brightness (would not only suck all of the light out of the world, but also) is beyound easy reach.
-as a side note, its quite hard typing on the g1 when you’ve but off the end of your finger chopping onions
A week or so ago, I started playing about with the Raq in the hopes of being able to quickly get it doing something (and preferably hidden in a cupboard and not on the desk next to the bed).
I quickly got ahead of myself, and in the process of trying to update it managed to completely screw it to the point where all it would do is display Kernel Panic on the LCD Screen. Turns out that by updating the kernel on the eeprom, it can no longer boot its OS.
If I understand correctly, then the boot sequence for the Raq3 goes like this (when booting from the hard disk).
There are some interesting things to note about this. For a start there is no bootloader (eg lilo or grub) as you would need on most hardware as it is built into the eeprom. The eeprom on a Raq3 is limited to 1024k making it quite hard to fit a modern kernel on it, which leads to some interesting issues.
The Raq3′s built in OS uses a customised version of RedHat and boots a linux-2.2 (iirc) kernel which is completely obsolete and has been for quite some time (we are currently at 2.6.29-r1, see this for some idea of context), which then passes off to a linux-2.2 stage 2 kernel on the hard drive.
The latest possible kernel for the eeprom is a linux-2.4.24 kernel, which is still obsolete in terms of current features, but has the power to let us do something clever. There is a sourceforge project you can get this latest cobalt-rom (2.10.3) release (containing the afformentioned 2.4 kernel) but bear in mind the project was last touched in 2003.
When I updated the eeprom to the 2.4 kernel, its quite obvious that it would freak out when trying to load the 2.2 kernel (stage 2). -Or is it the 2.2 freaking out at being loaded by a 2.4?
It was at this point it got shelved for a couple of weeks whilst I flailed about the great intertubes trying to find a fix.