The AMD boards I use have dual processors. They are out of an old Linux Networx Evolocity I picked up years ago for my Minix Supercomputer project and MOS runs fine on that in Real mode. Being a DOS compatible OS, I am not sure if you could even wedge a second processor in there and have it function in SMP mode. It would be kind of cool though…

Stay safe. Scary stuff in your part of the world these days.

Jim

When I first had Xenix running on Qemu I had so many small businesses and municipalities reaching out to me on how to rescue their systems. Naturally that fell off a cliff, as I hope that those tens of users were rescued and have since moved on, either migrating their data, or keeping it running in a VM forever.

But never mistake it, if you have any kind of analytics loaded on a blog, you’ll find those lost souls from time to time looking up stuff. Back then I had wanted to do some kind of long term legacy support thing, but as always the trick is finding customers. Maybe I should have perused it harder, but I let that ‘full time job’ thing get in the way. I’m just glad I wrote the stuff down, otherwise I’d have forgotten most everything.

I’m having what seems like PSU issues with that dual P3 board I recently got just before one of the big protests broke out. The electronic district here has been beset by constant protests & overwhelming police response so I haven’t been able to try to source a different and ‘larger’ PSU and or other legacy components. While I do have a single proc board, I’ve been hesitant on erasing it just yet to load that Mach386 thing I have going on. I’m really dying to know if it’ll boot on read hardware.

I do run it in my lab on some old 32bit AMD boards, P4 desktops, and a laptop in my lab with an old Wyse terminal to have a second session. Some of the systems have issues with the Memory manager when it goes into protected mode and some don’t. Other than that, it just runs.

Most of my development and testing is done in DosBox and VirtualBox on Ubuntu. I have even set up a VirtualBox VM using 4 virtual COM ports and attached them to 4 minicom sessions on an Ubuntu VM for fun and to see how it all works. The security is interesting and the way it was implemented contributed to the disappearing files when the 2012 bug activated.

Just recently I had someone reach out to me as his business is still running MOS and I patched his kernel for him. I was surprised to find someone still using it in a business environment!

TheGrue

Awesome!

Are you running this native anywhere? I know that clock is ticking down for the end of the bios. Which is going to suck.

PC-MOS/386 v5.02 has been released. No more date bug, no more 60 minute timebomb, added CD-ROM driver and more!

Also v5 documentation has been uploaded to Roeland’s repo as well.

TheGrue

TheGrue

> want to see if I can get it on paper first

You need copyright assignment in writing. A verbal promise is worthless under U.S . copyright law, which applies since TSL was a Georgia company.

Do you have it? I don’t see it on github.

Hi Pete,
I’ve been searching for manuals etc for PC-MOS now that it’s been open sourced, but they don’t seem to be available anywhere (see https://github.com/roelandjansen/pcmos386v501/issues/27) I wonder if you still have your PC-MOS stuff and might consider helping out there?

Thanks for reading, Andrew

awesome!!! I see a tonne of assembly, and Borland stuff.. cool! Can’t wait to dive! Thanks for your hard work!

the initial commits are here.

https://github.com/roelandjansen/pcmos386v501