Saturday, 16 April 2022
The Story of the Commodore Amiga in Pixels by Chris Wilkins and Roger M Kean - Book Review
Friday, 8 April 2022
How To Build An Aircraft Carrier by Chris Terrill - Book Review
Sometimes, I just shouldn't be left in charge of a gift card when perusing the shelves of Waterstones. That's how I ended up buying this tome from Chris Terrill. How to Build an Aircraft Carrier is not an actual how to guide (though you could do worse than pick up Airfix's re-release of HMS Victorious in 1/600 scale) but the tale of how HMS Queen Elizabeth went from shipyard to first operational cruise from the viewpoint of her first captain and crew.
Let me say that I really, really wanted to like this book. However, whilst there are some strong points in its favour, there are several that detract from what could have been an excellent look at both the Royal Navy's new flagship and the people who choose to serve within its ranks.
The good stuff first, and Terrill captures the experience of serving in the Royal Navy tremendously well, from both a professional perspective and the more relaxed occasions. There are some good stories told here about individual crew members, highlighting the changes in the service over the last couple of decades and how inclusive it tries to be. Call me cynical, but there is a recruiting pitch in here somewhere.
In all seriousness though, the core story is one that is worth telling and Terrill goes good work here. You get to know the individuals he focuses on well and they are at the heart of the story. That leads to the first problem I have with this book: the dialogue.
I get that this is aimed at the casual reader, and I completely understand that some dramatic licence is required when portraying events, but at times (though certainly not always), the dialogue the author relates sounds completely implausible coming from various speakers. It's not exactly condescending but there is a lot of explanation left to the dialogue that, for example, you know two pilots would never say to each other. Don't get me wrong, it's not that bad most of time time but on occasion, the false tone hits you like a hammer and really detracts from the flow and believability.
The same can be said for the comparisons the author makes. When describing something and saying it is the equivalent of powering Swindon, that's great if you know roughly how big Swindon is. I don't, although I was on better ground with Aberdeen. However, those comparisons become meaningless when the author doesn't get the technical details right, and this is where my main complaint lies.
There's not much in the way of huge clangers, but the multiple smaller errors add up. It begins with calling HMS Dragon a frigate, and then quoting tech specs twice about the F35, one figure being 200mph higher than the other. The statement that Jutland was a British victory lacks even a scintilla of nuance, and when the author states the carrier's radar can detect a tennis ball-sized object travelling at supersonic speeds at 2 miles, eyebrows are raised. BAe System's website states that ability at 25km. My favourite is the GPMG that fires "7.92x57 Mauser ammunition." This from an author who was embedded with Royal Marines in Afghanistan.
There is also the political angle, which has dated slightly/been taken over by events, but crucially is delivered with all of the subtlety of a Tom Clancy novel, i.e. none at all.
You might be thinking I am being a little harsh here. You might be thinking that, as this book is aimed at the general public rather than naval aficionados, the author should be cut some slack when it comes to the technical stuff. In my humble opinion, no. If you want to write a book about how the crew of the Royal Navy's largest surface warship managed to get from the dock to completing trials, you need to get the technical stuff right, because if that side is lacking, what does that say about the personal dimension?
It's sad because Terrill puts across the human story very well and that's what kept me going. However, the cack-handed dialogue and the factual inaccuracies spoil it to the point where I can't recommend it whole-heartedly. You will learn some stuff here, there is no denying that, but it's one of those books where it's also best to have your phone/tablet to hand in order to verify what the author is saying is actually true. A shame then, but such was the risk when being let loose with a gift card. It may have been better as a cheaper paperback purchase.
You can buy How to Build an Aircraft Carrier from the usual high street and online stores.
Saturday, 2 April 2022
Adventure by Jamie Lendino - Book Review
As promised some months ago, I bought myself another of Jamie Lendino's books. Adventure focuses on the Atari VCS/2600 and the halcyon early days of the home console story. And whilst that story invariably contains the details of the US-centric Great Videogames Crash, Lendino writes, as he did with Faster Than Light and Breakout, from his personal point of view as an owner of the hardware and many of the games.
An aside for UK readers: If you're a person of a certain vintage (i.e. my age), the Atari VCS/2600 was a machine that you knew people had but you never really wanted one yourself. And before you light the torches and sharpen the pitchforks, let me explain. By the mid to late 1980's, the UK videogames market was pretty much sown up by the 8-bit home micros. Consoles were a thing, but that was because they were the cheapest options in your Mam's Freeman's catalogue. Sure, you could get an Amstrad CPC 464 or a ZX Spectrum but they were triple figure sums (albeit available for a low weekly payment), but something like a 2600 seemed to hover around the £40-50 mark and that meant it had the twin negatives of being cheap and the games looked worse than the most basic of Spectrum fayre. This did you no favours when the subject came up with your school friends.
The thing is, this was a disservice to the 2600. The base hardware was closing in to being a decade old and, for a lot of cash strapped families at the time, even the low weekly payments from a catalogue couldn't disguise the fact that the "low cost" micros were out of many people's reach. But if you had a 2600, the lack of playground boasting aside, you still got to play some cracking games, even if you were using a machine that dare not speak its name. With that, back to the review.
Structurally, the book is divided in to nine chronological sections: Beginnings, Open Worlds, Invasion, ICBM's, Pitfall, Empire, Assault, Gravity and Endgame. For each section, you get an overview of what was happening with Atari and the games market in general, then a curated selection of games from that time where Mr Lendino focuses on the most noteworthy titles. And by that, I mean good and bad, though he does refrain from having too many stinkers, a good call considering the shovelware that hit the 2600 in its middle years.
Each game is given space to breathe and even if the 2600 was not your favourite system (or if you've never owned one at all), you will find Lendino's passion and enthusiasm contagious. Once I had finished the book, I fired up the Evercade to get a better idea on some of the titles mentioned in this book. And yes, whilst time has in no way been kind to them, either graphically or sonically, the gameplay shone through in titles such as the titular Adventure, Asteroids and Missile Command. I was left with a sense of wonder as to how developers managed to get such nuanced control schemes out of what was effectively a one button joystick, and a wry smile was raised when the author related the lottery of getting a good or bad title from the bargain bins in the years after the Crash, something that chimes in very well with buying budget titles for the CPC or Spectrum, and a point very nicely noted in Stuart Ashen's book. No matter what the system, or the country, that experience of the lucky dip of budget gaming seems to have been very similar.
There are screenshots, one per featured title, but no colour. Unlike his previous books, there isn't a companion piece from another publisher on my shelves at the moment, although the Atari 2600/7800 Compendium from Bitmap Books could be a very good contender. No doubt at some point, I'll have to get my hands on a copy. Where other images are used, these are clearly reproduced with no issues present.
The bibliography takes up nearly five pages and quite a few are contemporaneous to the period of the 2600's time of the market. There are many of these I wouldn't mind reading, so there are more titles for the ever growing wish list.
This is yet another enjoyable title from the author and one that should be in anyone's Atari or videogame history library. Is this book just for fans of the 2600? No, of course not. It's an important look at the state of gaming on one of gaming's great machines. No, it wasn't powerful, or at least seen as powerful once the 1980's came along and, like some many computer/games companies throughout the history of the genre, the upper management were clueless (a judgement made with the benefit of hindsight, but they totally mis-understood the creative nature of videogames), but without the 2600, the world of gaming would be a very different place.
At this point, I would like to say that Mr Lendino only has one other book out that is on my list, but that would be a lie. As of mid-March 2022, he has a new tome, Starflight, which looks at the heady days of DOS gaming from 1987 to 1994. That will be my next purchase, as I loved reading about the type of games that you could only get on the PC back in the day. I mean, I didn't have a PC. When a colour Amstrad 1512 cost two to three times what a CPC cost, there was no chance of that at all. But that's for another time.
You can buy Adventure from Amazon here, and follow the author on Twitter here.
Saturday, 26 March 2022
Once Upon Atari by Howard Scott Warshaw - Book Review
Friday, 18 March 2022
Bullocks, Grain, and Good Madeira by Joshua Provan - Book Review
Saturday, 12 March 2022
Florin's Haul of ZX Spectrum Games by Paul Davies - Book Review
Saturday, 5 March 2022
Was That Film Really That Bad??? - Star Trek III: The Search for Spock
The "difficult third album" is only a cliche because it happens to be true in many cases. Indeed, the same could be said of any art, and never more true of Star Trek III: The Search for Spock. Not only did this film have to meet heady expectations raised by the seminal Wrath of Kahn, but it also had to juggle the difficult task of reintegrating a fan favourite character in to the series. Over the years, it has become a commonly held belief that the odd number entries into the Star Trek series are crap whilst the even numbered ones are held in high esteem (or at least in higher esteem than the odd-numbered entries). In the case of TSFS, it was too early for such simple labelling, so it must be asked of Star Trek III, was that film really that bad???
The film opens with the Starship Enterprise returning to Earth after the dramatic events of the previous movie. Looking much worse for wear, the ship is due for decommissioning and the crew are held to silence following the political fallout of the Genesis Project. When it becomes clear that Bones is carrying the soul of Spock and must be reunited with his body on the Genesis planet, Kirk and company resolve to steal the Enterprise and save their friends.
![]() |
| I'm sure that'll buff out... |
The Klingons want the Genesis device as a weapon and attack the science vessel dispatched by the Federation (the USS Grissom), whilst taking Kirk's son and Lt Savik (who were on an away mission to the Genesis planet) prisoner. Once the Enterprise arrives, it all kicks off, the Enterprise is destroyed, Kirk's son is killed, but the crew get Bones and a reborn Spock back to Vulcan.
![]() |
| Ok, that will definitely NOT buff out. |
It's a pretty simple tale and one that is delivered well. With a slightly higher budget than WoK, the space bound effects are top notch but the decision to film all of the Genesis planet scenes in a studio (and the sets are quite impressive at times) means that the film at times comes across as a standard TV episode writ large and paradoxically a little cheap.
![]() |
| A Toast! To the set designers and construction gang! |
The usual cast members return and, for a change, they are given a bit more screen time. After the first two films, it's nice to see Koenig and Takei actually have something to do, though Nichelle Nicols is criminally underused - and that is a trend that continued into the fourth movie. The sole returnee from WoK was Merritt Butrick as Kirk's son, David Marcus. Kirstie Alley didn't come back so the role of Savik was recast with Robin Curtis picking up the reins. A touch of class is provided by Dame Judith Anderson as a Vulcan high priestess and it's always good to see Mark Lenard as Sarek. The star of the show is Christopher Lloyd, playing a pitch perfect foil to Shatner's Kirk as Kluge, the Klingon commander chasing after the Genesis device.
![]() |
| He's just dropped one and appreciates the ambience it provides. |
The Search for Spock was a financial success, making $87m off a $16m budget, but it took less than WoK ($97m against a budget of $12m) and critical reaction was less favourable. No, it wasn't as slow or po-faced as The Motion Picture, but neither was it as action packed and dramatic as WoK. TSFS sits somewhere in between these two films but the key thing to remember is that it expands on the world outside of the Enterprise as well as allowing some of the cast to breathe a bit more. There is a enough humour to raise the odd smile and all told, this is very much a more personal story, relying as it does on the core trio of Kirk, Spock and McCoy.
![]() |
| The space effects are really good though. |
Maybe that's not what general audiences wanted. Maybe they wanted more of the ship combat and scenery chewing that WoK delivered. Or maybe not. Consider the next film in the series, The Voyage Home which was essentially a film about whale-napping, was a huge success for the series ($133m against $21m), as well as finishing off the story arc which began in WoK.
![]() |
| That guy at the back "Hey, Spock, do you like Sci-Fi movies?" |
Is The Search for Spock really that bad? No. Thematically and stylistically, it fits in perfectly with the prior and later films. Yes, the studio work is obvious but hey, these weren't mega-budget films at the time. Compared to the likes of Indiana Jones and the Temple of Doom and Ghostbusters, TSFS had roughly half the budget and put bloody impressive SFX onscreen. Perhaps best binge watched with the second and fourth films, The Search for Spock delivers the story it needs to in a poignant and respectful manner to the characters. And after all, wasn't it the characters and the story that kept us enthralled with Star Trek in the first place?

















