The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: gregg.drwho8@gmail.com (Gregg Levine)
Subject: [TUHS] Building a tape IMAGE of Fred's Ultrix-11 3.1
Date: Mon, 14 Aug 2006 23:28:32 -0400	[thread overview]
Message-ID: <18d205ed0608142028r6ae0d79eve1665884f063fa69@mail.gmail.com> (raw)
In-Reply-To: <20060811102637.4608e8b0.jrvalverde@cnb.uam.es>

Hello!
I have to admit that these are nice images. However what's the default
or root password for the NetBSD image? There are somethings I want to
try using it, and as it happens without that I can not get in. It also
requires that I change things inside it to match my network, but
that's of secondary importance as it happens.

Also you should actually compress each image using either the gzip or
bzip2 programs. Of the two I suggest the bzip2 one.
-- 
Gregg C Levine gregg.drwho8 at gmail.com
"This signature was once found posting rude
 messages in English in the Moscow subway."

On 8/11/06, Jose R. Valverde <jrvalverde at cnb.uam.es> wrote:
> I made (some time ago) a copy of many of the images I've been using
> on my FTP. Among them a working image of ultrix-3.1:
>
>         ftp://ftp.es.embnet.org/pub/misc/emul/images/SIMH
>
> I now see I've run out of disk space, so I'll have to move a lot of
> things to a new disk any time soon now which might cause momentary
> lapses in accessibility. Other than that, once the space problem is
> fixed, I'll post as well a  modification to the tape-to-file program
> I made for my own use which works like a charm.
>
>                                 j
>
> On Thu, 10 Aug 2006 17:49:46 -0400
> "Madcrow Maxwell" <madcrow.maxwell at gmail.com> wrote:
> > I downloaded the tape building kit of Fred's enhanced Ultrix 3.1 and
> > set about trying to build an image file suitable for use with SIMH. As
> > simply modifying the included script to write to a normal file instead
> > of a (non-existant) tape device failed, I tried doing things by hand,
> > running maketape and then "cat"ing the file it created along with all
> > the other  files "dd"ed by the script into a single file. While this
> > produced a file that looked about the right size, it didn't work with
> > SIMH as mounting it to the emulated TK50 device and booting produced:
> >
> > HALT instruction, PC: 016300 (CLR R3)
> >
> > Any help on how to get a working image available so that my nerdy
> > history project can proceed?
> >
> > Mike "Madcrow" K.
> > _______________________________________________
> > TUHS mailing list
> > TUHS at minnie.tuhs.org
> > https://minnie.tuhs.org/mailman/listinfo/tuhs
>
>
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
>
>
>



  parent reply	other threads:[~2006-08-15  3:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10 21:49 Madcrow Maxwell
2006-08-11  8:26 ` Jose R. Valverde
2006-08-11 12:35   ` Madcrow Maxwell
2006-08-15  3:28   ` Gregg Levine [this message]
2006-08-15 11:21     ` Andrzej Popielewicz

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=18d205ed0608142028r6ae0d79eve1665884f063fa69@mail.gmail.com \
    --to=gregg.drwho8@gmail.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).