Date: Wed, 6 May 1998 10:49:09 -0500 From: Jonathan Lemon <jlemon@americantv.com> To: Matthew Thyer <thyerm@camtech.net.au> Cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG Subject: Re: 'fatal trap 12' on boot (smp and up) Message-ID: <19980506104909.14890@right.PCS> In-Reply-To: <35505AEA.790DF80@camtech.net.au>; from Matthew Thyer on May 05, 1998 at 10:13:22PM %2B0930 References: <199805061016.DAA02535@antipodes.cdrom.com> <35505AEA.790DF80@camtech.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 05, 1998 at 10:13:22PM +0930, Matthew Thyer wrote: > It's sad to see that fbsdboot.exe will effectively become unusable > after VM86 becomes a mandatory option. > > Am I correct in that assumption ?? I'm still investigating (sorry for not replying earlier) but it looks like that is effectively the case. Once a Win/DOS program hooks the BIOS vector, all bets are off. Unless: - there a way to force Win/DOS to "un-hook" themselves? - there an INTx call or something that can reset the interrupt vector table to a "pristine" setate? I won't have time to look at this for about 2 weeks or so, until finals are over. However, one possibility would be to set some sort of "flag" from fbsdboot to indicate that the BIOS is unavailable. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980506104909.14890>