🚀 go-pugleaf

In article <4866@cica.cica.indiana.edu> burleigh@cica.cica.indiana.edu (Frank Burleigh) writes:
>I've been happily using TC++ professional 1.0 for a few months
>now.  All is basically well except for the debugger within the
>TC++ environment and some facets of the standalone debugger.
>I'm curious if others have noticed any of these and, if so, have
>a way to solve/improve them.
>
>I have a 20MHz 386 with 4mb, several MB of which is EMS memory.
>I start TC 
>
>   tc prjname /e
>

[stuff deleted]

>
>Some other bad things just popped into my head...
>
>3. Last week TC would die and kill my pc (protection violation
>   message from 386^max) every time I tried to compile even one
>   module in my project.  After a lot of horsing around I found
>   that if I deleted the .prj file and built a new one, I could
>   continue my work.  Apparently TC can corrupt a prj file but
>   does not recognize when the prj file is corrupted.

This is a known bug. There is a patch file available called (if I remember
right) tcppt1.zip. It fixes the corrupted .prj file problem along with a few
other problems. It is avaialble in the PROGB section of the Borland forum on
Compuserve. Note that you must rebuild your .prj files after applying the
patch before the problem goes away. This is documented.

I believe that someone has uploaded the patch to simtel recently.

Russ Poffenberger               DOMAIN: poffen@sj.ate.slb.com
Schlumberger Technologies       UUCP:   {uunet,decwrl,amdahl}!sjsca4!poffen
1601 Technology Drive		CIS:	72401,276
San Jose, Ca. 95110             (408)437-5254