On 2/27/2019 1:37 PM, Noel Chiappa via cctalk wrote:
> Hi, does anyone have any PDP-11/60 manuals? I went to do articles on the
> -11/60 and its CPU (KD11-K), but there isn't much online.
>
> Bitsavers has EK-KD11K-TD-PRE, but it only covers the maintenance features,
> not the whole CPU; there
On 2/28/19 5:49 AM, Jay Jaeger via cctalk wrote:
> I don't see this manual on bitsavers, so let me know and I will scan it
> in and stick it on my Google drive in a day or two or three where you
> and Al could snag the scan.
cool, one less thing for me to pull from the archive.
all of the
> Anybody know what the story is there?
It's an indicator that the pre-processor needs to be run first.
The v6 code I've seen never used an include file for the stty/gtty
calls (as opposed to using a struct defined in an include file) so I'm
betting it was a speedup to not fork/exec another
> From: Phil Budne
> I'm betting it was a speedup to not fork/exec another process if it was
> going to be a null transform!
It's worse than that! In vanilla V6, the pre-processor is built into 'cc',
not a separate command.
Here's the relevant code (from expand()):
if
> From: Jay Jaeger
> I have EK-11060-OP-003: "PDP-11/60 installation and operation manual"
> and an update EK-11060-OP-C1.
Yeah, that's the one I referred to as "the general -11/60 manual"; generally,
there's one such for all the -11 models, but the exact name varies from model
to
> On Feb 28, 2019, at 11:43 AM, Phil Budne wrote:
> It's an indicator that the pre-processor needs to be run first.
Ah, okay! So that's a fun bit of V6 apocrypha. Was this gone by V7?
So, I've been having some fun playing around with V6 Unix on my 11/45 a bit
after that last repair.
I've just been tripped up for a little over the fact that the C compiler barfs
if there is whitespace/comentary before the first #include; the workaround
seems to be to add a lone '#' at the
On Thu, 2/28/19, Fritz Mueller via cctalk wrote:
> I've just been tripped up for a little
> over the fact that the C compiler barfs if there is
> whitespace/comentary before the first #include; the
>
> I found this curious. Anybody
> know what the story is there?
My recollection is that it's
IIRC someone on this list was asking for an 1802 some time ago...
https://www.ebay.com/itm/CDP1802-CPU/132727125007
=]
--
Anders Nelson
+1 (517) 775-6129
www.erogear.com
Christian,
there is the document
"9915-TapeDuplicationAndEPROMProgrammingSoftware-09915-10011-46pages-Jul83.p
df" on the HP-.Museum web site.
I think the associated software is not available, but it also uses the
TAPDUP binary (pg. 1-2) and the same IMAGE program.
The binary itself was part of
10 matches
Mail list logo
