It was thus said that the Great Sam Ismail once stated:
On Sun, 22 Jun 1997, A.R. Duell wrote:
IMHO that's a much nicer way to do it than
the Apple method which means
you have to know which slot each card is in (and, in a lot of cases there
are 'standard' slots for particular cards that you'd better stick to. What
do you do if you want _2_ 80 column displays in the same machine? One in
slot 3, what about the other one).
That was a limitation introduced with the //e. The 80 column board had
its own special slot that took over slot 3 if you had it populated.
However, nothing was stopping you from putting another 80-column board
(such as a Videx) in another slot and using that, although I can't think
for the life of me why you'd need two 80-column cards.
Debugging. You can run your program on one screen, and have debugging
output/debugger output on the second screen. I did that once on a PS/2 when
I was writing code to manage the 8514 display. It was very nice to see not
only the output, but have the debugger not munging the display.
-spc (Could easily get addicted to a system with duo displays)