On 18 Feb 98 at 15:51, Michi Imamura wrote:
> On Tue, 10 Feb 1998, David Gillett wrote:
>
> > On 10 Feb 98 at 9:24, David Gillett wrote:
> >
> > > [*] The last version of "Turbo C++" I saw was about 7 years ago, and
> > > I don't think it was aware of Windows. So it seems unlikely that it
> > > would interfere with Windows operation.
> >
> > My apologies; Borland has recently revived the "Turbo C++ for
> > Windows" name. Michi, can you tell us what OS you're using, what
> > video card, and what version of Turbo C++? ANd do you have Adobe
> > Type Manager installed?
> >
> > David G
>
>
> Thanks for the input. I am running Windows '95 with the new STB velocity
> 128 video card. The version is "Borland C++ for Windows" I looked at
> the copyright and the date is 1995. Could it be that this version was
> not yet made compatible for Win '95?
Borland C++ 4.5 was current in 1995, and was basically a 16-bit
compiler. Windows 95 came out in August, and in September Borland
released 4.52; still the same compiler core, but able to generate
Win95 executables and DLLs. I believe version 5, their first 32-bit
version, shipped in spring of 1996.
So when you installed your version, it included 1995 16-bit
versions of various DLLs. It's quite possible that you already have
applications on your system that were compiled with more recent
Borland compiler versions, and have (until now) been using newer (and
possibly 32-bit) versions of those DLLs. Or, just possibly, of other
Win95 support DLLs that are included with the compiler as
redistributables.
As I recall, you're coming up in safe mode after a fatal exception
0D. There are five places (I think the list was posted here earlier
this week) where applications can get launched at startup, and so
maybe you can make a list of what programs on your machine are listed
in these places. If one of them is clearly associated with BC++, try
taking it out. [I think Borland have their own runtime tool like Dr.
Watson, and it may be set up by the compiler install....]
David G
|
