Archives
- November 2025
- October 2025
- September 2025
- August 2025
- July 2025
- June 2025
- May 2025
- April 2025
- March 2025
- February 2025
- January 2025
- December 2024
- November 2024
- October 2024
- September 2024
- August 2024
- July 2024
- June 2024
- May 2024
- April 2024
- March 2024
- February 2024
- January 2024
- October 2023
- September 2023
- August 2023
- July 2023
- June 2023
- May 2023
- April 2023
- March 2023
- January 2023
- December 2022
- November 2022
- October 2022
- September 2022
- July 2022
- June 2022
- May 2022
- April 2022
- March 2022
- February 2022
- January 2022
- December 2021
- November 2021
- October 2021
- September 2021
- August 2021
- July 2021
- June 2021
- May 2021
- April 2021
- March 2021
- February 2021
- January 2021
- December 2020
- November 2020
- October 2020
- September 2020
- August 2020
- July 2020
- June 2020
- May 2020
- April 2020
- March 2020
- February 2020
- January 2020
- December 2019
- November 2019
- October 2019
- September 2019
- August 2019
- July 2019
- June 2019
- May 2019
- April 2019
- March 2019
- February 2019
- January 2019
- December 2018
- November 2018
- October 2018
- August 2018
- July 2018
- June 2018
- May 2018
- April 2018
- March 2018
- February 2018
- January 2018
- December 2017
- November 2017
- October 2017
- August 2017
- July 2017
- June 2017
- May 2017
- April 2017
- March 2017
- February 2017
- January 2017
- December 2016
- November 2016
- October 2016
- September 2016
- August 2016
- July 2016
- June 2016
- May 2016
- April 2016
- March 2016
- February 2016
- January 2016
- December 2015
- November 2015
- October 2015
- September 2015
- August 2015
- July 2015
- June 2015
- May 2015
- April 2015
- March 2015
- February 2015
- January 2015
- December 2014
- November 2014
- October 2014
- September 2014
- August 2014
- July 2014
- June 2014
- May 2014
- April 2014
- March 2014
- February 2014
- January 2014
- December 2013
- November 2013
- October 2013
- September 2013
- August 2013
- July 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- January 2011
- November 2010
- October 2010
- August 2010
- July 2010
PC-MOS/386 Source Code
I missed this when it was initially announced. The source code for PC-MOS/386 version 5.01 is now available on github under the GPLv3 license. It requires the user to supply Borland C++ 3.1 in order to build, but there are binaries checked in as well, including a bootable floppy image.
PC-MOS is a multi-tasking/multi-user DOS clone. It was one of the first commercial products which used the 386’s virtual-8086 mode when it was released in early 1987 (but not the first, that was almost certainly CEMM in 1986).
It is worth noting that PC-MOS also supported 286 systems. It required custom hardware and also used the well-undocumented LOADALL instruction (see MOXMEM.INC).
The source code is unfortunately not organized in a very clear fashion; there are for example three separate and not quite identical copies of the PC-MOS kernel.
There is an interesting reference to “Bimini 2-SX” aka IBM 486SLC, which apparently had a bug affecting PC-MOS/386: “When executing a CALL or JMP instruction with a negative
displacement within a 32-bit code segment and an operand prefix override is used (i.e., to limit the target address to 16 bits), the resulting target address is computed incorrectly.” (see _386.ASM in the mos5src directory for additional detail).
8 Responses to PC-MOS/386 Source Code
Hi is this something for you?
Citrix win view för networks v2.3
Microsoft powerpoint för windows 1990-91
Lotus notes server för OS/2
Lotus notes Arbets station för windows v3.0c
Lotus Notes windows v3.0c
Lotus notes server OS/2 v3.0c
Lotus notes OS/2 v3.0
Microsoft Axel för windows v5.0
Lotus notes data disk
Lotus Notes Release 3 client för windows
Lotus notes release 3 mediaclips
Lotus notes release 3 windows program international edition
AU system Avitel windows svensk v2.11
Lotus notes sample application
Lotus notes Release 3 OS/2 program
Lotus notes v3.0c
Microsoft windows v3.1 HP swedish localisation
Central point pc tools för windows
Lotus freelance graphicks v2.01 för win
Lotus inprove 2.0 för windows
Tulop computers win TM 3.1
Discserv v3.11x
Lotus organizer evaluation copy orginal disk
Netware NML Library update disk Ink LIBUP3.exe
Central point PC tools sv dos shell&file viewers
Olicom Token ring driver disk
Wordperfect presentation v2.0
Lotus organizer 1.0
Lotus Datalens för Lotus notes för windows v3.0
Corel SCSI network manager netware modules v1.0
Central point backup för windows v7.2
Microsoft Exel programdiskett
IBM OS/" Warp v3.0
Recognita plus international v1.1w release
Adobe typ manager win ver
Neat. I’m looking forward to see how that extra piece of hardware (apparently a “CHARGE” card) worked. There is also mention of an “ALL CARD (FOR 8088)”, which could potentially be even more interesting, given that the 8088 of course had no MMU at all to speak of:
I386 equ FALSE ; IF INTEL 80386 CPU
GIZMO equ FALSE ; IF GIZMO IS USED
ALLCARD equ TRUE ; IF ALL CARD (FOR 8088) IS USED
CHARGE equ FALSE ; IF ALL’S CHARGE CARD IS USED
But maybe that comment is misleading. I also wonder why it says 8088 instead of 8086. Was this actually something specific to the 8088?
Guess we’ll find out.
That’s probably more something for archive.org. Mostly in Swedish I assume?
What I read somewhere is that the PC/MOS custom 286 hardware included some kind of interposer between the CPU and motherboard. So if they had something similar for 8086 class hardware, the interposer would have to be different for 8088 and 8086. And all the early PCs used 8088 CPUs. IBM at least didn’t offer 8086-based systems until 1987 I believe, years after 286s. So if there was something, it may well have only supported 8088 and not 8086 CPUs.
@Cassiel: I’d be extremely interested in WinView for Networks. Can I contact you using email with regards to it?
The Eagle Turbo XL from 1984* was an XT clone with an 8086 processor; it may have been the first PC compatible with 8086. By that time, the All Card was being phased out. Moving the video addresses to increase contiguous memory required patching applications but All Computers only managed to make a small number of patches and worse still did not work at all if the system had EGA. Being able to turn part of the 640k into expanded memory wasn’t much benefit.
The All Charge Card had similar problems but at least extended memory could be turned into expanded. Worked wonderfully with the serial port text only Multilink** which made the AT Gizmo such a nice idea. Been a long time but I thought AT Gizmo was a licensed version of Charge Card. Ran into a bit of a problem once 386 prices started to decline; no one would pay 300ドル to give a 286 system a limited portion of 386 capabilities.
* Well, 1983’s Eagle had a copyright issue with its original ROMs. Not sure if any were sold before IBM legal noticed.
** Multilink*** was the precursor to PC-MOS that ran on top of some versions of MS-DOS.
*** Multilink had combined with the Tall Tree JRAM memory card to run background processes on an XT speedily making it one of the few programs that used (or even understood) the Tall Tree memory standard. Proved the concept of large DOS sessions which set the stage for newer more general purpose solutions.
If I recall correctly AT&T / Olivetti had some extra hardware on the PC 6300+ with a 286 that would intercept signals on the bus and give you some of the features that would later exist in the 386’s v8086 mode. I own one of the machines, I’ve meant to look into it more but never got around to it. The idea was that System V could run in 286 protected mode and the hardware would handle switching modes and virtualizing certain machine states, etc for DOS. I’d imagine its similar in concept.
The AT&T 6300. and +. Wikipedia has some good information on that: the 6300 ran Venix/86 and the 6300+ ran DOS and Sys V III under Locus’s Dos Merge, Simultask 1.0 was based on Locus Merge, Simultask 2.0 was based on VP/IX, and then the product became Univel UnixWare 1.0 Personal Edition came with DOS Merge 3.0 and Novell’s DR DOS.
https://en.wikipedia.org/wiki/Olivetti_M24
“The 6300 Plus was designed with special hardware on the bus that would suppress and capture bus cycles from the DOS program if they were directed toward addresses not assigned for direct access by the DOS virtual machine.”
https://en.wikipedia.org/wiki/Merge_(software) Special hardware confirmed and for what purpose.
This site uses Akismet to reduce spam. Learn how your comment data is processed.