22 Aug
1999
22 Aug
'99
1:51 a.m.
The thing really wierd about this system, and one of
the main reasons I
call it a mutant beast is the following:
Controller CSR Vector Purpose
Viking QDT 172150 154 Both Hard Drives are on this board
WQESD 160334 150 Bootstrap (that's all it does)
RQDX3 160354 144 RX50
There's no real need for RT-11 to know about the existence of the WQESD,
if there aren't any drives there. I'd do a SET DU:CSR2=160354 and
map any other ports to unused CSR's and see if that helps.
If you ever want to get rid of your WQESD, let me know - I *love* them -
they're wonderfully configurable controllers, and particularly good under
RT-11 as you can get 8 bootable OS's per drive.
After one minute, I get the following:
@134606 ...
I think it's always at 134606, but the minds a little fuzzy at the moment,
Which monitor - FB? XM? SJ?
If you do a SHOW MEM (on a running system, clearly!) where does 134606
fall?
Which version of RT-11? RT-11 5.3 had some seriously screwy problems with
the DU driver in some situations, and the early 5.4's had some
serious difficulties. 5.4G isn't so bad, but not as good as 5.5 or later.
I'm working on this while working on problems at
work, and it's just a
little late. Anyone have any ideas? My plan is to normally have DU7: set
to PART=3 of UNIT=1, and only switch it to the RX50 when I need to use a
floppy drive.
Are you running any foreground jobs simultaneously? TCP/IP, maybe? Does
the crash happen if you don't start up the foreground jobs?
--
Tim Shoppa Email: shoppa(a)trailing-edge.com
Trailing Edge Technology WWW: http://www.trailing-edge.com/
7328 Bradley Blvd Voice: 301-767-5917
Bethesda, MD, USA 20817 Fax: 301-767-5927