The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: j.r.engdahl@adelphia.net (Jonathan Engdahl)
Subject: [pups] Re: PDP11 - RQDX1 standalone format utility? --> XXDP
Date: Sun, 23 Feb 2003 23:32:57 -0500	[thread overview]
Message-ID: <00cb01c2dbbd$ce8d64f0$8a00a8c0@arctura> (raw)
In-Reply-To: <3E593FD8.2090207@pacbell.net>

Now that I think of it,

> 000137
> 145702

is wrong too. Assuming that the program is relocatable (which in this case
it probably is not), and you simply loaded the entire file into memory, it
would be offset by the 16 byte header, so you would want to jump to 145722.

I think I will remove that patch at 20 altogether.

Did you know that the output from PDPXASM can be loaded to a barely
twitching PDP-11 via VTserver? I used PDPXASM to write scope loops for an
RX02 (DSD 4140) board I resurrected.

--
Jonathan Engdahl
http://users.safeaccess.com/engdahl

"The things which are seen are temporary,
 but the things which are not seen are eternal."  II Cor. 4:18


----- Original Message -----
From: "Michael Davidson" <michael_davidson@pacbell.net>
To: "Jonathan Engdahl" <j.r.engdahl at adelphia.net>
Cc: <cctech at classiccmp.org>; <pups at minnie.tuhs.org>
Sent: Sunday, February 23, 2003 4:40 PM
Subject: Re: [pups] Re: PDP11 - RQDX1 standalone format utility? --> XXDP


> Jonathan Engdahl wrote:
>
> >I documented the procedure to extract a program from XXDP and put a
header
> >on it so that you can boot it from VTserver or a UNIX disk. It has been a
> >long time since I did this to ZRQCH0, so I practiced on the program that
I
> >think Christos needs (ZRQBC1) and sent it to him.
> >
> >There's a lot I don't know about the a.out header, so if someone can
improve
> >my method, let me know.
> >
> >http://users.safeaccess.com/engdahl/xxdp.htm#hackXXDP
> >
> There isn't very much to know about the a.out header,
> and what you are doing looks OK although I would probably
> have set a_text to 160000 and left a_data and a_bss as 0.
>
> While I am not really familiar with the BSD boot code that
> vtserver uses when loading a program I am almost certain that
> it will use the entrypoint address in the a.out header and
> not just jump to address 0. (remember it's an actual program
> loader that understands a.out format, not just something that
> only knows how to load a boot block and jump to it)
>
> This is confirmed by the fact that the code you are patching
> into the image at address 0 is wrong if you want it to get
> you to the restart address.
>
> In your example you have:
>
> 000020/ 000167
> 000022/ 145702
>
> If this was loaded at address 0 in memory and the boot code
> jumped to address 0, you would end up at 145706 *not* 145702
> (of course, you might very well get lucky and still land on
> an instruction boundary, but you would have skipped the first
> 2 words of the restart code).
>
> If this code were really necessary (and I'm 99.99% sure that
> it isn't) you would want either:
>
> 000137
> 145702
>
> or:
>
> 000167
> 145676
>
>
>
>
>
> _______________________________________________
> PUPS mailing list
> PUPS at minnie.tuhs.org
> http://minnie.tuhs.org/mailman/listinfo/pups




  parent reply	other threads:[~2003-02-24  4:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <001201c2d98f$b4ff34d0$77b95b8b@ics.forth.gr>
2003-02-23  0:59 ` Jonathan Engdahl
2003-02-23  6:22   ` Gregg C Levine
2003-02-23 17:15     ` Jonathan Engdahl
2003-02-23 20:31       ` Gregg C Levine
2003-02-23 20:31       ` Gregg C Levine
2003-02-23 21:40   ` Michael Davidson
2003-02-24  2:41     ` Jonathan Engdahl
2003-02-24  4:32     ` Jonathan Engdahl [this message]
2003-02-24  5:10       ` Warren Toomey
2003-02-24  5:40       ` Gregg C Levine
2003-02-24  6:34         ` Jonathan Engdahl
2003-02-24  7:24           ` DEC Compatible boards was " Gregg C Levine
2003-02-23 22:26 Fred N. van Kempen

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='00cb01c2dbbd$ce8d64f0$8a00a8c0@arctura' \
    --to=j.r.engdahl@adelphia.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).