Date: Thu, 3 Feb 2005 12:08:12 +0400 From: Rakhesh Sasidharan <rakhesh.s@gmail.com> To: Mark Ovens <marko@freebsd.org> Cc: freebsd-questions@freebsd.org Subject: Re: Booting FreeBSD-5.3 from NTLDR Message-ID: <38b3f6e405020300081606f572@mail.gmail.com> In-Reply-To: <4200FA32.3030505@freebsd.org> References: <41FDEFE7.1090204@freebsd.org> <38b3f6e4050131074327d2e583@mail.gmail.com> <41FE578F.60706@freebsd.org> <38b3f6e405013122047a2b8206@mail.gmail.com> <20050201121049.GL8619@alzatex.com> <38b3f6e40502010704292f0b6a@mail.gmail.com> <38b3f6e405020107327b94bfd3@mail.gmail.com> <20050202094847.GP8619@alzatex.com> <38b3f6e405020207077ab28401@mail.gmail.com> <4200FA32.3030505@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 02 Feb 2005 16:05:06 +0000, Mark Ovens <marko@freebsd.org> wrote: > The limitation is in NTLDR because it's M$ so is only designed for > booting M$ OSes and the BOOTSECT file method is designed for booting DOS > and non-NT class Windows which could only boot from the first partition > on the first drive anyway therefore there is no need for NTLDR to > support booting from the second, third, etc. disk using a BOOTSECT file. Yes. I figured that yesterday after checking around. NTLDR has a limitation of not being able to boot OSes from other disks. So no, I dont think its a FreeBSD problem as such -- BootPart prolly modifies the bootsectors (while extracting) to add whatever info is required to let NTLDR boot it. :)) -- -- Rakhesh rax -at- rakhesh -dot- com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38b3f6e405020300081606f572>