Erich Boleyn <[EMAIL PROTECTED]> wrote:
...
> Yes. I've noticed this and a few other problems which appear to have
> been caused by "cleanups" to my original code by others working on it.
...
> I think part of the point here is that a bootloader has a lot of
Jeff Sheinberg <[EMAIL PROTECTED]> wrote:
> Grub will either report false information or go into an infinite
> loop when the disk media on (fd0) is physically changed.
Yes. I've noticed this and a few other problems which appear to have
been caused by "cleanups" to my original code by others
Erich Boleyn <[EMAIL PROTECTED]> wrote:
> Uhh, how could GRUB's notion of the geometry of a hard disk screw things
> up? The standard hard disk BIOS calls are very reliable.
OK, I have seen some problems with the GNU version of GRUB and the way
it is probing for floppies (no
Goran Koruga <[EMAIL PROTECTED]> wrote:
...
> Yes it does - I think I know where the problem is. I already had problems
> when I hosed my partition table by creating new partitions with Linux's
> fdisk because the geometry is incorrect (or rather different than the
> one used when creating the v
OKUJI Yoshinori <[EMAIL PROTECTED]> wrote:
> > One of them would be generated by a modified isapnp from isapnp.conf
> > I don't want to embed a bison parser into GRUB. It is much easier to
> > generate i386 code that just writes to the ports.
>
> I agree.
The disadvantage to this, if I'm und
OKUJI Yoshinori <[EMAIL PROTECTED]> wrote:
> > Has this been changed since the old GRUB 0.5? It was there for a
> > reason.
>
> Yes, we have changed this to use BIOS, because your original code
> didn't work with the "floppy emulation" in the El Torito
> specification. It seems that we shoul
Pavel Roskin <[EMAIL PROTECTED]> wrote:
> On Wed, 22 Sep 1999, Rogelio M. Serrnao wrote:
>
> > I have an IBM PS2 77s with a 2.88 Mb disk drive. I dd'd GRUB stage1 and
> > stage2 on a 1.44 Mb diskette. When I try to boot from that diskette, all I
> > get is "Read Error".This does not happen with
Edmund GRIMLEY EVANS <[EMAIL PROTECTED]> wrote:
> (2) LBA didn't work for me with grub-0.5.92. I installed stage1_lba,
> with no errors, but I got a "Disc geometry error" or something similar
> when I tried to boot. Is this a known problem?
I have seen a few errors in the LBA code in the GRUB s
Edmund GRIMLEY EVANS <[EMAIL PROTECTED]> wrote:
> I don't understand autoconf, but I found that I can't build the CVS
> version of GRUB unless I replace "-DEXT_C=\(sym\)\ sym" by
> "-DEXT_C\(sym\)=sym" in config.status after running ./configure.
You probably already heard this from someone else
Pavel Roskin <[EMAIL PROTECTED]> wrote:
> > The one thing to remember in this is that if you discard the BPB
> > compatibility, then FAT-formatted floppies will not be bootable any
> > longer. This has been highly useful for some research OSes that people
> > have worked on in the past. I stil
OKUJI Yoshinori <[EMAIL PROTECTED]> wrote:
> From: "Chris Jones" <[EMAIL PROTECTED]>
> Subject: RE: Why do we preserve the BPB???
> Date: Tue, 31 Aug 1999 21:07:50 -0500
>
> > one person out there who can use the functionality, I will see what I
> > can do to preserve the BPB in the new loader.
Pavel Roskin <[EMAIL PROTECTED]> wrote:
...
> menu.diff
>
> More meaningful example for using "pause"
> Example on how to boot FreeBSD from BSD subpartitions
> Using (hd0,0) instead of (0x80,0) to avoid confusion. One could ask -
> why do Unices use hd0 whereas the OS'es from Redmond use 0x80 ?
"Chris Jones" <[EMAIL PROTECTED]> wrote:
> Would someone please explain to me why we preserve the BPB? Am I wrong in
> assuming that Grub will always just chain load DOS/WindowsXX/OS2?
>
> The way I see it, if Grub is installed in the MBR of a hard drive, then the
> BPB isn't needed. If Grub
13 matches
Mail list logo
