🚀 go-pugleaf

In article <timann.711818019@narziss> timann.pad@sni.de (Martin Timann) writes:

>I had a similar problem with my ET 4000 Tseng card (1 MB) with BC++ 3.0 :
>The debugger came with a SVGA DLL for Tseng based  cards.
>I have renamed the DLL according the readme file to tdvideo.dll.
>When debugging with a single monitor in 640*480 (256 colors) the user
>screen was trashed.  When switching to 1024*768 (256) and 800*600 (256)
>everything worked fine.  The only way I could use the 640*480 (256) was to
>switch on Int2Fassist in the tdvideo.ini file but this slows down speed
>if you specify Fullscreen saving too. The problem dissappeared on a two
>monitor system.

I am having a related, similar problem with my Orchid F1280 card and BC++ 3.1
on a 2 monitor system.  (The same problem occurred with 2.0, which I recently
upgraded from.)  When I run the DOS debugger or IDE from the command line with
the switch to display the code on the other monitor, the display on the
monochrome monitor is fine, but the display on the VGA screen does not show up
unless I explicitly set the text mode (with an INT 10 call to function 00,
AL=03).  Even then, the display sometimes does not work.  Graphics screens
seem to work fine, but text display of any sort simply does not print.  (The
cursor moves, but the text is "invisible.")

When I called Orchid, the tech told me that there was a known problem with the
F1280 coexisting with a monochrome card that was at all capable of going into
graphics mode, even if no attempt to enter graphics mode was made.  He
suggested that I replace my Hercules card with an honest-to-God MDA.  (Where
on earth can I find an MDA?)

Question:

	Has anyone else exterienced this problem?

	What, short of replacing my mono card, can I do to remedy the
	situation?

(BTW, I haven't even tried debugging a Windows app yet, given the problems
with DOS debugging.  I'd imagine the problems would arise there as well.  Any
experiences out there?)

-- 
 --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