From owner-freebsd-emulation Sat Jun 10 18: 1:33 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mass.cdrom.com (adsl-63-206-88-224.dsl.snfc21.pacbell.net [63.206.88.224]) by hub.freebsd.org (Postfix) with ESMTP id 1538D37B960; Sat, 10 Jun 2000 18:01:29 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA11913; Sat, 10 Jun 2000 18:05:25 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200006110105.SAA11913@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Luoqi Chen Cc: dcs@newsguy.com, current@FreeBSD.ORG, emulation@FreeBSD.ORG Subject: Re: VMware detection code in boot loader In-reply-to: Your message of "Sat, 10 Jun 2000 20:40:12 EDT." <200006110040.e5B0eB514121@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 10 Jun 2000 18:05:25 -0700 From: Mike Smith Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > As for setting registers ti specific values... huh? Why does this > > matter? Can you explain exactly what your code does and how? > > > VMware intercepts the inb/outb instruction to port 0x5658 when the eax > register is set to a magic value, otherwise it would be handled as any > other ports. I think, again, that adding an i386-specific word that detects the presence of VMware is a perfectly sensible idea, and it should simply be done. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message