Mike,
> this smacks of the 8gig limit. Is your motherboard cabable?
> What boot manager
> is causing bios to report an error? Is lilo the later version?
I never get to the LILO loader -- the "Primary Master Hard Disk Fail"
message comes first. This is just after the "Bios Successfully Installed"
message. It occurs even when I'm booting from a floppy (which is the first
boot device).
> A quick check incidentally of discovering bios
> incompatibilties is to install
> windoze. The cmos CAN dsicover the real size of the drive,
> but if the bios
> cannot use ead, then windoze will limit that drive to 8gig no
> matter what.
Installing Windoz is the "quick" test? I've never found that to be less
than a 4 hour job. Of course, the only M$ OS I have available is NT 4.0
(workstation or server), and I scraped that off to run a decent OS some time
ago. I'd prefer a simpler way to test it.
Incidentally, it strikes me as counter-productive for Linux users to decry
the nasty folks at M$ while expecting to find and use M$ and DOS tools to
fix/run our systems. Hmm. Maybe we need more tools of our own.
Last night's results:
Linux fdisk does not have a /mbr option. I suspect that is dos. I couldn't
find anything in man of fdisk on how to write the mbr, so in ran YaST2
(since I'd booted SuSE with the floppy). In Yast I found where to write
LILO to the MBR, and did so. Rebooting showed no change to the situation.
I suspect you are right about the 8GB limit, so I'll look into that in
toady's reading. Debugging the home system from tips I pick up in spare
time at work is difficult.
Thanks to all for suggestions so far.
Tom
_______________________________________________
http://linux.nf -- [EMAIL PROTECTED]
Archives, Subscribe, Unsubscribe, Digest, Etc
->http://linux.nf/mailman/listinfo/linux-users
