Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!hc!beta!hgm
From: hgm@beta.UUCP (Harry McGavran)
Newsgroups: comp.os.minix
Subject: Re: fsck fails on hard disk
Message-ID: <5128@beta.UUCP>
Date: Wed, 6-May-87 18:23:26 EDT
Article-I.D.: beta.5128
Posted: Wed May  6 18:23:26 1987
Date-Received: Sat, 9-May-87 01:31:03 EDT
Organization: Los Alamos Natl Lab, Los Alamos, N.M.
Lines: 20


One additional note to the item I posted earlier about the bootblok
stack causing problems.  It has been mentioned in this news group
that some conrtollers with configurable tables place the tables
in the vector space. That is true, but some of these controllers
and others as well, place other things there too. My problems
with fsck occurred even though I was not using configurable tables.
I was using hardwired tables, in C800:xxxx.  Other parameters
put below 0000:0500 by the controller for use later by its bios
were being clobbered as well. So, depending on your controller,
independently of whether the disk tables are configurable, fsck may
fail because of the stack problem.


Harry McGavran
hgm@LANL.GOV
Los Alamos National Laboratory
MS-B294, Group C-8
Los Alamos, New Mexico 87545
505/667-4050