More testing this evening.
Drive 1 ran for 8 ten-minute AJRLIA read-write passes before I stopped it,
with a single error flagged during pass 6:
WD1 0235
WD2
ER 4001
CB 1117
indicating a Data CRC error and a Read header without CRC command. Not
completely unexpected, a lot of data is bein
Recall that the other day, I was seeing this on running AJRLHA.DG:
STATE NOT 5 AFTER SEEK WITH 0 DIFFERENCE (this error and register dump
prints twice in succession. State 5 = Lock-on, keeping on track).
WD1 0317 (lower head, heads not out, spin-down)
WD2 0204 (write data error, write gate error)
On 09/13/2015 02:52 AM, Henk Gooijen wrote:
-Oorspronkelijk bericht- From: Charles
Sent: Sunday, September 13, 2015 12:36 AM
To: cctalk digest
Subject: Re: Even more PDP-8/A weirdness (was: Re: PDP-8
diagnostics SR settings?)
As previously posted, reseating the boot ROMs in their
-Oorspronkelijk bericht-
From: Charles
Sent: Sunday, September 13, 2015 12:36 AM
To: cctalk digest
Subject: Re: Even more PDP-8/A weirdness (was: Re: PDP-8 diagnostics SR
settings?)
As previously posted, reseating the boot ROMs in their sockets cured the
corrupted boot loader issue
At 12:31 PM 9/12/2015, Charles wrote:
Update: The first thing I tried was removing and reseating the boot
ROMs (465A2/469A2), since they did not use good machine-tooled sockets.
Now the boot loader performs normally, no incorrect locations, and
OS/8 boots from Drive 0 whether using the boot key
As previously posted, reseating the boot ROMs in their sockets cured the
corrupted boot loader issue. Got lucky there :)
In my system there are two RL02 drives. I will call them "Top" and "Bottom"
here, after their physical locations.
I put the OS/8 pack that had been acting strangely in the bo
On 9/12/2015 10:08 AM, Charles wrote:
So, either something is corrupting the bus, or the memory is bad.
Correct me if I'm wrong, but if I got this right, you wrote the boot
code by hand into memory, single-stepped it, and after a while, you had
bad contents in memory.
Now, execution here woul
So, either something is corrupting the bus, or the memory is bad.
Correct me if I'm wrong, but if I got this right, you wrote the boot
code by hand into memory, single-stepped it, and after a while, you had
bad contents in memory.
Now, execution here would only be reading from memory, and not wr
On 2015-09-12 17:23, Charles wrote:
Since the computer doesn't mind doing boring, repetitive tasks, I set
the 11/23+ to yet again remaking the bootable RL02 pack (3 hrs at 9600
baud while I did other things).
Plunked it in (without the programmer's panel connected), hit the boot
switch on the lim
Update: The first thing I tried was removing and reseating the boot ROMs
(465A2/469A2), since they did not use good machine-tooled sockets.
Now the boot loader performs normally, no incorrect locations, and OS/8
boots from Drive 0 whether using the boot key or manual start at 0001.
Great!
So o
Since the computer doesn't mind doing boring, repetitive tasks, I set the
11/23+ to yet again remaking the bootable RL02 pack (3 hrs at 9600 baud
while I did other things).
Plunked it in (without the programmer's panel connected), hit the boot
switch on the limited function panel, and it fired r
11 matches
Mail list logo
