Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!uw-beaver!tektronix!zeus!bobr
From: bobr@zeus.TEK.COM (Robert Reed)
Newsgroups: comp.sys.ibm.pc
Subject: Microsoft Codeview, Logitech and Compaq EGA troubles
Message-ID: <2509@zeus.TEK.COM>
Date: Thu, 8-Oct-87 19:08:59 EDT
Article-I.D.: zeus.2509
Posted: Thu Oct  8 19:08:59 1987
Date-Received: Sun, 11-Oct-87 10:26:55 EDT
Reply-To: bobr@zeus.UUCP (Robert Reed)
Organization: CAE Systems Division, Tektronix Inc., Beaverton OR
Lines: 24

I have a copy of Codeview which I got with MS C 4.0 which exhibits several
peculiar behaviors.  This note is a query about other encounters with these
problems and any possible avoidance procedures, etc:

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
disabled, output from the program gets garbled with Codeview data, sometimes
creating quite a mess.

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
Codeview doesn't know about using the mouse in 43 line mode.  If I set 43
line mode in Codeview, the cursor echo is disabled if the cursor drops below
the normal (24th?) bottom line.  Coordinates are making it to Codeview,
because I can set breakpoints, but position a cursor that is not being
echoed can be a real bitch.

Has anyone encountered these difficulties?  Any suggestions?
-- 
Robert Reed, Tektronix CAE Systems Division, bobr@zeus.TEK