The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: brad@heeltoe.com (Brad Parker)
Subject: [Unix-jun72] more corrections
Date: Fri, 02 May 2008 06:24:44 -0400	[thread overview]
Message-ID: <11428.1209723884@mini> (raw)
In-Reply-To: <Pine.BSI.4.64.0805011927100.20114@malasada.lava.net>


Tim Newsham wrote:
>
>How can I get the modified simh? 

Here's a diff against v36 and a tar of my working directory:

http://www.unlambda.com/download/pdp11/unix-jun72/KE.diff
http://www.unlambda.com/download/pdp11/unix-jun72/simhv36-1-ke.tar.gz

>Also what configuration are you using?  I have this so far:
>
>   set tc enabled
>   att tc tape.dt
>   set rk3 enabled
>   att rk3 rk0.dsk
>   set rf enabled
>   att rf rf0.dsk
>   set cpu 11/20
>   set cpu 32K

I'm using this:

set cpu 11/20
set hk disabled
set rha disabled
set tm disabled
set rx disabled
set rl disabled
set tq disabled
set rk3 enabled
att rk3 rk3.dsk
set tc enabled
set rf enabled
set ke enabled
set cpu 32K
load loadfile
d pc 400
set cpu history=1000
attach rf rf0.dsk

I forgot to include my a.out->loadfile conversion program.  I'll check it
in to svn.

>Have you gotten far enough that it writes out the full primitive
>root on rf0 so that you can reboot and get init going?

No - it writes a bunch of blocks to rf0 but no directories.

The 'zero i list' appears to work, and the code to init i-node 41-47 runs
but nothing gets written.  Or if it does the wrong thing gets written.  not
sure why.

To debug I sprinkle "halt"'s in the code and then do "show cpu history"
to see what happened.

As a sanity check I also do 'e 0-40' and 'e 400-440' to make sure
location 34 (iot vector) is filled in and the code at 400 is correct (it
loads the sp with 60000).

I might turn on some RF debug to see exactly what gets written when.

-brad




  parent reply	other threads:[~2008-05-02 10:24 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
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   ` Brad Parker [this message]
2008-05-01 17:44 [Unix-jun72] more corrections 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=11428.1209723884@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).