From: Jay Jaeger
> Here is what I have for drawings:
Wow. You have some very desirable stuff there! Let me point at a couple
of things of particular interest:
> B-TC-FP11-C-6 FP11-C (Print Set MP00038) December 75
> [M8126, M8127, M8128, M8129]
AFAIK, prints for the FP11-C are
> From: Fritz Mueller
> I would really like to track down any of the following resources:
> - PDP 11/45 system engineering drawings *earlier* than those currently
> available on bitsavers (Jun '74)
My KB11-A prints have an 'overall' date of "4/76" (on the front page), but
prints
> From: Electronics Plus
> I did not bring the stuff home. ... Call John Adler ... he owns the
> stuff in the sheds.
Now I am completely confused. What happened to the online spread-sheet that
some of us filled out? Did that go to him? If so, does the fact that we've
heard nothing
> From: Fritz Mueller
> those PDP-11's have their toggles set for V6 single-user boot! :-)
Very observant! (Although I guess you've been using that a lot recently! :-)
> From: Paul Koning
> Was the 11/74 ever shipped?
I don't think so. (Well, I vaguely recall rumours of a
Does anyone know what the difference is between the M8290 and M8291 versions
of the CR11? The only version of the CR11 manual online only seems to cover
the M8290?
Noel
In response to a request a couple of years back from Cindy, I've been slowly
working on a page to help scrappers identify PDP-11's, and give them an idea
what to look for. I have it _mostly_ done:
http://ana-3.lcs.mit.edu/~jnc/tech/pdp11/PDP-11_Models.html
Comments/error-checking etc welcome.
> Even better, it claims to be able to control whether the memory uses odd
> or even parity! (How, for UNIBUS memory, I don't know - there's no way to
do
> this over the UNIBUS.
So this really confused me, as the UNIBUS spec says parity is wholly within
the slave device, and only an
> From: Fritz Mueller
> The most efficient way I think would be to work up a simple LDA loader
> that would fit in a boot sector, and load a diagnostic from contiguous
> disk starting at the second sector. It would then be easy to blast down
> just the boot sector and a
> From: Paul Koning
> It checks if the bits 007750 are active in the parity CSR, if so it
> takes that to be an address/ECC parity CSR.
That's odd; those are the 'error address' bits. Maybe there's an assumption
that the sweep of memory to size it will have caused a parity error from
> From: Fritz Mueller
> it flagged a bunch of memory locations that weren't reported by my much
> simpler diagnostic (which only does all-ones/all-zeros passes looking for
> stuck bits at this point.)
What is is complaining about?
> The MAINDEC memory diagnostic is bulky
> From: Zane Healy
> Paper is an archival medium
If you want archival, you really need to go the 'baked clay tablet' approach..
:-)
Noel
> From: Chuck Guzis
> Maybe paper is obsolete and I'm just behind the times.
You and me both... :-)
Noel
> From: Al Kossow
> I found the brochure for the board
Ah, thanks very much! I had some details (from my old driver), but this
discovery of yours answers my open questions (e.g. board format).
Noel
> From: Jorg Hoppe
> Now you can painlessly plug a physical 11/70 panel
So I'm curious about the flat cables to the -11/70 console, which have been
taken apart into individual conductors. I am wondering why?
This doesn't seem to have been done because you needed to re-order them (they
> From: Fritz Mueller
> Worked up some simple standalone diagnostics to map and test all the
> memory on my 256K MS11-P. Sure enough, I'm seeing some stuck bits at
> various addresses in physical address range 70-75.
Excellent news. (Sorry I've gone quiet - I got
> From: Fritz Mueller
> I think I see an H960 with a couple DEC half panels stuck on it peeking
> out of the very back there...
Two H960's, actually - it looks like there's another one in front of that
one.
If the half panels are for sale, I'll take them! :-)
Noel
Not my thing (I'm into earlier stuff):
https://www.ebay.com/itm/392212420626?
but I thought I'd post it since it's filed in an unusual place.
Noel
> From: Fritz Mueller fritzm at fritzm.org
> I'm assuming that if I had to release the media from the hub in order
> to true it, its value as an alignment cartridge would be lost anyway.
Yes and no The RK05 alignment pack is mostly to make sure that the fine
lateral track
> From: Bill Gunshannon
> I have a number of different memory modules. Mostly DEC but a couple
> zthird party. Here's the problem. None of them are reflected in any of
> the documentation I have been able to find so I can't configure them
> away from their defaults! ...
>
> From: Bill Degnan
> I attempted to port the same version of unix to an rl02 disk pack and
> to run on an actual 11/40. I was able to get ir to boot up to the #
> prompt but my system does not have a working EIS card to proceed any
> further.
I"m incredibly surprised that
> the swappable per-process kernel data does in fact include pre-computed
> contents for all the memory management registers, so we'll be able to
> see (from the process core dump) where the code and data segments were.
Uh, no. The copies there are 'prototypes', later modified for
> I don't recall off the top of my head whether the location of that
> shared block of memory is in the per-process swappable kernel data
> (which is included in the process core dump).
So I checked, and the swappable per-process kernel data does in fact include
pre-computed contents
> From: Fritz Mueller
PPS:
> I could work to extract the core file
I just checked, and the binary for the 'ls' command is what's called 'pure
code'; i.e. the instructions are in a separate (potentially shared) block of
memory from the process' data (un-shared).
I don't recall off the
> From: Fritz Mueller
PS:
> I could work to extract the core file
Can PDP11GUI save output from the -11's console? If so, just say 'od core',
and send me the output.
Noel
> From: Fritz Mueller
> Kernel boots on my actual hardware, but an "ls" in single-user mode
> generates a "Memory error -- core dumped".
Oh, yeah, your hardware definitely has issues, then.
> So evidence is mounting that I really do have some sort of issue with
> my MS11-L.
> From: Fritz Mueller
> I should go read up on QSIC.
There's not much on the Web, alas. We have two working prototypes (a wirewrap
QBUS mother-board with bus transceivers, level converters, etc, connected to
an FPGA prototyp ung card by flat cables), and working FPGA code to emulate an
> From: Fritz Mueller
>>
http://www.tuhs.org/Archive/PDP-11/Distributions/research/Ken_Wellsch_v6/
> Hmm, this link didn't work for me
Arggh, sorry. I simply copied the link from my page:
http://www.chiappa.net/~jnc/tech/V6Unix.html
and didn't check it. :-( I'm a bit
> From: Fritz Mueller
>> the last microinstruction for RTI/RTT has been moved from 002 -> 744.
> So what's at 002 now? Maybe something new was required there by micro
> branch/fork logic, so the original contents had to be moved?
Well, it turns out I've been transcribing the
> From: Fritz Mueller
> Thanks, Noel -- I'll give that a try!
Sure - always glad to help with anything V6 related - that's my chief
technical amusement, now that I'm retired! :-) Any questions/issues, let me
know, and I'll try and get right back.
When booting UNIX, remember make sure
> I guess I'll do up a cheat sheet.
OK, first crack here:
http://gunkies.org/wiki/Upgrading_UNIX_Sixth_Edition
If there are any improvement I can/should make, please let me know.
Thanks!
Noel
> From: Fritz Mueller
> I've thought about that; Unix V6 is actually next on my list of OS's to
> try. I think I have seen a fairly detailed set of instructions on
> building an image from this from the commonly available distribution
> tape.
Yeah, one comes with the V6
> From: Fritz Mueller
> Oh, one last thing: if anybody else out there has a real working '11/45
> + RK05 and wants to try this RSTS image, let me know, and I'll send you
> a copy (all 2.5MB of it, hah). It'd be interesting to see if this a
> really just limited to my machine?
> From: Dave Wade
> The only machine I know where a "byte" is not eight bits is the
> Honeywell L6000 and its siblings
I'm not sure why I bother to post to this list, since apparently people don't
bother to read my messages.
>From the "pdp10 reference handbook", 1970, section 2.3,
> From: William Donzelli
>> in 1980, there were more PDP-11's, world-wide, than any other kind of
>> computer.
> I bet the guys at Zilog might have something to talk to you about.
I was quoting my memory of a DEC ad in the WSJ, which now that I go check,
says the -11 was "the
> From: Guy Sotomayor Jr
> I think it's also telling that the IETF uses the term octet in all of
> the specifications to refer to 8-bit sized data.
Yes; at the time the TCP/IP specs were done, PDP-10's were still probably the
most numerous machines on the 'net, so we were careful to
> From: Grant Taylor
> Is "byte" the correct term for 6-bits? I thought a "byte" had always
> been 8-bits.
I don't claim wide familiary with architectural jargon from the early days,
but the PDP-10 at least (I don't know about other prominent 36-bit machines
such as the IBM
The copy of the KD11-EA engineering drawings (in the 11/34A Field Maintenance
Print Set, MP-00190) on Bitsavers is missing most of the pages that hold the
microcode flow diagrams. I have a set of the KD11-EA FMPS (MP-00192), which
does have all the missing pages, which I can eventually scan.
> From: Fritz Mueller
> All the CPU, FPU, KT11, KW11, and RK11 MAINDECS are passing just fine.
Don't forget Vonada Maxim #12:
"Diagnostics are highly efficient in finding solved problems."
:-)
Noel
> From: Al Kossow
> I do not archive any paper myself.
There are quite a few silver-dish lovers; you might be able to raise some
funds by listing stuff on eBait (although I can easily see that maybe it
would be more hassle than it's worth).
> Currently, I am being asked to reduce my
> From: Paul Koning
>> On Dec 31, 2018, at 6:32 PM, Henk Gooijen via cctalk wrote:
>> ...
>> There are one or two bits in a register of the RK11 that have a
>> different meaning/function, depending on the controller being a -C or
>> -D.
> If someone can point me to
> From: Bill Degnan
> It's pretty well researched at this point to be true to state that the
> first two PDP 11 models were the 11/10 and 11/20. It just takes a while
> for this to work its way through academia.
Some places got the message a while ago:
>> people recently picked that to disambiguate them from all the other
>> -8's.
So my assumption (that it was recent) seems to be incorrect; I heard that it
was in use in the 60's to differentiate it (e.g. for knowing what spares to
take). Alas, with the origin that far back in time,
> From: Al Kossow
> "Straight-8" seems to be a fairly modern name coming from collectors
My _guess_ is that that probably happened because there is no formal 'model'
for that first one (unlike the first -11, which got re-named the -11/20
BITD), and people recently picked that to
> From: Allison
> IC as in digital logic were in production in the early 60s
Yes, but if you look at the picture/manual (I found a "Module location for
I/O" chart on pg. 335 of the PDP-7 Maint Manual - alas, not the whole
machine, just the FLIP CHIP part), the PDP-7 is all B-series and
Does anyone know where the 'Straight 8' name for the first PDP-8 model came
from? Obviously, it's probably a play on the car engine configuration name,
but how did the connection get made? Thanks - I hope!
Noel
> through (I think) the PDP-7; at least, this PDP-7 internals image
> .. seems to show System Modules at the top, and FLIP CHIPs at the
> bottom.
After groveling through the 'PDP-7 Maintainence Manual' (F-77A), this seems to
be accurate. In "Module Identification" (pg. 6-5), it refers
> From: Mattis Lind
> I cannot figure out which early machine it comes from.
They're called 'System Modules':
http://gunkies.org/wiki/System_Module
and they were used from the PDP-1 through (I think) the PDP-7; at least, this
PDP-7 internals image:
> From: Chris Hanson
> Do you mean you would prefer to visit a web page to read the latest
> posts on cctalk rather than have them delivered to you via email?
Hey, that's how I read CCTalk:
http://www.classiccmp.org/pipermail/cctalk/
I don't want all this cruft clogging up my
> From: Paul Koning
>>> core memory details such as destructive read weren't visible to the
>>> CPU
> DATAIP/DATAO on the Unibus doesn't depend on the destructive read
> property.
Yes, the CPU can't tell what the memory is doing.
> The reason it existed is that it
> From: Paul Koning
> For that matter, core memory details such as destructive read weren't
> visible to the CPU
Umm, not quite. If you'd said 'core memory details such as destructive read
weren't visible to the _program_', you'd have been 100% correct.
But as I suspect you know,
> From: Kyle Owen
> Gah...just found it.
We've all been there... :-)
Noel
> From: Jay Jaeger
> I have finished the 3rd phase of my IBM 1410 SMS computer
> reverse-engineering project. ... The ALDs comprise 752 pages from 9 of
> the 11 total volumes of system schematics/engineering drawings ... It
> took me roughly 375 hours of time (probably more
> From: Jay Jaeger
> That code would not run in Windows of course, but it wouldn't be all
> that difficult for someone with a C programming background to move it
> to Windows under gnucc, or even Microsoft C++ or C#.
I highly recommend CygWin (which comes with 'gnucc) for doing C
> From: Paul Birkel
>> I thought RL0x drives use an IBM 5440 type pack (as used on the IBM
>> System/3 DEC may have used their own format (and servo track
>> stuff), I don't know much about the 5440.
> Sounds to me like it was different, but in a good way?
I took a
> From>: Christian Corti
> I thought that the DEC packs would be similar but no, DEC had to invent
> something different...
Huh? I thought RL0x drives use an IBM 5440 type pack (as used on the IBM
System/3 - I used one of those at my first computer job, they'd just gotten
it in); DEC
> On a whim, I tried searching for '"pdp-11" "pdp-11"' (i.e. just
> repeated the keyword), and this time it _did_ turn it up! Very odd.
> I wonder why that made a difference?
So I have a new theory about this. Searching for 'pdp-11' causes eBay to
automagically limit the search to
For some actual content about classic computers (instead of flaming about
various ideas for improving existing systems), I think I've worked out
why the BA11-C and BA11-E mounting boxes have out of sequence variant codes.
It's obvious the variants were not assigned in creation order (the /44 and
> From: Camiel Vanderhoeven
> I have a fully working Ardent Titan with some interesting software on
> it - the bundled version of MATLAB, and BIOGRAF, a molecular modeling
> application
Neat! Excellent! Do you have the source for any/all of the software on it?
Noel
I thought cctalk was supposed to be a complete superset of cctech, but
looking at the cctech archives, I see a lot of posts that didn't make it
to cctalk. Does one need to do both to see everything?
Noel
> From: Paul Koning
>> The DEC font uses a zero with a slash
> For that, a capital O with a slash would probably serve.
Actually, it turns out that only earlier panels (e.g. KA10, TC08, etc) use the
slashed zero; later ones (KI10, RP11, etc) use the ordinary ones. Since our
panel is
> From: Toby Thain
> To get closer I'd need better images of the panels.
Hi, I borrowed a DEC inlay from someone (a KA10 CPU bay) and scanned a chunk
of it (as much as I could fit into my A4 scanner :-) at 200 dpi:
http://ana-3.lcs.mit.edu/~jnc/tech/jpg/KACPUPanel.jpg
I have a TC08
> From: Jason T
> According to my notes, for the VCFMW8 shirts ... I used DIN Next Pro
> Rounded Medium for the panel text, although the font I had in my work
> directory is "DIN 1451 Fette Breitschrift 1936". That is probably the
> font next to the knob on the right and the
> We're just about settled on the format for the QSIC RKV11-F/RPV11-D
> panels.
PS: Here's the latest rev of our thinking:
http://ana-3.lcs.mit.edu/~jnc/tech/pdp11/jpg/inlay-rk11-f3.pdf
if anyone has any comments. (Since the format is entirely set by the FPGA,
it's 'easy' to tweak
So, anyone happen to know the font used in DEC's indicator panels:
http://ana-3.lcs.mit.edu/~jnc/tech/DECIndicatorPanels.html
or, at least, a very close match?
For mockups we're doing, Dave B is using 'DejaVu Sans', but that's not a
really close match: the vertical bars are wider than in the
> From: Steven Malikoff
>> The bulbs had "flying leads" coming out of the glass, no bases ... The
>> bulbs just hovered over the PCB
> It makes me wonder if the 11/15 is much the same.
I just had a look at my -11/20 (the two are basically the same machine; the
/15 was intended
> From: Columbia Valley Maker Space
> The unit starts up and displays some data on the displays
You're lucky that worked. Old power supplies need to be brought back to
life in stages.
> something I can enter via the keypad. ... if you are going to suggest
> some tests, I need
> From: Al Kossow
> CHM has a rather large Intel Paragon system.
> I just recently snagged the software and manuals for it on eBay
> which we didn't have
Excellent! Congratulations!
So, I'm curious - what's the 'most important missing thing' at the
CHM - either am important
> From: Chuck Guzis
> Danny Hillis' CM-1 also used lots of 1-bit processors.
Does anyone know why they didn't catch on? Was it something like 'commodity
'ordinary' processors became so cheap one could build large parallel machines
out of them, and each node had a lot more computing
> From: Rob Jarratt
> DEC 8640 chip. Does anyone have a pinout for it, perhaps even a
> datasheet,
That's almost certainly a DS8640; a quad NOR unified bus receiver. Data
sheets for the are readily available.
Noel
So, I bought a copy of the FP11-A Technical Manual (EK-FP11A-TM), but when it
got here, it was the 'Preliminary' version (-PRE), with type-written text,
some of the figures are hand-drawn, etc.
This manual does not seem to be generally available online, although at one
point a copy was available
> I'm pretty sure the other two have the same orientation.
They do; I looked at the KDF11-A prints in the /23 print set, and then looked
at an actual /23. (I should put a hi-res picture of one on the CHWiki page;
the one that's there is pretty miserable.)
Noel
> From: Rob Jarratt
> The chips where I believe the RESET is oscillating on pin 23 have been
> labelled E151 and E152 ... But I am not really sure if I have
> identified them and the pin correctly.
E151 is the main CPU chip:
http://gunkies.org/wiki/F-11_chip_set
E152 is the
> From: Paul Koning
> A lot more comes from the CPU architecture. The instruction set, of
> course (arguably the first RISC).
An observation about RISC: I've opined before that the CISC->RISC transition
was driven, in part, by the changing balance of CPU speed versus memory
speed:
> From: Paul Koning
> Some years ago I learned the architecture of the Dutch Electrologica X1
> and X8 machines. ... they gain a lot of efficiency by allowing almost
> all instructions to optionally set a condition flag, and almost all
> instructions to be executed
PS:
> Not the simplest machine to implement, mind - the -8 is a lot
> simpler.
As a rough measure of how much more complex, the -8/E and -11/20 are roughly
contemporaneous, and built out of the same technology (SSI TTL on larger
boards): the -8/E CPU is 5 quad boards, and the -11/20 CPU
> From: Ben Bfranchuk
> I just can't find a clean simple design yet. ...
> The PDP 11 is nice machine, but I am looking for simpler designs
> where 16K words is a valid memory size for a OS and small single user
> software.
There was a recent discussion about code density
> From: Doc Shipley
> You guys want people to stop scavenging those irreplaceable treasures?
> Ante up, pure and simple.
That works for keeping stuff out of the hands of scrappers (who are, after
all, business-people) - but not for fetishists who will pay totally
mind-blowing sums
> From: Al Kossow
> The quality of modern keycaps is poor.
> These guys are after mechanical boards with double-shot keytops.
There's something I'm still not quite grasping.
I can see two reasons for people liking the old keyboards:
- i) Higher quality construction
- ii)
> From: Lars Brinkhoff
> I have Alan Snyder's C compiler running
Way cool! Congrats!
Where did you find it? Do you have source too?
> there may also be machine descriptions for Honeywell 6000 series and
> PDP-11
There _was_ one for the H6000, not sure about the -11.
> At
FYI:
From: Lars Brinkhoff
Date: Fri, 19 Oct 2018 11:08:29 +
I have Alan Snyder's C compiler running in case anyone would like to
play with it. It's from around 1975, so the syntax is yummily archaic.
The primary host is a PDP-10 running ITS, but there may also be machine
> the unavilable on-line -11/44 Tech Manual, EK-KD11Z-TM-001
Ooops:
https://vt100.net/manx/details/1,3126
Not sure how that one didn't make it into my PDF collection
Noel
So, I recently acquired a copy of the unavilable on-line -11/44 Tech Manual,
EK-KD11Z-TM-001; alas, it's bound, and I don't wish to debind it to scan it.
If anyone has one of those gizmos that can scan bound books, and wants to scan
this, please let me know, and I can lend it to you.
Noel
> From: Bill Gunshannon
>> From: Jerry Weiss
>> Note: Apparently the RY emulation won't load if more than 256K memory
>> is specified ... I'm entirely not sure why SIMH has to enforce this
>> as its possible to work around .. Anyone know how to override and load
>> in
> From: Paul Anderson
> I don't remember the D tilting.
http://gunkies.org/wiki/File:BA11-DSide.jpg
This is very similar to the slides on the BA11 (-11/20), which also had the
rotation, so I suspect they were all this way (i.e. there no early versions
without, etc). Having said that, if
> From: systems_glitch
> I do have the inner rails/latch system for tilting the box, they are
> plain aluminum.
Like the lower picture:
http://gunkies.org/wiki/BA11-K_mounting_box
there? I'm guessing that's zinc-plated steel.
Alas, I don't know who made those (may have been DEC
> From: Bill Degnan
> What is the part number for the -D ?
Do you have the inners? The only -D inners I know of are the kind shown here:
http://gunkies.org/wiki/BA11-D_Mounting_Box
and if you have those, you're in luck; the outers from a still-available
Chassis Track unit are perfect
> From: systems_glitch
> Looking for a pair of rack rails for my PDP-11/10.
Is it in a BA11-K (as suggested by the Subject line), or BA11-D? (-11/10's
came in both, for the 10-1/2" box.) The -K has the power supply on the end,
the -D down one side.
What slide hardware, if any, do you
> From: Keven Miller
> I found that I have a copy of X3J11-88-001
I turned up a copy of X3J11/87-221; the one before that was X3J11/87-140.
Noel
> From: Eric Smith
> I think the account given in the book may be a bit confused on this
> point. ... That sequence of events is contradicted by Pelkey ...
> describes the name change from Alto Aloha to Ether as happening in May
> 1973 in agreement with WWSUL, except that in
> From: Eric Smith
> 3 Mbps was sometimes referred to as experimental Ethernet, but AFAIK
> the only official name was "Ethernet".
> The best way to refer to it is probably "3 Mbps Ethernet".
I was trying to remember what we called it at MIT (which had one), but my
memory was
> From: Andrew Luke Nesbit ullbeking at andrewnesbit.org
> Where are you located?
Like the listing says, "north side of Boston".
Noel
> From: Mark Tapley
> I'm interested in one of the DECServers but Bill says it's big
> enough to be in the "pick up only" pile. ... drop it at a Pak/n/Ship or
> equivalent to get it headed my way.
PakMail will go pick stuff up.
If several people get together, they could make
Anyone recognize these:
https://www.ebay.com/itm/183446161463
They've got a fair amount of wire-wrap, so I'd think 70's-80's.
Noel
> From: Brent Hilpert
> Your conceptualisation around the role of electrons is perhaps a
> little off.
Well, I'm not taking into effect things like the velocity of electrons
passing around the circuit (more current, with the same number of electrons,
effectively), etc, but I
> From: Brent Hilpert
> With the given 20-30VAC input (do I have that right?)
Yup.
> A glance at the schematic ... you might think it's just a linear
> regulator
And the writeup in the maint manual gives that impression too, which didn't
help! (Hence my assumtion that it was
> From: Alexandre Souza
> What about a nuclear bomb?
OK, if we're going to start being _really_ silly. drop them into a
singularity! :-)
The best part is that you'll get to watch them being ripped apart and
destroyed by tidal forces _forever_ (since time dilation means that as they
> From: Brent Hilpert
> In typical "down-converters" there are additional current paths in the
> supply, paralleling the input path, that can provide the 'additional'
> electron flow rate. ... the whole rationale of a switching supply is to
> use time (varying switching
> From: Mattis Lind
> The H744 is a buck converter. You can read about buck converters here:
> https://en.wikipedia.org/wiki/Buck_converter
Wow, that was incredibly hard to read; no clear and simple explanation of the
basic concept of how it works, before getting into the details!
Oh, one thing I forgot to include:
> a lot of the incoming power in that 30V AC has to be thrown away, in
> producing +5V.
So, if my understanding is correct, the 'switching' H744 really isn't much
better than a classic linear supply. It still wastes a very large amount of
the input
So there's something about the H744 I'm not sure I understand; hopefully those
with more analog-fu will set me straight if I'm confused.
This supply runs off 20-30V AC. It takes the input AC, rectifies it, and runs
it through a cap to filter out the ripple. What's next is that it's an early
401 - 500 of 1540 matches
Mail list logo
