🚀 go-pugleaf

I've been using TURBO C since version 1.01 (a very grotty package) up to the
later version I got BROLAND C++ 2.00 (Heaps better, even great!).

Since TURBO C++ 2.00 I've had a problem with one 386, that desptie throwing
money at hasn't gone away.

The PC is an early 386/16, No cache, 4Meg (Mortech I think), which keeps
crashing upon starting the IDE.

If I don't clean up all windows (<alt>-<space> C) before exiting, then *USUALLY*
the next time I run the IDE, I get the following message:

ERROR:
Internal error - Please report to Borland. Press ESC

And then upon pressing ESC:

exit error=0, winerror=3

and then the shell prompt.

I discussed this problem with BORLAND Australia many times, and after some
time was told that moving to BORLAND C++ 2.00 would cure the problems.

It didn't !

The only difference I get is that the first message now says:

ERROR:
sorry, unrecoverable internal error. Press ESC

I find this very annoying, especially I can "export" the problem to other
machines, simply by moving .DSK and .PRJ files. (Kinda makes it hard on a
network).

Following is a partial copy of the FAX I sent to Borland 22/3/91:

Screen upon booting:
________________________________________________________________________________
Phoenix Enhanced Video BIOS PLUS Version 1.00.00
Copyrite (c) 1986, 1987 Phoenix Technologies Ltd
All Rights Reserved
Video RAM 256KB

386-BIOS  (c) 1987 American Megatrends Inc

04096 KB OK







 (c) American Megatrends Inc.,
    SC&T-1102-011388-K0
________________________________________________________________________________


My config.sys looks like:
________________________________________________________________________________
Files = 35
Buffers = 20
Shell = c:\dos\command.com c:\dos /e:1024 /p
Country = 061,,c:\dos\country.sys
LastDrive = Z
________________________________________________________________________________

My autoexec.bat :
________________________________________________________________________________
@echo off
path ..;c:\dos;c:\tools;r:;s:;c:\batch;c:\tools\emacs;c:\applic
set bgi=c:\applic\bgi
set tctokstart=9,2,0,0
set stfscrz=520,400,120,400,640,80
set mfs=8,200,4
set help=c:\help\
set nvt80=3
set nvt132=57
subst h: c:\borland\tc\include
subst s: c:\borland
subst l: c:\borland\lib
subst r: c:\rwa
subst x: d:\libdvt
prompt $p$g
d:
________________________________________________________________________________

We have two other 386 machines (25Mhz) also with 4 Meg memory, and a NEC APC IV,
none of which cause the porblem to appear. This problem is very frustrating,
because It means that we have to take one of the other machines off-line to
do development.

Has anyone had a similar problem: could Borland U.S. reply - I get no joy
from Borland Australia, and am unwilling to keep forking out $ for new
versions, if they might not cure the problem.

...BRU