J. Buck Caldwell wrote:
> 
> Kay, so, I downloaded the right kernel &such, and BOOM it works well (with the exception that the
> first-stage bootloader still goes to the serial console, but I'll fix that later). However, I wasn't

Currently boot and xxboot support the KA630 ROM routines.  On the KA650
they use gencons.  Maybe the 630 code will work on the 650 and in any
case it shouldn't be too much trouble to add KA650 support.

> went away. But there's still one thing bothering me - MORE. Whenever I use more (man, listing files,

Weird... more works for me.  

> Also - the little question - in man, I see codes <> that indicate something should be underlined or
> blocked - will this eventualy be supported?

Hmm... you shouldn't.  Are you *sure* that you're using qdss as your
terminal type?  If you aren't that would explain more and man.

In any case, I admit that the qdss terminal type really sucks and the
driver should be using some other emulation instead.  Any suggestions?

> Damn, alright, one more question, I promise, this will be the last. Ever since putting in my QDSS,
> my DHV11 has been giving me Silo errors. Can I change around the Q-bus order as so: KA650, MEM, MEM,
> MEM, DELNI/GRANT, DHV11, QDSS, QDSS, QDSS, TQK50/RQDX3 ? I assume that if you put the DHV11 closer
> to the CPU, it'll work better - but will that do anything detrimental to the QDSS?

By all means change the order.  The QDSS does DMA and it probably isn't
being very nice to your DHV11.  Mine is before the MSCP disk controllers
but after everything else and it is happy.

-- 
|  Boris Gjenero <bgjenero@undergrad.math.uwaterloo.ca>              |
|  Home page:  http://www.undergrad.math.uwaterloo.ca/~bgjenero/     |
|  "Luke, you're going to find that many of the truths we cling to   |
|  depend greatly on our own point of view." - Obi-Wan Kenobi, ROTJ  |