From: Adam Thornton <athornton@gmail.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>,
"[PiDP-11]" <pidp-11@googlegroups.com>,
"General Discussion: On-Topic Posts" <cctech@classiccmp.org>
Subject: [TUHS] Some new text adventure stuff for 2.11BSD
Date: Fri, 3 Jan 2020 22:12:21 -0700 [thread overview]
Message-ID: <CAP2nic3C7OW5OKPB_a2n9jOYDA7476MDRjgxKVyW0DkMKf6OsA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
I'm having a party on Saturday January 11 (and if any of you are in Tucson,
or want to come to Tucson for it, you're invited; email me for the address
and time).
Although the party is Elvis-themed, it's really about boardgaming and
classic videogaming.
So I kind of wanted to put a general-purpose Z-machine interpreter on my
PiDP-11, so that people could play Infocom (and community) games on a real
terminal.
Turns out there wasn't really one, so I ported the venerable ZIP (which I
have renamed "zterp" for obvious reasons) to 2.11BSD on the PDP-11, and I
also wrote a little utility I call "tmenu" to take a directory (and an
optional command applying to files in the directory) and make a numbered
menu, so that my guests who are not familiar with Actual Bourne Shell can
play games too.
These things are at:
https://github.com/athornton/pdp11-zterp
and
https://github.com/athornton/pdp11-tmenu/
Both are K&R C, and compile with the 2.11BSD system C compiler.
My biggest disappointment is that the memory map of Trinity, my favorite
Infocom game, is weird and even though it's only a V5 game, I can't
allocate enough memory to start it. Other than that, V5 and below seem to
work mostly fine; V8 is in theory supported but no game that I've tried has
little enough low memory that I can malloc() it using C on 2.11BSD.
Adam
[-- Attachment #2: Type: text/html, Size: 1789 bytes --]
next reply other threads:[~2020-01-04 5:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 5:12 Adam Thornton [this message]
2020-01-04 9:59 ` [TUHS] [PiDP-11] " Johnny Billquist
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=CAP2nic3C7OW5OKPB_a2n9jOYDA7476MDRjgxKVyW0DkMKf6OsA@mail.gmail.com \
--to=athornton@gmail.com \
--cc=cctech@classiccmp.org \
--cc=pidp-11@googlegroups.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).