54
votes
Why did "protected-mode MS-DOS" never happen?
16-bit protected mode DOS did sort of happen: Concurrent DOS 286 and FlexOS 286 were able to run some DOS applications in protected mode (this involved complex LOADALL shenanigans and revealed bugs in ...
37
votes
Accepted
How much slower was the 286 in protected mode?
Basically, anything that involves changing segments is slower, sometimes significantly so; this is unsurprising since descriptors have to be checked, privilege levels potentially changed etc. Other ...
34
votes
Accepted
Were Windows 3.x applications dependent upon 80286 instructions?
Windows 3.x wasn’t “stuck to the 80286 platform”: Windows 3.0 still supported real mode on 8086 processors. The requirement for a 286 at the platform level only came with Windows 3.1.
As far as ...
29
votes
Accepted
Did any software attempt to perform 8086 emulation on the 80286 using LOADALL, in the vein of the later virtual 8086 mode of the 80386?
I believe what you are describing was in fact done. Concurrent DOS for the 286 could multitask DOS programs in protected mode. See the Wikipedia article on Multiuser DOS as well as DOS VMs.
The ...
29
votes
Accepted
80286 can switch from real mode to protected mode - but why not back?
This was intentional so that the CPU would support secure operating systems. In a secure operating system with rigorous memory access protections you could not allow any software - user or kernel ...
25
votes
Accepted
How can a protected-mode Watcom C program access memory that a real-mode interrupt service returned in a segment:offset register pair?
In OpenWatcom, which was used in the example given in the question, the intr function performs transparent translation between segment values and protected-mode selectors, presumably using DPMI ...
25
votes
Accepted
Are .COM executable binaries real mode or protected mode?
DOS programs always start in real mode (or an emulation thereof), so it’s best to start disassembling them assuming that. When disassembling, you should assume real mode, with 16-bit data and 16-bit ...
19
votes
Why did "protected-mode MS-DOS" never happen?
And, marketing-wise, did everyone want multitasking and GUI so much that an idea of a single-tasked OS was no longer appealing by definition?
In a word, yes.
The 80386 came to market in 86/87, well ...
18
votes
Accepted
Example Windows 3.11 286 protected mode program - how long did Win 3.1 286 protected mode last?
The first version of Windows to use 286 protected mode was Windows 3.0, released in 1990. Support for 286-based systems was dropped in version 3.11 for Workgroups in 1993, but support for software ...
16
votes
The move to protected mode on x86
Where became protected mode the norm and real mode something for old people with fond memories?
I think the answer to that question is with the 80386. Protected mode on the 286 had some issues in ...
14
votes
Accepted
BIOS support for 286 Protected Mode
“Regular” BIOS only provides a function to switch to protected mode (interrupt 15h, service 89h), and can’t be called from protected mode in general.¹ BIOS services can use protected mode, for example ...
14
votes
Why did "protected-mode MS-DOS" never happen?
The programs that you already had and needed to run were not protected mode programs, they needed to be run in 16-bit real mode anyway.
DOS drivers used BIOS for I/O, which also was 16-bit real mode ...
13
votes
Did any software attempt to perform 8086 emulation on the 80286 using LOADALL, in the vein of the later virtual 8086 mode of the 80386?
As RETRAC writes, this was indeed done.
Companies other than Digital Research also considered similar approaches, but ultimately discarded them. One documented case is IBM with OS/2’s DOS support ...
12
votes
Accepted
How do you put a 286 in Protected Mode?
Actually this is a lot easier than I thought, after trying to link to another MSW note, I found it in the Intel Instruction Set: Machine Status Word (286+ only).
The machine status word seems to be a ...
10
votes
Were Windows 3.x applications dependent upon 80286 instructions?
While Win 3.x operating system stuck to the 80286 platform,
Not really as Windows was since 2.1 available in two versions:
Windows/286 and
Windows/386
It got only unified by name with Windows 3.0. ...
10
votes
How can a protected-mode Watcom C program access memory that a real-mode interrupt service returned in a segment:offset register pair?
I've accepted user3840170's answer as it solved my issue but I want to add a second answer that contains just the concepts that I lacked in order to solve my problem:
The far keyword is still ...
9
votes
Are .COM executable binaries real mode or protected mode?
com files are not segmented (they have just a single segment). They have a limitation that they cannot have more than 64K of code (filesize).
They always start in real mode but I do not think there is ...
8
votes
Why did "protected-mode MS-DOS" never happen?
There was at least one proposal for a 32-bit OS that would have been a drop-in replacement for MSDOS: Marc Perkel's NovOS, submitted to Novell in 1991. The intention was that existing MS-DOS programs ...
7
votes
Example Windows 3.11 286 protected mode program - how long did Win 3.1 286 protected mode last?
While Minix was always a niche operating system, it gained somewhat wide use in teaching and hobbyist circles. Especially as Linux required 386 processors, while Minix ran on the cheaper 286.
From ...
7
votes
Can you write to the GDT on Windows 95 from protected mode? Why, and how?
Due to being required to run in 4Mb of RAM, a number of security protections were compromised. As a result, those tables were indeed writable. The CIH virus took advantage of this, for example, by ...
7
votes
Why did "protected-mode MS-DOS" never happen?
There were several attempts to introduce an ABI like this, including VCPI (Virtual Control Program Interface) and DPMS (DOS Protected-Mode Services), but the one that came closest to being a standard ...
6
votes
The move to protected mode on x86
But where was this step really done? Where became protected mode the norm and real mode something for old people with fond memories?
My understanding is it was a gradual transition, spanning a decade....
6
votes
The move to protected mode on x86
A major weakness of the 80286 was the fact that most programs were limited to having two general-purpose segment registers loaded at a time. This was adequate if one wanted to copy a range of data ...
6
votes
Why did "protected-mode MS-DOS" never happen?
In a nutshell: because at that time everybody wanted GUI and multitasking.
In the other answers to this question, clever people have listed plenty of technical reasons why it would have been very ...
6
votes
Accepted
Why does the ‘Get Next Selector Increment Value’ DPMI call exist?
I don’t have any insider knowledge on this topic, so this is purely speculation.
I suspect the call exists because there was potential variation in similar mechanisms available at the time, which ...
5
votes
Were Windows 3.x applications dependent upon 80286 instructions?
I could be mistaken—and I would love to see some examples!—but I believe that it was rare for 16-bit Windows programs to require an 80286 (although some might need an 80386). For example, Version 1.0 ...
4
votes
Why did "protected-mode MS-DOS" never happen?
There was multitasking DOS called Wendin DOS constructed with their Wendin Operating System Toolkit (OST.)
The toolkit internally appeared to me to be inspired by VMS.
To get around the non-rentrant ...
3
votes
The move to protected mode on x86
Early versions of OS/2 and SCO Xenix (Unix like system for PC) supported 286. Sometime after the 386 was released, Microsoft switched to Windows NT while IBM continued with later versions of OS/2.
...
2
votes
Why did "protected-mode MS-DOS" never happen?
I'd think it was pretty obvious at the time that
the real-mode limitations of both BIOS and MS-DOS
Real-mode limitations are not of BIOS or MS-DOS.
Real-mode uses a 16bit addressing + segmentation,
...
2
votes
Did any software attempt to perform 8086 emulation on the 80286 using LOADALL, in the vein of the later virtual 8086 mode of the 80386?
I don't think the engineers at Intel really understood what made real-mode 8086 segmentation so useful: it allowed memory to be allocated in 16-byte chunks, and allowed any group of up to 4096 such ...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
protected-mode × 1480286 × 7
real-mode × 6
ms-dos × 5
x86 × 4
programming × 3
bios × 2
virtual-memory × 2
operating-system × 1
intel × 1
compilers × 1
windows-3.x × 1
performance × 1
design-choices × 1
windows-95 × 1
80386 × 1
executables × 1