Yep, I noticed that, but thought it was a idea you might want to explore and it?s simple
enough to do.
Without the full output from the ls command and how it was executed I was just throwing it
For instance, was the default dir where ls was run, the same dir as when the backgrounded
one was run.
That would make a difference if the filesystem was corrupt. In previous threads, there was
an issue getting the proper image onto the disk, there is the potential for corruption.
There is the assumption, since boards were being worked on, that the problem for a
software is probably due to said hardware, even though diags pass. With that assumption,
shouldn?t you try to eliminate different hardware pieces? I would try running something
that uses memory and doesn?t use disk to narrow the problem down.
Take care and good luck,
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986>
for Windows 10
From: Noel Chiappa <jnc at mercury.lcs.mit.edu>
Sent: Monday, February 4, 2019 12:43:09 PM
To: cctalk at classiccmp.org
Cc: jnc at mercury.lcs.mit.edu
Subject: RE: PDP-11/45 RSTS/E boot problem
From: Wayne S
it might be a wonky filesystem. ...
The corruption probably came because the entire disk was going bad.
This theory is contradicted by the fact (mentioned several times, including in
the message you were replying to) that doing a plain 'ls' bombs, but 'sleep
300 &; ls' works fine.