Re: Making Computers Secure

Article View: alt.folklore.computers

Article #619960

Back to alt.folklore.computers Previous Next

#619960

From: Quadibloc
Date: Sat, 03 Feb 2018 14:06

22 lines
2947 bytes

On Saturday, February 3, 2018 at 3:52:02 AM UTC-7, Bob Eager wrote:
> On Sat, 03 Feb 2018 03:41:11 +0000, Melzzzzz wrote:

> > Correct. 286 had protected mode, but almost no OS used it...

> The only systems I can think of were some nice UNIX-like systems, 
> including IBM's PC-IX. It didn't help that protected mode was 
> incompatible address-wise with real mode.

Basically, an operating system that used 286 protected mode would have to 
*reboot* before it could run real mode software. So an operating system 
using 286 protected mode was _incompatible_ with DOS software for the PC, 
which is why Windows didn't get written that way.

But AMD - and then Intel - made the same mistake with 64 bit mode, which 
is why you can't run (directly on the bare iron, without using 
virtualization) 16-bit Windows programs on the 64-bit versions of 
Windows. I just can't understand why, having the historical example of 
the 80286 before them, they would fail to recognize the supreme 
importance of always maintaining upwards compatibility.

John Savard

Technical Details

Message-ID: <11994840-8e9b-47fe-a35f-0bc3344d791a@googlegroups.com>

Path:

mbox-mo1.pugleaf.net!e39ni2207qtk.1!nntp.google.com!i22no6714271qta.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail

References:

<3b1840a6-2ad7-4360-9c87-e3e8ad601ee2@googlegroups.com> <PM000563FF4B2EF298@aca401e3.ipt.aol.com> <3b1840a6-2ad7-4360-9c87-e3e8ad601ee2@googlegroups.com> <PM000563FF4B2EF298@aca401e3.ipt.aol.com> <3b1840a6-2ad7-4360-9c87-e3e8ad601ee2@googlegroups.com> <PM000563FF4B2EF298@aca401e3.ipt.aol.com> <2V%bC.222517$%a1.58398@fx35.iad> <PM000564128FA48D01@aca40a86.ipt.aol.com> <43aeaf25-249f-42c6-b590-4dc9890d1c1c@googlegroups.com> <PM0005643BABCD6267@aca42e3d.ipt.aol.com> <hfba7dtavskr85ssg6crut8hosus6ec3fd@4ax.com> <p53b0n$r5b$2@news.albasani.net> <fdliigFfgjjU24@mid.individual.net>

Show Full Headers

Complete Article Headers

X-Received: by 10.200.68.16 with SMTP id j16mr6243592qtn.17.1517666806968;        Sat, 03 Feb 2018 06:06:46 -0800 (PST)
X-BeenThere: alt.folklore.computers@googlegroups.com
Received: by 10.200.19.197 with SMTP id i5ls2431984qtj.12.gmail; Sat, 03 Feb 2018 06:06:46 -0800 (PST)
X-Received: by 10.200.46.97 with SMTP id s30mr29766505qta.22.1517666806057;        Sat, 03 Feb 2018 06:06:46 -0800 (PST)
X-Received: by 10.31.98.66 with SMTP id w63mr4249512vkb.2.1517666805863; Sat, 03 Feb 2018 06:06:45 -0800 (PST)
Path: mbox-mo1.pugleaf.net!e39ni2207qtk.1!nntp.google.com!i22no6714271qta.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: alt.folklore.computers
Date: Sat, 3 Feb 2018 06:06:45 -0800 (PST)
In-Reply-To: <fdliigFfgjjU24@mid.individual.net>
Complaints-To: groups...@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=72.143.233.231; posting-account=1nOeKQkAAABD2jxp4Pzmx9Hx5g9miO8y
NNTP-Posting-Host: 72.143.233.231
References: <3b1840a6-2ad7-4360-9c87-e3e8ad601ee2@googlegroups.com> <PM000563FF4B2EF298@aca401e3.ipt.aol.com> <3b1840a6-2ad7-4360-9c87-e3e8ad601ee2@googlegroups.com> <PM000563FF4B2EF298@aca401e3.ipt.aol.com> <3b1840a6-2ad7-4360-9c87-e3e8ad601ee2@googlegroups.com> <PM000563FF4B2EF298@aca401e3.ipt.aol.com> <2V%bC.222517$%a1.58398@fx35.iad> <PM000564128FA48D01@aca40a86.ipt.aol.com> <43aeaf25-249f-42c6-b590-4dc9890d1c1c@googlegroups.com> <PM0005643BABCD6267@aca42e3d.ipt.aol.com> <hfba7dtavskr85ssg6crut8hosus6ec3fd@4ax.com> <p53b0n$r5b$2@news.albasani.net> <fdliigFfgjjU24@mid.individual.net>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <11994840-8e9b-47fe-a35f-0bc3344d791a@googlegroups.com>
Subject: Re: Making Computers Secure
From: Quadibloc <jsa...@ecn.ab.ca>
Injection-Date: Sat, 03 Feb 2018 14:06:46 +0000
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Reply to Parent Message