From: Clem Cole <clemc@ccc.com>
To: Marc Rochkind <mrochkind@gmail.com>
Cc: "tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: [TUHS] Re: History of non-Bell C compilers?
Date: Wed, 13 Mar 2024 11:53:16 -0400 [thread overview]
Message-ID: <CAC20D2OPEwRcr8i5U1jEiLZ3kw2Ud1o6gWGySbG=h7pUY1Z2Ew@mail.gmail.com> (raw)
In-Reply-To: <CAOkr1zXP5FDnes4BssrP-MOSBCf8=7yyK1+mdi=UTdnxF22eWA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2610 bytes --]
Thanks. Fair enough. You mentioned PC/IX as *ISC's System III*
I'm not sure I ever ran ISC's System III port—only the V.3 port - which was
the basis for their ATT, Intel, and IBM work and later sold directly. I'm
fairly sure ISC also called that port PC/IX, but they might have added
something to say with 386 in the name—I've forgotten. [Heinz probably can
clarify here]. Anyway, this is likely the source of my thinking. FWIW: The
copy of PC/IX for the 386 (which I still have on a system I have not booted
in ages) definitely has VPIX.
ᐧ
On Wed, Mar 13, 2024 at 11:28 AM Marc Rochkind <mrochkind@gmail.com> wrote:
> @Clem Cole <clemc@ccc.com>,
>
> I don't remember what it was. But, the XT had an 8088, so certainly no 386
> technology was involved.
>
> Marc
>
> On Wed, Mar 13, 2024 at 8:38 AM Clem Cole <clemc@ccc.com> wrote:
>
>> @Marc
>>
>> On Tue, Mar 12, 2024 at 1:18 PM Marc Rochkind <mrochkind@gmail.com>
>> wrote:
>>
>>> At a trade show, I bought a utility that allowed me to run PC-DOS under
>>> PC/IX. I'm sure it wasn't a virtual machine. Rather, it just swapped back
>>> and forth. (Guessing a bit there.)
>>>
>> Hmm ... you sure it was not either VPIX or DOS/Merge -- ISC built VPIX in
>> cooperation with the Phoenix Tech folks for PC/IX. I always bought a copy
>> with it, but it may have been an option. LCC did DOS/Merge originally as
>> part of the AIX work for IBM and would become a core part of OS/2 Warp
>> IIRC. Both Merge and VPIX had some rough edges but certainly worked fine
>> for DOS 3.3 programs. The issue tended to be Win and DOS graphics-based
>> programs/games that played fast and loose, bypassing the DOS OS interface
>> and accessing the HW directly. For instance, I never got the flight
>> simulator (Air War over Germany) for Dad's WWII plane (P-47 Thunderbolt) to
>> run under either (i.e., only under DOS directly on the HW. FWIW: In that
>> mode, Dad said the simulator flew a lot like how he remembered it).
>>
>> Both Merge and VPIX used the 386 VM support and a bunch of work in the
>> core OS. Heinz would have to fill us in here. The version of the 386
>> port ISC delivered to AT&T and Intel only had the kernel changes to allow
>> the VM support for VPIX to be linked in, but it was not there. IICR (and
>> I'm not sure I am) is that Merge could run on PC/IX also, but you had to
>> replace a couple of kernel modules. It certainly would work on the AT&T
>> and Intel versions.
>> ᐧ
>>
>
>
> --
> *My new email address is mrochkind@gmail.com <mrochkind@gmail.com>*
>
[-- Attachment #2: Type: text/html, Size: 5449 bytes --]
next prev parent reply other threads:[~2024-03-13 15:54 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 17:12 Paul Ruizendaal
2024-03-11 20:44 ` Marc Rochkind
2024-03-11 22:28 ` Peter Yardley
2024-03-12 0:30 ` ron minnich
2024-03-12 13:31 ` Larry Stewart
2024-03-12 16:41 ` Paul Winalski
2024-03-12 14:55 ` Henry Bent
2024-03-12 17:17 ` Marc Rochkind
2024-03-13 14:37 ` Clem Cole
2024-03-13 15:28 ` Marc Rochkind
2024-03-13 15:33 ` Warner Losh
2024-03-13 15:50 ` [TUHS] PC/IX, VPIX, DOS/merge, etc. [was " Charles H Sauer (he/him)
2024-03-13 15:53 ` Clem Cole [this message]
2024-03-12 15:42 ` [TUHS] " Paul Ruizendaal
[not found] <aee297f1-2f6a-4620-87f7-f1672ae03b61@osta.com>
2024-03-15 3:34 ` Heinz Lycklama
-- strict thread matches above, loose matches on Subject: below --
2024-03-12 23:08 Steve Simon
2024-03-07 23:14 [TUHS] " Tom Lyon
2024-03-07 23:24 ` [TUHS] " Warner Losh
2024-03-07 23:39 ` Dave Horsfall
2024-03-07 23:49 ` Larry McVoy
2024-03-07 23:56 ` Luther Johnson
2024-03-08 14:03 ` John Foust via TUHS
2024-03-07 23:59 ` Greg 'groggy' Lehey
2024-03-08 0:08 ` Rich Salz
2024-03-08 0:30 ` Warner Losh
2024-03-08 0:57 ` Rob Pike
2024-03-08 1:08 ` Bakul Shah via TUHS
2024-03-08 1:10 ` Rob Pike
2024-03-08 1:12 ` Rob Pike
2024-03-08 1:22 ` Bakul Shah via TUHS
2024-03-08 9:33 ` arnold
2024-03-08 9:45 ` Wesley Parish
2024-03-08 13:06 ` Luther Johnson
2024-03-08 18:33 ` William H. Mitchell
2024-03-10 3:14 ` Adam Thornton
2024-03-11 22:21 ` Phil Budne
2024-03-07 23:52 ` Warner Losh
2024-03-08 0:15 ` Charles H Sauer (he/him)
2024-03-08 0:30 ` Marc Rochkind
2024-03-08 0:54 ` Heinz Lycklama
2024-03-08 1:48 ` segaloco via TUHS
2024-03-08 2:12 ` Tom Lyon
2024-03-08 2:13 ` Lawrence Stewart
2024-03-08 3:15 ` Jonathan Gray
2024-03-07 23:24 ` Luther Johnson
2024-03-07 23:27 ` Luther Johnson
2024-03-07 23:44 ` Tom Lyon
2024-03-08 0:24 ` Marc Rochkind
2024-03-08 1:27 ` Jeffry R. Abramson
2024-03-10 2:13 ` Greg A. Woods
2024-03-08 2:26 ` Will Senn
2024-03-08 3:03 ` Peter Yardley
2024-03-08 3:28 ` George Michaelson
2024-03-08 3:58 ` Luther Johnson
2024-03-08 5:53 ` Lars Brinkhoff
2024-03-08 13:42 ` Henry Bent
2024-03-08 14:00 ` arnold
2024-03-08 14:16 ` Warner Losh
2024-03-08 15:44 ` Paul Winalski
2024-03-08 17:18 ` Adam Thornton
2024-03-10 2:31 ` Damian Wildie
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='CAC20D2OPEwRcr8i5U1jEiLZ3kw2Ud1o6gWGySbG=h7pUY1Z2Ew@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=mrochkind@gmail.com \
--cc=tuhs@tuhs.org \
/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).