Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ucsd!ucbvax!edison.cho.ge.com!rja
From: rja@edison.cho.ge.com (rja)
Newsgroups: comp.os.msdos.programmer
Subject: TC++ & mice & 386's
Message-ID: <9007171159.AA11108@edison.CHO.GE.COM>
Date: 17 Jul 90 11:59:09 GMT
References: <MAILER-DAEMON>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: rja <rja@edison.cho.ge.com>
Lines: 13

In-Reply-To: <5953@hub.ucsb.edu>
References: <46500140@uxa.cso.uiuc.edu> <647@cvbnetPrime.COM> <AV.90Jul12093734@kielo.uta.fi> <7790@tekgvs.LABS.TEK.COM> <4029@isis.UUCP>

If one is using VRROOM with TD386/TDH386.SYS and one hasn't
configured VRROOM to leave alone the memory where
TD386 lives and also suitably configured TD386, 
there can be protection violations as a result.
 
It is generally the case that one has to be careful when
configuring things to be sure that all users of high-memory
do so in an appropriate manner.  It can be non-trivial to
figure such beasties out if you have lots of high-memory
using applications, but it is do-able.