Full Width [alt+shift+f] Shortcuts [alt+shift+k]
Sign Up [alt+shift+s] Log In [alt+shift+l]
1

A boxed set of DR DOS 6!

from Rubenerd [alt+shift+b] in life

I feel like I righted a wrong in some small way recently. It also gives me an excuse to write another of my shaggy dog posts about old computers, which I’ll never pass up the opportunity to do. Behold, our boxed copy of Digital Research DOS 6.0 from 1992: The first OS I ever used was MS-DOS 5.x on the family 486, upgraded shortly after to MS-DOS 6.2 [sic], then Windows 95. DOS was “what came with computers” to me at the time, so the idea there were alternatives didn’t even cross my mind. MS-DOS’s origins lay with QDOS, itself a broad clone of Digital Research’s CP/M operating system. CP/M-86 was compiled and offered for the original PC, but IBM famously went with Microsoft instead. The circumstances surrounding this decision remain… contentious. Either way, I’ve had a soft spot for Gary Kildall since I first saw him on those archived episodes of the Computer Chronicles. People like exploring an alternative universe where IBM went with CP/M over DOS, and Gary had become the billionaire tyrant instead of Gates. We can only speculate, but Gary always struck me as more of a self aware, Woz-type character than Bill. I’ve mentioned how Digital Research’s GEM desktop was a big part of the reason why I got into the Atari ST, but I haven’t talked much about DR DOS, the OS Digital Research released to compete with Microsoft and IBM. I never used it as a kid, but I wondered what Gary and his team had been able to deliver. Last year I acquired disk images for every major release, in part for a blog post series about DOS that I never ended up publishing. Version 6.0 quickly supplanted IBM PC DOS 7 as my preferred DOS; everything from the installer to the included utilities are vastly superior, and it even came with ViewMAX, a file manager based on GEM/3. Awesomesause! Pair this with Turbo Pascal, Commander Keen, Sim City 2000, The Games: Winter Challenge, the Brief editor, and the DOS port of Lemmings, and I’ve got all the bases covered! DR DOS 6 was released in 1992,...
1st Sep 2026

Stay updated

Get a weekly newsletter with the top 5 articles worth reading every week.

More from Rubenerd

CommSec says goodbye to Mr “Middle”

I can’t remember if I told the story before, but in the Before Times™ I opened a trading account with CommSec, the public brokerage associated with Australia’s largest bank. Or I tried to, at least. After registering, I got an email welcoming me to CommSec, in which they referred to me by my full name. Except, it had a problem: Welcome, Ruben Middle Schade. Just in case it’s unclear, my middle name is not “middle”! I thought it might have been a mail merge issue, but I logged in and confirmed my name was listed as “Middle” everywhere. Likewise, every piece of correspondence in print and email referred to me as such. How did this happen? I had a few theories: I absent-mindedly wrote my name as “middle” on the signup form, which slipped through. A system internal to CommSec transcribed my name incorrectly. I have family and friends who work in finance, and it’s surprising how many manual processes are still involved. Cocaine’s a hell of a drug. Number (1) seemed more likely at first, so I was ready to blame myself. Except, there are systems that are supposed to catch such mistakes. Signing up to a new financial account in Australia requires 100 points of ID. These documents clearly, and unambiguously, refer to you by name. If I did write my name wrong, how did CommSec’s systems not flag this obvious discrepancy between that mistake and my real name, and immediately fail to activate the account? To be crystal clear, “Middle” wasn’t listed as my middle name on any of my provided documentation, yet their identity verification erroneously matched them, and proceeded to create the account. That’s… more than a bit worrying. I’d blame people using “AI” for this mistake in 2026, but they didn’t even have that as an excuse back then. So what about option (2)? How likely was it that I failed verification, but that my account was created in their system anyway? Or was it a transcription error? Again, I find both of these difficult to understand. As for option (3), I wouldn’t dare cast stereotypes about people who work in a specific industry. This was merely a joke, like listing someone’s middle name as “Middle”, then verifying it against documents where the person’s name isn’t “Middle”. That’d be funny. Fixing my name What proceeded felt like a comedy of errors. I enquired to CommSec asking if I could change my middle name to… my middle name. I expected this to be easy, because it was such an obvious mistake. That was on me. Their support team rejected my initial request, telling me I’d need to request a “change of name form”. I objected, because I wasn’t “changing” my name, I was correcting a mistake with my real name. But fine, I downloaded the form, completed it, and returned it with a cover letter explaining the bizarre situation. CommSec’s system denied the request, citing insufficient evidence for my name change. I wasn’t changing my name, I was fixing my name! GAH! I’ll admit at that point I lost interest, and went with another broker. This turned out to be a fateful decision, because I ended up paying much lower fees, and I got access to some foreign markets. The capital gains from these investments were instrumental in Clara and I buying our first home. So, thanks CommSec! I think? Closure Every month or so since, I’d receive a newsletter from CommSec advising me of market conditions, and new features I couldn’t use. This was quite funny. But it wasn’t to last: Dear Ruben, We are writing to let you know that your account(s) will be closed, as they have no holdings or balances and have not been used to transact for an extended period of time. These accounts may have been opened directly with CommSec, CommBank, or with one of the brokers CommSec has acquired. Please note that your account may be suspended prior to closure. As part of this account closure process and in accordance with ASX Settlement Operating Rule 7.1.11(a) and CommSec’s Terms and Conditions, we are also formally notifying you of the termination of your CHESS sponsorship agreement. Goodbye, Mr Middle, we hardly knew ye. By Ruben Schade in Sydney, 2026-11-02.

a week ago • 1 votes
Rubenerd Show 434: The toastrack episode

Podcast: Play in new window | Download 37:37 – A feedback episode, reading comments about the show from Adam, Alistair, and Abdullah. Discussing my favourite personal shows that are still going (Into Your Head, The Overnightscape Underground), task management (Getting Things Done™, the spark to get something started), 1980s British retrocomputers (Spectrums, Amstrads, Orics, and Acorns), coffee (my own snobbery, instant coffee, how supermarkets sell it), and what constitutes a mathematics coprocessor! Recorded late September 2026. Recorded in Sydney, Australia. Licence for this track: Creative Commons Attribution 3.0. Attribution: Ruben Schade. Released October 2026 on The Overnightscape Underground, an Internet talk radio channel focusing on a freeform monologue style, with diverse and fascinating hosts; this one notwithstanding. Hosted graciously by the Internet Archive. Subscribe with iTunes, Pocket Casts, Overcast or add this feed to your podcast client. By Ruben Schade in Sydney, 2026-10-01.

1st Oct 2026 • 1 votes
The myth of Snow Leopard

Snow Leopard was a version of Mac OS X released in 2010. It was billed by Apple as having “0 new features”, with a focus on refining the system, improving efficiency, and fixing bugs. Those of us using Macs at the time welcomed the news after living with updates that seemingly broke as many things as they introduced with each release. This idea is so powerful—and so longed for—that it’s escaped containment among the Apple crowd. I’ve seen everything from Linux distro to phone updates referred to as Snow Leopard releases, when their vendors cite stability and bug fixes over new features. Likewise, people plead with their vendors for a Snow Leopard release when they feel quality has slipped. The reality at the time was a bit different. As I wrote at the time: This could be the first time I’ve ever downgraded an Apple OS. As we speak I’m downgrading the Snow Leopard partition on my trusty old Core Duo 2006 MacBook Pro back to Leopard (and while I’m at it, I’m finally getting around to upgrading the FreeBSD partition to 8.0!). I kept waiting for updates to fix the severe stability problems in the Finder, my FireWire 800 ExpressCard and my iMovie HD plugins, but I’ve decided to give up for now. This was putting it mildly. When I tried it again a few months later, I still had so many problems that I downgraded again, then leapfrogged it for Lion when it was released in 2011. Jeff Johnson has a great post discussing all the problems Snow Leopard introduced and had to have patched. It was a mess. Still, whether Snow Leopard really was this bastion of stability and polish, the myth surrounding its development and stated purpose obviously resonates today. People invoke its memory because they’re broadly craving stability and quality of life improvements, something almost everyone has wilfully discarded as they chase the next rung of enshittification. Apple’s marketing team hit on something so popular that it has staying power sixteen years later. By Ruben Schade in Sydney, 2026-08-02.

1st Aug 2026 • 1 votes
Uniform boolean definitions in DB schemas are good!

I worked briefly in process control when I was younger, and saw Things.™ One of those Things™ was a wall of LEDs to indicate statuses of various valves and sensors across the entire plant. It was old school, but it worked. It also made you feel like you were on a 1960s-era sci-fi set. What does this have to do with databases? That’s an extremely excellent, and dare I say handsome, question. While we’re on the topic of things I used to do, I used to work against a large database that had a schema with a specific quirk that used to drive me up the wall. Take this contrived example of a table for an account: username | active | paid ---------------+--------+------ nagato_yuki | true | true takarada_rikka | true | false And another for some basic infrastructure: hostname | running | error ------------------+---------+------- retro.rubenerd.au | true | false www.sasara.moe | true | true Do you spot the subtle difference between the two? Why is the first table well designed, and the second one horrible? The first table has uniform positive attributes. Having an active account is good, and being paid is good. This means one can tell at a glance whether an account is in good standing or not. You can also do trivial boolean algebra to derive a status. The second table has a mix of positive and negative attributes. Having a running state of true is good, but having an error state of true is bad. This means you can’t as easily tell at a glance the status of an instance. You can’t also as easily derive an overall status. The value of consistent booleans was something that was immediately obvious when looking at that status wall. It mostly had white lights. When one of these changed colour, you knew there was something actionable. If that status wall instead was designed with some lights being positive, and some being negative, it would be almost (but perhaps not entirely) useless. ☕︎ ☕︎ ☕︎ Why am I thinking about this today? I’ll admit it’s for an incredibly embarrassing reason: I had a dream about databases last night. I know, some people have fun dreams involving flight, reliving something they enjoyed, or exploring a new side of themselves. I dreamed I was back at uni with my DB professor who insisted that all booleans should have positive assertions. Anyway, I was shy at the time when I went to that class in the real world, and said nothing. But what I wanted to say was that uniformity is more important. Most of the time there’s an unambiguous, convenient term to describe something positive, but I also acknowledge there are some circumstances where forcing this naming can get clumsy, such as having a schema full of not_$foo attributes. It’s not a data science to me, but I’m reminded of the sixth rule from The Economist Style Guide: Break any of these rules sooner than say anything outright barbarous. The same applies for software variables, but that would be a whole other post, can of worms, and kettle of fish. By Ruben Schade in Sydney, 2026-07-01.

1st Jul 2026 • 1 votes

More in life

AI and women at work: 5 positives, 8 negatives

Laetitia@Work #106

17 hours ago • 1 votes
Optimal virulence and the Android lockdown

When you get a cold, the virus hijacks your cells and uses them to make copies of itself, destroying the cells in the process. The virus does not care about you. And yet, if you get a cold, your body doesn’t dissolve into a pile of virus-enriched goo as a result of all your cells disregarding survival to focus on virus manufacturing. Why? Well, you have an immune system. But also, if that did happen, other people would say, “Oh no, Alice has dissolved into a pile of virus-enriched goo; we should stay away lest we also become goo piles.” Better to just hijack some of your cells, so you can walk around and spread the virus to other people. Thus, the theory of optimal virulence says that a more laid-back cold virus will be more successful in the long run, which is why the cold viruses that thrive today are the non-goo-pile-converting kind. Anyway. Most people reading this have paid Apple $400-$1600 for a phone on which you can’t do anything without Apple’s permission and monitoring. That was a strange decision, but on Android phones you can run whatever you want. For example, I noticed a couple of months ago that all RSS apps were terrible, so I spent 15 long minutes having AI make me a non-terrible one. I copied the file to my phone, installed it, and entered RSS nirvana, no registration, no app store, no nothing. It seems ludicrous that I wouldn’t be able to do that. And yet, Google plans to change things. Soon, you won’t be able to run any app on an Android phone unless the person who made it bends the knee by paying a fee, giving Google their government ID, listing all apps they’ve ever made, etc. There will be an “escape hatch” for users to install other apps, but it involves secret menus and scary warnings and a 24-hour waiting period. Google says they’re doing this for security reasons, to prevent people from installing malware that does things like steal financial information. Three things that any credible analysis of this situation must acknowledge The security issue is real, and this change will help. Lots of people are in fact getting tricked into installing malware on their phones, and common sense says that this will accelerate with AI. Common sense also says that during that 24-hour waiting period, some of those people might wonder if it’s really normal for OfficialMicrosoftSupportProfessional021 to contact them on WhatsApp to send totally-safe-virus-scanner.apk. It would be convenient for lockdown opponents if the security issue was fake, but it isn’t. For 95% of people reading this, these restrictions would not be a big deal. You click a few buttons, wait 24 hours once, and then you have the same freedom you have now. That’s still far better than Apple phones where there is no process at all. Oddly, it’s also better than Apple computers, where installing programs from non-verified developers has all sorts of friction that can never be removed. Most people I know use Apple computers anyway and just tolerate the indignity. If Google cared about freedom or privacy, they could have achieved their security goals without as much harm to freedom or privacy. For example, instead instead of making themselves the sole arbiter, they could have allowed for multiple certifying entities, and could have allowed users to add others (perhaps after a 24-hour waiting period). Arguably, that would be more secure: That way, grandma could install my RSS app without leaving herself open to random malware. Or, Google could have used private on-device malware scanning, or lots of other things. Google didn’t do that because they don’t care about freedom and privacy and because they like money.1 I think that’s a fair summary. This change addresses a real issue, but it does so in a self-serving way that needlessly destroys freedom. Even so, it only destroys a bit of freedom. This change, by itself, isn’t really a huge deal. Reading between the lines, I think the real concern is what this might portend. Having made this change, maybe Google will gradually add further restrictions, slowly boiling the frog and moving ever-closer to an Apple-style dictatorship. But will they? Maybe! Still, this whole situation seems under-theorized. There are good reasons to think that a full lockdown would not be in Google’s interest. And if you care about digital freedom, you could argue that a full lockdown would be a good thing. Some other analogies Switching insurance sucks, so some insurers offer a low initial rate and then gradually raise it over time. But they don’t want to raise it too much. Maybe they can charge you $50 more per year than a competitor, because it’s not worth your time to switch to save $50. But if they tried to charge you $5000 more per year, you’d be gone. Or try this: Say it’s 1750 AD and you’re the King of France. You care nothing about your subjects and only want to extract the maximum possible loot for yourself, no offense Louis XV. How high should you set taxes? High, because you want loot. But not too high, because you don’t want your subjects to revolt and kill you. But still pretty high, because revolting is hard, and your subject know that even if they succeed, they might just end up with another ruler that’s just as rapacious as you. Or: Say you put a frog in a pot of water and slowly heat it up. What do you think actually happens? Back to phones Why are there no Linux phones? OK, technically there are Linux phones. There are various Linux phone operating systems (PureOS, postmarketOS, Mobian, Manjaro Mobile, Fedora Mobility, openSUSE Mobile) as well as sorta-Linux-sorta-Android operating systems (Ubtuntu touch, Droidian, FuriOS, Sailfish OS) and manufacturers who support them (Purism, Pine, Fairphone, Shift, FuriLabs, {J,V}olla). While I love and support these (♡), the general consensus is that they don’t currently offer an experience that’s remotely comparable to stock Android or iOS, especially for the price. (Even more technically, Android is itself a kind of Linux, but you know what I mean.) Obviously, the laws of physics do not forbid Linux phones from being just as good and cheap as an Android phone. They currently aren’t because: Making cheap phones requires huge economies of scale. Making a good operating system requires a huge amount of work. For a phone to be useful it needs good apps, which requires a huge amount of work. Linux phones don’t have those economies of scale because few people buy them. So, there isn’t enough money to pay people to perfect the operating systems, and most companies don’t bother making apps, and so few people buy those phones. Meanwhile, there are also various Android-except-de-Googled phone operating systems (LineageOS, GrapheneOS, /e/OS, CalyxOS), and the consensus is that these do come reasonably close to the experience of stock Android or iOS. Personally, I used Android for a long time while trying to disable as much of Google’s apps and telemetry as I could. A while ago, I got fed up with this and switched to Graphene, one of the most popular Android-except-de-Googled variants. I don’t enjoy tech support bullshit, so I expected some pain, but I was willing to tolerate it for freedom/privacy/whatever. In practice, I found that everything was easy and worked flawlessly and there was no pain at all. Using Graphene made me realize that I had forgotten what it feels like to be “respected” by technology. So, on a personal level, I recommend that you use Graphene. But this whole situation is full of weird tensions. For one thing, the Graphene project depends on Google for the base of their operating system, and only really survives because of Google’s tolerance. And, at the moment, the only way to use Graphene is to… buy a phone made by Google. And while I recommend you use Graphene, what I’d prefer you do is switch to a true Linux phone. That would mean that you pay a lot of money for a poor phone experience. But it would help grow the Linux phone ecosystem. If enough people did that, then Linux phones might become become good enough that selfish people like me would switch, further growing the Linux phone ecosystem, et cetera. That seems unlikely, because digital freedom weirdos face a collective action problem: Linux phones are bad and people are selfish, so we keep buying Android phones and Linux phones stay bad. There are two ways to solve that collective action problem. Either some entity could invest a ton of money to make Linux phones good, or some entity could do something to make Android worse. The status quo is good for Google You may already see the argument I’m making here. Currently Android is just open enough that weirdos like me can run a variant that gives us most of what we want. But doing that is annoying enough that 99.9% of people don’t. This gives Google almost all the benefits of full control, while also sucking up all the oxygen and preventing a real alternative from emerging. (Apple, incidentally, is laughing. They get to enjoy a full dictatorship while Google does all the hard work.) Suppose that in six months, Google decides to escalate the lockdown and completely removes the ability to run independent apps. What then? In the short-run, not much. Tech freedom weirdos would howl, normies wouldn’t notice, and the world would keep turning. But let’s look at some numbers. A rough estimate is that 3-5 million people currently use private de-Googled Android variants like Lineage or Graphene. That’s a crisp 0.1% of the global Android market. Meanwhile, it’s thought that 300-500 million people install Android apps outside the Google store. (That’s excluding China and things like the Samsung and Epic Games Stores.) The biggest reasons are (i) piracy, (ii) modified YouTube/Spotify/WhatsApp clients, (iii) region-locked games, (iv) forbidden gambling or crypto apps, (v) local sharing to save on mobile data, and (vi; least common) open-source app repositories like F-Droid. In an escalated lockdown, some of this might still be allowed, e.g. local sharing. And many people would simply accept the new restrictions. But I expect that a substantial number would suddenly become interested in de-Googled Android variants that don’t enforce the lockdown. That would be dangerous for Google: If a significant fraction of those 300-500 million people switched, there’s a risk of a vicious/virtuous cycle, where people tell their friends, manufacturers start to cater to those variants, and so on. If that happened, what would Google do? Might they clamp down on those Android variants, too? Again, maybe! Technically, Android is open-source, but if Google really wanted to kill Lineage or Graphene, there are about 200 different ways they could do that. So say they did. What would the people currently using those variants do? Again, many would simply submit. That’s good for Google. Others would decide that if they must have an overlord, they’d prefer Apple. That’s not good for Google, but probably not a huge problem given the numbers. But others would decide to look elsewhere, likely to true Linux phones. Currently, it’s estimated that less than 100 thousand people daily-drive true Linux phones, 30-50 times less than the number of people who use de-Googled Android variants. I’m too lazy and selfish to use a Linux phone now, but Google will take my RSS app from my cold dead hands, so in this scenario, I’d likely switch. If a fraction of people do that—or even get a second Linux phone—it would still represent a huge infusion of money and energy into the Linux phone ecosystem. If this pushed Linux phones from “bad” to “sort of OK”, that could kick off a growth cycle. Eventually, there would be a risk that Europe—eager to decouple from an unreliable US—might embrace them by mandating that government employees use them, or passing a law that popular apps must provide a web-app version that works on Linux phones, or whatever. Would that actually happen? I don’t know, but neither does Google. My point is that the downside risk of losing their phone duopoly seems vastly larger than the upside, so why risk it? The smart move is to crush alternative app stores and fight malicious apps while making the bare minimum concessions to keep the freedom and privacy people onside. That’s exactly what what Google appears to be doing. Of course, they might go for a full lockdown anyway. Corporations do dumb things all the time. But I really don’t see how it would be in their self-interest, and I’m not sure it would be a bad thing if they did. Dynomight: could google achieve the security aims of the android lockdown without so much harm to freedom or privacy Google Gemini 4: Yes. Security experts, privacy advocates, and open-source developers widely agree that Google’s primary security objectives—protecting users from malware, financial fraud, spyware, and social engineering—can be achieved through architectural containment, transparent auditing, and informed consent rather than centralized gatekeeping and surveillance. […] The reason Google chooses centralized lockdown over user-controlled security is largely economic and strategic, not technical: Ecosystem Lock-in: Tying security APIs (like Play Integrity) to Google Play Services makes it nearly impossible for competitors or open-source forks to build a viable alternative Android ecosystem that supports banking and media apps. Advertising Revenue: Features that dramatically improve both security and privacy—like a native network firewall, revocable internet permissions, or frictionless support for system-wide ad blockers—directly threaten Google’s primary revenue stream. Liability & Support Reduction: Treating all users as untrusted and removing root/power-user capabilities reduces the surface area of user error, even if it removes the user’s ownership of their own hardware. ↩

23 hours ago • 1 votes
Confident communication lessons from an unexpected teacher

How my 2.5 year-old is training me to speak more confidently, or else.

yesterday • 1 votes
America In ‘Still Functioning Democracy’ Shock

Notes on the 2026 Midterms

2 days ago • 1 votes
The Music Innovator Who Lived in a Friend's Basement

But anticipated the rise of techno, disco, rap, and fusion before they even had names

5 days ago • 2 votes
📚 BoredReading

You seem to be enjoying this.

Join free to unlock everything.

Create free account

Already have an account? Sign in