On Fri, 13 Sep 2002, Jochen Kunz wrote:

> On Fri, Sep 13, 2002 at 07:09:06AM -0700, Roger Ivie wrote:
>
> > Oh, I know the bug was there and I know I got bzapped by it. What I don't
> > know is whether the NetBSD folks have fixed the bug yet.
> It should be fixed. The dz driver is the suspicious object and it has
> a "if (machine == VS4K9x) { don't probe}" in it now. What we need is
> someone with a untouched machine who installs NetBSD 1.6 and confirms
> that the bug is really gone. Dayly snapshoots are at:
> ftp://releng.netbsd.org/

  It has been fixed.  I was working on installing NetBSD on a 4000/90, and
was trying very hard to only boot fixed kernels.  There were no problems,
until I managed to forget once, and now my 4000/90 has the modified flash
memory bug.

  I started working on a program to try to fix it (but haven't had the
time to work on it for serveral months now).  One problem is that if the
program doesn't work right, I could easily end up with an erased flash
memory, or a partially erased flash memory, or a partially programmed
flash memory.  [As best I've been able to determine, the flash memory has
to be total erased and rewritten with the new image.]

--
Michael L. Hitch			mhitch@montana.edu
Computer Consultant
Information Technology Center
Montana State University	Bozeman, MT	USA