🚀 go-pugleaf

hartung@crl.ucsd.edu (Jeff Hartung) writes:

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

>...[I had a problem with Orchid's F1280 card and BC++ 3.1] :
>>everything worked fine.  The only way I could use the 640*480 (256) was to
>(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?)

I have an application that I developed using BC for Dos, which was
running and debugged when I ported it to windows.  Once I got the
windows version running, (running without any error messages upon exit)
I tried to run the debugger to step thru the code.  It (TDW) left for Dos,
gave me the menu & source editor windows etc. all fine and dandy.  But 
when I asked it to display the output window (i.e., Windows)
it hung.  

I am using Windows 3.1, BC for Windows 3.1, a Fahrenheit 1280D card
(with the upgraded drivers for Windows 3.1) at 1028x768 with 8 Meg of RAM.
(I may have experienced the same difficulty at 800x600 but don't quote
me on that.. my memory is failing me) 

= Mark


P.S. Oh, BTW, Borland's usually helpful tech support offered great
insight into this problem (NOT!)  I think the exact quote was:
"Hmmm.  [Silence.]"