Ontario's Computer: The Burroughs ICON
jasoneckert.github.io
jasoneckert.github.io
It's sad they ordered them all destroyed. While they were obsolete the day they were made it would be great for there to be a working installation of them to show off how advanced Ontario was once upon a time.
Or walking in for computer class and they would all be hung on the boot screen
One problem with saying they had written it was that clients would report bugs which they would forward to Quantum (much later renamed to QNX Software Systems) but nothing would happen. When I produced the decompiled sources it took me a single afternoon to fix the pending bugs and implement the feature requests.
The first step was to disassemble the binaries. As an OEM Softec had access to the .obj files so they could link in new drivers if needed, and those included the symbol tables giving me at least the function names. The C compiler didn't do any optimizations, so compiling a few sample programs was enough for me to then read through the assembler while typing in C and adding comments as I went along.
The version I worked on was called 1.1e even though versions 1.2 and 2.0 (which was just 1.2 plus networking) were available.
The overall idea for QNX (originally QUNIX) was solid, but early implementations were not so nice. In 1.1e it was possible to see that a lot had been fixed from earlier versions, but there still were a lot of problems. The File Manager was responsible for decoding executable files (the Task Manager should have done that instead), for example, and most of the functionality that should have been in the shell were hardwired into the Task Manager instead. This was greatly improved in version 1.2 which I looked at though I didn't decompile.
Even in version 1.1e, running QNX on a 256KB PC with floppies only was way nicer than other Unixes on much beefier machines. Each version was much better than the previous ones so by the 1990s the QNX people saw was a different experience than what was on those old machines.
The hardware itself had a number of features that predated similar hardware being widely available in the PC world. Every workstation had built in arcnet and booted from the network. They used an 80186 CPU, so slightly higher performance than an IBM PC. Every system came with audio hardware capable of playing back samples (I have no idea what sample rate or how many bits per sample it had, but it was grungy enough to probably be 8 bits at 20kHz). And they had glorious trackballs built into the keyboards that us kids would often swipe furiously. It was certainly an interesting system at the time, but I had already been exposed to 80386 PCs running MS-DOS with NetWare over ethernet in the summer which was far more performant.
At the end of my grade school year I ended up breaking the network horribly and knocked the ICONs offline until the system was reinstalled. By this time I had root acess, and mistakenly typed a 1 instead of a 4 and destroyed the root filesystem on the server. Ooops! That was quite the lesson. At least I didn't get in trouble (unlike some of my earlier antics in the school year that stemmed from complete boredom and an utter lack of interest in going outside for recess in -25C to -30C weather). Ah, those were quite the years.
- a horse race game where people raced horses by answering math questions
- a fishing game where your boat went across the top of the water and you had to catch fish and lobster without snagging your line
- a typing game that did not check if you typed the correct words or all the words, and would just calculate "number of words entered / time you took", so if you started a typing test and hit a letter and then escape, it would give you a ridiculous WPM score
It's wild to think that this entire system was only for such a small segment of the population, that we'd have our own computer line. What a weird time, the 1980s
I remember a game where you played the role of a colonial farmer in Canada and you got to decide what to plant every season. It always stuck with me because there was a bug that didn't allow you to skip one section.
This is roughly my memory. I had forgotten about these entirely and now I'm racking my brain trying to remember how we used them. I do remember the trackballs, a big computer lab, and only using them on special occasions... I think it must have been around 1989 but I may be off by a year or two
We didn’t have any programming classes, just a room full of them for typing class, with the server in the closet.
F F F space H H H space. Ugh.
You could wander the menus of the word processor and actually dial the modem. We got endless joy from calling Pizza Pizza and hearing an annoyed voice coming from the closet.
We shared one dot matrix paper and my friend and I just split the odd and even pages and print twice because the teacher would let us listen to our walk/discman when we were finished and I really wanted to listen to The Bends.
So I guess I did learn a bit about programming :).
The trackball had the advantage over a mouse where you could keep spinning it with force and it felt like endless fun.
Our teachers were pretty novice, and as admins ... um, not really. All the teachers signed in as the superuser (I guess it was root?) to do anything, and they'd often just walk away, leaving us a superuser shell. Fun times. A friend in that class would create superuser accounts, but they find them and delete them. If I remember correctly, there wasn't a RTC backup, so turning the system off meant you had to set the date; and they would only power on the lab when there were students there. So they had this clever script that would run on superuser login that would set the time. So I wrote a little addition that would create a SUID-like shell in some obscure part of the system, so we could have the superuser privs whenever we wanted. A first hack! :) QNX was fun, and it was a good baseline for learning Unix later in University.
My first computer. I figured out the password on my own so I could play more. It was password!
What I remember was the trackball, the multi-player games ... and if you used the equivalent of "NET SEND" to send a message to another terminal to another you could crash the network. Maybe we had an older/non-patched version of the system.
I never heard of one of these things. I would have been intrigued.