From: Michael Casadevall <michael@casadevall.pro>
To: Grant Taylor <gtaylor@tnetconsulting.net>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Four windowing systems on SunOS
Date: Wed, 2 Nov 2022 04:55:20 -0400 [thread overview]
Message-ID: <CAEMRDeEs56Fku8yC0dHcd2Lf6VBS4ijThyG9zyrB33f_2NuPpA@mail.gmail.com> (raw)
In-Reply-To: <16d7a543-8c34-3663-f0d7-14b588683d6c@spamtrap.tnetconsulting.net>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
I extensively researched this; there are infact copies of Pinball for
64-bit platforms: https://www.youtube.com/watch?v=3EPTfOTC4Jw&t=47s
Pinball had problems relating to 64-bit FPU precision (and this can
actually be reproduced by fiddling with FPU flags), but it did ship in
Windows XP x64 Professional.
Michael
On Mon, Oct 31, 2022 at 5:55 PM Grant Taylor via TUHS <tuhs@tuhs.org> wrote:
> On 10/31/22 1:21 PM, Dan Cross wrote:
> > That sounds like a ton of codebases, though. I remember trying to port
> > an APL interpreter to 64-bit, and giving up; too much type puning of
> > pointers through int's.
>
> This reminds me of the stories I've heard about Microsoft's inability to
> port Pinball to /their/ 64-bit processor, the Itanium.
>
> No, not their copy of /AMD/'s 64-bit extension on Intel's x86
> architecture. ;-)
>
>
>
> --
> Grant. . . .
> unix || die
>
>
[-- Attachment #2: Type: text/html, Size: 1328 bytes --]
next prev parent reply other threads:[~2022-11-02 8:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 18:21 [TUHS] " Kevin Bowling
2022-10-31 19:14 ` [TUHS] " Larry McVoy
2022-10-31 19:17 ` Jon Steinhart
2022-10-31 19:21 ` Dan Cross
2022-10-31 21:52 ` Grant Taylor via TUHS
2022-11-01 11:02 ` Liam Proven
2022-11-02 8:55 ` Michael Casadevall [this message]
2022-11-02 15:34 ` Grant Taylor via TUHS
2022-11-02 15:44 ` Michael Kjörling
2022-11-05 10:38 ` Michael Casadevall
2022-11-05 11:21 ` Liam Proven
2022-10-31 19:26 ` Larry McVoy
2022-10-31 19:59 ` Ronald Natalie
2022-10-31 19:33 Nelson H. F. Beebe
2022-11-01 3:25 ` Tomasz Rola
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=CAEMRDeEs56Fku8yC0dHcd2Lf6VBS4ijThyG9zyrB33f_2NuPpA@mail.gmail.com \
--to=michael@casadevall.pro \
--cc=gtaylor@tnetconsulting.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).