home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!sdd.hp.com!network.ucsd.edu!sdcc12!cs!pluto
- From: pluto@cs.ucsd.edu (Mark Plutowksi)
- Newsgroups: comp.os.ms-windows.programmer.misc
- Subject: Re: TDW and Video Drivers
- Message-ID: <37387@sdcc12.ucsd.edu>
- Date: 28 Aug 92 18:30:00 GMT
- References: <1992Aug28.153940.23634@das.harvard.edu>
- Sender: news@sdcc12.ucsd.edu
- Lines: 44
- Nntp-Posting-Host: beowulf.ucsd.edu
-
- gordy@endor.uucp (Robert Gordy) writes:
-
- >Has anyone had problems running Borland C++ 3.1 Turbo Debugger
- >for Windows using certain video drivers? I spent a couple
- >of hours fighting with TDW last night before I realized it
- >was the video driver. If I use any of the drivers that
- >came with my Ultra Graphics Board or the 8514 driver that
- >came with Windows 3.1, TDW will not only bomb out (ie. lock
- >up the system) but when I try to cancel the task with Cntl-Alt-Del,
- >it gives me a GPF and brings me back to the DOS prompt.
-
- >When I run TDW using the 800x600 16 color VGA driver (comes with
- >Windows 3.1) it runs fine.
-
- >Other details:
- > 486 50 Mhz (DX2) processor
- > ATI Ultra Graphics Board w/1 Mg
- > Crystal Scan 15" monitor (1248 x 1240)
- > Windows 3.1/DOS 5.0
- > Borland C++ w/Application Frameworks 3.1
-
- >Thanks in advance for the help.
-
- >Rob Gordy
-
-
-
- YES. I'm using a Fahrenheit 1280D display
- card. BCW 3.1's TDW locks up when I use
- the 800x600 or 1068x768 drivers.
- It locks up when it is supposed to
- switch to Windows mode. I then to a Ctrl-Alt-Del,
- and then, if I'm lucky, it returns to the the
- Windows mode. Eventually, however, it bombs
- rather ungracefully, invoking a reboot.
-
-
- LISTEN UP BORLAND!! So far, TDW is worthless to me
- because of this. It is The Big Sore Point in an otherwise
- seamlessly crafted product.
-
-
- = Mark
-
-