*BSD News Article 19811


Return to BSD News archive

Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!vixen.cso.uiuc.edu!sdd.hp.com!network.ucsd.edu!news.cerf.net!crash!warelock
From: warelock@crash.cts.com (Tom Zacharoff)
Subject: Re: bad144 problem?
Organization: CTS Network Services (crash, ctsnet), El Cajon, CA
Date: 22 Aug 93 09:09:35 PDT
Message-ID: <1993Aug22.090935.24595@crash>
References: <f1Io03hUd8E400@amdahl.uts.amdahl.com>
Lines: 12

Alistair G. Crooks (agc@uts.amdahl.com) wrote:
: 
: This is incorrect for NetBSD 0.8 - I'm not sure about 386bsd, it's
: been a long time.  The reason for this is that the BIOS is used to
: read the bad sector table during the NetBSD boot process, and the BIOS
: maxes out at 1023 cylinders.  (During boot, if you get the message
: "Bad badsect table" displayed, you've got this problem.)

Hmmm. I've got 979 cylinders and I get the error message "Bad badsect table".
Can someone please explain what is up with this bad sector forwarding? Does
it work at all? Or should I just resort to the badsect program instead of the
bad144 program?