Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bunny!rhb6
From: rhb6@bunny.UUCP (Robert H. Barkan)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Microsoft Codeview, Logitech and Compaq EGA troubles
Message-ID: <5213@bunny.UUCP>
Date: Tue, 13-Oct-87 18:40:19 EDT
Article-I.D.: bunny.5213
Posted: Tue Oct 13 18:40:19 1987
Date-Received: Thu, 15-Oct-87 05:19:22 EDT
References: <2509@zeus.TEK.COM>
Organization: GTE Laboratories, Waltham, MA
Lines: 52
Summary: Codeview/EGA ibm compatible problem revisited


> I have a copy of Codeview which I got with MS C 4.0 which exhibits several
> peculiar behaviors....
> My system is a Compaq 386 running MSDOS 3.1.  When I try to use Codeview to
> debug a program, I have to be very careful to disable the Flip option before
> letting the debugged program start.  If I don't, the whole screen will go
> into reverse video, which makes it very hard to read things in Codeview.
> Even when I do this, when I return to Codeview at the first breakpoint, the
> nonaddressable margin of the display shifts to bright green.  With flip
> ...

The Codeview/EGA bug on ibm compatibles was discussed a few months ago, but
I don't remember seeing anything specific about the Compaq.  Since I had the
same problem, here's how I resolved it.

We have 2 Compaq 386s, both with Compaq EGA boards running DOS 3.1.  One of
them had this color problem, and the other was fine.  A little detective work
revealed just two differences in the 2 EGA boards.  The newer EGA board (the
good one) had a higher revision number on it (don't remember the numbers),
and a wire jumper across one of the chips, probably a quick fix.  When I
swapped boards, the problem disappeared.  I then spoke to a person at Compaq
who didn't acknowledge the problem, but said only "contact your vendor".
After about 2 months of "*contacting* my vendor", they reluctantly sent a
newer replacement EGA board.  End of bright-green-and-inverted-color problem.

\begin{flame}
During part of the ordeal, I was asked (more than once):
    - was I using the right dip switch settings?
    - was my system configured properly?
    - is the software causing the problem?
    - was I entitled to a replacement board even though my original one was
      no longer under warranty?
These might be valid questions for a previously unreported problem, but it
seems like someone was aware of the problem, and quietly fixed it.  Since the
problem didn't appear on IBM machines, and the fact that Compaq makes *100%*
compatibles (said the Compaq rep), was enough to finally resolve the matter.
\end{flame}

> I also recently acquired a Logitech bus mouse, which makes using Codeview a
> whole lot easier except for one problem.  Either the Logitech driver or
> ...
> Robert Reed, Tektronix CAE Systems Division, bobr@zeus.TEK

I have a Mouse Systems mouse.  After the first time the output screen is
shown, the mouse is not echoed.  If I then blindly position the mouse in the
right side of the top line, I can "dig it out" when I press the left button.
I suspect this is a problem with the Mouse Systems device driver.
-- 
Bob Barkan				GTE Laboratories
					40 Sylvan Rd
..!harvard!bunny!rhb6			Waltham, MA 02254
rhb6%gte-labs.csnet@relay.cs.net	617/466-2568