the first step in a brave new world

After being in the internet backwater for what felt like eons, I’ve finally been set up with some pretty decent internet – mainly a proper NBN connection. Whilst the plan that I’ve started on isn’t the beefiest, and is essentially the top tier of what ADSL2 can deliver – the fact is that there was no way that ADSL2 was capable of actually hitting those speeds.

The other big issue was uploads, mainly due to the way that ADSL handles uploads. I’ll have to do a write up on that at some point, but this is all essentially fluff.

I’ve got enough upload speed to be able to stream properly.

You can find me over at

I’m going to try to play a lot of older games, not just old DOS games, but a lot of older windows titles that always get overlooked. I know that I’m planning on getting some mates together an play some Unreal Tournament ’99 very soon.

learning curves

Unique Hardware = Unique Headaches.

Earlier this week, I was banging on about how bloody rad it was to have all my nostalgia bones tickled by all those awesome graphics, digitized sound and FM music coming from the faithful little beige box. I also mentioned that there was some petty issues that were no big deal.

The petty annoyances are just that: petty, and having that little bit of extra work make the times where I get everything working like magic so much sweeter.

I’d like to point out that I’ve been eating my words for the past two days.

Curiousity Is Cruel Mistress

For the week or two after picking up the machine, I was having a blast. I spent most of my time trying to figure out what games I actually wanted to play, more than getting into any system or OS drudgery. I managed to get a few old favourites working, and even started writing up a review of One Must Fall as the next article. It was all going so well.

So what on earth happened?

I ran out of space on the hard drive. That’s it, the singular proverbial cause of two days of frustration. When I picked up the machine, I was told that there was a 2GB hard drive installed in the machine. Yet, when I checked available space in both Windows and via the dir command in DOS, the total space amounted to 504MB. This is due to the BIOS not recognising any drive over the 504MB limit as a main drive. There’s a couple of workarounds that I came across, but the easiest way I found was through using what’s called a Dynamic Drive Overlay, or DDO.

A DDO is a classic example of bootstrapping, where a small program is used to enhance the capabilities of the initial hardware. In this case, a DDO will override the motherboard’s BIOS’s hard drive controller, allowing the system to access areas of the drive past the 504MB limit. There’s a few options when it comes to DDO’s that work in this situation, but a lot of them are proprietary, and only work with certain brands of hard disk. I eventually settled on using a DDO called EZ-Drive, as it looked to have the best compatibility with the drive I was using. Normally, I’d go into detail about how to get all this running, but Phil over at has a wonderful install guide right here. Go check out his site and his YouTube channel, some interesting stuff over there.

The Big Mistake

All this EZ-Drive and DDO stuff is neat, but in order to access the full drive, I was going to need to format the C: drive. I’ve got a full set of DOS6.22 disks, Windows 3.11 disks, and I made copies of all the drivers that were stored on the hard drive. I knew the models of the sound card, as well as the CD drive. I made sure I had all the software I needed to get everything running, and it would be a fresh install. Everything was set, and I formatted the drive and got EZ-Drive up and running. So far so awesome. Here’s where I screwed up, and it comes as a warning to anyone else working on unfamiliar hardware. I’m going to put this in bold so you know I’ve got my serious face on.

Remember to back up your driver configuration as well as the drivers.

This came back to bite me in the arse something shocking when it came time to install the sound card and CD-ROM drivers.

And Now, A History Lesson

Before I get into what the exact problem was here, a quick look back to the introduction of the CD-ROM drive. Just like any new technology, the CD-ROM was an amazing leap forward, allowing for massive amounts of data to be stored on a single disc, as compared to other removable media like the then ubiquitous floppy disk. So you can get an idea, my first computer had a 420MB hard drive. The smallest CD format can hold 650MB. You can fit more on a CD than most hard drives of the era could hold. Granted, CD burners of the time were expensive and rather unreliable, so most people couldn’t use them to write to, but it’s really damn impressive.

However, when the CD drive was introduced, there was no standard when it came to connecting a drive to the system. Eventually most drives used the IDE standard, but before that was adopted, there was a lot of different ways of connecting drives, and a lot of manufacturers used proprietary ISA controller cards with their own connectors and cables. A similar situation can be seen at the dawn of 3D acceleration, where different chipset manufacturers had vastly different APIs until 3DFX came along with the Glide API and gave a glimpse into the future. A future that 3DFX wasn’t going to see, but others took the idea of a common API for maximum compatibility and ran with it.

Transitional Hardware

Here’s where the root of all my issues came from. The CD drive in my 486 is a Sony CDU33A-01. It’s a 2 speed CD-ROM drive, and is one of Sony’s first CD drives. This specific model was designed to work with either one of their proprietary ISA cards, or with a compatible Sound Blaster card – The Sound Blaster 16 CT2260 MCD. There’s other compatible cards, but this exact Sound Blaster card is installed in my machine, and acts as a controller card for the CDU33A-01. It took a while, but I managed to track down drivers that would work with the card, as well as drivers for the CD drive. Yet even after running the sound card setup and the CD drive setup, the system still refused to recognise the CD drive.

After trawling through every readme file, and attempting to find documentation on some of the most obscure corners of the internet, it turns out the solution was a classic PEBKAC error.

PEBKAC: Problem Exists Between Keyboard And Chair

On the setup disk for the sound card, there was two setup files: SETUP.EXE and SETUPSB.EXE. I think you can guess what the SB stands for on the last file. That’s right, Sound Blaster. Old computers suffer no fools, and a lot of the time it’s due to something tiny like this that brings everything down.

For those interested, here’s the line in the CONFIG.SYS file that works for this drive/sound card configuration:


and for the AUTOEXEC.BAT:


\DEV\ is the default install address, and can be changed when you install the drivers.


So that’s the story of the first major hurdle I’ve faced. Now I can get back to writing that One Must Fall article.



Say hello to the class, everyone.

Welcome to foureightsix, the rambling journal of one man’s blind fumbling through the world of vintage computing, as well as other miscellany I come across in my adventures.

So expect a lot of detailed accounts of my idiocy as I fumble my way through re-learning how to run and maintain old computers, and hopefully we’ll all be able to learn from my experiences. I’ll also be taking a look at the games that I remember so fondly from my youth, and whether or not they live up to the hazy memories I have.

It’s shaping up to be a whole lot of fun, so I hope you’ll join me on this carnival ride, even if we have to stop every now and then and figure out why it’s inexplicably crashed.