Date: Fri, 26 Jun 1998 17:05:15 +0930 From: Matthew Thyer <Matthew.Thyer@dsto.defence.gov.au> To: Matthew Thyer <thyerm@camtech.net.au> Cc: Terry Lambert <tlambert@primenet.com>, Jonathan Lemon <jlemon@americantv.com>, mike@smith.net.au, current@FreeBSD.ORG Subject: Re: 'fatal trap 12' on boot (smp and up) Message-ID: <35934F33.4DF43083@dsto.defence.gov.au> References: <199805070605.XAA11817@usr02.primenet.com> <3552CFD5.C829866B@camtech.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
I didn't get around to trying this for a while but now that I have, there is no way to select "real mode" or anything much at all. I think you must have been thinking about Windows 3.X where you could do these things. So my question still stands: Is there anyway to use fbsdboot.exe to boot FreeBSD after Windows 95 has restarted into DOS (to run your DOS program) when you have "options VM86" in your kernel ? This is useful to be able to get into a real OS from Windows via an icon. Many people who run multiple OS's rely on fbsdboot to recover when their boot block has been trashed. I'm concerned that we may end up in a situation where people cannot use fbsdboot.exe (i.e. when "options VM86" is not optional and a future versions of DOS will have changed these vectors). Can this memory check be changed to detect whether the vectors have been changed ?? Matthew Thyer wrote: > > Thanks Terry, > > I thought there had to be a way.... I will try this tonight > (Australian night!). > > Terry Lambert wrote: > > > > > 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 -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 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?35934F33.4DF43083>