It’s been a few months without an update on my quest to find the source code to Concurrent DOS.
I haven’t forgotten about it, and I haven’t abandoned it either, but annoyingly in my position a lot of my work boils down to “search until you find an email address, send email, and wait”.
And waiting I have, and I’ve hit a few dead ends.
Update on REAL/32
I had agreed to buy a hard drive with an installation of REAL/32, which may even have source code on it from the engineer-turned-kitchen-remodeler in the United Kingdom.
I was really hoping that that would be the conclusion to this search, but after our agreement he became more and more sporadic responding to emails. He would either not respond at all, or respond saying he’ll get it to me soon.
Then after another follow-up, I got this message:
Hello Thomas
Sorry for being quiet.
My offices were flooded a few weeks ago. I am still recovering from the disaster and I am not sure if I will be able to produce any Real/32 product again.
Damnit.
I feel bad for the guy, though I have to admit that the thought crossed my mind that if he had sent the hard drive when he told me he would, we at least might have been able to save REAL/32. Oh well.
Then a little later today, I got this email:
Hello Thomas
Whilst having to sort out my disaster of an office and going through my separate storage unit, I have found a Concurrent CPM 3.1 operating system manual. Very good condition.
Are you interested in it?
I agreed, so we shall see what comes of that. If it actually gets sent, I’ll scan a copy and put it on the Internet Archive.
Concurrent DOS Manual
I found a copy of the manual for the Concurrent Controls Inc. distribution of Concurrent DOS on eBay. It wasn’t terribly pricey, so I picked it up and scanned it.
It’s on the Internet Archive if you would like to read it.
Concurrent Controls Inc.
In my last post, I mentioned that I had messaged the founder of Concurrent Controls.
I actually got a response on LinkedIn, but it was just “hi!“. I then switched to email and got this:
I bothered you on LinkedIn, which you replied to (thank you!) and I’m a little afraid I might fall through the cracks, because LinkedIn is the worst website ever made and I wouldn’t blame you for not checking that very frequently.
If you have any insight as to the current owners of any Concurrent/Multiuser DOS source code, I would be very appreciative!
For that matter, any light that you can shine on the the history of Concurrent Controls would actually be very cool as well; I’ve been trying to find as much information about Concurrent DOS as possible so that its history can be preserved (I think Concurrent DOS is one of the most under-appreciated things to come out of the 80s).
To this I got a response:
Haha. I was a cofounder and CEO of Concurrent Controls so I could talk for hours about it. But no time at present, maybe when things slow down. And appreciate that you appreciate Concurrent Dos, our CCI version spread quickly - unfortunately as many illegal copies as legal, through many vertical app/process control developers.
Hey! More of a response. I replied:
Thank you for replying (especially so quickly!)
Yeah, I’ve been down a Digital Research rabbit hole for quite awhile, and while a lot of their products were pretty neat, I have been infinitely impressed with Concurrent DOS and how ahead of its time it feels.
It is interesting that you mention software piracy. I have been in contact with the guy who maintains REAL/32 (who has pivoted to remodeling kitchens now, which I was not expecting!), and he said that he too had a lot of issues with people making illegal copies of the software. I guess this was something that a lot of people had to deal with in the 90’s.
No problem if you cannot speak in detail right now; if you ever get a few free minutes, I would love to chat about Concurrent Controls and Concurrent DOS sometime!
Thanks again for reaching back, and I hope you have a great rest of your day!
Then a week or so later, I also sent this:
Hi!
I hope you’re doing well!
I was wondering if it was possible to schedule some time to discuss Concurrent DOS and Concurrent Controls in the near-ish future. I know you’re busy, so there’s no rush at all with this!
To which I received this reply:
Thomas, give me two weeks and ping me again. I hope to be a little less busy than right now, and will try and make some time.
After that, I stopped getting responses to my messages.
I understand that they’re busy, and I’m not entitled to any kind of exclusive interview, but I am still a little disappointed.
Maybe something else will materialize.
I think that catches us up for now.
I have not given up, I am convinced that some kind of source code is available somewhere. I just need to find the right people to email.