Re: pdp-8/e restoration.

[Ian S. King via cctalk]

On Mon, Aug 7, 2017 at 5:28 PM, Rod Smallwood via cctalk <
cctalk@classiccmp.org> wrote:

>
>
> On 08/08/2017 00:01, Josh Dersch via cctalk wrote:
>
>> On 8/7/2017 3:50 PM, Rod Smallwood via cctalk wrote:
>>
>>
>>>
>>> One other thing - I have a working TU58.
>>> The two cassette drives in a box type with serial interface.
>>> Now the pdp-8/e DECTapes were also called TU58.
>>>
>>
>> The typical DECtapes used with the PDP-8 were TU56's, a completely
>> different (and much more rare) beast.
>>
>> The M8650 is on the list of what you can connect it to.
>>> So does the one substitute for the other and raise the possibility of
>>> booting from tape?
>>>
>>
>> No, they're not substitutes.  I'm not aware of any PDP-8 systems booting
>> and running from a TU58, but I suppose it's not impossible. Mostly the
>> problem with the TU58 at this point is that (a) the capstan rollers in your
>> drives are most likely tar, and (b) the rubber parts in the tape itself
>> have done the same, and (c) the tape itself probably isn't in great shape
>> either.
>>
>> - Josh
>>
>>
>>> Rod
>>>
>>>
>> Mmm senior confusion.
>
> Its a working TU58 - Restored including fixing the roller problem.
> Runs on a PC OK.
>
> Just fixed the echo test problem.
> RS232 on M8650 needed a jumper E-M on board or plug.
>
>
> So now to check out that  rim loader stuff.
> Its in C but I can get round that problem.
>
>
> Rod
>
> --
> Wanted one pdp-8/i rocker switch leaver to copy.
>
>
For verily, LINCtape begat DECtape, and DECtape begat DECtape II.  LINCtape
and DECtape were legitimate backing store, DECtape II was a cheap way of
delivering software updates.

And since when is C a 'problem'?  :-)  -- Ian

-- 
Ian S. King, MSIS, MSCS, Ph.D. Candidate
The Information School 
Dissertation: "Why the Conversation Mattered: Constructing a Sociotechnical
Narrative Through a Design Lens

Principal Investigator, "Reflections on Early Computing and Social Change",
UW IRB #42619

Archivist, Voices From the Rwanda Tribunal 
Value Sensitive Design Research Lab 

University of Washington

There is an old Vulcan saying: "Only Nixon could go to China."

Re: Avoiding Shorts While Testing a DIN Plug

[Brent Hilpert via cctalk]

On 2017-Aug-07, at 3:43 PM, James Hamilton via cctech wrote:
> Hello all,
> 
> Is there any good advice on avoiding shorts while testing a male DIN plug
> with a multimeter? I'm trying to test my C64 power supply, but I'm very
> nervous about accidentally shorting it in the process.
> 


a few options:

a) scavenge an individual pin a from scrap socket of some sort that will fit 
the DIN pins and insert it over the DIN pin
   so it effectively extends out the DIN pins one at a time. Not so great maybe 
if you don't have a junk box with a variety of sockets.
   If you're really particular use some heat shrink over the socket pin to 
insulate it.

b) cut a piece of thin insulating material, paper even, and fold it into a tube 
or into half and insert it over a DIN pin
   so it isolates one pin at a time, and guides the test probe down to the 
target pin.

c) cut a ~1/2" piece of insulating tubing or strip a piece of insulation off a 
piece of wire and use it an in (b). 
   Common #14 house wire (loomex) might be about the right ID if it's not too 
thick at the OD to avoid interference with adjacent pins.

(c) sounds like the most time/effort effective method.

Re: pdp-8/e restoration.

[Ed via cctalk]

I did not  know of Kevin's  site..
Great  stuff there.
 
Ed#
 
 
In a message dated 8/7/2017 2:41:24 P.M. US Mountain Standard Time,  
cctalk@classiccmp.org writes:

On  07/08/2017 18:37, Rod Smallwood via cctalk wrote:

> So to-morrow  connect up a terminal that will do 110 baud and try an echo 
>  test.
> 
> Next part is interesting. There should be a way to fake  a reader / punch 
> and feed in tape images.

There is.  Look  on Kevin McQuiggin's site:
http://highgate.comm.sfu.ca/pdp8/

In the  section called "Software", about 1/3 of the way down, look for 
send.c or  better still new-send.c (I call it rsend, on my system).  You 
might  also find rim.c and the BIN loader useful.

They're also on my webpage,  with the corresponding  manpages:
http://www.dunnington.info/public/PDP-8/

That's the  easiest place to get the manpages for rim.c, send.c, rsend.c. 
Here's the  gist (top parts of the manpages):

rim - create RIM-format file from  ASCII addr/instr
rim is a very simple converter.  It  reads in a file containing two
columns of ASCII digits; the  first column is a list of addresses (in
octal) and the second  is a list of machine instructions (also octal).
Output is a  file suitable to feed to the RIM loader on a PDP-8.

send, rsend - send  a file in RIM or BIN format to a PDP-8
send and rsend are  utilities to transmit a RIM format or BIN format
file from a  UNIX (or other) host to a PDP-8 over a serial line.  The
PDP-8 should be running the RIM loader routine prior to  starting
either of these programs.
Input  should be a file in RIM format or BIN format.  Output goes  to
the host serial port, which should be connected via  appropriate cable
to the PDP-8.
send is a  simple version, with built-in serial port settings and a
fixed  delay between characters.  rsend is more sophisticated; it  can
be controlled by command-line options or environment  variables, and
can accept input on stdin.

On a Unix (or  Linux etc) machine you can pipe the output from rim to 
rsend, and if  you're using papertape images (of which there are load on 
the net), rsend  can strip the headers for you.

-- 
Pete
Pete  Turnbull

Re: pdp-8/e restoration.

[Josh Dersch via cctalk]

On 8/7/2017 3:50 PM, Rod Smallwood via cctalk wrote:




On 07/08/2017 22:52, Ian S. King via cctalk wrote:

On Mon, Aug 7, 2017 at 2:40 PM, Pete Turnbull via cctalk <
cctalk@classiccmp.org> wrote:


On 07/08/2017 18:37, Rod Smallwood via cctalk wrote:

So to-morrow connect up a terminal that will do 110 baud and try an 
echo

test.

Next part is interesting. There should be a way to fake a reader / 
punch

and feed in tape images.


There is.  Look on Kevin McQuiggin's site:
http://highgate.comm.sfu.ca/pdp8/

In the section called "Software", about 1/3 of the way down, look for
send.c or better still new-send.c (I call it rsend, on my system).  You
might also find rim.c and the BIN loader useful.

They're also on my webpage, with the corresponding manpages:
http://www.dunnington.info/public/PDP-8/

That's the easiest place to get the manpages for rim.c, send.c, 
rsend.c.

Here's the gist (top parts of the manpages):

rim - create RIM-format file from ASCII addr/instr
   rim is a very simple converter.  It reads in a file containing two
   columns of ASCII digits; the first column is a list of addresses (in
   octal) and the second is a list of machine instructions (also 
octal).

   Output is a file suitable to feed to the RIM loader on a PDP-8.

send, rsend - send a file in RIM or BIN format to a PDP-8
   send and rsend are utilities to transmit a RIM format or BIN format
   file from a UNIX (or other) host to a PDP-8 over a serial line.  The
   PDP-8 should be running the RIM loader routine prior to starting
   either of these programs.
   Input should be a file in RIM format or BIN format.  Output goes to
   the host serial port, which should be connected via appropriate 
cable

   to the PDP-8.
   send is a simple version, with built-in serial port settings and a
   fixed delay between characters.  rsend is more sophisticated; it can
   be controlled by command-line options or environment variables, and
   can accept input on stdin.

On a Unix (or Linux etc) machine you can pipe the output from rim to
rsend, and if you're using papertape images (of which there are load 
on the

net), rsend can strip the headers for you.

--
Pete
Pete Turnbull


Once upon a time I wrote a Python program to stand in for an ASR-33,
providing both a terminal session and a papertape image reader/punch.
N.B.: much PDP-8 software likes 7E1, but PTR/PTP is 8N1.  ISTR that even
when I fiddled with SLU settings, I couldn't get away from 7E1 for 
some of

the diagnostics.  Of course, I've slept since then.  -- Ian


Thank you that's interesting.
So far to-day I hooked up a three wire RS232 connection to an old 
Compaq notebook and ran msk315 (kermit)

Next SET BAUD 110
Then toggle in the print test on the 8/e.
Yup prints the character set on the notebook
Then echo test - nope.
The M8650 probably needs DTR or whatever.
Three wires was a bit cheeky I guess
In the hardware docs for the 8/e there's a load of info about the 8650.
I'll go read that.


Three wires should be enough, no DTR necessary.  Double-check your 
wiring and the jumpering on the M8650.




One other thing - I have a working TU58.
The two cassette drives in a box type with serial interface.
Now the pdp-8/e DECTapes were also called TU58.


The typical DECtapes used with the PDP-8 were TU56's, a completely 
different (and much more rare) beast.



The M8650 is on the list of what you can connect it to.
So does the one substitute for the other and raise the possibility of 
booting from tape?


No, they're not substitutes.  I'm not aware of any PDP-8 systems booting 
and running from a TU58, but I suppose it's not impossible. Mostly the 
problem with the TU58 at this point is that (a) the capstan rollers in 
your drives are most likely tar, and (b) the rubber parts in the tape 
itself have done the same, and (c) the tape itself probably isn't in 
great shape either.


- Josh



Rod

Re: pdp-8/e restoration.

[Rod Smallwood via cctalk]

On 07/08/2017 22:52, Ian S. King via cctalk wrote:

On Mon, Aug 7, 2017 at 2:40 PM, Pete Turnbull via cctalk <
cctalk@classiccmp.org> wrote:


On 07/08/2017 18:37, Rod Smallwood via cctalk wrote:

So to-morrow connect up a terminal that will do 110 baud and try an echo

test.

Next part is interesting. There should be a way to fake a reader / punch
and feed in tape images.


There is.  Look on Kevin McQuiggin's site:
http://highgate.comm.sfu.ca/pdp8/

In the section called "Software", about 1/3 of the way down, look for
send.c or better still new-send.c (I call it rsend, on my system).  You
might also find rim.c and the BIN loader useful.

They're also on my webpage, with the corresponding manpages:
http://www.dunnington.info/public/PDP-8/

That's the easiest place to get the manpages for rim.c, send.c, rsend.c.
Here's the gist (top parts of the manpages):

rim - create RIM-format file from ASCII addr/instr
   rim is a very simple converter.  It reads in a file containing two
   columns of ASCII digits; the first column is a list of addresses (in
   octal) and the second is a list of machine instructions (also octal).
   Output is a file suitable to feed to the RIM loader on a PDP-8.

send, rsend - send a file in RIM or BIN format to a PDP-8
   send and rsend are utilities to transmit a RIM format or BIN format
   file from a UNIX (or other) host to a PDP-8 over a serial line.  The
   PDP-8 should be running the RIM loader routine prior to starting
   either of these programs.
   Input should be a file in RIM format or BIN format.  Output goes to
   the host serial port, which should be connected via appropriate cable
   to the PDP-8.
   send is a simple version, with built-in serial port settings and a
   fixed delay between characters.  rsend is more sophisticated; it can
   be controlled by command-line options or environment variables, and
   can accept input on stdin.

On a Unix (or Linux etc) machine you can pipe the output from rim to
rsend, and if you're using papertape images (of which there are load on the
net), rsend can strip the headers for you.

--
Pete
Pete Turnbull


Once upon a time I wrote a Python program to stand in for an ASR-33,
providing both a terminal session and a papertape image reader/punch.
N.B.: much PDP-8 software likes 7E1, but PTR/PTP is 8N1.  ISTR that even
when I fiddled with SLU settings, I couldn't get away from 7E1 for some of
the diagnostics.  Of course, I've slept since then.  -- Ian


Thank you that's interesting.
So far to-day I hooked up a three wire RS232 connection to an old Compaq 
notebook and ran msk315 (kermit)

Next SET BAUD 110
Then toggle in the print test on the 8/e.
Yup prints the character set on the notebook
Then echo test - nope.
The M8650 probably needs DTR or whatever.
Three wires was a bit cheeky I guess
In the hardware docs for the 8/e there's a load of info about the 8650.
I'll go read that.

One other thing - I have a working TU58.
The two cassette drives in a box type with serial interface.
Now the pdp-8/e DECTapes were also called TU58.
The M8650 is on the list of what you can connect it to.
So does the one substitute for the other and raise the possibility of 
booting from tape?


Rod

--
Wanted one pdp-8/i rocker switch leaver to copy.

Re: pdp-8/e restoration.

[Ian S. King via cctalk]

On Mon, Aug 7, 2017 at 2:40 PM, Pete Turnbull via cctalk <
cctalk@classiccmp.org> wrote:

> On 07/08/2017 18:37, Rod Smallwood via cctalk wrote:
>
> So to-morrow connect up a terminal that will do 110 baud and try an echo
>> test.
>>
>> Next part is interesting. There should be a way to fake a reader / punch
>> and feed in tape images.
>>
>
> There is.  Look on Kevin McQuiggin's site:
> http://highgate.comm.sfu.ca/pdp8/
>
> In the section called "Software", about 1/3 of the way down, look for
> send.c or better still new-send.c (I call it rsend, on my system).  You
> might also find rim.c and the BIN loader useful.
>
> They're also on my webpage, with the corresponding manpages:
> http://www.dunnington.info/public/PDP-8/
>
> That's the easiest place to get the manpages for rim.c, send.c, rsend.c.
> Here's the gist (top parts of the manpages):
>
> rim - create RIM-format file from ASCII addr/instr
>   rim is a very simple converter.  It reads in a file containing two
>   columns of ASCII digits; the first column is a list of addresses (in
>   octal) and the second is a list of machine instructions (also octal).
>   Output is a file suitable to feed to the RIM loader on a PDP-8.
>
> send, rsend - send a file in RIM or BIN format to a PDP-8
>   send and rsend are utilities to transmit a RIM format or BIN format
>   file from a UNIX (or other) host to a PDP-8 over a serial line.  The
>   PDP-8 should be running the RIM loader routine prior to starting
>   either of these programs.
>   Input should be a file in RIM format or BIN format.  Output goes to
>   the host serial port, which should be connected via appropriate cable
>   to the PDP-8.
>   send is a simple version, with built-in serial port settings and a
>   fixed delay between characters.  rsend is more sophisticated; it can
>   be controlled by command-line options or environment variables, and
>   can accept input on stdin.
>
> On a Unix (or Linux etc) machine you can pipe the output from rim to
> rsend, and if you're using papertape images (of which there are load on the
> net), rsend can strip the headers for you.
>
> --
> Pete
> Pete Turnbull
>

Once upon a time I wrote a Python program to stand in for an ASR-33,
providing both a terminal session and a papertape image reader/punch.
N.B.: much PDP-8 software likes 7E1, but PTR/PTP is 8N1.  ISTR that even
when I fiddled with SLU settings, I couldn't get away from 7E1 for some of
the diagnostics.  Of course, I've slept since then.  -- Ian

-- 
Ian S. King, MSIS, MSCS, Ph.D. Candidate
The Information School 
Dissertation: "Why the Conversation Mattered: Constructing a Sociotechnical
Narrative Through a Design Lens

Principal Investigator, "Reflections on Early Computing and Social Change",
UW IRB #42619

Archivist, Voices From the Rwanda Tribunal 
Value Sensitive Design Research Lab 

University of Washington

There is an old Vulcan saying: "Only Nixon could go to China."

Re: pdp-8/e restoration.

[Pete Turnbull via cctalk]

On 07/08/2017 18:37, Rod Smallwood via cctalk wrote:

So to-morrow connect up a terminal that will do 110 baud and try an echo 
test.


Next part is interesting. There should be a way to fake a reader / punch 
and feed in tape images.


There is.  Look on Kevin McQuiggin's site:
http://highgate.comm.sfu.ca/pdp8/

In the section called "Software", about 1/3 of the way down, look for 
send.c or better still new-send.c (I call it rsend, on my system).  You 
might also find rim.c and the BIN loader useful.


They're also on my webpage, with the corresponding manpages:
http://www.dunnington.info/public/PDP-8/

That's the easiest place to get the manpages for rim.c, send.c, rsend.c. 
Here's the gist (top parts of the manpages):


rim - create RIM-format file from ASCII addr/instr
  rim is a very simple converter.  It reads in a file containing two
  columns of ASCII digits; the first column is a list of addresses (in
  octal) and the second is a list of machine instructions (also octal).
  Output is a file suitable to feed to the RIM loader on a PDP-8.

send, rsend - send a file in RIM or BIN format to a PDP-8
  send and rsend are utilities to transmit a RIM format or BIN format
  file from a UNIX (or other) host to a PDP-8 over a serial line.  The
  PDP-8 should be running the RIM loader routine prior to starting
  either of these programs.
  Input should be a file in RIM format or BIN format.  Output goes to
  the host serial port, which should be connected via appropriate cable
  to the PDP-8.
  send is a simple version, with built-in serial port settings and a
  fixed delay between characters.  rsend is more sophisticated; it can
  be controlled by command-line options or environment variables, and
  can accept input on stdin.

On a Unix (or Linux etc) machine you can pipe the output from rim to 
rsend, and if you're using papertape images (of which there are load on 
the net), rsend can strip the headers for you.


--
Pete
Pete Turnbull

Re: Convex documentation online (C220 arrived)

[Mark J. Blair via cctalk]

> On Aug 7, 2017, at 12:13 AM, Camiel Vanderhoeven 
>  wrote:
> 
> That would have been the CPU cabinet for the C240 (which is twice as wide
> as the C220¹s CPU cabinet. The C240¹s CPU consumes - i.e. converts to heat
> - about 20 kilowatts of power, so that would indeed have created a hotspot
> in a computer room. It will surely create a hotspot in my barn!


Ok, that makes sense. All I remember is that from the rear side of the cabinet, 
it was behind the exhaust vents at the lower right corner that was the optimal 
place in the computer room to curl up in a fetal position at 6AM, when the main 
building A/C came on and the computer room temperature plummeted, right about 
when the metabolism of an exhausted college student working a graveyard 
computer operator shift was at minimum. But it was all worth it for a key to 
the computer room, and unlimited root access on Sun workstations when most 
students were lucky to get a small quota on the heavily-loaded Sequent Symmetry 
series machine. Oh, and they paid me, too. :)

That C240 also had the nicest 9-track drive in the room. Most of my tape mounts 
were on the TU77 next to the VAX-11/780 (or maybe 785?), but I always liked 
working with that drive on the C240. I no longer recall which company 
manufactured its transport, but it was really fast.

> 
> I¹m getting a C240 two weeks from now. Between the C220, the C240, and the
> two C1s, I hope to be able to  get at least one Convex up and running
> ConvexOS.

That is really cool, and it sounds like you have all of your barn heating needs 
sorted out, too!


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

Re: Convex documentation online (C220 arrived)

[Dennis Boone via cctalk]

 > That would have been the CPU cabinet for the C240 (which is twice as
 > wide as the C220^1s CPU cabinet. The C240^1s CPU consumes -
 > i.e. converts to heat - about 20 kilowatts of power, so that would
 > indeed have created a hotspot in a computer room. It will surely
 > create a hotspot in my barn!

Behind the C240 CPU cabinet was certainly the warmest area in our data
center.  The BBN Butterfly machine was not _too_ far behind, but the
vaxen and IBM machines weren't even close.

De

Re: Convex documentation online (C220 arrived)

[Camiel Vanderhoeven via cctalk]

On 8/6/17, 7:31 PM, "cctech on behalf of Mark J. Blair via cctech"
 wrote:


>Wow! I fondly remember the air exhaust from the power supply cabinet of
>the Convex C240 as being the warmest spot in the UCI computer room at
>6AM, when the main Computer Science building A/C turned on and the
>computer room temperature plummeted. Maybe I should finally learn how to
>use one for its designed purpose? :)

That would have been the CPU cabinet for the C240 (which is twice as wide
as the C220¹s CPU cabinet. The C240¹s CPU consumes - i.e. converts to heat
- about 20 kilowatts of power, so that would indeed have created a hotspot
in a computer room. It will surely create a hotspot in my barn!

I¹m getting a C240 two weeks from now. Between the C220, the C240, and the
two C1s, I hope to be able to  get at least one Convex up and running
ConvexOS.

Camiel

Re: VCF?

[dwight via cctalk]

It's over now.

I came away with about 3 times as much stuff as I when with.

I've not seen any photos posted yet.

For those that do post photos I recommend adding

xiiw as a single word. It will make searches easier.

Dwight



From: cctalk  on behalf of Ed via cctalk 

Sent: Sunday, August 6, 2017 2:06:48 PM
To: ci...@xenosoft.com; cctalk@classiccmp.org
Subject: Re: VCF?

Ol'  Fred -  Best of  luck  with surgery
Prayers be  with you...

Ed#


In a message dated 8/6/2017 11:27:03 A.M. US Mountain Standard Time,
cctalk@classiccmp.org writes:

How is  VCF going?


I was going to take a dozen boxes of books, a couple of  computers, and
some miscellaneous.
My health got in the way.
I'm  getting prostate surgery (ANOTHER TURP) on Thursday,
I just don't feel up  to packing loading, or even driving an hour each
way.


--
Grumpy Ol' Fred   ci...@xenosoft.com

Re: pdp-8/e restoration.

[Rod Smallwood via cctalk]

On 07/08/2017 17:05, Philipp Hachtmann via cctalk wrote:

On 04.08.2017 09:24, Rod Smallwood via cctalk wrote:

Hi List

Hi Rod!

  I looks like I have at last got a KK8-E CPU set to continue 
getting my 8/e back running again.

It looks that you have one more set stored in my facility in Hannover!!!
I became feeling more and more bad about that. Then I forgot it again. 
Then I felt even more bad by not remembering WHOSE boards those are 
(because there is no "Rod Smallwood" written nowhere on the packet).

Now I have connected that again!

The system has a working rebuilt PSU with all of the caps reformed or 
replaced. Voltages are good.

Wow, I never did that. I always made a smoke test.


There's 16k of core at the back with a terminator at the end.

Not bad.

Power up and all the lamps come on either bright or dim (off) except 
the RUN light.

Sounds not so wrong.

2. Are there any tests like resistance I can do on the CPU board set 
before inserting them in the correct front slots?
There are no "correct" slots. Not for *any* of the boards. You can mix 
it up completely. Even the front panel could be omitted, doubled, or 
put into an expansion box.
BUT.. There actually IS a DEC recommended order, yes... And having the 
terminator board somehow at the end of the Omnibus seems to be a good 
idea.


3. In the event the CPU set does not even do a simple write to and 
read from memory. Where do I start to look?
At the schematics? Front panel (!), timing generator, major state 
registers.


The DEC stuff was designed quite wrong-insertion resistant. But:
There is just one MAJOR fault you HAVE TO AVOID: NEVER NEVER NEVER 
plug in the middle board of an RK8E controller upside down!!


I did it. Once. It leads to impressive fireworks on many boards.

Regards
Philipp


Its now running just fine.
Count test runs.
The second set of 4k core is in and checks out.
Async. board has just gone in and is running.
I'm getting output RS232 on my BOB  when the print test is toggled in 
and run.
So to-morrow connect up a terminal that will do 110 baud and try an echo 
test.


Next part is interesting. There should be a way to fake a reader / punch 
and feed in tape images.


Rod

--
Wanted one pdp-8/i rocker switch leaver to copy.

Re: Visual 1050

[Ian S. King via cctalk]

On Mon, Aug 7, 2017 at 9:06 AM, william degnan via cctalk <
cctalk@classiccmp.org> wrote:

> >
> > >
> > > dumping the firmware and character generator would be a good thing to
> do
> > as well
> > >
> > >
> > There are milti versions of these I believe.
> >
> > "MULTI" not milti :-)
>

Gary, if you're not in too much of a hurry I'd be interested in driving up
to Bellingham and picking it up.  :-)

-- 
Ian S. King, MSIS, MSCS, Ph.D. Candidate
The Information School 
Dissertation: "Why the Conversation Mattered: Constructing a Sociotechnical
Narrative Through a Design Lens

Principal Investigator, "Reflections on Early Computing and Social Change",
UW IRB #42619

Archivist, Voices From the Rwanda Tribunal 
Value Sensitive Design Research Lab 

University of Washington

There is an old Vulcan saying: "Only Nixon could go to China."

Re: Visual 1050

[william degnan via cctalk]

>
> >
> > dumping the firmware and character generator would be a good thing to do
> as well
> >
> >
> There are milti versions of these I believe.
>
> "MULTI" not milti :-)

Re: pdp-8/e restoration.

[Philipp Hachtmann via cctalk]

On 04.08.2017 09:24, Rod Smallwood via cctalk wrote:

Hi List

Hi Rod!

  I looks like I have at last got a KK8-E CPU set to continue 
getting my 8/e back running again.

It looks that you have one more set stored in my facility in Hannover!!!
I became feeling more and more bad about that. Then I forgot it again. 
Then I felt even more bad by not remembering WHOSE boards those are 
(because there is no "Rod Smallwood" written nowhere on the packet).

Now I have connected that again!

The system has a working rebuilt PSU with all of the caps reformed or 
replaced. Voltages are good.

Wow, I never did that. I always made a smoke test.


There's 16k of core at the back with a terminator at the end.

Not bad.

Power up and all the lamps come on either bright or dim (off) except the 
RUN light.

Sounds not so wrong.

2. Are there any tests like resistance I can do on the CPU board set 
before inserting them in the correct front slots?
There are no "correct" slots. Not for *any* of the boards. You can mix 
it up completely. Even the front panel could be omitted, doubled, or put 
into an expansion box.
BUT.. There actually IS a DEC recommended order, yes... And having the 
terminator board somehow at the end of the Omnibus seems to be a good idea.


3. In the event the CPU set does not even do a simple write to and read 
from memory. Where do I start to look?

At the schematics? Front panel (!), timing generator, major state registers.

The DEC stuff was designed quite wrong-insertion resistant. But:
There is just one MAJOR fault you HAVE TO AVOID: NEVER NEVER NEVER plug 
in the middle board of an RK8E controller upside down!!


I did it. Once. It leads to impressive fireworks on many boards.

Regards
Philipp

Re: pdp-8/e restoration.

[Philipp Hachtmann via cctalk]

On 04.08.2017 17:23, Doug Ingraham via cctalk wrote:

On Fri, Aug 4, 2017 at 1:24 AM, Rod Smallwood via cctalk <
cctalk@classiccmp.org> wrote:


1. Should the run light glow dimly?



Without looking at the schematics I can't tell you if they bothered to put
the resistor in there to make
it glow dimly but I can tell you that it isn't necessary for the run lamp.
The reason to make it glow
dimly when off is to reduce the filament thermal shock when turning on and
off.  This makes the bulbs
last a lot longer.  The run lamp does not flicker in operation so not
necessary on that one.


At least for the "normal" bulbs, the resistor is there. I once refitted 
a whole front panel with bulbs and resistors (which have to be removed 
when using anything LED related).

Re: Visual 1050

[william degnan via cctalk]

On Aug 7, 2017 11:55 AM, "Al Kossow via cctalk" 
wrote:
>
>
>
> On 8/7/17 7:08 AM, william degnan via cctalk wrote:
>
> > I agree.  I keep meaning to archive my software
>
>
> dumping the firmware and character generator would be a good thing to do
as well
>
>
There are milti versions of these I believe.

Re: Visual 1050

[Al Kossow via cctalk]

On 8/7/17 7:08 AM, william degnan via cctalk wrote:

> I agree.  I keep meaning to archive my software


dumping the firmware and character generator would be a good thing to do as well

Re: Visual 1050

[william degnan via cctalk]

On Mon, Aug 7, 2017 at 8:33 AM, allison via cctalk 
wrote:

>
>
> On 8/7/17 1:43 AM, Chuck Guzis via cctalk wrote:
>
>> On 08/06/2017 04:16 PM, Gary McGill via cctalk wrote:
>>
>>> I have an Visual 1050 computer (CPM based) with screen and keyboard.
>>> Probably works but I have not tried it yet.  Will likely uncover boot
>>> disks, and other software.
>>>
>>> Anyone interested to pay shipping from Bellingham, WA?
>>>
>>>
>> Gary, there's a CP/M collector's community over at vcfed.org.  You might
>> want to try posting on the forum over there.
>>
>> --Chuck
>>
> As someone that has three of them with hard disk its nearly the last word
> on
> Z80 CP/M systems with the 6502 doing terminal and graphics.  Worth
> collecting.
>
> Allison
>


I agree.  I keep meaning to archive my software, need to attach a quad
density drive to my archiving station.
http://vintagecomputer.net/visualtechnology/1050/

Re: Visual 1050

[allison via cctalk]

On 8/7/17 1:43 AM, Chuck Guzis via cctalk wrote:

On 08/06/2017 04:16 PM, Gary McGill via cctalk wrote:

I have an Visual 1050 computer (CPM based) with screen and keyboard.
Probably works but I have not tried it yet.  Will likely uncover boot
disks, and other software.

Anyone interested to pay shipping from Bellingham, WA?



Gary, there's a CP/M collector's community over at vcfed.org.  You might
want to try posting on the forum over there.

--Chuck
As someone that has three of them with hard disk its nearly the last 
word on
Z80 CP/M systems with the 6502 doing terminal and graphics.  Worth 
collecting.


Allison

RE: Sperry UTS 40 on Ebay - Statesboro, Georgia (part of Operator's Guide FFS)

[Electronics Plus via cctalk]

I have the keyboard for a UTS-40 here.
If you get a terminal that has been shipped, BEFORE you plug it in, take off
the back cover and examine the connectors.
These are not screwed together in the back; the circuit boards just press
together and will come apart at the back corner if the monitor flexes at
all.

Cindy


-Original Message-
From: cctalk [mailto:cctalk-boun...@classiccmp.org] On Behalf Of Tapley,
Mark via cctalk
Sent: Sunday, August 06, 2017 4:17 PM
To: General Discussion: On-Topic and Off-Topic Posts
Subject: Re: Sperry UTS 40 on Ebay - Statesboro, Georgia (part of Operator's
Guide FFS)

All,
in one of those spectacular coincidences, my excavations today
turned up a blue brad binder with 1 page of handwritten notes and
photocopies of pages 20-1 through 20-8 of the Sperry UTS 40-81 Operator's
guide (in addition to the other things I'm listing). 
Terms same as in my other emails, Al K. gets priority but anyone
else gets it for the cost of shipping. 
- Mark
210-522-6025 office
210-379-4635cell

Re: RL drive bulkhead connector

[Ulrich Tagge via cctalk]

Each drive has this adapter internally at the flat ribbon cable, so if 
you have a spare drive you could think about using them.
I have done this also, but my drive was damaged by water, so it was ok 
for me to cannibalize the adapter.
It's also possible to go direct from the controller to the drive with a 
flat ribbon cable, but I have not done this, and think that the original 
cable is shielded, ... .


Many Greetings
Ulrich