From: jsteve@superglobalmegacorp.com (jsteve@superglobalmegacorp.com)
Subject: [TUHS] FYI v9 runs on TME
Date: Sat, 1 Apr 2017 14:51:18 +0800 [thread overview]
Message-ID: <00b0238e-56c2-41ec-9cdb-7813cc266016@SG2APC01FT041.eop-APC01.prod.protection.outlook.com> (raw)
In-Reply-To: <1491026380.1389630.930594288.519397F0@webmail.messagingengine.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1570 bytes --]
It’s far from perfect, but here:
https://sourceforge.net/projects/bsd42/files/4BSD%20under%20Windows/v0/SUN3-research_v9.7z/download
This is my binary, config file and all that jazz…. It’s 40MB compressed and over 1GB uncompressed…
Sent from Mail for Windows 10
From: Cory Smelosky
Sent: Saturday, 1 April 2017 2:00 PM
To: tuhs at minnie.tuhs.org
Subject: Re: [TUHS] FYI v9 runs on TME
Have a pre-made image?
I'm busy fighting with an IPX that is convinced the motherboard is occasionally shorted.
On Fri, Mar 31, 2017, at 22:36, jsteve at superglobalmegacorp.com wrote:
For the 99% of us that don’t have a SUN-3, it’ll run on TME. I followed the instructions on abiyo.net on installing SunOS 4.1.1 onto TME ( http://www.abiyo.net/retrocomputing/installingsunos411tosun3emulatedintme08onlinux ), and then added in the v9.tar file, and walked through the instructions on bootstrapping v9 from SunOS.
I just cheated by copying the SunOS disk into a new scsi disk so I didn’t have to go through the fun of labeling it. TME emulates a SUN3-150 although the BIOS appears to be for a SUN3-160(?).. so the kernel unix.v75 will work when altering the proto0a file.
TME can be a little (lot!) touchy to get working, but with enough persistence you can get it booting the ‘funinthe’ v9 image.
Sent from Mail for Windows 10
--
Cory Smelosky
b4 at gewt.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170401/2da10d26/attachment-0001.html>
prev parent reply other threads:[~2017-04-01 6:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-01 5:36 jsteve
2017-04-01 5:59 ` Cory Smelosky
2017-04-01 6:51 ` jsteve [this message]
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=00b0238e-56c2-41ec-9cdb-7813cc266016@SG2APC01FT041.eop-APC01.prod.protection.outlook.com \
--to=jsteve@superglobalmegacorp.com \
/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).