The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: brad@heeltoe.com (Brad Parker)
Subject: [Unix-jun72] more corrections
Date: Thu, 01 May 2008 13:19:13 -0400	[thread overview]
Message-ID: <30873.1209662353@mini> (raw)
In-Reply-To: <Pine.BSI.4.64.0805010657460.20990@malasada.lava.net>


Tim Newsham wrote:
>> I made some more minor corrections; turns out the commands in e00-01
>> around "4;4" are wrong, those lines are needed or the IOT dispatch
>> vector ends up in the wrong place.
>>
>> I suspect, in the end, most of the "hand written" corrections should
>> ignored.
>
>I'm suspecting the opposite.. I went through all of the comments in
>notes.txt about hand written corrections and read through the code to
>see if they make sense or not and it seems like all of the corrections
>did make sense in the code and the original code that they replaced
>did not.  I updated the code to reflect this and added comments to
>the notes file.

Ok, I may well be confused.

Before I took the comments the IOT vector was zero.  After I removed
them the IOT vector (34) was correct.

Perhaps the code wants to be loaded at 014 instead of 0.
I put the comments back in - I'll try changing where I load.

>btw, there are still a bunch of unresolved symbols in the low address
>vector tables..

I thought only fpsym was undefined in those vectors.

>> I had to add KE11A support to simh;  I mostly copied the code from
>> apout.
>
>This discussion of hardware is making me wonder -- does this nail down
>the hardware?  The 1ed manuals mention tht they ran on a 24kbyte
>pdp 11/20, but that they were eying an 11/45.  My reading of the code
>was making me lean towards the original 11/20 configuration, but it
>sounds like some of these features might be present in the 11/40 or
>11/45?

I sure looks like they used an 11/20 with a KE11A board.

>speaking of modifying simh, we may have to map one of the similar
>serial devices in at the dc11 address to support ttys.  simh doesn't
>support the DC-11, but when I asked on the simh mailing list someone
>mentioned that one of the existing devices is very similar with
>less support for modem control lines.

I can do that.  Are there docs on the DC-11?

-brad




  parent reply	other threads:[~2008-05-01 17:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-01 16:09 Brad Parker
2008-05-01 17:03 ` Tim Newsham
2008-05-01 17:10   ` Al Kossow
2008-05-01 17:19   ` Brad Parker [this message]
2008-05-01 17:10 ` Tim Newsham
2008-05-01 17:22   ` Brad Parker
     [not found]     ` <Pine.BSI.4.64.0805010726040.20990@malasada.lava.net>
2008-05-01 17:47       ` Brad Parker
2008-05-01 17:54         ` Tim Newsham
2008-05-01 18:15           ` Tim Newsham
2008-05-01 18:21             ` Tim Newsham
2008-05-01 18:34             ` Tim Newsham
2008-05-01 22:51               ` Warren Toomey
2008-05-01 23:31                 ` Tim Newsham
2008-05-01 19:02         ` John Cowan
2008-05-01 21:18           ` [Unix-jun72] 11/20 handbook Al Kossow
2008-05-01 23:09             ` Hellwig Geisse
2008-05-01 22:23         ` [Unix-jun72] Early a.out headers Warren Toomey
2008-05-01 22:28           ` Warren Toomey
2008-05-01 23:01           ` Al Kossow
     [not found] ` <Pine.BSI.4.64.0805011927100.20114@malasada.lava.net>
2008-05-02 10:24   ` [Unix-jun72] more corrections Brad Parker
2008-05-01 17:44 James A. Markevitch

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=30873.1209662353@mini \
    --to=brad@heeltoe.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).