<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(a)dunnington.u-net.com (Pete Turnbull) X-Beware: experimental sendmail.cf 940816.SGI.8.6.9/980207.PNT Message-Id: &lt;9803170219.ZM17332(a)indy.dunnington.york.ac.uk&gt; In-Reply-To: allisonp(a)world.std.com (Allison J Parent) "Re: V7 startup" (Mar 16, 20:44) References: &lt;199803170144.AA16350(a)world.std.com&gt; Reply-To: pete(a)dunnington.u-net.com X-Mailer: Z-Mail (3.2.2 10apr95 MediaMail) To: allisonp(a)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. 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 @ prompt, then type 'boot' which runs the 'boot' program, which has a ':' prompt, then specify the drive, partition, and kernel file: @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 @ (looks just like odt!) either @unix or @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