Date: Thu, 7 May 1998 06:05:24 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: jlemon@americantv.com (Jonathan Lemon) Cc: thyerm@camtech.net.au, mike@smith.net.au, current@FreeBSD.ORG Subject: Re: 'fatal trap 12' on boot (smp and up) Message-ID: <199805070605.XAA11817@usr02.primenet.com> In-Reply-To: <19980506104909.14890@right.PCS> from "Jonathan Lemon" at May 6, 98 10:49:09 am
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. My suggestion would be to run the icon as "real mode". I almost posted this last night, but didn't, because I was lacking the data you just supplied. The magic incantation should be: Right-button Properties Memory Thwen check the "run in real mode" (or similarly named) checkbox on the icon. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. 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?199805070605.XAA11817>