Re: PDP-11/60 manuals needed

2019-02-28 Thread Jay Jaeger via cctalk


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 is a tech manual - KD11K-TM-001 (I have it in fiche,
> but my fiche reader has a burned out bulb which I have not yet been able to
> replace, so it doesn't do me much good). There is a user manual for the
> FP11-E, which has a certain amount of useful details, but it refers to the
> technical manual, which is not there. And there's EK-11060-SV-01, which covers
> the cabinet and power supply.
> 
> So if anyone has the general -11/60 manual, or the KD11-K tech manual, those
> would be super useful. The FP11-E tech manual would be nice to have, but isn't
> as important as the others.
> 
> Thanks (I hope!)!
> 
>Noel
> 

I have EK-11060-OP-003: "PDP-11/60 installation and operation manual"
and an update EK-11060-OP-C1.

Of course this is not the real technical manual that explains the
processor in detail, but it has the self-test error halts, boot
procedure, etc., which I expect would be handy.

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.

I also have a spare processor handbook, EB-06498-20/77, but it is in a
box in the garage, so I'd rather wait a week or two for warmer weather
to dig it out.  

JRJ


Re: PDP-11/60 manuals needed

2019-02-28 Thread Al Kossow via cctalk



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 paper from the DEC archives have been cataloged, and nothing
is coming up beyond that, the handbook and what i've already scanned.



Re: V6 cc needs hash before whitespace before first include?

2019-02-28 Thread Phil Budne via cctalk
> 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 process if it was
going to be a null transform!



Re: V6 cc needs hash before whitespace before first include?

2019-02-28 Thread Noel Chiappa via cctalk
> 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 (getc(ibuf1) != '#') {
close(ibuf1[0]);
return(file);
}

The code to implement the directives is, ah, entertaining.

Noel


Re: PDP-11/60 manuals needed

2019-02-28 Thread Noel Chiappa via cctalk
> 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 model (unlike, say, the CPU tech manuals, the name for which is pretty
predictable).

> let me know and I will scan it in and stick it on my Google drive in a
> day or two or three

That would be great; thanks very much! No rush at all...

> I also have a spare processor handbook, EB-06498-20/77

We do have that one, thanks.

BTW, looking a little more closely at the cabinet/power-supply manual
(pg. 1-7), the KD11-K TM might _only_ be available on fiche. If so, that'll be
the first time I've ever seen that. Oddly enough, further down the page, the
FP11-E TM seems to be available in printed form (EK-FP11E-TM).


> From: Ethan Dicks 

> I've seen Tech Manuals printed as 2-up on C-sized paper

Yeah, generally things from the -11/20 era are like that (e.g. the RK11-C
manual). Nothing later than that that I've ever seen, though.

>>> I have the two BA11 cabinets for an 11/60, the PSUs, and the front
>>> panel (I'm missing the rack).

> "the rack" is just the outer box with rails (not an H960 - whatever the
> designation is for the odd 11/60 cabinet).

I think it's the H9500 low-boy corporate cabinet, per Chapter 5 in
the cabinet/power manual.

> The backplanes are in the BA11s. I seem to have both MOS and core
> memory and, I am fairly sure, an RK611, along with the CPU. I need to
> take a module inventory.

You seem to have most of the crucial bits, although you might be missing
the power harness.

Do you have the optional WCS module (M7870)? There are also ROM modules, and
a diagnostic module, that can go in that slot - only one of the three at a
time, though.

Noel


Re: V6 cc needs hash before whitespace before first include?

2019-02-28 Thread Fritz Mueller via cctalk
> 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?


V6 cc needs hash before whitespace before first include?

2019-02-28 Thread Fritz Mueller via cctalk
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 beginning of the file.  It took me a while 
to notice that this was done, for example, in all of the device driver sources.

I found this curious.  Anybody know what the story is there?

--FritzM.




Re: V6 cc needs hash before whitespace before first include?

2019-02-28 Thread Brian L. Stuart via cctalk
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 documented in the 6th
Ed C manual that # has to be in the first column.
Beyond that, I vaguely recall something to the effect
that if the first line isn't a preprocessor directive,
then it skips any preprocessing at all.

BLS
 


eBay: RCA CDP1802

2019-02-28 Thread Anders Nelson via cctalk
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


Re: HP 85 tapes

2019-02-28 Thread Martin Hepperle via cctalk
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 this and is not documented (it was considered
part of the whole package).

What is available via M. Craggs web site are the files from a "Hybrid ROM
Creation Pak", which includes TAPDUP. The IMAGE program (pg 2-2) contained
there is probably similar or the same. The Master/Slave programs and some
more are not in this package.

>From the "Hybrid ROM Creation Pak"
AUXROM.ASM
AUXROM.BAS
AUXSHELL.BAS
CREATEROM.BAS
DATAIO-19.BAS
DATAIO-29A.BAS
EPROM2.BAS
IMAGE.BAS  ---   20 ! (program "IMAGE", 09915-90022, p.5-5...5-6) (these
page numbers do not refer to the manual 09915-10011)
MAINBASIC.BAS
RBUILD85S.ASM
RBUILD87S.ASM
ROMSHELL.ASM
TAPDUP.ASM

Martin