Article View: comp.windows.ms.programmer
Article #211Re: BCC TDW Doesn't Work Under Win 3.1
From: jim Jim Ruehlin
Date: Tue, 07 Apr 1992 20:20
Date: Tue, 07 Apr 1992 20:20
20 lines
1479 bytes
1479 bytes
In article <1992Apr7.035208.24356@mnemosyne.cs.du.edu> ebergman@isis.cs.du.edu (Eric Bergman-Terrell) writes: >The TDW debugger doesn't seem to work anymore now that I've installed Windows >version 3.1. It complains that it "Can't Load WINDEBUG.DLL". (windebug.dll >is in \borlandc\bin). > >I know that we (BCC users) have to wait about a month for a 3.1 maintenance >upgrade, but I was hoping that the tools would still allow us to compile >and debug 3.0 programs. Windows 3.1 SDK doesn't come with WINDEBUG.DLL like 3.0 did. It's been renamed, and since I'm over 30 now I can't remember what the darn thing's called! It comes with the Windows SDK for 3.1, I think. You need to get that DLL and rename it to WINDEBUG.DLL. I found this out because I was a beta tester for 3.1 and some of my co-workers were using the 3.1 SDK. Shame on Borland for not filling developers in on this! - Jim Ruehlin
Technical Details
Message-ID:
<1992Apr7.202021.17304@donner.SanDiego.NCR.COM>Path:
arc1-ca.pugleaf.net!sparky!uunet!haven.umd.edu!darwin.sura.net!gatech!hubcap!ncrcae!ncr-sd!SanDiego.NCR.COM!!jimReferences:
<1992Apr7.035208.24356@mnemosyne.cs.du.edu>Show Full Headers
Complete Article Headers
Newsgroups: comp.windows.ms.programmer,comp.lang.c++ Path: arc1-ca.pugleaf.net!sparky!uunet!haven.umd.edu!darwin.sura.net!gatech!hubcap!ncrcae!ncr-sd!SanDiego.NCR.COM!!jim From: jim@.SanDiego.NCR.COM (Jim Ruehlin) Subject: Re: BCC TDW Doesn't Work Under Win 3.1 Message-ID: <1992Apr7.202021.17304@donner.SanDiego.NCR.COM> Sender: news@donner.SanDiego.NCR.COM (News Owner) Reply-To: jim@cheers.SanDiego.NCR.COM (Jim Ruehlin) Organization: NCR Corporation, Rancho Bernardo References: <1992Apr7.035208.24356@mnemosyne.cs.du.edu> Date: Tue, 7 Apr 1992 20:20:21 GMT