The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: downing.nick@gmail.com (Nick Downing)
Subject: [TUHS] 2.9bsd on 11/45 restoration
Date: Mon, 6 Oct 2014 08:46:12 +1100	[thread overview]
Message-ID: <CAH1jEzYWGhX6duL8dJsxONR-GfNZG2jhMk7fDjs6c8jE1yonRA@mail.gmail.com> (raw)
In-Reply-To: <5431B1B7.1040303@update.uu.se>

I had an 11/70 service manual as an ebook at one stage, it had full
schematics etc, you also have access to various simulators to help you
understand the programming interface so i can't see what other info you
would need for your restoration, maybe you'd need help jerry rigging some
setup to get an initial tape written to get u started?

If you have any questions about the schematics or electrical
troubleshooting I'm happy to help although I have never owned a physical
pdp11... concepts are the same as any more modern system.

cheers, Nick
On 06/10/2014 8:08 AM, "Johnny Billquist" <bqt at update.uu.se> wrote:

> On 2014-10-05 03:00, Dave Horsfall<dave at horsfall.org> wrote:
>
>>
>> On Sat, 4 Oct 2014, Noel Chiappa wrote:
>>
>>  >Anyone seriously working on bringing old hardware back to life needs to
>>> >get in touch with the Classic Computer Talk list:
>>>
>> Is John Dodson on this list?  He has an 11/70 in his house.
>>
>
> No idea. I occasionally scan cctalk, but most of the time don't bother.
> Too much noise and irrelevant or ignorant posts. However, unfortunately I
> don't have any better suggestions where to go if you are trying to restore
> old hardware and don't have enough knowledge.
>
> And yes, I keep lots of different PDP-8, PDP-11 and VAXen running,
> including 11/70 systems.
>
>         Johnny
>
> --
> Johnny Billquist                  || "I'm on a bus
>                                   ||  on a psychedelic trip
> email: bqt at softjar.se             ||  Reading murder books
> pdp is alive!                     ||  tryin' to stay hip" - B. Idol
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20141006/61a55a5d/attachment.html>


  reply	other threads:[~2014-10-05 21:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1412470802.24227.tuhs@minnie.tuhs.org>
2014-10-05 21:01 ` Johnny Billquist
2014-10-05 21:46   ` Nick Downing [this message]
2014-10-05 22:49     ` Johnny Billquist
     [not found] <mailman.1.1412643601.13349.tuhs@minnie.tuhs.org>
2014-10-07 18:15 ` Johnny Billquist
2014-10-06  1:36 Norman Wilson
  -- strict thread matches above, loose matches on Subject: below --
2014-10-04 12:19 Noel Chiappa
2014-10-04 20:26 ` Dave Horsfall
2014-10-03  3:36 Warren Toomey
2014-10-04  8:06 ` random832
     [not found]   ` <CAHYQbfBaPwsA0ps3FS9LKdeLKSjYCxTrYtPc5Ct4AV0Sgs1S0w@mail.gmail.com>
2014-10-05  3:26     ` random832
     [not found]       ` <CAHYQbfC3t-5ukH-xM1QL5nq21DiC2z3i5bcPWcmgoQK4TZDkbA@mail.gmail.com>
     [not found]         ` <1412538525.277114.175397473.12347280@webmail.messagingengine.com>
2014-10-05 19:49           ` random832
2014-10-07  8:54 ` Peter Jeremy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAH1jEzYWGhX6duL8dJsxONR-GfNZG2jhMk7fDjs6c8jE1yonRA@mail.gmail.com \
    --to=downing.nick@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).