Xref: utzoo comp.lang.c++:12747 comp.windows.ms.programmer:1748
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!att!ucbvax!tut.cis.ohio-state.edu!harpsichord.cis.ohio-state.edu!mcmillan
From: mcmillan@harpsichord.cis.ohio-state.edu (Harold McMillan)
Newsgroups: comp.lang.c++,comp.windows.ms.programmer
Subject: Re: Strange run-time error with Borland C++2.0 IDE
Summary: conflict with mouse
Message-ID: <105414@tut.cis.ohio-state.edu>
Date: 9 Apr 91 16:06:52 GMT
References: <05c3fa6bec3a27f37740@rose.uucp> <104577@tut.cis.ohio-state.edu> <4535@se-sd.SanDiego.NCR.COM>
Sender: news@tut.cis.ohio-state.edu
Followup-To: comp.lang.c++
Organization: The Ohio State University, Department of Computer and Information Science
Lines: 12

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?

	Hal
--
Hal McMillan                | "It's an ideal principle, which can be verified
mcmillan@cis.ohio-state.edu |  only under ideal conditions.  Which means never.
72627.642@CompuServe.com    |  But it's still true."