🚀 go-pugleaf

In article <69954@ut-emx.uucp> jamshid@ut-emx.uucp (Jamshid Afshar) writes:
>In article <31390003@col.hp.com> denisl@col.hp.com (Denis Lambert) writes:
>>Ihave had similar problems with TDW and Windows 3.1.  [...]
>>I could read the TDW display now, but whenever I tried to load
>>a program I got the error message "Cannot load WINDEBUG.DLL."  Apparently
>>there are more serious incompatabilities than the video.  
>
>Last time I was on the phone with tech. support I asked if there were
>any problems with B/TC++ and Win3.1.  They said the debugger doesn't
>work.  Some file was changed or something, I didn't get the details.
>I was told that is the only problem they know of with 3.1 (but make
>sure you already have the TCW/WINSIGHT patch announced a month ago).
>
>>My solution:  Load Windows 3.0 back on my system and start it up whenever
>>I need to debug something.  Not very elegant, but I can put up with it
>>for the short term.
>
>I don't think there is any other solution.  The tech. support person
>said they would release a patch for TDW "as soon as reasonably
>possible", so you probably won't have to put up with it for much
>longer.  If anyone (esp. an X@borland.com) knows more, please post.

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)