Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!ucdavis!iris!foss
From: foss@iris.ucdavis.edu (Jim Alves-Foss)
Newsgroups: comp.sys.ibm.pc
Subject: Re: DESQView+Codeview=internal error 80
Message-ID: <4692@ucdavis.ucdavis.edu>
Date: 19 Jun 89 16:55:12 GMT
References: <89Jun17.232505edt.18900@me.utoronto.ca>
Sender: uucp@ucdavis.ucdavis.edu
Reply-To: foss@iris.ucdavis.edu (Jim Alves-Foss)
Organization: U.C. Davis - Department of Electrical Engineering and Computer Science
Lines: 23

In article <89Jun17.232505edt.18900@me.utoronto.ca> rwh@me.utoronto.ca (Russell Herman) writes:
>Trying to use MSC 5.1 Codeview and DESQView 386 (ver. 2.23) produces an
>"Internal Error 80" from Codeview.  If there are any patches or workarounds
>(besides using TurboC 2.0 which works fine) please let me know.  I'm using
>XDV and QEMM.SYS with an exclude region to make a "hole" for an ATI EGA
>Wonder800 card.
>
>Perhaps some DESQView expert can enlighten me why my system locks up when
>I add the 'ram' parameter to the QEMM.SYS call as well.  The machine is a
           ^^^^^
>noname clone wth 4MB RAM running a Phoenix bios.

I had some problems installing QEMM with 'ram' parameter. They occured because
the onboard BIOS was using 'shadow' ram (mapping the ROM to RAM at the same
location). Perhaps this is what happens to you. 

Does the system lock up if you don't make a hole for the EGA card. I have an
Everex EVGA and QEMM detects this fine. 

As for Codeview, I haven't noticed any problems (yet) but I don't recall if
I've ever tried to run codeview in a window. Maybe Quarterdeck has a solution,
I hear their technical support tries to be helpful.
-Jim Alves-Foss (foss@iris.ucdavis.edu)