test-drb

test-drb@ccmp.vtda.org

101090 discussions

by jnc＠mercury.lcs.mit.edu

> Neither the KD11-E nor the KD11-EA has built-in termination and pull-ups > ... I haven't yet checked, but it may be the only PDP-11 CPU of which > that is true Also the KD11-D of the -11/04. Noel

3 years, 10 months

Is The M9312 Boot Module Essential?

by jnc＠mercury.lcs.mit.edu

So, I've made what I think is a significant discovery about the -11/34: > 1B _is_ necessary, but can be provided anywhere on the bus; most > UNIBUS/QBUS CPU [pullups] have it built in I was wrong. Neither the KD11-E nor the KD11-EA has built-in termination and pull-ups (those are both done with one set of components). I haven't yet checked, but it may be the only PDP-11 CPU of which that is true Without _something_ doing the latter of the above, the UNIBUS won't function at all. (The UNIBUS signal lines mostly operate as negative-logic wired-OR; the pull-ups float it high for '0', and any board pulls it low to send a '1'. No pull-ups, then..) This is almost certainly the reason that the manual calls for the use of either an M9301 ROM or M9312 ROM (which include bus termination) at the start of their UNIBUS, in slot 3 or 4 of the CPU's backplane. (The M7859 of the KY11-LB doesn't have pull-ups either; so in a system with a set of KD11-E/EA cards, and a KY11-B, and nothing else, the KY11-B won't be able to examine UNIBUS locations - even though in a system with _just_ a KY11-B, and one of M9301/M9302/M9312, and NO KD11-E/EA, the KY11-B _can_ do UNIBUS operations.) A system with just an M9302, and no M9301/M9312, will _probably_ work, even though the UNIBUS is only terminated at one end (see my previous post, about QBUS termination on one end only); the M9302 will provide the pull-ups needed for the UNIBUS to function (above). I have also made a number of interesting discoveries about the SACK turnaround; I'll put them in a reply to Fritz's message. Noel

3 years, 10 months

SGI Indigo keyboard / mouse / converter wanted

by jules.richardson99＠gmail.com

Hi all, A friend of mine has just acquired an Indigo (R4k with XZ graphics option), but of course it's the usual story and the keyboard/rodent had been lost. In absence of the genuine items they'd still be happy with a USB converter (at least for the time being), but it seems those are difficult to come by at present, too. Does anyone happen to have a surplus converter suitable for these machines, and/or keyboard/rodent? (according to sgistuff keyboard is p/n 9500801 and mouse p/n 9150800) [side note: they mentioned a USB converter, but I'm pretty sure years ago someone had implemented an adapter to PC-friendly PS/2 parts, too. I'm sure something like would do the trick, too] thanks, Jules

3 years, 10 months

Is The M9312 Boot Module Essential?

by jnc＠mercury.lcs.mit.edu

> From: Jay Jaeger > SACK turnaround capability so that the machine doesn't hang accessing > an address that doesn't respond on the UNIBUS. Umm, I think you're mixing up i) grant timeouts and ii) master-slave timeouts. All PDP-11 CPUs have master-slave timeout handling; after a short delay (10usec or so) with no SSYN (UNIBUS) or BRPLY (QBUS), they resume processing, and take an immediate trap. Most OS's (UNIX, for sure) use this when they are sizing memory. Grant timeouts are less well-documented. I think most CPUs deal with this (not receiving a SACK 'fairly quickly' in response to a grant); I think they basically just ignore t, and keep processing. (That is because there are legitimate causes for not having a grant ackknowledged; e.g. if a device is requesting an interrupt, and then just as the CPU sends out a grant, the device is reset, the device won't respond to the grant, since it's no longer trying to do an interrupt.) The 'SACK turnaround' I think is only used with system health verification; the system wants to make sure that the grant lines aren't broken anywhere. (That's because _if_ a grant line is broken, devices downstream of the break can no longer do interrupts, which generally _will_ hang the overall system, when interrupts don't work as usual.) To do this, the CPU sends an _un-requested_ grant out (on startup), and the SACK turnaround circuitry on the terminator turns it around and sends it back to the CPU; when the CPU sees that, it knows the grant line has no break. It probably caused more problems than it caught, which is my guess as to why no QBUS machine has/uses it. The -11/34 (not the /34A) has something unusual for grant timeouts, but I forget the details. I'll look it up. Noel

3 years, 10 months

Red Hat Linux 7.2 for Alpha

by me＠larbob.org

Try these: https://mirror.rqsall.com/misc/rh-alpha/7.2/ Larkin

3 years, 10 months

VAX9000 unearthed

by ioerg.hoppe＠gmail.com

Hi, my computer club c-c-g.de could acquire the remains of a VAX9000 ! The machine ran at the GWDG computing center in G?ttingen, Germany, around 1993. Parts of it were in stock of their museum for 20+ years. See lots of hires-pictures at https://c-c-g.de/fachartikel/359-vax-9000-ein-starker-exot (scroll to the bottom for a slide show). Joerg

3 years, 10 months

Is The M9312 Boot Module Essential?

by robert.jarratt＠ntlworld.com

I have a PDP-11/24. I have never got very far with it because of power supply problems which I am hopeful will be resolved soon. Looking at the technical manual, it describes an M9312 bootstrap/terminator module. The machine did not come with one of these. I am not sure how the machine could have been useful without it. It did work briefly before the PSU failed and I remember getting a console prompt. So, is the M9312 essential to ever get this machine to boot up an operating system? Thanks Rob

3 years, 10 months

DEC AXV11-C analog board

by dj.taylor4＠comcast.net

I have one of these and would like to use it, however it appears to only partially work.? Here is what I have found that works and what doesn't: 1. CSR and DBR are present and operational. 2. Jumpers set to 'factory'. 3. D/A portion works, can deposit codes in ODT and see voltages out on DAC pins that change depending on the octal value deposited in CSR+4 or +6. 4. A/D portion returns full scale code, either 3777 (2's compliment) or 7777 (offset binary) whether in the input is open or shorted to gnd. I think the problem is that the A/D inputs are not exactly protected and damage has occurred to this portion in the past. Does anyone have any info on the A/D module?? Who made it?? Can you open it up?? Does XXDP have a test for this? Doug

3 years, 10 months

Free Stuff - Pleasanton, Calif.

by bpettitx＠comcast.net

I'm downsizing. Have to get rid of everything. The driveway is filled systems test equipment, components, parts, books, etc. Several thousand TTL chips prototyping boards. Come out and take what you. Junk Bees will be here on Tuesday for what is left. Call 925-998-9968 for directions.

3 years, 10 months

Is The M9312 Boot Module Essential?

by jnc＠mercury.lcs.mit.edu

> From: Rob Jarratt > is the M9312 essential to ever get this machine to boot up an operating > system? Interesting question. I don't have my -11/24 running yet, so this reply is theoretical, not tried in practice (and as we all know, the difference between theory and practice is even larger in practice than it is in theory), but here goes. The M9312 basically provides two things: 1) UNIBUS termination, and 2) boostrap ROM. To further subdivide the former, it provides 1A) analog termination (i.e. a resistance at the end of a transmission line that prevents reflections of signals passing down the otherwise un-terminated transmission lines of the bus), 1B) pullups (so those transmission lines normally float at roughly 3V, unless actively driven by one of the boards plugged into the bus) and 1C) 'SACK turnaround' (a start-up 'safety check' where an un-requested - and thus 'un-grabbed' by any device - bus grant from the CPU on start-up is 'turned around' by the terminator; this verifies that the grant lines are un-broken between the CPU and the terminator - e.g. by someone forgetting to plug in a grant jumper). 1A is not _absolutely_ necessary; this can be seen in small QBUS systems (the QBUS is, at the analog level, sort of identical to the UNIBUS; this an be seen in the use of the same transceiver chips, such as 8641's, on both) which can get away without 1A in small configurations. Whether it's needed on your -11/24 is hard to predict, theoretically; the easiest thing is to just try it and see. Note: it may 'work' without it, but not be as _reliable_ as with it. 1B _is_ necessary, but can be provided anywhere on the bus; most UNIBUS/QBUS CPUs have it built in, and so does the KDF11-U of the -11/24: see pg. of MP01028. 1C is required by _some_ UNIBUS CPUs (ISTR that the -11/04 won't run without it), but the KDF11's in general don't; e.g. the -11/23 definitely runs without it. The KDF11-U might have outboard circuitry to require it, but I'm too lazy to grovel over the prints to see. Easiest to just try it and see. For 2, it all depends on what you're booting from. E.g. the RK11 has a simple enough bootstrap that you can just enter it manually (although it gets old after a while - I remember re-'programming' (think 'soldering iron' :-) a castoff BM-792 someone gave us for our -11/40 so I wouldn't have to). But if you're loading it over the console serial line, e.g. with PDP11GUI, you don't need any ROM bootstrap - the built in console ODT will be enough. You can also load a bootstrap that way; I was booting off the QSIC RK11 with a boostrap loaded over the console serial line; that was faster than the bootstrap in the BDV11. This requires finding - or writing - a bootstrap, which for later DEC mass storage controllers is not trivial. YMMV. TLDR version - probably not! Noel

3 years, 10 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

test-drb