The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lothar.felten@gmx.net (lothar felten)
Subject: [pups] 2.11BSD disklabel-programm
Date: Sat, 26 Jan 2002 13:50:49 +0100	[thread overview]
Message-ID: <PKEKIKBJNMFKLFAMAKINAEGACBAA.lothar.felten@gmx.net> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2036 bytes --]

about the pdp-11/83:

swapping cpu and memoryboard does work, but
the performance stays the same:
none, because i still don´t have any system
by now. there is a small difference:
the run led stays off all the time, but the
system ODT works fine. i suppose this
is a problem of passing the signals, but this
is only a vague guess.
when i boot the TK50 2.11BSD tape, i can get
the disklabel program loaded.
it asks: Disk?
when i try to access the disks, the system
hangs. when i access rl(0,0) (RL02
disk drive0) the system just hangs, no
response. when i access ra(0,0) (RD54 disk
drive0) i get a "menu": d(isplay) D(efault)
m(odify) w(rite) q(uit)?
i can enter D, then it should write the
defaults to the disk. after this i get:
d(isplay) D(efault) m(odify) w(rite) q(uit)?
i enter d (to see what the program did), and
i get:
type:MSCP
disk:RD54
flags:
bytes/sector:512
sectors/track:17
tr
(it stops right after tr) i suppose the
program is asking the controller about
drive parameters, and that´s where it fails.
i can wait for hours, i´ll get no
response.
i can use all the menu, except d=display.
i thought that maybe one of the controlles is
broken and causes trouble on the
qbus (maybe the RL02 controller). is there a
way to check all this stuff?
i do have some "winchester" controllers for
PC/ISA, i could check the disks on
a linux pc, no problem, but i don´t want to
overwrite something "digital"-specific
that i could not restore. those RD54-disks
are regular ST506-mfm, right?
maybe i should "downsize" the system to the
basic elements i need to get it running
maybe there really is a bus problem.
i´d try this configuration:
mem - cpu - rqdx3 - tqk50 (top-bottom)
would this be ok?
or, instead of using RD54 disks, should i try
to use the rl02 as "pair" (one swap,
one systemdisk)?
i think step by step checking the hardware is
the only thing i can do to get the
pdp up and running.

have a nice weekend

-- lothar

btw: does anyone know a good book/link about
system-architecture, specially harvard-
architecture ?




             reply	other threads:[~2002-01-26 12:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-26 12:50 lothar felten [this message]
2002-01-26 17:39 ` jkunz
2002-01-28 21:38   ` Wilko Bulte
2002-01-29 18:34     ` emanuel stiebler
  -- strict thread matches above, loose matches on Subject: below --
2002-01-19 19:47 lothar felten
2002-01-19 21:35 ` jkunz
2002-01-20 14:57   ` Pete Turnbull
2002-01-20 17:45     ` Jochen Kunz
     [not found]       ` <jkunz@unixag-kl.fh-kl.de>
2002-01-20 18:31         ` Pete Turnbull
2002-01-19 11:43 lothar felten
2002-01-19 13:49 ` jkunz
     [not found] ` <lothar.felten@gmx.net>
2002-01-19 16:05   ` Pete Turnbull
2002-01-19 22:18   ` Pete Turnbull
2002-01-20 11:44     ` jkunz
2002-01-20 15:01       ` Pete Turnbull

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=PKEKIKBJNMFKLFAMAKINAEGACBAA.lothar.felten@gmx.net \
    --to=lothar.felten@gmx.net \
    /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).