I’m still trying to get my FM Towns in a state to play Wing Commander. It might help if I hadn’t spent so much time playing Truxton 2 on it but I have made some progress this weekend. The main problem I’m having is the lack of information and what there is often conflicting. As such, I thought I’d share what knowledge I do gain starting today with the memory upgrade.
My FM Towns II (like most of the models) comes with 2Mb of RAM. This was quite a lot for the time but that single speed CD-ROM drive just isn’t up to loading data on the fly (as shown in the fairly painful first attempt with Wing Commander a couple of weeks back). I gather some machines support EDO RAM, provided you set the appropriate jumper on the motherboard but I opted for what I hoped was the safe option of buying some 8Mb 70ns FPM, Non-Parity SIMMS from Ebay. Early FM Towns machines are limited to 8Mb SIMM’s as a maximum. I expect that’s not the case with my FM Towns II but 10Mb sounds like plenty for the games I have in mind.
The SIMM’s themselves are cheaply available, more so if you happen to be in the USA. I understand that other FM Towns models vary with many having several slots for SIMM’s but my particular UR model just has the one slot, conveniently located at the side of the case under a plastic flap:-
You can just see the Intex 486SX chip nestling behind the RAM slot. It seems pretty strange these days for a PC CPU to have no heatsink whatsoever but it clearly gets by without. I slotted my RAM in here and of course when I switched the PC on, it wasn’t detected. After much Googling I stumbled on a post at http://nfggames.com/forum2/index.php?topic=6150.0
The upshot is that pins 67-70 on the SIMM chip are used to report the size and speed of the SIMM in question. The IBM compatible chips use a completely different standard to those on the FM Towns so a bit of finagling is required. Fortunately, this is fairly easy to achieve with a soldering iron even for me.
The table above (stolen from the forum post) shows the settings required with O being the pins that should be connected. Most (but not all) SIMM’s will have somewhere on them pairs of solder points for this purpose.
The jumpers in question are at the top right of the chip I’ve used here. R1-R4 represent pins 67-70 in order. R3 was already bridged with a little connector. From the chart above, I also needed to connect R2 and R4. I just filled the gaps with a bit of solder and I’m pleased to report that my FM towns now detected the memory correctly on boot.
I should mention that the first chip I tried still refused to work as it didn’t pass the memory tests at startup. It may well just have been a faulty chip but I’ve heard that some SIMM’s can prove to be incompatible. The one that did work is an HP D2975A which is available on Ebay for under $3.
As far as improving Wing Commander goes, the difference is marked. During cutscenes, the extra memory appears to largely used as a cache, so the first time a given character or scene is shown it is still slow to load but once you have played a mission or two the CD isn’t even accessed most of the time. Gameplay itself is all pre-loaded before the mission and the game is so much more playable now, albeit with a really, really long loading time for that first mission. It’s still quicker than playing Wing Commander 3 on a 486 was.
I’m going to be needing that hard disk if I’m ever going to play Wing Commander 2 as it requires installation to run at all. I have the hard disk but am still waiting on the SCSI cable to try it out. One hitch I know is coming is that the BIOS battery on this thing is long dead and it appears I will have to completely dismantle the machine to get to it. The hard disk will need setting up every time I switch the machine on if I don’t fix this but I might just live with it depending on how much grief it causes. I definitely want to get the hard disk up and running first..
The main thing that is keeping me from a Wing Commander playthrough is that I really don’t much fancy using the keyboard to play the game. The solution to that problem is being delivered next week so providing it works I hope to have this fully up and running before too much longer.