From: Jason Stevens <jsteve@superglobalmegacorp.com>
To: Angus Robinson <angus@fairhaven.za.net>,
Jason Stevens <jsteve@superglobalmegacorp.com>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: 386 PCC
Date: Mon, 25 Mar 2024 09:32:22 -0000 [thread overview]
Message-ID: <7D65B884BDE2EE11A8F800155D08821210B7@SGMCEXCH> (raw)
yeah that was the one that id' first mentioned.
Although I was more so interested in when/where the 386 PCC came from
Seems at best all those sources are locked away.
____
| From: Angus Robinson
| To: Jason Stevens
| Cc: TUHS main list
| Sent: March 25, 2024 09:17 AM
| Subject: Re: [TUHS] 386 PCC
|
|
| Is this it ?
|
| https://web.archive.org/web/20071017025542/http://pcc.l
| udd.ltu.se/
|
| Kind Regards,
| Angus Robinson
|
|
| On Sun, Mar 24, 2024 at 2:13?AM Jason Stevens <
| jsteve@superglobalmegacorp.com> wrote:
|
|
| I'd been on this whole rabbithole exploration thing of
| those MIT PCC 8086
| uploads that have been on the site & on bitsavers, it
| had me wondering is
| there any version of PCC that targeted the 386?
|
| While rebuilding all the 8086 port stuff, and MIT
| PC/IP was fun, it'd be
| kind of interesting to see if anything that ancient
| could be forced to work
| with a DOS Extender..
|
| I know there was the Anders Magnusson one in 2007,
| although the site is now
| offline. But surely there must have been another one
| between 1988/2007?
|
| Thanks!
|
|
|
|
next reply other threads:[~2024-03-25 9:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 9:32 Jason Stevens [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-25 9:07 Jason Stevens
2024-03-24 0:13 [TUHS] " Jason Stevens
2024-03-24 0:17 ` [TUHS] " Luther Johnson
2024-03-24 0:20 ` Charles H Sauer (he/him)
2024-03-24 2:34 ` Heinz Lycklama
2024-03-24 0:25 ` Luther Johnson
2024-03-24 0:27 ` Charles H Sauer (he/him)
2024-03-24 2:00 ` segaloco via TUHS
2024-03-25 8:46 ` arnold
2024-03-25 9:17 ` Angus Robinson
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=7D65B884BDE2EE11A8F800155D08821210B7@SGMCEXCH \
--to=jsteve@superglobalmegacorp.com \
--cc=angus@fairhaven.za.net \
--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).