Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!hp4nl!star.cs.vu.nl!raymond
From: raymond@cs.vu.nl (=Raymond Michiels)
Newsgroups: comp.os.minix
Subject: Re: Trouble with Amiga floppies - a possible solution
Message-ID: <7897@star.cs.vu.nl>
Date: 11 Oct 90 07:48:42 GMT
References: <33009@nigel.ee.udel.edu>
Sender: news@cs.vu.nl
Lines: 31

JAGBDED1%PANAM.BITNET@ricevm1.rice.edu writes:

>   This is not the real problem though.  The minix floppy driver is somehow
>corrupting every floppy it writes on.  If you run minix without write
>protection, you soon end up with many unreadable floppies.

OK, so it seems that are some minor (ahem) problems with AmigaMINIX.
We are willing to fix the problems, but until now we don't have a clue
as to what the problems are.

We do know that all BOOT disks have a read error in the "minix.img"
file, but fortunately enough we have included a backup of this file
("minix.img.bu").  Other problems that I have heard of are other
unreadable disks (MINIX file systems) and, as Joe Gonzalez found out,
that AmigaMINIX can't read back data it has written to disk.

Since we have debugged MINIX before we shipped it to P-H we are
wondering what might cause the abovementioned problems. To get a better
idea of the situation I would like to have a small reports on people's
experiences with AmigaMINIX: good and bad, from America and Europe,
on A500's, and A2000's, etc, etc. When we know what is going on, you'll
be the first to know.

I have tried AmigaMINIX at several other places and haven't found any
of the described bugs, so I really am curious as to what is happening.

	-Raymond.

PS: Just in case you're wondering: I have personally recompiled AmigaMINIX
    from scratch on my own Amiga500 (1 disk driver, 1.5Mb) without any
    errors.