23 Apr
2013
23 Apr
'13
3:44 p.m.
On 23/04/13 1:34 PM, John Wilson wrote:
On Tue, Apr 23, 2013 at 08:58:43AM -0700, Bob
Armstrong wrote:
Is there a more recent upstream than this fork I had to make? The fixes
that this required were probably already done by somebody but this was
the most recent code I could get hold of at the time...
https://github.com/qu1j0t3/mopd
--Toby
Is this all stuff that's in the task header?
Looks that way.
The RSX system image .SYS
file (the one on disk, for booting with the hardware boot) is built without
a task header (the TKB /-HD option) and things like the loading and starting
addresses are assumed somehow. I was guessing that the .SYS files for MOP
download would be the same, but maybe I'm wrong.
Here's where I'm getting hazy. I wrote a MOP boot server a few years ago
for debugging PDP-11 network booting (last I checked, the "mopd" package
doesn't support booting PDP-11s) and my notes show that I was pulling those
four fields out of the .TSK header, which should mean that I figured out that
that's how DEC does it. But I can't think what my test case must have been
(the .SYS files I have are for DSRVA and DSRVB), unless it all came from
fiddling with DECnet/RSX's own MOP server.
Well it would be very easy to prove me wrong -- making a .TSK file with a
stand-alone "Hello world" program would only take a couple of minutes.
Or I can send you a FORTH .SYS image I was using for testing on DELQA and
DELUA, but it'll take longer to download so testing will get annoying
quickly unless it magically works on the first try.
John Wilson
D Bit