Hello, Erich!
> > This time BIOS apparently believes that all diskettes in 2.88M drives
> > should also be 2.88M
> > Stage1 tries to read sectors above 18 and gets an error.
>
> The point is that, with the iterative probe, both the stage1 and stage2
> should not believe the BIOS anyway.
Neither
OKUJI Yoshinori <[EMAIL PROTECTED]> wrote:
> I'm sorry, your problem was due to a bug in configure. I have fixed
> the bug.
Here is another one:
--- configure.cvs Thu Sep 23 13:57:29 1999
+++ configure Thu Sep 23 15:07:43 1999
@@ -1720,7 +1720,7 @@
int
main (void)
{
- asm ("incl e
OKUJI Yoshinori writes:
> From: Jeff Sheinberg <[EMAIL PROTECTED]>
> Subject: Re: Installation documentation
> Date: Wed, 22 Sep 1999 17:42:39 -0400 (EDT)
>
> > IMNSHO, the block list for stage2 belongs in the first block of
> > stage2 itself. This way, stage1 only needs a pointer to the f
From: OKUJI Yoshinori <[EMAIL PROTECTED]>
Subject: Re: Cannot write stage2
Date: Thu, 23 Sep 1999 18:15:27 +0900
> I was wondering if debug_fs_func (currently, disk_read_func) was
> really necessary. If it is not needed, it is better to remove the
> variable than to rename it to something. What
From: Pavel Roskin <[EMAIL PROTECTED]>
Subject: Re: Cannot write stage2
Date: Thu, 23 Sep 1999 12:15:19 +0400 (EEST)
> What is needed is a function (disk_read_hook) and a variable (I've named
> it disk_read_file) indicating that the sectors being read belong to the
> file in question, not to othe
Hello, OKUJI!
> > Well, I've rewritten it.
>
> Thank you very much! You are a very nice guy. :)
You have renamed debug_fs_func to disk_read_func
I think it's not necessary to have two function for the same purpose.
What is needed is a function (disk_read_hook) and a variable (I've named
it d
