Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!henry From: henry@utzoo.UUCP (Henry Spencer) Newsgroups: net.unix-wizards Subject: Re: Problem Booting System 5 on 11/70 Message-ID: <4452@utzoo.UUCP> Date: Sat, 13-Oct-84 19:19:14 EDT Article-I.D.: utzoo.4452 Posted: Sat Oct 13 19:19:14 1984 Date-Received: Sat, 13-Oct-84 19:19:14 EDT References: <785@aplvax.UUCP> Organization: U of Toronto Zoology Lines: 22 > He has an 11/70 with a western peripherals controller which emulates an > rm05. When he attempts to boot he gets a trap 0. This controller-disk > combination works perfectly using RST/S but somehow system 5 seems to > have problems.... Bell/AT&T RP/RM drivers are notorious for assuming that, if they're on a 70, the controller must be on the Massbus (loose terminology here, but it's what people understand). If your Western Peripherals controller is a Unibus controller, that's almost certainly where the problem is. The difference is in how >16-bit addresses are handled; the "Massbus" controllers can directly address 22 bits of memory, whereas the Unibus controllers need help from the Unibus map. The underlying problem is that AT&T buys only certain combinations of peripherals for internal use, and doesn't test on other combinations. (At least, that's the way it used to be.) Evidently DEC is more paranoid about varying configurations (hence RSTS works). Berklix will probably handle this correctly, since Berkeley is/was heavily into non-Dec and hence often non-Massbus controllers. -- Henry Spencer @ U of Toronto Zoology {allegra,ihnp4,linus,decvax}!utzoo!henry