30 Oct
2015
30 Oct
'15
7:42 a.m.
Hi all,
I'm trying to set up a MicroVAX II that has an SMD disk attached to an
Emulex QD32 controller. I need to test and/or format the disk and so I'm
looking for images of the Emulex diagnostic floppies (should be RX50
AFAIK). Those found at http://www.headcrashers.org/comp/rx50/ boot, but I
have not the faintest idea of how to start anything in there; even a "DIR"
gives only an error, so I assume they are faulty/incomplete.
That's what I get:
>> b dua0
2..1..0..
Emulex VAX Monitor V1.2 MicroVAX I 16-SEP-1985 09:00:00
uEVM>DIR
---> ERROR: PHYSICAL READ ERROR
Is there by any chance also a diagnostic manual for this stuff?
Christian
30 Oct
30 Oct
9:21 a.m.
On 10/30/2015 09:42 AM, Christian Corti wrote:
Hi all,
I'm trying to set up a MicroVAX II that has an SMD disk
attached to an Emulex QD32 controller. I need to test
and/or format the disk and so I'm looking for images of
the Emulex diagnostic floppies (should be RX50 AFAIK).
Those found at http://www.headcrashers.org/comp/rx50/
boot, but I have not the faintest idea of how to start
anything in there; even a "DIR"
How about HELP or even "?"
I seem to recall they have a help menu in the program.
Also, you log shows MicroVAX I, so it is possible the
program won't support a Q-bus board on a MicroVAX-II.
Jon
9:34 a.m.
Just something cool - VMS Software Inc. is located in what used to be the Emulex building
in Bolton MA.
Sue Skonetski
On Oct 30, 2015, at 12:21 PM, Jon Elson <elson at
pico-systems.com> wrote:
On 10/30/2015 09:42 AM, Christian Corti wrote:
Sue Skonetski
VP of Customer Advocacy
Sue.Skonetski at vmssoftware.com
Office: +1 (978) 451-0116
Mobile: +1 (603) 494-9886
Mit freundlichen Gr??en ? Avec mes meilleures salutations
Hi all,
I'm trying to set up a MicroVAX II that has an SMD disk attached to an Emulex QD32
controller. I need to test and/or format the disk and so I'm looking for images of the
Emulex diagnostic floppies (should be RX50 AFAIK). Those found at
http://www.headcrashers.org/comp/rx50/ boot, but I have not the faintest idea of how to
start anything in there; even a "DIR"
How about HELP or even
"?"
I seem to recall they have a help menu in the program.
Also, you log shows MicroVAX I, so it is possible the program won't support a Q-bus
board on a MicroVAX-II.
Jon
10:04 a.m.
On Fri, 30 Oct 2015, Jon Elson wrote:
That's how I found the DIR command. But the HELP menu isn't very helpful
at that point.
On 10/30/2015 09:42 AM, Christian Corti wrote:
[...]
AFAIK). Those
found at http://www.headcrashers.org/comp/rx50/ boot, but I
have not the faintest idea of how to start anything in there; even a "DIR"
How about HELP or even "?"
I seem to recall they have a help menu in the program. Also, you log shows MicroVAX I, so it is possible the
program won't support a
Q-bus board on a MicroVAX-II.
Oh, that was a typo. It actually says this:
>> B DUA0
2..1..0..
Emulex VAX Monitor V1.2 MicroVAX II 16-SEP-1985 09:00:00
uEVM>DIR
START #
FILE NAME BLOCK# BLKS CREATION DATE
----------------------------------------
---> ERROR: PHYSICAL READ ERROR
Christian
7:54 p.m.
On 10/30/2015 12:04 PM, Christian Corti wrote:
On Fri, 30 Oct 2015, Jon Elson wrote:
OK, that makes much more sense with the 1985 date. Can't
imagine anybody using a MicroVAX I for more than a couple
months after the UV-II came out.
Jon
Also, you log shows MicroVAX I, so it is possible
the
program won't support a Q-bus board on a MicroVAX-II.
Oh, that was a typo. It actually says this:
>> B DUA0
2..1..0..
Emulex VAX Monitor V1.2 MicroVAX II 16-SEP-1985 09:00:00
9:37 a.m.
On 10/30/2015 9:42 AM, Christian Corti wrote:
Hi all,
I'm trying to set up a MicroVAX II that has an SMD disk attached to an
Emulex QD32 controller. I need to test and/or format the disk and so I'm
looking for images of the Emulex diagnostic floppies (should be RX50
AFAIK). Those found at http://www.headcrashers.org/comp/rx50/ boot, but
I have not the faintest idea of how to start anything in there; even a
"DIR" gives only an error, so I assume they are faulty/incomplete.
That's what I get:
I also have a QD32. I have Emulex diagnostics, but on a TK50, and I
don't have an image, nor do I have any diagnostic documentation.
However, when I ran the diagnostic (many YEARS ago) on my uVax II
(FVD32M) it was self-explanatory.
The tape is VX9962004 Rev J.
My notes say:
FQD01M is the MSCP FORMAT program for a QD32 (and QD01 and SC03) for a
PDP-11.
FVD32M is the MSCP FORMAT program for a QD32 (and QD01 and SC41 and
SC03) on a uVax. So this is the one you want.
HELP is supposed to give help.
DIR is supposed to list the diagnostics.
>> b dua0
2..1..0..
Emulex VAX Monitor V1.2 MicroVAX I 16-SEP-1985 09:00:00
uEVM>DIR
---> ERROR: PHYSICAL READ ERROR
Is there by any chance also a diagnostic manual for this stuff?
Christian
There is an Emulex QD32 manual on bitsavers, but it doesn't seem to have
any info on the diagnostics.
JRJ
2 Nov
2 Nov
3:37 a.m.
On Fri, 30 Oct 2015, Jay Jaeger wrote:
because
of read errors).
This is the SIMH output (running the microvax2 binary with the patched
ka630.bin image):
(and yes, the monitor identifies the CPU as MicroVAX I ...)
sim> att rq3 emulex_qd32_diag.img
sim> b cpu
KA630-A.V1.3
Performing normal system tests.
5..4..3..
Tests completed.
I also have a QD32. I have Emulex diagnostics, but on
a TK50, and I
don't have an image, nor do I have any diagnostic documentation.
However, when I ran the diagnostic (many YEARS ago) on my uVax II
(FVD32M) it was self-explanatory.
[...]
I wish it were true in my case. I don't even get it running under SIMH.
Is it possible that the error is because of the monitor not seeing the
QD32? At least if I netboot NetBSD it doesn't see the QD32 either, only
the RQDX3. But OTOH I can enter
> B DUB2
from the console and it tries to boot from the SMD disk (which fails >> b dua3
2..1..0..
Emulex VAX Monitor V1.2 MicroVAX I 16-SEP-1985 09:00:00
uEVM>LOAD FVD32M
--->ERROR: COULD NOT LOAD PROGRAM;
PHYSICAL READ ERROR
I think it would be great to have your TK50 imaged in some way and have it
e.g. on bitsavers.
Christian
5:56 a.m.
On Mon, 2 Nov 2015, Christian Corti wrote:
I wish it were true in my case. I don't even get
it running under SIMH.
Is it possible that the error is because of the monitor not seeing the QD32?
At least if I netboot NetBSD it doesn't see the QD32 either, only the RQDX3.
[...]
Playing a bit with the QD32 I've found out that it has the "big" EPROM,
i.e. the 27256 32kB ROM, and this one *includes* the diagnostic routines.
So there are the instructions how to enter the built-in routines:
U
I
D/P/W 20001F40 20
D/P/L 20088000 80000000
D/P/L 20088004 80000001
D/P/W 200000EC 1
D/P/W 200000EE 3003
D * 4401
S 80
And here we go:
Firmware-Resident Diagnostic
Copyright (c) 1988 Emulex Corporation all rights reserved
QD32 controller, firmware revision level K
IP address = 160354
Option menu
1 - Self Test Loop
2 - Format
3 - Verify
4 - Format and Verify
5 - Data Reliability Test
6 - Format, Verify, and Data Reliability Test
7 - Read Only Test
8 - List Known Units
9 - Replace Block
10 - Display Novram
11 - Edit / Load Novram
Enter option number:
Christian
7:57 a.m.
On Mon, Nov 2, 2015 at 5:56 AM, Christian Corti
<cc at informatik.uni-stuttgart.de> wrote:
Playing a bit with the QD32 I've found out that it has the "big" EPROM,
i.e.
the 27256 32kB ROM, and this one *includes* the diagnostic routines.
So there are the instructions how to enter the built-in routines:
U
I
D/P/W 20001F40 20
D/P/L 20088000 80000000
D/P/L 20088004 80000001
D/P/W 200000EC 1
D/P/W 200000EE 3003
D * 4401
S 80
And here we go:
Firmware-Resident Diagnostic
Copyright (c) 1988 Emulex Corporation all rights reserved
That looks like the same magic F.R.D. spell shared by at least the
QD21 and QD33 as documented in section 4.7.3 Starting F.R.D. on a
MicroVAX II and a GPX Workstation in these manuals:
http://www.bitsavers.org/pdf/emulex/QD2151002-J_QD21_Jun90.pdf
http://www.bitsavers.org/pdf/emulex/QD3351002-M_QD33_Dec90.pdf
Helpful that they kept that consistent across multiple controllers.
3100
days inactive
3103
days old
8 comments
5 participants
participants (5)
-
cc＠informatik.uni-stuttgart.de -
cube1＠charter.net -
elson＠pico-systems.com -
glen.slick＠gmail.com -
Sue.Skonetski＠VMSSoftware.com