George Hartzell wrote:
> On boot I get "Loading GRUB... Please Wait..." but after that I get "GRUB
> Error 17" which according to the manual means that GRUB doesn't know how to
> load the selected partition. Even though when I boot from the floppy it
> starts no problem and I can type commands to
George Hartzell writes:
> [...]
> grub> setup (hd0)
>
> Here you boot process would be
>
> power on->bios->load the MBR which is really GRUB->grub loads its stage1,...
>
> Or you could leave a "normal" MBR at the beginning of the disk and
> install GRUB into the beginning of the Free
Andrew Boothman writes:
> [...]
> OK Guys, I think I'm still a little confused here.
>
> I've just had a few botched installs of GRUB so I think I need a little more
> direction, if you could :)
>
> I've got GRUB on a floppy and it boots fine. If I type :
> rootnoverify (hd0,0)
> makeact
I have never emailed this list, and am only reading it to see how
5.0-RELEASE is shaping up. Sorry if I'm repeating stuff or commenting out
of turn.
This problem sounds like the one I've had on several occasions when
repartitioning my HDD.
My Windows2000 "boot.ini" invariably needs to be u
Darryl Okahata writes:
> [EMAIL PROTECTED] (George Hartzell) wrote:
>
> > Only differences are which partition we mark active and what boot
> > loader lives there.
>
> True, but that's the key point: "... and what boot loader lives
> there." There are times when not touching the boot
[EMAIL PROTECTED] (George Hartzell) wrote:
> Only differences are which partition we mark active and what boot
> loader lives there.
True, but that's the key point: "... and what boot loader lives
there." There are times when not touching the boot loader is desirable.
While GRUB, booteasy,
Darryl Okahata writes:
> [...]
> I installed 5.0 with the booteasy MBR on my IBM laptop, and it
> worked fine. The problem I had was that *ANY* MBR-based boot program
> interfered with IBM's special "product recovery" software, and so I
> instead decided to just use Win2K/XP's boot mecha
[EMAIL PROTECTED] (George Hartzell) wrote:
> I'm pretty sure that it's not operator error on my part, since it
> happened several times. I suspect that there aren't that many people
> playing with 5.0 that don't install the standard boot stuff, and so
> that path isn't exercised too much.
I
Andrew Boothman writes:
> [...]
> It's possible I guess that we both suffered from the same problem. I'd
> be inclined to think that it must be operator error over something wrong
> with sysinstall since I've not seen people complaining of these problems
> before, yet there must be loads of
walt <[EMAIL PROTECTED]> wrote:
> For example, IIRC, I just went thru this myself (although it's all so routine
> now I can't even remember what I do to bail out anymore) when I installed XP
> on a brand new disk and then installed FBSD afterwards. I got the MBR screwed
> up just like you, then r
My experience with the FBSD boot manager is virtually zero, so I can't
address it's workings, but I use GRUB as a booter just because it gets
me out of so many jams like yours -- if something isn't where you thought
it was you can point GRUB at your disks and let it do the looking for you.
The se
George Hartzell wrote:
Andrew Boothman writes:
> [...]
> I didn't really change much about my system when I installed FreeBSD.
>
> Windows is installed on the whole of the first HDD, and FreeBSD on the whole of
> the second. Prior to installing 5.0, the second disc had an old installation of
>
Matt Smith wrote:
What does your Drive Layout look like? Is your W2k partition FAT32?
Has it always been the first partition on the drive, or did you move it,
using something like partition magic? Is freeBSD in the extended
partition?
-Matt
On Tue, 2003-02-25 at 11:58, Andrew Boothman wrote:
Qu
Hi!
I also encountered the same problem and I thought it was my own mistake.
Attempt to repair the partition failed. Even new installation was
failed. I did fdisk /mbr after booting through diskette into dos and
then installing fresh windows 2000 also failed. The copy process from cd
to hd is okay
Andrew Boothman writes:
> [...]
> I didn't really change much about my system when I installed FreeBSD.
>
> Windows is installed on the whole of the first HDD, and FreeBSD on the whole of
> the second. Prior to installing 5.0, the second disc had an old installation of
> 4.6 that I wasn't
Quoting Matt Smith <[EMAIL PROTECTED]>:
> What does your Drive Layout look like? Is your W2k partition FAT32?
> Has it always been the first partition on the drive, or did you move
> it,
> using something like partition magic? Is freeBSD in the extended
> partition?
> -Matt
> On Tue, 2003-02-25
What does your Drive Layout look like? Is your W2k partition FAT32?
Has it always been the first partition on the drive, or did you move it,
using something like partition magic? Is freeBSD in the extended
partition?
-Matt
On Tue, 2003-02-25 at 11:58, Andrew Boothman wrote:
> Quoting Lucas Holt
Quoting Lucas Holt <[EMAIL PROTECTED]>:
> It probably is. You need to put in the win 2k CD and do a repair on
> your windows install.. unfortunetely this may screw up your freebsd
> install.
>
> On Tuesday, February 25, 2003, at 05:58 AM, Andrew Boothman wrote:
>
> > Hi!
> >
> > I've just in
18 matches
Mail list logo
