From owner-freebsd-current Wed Oct 7 07:08:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA25324 for freebsd-current-outgoing; Wed, 7 Oct 1998 07:08:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25291 for ; Wed, 7 Oct 1998 07:08:34 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id QAA16921; Wed, 7 Oct 1998 16:05:15 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id PAA00639; Wed, 7 Oct 1998 15:57:21 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199810071357.PAA00639@semyam.dinoco.de> To: "Viren R. Shah" Cc: freebsd-current@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: boot loader problems.. In-reply-to: Your message of "Wed, 07 Oct 1998 14:40:26 +0200." <199810071240.OAA25584@semyam.dinoco.de> Date: Wed, 07 Oct 1998 15:57:20 +0200 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > yesterday evening) and I don't know why. It could be a BIOS bug or a > bug with returning flags in the new boot loader's VM86 code I think. I It was a bug in VM86 interrupt usage which caused the trouble I have seen with the fix suggested by Mike Smith. I have it working for me now. See my other mail where I included a new fix which now works for me. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message