Re: IBM System/32 available

[Mark J. Blair]

> On Nov 10, 2015, at 07:55, Paul Berger  wrote:
> 
> For the burn in on the CRT, only half of the CRT is used so you can rotate it 
> 180 degrees if that has not already been done.  That also works for 3741 key 
> to diskette machine, same display unit.

I only noticed burn-in on the lower half of the CRT, so this unit probably has 
another lifetime left in its display.

> On the disk drive there is a head lock back top left should be locked when 
> moving and I believe there is also a spindle lock.

The head lock lever was "OFF" as I found the unit, so I rotated it to the "ON" 
position. If there's a spindle lock, it wasn't obvious enough for me to notice 
it.


-- 
Mark J. Blair, NF6X 
http://www.nf6x.net/

RE: VT100 - FUN

[tony duell]

> 
> They were for video in and out. You could sync the VT100  to a feed of
> mono video and the overlaid
> picture would appear on the screen and at the video out connector.

Actually, I beleive (confirmed by the VT100 tech manual and schematics)
that you have to sync the external video to the VT100 and not the other
way round. In other words, you take the signal from the Video Out socket,
extract the sync, then use that to sync the video source (camera or whatever)
that you feed into the Video In socket

> The only secret was you had to set it for 50Hz .

It works perfectly well with the VT100 set to 60Hz, provided that is the 
vertical
rate of the external video source.

-tony

Re: PDP 11/03

[Mark J. Blair]

> On Nov 10, 2015, at 05:56, Noel Chiappa  wrote:
> 
> (Actually, although there are only 10 pins, it looks like the connector
> housings will hold 14-pin shells, so it you want to not have to carefully
> align the cable before plugging it in, go for 14's. Haven't tried this
> personally - yet - so take that one with a grain of salt!)

That's precisely what I did for my little DLV11 to modular adapter. I'll share 
a picture later this morning. The DLV11 housing is wide, presumably to allow 
for wider ribbon cable connectors. I used a 14 pin housing to make it easier to 
line the connector up in the back of a dark equipment rack.

For my discrete wire cables, I've been using 10 pin housings with the keying 
pin blocked off, but 14 pin housings should also work. I keep a supply of the 
crimp pins on hand along with 1, 2, 3 and 10 pin housings to cover DLV11 cables 
plus the common varieties of jumpers I often need to cobble together. I can 
share part numbers if anybody would like me to.


-- 
Mark J. Blair, NF6X 
http://www.nf6x.net/

Re: IBM System/32 available

[Paul Berger]

On 2015-11-09 10:53 PM, Connor Krukosky wrote:
Wow that looks to be in fantastic condition considering its around 40 
years old now!

I really wish the best of luck to whomever gets it.
I must say I'm very jealous ;)

-Connor K

On 11/9/2015 9:20 PM, Mark J. Blair wrote:

At long last, here are pictures and details!

http://www.nf6x.net/2015/11/ibm-system32-at-the-local-electronics-recycler/ 






That big disk is nearly bullet proof, we had one in a store controller 
where they had a fire in the store and the fire got close enough to it 
to scorch the paint on the covers, but the drive still worked and all 
the data was recovered off of it.  They do however sometimes squeak a 
little when they seek.


For the burn in on the CRT, only half of the CRT is used so you can 
rotate it 180 degrees if that has not already been done.  That also 
works for 3741 key to diskette machine, same display unit.


The orange plastic box inside the cardboard box contains a head 
alignment tool for the 33FD diskette unit.  One thing that may go wrong 
with the diskette drives is the lower limit stop on the head carriage 
may break off and allow it to go below track 0.  These drives do not 
have a track 0 sensor so when they are initialized the drive does about 
80 out steps to make sure it is at zero so it hammers on that down stop. 
and it is plastic so it won't get better with age.


On the disk drive there is a head lock back top left should be locked 
when moving and I believe there is also a spindle lock.


Those little cards in the envelopes may have been used for indicator 
cards or probing.  I seem to remember that the service guide sat in the 
space just above the logic gate, but I don't see it in the pictures.


Paul.

Re: VT100 - FUN

[rod]

Now that would be a find.

As it so happens one of the guys who worked with me at NL
lives locally and we are both on the local council so I see him often.
 In fact his wife (also councilor) was here yesterday.
As he was still there after I left to join DEC he may know more.

The keyboards some were not cherry.
There was one type that counted through a matrix until it found the
connected crosspoint and stopped the count. The count was your key code.

The early ones were blue and the later ones brown and gray I think.

My wife worked at a local building society and they had some.
One day I showed her a label on the back of hers stating
'Tested OK RVS' (needless to say RVS is me) and a date
before we even met.  Coincidences are great.

I'd love to get it running for old times sake.



On 10/11/15 18:00, tony duell wrote:

I remember joining DEC in early October 1973. At the time I was working
for a small local company called Newbury Labs.

When I was an undergraduate at Cambridge University (1985-1988) they were
still using (somewhat later) Newbury terminals on the mainframe. Due to the
metal cases they were often known as 'biscuit tins'.

I rescued one when they were being cleared out, I probably still have it 
somewhere.
It has a separate keyboard (just an array of switches) and I think has a 
VT131-like
editing mode (probably totall different commands though). I remember inside 
there's
a monitor PCB on the back of the upper part of the case and one or two boards
full of logic. Probably a microprocessor in there, and quite a bit of TTL. I 
remember
some 74181 ALUs (of all things!)

-tony

Re: WD9000 Pascal microengine schematics available

[Al Kossow]

On 11/10/15 2:00 AM, GerardCJAT wrote:

Help would be nice reverse-engineering the chipset.



I also picked up some of the Russian versions of the >instruction decode chip.


Any idea how one can do it ???



The same way the other NMOS devices like the 6502 have been done. Mapping the 
photos to polygons and tracing
out the layout.

My problem is I've not done it before. I also have the logic-analyzer-on-a-chip 
out of the 165xx series shot but
not analyzed.

http://siliconpr0n.org/archive/doku.php?id=mcmaster:hp:hp-c5_1fi1-0001

RE: VT100 - FUN

[tony duell]

> 
> I remember joining DEC in early October 1973. At the time I was working
> for a small local company called Newbury Labs.

When I was an undergraduate at Cambridge University (1985-1988) they were 
still using (somewhat later) Newbury terminals on the mainframe. Due to the 
metal cases they were often known as 'biscuit tins'.

I rescued one when they were being cleared out, I probably still have it 
somewhere.
It has a separate keyboard (just an array of switches) and I think has a 
VT131-like
editing mode (probably totall different commands though). I remember inside 
there's
a monitor PCB on the back of the upper part of the case and one or two boards
full of logic. Probably a microprocessor in there, and quite a bit of TTL. I 
remember
some 74181 ALUs (of all things!)

-tony

Re: WD9000 Pascal microengine schematics available

[Brad Parker]

My problem is I've not done it before. I also have the 
logic-analyzer-on-a-chip out of the 165xx series shot but

not analyzed.

http://siliconpr0n.org/archive/doku.php?id=mcmaster:hp:hp-c5_1fi1-0001

Don't you also need to "delayer" the chip to get all the hidden 
features?   I thought the process of reconstructing the polygons 
required that each successive layer be exposed.  From the "top" I'd 
think you'd only see a single metal layer.  But then again, on a old 
chip like that there may only *be* one metal layer :-)


My primitive understanding is that there will be a "base layer" with 
junctions and one or more metal layers on top doing the interconnect.


(I try and steer clear of physical design, or "PD" as we call it, since 
it's seriously complex.  but also interesting!)



-brad

Re: WD9000 Pascal microengine schematics available

[Kyle Owen]

On Nov 10, 2015 2:40 PM, "Brad Parker"  wrote:
>
>
> Don't you also need to "delayer" the chip to get all the hidden
features?   I thought the process of reconstructing the polygons required
that each successive layer be exposed.  From the "top" I'd think you'd only
see a single metal layer.  But then again, on a old chip like that there
may only *be* one metal layer :-)
>
> My primitive understanding is that there will be a "base layer" with
junctions and one or more metal layers on top doing the interconnect.
>
> (I try and steer clear of physical design, or "PD" as we call it, since
it's seriously complex.  but also interesting!)
>

As a physical layout guy, you're absolutely correct. Some ICs can have tens
of metal layers, and in order to have better yield, planarization is used,
requiring fairly uniform metal density across all layers. This means adding
metal fill where necessary, so that makes visualizing ICs much more
difficult. Modern digital ICs typically rely on standard cell libraries, so
that can make identification a little easier. Once you've identified one
NAND gate or inverter, for instance, you've identified them all. Not so
with the early designs that were more discrete, in that respect.

These folks have done a lot of work related to this field:
http://www.visual6502.org

Kyle

Re: PDP-11/45-55 CPU fan assemblies

[Henk Gooijen]

-Oorspronkelijk bericht- 
From: Noel Chiappa 
Sent: Saturday, November 07, 2015 2:50 PM 
To: cctalk@classiccmp.org 
Cc: j...@mercury.lcs.mit.edu 
Subject: PDP-11/45-55 CPU fan assemblies 


Hi, all: I recently bought a PDP-11/45 [well, a /55, to be technical;
the /45, /50 and /55 are completely identical except for
i) the memory options installed at purchase, and
ii) the printing on the front console :-], but alas, when I looked
closely, it is missing both upper and lower CPU fan assemblies.
(No doubt, removed to allow cannabilization of the fans, to keep
another machine running.)



(For those who aren't familiar, these are long brackets to which a
number of the usual square fans are bolted; one is placed above,
and one below, the cards in the main pull-out rack of the CPU. The
one on top is hinged along the long edge, so it can be rolled back
out out of the way, for running cables to boards.)


To be more exact, the bottom is sort of an open box and has 4 fans.
The open side faces towards the card cage, the bottom (outside) has
3 rows of slits, size of the square fans.
The top part consist of *two* parts, one is a small box with the
downward side open. You would not want to stick your fingers there
when the fans run :-/  This side faced the card cage from the top.
The outer top has slits over the entire length. The width is the
width of the fans. With 5 "lips" another sheet of metal is hinged
onto the top fan box. When mounted on the BA11-F box, you can open
this sheet of metal and have access to the cables conduit.


So, does anyone i) have a spare set they don't want (I know, I know,
I know, p < .1, but maybe a miracle will happen);


That makes me the "miracle worker" :-)
Sending an email off-line.

- Henk


Thanks (hopefully :-)!

  Noel

MAINDEC-11-DZQKC-E-D listing posted (Re: Deciphering PDP-11/05 ZQKC (Instruction Exerciser) MAINDEC failures...)

[Jay Jaeger]

On 11/9/2015 3:42 PM, Josh Dersch wrote:

> On Mon, Nov 9, 2015 at 12:37 PM, Jay Jaeger  wrote:
> 
>> On 11/8/2015 11:50 AM, Josh Dersch wrote:
>>
>>>
>>> Anyone have any experience with this particular diagnostic?
>>>
>>> Thanks,
>>> Josh
>>>
>>
>> The version can normally be identified either by the file name or on the
>> paper tape if you are using a real paper tape.  My guess is that the
>> version you are running does not match the PDF.
>>
>> Some of us also have diagnostic listings of various versions, and have
>> some of them on Microfiche.  Unfortunately, I do not seem to have a
>> listing for DZQKC (any revision).  [It isn't missing - it isn't even
>> listed in the fiche index.  :( ]
>>
>> HOWEVER, I *DO* have a *paper* listing of revision E (among others).
>> The code starting at 16002 reads
>>
>> 016002  105737 177564  TSTB @#TPS
>> 016006  100375 BPL  .-4
>> 016010  006237 177564  TSTB @#TPS
>> 016014  01 WAIT  ; WAIT FOR FIRST INTERRUPT
>>
>> The routine starts at 015734 and the comment is ";CHECK TTY INTERRUPT"
>>
>> AND, the paper copy has a red stamp indicating that a change may be
>> required for it to operation.
>>
>>   LOC  FROM TO
>>  2266   200 340
>> 14146   200 340
>> 16164  52274737
>> 16166 0 160
>>
>>  160  - 5227
>>  162  -0
>>  164  - 1375
>>  166  -  207
>>
>> So, please provide either the complete file name you loaded (if you are
>> loading from RX, hard disk, DECTape, etc., or the complete information
>> on the paper tape and we should at least be able to help you figure out
>> if they match, or not, and whether or not someone has a listing that
>> matches and can tell you what the error might mean, and perhaps provide
>> a scan to you (and bitsavers).
>>
> 
> Thanks, I should have thought to check the revision codes in the first
> place.  Looks like the Bitsavers docs are from revision C; I've been
> running the paper-tape version that's on Bitsavers (
> http://bitsavers.informatik.uni-stuttgart.de/bits/DEC/pdp11/papertapeimages/20031230/tray4.txt),
> which is labeled as "maindec-11-dzqkc-e-pb" which looks like it should be
> Revision E (which is fortunate!).
> 
> If you do have the ability to scan this, I'd love to see it.
> 
> Thanks,
> Josh
> 
> 
> 
>>
>> JRJ
>>
>>
>>
> 

The diagnostic listing is now available in my new bitsavers-contrib
folder on Google drive:

https://drive.google.com/folderview?id=0B2v4WRwISEQRWWFFdVpCZWFTZEU=sharing

This is the only document in there right now, and you will find it in
the same path that the other occupies on bitsavers, i.e. in folder
./pdf/dec/pdp11/xxdp/diag_listings

A PDF is there as well as a zip file containing the original .tif files
as Al Kossow prefers for submissions.  (Al:  Hint, Hint  ;) ).

JRJ

Re: WD9000 Pascal microengine schematics available

[Al Kossow]

On 11/10/15 3:47 PM, Brad Parker wrote:

but what is special about the HP 165xx chip which Al referenced?


Variations of that ASIC are the core of HP's logic logic analyzers for a LONG 
time
(at least while they were using 68K processors).

One of my back burner projects has been to understand how they worked as an 
embedded
system. Sadly, I've heard the person who designed it passed away this past year.

One of the things that made HP magical in the 70's and 80's was how advanced 
their ASIC
capabilites were compared to the competition.

Re: WD9000 Pascal microengine schematics available

[Al Kossow]

On 11/10/15 3:56 PM, Brad Parker wrote:

fyi:  from the 6502 faq:

/* How do you turn bitmaps into polygons?/
We draw them in our custom Python app.  We spent about two months looking at 
automatic vectorization and using the bitmaps to create polygon fragments, but 
neither of these was better than just
sitting down and clicking out the polygons.  It's almost essential to have our 
own vector drawing app, so we can control snapping, do fancy copy-paste, get 
good vector data, and greatly speed up the
work.




/* How did automatic vectorization fail?/
It was more work to clean up the results of automatic vectorization than to do 
clean work in the first place.  Damage, dirt, and ambiguous or falsely detected 
features in the chip die shots create
problems.  We also rely on finding and modelingburied contacts 
like they would appear in the original 
fabrication masks, not like they appear in silicon.  This is
very difficult, if not impossible, to do automatically.

I'm not surprised by this.  So in the end, a human brain figured out where the polygons 
are.  It might be a fun "internet distributed" project to farm out sections to 
lots of people and then assemble
the results...

-brad



you may want to check out
https://siliconpr0n.org/archive/doku.php?id=motorola:68000

Re: WD9000 Pascal microengine schematics available

[Eric Smith]

On Tue, Nov 10, 2015 at 1:39 PM, Brad Parker  wrote:
> Don't you also need to "delayer" the chip to get all the hidden features?
> I thought the process of reconstructing the polygons required that each
> successive layer be exposed.  From the "top" I'd think you'd only see a
> single metal layer.  But then again, on a old chip like that there may only
> *be* one metal layer :-)

For late 1970s coarse geometry NMOS with only one metal layer, it's
usually possible with only a single photomicrograph, especially if
there isn't a thick passivation layer. That's how the 6502 was
originally reverse-engineered. As the processes became more complex
and added more metal layers, reverse-engineering has increasingly
required delayering.

The use of depletion mode nFETs for loads does make it a little more
difficult, as you can't see the difference in the diffusion, but it's
usually possible to infer which nFETs are the loads.

The LSI-11, WD16, and WD9000 chipsets are three-supply-voltage NMOS,
so they shouldn't even have any depletion loads to worry about.
Depletion-load NMOS eliminated the +12V requirement, so was usually
only used for single-supply 5V parts, Mostek pioneered depletion-load,
and one of the earliest commercial uses was the Zilog Z80 CPU, which
was originally fabbed by Mostek both under contract to Zilog and as
Mostek's second-source.

Usually along with depletion-load, an on-chip substrate bias generator
eliminates the Vbb requirement, which was usually -5V.

RE: VT100 - FUN

[Robert Jarratt]

> -Original Message-
> From: cctalk [mailto:cctalk-boun...@classiccmp.org] On Behalf Of rod
> Sent: 10 November 2015 17:05
> To: General Discussion: On-Topic and Off-Topic Posts
> Subject: Re: VT100 - FUN
> 
> I remember joining DEC in early October 1973. At the time I was working for a
> small local company called Newbury Labs.
> We designed and built what were then called glass teletypes.  Twenty four 
> lines
> of eighty characters, upwards scrolling only,shift registers for memory. TTL
> everything else.
> 


When I was at school I seem to recall that the glass teletypes used by my local 
polytechnic on their DECSYSTEM20 were Newbury Labs. They were a great step up 
from the Teletype at the time. I didn't see a VT1xx until I got to my M.Sc at 
Manchester (1984-1985) where I had a VT125 connected to a 780. I have a VT101 
and VT102, but would love to get a 125 just for old times sake.

Regards

Rob

Re: WD9000 Pascal microengine schematics available

[Brad Parker]

On 11/10/15 5:50 PM, Eric Smith wrote:

On Tue, Nov 10, 2015 at 1:39 PM, Brad Parker  wrote:

Don't you also need to "delayer" the chip to get all the hidden features?



For late 1970s coarse geometry NMOS with only one metal layer, it's
usually possible with only a single photomicrograph, especially if
there isn't a thick passivation layer. That's how the 6502 was


...

Wow.  That was really interesting and helpful (thanks to both of you - 
Kyle and Eric).


So, since it appears to be NMOS with a single metal layer, it seems like 
one could feed the jpeg into a program and find all the polygons.  
Interesting.  Now I'm curious how the 6502 guys did it :-)


I understand why it would be interesting to figure out the WD pascal 
engine, but what is special about the HP 165xx chip which Al 
referenced?  (I've sort of given up on LA's, at least once which are not 
embedded in the cpu :-)


-brad

Re: WD9000 Pascal microengine schematics available

[Brad Parker]

fyi:  from the 6502 faq:

/* How do you turn bitmaps into polygons?/
We draw them in our custom Python app.  We spent about two months 
looking at automatic vectorization and using the bitmaps to create 
polygon fragments, but neither of these was better than just sitting 
down and clicking out the polygons.  It's almost essential to have our 
own vector drawing app, so we can control snapping, do fancy copy-paste, 
get good vector data, and greatly speed up the work.


/* How did automatic vectorization fail?/
It was more work to clean up the results of automatic vectorization than 
to do clean work in the first place.  Damage, dirt, and ambiguous or 
falsely detected features in the chip die shots create problems.  We 
also rely on finding and modelingburied contacts 
like they would appear in the 
original fabrication masks, not like they appear in silicon.  This is 
very difficult, if not impossible, to do automatically.


I'm not surprised by this.  So in the end, a human brain figured out 
where the polygons are.  It might be a fun "internet distributed" 
project to farm out sections to lots of people and then assemble the 
results...


-brad

Re: MAINDEC-11-DZQKC-E-D listing posted (Re: Deciphering PDP-11/05 ZQKC (Instruction Exerciser) MAINDEC failures...)

[Al Kossow]

On 11/10/15 2:10 PM, Jay Jaeger wrote:


A PDF is there as well as a zip file containing the original .tif files
as Al Kossow prefers for submissions.  (Al:  Hint, Hint  ;) ).



Thanks! Just send me an email as you add things, and I will pick them up.

Re: VT100 - FUN

[Pontus Pihlgren]

On Tue, Nov 10, 2015 at 07:52:51AM +, rod wrote:
>
> Now there was one interesting but little known VT100 feature. On the
> back it had two BNC connectors.
> They were for video in and out. You could sync the VT100  to a feed
> of mono video and the overlaid
> picture would appear on the screen and at the video out connector.

I actually used this once to debug a broken vt220:

http://www.update.uu.se/~pontus/slask/vt220-125.jpg

I could verify that the logic board of the vt220 was ok.

/P

Re: PDP 8E Panel Paint Chipping - How to seal edges

[rod]

Hi Al
Thanks for the order - please remind me of your exact requirement

Needless to say this is an issue I am all too aware of.
This time round as per my updates we are going for a matte finish.
My silk screen girls are deciding at which stage to put the matting 
agent on.
They also think it might well improve even the latest inks when it comes 
to bonding.


Screening is quite robust but if you go at it with something sharp, you 
can scratch it.


My my sample (old and damaged) panel has left the us and I'll track it

Regards

Rod




On 09/11/15 23:11, Al Kossow wrote:



On 11/9/15 3:04 PM, rod wrote:


  2.  Screen Print first holes second.



That was clearly the case on the panel that I sent scans of to you
and I mentioned that they had milled off some of the white lines around
the cutouts for the paddle switches.

Re: VT100 - FUN

[rod]

Ah yes forgot that bit (thirty plus years is a while back) Tee adapter 
on VT100 out, cable to cam sync in on cam - cam out to vt100 in.

Ill give it a go later- my video titler has an ext sync connector

On 10/11/15 10:59, Christian Corti wrote:

On Tue, 10 Nov 2015, rod wrote:
They were for video in and out. You could sync the VT100 to a feed of 
mono video and the overlaid picture would appear on the screen and at 
the video out connector.


AFAIR you couldn't. You had to synchronize the external video source 
to the VT100.


Christian

Re: VT100 - FUN

[Paul Koning]

> On Nov 10, 2015, at 5:23 PM, Robert Jarratt  
> wrote:
> 
> 
> 
>> -Original Message-
>> From: cctalk [mailto:cctalk-boun...@classiccmp.org] On Behalf Of rod
>> Sent: 10 November 2015 17:05
>> To: General Discussion: On-Topic and Off-Topic Posts
>> Subject: Re: VT100 - FUN
>> 
>> I remember joining DEC in early October 1973. At the time I was working for a
>> small local company called Newbury Labs.
>> We designed and built what were then called glass teletypes.  Twenty four 
>> lines
>> of eighty characters, upwards scrolling only,shift registers for memory. TTL
>> everything else.
>> 
> 
> 
> When I was at school I seem to recall that the glass teletypes used by my 
> local polytechnic on their DECSYSTEM20 were Newbury Labs. They were a great 
> step up from the Teletype at the time. I didn't see a VT1xx until I got to my 
> M.Sc at Manchester (1984-1985) where I had a VT125 connected to a 780. I have 
> a VT101 and VT102, but would love to get a 125 just for old times sake.

It's interesting that people were building glass TTYs when DEC was well beyond 
them with the VT05 by that time or earlier, never mind the VT52.

paul

Re: MAINDEC-11-DZQKC-E-D listing posted (Re: Deciphering PDP-11/05 ZQKC (Instruction Exerciser) MAINDEC failures...)

[Jerome H. Fine]

>Al Kossow wrote:


>On 11/10/15 2:10 PM, Jay Jaeger wrote:


A PDF is there as well as a zip file containing the original .tif files
as Al Kossow prefers for submissions.  (Al:  Hint, Hint  ;) ). 


Thanks! Just send me an email as you add things, and I will pick them up.


I also notice that the /bits/ files do not seem to have had the
same attention as the /pdf/ side of the fence.  In particular,
as an RT-11 addict, there are many additional image files
available on the internet which are not reflected at bitsavers
and its mirrors.  While I agree that you may be concerned
that some at those image files are for versions of RT-11
after V05.03, at least a few are not and at least those had
been explicitly allowed even by Mentec.  Would you find
it appropriate to host these files at bitsavers and its mirrors?

In addition, a few internet sites have also had a number of files
for versions of RT-11 after V05.03 for over 5 years now.
Since bitsavers and its mirrors are probably better known
than most other sites, would you also find it appropriate
to host these as well?

Do you also have an incoming directory which will accept image
files?  You can then move them to the correct sub-directory and
maybe even rename them?

Some of the RT-11 image files have DEC ( owner / volumeID )
values which are the equivalent of the names given to PDF files
for DEC manuals.

Please advise whether or not you wish to have copies of these
RT-11 DEC image files.

Jerome Fine

Re: PDP 11/03

[Christian Corti]

On Mon, 9 Nov 2015, Johnny Billquist wrote:

Normally, you'd call them Tx, Rx and GND, but anyway...
No, you do not need to loop back any signals. DEC didn't like to abuse modem 
control for flow control.


What about the connections between the TTL signals and the line 
drivers/receivers? There are definitley such connections to be made in the 
Berg connector (like TTL SERIAL DATA IN on connector pin E). For EIA you 
need to connect pin E with pin M. (See also page 178 in the microcomputer 
interfaces handbook [1980]).


Christian

Re: VT100 - FUN

[Christian Corti]

On Tue, 10 Nov 2015, rod wrote:
They were for video in and out. You could sync the VT100 to a feed of 
mono video and the overlaid picture would appear on the screen and at 
the video out connector.


AFAIR you couldn't. You had to synchronize the external video source to 
the VT100.


Christian

Re: Keshe Plasma Energy (MAGRAV) Blueprints Available For Download

[drlegendre .]

Sorry, but this is total bunkum.

TNSTAAFL

On Tue, Nov 10, 2015 at 9:21 PM, Jerome H. Fine 
wrote:

> This hardware needs to be tested, but I don't have anything like
> the hardware or the equipment to build and test it.
>
> From: "Starship Earth: The Big Picture"  donotre...@wordpress.com>>
>> Date: Thursday, 5 November, 2015 6:48 PM
>> To: Steven Goldhar >
>> Subject: [New post] Keshe Plasma Energy (MAGRAV) Blueprints Available For
>> Download
>>
>> Starship Earth: The Big Picture posted: " Keshe Plasma Energy (MAGRAV)
>> Blueprints Available For Download Please go to Deus Nexus for the
>> details..."
>>
>>
>> New post on Starship Earth: The Big Picture
>>
>>
>>
>> 
>>
>>
>> Keshe Plasma Energy (MAGRAV) Blueprints Available For Download
>> <
>> http://www.starshipearththebigpicture.com/2015/11/05/keshe-plasma-energy-magrav-blueprints-available-for-download/
>> >
>>
>> by Starship Earth: The Big Picture <
>> http://www.starshipearththebigpicture.com/?author=1>
>>
>>
>> KesheFoundation
>>
>>
>> Keshe Plasma Energy (MAGRAV) Blueprints Available For Download
>>
>> Please go to Deus Nexus for the details... <
>> https://deusnexus.wordpress.com/2015/11/05/plasma-energy-download/>
>>
>> Starship Earth: The Big Picture <
>> http://www.starshipearththebigpicture.com/?author=1> | November 5, 2015
>> at 4:48 pm | Tags: blueprints <
>> http://www.starshipearththebigpicture.com/?taxonomy=post_tag=blueprints>,
>> distribution <
>> http://www.starshipearththebigpicture.com/?taxonomy=post_tag=distribution>,
>> download <
>> http://www.starshipearththebigpicture.com/?taxonomy=post_tag=download>,
>> electro-gravitics <
>> http://www.starshipearththebigpicture.com/?taxonomy=post_tag=electro-gravitics>,
>> free energy <
>> http://www.starshipearththebigpicture.com/?taxonomy=post_tag=free-energy>,
>> global <
>> http://www.starshipearththebigpicture.com/?taxonomy=post_tag=global>,
>> Keshe foundation <
>> http://www.starshipearththebigpicture.com/?taxonomy=post_tag=keshe-foundation>,
>> magrav <
>> http://www.starshipearththebigpicture.com/?taxonomy=post_tag=magrav>,
>> Mehran T Keshe <
>> http://www.starshipearththebigpicture.com/?taxonomy=post_tag=mehran-t-keshe>,
>> technology <
>> http://www.starshipearththebigpicture.com/?taxonomy=post_tag=technology>
>> | Categories: Current Updates <
>> http://www.starshipearththebigpicture.com/?taxonomy=category=current-updates>
>> | URL: http://wp.me/p5mdeR-7pH
>>
>> Comment <
>> http://www.starshipearththebigpicture.com/2015/11/05/keshe-plasma-energy-magrav-blueprints-available-for-download/#respond>
>>  See all comments <
>> http://www.starshipearththebigpicture.com/2015/11/05/keshe-plasma-energy-magrav-blueprints-available-for-download/#comments>
>>
>>
>> Unsubscribe <
>> https://subscribe.wordpress.com/?key=ae58620dacfaf1ada77868c6ca1ae577=moegoldhar%40rogers.com=LseOXy%5Be8dXI2kv%2Fgh1hmlMHutrI6KS9itB7%5BhBn%2FfcBLKksw%26F>
>> to no longer receive posts from Starship Earth: The Big Picture.
>> Change your email settings at Manage Subscriptions <
>> https://subscribe.wordpress.com/?key=ae58620dacfaf1ada77868c6ca1ae577=moegoldhar%40rogers.com>.
>>
>>
>> Trouble clicking? Copy and paste this URL into your browser:
>>
>> http://www.starshipearththebigpicture.com/2015/11/05/keshe-plasma-energy-magrav-blueprints-available-for-download/
>>
>>
>>
>>
> Evidently, this possible technology is so far beyond any
> current concepts in quantum physics that some individuals
> refuse to consider that it might work.
>
> Just in case anyone is interested and might be able to build,
> test and evaluate even a small model, I though it might be
> reasonable to distribute the information more widely.
>
> Since a single successful, or even partially successful,
> test that produces at least some power or energy over
> a period that would exceed any possible battery capability
> would point to concepts which can't presently be explained,
> it seems to me to be worth while to build one.  Of course,
> that is easy for me to say since I will not be spending the time
> and effort.
>
> But please let all of us know the details if anyone tries!
>
> Jerome Fine
>

Re: PDP 11/03

[Noel Chiappa]

> From: Jim Stephensn

> thanks for the help.

Eh, always happy to help anyone with PDP-11 stuff.

> the buddy mentioned above did a lot of dec maintenance and put these
> cables in a pile as he found them..

They're probably worth a good bit now, given how scarce they are! ;-)

> Also will order some parts to make the cable off the M7940.

You might want to order some 10-pin shells (for the DLV11-J, etc) at the same
time, those are really common on later DEC gear - the DLV11/DLV11-J was the
transition point.

(Actually, although there are only 10 pins, it looks like the connector
housings will hold 14-pin shells, so it you want to not have to carefully
align the cable before plugging it in, go for 14's. Haven't tried this
personally - yet - so take that one with a grain of salt!)

I'm off to order some 14-pin shells myself! :-)

Noel

Re: PDP 11/03

[Johnny Billquist]

On 2015-11-10 11:55, Christian Corti wrote:

On Mon, 9 Nov 2015, Johnny Billquist wrote:

Normally, you'd call them Tx, Rx and GND, but anyway...
No, you do not need to loop back any signals. DEC didn't like to abuse
modem control for flow control.


What about the connections between the TTL signals and the line
drivers/receivers? There are definitley such connections to be made in
the Berg connector (like TTL SERIAL DATA IN on connector pin E). For EIA
you need to connect pin E with pin M. (See also page 178 in the
microcomputer interfaces handbook [1980]).


Yes. The signals exist, because you might be connecting to a modem. But 
they are not used for flow control. You can control what is output, and 
you can check what comes in. But the hardware do not act on any of this.
If you write your own software then you can of course do things based on 
those signals...


Johnny

Re: Keshe Plasma Energy (MAGRAV) Blueprints Available For Download

[Jerome H. Fine]

This hardware needs to be tested, but I don't have anything like
the hardware or the equipment to build and test it.

From: "Starship Earth: The Big Picture" >

Date: Thursday, 5 November, 2015 6:48 PM
To: Steven Goldhar >
Subject: [New post] Keshe Plasma Energy (MAGRAV) Blueprints Available 
For Download


Starship Earth: The Big Picture posted: " Keshe Plasma Energy (MAGRAV) 
Blueprints Available For Download Please go to Deus Nexus for the 
details..."



New post on Starship Earth: The Big Picture



 


Keshe Plasma Energy (MAGRAV) Blueprints Available For Download



by Starship Earth: The Big Picture 




KesheFoundation


Keshe Plasma Energy (MAGRAV) Blueprints Available For Download

Please go to Deus Nexus for the details... 



Starship Earth: The Big Picture 
 | November 5, 
2015 at 4:48 pm | Tags: blueprints 
, 
distribution 
, 
download 
, 
electro-gravitics 
, 
free energy 
, 
global 
, 
Keshe foundation 
, 
magrav 
, 
Mehran T Keshe 
, 
technology 
 
| Categories: Current Updates 
 
| URL: http://wp.me/p5mdeR-7pH


Comment 
 
	   See all comments 
 



Unsubscribe 
 
to no longer receive posts from Starship Earth: The Big Picture.
Change your email settings at Manage Subscriptions 
. 



Trouble clicking? Copy and paste this URL into your browser:
http://www.starshipearththebigpicture.com/2015/11/05/keshe-plasma-energy-magrav-blueprints-available-for-download/ 







Evidently, this possible technology is so far beyond any
current concepts in quantum physics that some individuals
refuse to consider that it might work.

Just in case anyone is interested and might be able to build,
test and evaluate even a small model, I though it might be
reasonable to distribute the information more widely.

Since a single successful, or even partially successful,
test that produces at least some power or energy over
a period that would exceed any possible battery capability
would point to concepts which can't presently be explained,
it seems to me to be worth while to build one.  Of course,
that is easy for me to say since I will not be spending the time
and effort.

But please let all of us know the details if anyone tries!

Jerome Fine

Re: MAINDEC-11-DZQKC-E-D listing posted (Re: Deciphering PDP-11/05 ZQKC (Instruction Exerciser) MAINDEC failures...)

[Josh Dersch]

On 11/10/15 2:10 PM, Jay Jaeger wrote:

On 11/9/2015 3:42 PM, Josh Dersch wrote:


On Mon, Nov 9, 2015 at 12:37 PM, Jay Jaeger  wrote:


On 11/8/2015 11:50 AM, Josh Dersch wrote:


Anyone have any experience with this particular diagnostic?

Thanks,
Josh


The version can normally be identified either by the file name or on the
paper tape if you are using a real paper tape.  My guess is that the
version you are running does not match the PDF.

Some of us also have diagnostic listings of various versions, and have
some of them on Microfiche.  Unfortunately, I do not seem to have a
listing for DZQKC (any revision).  [It isn't missing - it isn't even
listed in the fiche index.  :( ]

HOWEVER, I *DO* have a *paper* listing of revision E (among others).
The code starting at 16002 reads

016002  105737 177564  TSTB @#TPS
016006  100375 BPL  .-4
016010  006237 177564  TSTB @#TPS
016014  01 WAIT  ; WAIT FOR FIRST INTERRUPT

The routine starts at 015734 and the comment is ";CHECK TTY INTERRUPT"

AND, the paper copy has a red stamp indicating that a change may be
required for it to operation.

   LOC  FROM TO
  2266   200 340
14146   200 340
16164  52274737
16166 0 160

  160  - 5227
  162  -0
  164  - 1375
  166  -  207

So, please provide either the complete file name you loaded (if you are
loading from RX, hard disk, DECTape, etc., or the complete information
on the paper tape and we should at least be able to help you figure out
if they match, or not, and whether or not someone has a listing that
matches and can tell you what the error might mean, and perhaps provide
a scan to you (and bitsavers).


Thanks, I should have thought to check the revision codes in the first
place.  Looks like the Bitsavers docs are from revision C; I've been
running the paper-tape version that's on Bitsavers (
http://bitsavers.informatik.uni-stuttgart.de/bits/DEC/pdp11/papertapeimages/20031230/tray4.txt),
which is labeled as "maindec-11-dzqkc-e-pb" which looks like it should be
Revision E (which is fortunate!).

If you do have the ability to scan this, I'd love to see it.

Thanks,
Josh




JRJ




The diagnostic listing is now available in my new bitsavers-contrib
folder on Google drive:

https://drive.google.com/folderview?id=0B2v4WRwISEQRWWFFdVpCZWFTZEU=sharing

This is the only document in there right now, and you will find it in
the same path that the other occupies on bitsavers, i.e. in folder
./pdf/dec/pdp11/xxdp/diag_listings

A PDF is there as well as a zip file containing the original .tif files
as Al Kossow prefers for submissions.  (Al:  Hint, Hint  ;) ).

JRJ





Thanks a ton for taking the time to make this available.  Time for some 
debugging!


- Josh