From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: From: Daniel Lyons To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> In-Reply-To: Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v935.3) Date: Mon, 3 Aug 2009 00:57:39 -0600 References: Subject: Re: [9fans] Parallels Vesa driver question Topicbox-Message-UUID: 3628adca-ead5-11e9-9d60-3106f5b1d025 On Aug 2, 2009, at 3:41 PM, erik quanstrom wrote: >> Erik, >> >> Thanks for your speedy assistance! I think the two things are closely >> interrrelated via the global variable hardscreen. Reverting this file >> solved the problem. I wouldn't be surprised if there were something >> weird about Parallels' MTRR support, and since this isn't the current >> version it's not likely to get any better. If anyone's using =20 >> Parallels >> 4 and not running into this issue, I'd love to know. > > you're welcome. > > but if you wouldn't mind, would you try the new source but modify > it by replacing the vgavesaflush in the following diff with "0"? Yes, this alone is not sufficient to fix the problem, which I believe =20= confirms your suspicion that there is a defect in either Parallel's =20 MTRR or Plan 9's Vesa MTRR. My money would be on Parallels, since they =20= have a reputation for building the VM to support Windows first. Again, thanks! Hopefully I'll be able to afford a copy of the new =20 version of Parallels in a little while and perhaps that will help =20 further isolate the problem. =97 Daniel Lyons