Path: utzoo!attcan!uunet!jarthur!usc!julius.cs.uiuc.edu!apple!agate!shelby!portia.stanford.edu!jessica.stanford.edu!aaron
From: aaron@jessica.stanford.edu (Aaron Wallace)
Newsgroups: comp.windows.ms
Subject: Re: Video 7 bug in Codeview for Windows
Keywords: codeview
Message-ID: <1990Sep19.170953.8829@portia.Stanford.EDU>
Date: 19 Sep 90 17:09:53 GMT
References: <6577@sugar.hackercorp.com> <1990Sep18.165215.22281@jdyx.UUCP> <1990Sep18.194810.2713@athena.mit.edu>
Sender: Aaron  Wallace
Organization: Academic Information Resources
Lines: 27

In article <1990Sep18.194810.2713@athena.mit.edu> mmshah@athena.mit.edu (Milan M Shah) writes:
>Since the topic was brought up by someone other than myself, I feel
>inclined to recount my experience with Video 7 and their SVGA (Shit
>VGA) cards.

>Most have Video 7 1024i in them. They all have the same problem - if 
>you try to use Codeview for Windows (and therefore have a second mono
>card in your system), your VGA screen will go black and white. Bad.
>Bad. Bad.
>
>I have tried n number of compatible mono cards, an original Hercules
>card, and an original IBM PC MDA card (yes, the original one). Same
>problem on all machines. No can debug.
>

Were the Video 7 cards running in 8 or 16-bit mode?  I'm not even sure if this
can be configured on them, but they may have to be in 8-bit mode to work with
other 8-bit cards that reside in the same address space.  Mono cards and VGA
cards tend to share the B000 space.  And, as a good article in PC Mag stated,
what happens is that the 16-bit card says send the data in 16-bits, even if 
it's intended for the 8-bit card.  Some cards sense when there could be a
conflict and auto-set themselves to 8-bits (maybe Paradise does?), and this
addressing conflict isn't a problem with MCA (PS/2 VGA)...

Just a hunch...

Aaron Wallace