Xref: utzoo comp.lang.c++:12802 comp.os.msdos.programmer:4573
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!mcnc!uvaarpa!murdoch!usenet
From: randall@Virginia.EDU (Randall Atkinson)
Newsgroups: comp.lang.c++,comp.os.msdos.programmer
Subject: Re: Strange run-time error with Borland C++2.0 IDE
Message-ID: <1991Apr9.201916.17649@murdoch.acc.Virginia.EDU>
Date: 9 Apr 91 20:19:16 GMT
References: <104577@tut.cis.ohio-state.edu> <4535@se-sd.SanDiego.NCR.COM> <105414@tut.cis.ohio-state.edu>
Sender: usenet@murdoch.acc.Virginia.EDU
Followup-To: comp.os.msdos.programmer
Organization: University of Virginia
Lines: 13


In article <105414@tut.cis.ohio-state.edu> mcmillan@harpsichord.cis.ohio-state.edu (Harold McMillan) writes:
>It seems that the problem with the GP exception  in Borland C++ 2.0
>that I posted earlier may have to do with the Microsoft mouse driver.
>Someone sent me mail to this effect, and I have not seen the problem
>recur without the mouse driver loaded.  Now, how on earth did Borland
>design BCX to be incompatible with the Microsoft Mouse, or did they
>just see this as a way to get back at Microsoft?

Gee, why jump to unwarranted conclusions ?  The problem is that
OLDER versions of the MS Mouse driver aren't compatible.  BC++ is
fully compatible with the current MS Mouse driver.  The fix reported
by others on the net is to get a current MS Mouse device driver...