The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: toby@telegraphics.com.au (Toby Thain)
Subject: [TUHS] Windows roots and Unix influence (was Re: Happy birthday, Ken Thompson!)
Date: Sun, 4 Feb 2018 16:04:34 -0500	[thread overview]
Message-ID: <62376536-f247-2026-82cb-1defdcca7976@telegraphics.com.au> (raw)
In-Reply-To: <CAEoi9W7Q8eAoWjGZHx2S9cYkU4hNYCGd9abs86QJEfcn5886BA@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1720 bytes --]

On 2018-02-04 3:05 PM, Dan Cross wrote:
> On Sun, Feb 4, 2018 at 12:21 PM, Ron Natalie <ron at ronnatalie.com
> <mailto:ron at ronnatalie.com>> wrote:
> 
>     > None of these APIs is native to NT, they're implemented on top of it.
>     > I think only at boot you can run code that uses the NT API directly.
>     Amusingly, I have a device in my airplane that runs NT4 without any
>     Windows
>     graphical API on it.   You can see the thing printing the NT4
>     startup and
>     build number when you power it on and it will BSOD.
> 
> 
> BSOD on an airplane? That sounds kind of scary.
> 
> One time I was poking around a US Navy landing craft after coming off an
> amphibious assault ship and somehow found myself down in the engine
> room. The computer controlling either the engines or the screws was
> running some variant of Windows. It wasn't my bailiwick at the time (I
> was a Marine officer; I wasn't even *supposed* to be there ... but I was
> curious and pretty much had the run of the boat as long as I didn't
> touch anything) but it sort of scared me.

You might remember this:
https://www.wired.com/1998/07/sunk-by-windows-nt/

--Toby

> 
>     I actually worked with the n10 and i860.   IBM build a 4 processor i860
>     card.   We ported the 370/386 AIX to it.
> 
> 
> That actually sounds kind of cool.
> 
>     The only non x86 chip I worked with NT on was the iTanium (or as we
>     called
>     it the iTanic).   I might have had an NT Alpha around but we pretty much
>     were an OSF/1 shop at the time.
> 
> 
> I think it was Lockheed Martin that ended up buying a ton of Alphas to
> run NT for Exchange server. Shoulda stuck with sendmail....
> 
>         - Dan C.
> 



  parent reply	other threads:[~2018-02-04 21:04 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-04  0:37 Dan Cross
2018-02-04  2:59 ` Nemo Nusquam
2018-02-04  5:06   ` Wesley Parish
2018-02-04  5:18     ` Warner Losh
2018-02-05 19:43     ` Paul Winalski
2018-02-05 21:19       ` Michael Kjörling
2018-02-06  0:37         ` Steve Nickolas
2018-02-06  0:45           ` Warner Losh
2018-02-06  9:14           ` Wesley Parish
2018-02-04  9:14   ` Angelo Papenhoff
2018-02-04 14:15     ` arnold
2018-02-04 17:21     ` Ron Natalie
2018-02-04 20:05       ` Dan Cross
2018-02-04 20:55         ` Nemo
2018-02-04 20:57           ` Warner Losh
2018-02-04 20:59           ` Jon Steinhart
2018-02-04 22:12             ` Clem Cole
2018-02-05  1:32             ` William Cheswick
2018-02-05  1:44               ` Dave Horsfall
2018-02-04 21:04         ` Toby Thain [this message]
2018-02-04 22:22           ` Andy Kosela
2018-02-04 22:43         ` Dave Horsfall
2018-02-04 22:54           ` George Michaelson
2018-02-05  3:35           ` Ron Natalie
2018-02-05  3:40           ` Dan Cross
2018-02-05 13:48             ` William Cheswick
2018-02-05 14:31               ` Ron Natalie
2018-02-05 21:51               ` Dave Horsfall
2018-02-05 21:57                 ` Ron Natalie
2018-02-05 22:31                   ` Grant Taylor
2018-02-05 23:16                     ` Arthur Krewat
2018-02-05 23:49                       ` Grant Taylor
2018-02-06 17:42                       ` Ron Natalie
2018-02-06 18:23                         ` Arthur Krewat
2018-02-05 23:10                   ` Charles Anthony
2018-02-05 23:20                   ` Arthur Krewat
2018-02-05 23:28                     ` Dave Horsfall
2018-02-05 23:36                       ` Arthur Krewat
2018-02-05 23:52                         ` George Michaelson
2018-02-06 14:52                 ` Steffen Nurpmeso
2018-02-05 23:18               ` Lyndon Nerenberg
2018-02-06 21:51               ` Dan Cross
2018-02-06 23:14                 ` Nemo Nusquam
2018-02-06 23:22                   ` Warner Losh
2018-02-07  3:03                     ` Dave Horsfall
2018-02-07  1:23                 ` Dave Horsfall
2018-02-07  1:33                   ` Clem Cole
2018-02-07  1:54                   ` Dan Cross
2018-02-07 18:01                     ` Tony Finch
2018-02-09  2:35                       ` Wesley Parish
2018-02-07 18:50                     ` Bakul Shah
2018-02-15 13:23                     ` Tim Bradshaw
2018-02-05  0:27         ` Kurt H Maier
2018-02-05  0:41     ` Robert Brockway
2018-02-04  9:11 ` Donald ODona
2018-02-04 23:25 ` Dave Horsfall
2018-02-04 23:46   ` Bakul Shah
2018-02-04 23:58     ` Dave Horsfall
2018-02-05  0:06 ` Robert Brockway
2018-02-05  5:37   ` Steve Johnson
2018-02-05  5:53     ` Greg 'groggy' Lehey
2018-02-05 10:49       ` Ron Natalie
2018-02-05  6:57     ` Robert Brockway
2018-02-05 15:20 Doug McIlroy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=62376536-f247-2026-82cb-1defdcca7976@telegraphics.com.au \
    --to=toby@telegraphics.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).