Path: utzoo!attcan!uunet!ncrlnk!ncr-sd!hp-sdd!hplabs!hpda!hpwala!boba
From: boba@hpwala.wal.hp.com (Bob Alexander)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Turbo C 2.0 and EMS
Message-ID: <788@hpwala.wal.hp.com>
Date: 18 Jan 89 17:58:06 GMT
References: <6957@june.cs.washington.edu> <598@dms.UUCP>
Reply-To: boba@hpwala.wal.hp.com (Bob Alexander)
Organization: Hewlett Packard, Waltham, Mass
Lines: 17
UUCP-Path: hpwala!boba

>Off the top of my head I remember that there is a bug in the integrated
>debugger that will totally screw up your programs graphics output to the second
>page of video memory, regardless of what the debugger settings are, but
>works fine if you only use the first video page, and don't swap pages.

I don't understand this.  I've been working on a game that uses both graphics
pages on a Hercules adapter clone, and I've had no problems with the TC
debugger.  Is there a certain sequence that triggers the bug that I might
be missing?


  Bob Alexander      | Nerds are people, too - I think... 
  boba@hpwala.hp.com | 
  -------------------+---------------------------------------------------
  Organizations don't have opinions: individuals do.  The opinions expressed
  above do not necessarily reflect those of the stockholders, employees, or
  directors of Hewlett-Packard.