>
> > The loader won't help you because you are booting from under DOS, but
> > the loader will boot the kernel just fine off a DOS filesystem.
>
> I'd like to understand this aspect of the loader better. This mode
> might be useful for booting from (for example) a DOS flash filesystem?
Typica
Lets also consider the case of a root partition exists on a device which the
BIOS does not support, but DOS and FreeBSD do. A good example of this may be
a SCSI controller without a BIOS, or maybe a network style load. A person
could have just the kernel on the DOS parition, or have the driver for
Anthony writes,
>
>The problem which remains unsolved is how to boot FreeBSD from
>DOS/Windows without the ability to use a boot floppy or boot CD.
>
>Perhaps a DOS/Windows utility which installs boot blocks?
>
Such a utility may be useful in most cases, but I do not want to have to
mess around wit
Maxim writes,
>Correct me if I'm wrong, but loader is unable to directly load kernel from
>non-FreeBSD partition (DOS in your case), so problem is slightly more
>complicated but I though your can take PicoBSD (FreeBSD on floppy) and
tweak it
>to match your needs.
>
I have tried booting /boot/loader
The problem which remains unsolved is how to boot FreeBSD from
DOS/Windows without the ability to use a boot floppy or boot CD.
Perhaps a DOS/Windows utility which installs boot blocks?
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the mes
"Carlos C. Tapang" wrote:
> Thanks to all who pitched in their input to this issue. Most users of my
> system are running Windows and don't want to have to reformat or repartition
> their hard disk. So I am stuck with the DOS file system. I think the best
> solution is to have my users use a FreeB
On Wed, 19 May 1999, Luoqi Chen wrote:
> > Jonathan Lemon says:
> > :
> > : Not true. VM86 is also required to support VESA. Also, it is used
> > : for reliable memory detection (which is why I want to make it mandatory).
> > : No more "My Stinkpad only detected 64M, what do I do now??!" quest
ously confuse matters.
>>
>>Incidentally (to correct a point made in an earlier post) *all*
>>versions of DOS since 1.x have changed interrupt vectors. This is
>>not a DOS 7+ phenomenon. The reason FBSDBOOT.EXE is deprecated at
>>this stage is that, in the fut
the potential to seriously confuse matters.
>
>Incidentally (to correct a point made in an earlier post) *all*
>versions of DOS since 1.x have changed interrupt vectors. This is
>not a DOS 7+ phenomenon. The reason FBSDBOOT.EXE is deprecated at
>this stage is that, in the future, VM86 will be
> > > > Therefore it *MAY* be possible to make a DOS 6.0, 6.20 or even 6.22
> > > > boot floppy which runs FBSDBOOT.EXE to boot your a.out FreeBSD kernel
> > > > and hence the whole system.
> > >
> > > Obviously it makes no sense at all to
On May 05, 1999 at 12:27:31PM -0700, Mike Smith wrote:
> The issue here is that the BIOS will tell us how much memory we are
> _allowed_to_use_, which is not always the same as the amount of
> physical memory present in the system. Some memory may be (is
> sometimes) reserved for use by eg. APM
> > > Therefore it *MAY* be possible to make a DOS 6.0, 6.20 or even 6.22
> > > boot floppy which runs FBSDBOOT.EXE to boot your a.out FreeBSD kernel
> > > and hence the whole system.
> >
> > Obviously it makes no sense at all to make special DOS boot flo
> > Not at all. If there's 640k chopped off the end of eg. 128M of
> > physical memory, you'd have to use a 64M segment, a 32M segment, a 16M
> > segment, an 8M segment, a 4M segment, a 2M segment, a 1M segment, a
> > 256k segment and a 128k segment to map it accurately. That's 9
> > variable
On May 05, 1999 at 03:38:05AM -0400, Jerry Alexandratos wrote:
> Jonathan Lemon says:
> :
> : Not true. VM86 is also required to support VESA. Also, it is used
> : for reliable memory detection (which is why I want to make it mandatory).
> : No more "My Stinkpad only detected 64M, what do I do
> > Therefore it *MAY* be possible to make a DOS 6.0, 6.20 or even 6.22
> > boot floppy which runs FBSDBOOT.EXE to boot your a.out FreeBSD kernel
> > and hence the whole system.
>
> Obviously it makes no sense at all to make special DOS boot floppy with older
> DOS
> Not at all. If there's 640k chopped off the end of eg. 128M of
> physical memory, you'd have to use a 64M segment, a 32M segment, a 16M
> segment, an 8M segment, a 4M segment, a 2M segment, a 1M segment, a
> 256k segment and a 128k segment to map it accurately. That's 9
> variable MTRRs, an
> > Jonathan Lemon says:
> > :
> > : Not true. VM86 is also required to support VESA. Also, it is used
> > : for reliable memory detection (which is why I want to make it mandatory).
> > : No more "My Stinkpad only detected 64M, what do I do now??!" questions.
> >
> > Actually, even with VM86,
Matthew Thyer wrote:
> Therefore it *MAY* be possible to make a DOS 6.0, 6.20 or even 6.22
> boot floppy which runs FBSDBOOT.EXE to boot your a.out FreeBSD kernel
> and hence the whole system.
Obviously it makes no sense at all to make special DOS boot floppy with older
DOS
just to run
FBSDBOOT.EXE to boot your a.out FreeBSD kernel
and hence the whole system.
Hopefully now that Carlos Tapang has updated FBSDBOOT.EXE for ELF, such
a boot floppy could boot a 3.1, 3.2 or -CURRENT system.
Unfortunately the project cannot guarantee anything when you are booting
from another vendor&#
> Jonathan Lemon says:
> :
> : Not true. VM86 is also required to support VESA. Also, it is used
> : for reliable memory detection (which is why I want to make it mandatory).
> : No more "My Stinkpad only detected 64M, what do I do now??!" questions.
>
> Actually, even with VM86, the kernel st
Jonathan Lemon says:
:
: Not true. VM86 is also required to support VESA. Also, it is used
: for reliable memory detection (which is why I want to make it mandatory).
: No more "My Stinkpad only detected 64M, what do I do now??!" questions.
Actually, even with VM86, the kernel still doesn't co
ably because I do not have vm86 enabled.
The problem only comes into play during case 2; where the kernel actually
calls the BIOS. The difficulty is that while FBSDBOOT.EXE may work in some
cases, it is not guaranteed to work in _all_ cases (which causes a support
nightmare).
--
Jonathan
To Un
>
>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. I
> DOS, when it boots, loads itself into memory somewhere, and then
> changes the interrupt vectors to point to itself.
How does Linux do it with loadlin?
Tim
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
In article
you
write:
>Mike, Thanks for trying fbsdboot.exe. I need more information to fix it. I
>would like to fix it, so please describe exactly what the problem is. What
>do you mean by the "need to reboot the system to restore various vectors
>that DOS destroys"? Do
Mike, Thanks for trying fbsdboot.exe. I need more information to fix it. I
would like to fix it, so please describe exactly what the problem is. What
do you mean by the "need to reboot the system to restore various vectors
that DOS destroys"? Do you mean that prior to executing the Free
hinking aloud :-)
>
> The only way to get a clean slate with the system is to reboot. If you
> can arrange a "controlled" reboot of some sort, we might get somewhere.
If you are going to reboot anyway, its not too much to ask for a bootable
floppy/cd
> > It doesn't work. Don't use it. You need to reboot the system to
> > restore various vectors that DOS destroys. Please see the previous
> > threads on this topic, especially anything from Robert Nordier.
>
> Would it be possible to add a driver to config.sys which could record the
> variou
On Sun, 16 May 1999, Mike Smith wrote:
> > Hi,
> >
> > At 15:22 11/05/99 -0700, you wrote:
> > >Because I need it, I have upgraded fbsdboot.exe so now it can recognize
> > >ELF.
> > >If anybody else needs it, please let me know and I'll see what
> The loader won't help you because you are booting from under DOS, but
> the loader will boot the kernel just fine off a DOS filesystem.
I'd like to understand this aspect of the loader better. This mode
might be useful for booting from (for example) a DOS flash filesystem?
Um... off to the s
m R. Nordier is the following:
> "The fbsdboot.exe program should probably be considered obsolete. It
> should (in theory) be possible to use it to load /boot/loader, which
> can then load the kernel, but there are various reasons this doesn't
> work too well."
These reasons were
>It doesn't work. Don't use it. You need to reboot the system to
>restore various vectors that DOS destroys. Please see the previous
>threads on this topic, especially anything from Robert Nordier.
>
The most relevant piece I can find from R. Nordier is the following:
&qu
On Sun, 16 May 1999, Mike Smith wrote:
> > Hi,
> >
> > At 15:22 11/05/99 -0700, you wrote:
> > >Because I need it, I have upgraded fbsdboot.exe so now it can recognize
> > >ELF.
> > >If anybody else needs it, please let me know and I'll see
> Hi,
>
> At 15:22 11/05/99 -0700, you wrote:
> >Because I need it, I have upgraded fbsdboot.exe so now it can recognize ELF.
> >If anybody else needs it, please let me know and I'll see what I can do for
> >you.
>
> I'm going to have a use for it RSN
@FreeBSD.ORG
Date: Tuesday, May 11, 1999 10:45 PM
Subject: Re: FBSDBOOT.EXE
>hi, there!
>
>On Tue, 11 May 1999, Carlos C. Tapang wrote:
>
>> Because I need it, I have upgraded fbsdboot.exe so now it can recognize
ELF.
>> If anybody else needs it, please let me know and I&
hi, there!
On Tue, 11 May 1999, Carlos C. Tapang wrote:
> Because I need it, I have upgraded fbsdboot.exe so now it can recognize ELF.
> If anybody else needs it, please let me know and I'll see what I can do for
> you.
> ps. I had to use my old Microsoft Visual C++ (ve
Hi,
At 15:22 11/05/99 -0700, you wrote:
>Because I need it, I have upgraded fbsdboot.exe so now it can recognize ELF.
>If anybody else needs it, please let me know and I'll see what I can do for
>you.
I'm going to have a use for it RSN
>ps. I had to use my old Microsoft V
Because I need it, I have upgraded fbsdboot.exe so now it can recognize ELF.
If anybody else needs it, please let me know and I'll see what I can do for
you.
ps. I had to use my old Microsoft Visual C++ (ver 1.5) to do this
modification.
Carlos C. Tapang
http://www.genericwindow
> Won't fbsdboot.exe be able to boot /boot/loader? (maybe I am just naive)
> (or could it be modified to do so with little effort?)
We've had this discussion. No.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.n
> Does this mean that install.bat will disappear as well?
It already did.
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
On Saturday, 1 May 1999 at 17:54:26 -0700, Jordan K. Hubbard wrote:
>> Is there anybody out there working on upgrading fbsdboot.exe so that it can
>> recognize ELF?
>
> I believe that fbsdboot.exe has, instead, simply been retired. Sorry
> I don't have better news than
> Won't fbsdboot.exe be able to boot /boot/loader? (maybe I am just naive)
> (or could it be modified to do so with little effort?)
Good question - you tell me. :)
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Won't fbsdboot.exe be able to boot /boot/loader? (maybe I am just naive)
(or could it be modified to do so with little effort?)
--
David Cross | email: cro...@cs.rpi.edu
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd
Renss
> Is there anybody out there working on upgrading fbsdboot.exe so that it can
> recognize ELF?
I believe that fbsdboot.exe has, instead, simply been retired. Sorry
I don't have better news than this.
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe
Is there anybody out there working on upgrading fbsdboot.exe so that it can
recognize ELF?
Carlos C. Tapang
http://www.genericwindows.com
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
45 matches
Mail list logo
