🚀 go-pugleaf

In article <16NOV199223050853@vms1.iscs.nus.sg> nuscss1@vms1.iscs.nus.sg (Vax BULLET-IN-Board SysOps) writes:
>	I've installed Borland C++ with App Frameworks on 3 different
>	machines, but I cannot run Turbo Debugger for WIndows on any of them.
>	When I launch TDW, it loads fine. But when I try to open a file,
>	TDW terminates, throws me back to the Windows desktop, and says
>	"Cannot Load WINDEBUG.DLL". 
>	
>	This is puzzling. I've ensured that the paths are correct, and even
>	placed a copy of WINDEBUG.DLL in the WIndows directory just to be safe.
>	TDDEBUG.386 is also loaded. But I just cannot get it to work.
>
>	Can anyone help ? Thanx in advance.
>

Almost certianly using BC++ 3.0 with windows 3.1, it won't. Either get
boralndc c++ 3.1 (worth it) or get a patched version of windebug.dll off borland

In article <1992Nov16.162408.23622@mksol.dseg.ti.com>, mccall@mksol.dseg.ti.com (fred j mccall 575-3539) writes...
> 
>You are apparently running an old version of Borland C++ (telling us
>the versions of Borland C++ and Windows you are running would have
>been helpful).  I am assuming you are running Borland C++ 3.0 and
>Windows 3.1 on these machines.  

	you're right on target: I am running BC++ 3.0 with Windows 3.1.

>You need to either patch the debugger
>(which still leaves some things not working quite well between Borland
>C++ and Windows 3.1, as I understand it) or you need to upgrade to the
>current version of Borland C++ (3.1).

	o rats! more $$$. the guys in the office won't be happy when they
	hear this... =-)
> 
>Just by the way, where did you get 3 OLD copies of Borland C++ that
>you are just now trying to load on machines?
> 
	My employer bought them. But then again, these copies 
	were bought a while back when they were coding for Windows 3.0.
	I guess upgrading the compiler was not high on their priority list...

>-- 
>"Insisting on perfect safety is for people who don't have the balls to live
> in the real world."   -- Mary Shafer, NASA Ames Dryden
>------------------------------------------------------------------------------
>Fred.McCall@dseg.ti.com - I don't speak for others and they don't speak for me.

In <19NOV199201082045@vms1.iscs.nus.sg> nuscss1@vms1.iscs.nus.sg (Vax BULLET-IN-Board SysOps) writes:

>In article <1992Nov16.162408.23622@mksol.dseg.ti.com>, mccall@mksol.dseg.ti.com (fred j mccall 575-3539) writes...

>	o rats! more $$$. the guys in the office won't be happy when they
>	hear this... =-)
>> 
>>Just by the way, where did you get 3 OLD copies of Borland C++ that
>>you are just now trying to load on machines?
>> 
>	My employer bought them. But then again, these copies 
>	were bought a while back when they were coding for Windows 3.0.
>	I guess upgrading the compiler was not high on their priority list...

Well, the upgrade isn't that expensive ($40?) and now you have the
perfect excuse -- just ask them if being able to DEBUG is high on
their priority list. :-)

The upgrade is really worth it, particularly if you are using the
Windows IDE during development.  The Windows version of the IDE now
does all the same kinds of optimizations and such that the DOS version
did, instead of being a basically 'non-optimizing' compiler.

-- 
"Insisting on perfect safety is for people who don't have the balls to live
 in the real world."   -- Mary Shafer, NASA Ames Dryden
------------------------------------------------------------------------------
Fred.McCall@dseg.ti.com - I don't speak for others and they don't speak for me.