🚀 go-pugleaf

In article <1993Jan20.123012.29125@jarvis.csri.toronto.edu> parki@csri.toronto.edu (Brian Parkinson) writes:
>Help !
>
>I am running Borland C++ with two monitors (vga and monochrome), as well
>as an AAmazing mouse with a Z-nix mouse driver version 7.04d.
>
>The problem I have is when I run the compiler with output to vga and user
>interface on mono (i.e. type bc from vga monitor).  All is well until I
>enter graphics mode and come back out (using egavga.obj autodetected, with
>a call to registerbgidriver), at which point the mouse is showing on the
>vga monitor, but activated on the mono monitor (i.e. moving the mouse to the
>top of the vga screen and pressing the button drops a menu on the mono
>screen).
>
>Any suggestions ?

Well, I'm sure glad I have *finally* heard of this from someone else.  I have
experienced some very similar problems on my (dual monitor) system.  When I
start the IDE from the command line (appearing on the VGA) with the /d switch,
I get the IDE on the mono and the code runs on the VGA OK.  I also get the
mouse cursor on the mono monitor OK.  What does not work is that the text
(underline) cursor appears on the VGA when it should be on the monochrome
monitor.  It's really weird since I can move the mouse somewhere, click on
some code, and watch the underline cursor on the VGA jump to the corresponding
location on the VGA.  However, unlike your problem, mine occurs immediately,
and does not depend on there being an initgraph().  Also, the menus and
whatnot appear on the mono monitor.  Only the text cursor appears on the VGA.
Under the debugger, however, everything works just fine.

Other strange things also occur.  I cannot see text written to the VGA while a
program is running unless I explicitly set graphics mode 3 (80x25 text).  When
I do this, The text prints white on a black background, but a clrscr() fills
the monitor with the foreground color (white), rather than the background
color (black).  This happens under either the debugger or the IDE.  The IDE
leaves the monitor in this state until I type 'mode co80'.  The debugger
apparently resets the text mode when it exits, so it does not leave the
monitor in a weird state.

My setup includes a Hercules-style mono/printer card as secondary (printer
port disabled), a Logitech wireless mouse on COM2,  (mouse driver is version
6.12, I believe), an Orchid Fahrenheit 1280 w/ 1 Mb as primary video (BIOS
version 3.0, S386C924 chip), a ProAudio Spectrum 16 sound card, 2 diasy
chained IDE hard drives, 2 serial/1 parallel/1 game card, running MSDOS 5.0
and QEMM 6.0.  The shell is 4DOS 4.0.  Oh, I also have ANSI.SYS and SmartDrv
(from Windows 3.1) installed.

Does any of this match with _YOUR_ hardware/software?  I had assumed that this
was due to the F1280 card since I had no such problems when I had a Paradise
1024 card installed.  Orchid tells me that its card is guaranteed to work only
with "a card that is incapable of going into graphics mode," but this is the
only major incompatibility I have ever noticed.

>thanx in advanx,
>
>-- 
>					What's the point in callin' shots
>Brian Parkinson				This cue ain't straight in line
><parki@csri.toronto.edu.ca>		The cue-ball's made of styrofoam
>					And no-one's got the time

Help from anyone else that might have experienced this would be _most_
welcome.

-- 
 --Jeff Hartung--  	
 Disclaimer: My opinions only, etc., etc., BLAH! BLAH! BLAH!...
 InterNet - hartung@crl.ucsd.edu    	 BITNET - hartung@ucsd
 UUCP - ucsd!crl.ucsd.edu!hartung