🚀 go-pugleaf

In article <1992Apr9.220506.18271@borland.com> ejs@borland.com (Eric Swenson) writes:
>In article <prao.702673242@hcfmail> prao@bluemoon.ucsb.edu writes:
>>Soo... there *is* a fix, a new WINDEBUG.DLL.  When will it come out?  Dunno.
>>I would definitely expect it in the windows v3.1 SDK, to ship in 4-6 weeks.
>>It will probably be in the w3.1 update from Borland as well, shipping in
>>4-6 weeks (sigh).  I have heard a rumor they may release a quick update,
>>containing a new windows.h file (implib it yourself I supose) and a updated
>>WINDEBUG.DLL.  This is just a rumor however.
>
>I don't know the details, but if I were you, I'd call Borland Tech Support
>and ask them.  We have a solution in place for TDW/Windows 3.1, but I just
>don't know what it is.  I'm sure they do.  You're not the only one who has
>"discovered" that TDW and Win31 don't mix.  The updated DLL does fix the
>problem, you just have to get it.  I think we're making it available for
>free now.  -- Eric

I've since learned what the solution is:  

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)