From: Warren Toomey via TUHS <tuhs@minnie.tuhs.org>
To: tuhs@tuhs.org
Subject: [TUHS] Pro/Venix 2.0: reconstructed
Date: Wed, 27 Apr 2022 08:33:58 +1000 [thread overview]
Message-ID: <20220426223358.GA19528@minnie.tuhs.org> (raw)
Hi all, I just received this in the e-mail a few days ago:
[ now at https://www.tuhs.org/Archive/Distributions/DEC/Venix/ProVenix_2.0/ ]
From: Peter Klapper
Subject: PRO/VENIX 2.0 reconstructed ...
... and tested, for your collection ;-)
Probably the best OS for the Pro, see the benchmark:
PRO380 - PRO/VENIX V2.0:
========================
pk$ dryr
Dhrystone(1.1) time for 50000 passes = 86
This machine benchmarks at 581 dhrystones/second
pk$ drynr
Dhrystone(1.1) time for 50000 passes = 95
This machine benchmarks at 526 dhrystones/second
The four additional floppy disks contain also the source code which I
used to rebuild the missing binaries.
I wish you and the community much fun with the "new" resurrected
PRO/VENIX V2.0.
reply other threads:[~2022-04-26 22:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220426223358.GA19528@minnie.tuhs.org \
--to=tuhs@minnie.tuhs.org \
--cc=tuhs@tuhs.org \
--cc=wkt@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).