🚀 go-pugleaf

In article <1992Apr7.202021.17304@donner.SanDiego.NCR.COM> jim@cheers.SanDiego.NCR.COM (Jim Ruehlin) writes:
>
>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!

Unfortunately, Microsoft would not allow us to violate our NDA for
Windows 3.1 in order to contact BC++ users about the TDW
incompatibility.

There is a replacement WINDEBUG.DLL available that allows TDW to run
with Windows 3.1.  You can get it from:

	Compuserve
	Genie
	Bix
	Borland BBS (408-439-9096)
	
There is a document available describing the problems and solutions.
You can get it from the above places (document number 868) as well
as through

	calling tech support
	calling our techfax number (800-822-4269) 
		request document 868

On the online systems, the file is called ti868.zip.

I'm sure it is available for FTP from somewhere, I just don't know
where.  I'm calling around to find out where it is, and I'm sure
someone will post something here describing the location.

-- Eric Swenson (Borland R&D)