Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!njin!princeton!udel!mmdf
From: PRINS%HLERUL5.BITNET@cunyvm.cuny.edu (Ryko Prins, CRI, Leiden, Netherlands)
Newsgroups: comp.os.minix
Subject: Megafile 60 problems, again.
Message-ID: <10013@louie.udel.EDU>
Date: 2 Mar 89 11:52:16 GMT
Sender: mmdf@udel.EDU
Lines: 18

I am still trying very hard to get Minix working on my Megafile 60, but Minix
still fights back v e r y effectively.
If I for example build a (original, distributed) system with a stwini.c with
TRACE enabled, and try "mkfs /dev/hd3 512" (partition 3) then after a lot of
trace messages which seem OK as such I get a kernel panic from -1.
If I afterwards try to reboot my ST that often fails because Minix has filled
some sectors of partition C: (partition 1) and has a definite preference for
(main) directory sectors.

I use A Mega 2, Minix BOOT on single sided floppy, ROOT, USR, etc. on double
sided floppy, 1 Meg Ramdisk.

Does anyone has an explanation how Minix can destroy data on a partition it
should stay off?

I hardly dare to use Minix on my hard disk anymore.

                                        Greetings, Ryko Prins.