🚀 go-pugleaf

In article <1992Apr10.004008.20583@colorado.edu> toupine@ciaibbs.Colorado.EDU (edward toupin) writes:
>
>I need some assistance with TDW (Borland Turbo Debugger for Win).
>
>I just got WIN3.1 and attempted to run TDW and got an error that
>stated
>
>		Cannot Load WINDEBUG.DLL
>
>I looked in TDW directory and it was there.  What has happened?  Is
>there a new version for WINDEBUG.DLL from BORLAND?  How do I
>fix this?  Are there any other situations such as this that
>anyone has noticed?
>
>Please send EMAIL if possible.
>
Sorry, but I think this might be general interest...

Found out about this on the CI$ Borland Forum, so it's official minus
whatever misinterpretions/misrememberings I've made (I suspect Sidney
and/or Pete will be posting the read.me file soon).

TDW does not work with Windows 3.1 because MS has updated the debugger
interface slightly, as defined by the windebug.dll.  You can get an
updated windebug.dll that will allow TDW to work under Windows 3.1 (but
NOT the SDK debugging kernel) by downloading tdwin.zip from the Windows
library section (section 7?).  There still are some other problems
concerned with things like not having the 3.1 windows.h file.  For those
fixes you'll have to wait until Borland sends out the 3.1 upgrade
package in 4-6 weeks after MS ships the SDK 3.1.  No word as to pricing
of the upgrade.

>Thanks in advance,
>
>Ed Toupin
>toupine@ciaibbs.colorado.edu

-- 

==========================================================================
Michael H. Cox			ARPA:  cox@garage.nj.att.com
AT&T Bell Labs			UUCP:  ihnp4!edsel!cox