PDP emulation

From: Allison J Parent <allisonp_at_world.std.com>
Date: Mon Mar 6 19:58:56 2000

<V7 doesn't run. More precisely, it boots and starts the kernel but it
<immediately panics. I can't remember what the message was; it's a long
<time since I tried it.

Ill boot mine and see. I have to do a boot foreign from RT-11 as apparently
there is no boot on the pack.

A copy of your mail as a reminder.... ;)
-----------------------------------------------------------------
Date: Tue, 17 Mar 1998 02:19:15 GMT
From: pete_at_dunnington.u-net.com (Pete Turnbull)
X-Beware: experimental sendmail.cf 940816.SGI.8.6.9/980207.PNT
Message-Id: <9803170219.ZM17332_at_indy.dunnington.york.ac.uk>
In-Reply-To: allisonp_at_world.std.com (Allison J Parent)
        "Re: V7 startup" (Mar 16, 20:44)
References: <199803170144.AA16350_at_world.std.com>
Reply-To: pete_at_dunnington.u-net.com
X-Mailer: Z-Mail (3.2.2 10apr95 MediaMail)
To: allisonp_at_world.std.com (Allison J Parent)
Subject: Re: V7 startup
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Status: R

Hi, Allison.

> >>>>>< _at_unix <<<<<<<
>
> THAT'S what I was trying to remember!
>
> Allison

If you're running V7 on real hardware, could you do me a favour once you get
it
running, please? The normal boot sequence for V7 is to hardware boot the
drive, which get the _at_ prompt, then type 'boot' which runs the 'boot'
program, which has a ':' prompt, then specify the drive, partition, and
kernel file:

_at_boot
boot
:rl(0,0)unix

Most systems then come up single-user, and you need to type CTRL-Z or CTRL-D
to continue multi-user. That might involve also typing in the date/time,
and often it's all in uppercase until the right tty driver is running. Lots
of systems also do an icheck on the disks before actually starting -- this
takes a while.

In case you didn't know, to stop it you do

# kill -1 1

which kills init and returns to single-user level; then you type

# sync

a couple of times to flush the disk buffers from memory to disk, and then
you
can halt it safely.

What I want to know is, does that version respond to 'boot' and does it do
the
disk checks?

-------------------------

Ok, it's doesn't boot from the pack so I need a RT-11 to act as primary
boot to acess the device at some higher level. My 11/73 does know DL
boot though. If I try to boot directly it says non-bootable. Invalid
boot block I'd guess.

Once I'm at the boot _at_ (looks just like odt!) either @unix or

 _at_boot
 boot
 :rl(0,0)unix

Also works.

I also have the advantage that I have RT-11 for my systems and if that runs
it's a good head start as you know the hardware works.

<It probably isn't memory, then. It's probably down to something (maybe a
<driver) that checks for something like the presence of a register, finds i
<on my 11/73, and makes an erroneous assumption. V7 predates the 11/73 by
<quite a way, so that wouldn't be too surprising.

The way I'm using it the assumption is that it's minimally 11/34 or better.
Keep in mind the primary IO, DLV11, RL02 are all direct equivalent to
the 11/34 and other unibus boards to the register level.

Since it runs I must be doing something right.

Allison
Received on Mon Mar 06 2000 - 19:58:56 GMT