From owner-freebsd-current Tue May 18 16:58:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from jumping-spider.aracnet.com (jumping-spider.aracnet.com [205.159.88.14]) by hub.freebsd.org (Postfix) with ESMTP id 6A32E15322 for ; Tue, 18 May 1999 16:58:14 -0700 (PDT) (envelope-from ctapang@easystreet.com) Received: from apex (216-99-199-225.cust.aracnet.com [216.99.199.225]) by jumping-spider.aracnet.com (8.9.1/8.9.0) with SMTP id QAA04560; Tue, 18 May 1999 16:57:55 -0700 Message-ID: <00b201bea18a$93afbfc0$0d787880@apex.tapang> From: "Carlos C. Tapang" To: "Jonathan Lemon" , Subject: Re: FBSDBOOT.EXE Date: Tue, 18 May 1999 17:00:16 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >In a nutshell, there is a table of interrupt vectors which is set >by the BIOS at boot time, which are used by the loader (and by the >FreeBSD kernel, if VM86 is turned on). > Thanks, Jonathan. Are any of the following TRUE? 1. FreeBSD is affected by these vectors only if VM86 is turned ON. 2. If somebody is using VM86, s/he must be using DOSEMU or some other DOS emulator also (I can't think of anything else one would use VM86 for). 3. DOSEMU or any other DOS emulator re-initializes the DOS vectors for virtualization. Basically, what I am guessing is that probably we can fix the problem during vm86 or DOSEMU initialization. I am going to enable vm86 on my system and see what happens. Right now I am not experiencing any problems, and that's probably because I do not have vm86 enabled. --Carlos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message