HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
roelandjansen
pcmos386v501
Assembly2017–2024
roelandjansen / pcmos386v501

pcmos386v501

PC-MOS/386 v5.01 and up, including cdrom driver sources.

7Distinct people
8Mentions
0Explicit recommenders
444GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

PC-MOS/386 v5.01 and up, including cdrom driver sources.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:01:10 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year8 dated mentions

Observed mentions: 2017-10-22 11:41:49 UTC to 2024-12-18 18:47:14 UTC.

01232017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC303
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC321
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

1 sources
The way the industry developed is this: First, in the early to mid 1980s, cheap PCs were all 8088/8086 machines (we called the XT class hardware). That was the baseline even when you could buy faster because it was so expensive. Then, from the mid-1980s, 80286 PCs came along (called AT-class kit). DOS couldn't really do anything much more on a 286 than it could on an 8086, so 286s were just used as faster XT-class boxes. There were 3 OSes that could use the 286: Digital Research's Concurrent DOS, SCO Xenix, and IBM/MS OS/2 1.x. Xenix was a hit. The others not so much. Then came the 386DX. Via UMBs and improved DOS memory management, 386s could do way more in plain old DOS. There were memory managers like QEMM386 and 386Max. (Now FOSS: https://github.com/sudleyplace/386MAX ) For power users they could multitask. There was a brief flowering
Read the rest
of multitasking DOS extensions and replacements: Concurrent DOS 386, DESQview, DESQview/X, PC-MOS 386, TSX-32, and others. Most aimed at multiuser stuff because 386DX kit was expensive. (PC-MOS is FOSS now. https://github.com/roelandjansen/pcmos386v501 ) This drove the market towards the 386. It could do more, even just for DOS and DOS users. I made a good living optimising the memory management of DOS PCs. Once it was established, the much cheaper 386SX came along and made 386 PCs cheap. The tech and the software and the skills were already there. But OS/2 1.x couldn't do any of it. It could barely run DOS at all. If you were a DOS user OS/2 gave you nothing worth having. NT was a hit by aiming at the PCs of the near future. That's what OS/2 should have been targeted at as well. Then gradually, incrementally, Windows 3 took over because it worked on XTs and ATs but on 386s it gave you DOS multitasking and copy-and-paste between DOS apps. It gave you the good stuff you got from DESQview. AND you got new apps. OS/2 1.x was gradual developing. It got a GUI after 1 version. It got a decent GUI next. Then it got smaller and faster. NT was incremental too. 3.1 worked but was huge. 3.5 got VFAT and was smaller and faster with better networking. 3.51 got smaller and faster and stabler and started ditching the OS/2 legacy stuff. The point being, OS/2 1.0 should have gone up against DESQview and Concurrent DOS as a DOS multitasker for rich power users, then OS/2 1.1 against Windows 2, then OS/2 1.3 would have taken the place of Windows 3.
In A quick look at OS/2's builtin virtualization

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.