----- Original Message -----
From: "Gilbert Baron" <[EMAIL PROTECTED]>
To: "Stephen Bosch" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, August 02, 2000 12:11 PM
Subject: RE: [expert]
>
>
> >-----Original Message-----
> >From: Stephen Bosch [mailto:[EMAIL PROTECTED]]
> >Sent: Wednesday, August 02, 2000 10:59 AM
> >To: Gilbert Baron
> >Cc: [EMAIL PROTECTED]
> >Subject: RE: [expert]
> >
> >
> >
> >
> >On Wed, 2 Aug 2000, Gilbert Baron wrote:
> >
> >> >> > I told you. Nobody ever asked before. It is the BIOS that
> >handles this
> >> >> > anyhow is it not. Version 7/1 should not se anything that
> >7.0 did not.
> >> >> > This message is useless, it does not ell why it is refusing to
> >> >accept it.
> >> >
> >> >I think you will find that with Linux, the BIOS only handles the drive
> >> >until the relevant parts of the kernel have loaded. After that, Linux
> >> >handles the job itself.
> >> >
> >>
> >> This would be stupid in my opinion. There are too many drives.
> >It is like no
> >> drivers would be written and it will all be in the Kernel..
> >> It is The BIOS that makes an API that is constant and that is
> >the way I am
> >> sure it is done.
> >
> >No, Ozz is correct. Linux does not rely on the BIOS for disk access - the
> >BIOS is only invoked during initial boot, just long enough to allow the
> >system to read the master boot record.
>
>
> >Windows relies on the BIOS for I/O -- Linux does not.
> >
> >Ironically, this lets you use large drives in Linux with *very* old BIOS
> >and motherboards - Windows cannot make the same claim, as it relies
>
> What you are saying is that you replace the BIOS with your own. Many old
> boards did this to support things not yet supported in dos, like the
Promise
> IEDE board controller.
>
> In any case, it should support today, anything, it supported yesterday. It
> does not.
>
> If anyone can explain why I can load 7.0 but not 7.1 and can explain why
> this should be so, perhaps I could be convinced, but I doubt it.
>
>
>
> >entirely on the BIOS. Yes, there are many drives -- but the BIOS still
has
> >to be able to talk to them, right? How big is the BIOS? 512k? Not many
> >drivers would fit in there, I'd say.
> >
> >That's why we have standardization.
> >
> >If you still think this is a stupid way of doing it, please write a new
> >operating system and let me know when you are finished. I will be sure to
> >try it.
> >
> >-Stephen-
> >
The problem is not a hardware problem I have the same Maxtor hd in one of my
systems. I specificly choose that hd because I have a somewhat older MOBOand
BIOS which only supports UDMA 33.
I have been able to install and run 7.0 and 7.1. I did each as a New
Installation in a clean partition and let the installation actually do the
partitioning.
If PM is used to set up the partitions on this hd then the 7.1
installation gives the file type error. In my case I believe this is caused
by the combination of different partitioning tool used but
mostly because I formated the drive using the MaxBlast software that came
with the drive.
Could this not be the cause of the install problem you are having?
And before you ask why this happens in 7.1 and not 7.0 it is because in
7.0 a /boot partition is reguired in 7.1 it is not and the MaxBlast program
screws this up because it lies to the BIOS and gives an incorrect reading to
the installation program so that the sectors do not match thereby not
allowing it to see a valid file system.
Charles
